Jump to content
Flirc Forums

jason

Administrators
  • Posts

    4,008
  • Joined

  • Last visited

  • Days Won

    256

Posts posted by jason

  1. I haven't made any changes to the hardware, but the bootloader is indeed different. A lot of people are experiencing problems with repeaters and small cabinets where the flirc registers a bunch of signal bounces. 

    While your firmware upgrades probably went okay and succeeded, there are chances of corruption still. Chances are small, but it's not worth ruling out. Feel free to shoot me an email, I'm more than happy to see if a new one helps. Just let me know.

  2. Nope, that's the minimalist view. Check out the rest of the controllers in the file menu.

     

    You are essentially mapping keyboard keys. That GUI you used is just the essentials. I present a full keyboard, and pre-mapped shortcuts for favorite apps in the controllers.

     

    XBMC, Keyboard, Media Center, WMC, etc

  3. Update:  Last night, I decided to take my universal remote out of the loop.  I dug out my old Xbox remote, but had the same problems.  I even opened up a second flirc with the same result.  I then decided to try my Roku remote.  Everything seemed to work with the Roku remote and my universal remote mimicking the Roku remote.  It appears that flirc has some incompatibilities with certain IR protocols.  flirc could not tell the difference between some of the Xbox directional buttons.  The Xbox uses the RCA protocol while the Roku uses the NEC1 protocol.  I also had problem with the MCE protocol.

     

    Update 2:  A little search of the forums confirms that both the Xbox and MCE remotes do not play nice with flirc.  No worries, I can tell my JP1 remote to mimic a different remote entirely.  I am off to search for a well supported remote/protocol.

     

    -Tom

    Yes, you found out before I was able to get back to you. They use non-standard frequencies and it messes with flirc a bit. I have it on my todo to fix this. 

    Try samsung or panasonic profiles. Those work great.

  4. I mentioned this in a few places, but don't like to because it doesn't excuse much, but it's just me here. I do everything, support, development, sales, packaging, testing, assembly, you name it. It's literally enough jobs for 2 people full time, and I do it outside a full time job. I may miss an occasional post, which I did, and I really apologize. One way to get a hold of me is by going to that contact support site, it goes directly to my email and is managed by zendesk so I don't lose track.

     

    That's a problem that is due to a bad driver. Give this a try: https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility

     

    I apologize I missed your post.

  5. So pictures are more important than a buggy Flirc () ... I think i should post that on Amazon ... -.-

    I mentioned this in a few places, but don't like to because it doesn't excuse much, but it's just me here. I do everything, support, development, sales, packaging, testing, assembly, you name it. It's literally enough jobs for 2 people full time, and I do it outside a full time job. I may miss an occasional post, which I did, and I really apologize. One way to get a hold of me is by going to that contact support site, it goes directly to my email and is managed by zendesk so I don't lose track. I'll respond about what your specific problem is in your thread.

  6. I added a second 2 foot USB extension  cable and ran my flirc out the back of my cabinet and it is now perched atop my center channel speaker.  It's been chilling out up there  for a week now and i haven't had a single issue of multiple key presses!  I'd prefer to have it inside behind the glass, but i don't have any spare material to use as a filter.

    Any chance I could you post a picture of your cabinet?

  7. Try this:

     

    https://flirc.zendesk.com/hc/en-us/articles/200712548-Using-the-ZADIG-Utility

     

    ** EDIT ** 

     

    you have an old driver, the installer doesn't do a good job of replacing the old driver, and I don't know why. Following the instructions, you'll force the update of the driver, and everything should be good. The -16.-16 is because that request to the device doesn't work because the old winusb driver is restricting commands.

  8. It's not too bad. Here is what I would recommend to help out. Use an sftp application, on the mac, it's transmit/cyber duck. There are plenty for windows.

     

    What this will do for you, is look like an FTP browser but connect over SSH. You'll want to connect to your raspberry pi on port 22. Use the default raspberry pi login and password for your distribution. root/openelec

     

    Then, browse to the location of the xml file. Looks like it's here: /storage/.xbmc/userdata/

    (found on this website: http://wiki.xbmc.org/?title=HOW-TO:Modify_keyboard.xml)

     

    Then, with that application, you could double click it, and open with a text editor, or drag it to your computer, edit it, and then send it back.

     

    That should make things easier. Let me know.

×
×
  • Create New...