jason

did you try the media center keys in the media controller view of the GUI?

it's basically a dumb fliter that expects the signal to be there multiple times before sending to the receiver. Helps prevent a false positive. I'm going to make it a bit smarter, but it does the job.

My pleasure, I poor my heart into this project, so it means a lot for the kind feedback. Yeah, I'll talk further with you about that, but I did post a new firmware image. Give it a shot, I'm pretty confident in it, but no one has tried it. Thanks so much, I really appreciate it.

Okay, I think I figured it out: Please grab the latest beta firmware, and give this a shot: It actually has a much more natural feel and seems to detect presses from holds much better now. I would also encourage you to format your configurations and relearn your keys. The reason is because the default settings after you format will likely cause people a lot less headache. They are much more generic, you probably don't need sleep detection, sequence modifiers, and anything other than an interkey delay of 3. Let me know.

I think I have an idea, I will post an image to try shortly.

What country are you in Joe? This is some really good work and I'm going to read it a few times to fully understand your suggestion. Can you also find me on skype or gchat? Both my names are jasonkotzin thanks so much Joe.

Are you seeing a few rapid key presses, or does the key feel like it's being stuck held down?

So yours is working?

I'm sure we can resurrect it. Traveling back home. I'll see what I can do when I return.

ah, interesting, and you're on 3.1?

Interkey delay is too small, need to crank it up to 3.

Interkey delay should be at 3.

The way it works now, if you don't have a sleep button mapped, but still have sleep detection enabled, any key will wake the machine up. Give that a try and let me know.

Absolutely can, but before you do, try upgrading to 3.1. File->advanced, force firmware upgrade. Then try again. If it's still the same, it's probably a really noisy source close by. Try turning off the lights or the TV, once they are recorded, it should work fine.

CHRIS!! I needed two exclamations because your user name has one.

Any interest in helping do documentation for compensation? :)

I really appreciate the feedback. Thank you so much. I'll do better with the documentation, but I really have to say in defense, it's not quite as awful of a picture as you're painting. It really makes me sound like a total failure and the product should never be recommended again. The advanced settings are very poorly documented, you're absolutely right. But they were never really intended for use and have been added to compensate for very small variations that don't fit the norm. That's not an excuse, it's my fault, and I'll fix it. record_api is a super advanced feature, and it's just going to go beyond someone who isn't comfortable reading the IEEE USB HID spec.I have no intentions of documenting that anymore than the help section of flirc_util: usage: record_api 'arg1 arg2' arg1 is key-modifier arg2 is HID key example: flirc record_api 136 4 '136' represents right cmd + left cmd '4' represents 'a' in HID Key modifiers are defined in the IEEE HID Spec as follows: LEFT CONTROL 1 LEFT SHIFT 2 LEFT ALT 4 LEFT CMD|WIN 8 RIGHT CONTROL 16 RIGHT SHIFT 32 RIGHT ALT 64 RIGHT CMD|WIN 128 For starters to help, I've put together a series of help articles here: https://flirc.zendesk.com At every opportunity I have, I add an article. Most people just got to the forums or email me, because it's easier than searching. That's not something I can do much about. If you hover over the advanced settings in the GUI, you get a tooltip describing what it is and what it does. Ideally, I'll have some help contents right in the GUI, and it's just a matter of time before it makes it on my list of priorities. I've got a new product launching this Friday, and I'm terribly excited about it: https://twitter.com/flirc/status/535914395650383872 But thank you for the criticism, it's not unfounded.

raise the interkey delay in the Flirc GUI under advanced.

I've been following this thread religiously and there are two problems that can happen and the multiple people posting are either experiencing one or the other. Flirc is essentially a keyboard, so consider Problem 1) When you hit a key on the remote, one key is received on your machine, there is a delay, and then several keys are seen. Like if you had a keyboard and just pressed and held the button down. 2) When you hit a key, several keys are received rapidly. These are two very different problems and users aren't distinguishing them here, and rightfully so, as the problem statement is too many keys are received. So let's talk about the solutions we've figured out. 1a) If you have a harmony remote, lower the repeat value in the harmony software: in the remote, go to the troubleshooter and lower the value to 0 or 1 1b) if you don't, lower the interkey_delay in the flirc advanced software. 2a) raise the interkey_delay in the flirc advanced software I think there is one more cause for 2, but I haven't determined what it is yet, I'm still working on it. It's going to require some special firmware that I started on. I'll put a sticky at the top of this thread for others, this seems to be the solution. [edit by Chris: A separate sticky has been made to make the issue easier to find for those who may be experiencing it. Continue to discus it here though]

No, I re-architechted the firmware to set it up to be easier, which was in the 3.x firmware. That also included much better support for other remote controls that always gave flirc problems. I quietly released a second product: http://www.streacom.com/news-item/introducing-flirc-se/ That's going to ramp up soon. I have a third product that I pre-announced (teased): https://twitter.com/flirc/status/535914395650383872 That's going to be released this coming Friday. I need to try and get the website ready for the new product. I also need to work on another version of firmware that captures the waveform from the remote so not only can I examine what others are seeing, I can reproduce it at home. After that version of firmware, I'll continue on that feature. I assure you, it's not intuitive to make intuitive. The work I did already for 3.x was an enormous under the hood change. Thanks for the patience. I'm sorry, I hadn't realized how tough this was going to be when I estimated and signed up for it. But it's on my list.

Open up the Flirc GUI, then go to the full keyboard, then pair your remote with the ones Rob has put above. For example, if you know which button you want as the home button, pair that button with escape. It looks like you also need to add the file Rob posted above and put it on your android in: /system/usr/keylayout/ I'm willing to bet that you need then go on your android, system keyboard preferences and select one called Vendor_20a0_Product_0001. But this is all a guess, I don't have an android TV. I'll try and put in better support in the flirc gui so you don't need to use the keyboard controller view.

I'm going to be tied up on planes for 10 hours. Shoot me an email at the support email address and I'll send you the old firmware while I try to figure out what to do next.

My pleasure. Well at the very least I can get you back on the previous version. I'm certain it's something particular with the protocol. I just need to sit down and look at it. Go to advanced and do a force firmware upgrade. What is the bootloader. Also make sure your not point the remote to close to Flirc. Point it up at the ceiling and see if that helps.

Well get it fixed. Hang in there I'm traveling. What kind of remote do you have?

are you on the very latest that's available on the website?