jason
-
Posts
3,758 -
Joined
-
Last visited
-
Days Won
233
Posts posted by jason
-
-
figured it out, try this link and let me know: v1.3.0-rc.1
-
I can repro, let me see if I can figure it out.
-
Maybe I shouldnt have been so quick to order a new one then????
Don't worry, I'll make you whole in either case, are you in the US?
-
going to loose it. It's going to take me a bit of time, but I think what it comes down to is something with the IR sensor. Has to be. It's causing the firmware to think the key is held down or pressed repeatedly.
So what I'm going to do is bring in some custom functionality into the firmware. I'm going to add the ability to capture the waveform as seen from flirc represented as timing information. I'll let you guys export that to me, in which case I'll feed that into some software to visually draw the signal, as well as another device that outputs that as IR to a flirc here to reproduce exactly what you're flirc is seeing.
This will also help me from buying 1000 remotes (which I've done).
But this is going to take a bit of time. I'm coming out with a new product this week and am sacked with the launch. This is a pretty decent effort, but I should have some really good time next week. Hang in there, if you guys are miserable, I can try sending you a replacement or issue a refund.
-
I'm pretty surprised that you have to point it at flirc. Flirc is pretty sensitive. What about if you upgraded to fw 3.1 if you haven't already. My algorithm is a little slicker
-
are you in the US?
-
did you recently update xbmc or openelec? If you open up a text editor, is it doing it in the text editor?
-
Yeah, this is definitely bothering me. I'm not sure what's going on. Another user reported he got his sell phone and having his cell phone in the room caused this.
I'm actively trying to determine a way to reproduce this 24/7. Please hang in there, I wont leave you hanging nor will I let anyone else.I think I need some special diagnostic firmware to tell me about the IR signal coming through.
Did you recently get any new Wifi radios, cell phone, anything attached to the wall sockets that are new that would cause noise?
-
In your harmony software. Hit your remote and then troubleshoot and then there should be an option that says too many keys are relieved. Change the number it presents to zero.
-
to clarify, when it's in this broken state, you erase, press the button, and it does not erase. Let me take a look at the config.
-
Can you post your configuration?
-
hmmm, maybe give this a shot:
I guess my rpm isn't working? I'll have to try. The release candidate is the same as the release version. You can use that for now.
-
No, mac's don't support that unfortunately. But it does wake from suspend and put to sleep.
-
I've just sent it to your support email. And yes definitely I've been tail'ing the xbmc.log (with xbmc's debug logging enabled of course) to get the keypresses it is seeing.
how about dmesg?
-
Sequence Modifiers is indeed disabled for me.
can you upload your config. I'll see about putting together some debug firmware for you to try. Doogie, can you ssh into the box once this happens and run some commands?
-
one more, if you fire up advanced, can you guys tell me if seq. modfiiers is enabled.
If it is enabled, can you disable it? -
maxwell, maybe you can ping me on skype. I'll get this sorted out.
-
okay, I read through this entire thread again. I'm really confused.
Can each of you experiencing the problem please describe exactly what is going wrong. Like for example, when you press a key, the key get's 'stuck', and the only remedy is to take it out. Or the only remedy is to press another key, but that key gets stuck. I'm very concerned that people are talking about different things. For example, there are a bunch of threads where people say, flirc loses it's settings. That didn't tell me much, what was actually happening was that the device was getting stuck in the bootloader, so remote control buttons didn't work until you fired up the gui (which gets the device out of the bootloader). So the more you give me, the better of a chance I'll catch what's going on.
Swear I'll get this problem. It's got my full attention now. -
wait, Maxwell, are the keys getting stuck indefinitely until you have to unplug the remote. Or is it just a bit sticky and you get multiple key presses when you hit a key?
-
By the way, you don't have to unplug it, you usually just have to close the GUI. That's a windows thing.
-
Remotes: Pioneer AXD 7247 (AV receiver), LG MKJ42519618 (TV), Speedlink SL-6399 (MCE spin off, black one), Hama MCE Remote (silver)
Makes no difference which ones I use. Best help at the moment (for me) really is switching USB ports. When it works, it is a great little thing. :-D
any chance you are using linux?
-
okay, can you guys also tell me what kind of remotes you are using? Any chance you have another remote control you can try to see if it is any different?
-
Jason - yeah, now that I read my post again, I was pretty unclear - I upgraded the FW in response to the problem starting to occur. v3.1 does not seem to make a difference.
did you upgrade from 3.0? or 2.x?
-
This is SO STRANGE because things have just worked up until a few weeks ago, unchanged, nothing touched. So much so that I thought, oh right, the remote's batteries must be dead. If there is any debugging info I can provide I am more than happy to, my setup:
OpenELEC 4.2.1 x86_64
Flirc 3.1 (was running on 1.0 prior)
Logitech Harmony 650
US, grounded outlets, brand new electrical actually
Remedies: moving the flirc to another USB port sometimes works, waiting sometimes works..short lived either way sadly.
Flirc is velcroed to the bottom of the TV chassis and a USB extension cable runs to the PC.
I have 3 PC's throughout the house with this setup and all 3 started having the issue at the same time.
edit=added more details
Did they all happen after a fw upgrade?
Using Flirc wirelessly? Connect it to a router?
in General Questions
Posted
there must be something else going on. Try another remote profile.
I have my mine behind my television which is up against a wall and it still gets the signals. It's line of sight, but the sensitivity is crazy good. Also make sure you don't have noise canceler enabled in advanced settings. That wants two keys before sending the key, so maybe that's it.