Jump to content
Flirc Forums

jason

Administrators
  • Posts

    2,734
  • Joined

  • Last visited

  • Days Won

    117

Everything posted by jason

  1. http://flirc.io/config/ But you can't really figure out what remote button belongs to each hash... That's as good as I have at the moment. Let me know if it's of any help.
  2. Stored on the device, so you can bring it to a friends computer, or this new computer, and it will work with your previously paired remote with no pairing or additional software needed.
  3. Once paired with a remote you don’t need to have the GUI running nor should it. It may even cause issues.
  4. I’m done. But I’ll need till next week to actually post it.
  5. Awesome, glad it’s up and running the way you like
  6. Awesome, glad it’s up and running the way you like
  7. I'll need a week, and I'll post something you can try out.
  8. Depends on your harmony. You have to see what happens in the ‘activity’ you created. If you said it to turn on your TV, make sure it was on the same input, and then ‘wake’ up your android, it might arbitrarily be sending the home key to get it to wake. You can change that to ‘back’.
  9. I can do this now. Let me know how you'd like this to work. Here are some of my thoughts: We can have an enable/disable or a toggle button? My initial hesitation with implementing this was that there is no visual feedback if the device is enabled or disabled. I see many pissed off spouses. This is going to make functionality frustrating. See below: From a practicality point of view, it would be easier to separate these. Meaning if we had an enable/disable button, then we would be able to know for certain which state flirc is in. If a user is insistent on keeping this in a single button, they could long press into an enable or disable. If they are separated, you need more buttons on your remote, unless you long press, but this has drawbacks. I see many people not being certain if it's enabled or disabled, so they press down harder and longer on their remote. If we do have a toggle, I need to block all buttons from being received for 3 seconds. Otherwise, the state can toggle back and forth. I'm really inclined to have an enable and disable button. And I'll probably hide these in the cli, I 'm going to have a customer support nightmare if this doesn't remain an advanced feature.
  10. Under Controllers->Media Keys, there are keys to sleep the machine as well as keys to do system wide media player keys (app doesn't have to be in focus). Let me know if there is something else missing from the windows media center key shortcut list.
  11. I read your PM, and what it sounds like is the following: You have flirc programmed, and installed in the pi. You go to your other PC, and ssh into it. When you press on your remote control buttons, they don't show up in your SSH remote session, is that right? If so, that's actually expected. The SSH session is a virtual console into the machine. Your mouse and keyboard are plugged into the machine, and on another 'virtual console'. Actually the display manager. Whatever is showing up on the HDMI interface, is assigned to this same virtual console (display manager 0). You wont see keystrokes unless you are looking at the monitor.
  12. Basically we only see the button when you press it, and nothing indicating you are still holding it down. Were you holding it down when you captured it? Is the verizon remote a universal remote too (Does it control other devices)?
  13. Can you go to File->Device log. Enable logging. Press and hold one of the buttons, and paste / share the output here.
  14. The harmony had no lag with the nexus? The harmony remotes have tremendous lag, I've talked with them about it, it's built in on purpose. There shouldn't be any lag with flirc.
  15. I can't figure out how they are doing their long press. I've lost all contacts at amazon because of their turnover. One day, I'll need to sit down and test a bunch of keys. Theoretically, it's possible. But we need to figure out what HID key they expect.
  16. Download my software. Plug in your flirc and go to Controllers-->"Nvidia Shield" http://cl.flirc.io/35e1393420d2 Hit go and pair your IR Remote. Take out Flirc, and plug it into your shield. Should work with your previously paired remote on your shield with no pairing software needed on the shield
  17. Pair on your PC, then bring it over to your shield, it'll work with your previously paired remote without any additional software
  18. Can you install the kodi keymapper addon, you'll be able to tell what key is for the play/pause.
  19. can you hook up a keyboard, figure out which keys are the play/pause buttons?
  20. What remote are you using? Have you ever used my software before?
  21. There is no reason it would crash. Kodi crashes? Or the Operating system? Try the play / pause from the media key controller: http://cl.flirc.io/73d2eeb9f8d0
  22. Hang in there, fixed a bunch of build issues, and am going to address this. I'll really try to have it pushed tomorrow.
  23. I'll fix this. Hang in there.
×
×
  • Create New...