jason

No, something went wrong. You were pressing the button, and it looked fine, and then all of a sudden the length of numbers reported increased. If I'm to believe the first press, than I see nothing wrong with the code. Can you try to re-learn again? Once done, save and post your configuration file.

First button looks fine. Second button, not sure what the hell is going on with that one. Can you share a pic of the remote, which buttons were which?

Thanks for letting me know it was working and thank you even more for the patience and support. I will not only document and pin this, I will improve on it. I don’t know if Microsoft will ever fix the issue so the goal will be to talk to the remote through an outside app and you skipapp wont know the difference. It’ll take a bit of time but it’s doable.

In the Settings (3 dots at the bottom right), go to accessibility, enable admin panel. upper right corner, hit the wrench. Go to the last tab called learning. Press and hold a button there. Copy both the windows and paste them here.

you can try learning it with the current beta version:

Downloads: SkipApp Tool SkipUpdate for Config Files Description: Thanks for your patience, this was a lot of work. You'll need special versions of software for now. But here is a summary of what you do. Use our app as you would. When you are ready to 'sync', you'll export your configuration with a special process. Enable special export by pressing 'tab' 3 times while in the tools tab Click Export Remote Configuration Save to Disk Open up skipUpdate Tool and load the saved config Sync Here is a video demo and a link if the embedded video doesn't play. CleanShot 2024-04-12 at 19.02.48.mp4

I understand you are frustrated. I have an idea that will be easier to implement but not as elegant. Basically, I'll make this a two step process. I'll add the ability to export the binary config that gets downloaded to the remote. This will export into a file. Step two will be to launch another program that will be able to upgrade the remote, as well as load this file. That is all. This will evolve into an app that SkipApp talks to. Basically, it will launch alongside SkipApp and handle the device communication when this situation happens. It will take a bit longer to implement this, and iterate on this elegantly. But will be our goal. Please be patient, it's just me and one other developer at the moment. I'll try and have something for you this week. I'm really sorry for this frustrating inconvenience.

I’m at a loss. Windows forces us to use a framework and then permits other developers to lock us out of our own device. we issued a fix and it asks you for permission and a password and it is supposed to reverse their registry modification. That has seemed to work for 75% of people. Were you prompted for a password? You can try right clicking the app and running as administrator. now that it doesn’t work for you I don’t know what the hell to do. The fact that our other software works proves the point that windows fucks us because they force us to use their dumb sandbox. so I have to write a client that our app talks to which talks to the remote. I don’t know what else to do. I’ve spent hundreds of hours on this dumb problem.

Thank you. I’ll have a solution this week.

Can you tell me if this works: Ringtune are you able to connect to the remote and change the led color?

Try again

Oh you are right. Are you on the updated firmware?

my mistake, my build script got stuck. Should be posted.

I posted an update 4.10.5, should fix it.

It's borked, send me a pm.

You said you had 0.9.957.7232, so it's not the right one. You have to re-install the one from the forum and don't let it update when it prompts you.

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.