jason

I'll get that up tomorrow. Can you help me figure out what's going on? I can't reproduce this. In the Installation directory: c:\Program Files (x86)\Flirc there is a flirc.ini file. Can you change all the false words to true. Then can you change loglevel = 0 to loglevel 5 Run the app, there will be a log file put on your desktop. Throw that on here, I'll take a look at what's going on. Thank you and very sorry for the trouble.

I believe you have the older one, correct? The issue reported above is definitely different. Long story short, I created another sku for a huge company who was looking to partner, and they ended up not moving forward. I repurposed that sku, but gave them a different USB Product ID in the process. The new 2.0 software has a completely re-written driver model that handles all the device communication. I simply forgot to add the AZ product id when searching for the device. This is why some people have a 'disconnected' state when opening the GUI. There was a substantial amount out there. Completely forgot about it, was about a year and a half ago.

can we set up a team viewer session? If not, at your convenience; There is a flirc.ini in the installation directory. Can you change all the false to true, then set the loglevel = 0 ---> loglevel=5 Then can you post the log?

Fix posted, let me know if this did it, and then please PM me as well Sid, I'll give you a new one as a thank you for the patience and my apologies for the trouble.

Hang tight. I see the issue. Will post an update soon.

Let's set up a team viewer. It could be a mistake in the version 2.0.0 software that I'm unable to reproduce. But this was one of my biggest gripes with the original version. I'm a bit limited with the hardware, and the new version operates completely driverless. None of this bullshit. In fact, PM me. Help me try and uncover what's wrong with this so I can issue a software update, and I'll send you the new one on the house.

Okay, no issues here. Maybe let's try and get on a team viewer session.

No, the two are currently virtually identical as far as features. I'll help figure this out. It's likely due to something I didn't catch. Please post a picture of your device manager when you have a moment.

Are you using the new metal Flirc, or the first version?

Can you try a Samsung or Panasonic? Let's just make sure it's not a problem with the device. HTPC codes are just more media center codes.

could just be because it's a media center remote. Do you have another you can try to confirm it might be the protocol?

If you ordered the new FLIRC there is a big drop down that says there is going to be a 10 day delay before the order ships. It's the tenth day today since first orders were placed, and I am literally just came back from the post. There wont be a ten day delay anymore. But the message is staying up in case weather conditions cause shipping delays from china if you want to know about your particular order, shoot me an email at support@flirc.tv

I want to apologize for the delay again. So here is a bit of back story. Flirc has been a side gig for 5 years and it's blown up in a good way. But managing the company, IP, development, orders, production, architecture, business model, marketing, customer support, etc, are all full time jobs themselves. However, I was a full time employee already at NVIDIA working on their GPU's for deep learning. Outside of that, I'm also a dad. It's been a journey, and I'm not making any excuses, but trying to describe why things have been a bit slow. About a month ago, I took the leap and left NVIDIA. It was absolutely a necessary step, especially being that this last month has been one of the most important defining months of the company. For the past year and a half, I've been working on the new flirc. The limitations with the original couldn't be overcome with any more tricks. It was time to start over. I've entered production and encountered a show stopping bug. Certain USB hubs weren't working, and after a bunch of all-nighters, we finally proved that it was the PLL in the device and not locking. Got a fix, and working on trying to figure out how to update the thousands in manufacturing. (The problem is the boot loader can't be updated). I've proven a couple ways to overcome this. The feature you're asking for is actually really trivial. But my time is needed ensuring a smooth launch, pretty much the entire company is riding on this. The new one is stunning, a work of art inside and out. It's built with stainless steel, and it packs a ton in it. Not only will I push an update to the one you guys have, but I'll send you the new one on the house to both of you as a thank you for not giving up on me. The site will be updated today. Once I push an update to manufacturing, I'll address this again. I pretty much have to figure this out by Sunday. Thanks again for being patient. And happy thanksgiving to you guys.

Ah, thanks yawor, my mistake. I changed it so I can open it in a hex editor. Forgot to change it back.

Working on a fix right now for you. Thanks for being patient.

@interr0bangr can you give the attached a shot? my_flirc_config2.bin

Are you guys in the US?

Did anyone try my suggestion of using the commandline application? @interr0bangr if you can send me your config, I can modify it if you are having trouble using my Commandline app. Let me know. Looks like we are almost there.

I believe I cover both in the commandlne utility: flirc_util record return & flirc_util record enter

This is great work and exactly what. Needed. Thank you. This is still on the map, but at the end of this month. Great job, and when I release my new product in the next two weeks, send me a message, you're getting on the house as a thank you. I can eventually help that one key, which is return. It could be joystick select or something. If anyone else figures it out, they'll get the same gratitude and thank you gift from me. Again, sorry I haven't been able to help with this. It will be evident why shortly.

Michiel - I thought you mentioned that firmware 3.1 fixed it? Was that not the case? I'm sorry, I can't see past black friday at this point. I will be working on the algorithm shortly after. I have some new code and simulations written so that I can write something to accomodate this remote as long as it's within the 38kHz.

It is. I will be looking into this shortly.

Try adding this to your /boot/cmdline.txt file: dwc_otg.speed=1 You'll need to reboot for that to work.

Does it upload? you don't need the ini to run the GUI. Does the GUI eventually launch? If not, try sudo Flirc.

Try the media center controller in my GUI, and record the 'sleep/suspend' button. This should also work to wake the pc.