jason
-
Posts
3,751 -
Joined
-
Last visited
-
Days Won
230
Posts posted by jason
-
-
Really sorry for the GUI bug in the release, but it's safe to say this bug is gone and done. Thank you everyone for your constant support, patience, and help solving this. As most of you know, I have a few friends that help, but I'm primarily a one man show doing this all on the side of a demanding full time job and recent father. So to say the least, the community and constant warm feedback makes all the sleepless night and hard work worth it. Thank you so much everyone.
-
The Flirc GUI, if you fire it up after the flirc stops working. What happens? Does it detect flirc, does it upgrade the flirc automatically?
-
Hi Jason
As in, I plugged it in and the exact same repeat issues are happening.. However, I just read in your other forum post that you have RC firmware.. I havent tried that.. So I will try that today an report back..
I think it fixes it, let me know on the release candidate forum if it doesn't resolve it.
-
Hi CHris
Has this been resolved? I just received my new FLIRC and it is acting the same way.... :(
can you describe what you mean?
-
It works here, Jason, keys are no longer stuck in endless repeats. Once in a while it ignores/skips a keypress, but maybe that has to do with the interkey delay. I will play around with that setting later. I was asked to install the firmware multiple times too, and also got a message saying something about (i quote from memory) unrecognized firmware. Still, it works, thanks!
Yeah, most likely going to be fixed with changing the interkey delay. But I believe this is only if you are rapid firing keys, is that right?
-
I can't post firmware images, and downgrading is a bit tricky. I think I fixed this, can you try the beta firmware image:
Want to give that a shot and let me know?
-
Thanks so much for your efforts. I'm testing it out tonight! Will report back.
Any luck? I'm 100% positive this fixed it. I was able to reproduce it, I've seen this before but very seldomly.
-
can you make sure you are on the latest firmware? Should say 3.1. If not, File->Advanced, force firmware upgrade.
Let me know.
Very Sincerely,
Jason
-
Anyone else have feedback? I'm fairly happy with the change on my end and will make this public soon as it also fixes another long standing bug deleting keys.
-
That doesn't sound quite right. When it stops working, can you fire up the GUI? What happens, does the GUI detect flirc, does it upgrade the firmware automatically? Let me know, I'll get it sorted out.
-
That shouldn't be the case, can you give the beta a try, I compile it differently;
-
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.
-
Jason,
I'm in the U.S. near Chicago. I'm glad my work was helpful. It's refreshing to see that you are as attentive as you are on these forums. It's quite rare to be able to actually talk with somebody that developed a product I bought on Amazon. I see you posted an experimental version in the "Keys Stuck" thread. Is that my suggestion? I'd like to try it out if so. I'm at work now right now , so I'll try and find you on skype later tonight.
Joe
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.
-
Hi, I registered here to join the club. The problem didn't appear out of the blue on my chromebox running Openelec. It had been there from time to time since I bought my flirc a few months ago, but it always disappeared again. Then, a few weeks ago, suddenly the sticking keys were there almost constantly, and the problem just wouldn't go away. I hadn't upgraded the firmware or anything. I had made no changes that could provoke it, I think. I've read all the threads on this, and I have spent hours trying to find a logic befind the problem and fix it. So, now my flirc goes back into the drawer, it's useless, sadly. I'm quite disappointed with this, I must say. Like the others here, I really wanted it to work.
Are you seeing a few rapid key presses, or does the key feel like it's being stuck held down?
-
Jason,
The FLIRC that was on 2.3 started acting wierd then said "Boot Loader detected, can not update firmware, contact support" (wording may not be exact) I took it over to another machine and now the firmware is v3.0. I grabbed the 3.1 FLIRC and erased and reprogrammed it using an old Firefly Mini that I have and it's working again.
Dude, gremlins! I want to help you solve the problem because I really like the concept and they worked for me for six weeks flawlessly. If you want we can take this PM.
Chris
So yours is working?
-
I'm sure we can resurrect it. Traveling back home. I'll see what I can do when I return.
-
I tried 3 with no change in behavior, I changed it to 6 and no change. I reseated the FLIRC and the remote went completely dead. I brought up the learning software and tried pressing keys, nothing on the on screen keyboard lit up. I tried programming a key and it came back with Key already exists. I tried erasing the configuration and reloading it, the remote still acted dead. I tried a different remote, no change, both are Hauppauge 45 RC6 remotes. I then pulled it out and watched a show :) using an old remote and usb reciever I had. I plugged it back in and the remote was working again like it was before, keys getting stuck. I went back and read almost the entire thread here and found the entry about sequnce modifiers, I unchecked it and left the Interkey delay at 6 and everything seems to be working normally. I went back and checked the Interkey delay and set it back to 3 and noted that the sequence modifer was checked again, I unchecked it and looked again. Sequence modifiers was checked again. I left it alone and tested the remote, everything appears to be working properly.
Hope this helps in isolating the issue. If there is anything else I can do, please let me know. I will keep you aprised of any changes in the behaviour.
ah, interesting, and you're on 3.1?
-
Same problem also here with same setup. Interkey 0 and noise cancelling helped a bit, but often when pressing up und down the command is issued twice.
Latest FW 3.1 running with Fire TV profile.
Interkey delay is too small, need to crank it up to 3.
-
My FLIEC with the 2.3 firmware is doing it now too. It started after a reboot of the machine
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.
Keys stuck
in Firmware Bugs
Posted
publishing the release now.