Jump to content
Flirc Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by henrythemouse

  1. Well, I can't explain it, but the problems have disappeared. I'm now using an old VCR remote, and since I started using that everything is working fine. Now it looks like it was just remote problems, although that's really hard to beleive with all the weird stuff that was going on. Anyway I'm thirlled! I've got control again ;-). Thanks for your help.
  2. Well, I don't sit next to the receiver, I settle for less than 100% response. Sometimes I'll need to press a button 5 times before I get a response, sometimes not. I upgraded the firmware to version 1.0 a while back, do you consider that the latest stable release?
  3. Well, it's not a total loss after all. I kept playing around with recording the keys and finally got it to work. I hate to say what I did because I can't see how it could have had any affect at all. I layed a cloth over the flirc. When I did that the automatic cycling of the keys stopped and I was able to press a remote key and have it recorded. Maybe I just got lucky. Anyway, it's back to having to hold the remote really close to get 100% response from XBMC. Better than nothing.
  4. I tried that can got this on both machines: me@host:~$ lsmod | grep usb usbhid 41116 0 hid 83856 1 usbhid me@host:~$ lsmod | grep hid usbhid 41116 0 hid 83856 1 usbhid Then I decided to run a few more tests. On my laptop I started to notice that I was getting more missed button presses. As it turns out the flirc was acting like it was sensitive to the closeness of the remote. I realized that in my previous tests I had been holding the remote right next to the flirc. So I plugged the flirc into my server and held the remote less than an inch from the flirc. Tha
  5. The obvious thing to do, can't imagine why I didn't think of it. The easiest of the two was to stick the flirc into my laptop and give XBMC a try there. The remote worked fine 99% of the time. Just once there was a hang where XBMC didn't respond to the buttons for about 10 seconds (I was doing some fast button clicking, putting the remote to the test). I'd have to say from this test that the issue must lie with my server. I'm not sure where to go with that, however. Do you have any ideas? By the way dmesg is quite a bit different for the flirc on my laptop which is running the same OS (a de
  6. I'm using an old remote from a previous dvd player to control XBMC. It had been working very well, but recently has become almost useless. I bought a new battery for it, but that didn't help. In order to get XBMC to respond to a button push I press the button continuously, from 5 to 10 times. If I don't get a response from that sometimes I can just wait a few seconds and XBMC will respond. I guess this could be a system issue, but the fact that it was working well less than a month ago has me thinking that it might be an issue with Flirc. I'm using Flirc on an Dual Core Ubuntu 10.4 serve
  7. I don't see anything there that I could use, but something else occurred to me while I was looking at it. Maybe I could just cover the flirc with something that would block the signal. I tried a cloth, that didn't work. Any ideas as to what might block that signal?
  8. Possible, but not optimal as this computer is also a web server which I'd just as soon have awake. Thanks for the suggestion, I hadn't thought of this possibility.
  9. I'm wanting to use my DVD remote to control XBMC. It takes the flirc programming correctly and will work flawlessly. The problem is that when I want to use it for the DVD player flirc is also getting the signals and XBMC is acting on those commands. I want to be able to switch between the two devices but can't think of a way to do that. I can turn off the DVD player so it doesn't get signals while I'm using XBMC, but I can't turn off XBMC while I'm using the DVD player (XBMC standalone runs on an always on computer). I can unplug flirc from the XBMC computer, but I'd rather not as I like to
  • Create New...