Jump to content
Flirc Forums

Boldo

Members
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Boldo

  • Rank
    Curious Flirc-er
  1. Flirc doesn't pass on keypresses

    Well a small update; I can reproduce what you did via teamviewer perfectly and when rebooting it works flawlessly. But on a cold boot (at least 1 min off) it refuses to work. I really have no clue what this is anymore and it's hard to test for you via teamviewer... Any ideas to where to look next?
  2. Flirc doesn't pass on keypresses

    Well after it worked yesterday reboot after reboot, now after a cold boot this x-mass morning it's back to how it was before. Will look tomorrow, guess I'll use a keyboard again today...
  3. Flirc doesn't pass on keypresses

    Sure, have installed it for you. I'm at a total loss. What I didn't mention yet is deleting all past drivers versions for Flirc that were present within windows and now it only has the ones supplied with 3.5.2. Will msg you the teamviewer credentials.
  4. Flirc doesn't pass on keypresses

    A few developments but no solution yet: Followed this support article; https://support.flirc.tv/hc/en-us/articles/200712548-Using-the-ZADIG-Utility I can upgrade to libusbK 3.0.7.0 with the latest version but no difference. Finally my replacement Flirc came in, a new revision with black PCB and overly unnecessary blue led on the back, and exactly the same behaviour! So we can eliminate it comes from the Flirc itself, it should be driver related. Also ever since connecting the new Flirc, I get this error in the Device log; "Error, unsupported device. Must have Flirc Gen2 enabled device and fw >= 4.1.0" Can't seem to get rid of this 'error' now. With the black one it's the same story; first time connecting it worked, next reboot it still worked, but after that it's unplugging and plugging back in till it works which can take up to 15 min to do. Thinking about the maintenance I did after which this happened; it was only using some compressed air to clean the htpc (which I do with all my pc's every year), upgrade to windows 10 version 1709 and since I got problems upgraded to the latest Flirc + FW. Beginning to suspect it's the windows update causing all of this as this setup had been working perfectly since november 2015.
  5. Flirc doesn't pass on keypresses

    Well I've tried a few remotes which were laying around in the house with no result; same behaviour. The gui still sees the Flirc connected (device log) and it behaves like this; When Kodi doesn't receive keypresses; - On button learning it will say the button has been already mapped - When pressing buttons the keys won't lid up When Kodi receives the keypresses; - On button learning it will say that button has been already mapped - When pressing buttons the keys will lid up like it's supposed to be I'm really not sure what this could be; faulty firmware would cause the receiver not to work at all I'd imagine or more constant behaviour, both of which is not the case. And if the USB connection were bad it wouldn't be connected at all? It makes no sense whatsoever. I'm not familiar with the zadig tool, will look it up and report back.
  6. Flirc doesn't pass on keypresses

    The mystery deepens; I can get it to work by plugging and unplugging the husband header in many times...like every 20th time it will work. Now the mystery; it will keep working until I restart the htpc or shut it down after which I need to do the same routine to get it working. Any idea what this weird behaviour is?
  7. Flirc doesn't pass on keypresses

    Thanks for moving =) A different USB pin header doesn't solve the issue, unfortunately. To be certain tried it on my tv card server but also nothing.
  8. First want to tell excuse me if I'm in the wrong section but couldn't find a support section. Edit (I meant to post this in the general questions section, darn you browser tabs :P). For a few years I've really enjoyed using my Flirc SE and it's like the perfect companion to my htpc! Just love it. Unfortunately since yesterday since I did some maintenance to my htpc it stopped working, in an odd way. So what's so odd about it? well it still records remote ir signals when I point at it, and it still gets recognised. If a key on the remote was already learned it gives the proper message too so nothing appears to bewaring at first glance. Except in Kodi or in a text editor test you don't see keypresses anymore! (have it passing on letters/numbers) Since it's a SE version I thought maybe the USB cable had gone bad and replaced it, but no luck. Upgraded the firmware to the latest 3.9.0 but no luck either there. Is there anything I could do or test besides buying a new one? It's out of warranty for sure. BTW if you were to do a V2 for my streacom case I'd totally buy one!
×