jason

Okay, I got it. I'll have updated images to try very shortly.

damn, sounds like my permissions aren't working in debian? Try doing: sudo Flirc in the commandline, let me know if that helps.

May be that I'm not doing something as per the USB spec, I'm still trying a few things.

Upgrade to version 3.3 and then enable sequence modifiers. It's in advanced settings. This will fix it.

This was a problem fixed in fw v3.3 Or If this is a harmony remote, there is a built in profile. You can disable it in advanced settings in the GUI (built in profiles).

thanks Matt, happy new year.

I tried sending these keys with a new firmware image, and it's not working. Also not sure if browser back is in fact the 0x224 yet.

I'm working on a debug mode to help with this exact thing, but it seems like the tivo remote is just extremely slow. I'll try and pick one up if I can't finish my debug firmware.

Definitely upgrade to v3.3 firmware. That should fix it, much improved algorithm for noise rejection and false signals. You'll have to re-record buttons.

= )

if there is a keyboard combination that does this, it is possible, otherwise no one has figure out what that combination is yet. You can hook up a keyboard and try and figure it out and then I can create a shortcut in the firetv menu of the flirc gui.

Have we confirmed that it actually is the browser back button that is the missing key? Looks like Chris just threw it out there and no one really confirmed it. I'm willing to do it, in fact I'll try this right now, but would love a bit of reassurance.

Sorry, I'm trying to catch up. Can you upgrade to firmware version 3.3?

Nope. Doesn't matter. I should clarify somewhere. Your the second to ask uncouple days.

Yeah usb org needs to update my vendor name which will make its way to Linux. Make sure enable sleep detect is enabled in the GUI. Any key will then wake the machine. If you record the wake key, then only the wake key will wake the machine

when you are recording, record the same button twice in a row. You might be using a remote that alternates signals on each consecutive press.

So it seems like there are a few issues with the firetv. I don't have any problems with mine. Although I'm using plex. Let's work together. Plug a keyboard in your firetv, and let's see if we can figure out what the keyboard keys are for the desired functions. I'll get the GUI updated as soon as possible once we've identified the correct keyboard keys. I'm booked until saturday, then I'm back on flirc.

can you snap a picture of your fios remote for me? Also, just shoot me an email at my support address and I'll give you a new firmware image. I need a remote like this and I can update the firmware.

I'm using schroot. I like the fact that it shares the home directory, and haven't figured out how to do that with just chroot.

the configuration stays on the device. You save the configuration with: flirc_util saveconfig <filename> It won't automatically load. You have to: flirc_util loadconfig <filename> Let me know if that answers your question.

Yes, absolutely, point it at the ceiling. Flirc is very sensitive.

Why the unhappy face? Chris! is actually helping with documentation. Day job is killing me this week. I have time off after this week where I will pick up the pace again. I don't think the GUI is missing anything the commandline has anymore other than these; ability to delete indexes (will get to this) Record API (don't inticipate on putting that in, this was probably what you are referring too. Wayyyy to complicated.)

Oh, you can definitely wake up your machine. Make sure 'sleep detect' is enabled in the advanced settings of the GUI. Power on is the feature that's still in progress. ** EDIT ** Also, make sure you are on v3.3 of the firmware. If not, you must have the 'wake' key recorded which can be found on the keyboard controller view. On firmware version 2.x, you have to enabled sleep detect, and record the wake key. Only that new key will wake up the machine. On firmware version 3.3+, you have to have sleep detect enabled. If sleep detect is enabled, any key will wake the machine, but if the wake key is recorded, only the wake key will wake the machine.

I'm using mint, and based on debian. I can't stand what ubuntu is doing to linux. They aren't helping anymore. Looks like you're right. I'm having trouble getting a system up and running. I don't want to manage multiple virtual machines or a machine with 100 distributions on it. So I'm using chroot on one system and it's working out nicely. But I'm going absolutely nuts because 12.04 isn't installing and everything I read is pointing to EOL. I'll just need some time to figure out why it's not working.

Poweron doesn't work yet. I'll need a software update. I keep wanting to get to it, but my day job is killing me. Taking next week off so I'll address it this weekend. Very sorry for the inconvenience, it should only take me a few hours.