jason

http://forum.flirc.tv/index.php?/forum/73-firmware-30/

it's covered in this great tutorial:

keep the interkey delay at 3. What remote control are you using, I'll take a look. i do have some improvements I will push soon.

I'll try and build a 64 bit version later tonight, what distro are you using?

Try the latest beta release.

shoot me an email at support at flirc.tv, thanks yawor for letting me know about this thread.

what do you mean it's not repeating commands? It's not forwarding button pressses or it's not detecting when you hold the button down?

Yes, please make sure you're on the 3.0 firmware version, and you clear your configuration and start over. After that, please let me know.

Hey Summers, I appreciate the analysis and detailed information. Really helps. I would love to be able to replicate this, I have my scope so I would be able to see it. There was an account of another user posting some information on not having his media equipment on an earth ground, which caused strange misbehavior. This is definitely pointing to a noise issue, however, I'm not sure what the potential fix would be. There are three issues and causes. Raspberry pi problems with power supplies. - Shitty power supplies are causing flirc to get stuck in the bootloader requiring them to be taken to a computer and fixed with the gui. Bootloaders have been updated with a workaround in later versions of the device. Light problems. There are several accounts that lights are causing indefinite key strokes, repeating and noise problems. I've released an updated firmware version to address this: EMI interference (could be related to what you've described). When I have my laptop power chord by my flirc, I see this issue. False triggers and indefinite key presses. The firmware image released above should help with this too. This problem described by you. I can't add any more filtering, any more capacitance on my device and the raspberry pi will actually reboot because I triggered an inrush current limiter. This is going to require investigation and take time. Not sure how I reproduce this Thanks so much for the information, this should help and I'll meet with my buddy to go over possible ways of reproducing this.

Check the beta thread I have the third version of the release candidate up. Please please let me know if it helps solve this.

might be a faulty unit, could you send me an email at support @Flirc.tv, I'll take care of it.

I will, I'm just a one man show, I'll put something together in the next release hopefully.

crazy, do you have a pic or a diagram of the setup? so a ground was added to the computer?

okay, got a release candidate, give that a shot:

Okay guys, 2:30 AM here, I'm sorry, couldn't finish it tonight. I'm close. Just a heads up this will be beta, and there will be a few features missing. I completely re-wrote nearly all the firmware. It's going to go up tomorrow...err. today... after sleep.

Hang in there, I'm going to post a beta image tomorrow that will add support for all the remotes that gave flirc problems. Here is the forum to keep your eye on:

Okay. Starting to take form. I've rewritten my firmware and I have a new adaptive algorithm that's going to help with noise suppression and all rc6 remotes will now work. I have two more items that need attention for the fw, and then I'll start working on putting together beta packages.

I think that message is a fluke.

Can you do file->advanced force upgrade in linux?

That's not a valid keyboard combination. For example, this wont be distinguished by the operating system with this unique press, rather alt+space or Alt+n = (

try sudo for both the commandline and the GUI

Several improvements to firmware are in the works. They should hopefully be posted this weekend. Hang in there. The linux version can't be lacking, it's the same source code that gets compiled for everything. Can you show me a screenshot, maybe there is something else going on? Do a file->clear configuration. Start over and make sure you use a samsung or panasonic profile on your universal remote. The firmware updated will solve all the issues for any other remote protocol, but those are the ones I'm 100% confident in with the firmware release you have now. Let me know, I want to turn your experience around.

can you do a dmesg at the beginning of this test and at the end? Maybe that give us some clues as to what linux is seeing.

okay, made some great progress. I'll need a few more days to clean this up before the release. Thanks for the patience guys.

hang in there guys, I've been working around the clock, I've got improved algorithms in the works, I'm polishing it off