jason

Sorry we are all tirelessly working. Final samples arrive soon for approval, and I'll have dates locked in as soon as I give my thumbs up. We will start to share regular updates. Promise

I think it's your language settings on your keyboard. I'm assuming standard US english qwerty. It sends those commands, and if you have a different language, they will remap on the host.

https://getchannels.com and https://www.silicondust.com are an amazing pair. Silicon dust sits on the network and turns any firetv/android/appltv and the channels app into an amazing DVR. Even works outside of the house.

Can you do flirc_util.exe settings 172 is probably meaningless. Do you have HID manager on the firetv to get the key from flirc and the remote?

flirc_util record_api 0x2 0x8D Try that

Yeah, the commandline should be able to do this. Trying to figure out why it's not working for you.

What was the problem you have and what version did you want to try?

I don't understand the question. I don't post older version of the firmware, they are embedded inside the GUI. There is no maximum age limit, any device can load any firmware. If someone needs to try an older version. The older version of hardware is really old. It's like 10 years old. I've done some minor updates. The firmware isn't compatible, the processor in the new model is infinitely better.

What does flirc_util.exe version give you?

Okay, here is how to figure it out. Check out the Desktop Consumer Usage table Here: https://www.usb.org/sites/default/files/documents/hut1_12v2.pdf Find Table 17 Now, as an example, in this table, AC_BACK is used to go back. To record this manually using the commandline, do the following: flirc_util record_api 0x2 0x223 The first argument is always going to be 0x2 for this table. The answer is something in this table. 0x297 is save and close. That would be strange they used that, but we can try it with the following: flirc_util record_api 0x2 0x297 Could it be decimal 297? Which would translate to hex code 0x129, but that's not in the table. So maybe they chose something that isn't listed to be safe? Try that with: flirc_util record_api 0x2 0x129 But if those don't do it, and I were to guess, I would think it would be something that kinda made sense. Maybe AC Catalog? That should help, let me know how that goes.

Can you do a logcat from the other firestick that works and get the keycode? That would be really helpful. I'll try and figure this out without hardware to test.

All really helpful clues, thank you. It's strange, because tens of thousands of users use flirc in pi's, and htpc's while in sleep, and allow the remote to wake up the PC. I would have a lot of complaints of users that can't get their devices to stay asleep. However, Apple's USB stack, and especially on their ipad is a different beast. I have not tested it, and that isn't to say there is something I'm missing. I'm thinking it's not so much with the device receiving a signal and waking up the ipad, but something in the USB response that reports a wake-up event. I have one more idea. Do you have anything like this: https://www.amazon.com/Syntech-Adapter-Thunderbolt-Compatible-MacBook/dp/B07CVX3516/ref=sr_1_4?crid=18PWPIJS0D44O&keywords=USB+A+to+C&qid=1661473174&sprefix=usb+a+to+c%2Caps%2C155&sr=8-4 Something without a hub to rule that out? Curious, how did you extract the log?

Can you disable the built in profiles. Fire up the GUI, go to advanced, and then disable all those profiles. Let me know if it's any better after that. Outside of that, if it doesn't work, can you clear the config, and just leave the flirc in there, and see if it happens again? I know that seems silly, but it would tell me if it's something wrong with my USB stack, rather than the usb submission of codes (because nothing would ever be received/submitted). Thank you. I'll see if I can reproduce locally. Is it in there with just an adapter, or a hub with other devices? A link to the adapter would be helpful.

Hey Nice job.

Thanks for the log, that was helpful. Can you attach your config? ** EDIT ** - To clarify, the configuration from Flirc