Jump to content
Flirc Forums

Chris!

Administrators
  • Posts

    1,300
  • Joined

  • Last visited

  • Days Won

    50

Posts posted by Chris!

  1. "(Skip chapter forwards = "]" and back is "[")"

     

    For some reason it's vice versa. [ is forward, ] is back but not the chapter, just moves video playback +10 (or so) sec.

    Sorry I got it mixed up. But those are the shortcuts, see XBMC wiki:

    http://wiki.xbmc.org/index.php?title=Keyboard

    Perhaps you don't have chapters in your video file.

     

    And yesterday I've encountered another issue. My Flirc just stooped working all of a sudden. For no obvious reason. I had to reprogram it late at night. Restarted my RPi, and after a couple of minutes it did the very same thing, just stopped recognizing signals from my remote. Didn't bother to test it again. I'm kind of disappointed.

    Did you experience these issues on your windows computer too.

    I would say 9/10 times the issues with flirc and the raspberry pi can be attributed to the power supply not supplying the required amount of current.

  2. I'm getting more and more confused by this issue (not getting frustrated with you though).

     

    I'm intrigued to see if it works fine on Ouya (we'll see what koying finds). I can't understand why it wouldn't work on one android system the same as another.

     

    Would really appreciate other users input on this too. I'm sure we can get to the bottom of it.

  3. Hi doshch, welcome to the forums 

    The product is untested and that's a fact.

     

    I'm pretty certain this isn't the case. Jason tests every one he sends out - rarely they turn bad but we don't leave customers hanging if they do.

     

    The software and firmware sometimes has it's quirks and we do respond to customer feedback - Flirc is a small project that we work on (in addition to full time jobs) though so it takes a bit longer.

     

    Sometimes I have to assigned keys a few times in a row.

    Some remotes toggle between frequencies - obviously flirc will need to know what frequency/frequencies you want to do what. Remote control examples include MCE remotes.

     

    mute button

    Just checked this. Don't know why but it's mapped to "i"

    Incidentally I couldn't see a key for mute in the XBMC wiki, so it looks like we would remove the mute key.

     

    There isn't a chapter skip button but as you've figured out you can switch to keyboard view and do it there for the moment (Skip chapter forwards = "]" and back is "[") 

     

    But after all this you're up and running?

  4. There is definitely an issue with XBMC Android and the Escape, Backspace, and the shift key. They work in Android 4.1.1 in all apps except XBMC. There have been quite a few posts about this issue over at the XBMC forums but no solution that I've found.

    I know i'm not much help as I don't have an android device to test this on but I've been in contact with one of the Team-XBMC members that has used Flirc with Ouya (android based) and they didn't remember having any problems mapping those buttons.

     

    What XBMC android version are you using?

  5. Hi to all,

    I have MINIX Neo X5 that has IR receiver inside. So, I would like to use my tv remote to control MINIX without flirc receiver. Is it possible?

    Where I can download the apk file for android? I saw only Linux win and Os version.

    Thank you in advance

    Davide

    I think you're getting confused. Flirc is a hardware product - they software does nothing without the flirc hardware.

    Also Flirc programming utility isn't available on android.

  6. I'm still not sure about this issue. Unfortunately I don't have an android device I can plug my flirc into but it appears others haven't had the issues you've had.

    Perhaps this is device related.

    Which keymap did you put in the userdata folder?

  7. If I buy one, will it work with long keypresses so I can use the hold functions listed here? http://wiki.xbmc.org/index.php?title=Apple_remote

    Unfortunately not. Where long-press functionality is mentioned in the beta's it relates to the ability for flirc to be more responsive and detect when you're scrolling (not pressing the button multiple times).

     

    I saw your post of the XBMC forums an hopefully someone can help - I can't think of anything at the moment but if I do i'll get back to you

  8. Yes, that's what I've been doing.  Pairing and deleting in the GUI is not a problem for me up to a certain point. 

     

    Oddly, most buttons delete correctly in GUI mode and in the command line up to a certain point (maybe after I've programmed ~30 keys or so). After that, deleting several other buttons fail, even though it displays a successful deletion attempt ("Erased Button" on the GUI, "Button Deleted Successfully" in the command line). The only way to delete these entries is to wipe everything out. I can still add entries, but I can't delete them.  I'm running Flirc Version 1.0.5 [fw_v255.9-18-geb49aca]  Firmware Version: 256 04-01-2013, so I think I'm up to date with firmware and software. I'm going to do more tests to see if there are any issues (try another PC or something), but please let me know if you have any ideas.

    Wow, does seem like a bug. I don't recall it being reported before.

    Please report back after you do some more experimenting and i'm sure Jason will pick up on it at some point 

     

    Thanks

  9. Hi evilestegg, welcome to the forums

     

    Just to check, how are you deleting the button?

    In the GUI you delete the button by pressing delete in the GUI then the button on the remote control. This then deletes the pairing off the Flirc.

     

    Is this what you are doing?

  10. Oh no!

     

    Flirc is usually quite resilient but sometime things can get corrupted.

    In addition to you reverting to stable firmware could you try clearing your configuration (file --> clear configuration). Re-upload the firmware and see if that helps.

     

    I can see how it's frustrating, it's not acceptable for Flirc to be doing this - we'll get you up and running :)

  11. One system uses a Sony DVD remote, the other uses a Logitech Harmony (perhaps with a sony profile, don't remember).

    If the harmony remote is set as a sony remote then we have probably found the culprit.

     

    You could try the lastest beta firmware too to see if that helps.

     

    It's unlikely to be an XBMC issue 

  12. Hi selfdetruct, welcome to the forums,

     

    Switch to "fully keyboard" controller:

    9.jpg

     

    Then choose the button on your remote that you want to be the contextual menu button, map this to "c"

     

    Does this answer your question?

×
×
  • Create New...