jason

Use this version in the forums and don’t upgrade.

Sorry for the delay, you can try the attached. If this doesn't work, open up the button, and set the button to repeat to 3, let me know if this works. Sony STR-ZA1100ES.json

Happy Easter. Embedded is v4.12.26 which should has this fixed. The GUI is unstable. We have core libraries updated with a lot of fixes involved. Unfortunately, this was a necessary step, as we were falling behind with react native desktops public stable release. There are things that could be broken, icons, crashes. Etc. But the firmware update should work, and you can revert back to the previous if it's giving you problems. But initial testing seems fine. We just not have tested everything yet. Linux Download Mac Download Windows Download

Listen, I've got very little time, and I'm not posting binary images all over the forum for users to brick their devices because they don't know what they are doing or don't understand their are multiple hardware sku's. The flirc config stores hashes. I know nothing about what it's receiving with those. In order for me to fix anything, I need to reproduce it.

Thank you, the log was helpful.

This is not true. You can plug the USB into another device with no GUI software and it should work with the previously paired remote.

Because the config is compressed, information is lost when put on the remote, and although I don't have a public way of reading it out, even if we did, it wouldn't tell us the device and manufacturer. But I would use my decoders to try and look it up. I have all the past firmwares posted on the forum somewhere.

Not helpful, what did you add here so I can reproduce this.

What remote profile did you use in the skip app? The manufacturer and device?

What profile are you using on your skip1s? Can you post your config from your skip and from your flirc?

Flirc USB

IMG_3189.mov If the attached video doesn't work, here is cloud link: https://share.flirc.io/3196CdTQ This took me about 5 minutes to reproduce of pressing the B button. It is purely timing. If you press a profile button at an exact moment in time, we cause the issue. You do not need to press the profile button in repetition. It can be A/B/C/Color dots at the exact moment after any subsequent button. I confirmed in lab today, in this state, it's stuck and using more power. So you might have pressed this sequence, put the remote down, come back the next day, see it stuck, and it would have had an impact on battery life. This was not the only issue that caused this in this thread. I fixed 3 other edge cases and documented them. I have also replaced a few remotes that were in the first batch of shipments, and completely unrelated. Firmware update coming, it's already solved. Just a matter of getting it into a release and publishing. Let's hope this is the last edge case.

I reproduced it and I fucking fixed it. Jesus christ. I'll post a video tomorrow. I swear I sat here for 3 hours with logging pressing buttons until I got it to happen. I analyzed the logs until I saw a pattern, tried it, never got it to happen. But noticed it only happens after pressing a/b/c It's strictly a timing issue. Edge case, and I understand why it can happen, but don't understand why it wont 'unstick'. But I handle these specific buttons in interrupt context. So I changed this. I queue them and move them into my normal task manager and it works fine. I'll push an update as soon as possible. GUI is currently a mess, so we need to clean it up. I'll look at some kinda remedy for everyone this week.

@asyba @revin can you send me your configurations. I'm working on this.

That shouldn’t be necessary unless there was a firmware upgrade. I’ll look into it

Wait what?

Sorry, they were auto archived. Updated the links.

Is it programmed to Manufacturer: Flirc, Device: Shield? Make sure ADB Debugging is off.

It’s always after a period of no use right? Like you pick it up and it’s unresponsive. Not right in the middle of pressing during operating an activity?

yeah, I'm going to look at it this week

The latest firmware is 4.12.23. I'm not sure if firmware updates are going to work in linux unfortunately. I can supply a tool for linux, but unfortunately, I am absolutely swamped. 4.12.23 will be better, but still has one bug. I'm working on it.

consistent in all applications?

Did you do anything in device manager? there are two devices. One is the hid keyboard and one is the hid custom device. Windows should auto assign the driver. This is strange. Do you see anything suspicious in device manager?

if you try to record the same signal again, does it say it's already been recorded?