jason

no, but what's your intention?

Oof, my bad. I released it. I never followed up here. Grab my latest version and then do a flirc_util record toggle

yes, that's exactly how flirc-se works. Also, if you have a regular flirc, record the 'wake' key, and it'll only wake the computer with that paired key. It's on the keyboard controller next to F12

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.

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.

Once paired with a remote you don’t need to have the GUI running nor should it. It may even cause issues.

I’m done. But I’ll need till next week to actually post it.

Awesome, glad it’s up and running the way you like

Awesome, glad it’s up and running the way you like

I'll need a week, and I'll post something you can try out.

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’.

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.

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.

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.

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)?