revin Posted March 30 Report Share Posted March 30 On 3/23/2024 at 11:30 PM, jason said: @asyba @revin can you send me your configurations. See attachedminipc.skip Quote Link to comment Share on other sites More sharing options...
jason Posted March 31 Report Share Posted March 31 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 4 Quote Link to comment Share on other sites More sharing options...
ajmxco Posted April 5 Report Share Posted April 5 @jason - thanks for finding the problem and fixing. When I click on one of the new download links I get a weird xml error. Is this a me problem? Quote Link to comment Share on other sites More sharing options...
jason Posted April 7 Report Share Posted April 7 On 4/5/2024 at 5:42 AM, ajmxco said: @jason - thanks for finding the problem and fixing. When I click on one of the new download links I get a weird xml error. Is this a me problem? Try again Quote Link to comment Share on other sites More sharing options...
jason Posted April 17 Report Share Posted April 17 Is no news good news? Quote Link to comment Share on other sites More sharing options...
MoSPDude Posted April 17 Report Share Posted April 17 With all the activity and the new firmware, I decided to give it an update and leave batteries in it. This may be just anecdotally, but it's been fine for the last week as I've pressed the volume button every night and it responded. Until last night, when I pressed the volume button, then pressed the "A" button to remind myself what device it is on. This morning, it is failing to respond... so I tried to follow the instructions under, However, this fails at the 2nd step - connecting the USB cable gives a message from Windows "USB device not recognised"... I had to remove the batteries to get it to respond to USB.... I tested the batteries, and they still measured Okay - put the same batteries in, and it came back to life. Current firmware is 4.12.26-0-gf661a78 - I've attached an export of my remote configuration and the log I got from it once it came back responding to the app. "proc" returned {"USB":243090} "butt" returned {"Vol Up":{"Released":280149}} (I guess it lost the error logs as I had to remove the batteries??) Is there any trick to get it to reset to respond to USB if it's showing Device not recognised?? flirc-remote-control20240417.log Lounge Remote.skip Quote Link to comment Share on other sites More sharing options...
Melchromate Posted April 18 Report Share Posted April 18 I installed firmware v4.12.26 back on the 2nd of April aand haven't had any battery issues since, so it is looking promising. Quote Link to comment Share on other sites More sharing options...
MoSPDude Posted April 24 Report Share Posted April 24 Definitely weird! I put new batteries in after last week to ensure I had another clean shot at getting any debug logs etc. Again, it's been fine for almost exactly week - tried this morning, and it wasn't responding. Fired up the application, connected the USB, the remote started responding, but the application still showed Offline. Unplugged, and the remote went back to dead. Re-connected, and the application recognised it. The log then simply showed, <2>task_start(41): Hypnos: v4.12.26 <1>malloc_addblock(61): Heap Block: 0x20002BFC - 0x20007BFF (20k) <1>log_rcause(378): BOD33 BOD12 SYST WDT EXT POR <1>log_rcause(385): F F F F F T <1>init_remote(266): Initializing Past Profile: A <3>usb_hotplug(46): Connected <2>default_handler(163): Vol Up pressed <2>default_handler(163): Vol Up released <2>default_handler(163): Vol Down pressed <2>default_handler(163): Vol Down released Same firmware are before :- "proc" returned "{"USB":247094}" and "butt" returned {"Vol Down":{"Released":264566}} I'll keep trying to see if I can get any more information from it - I'll start to use it more and see if that helps? Quote Link to comment Share on other sites More sharing options...
jason Posted April 24 Report Share Posted April 24 6 hours ago, MoSPDude said: Definitely weird! I put new batteries in after last week to ensure I had another clean shot at getting any debug logs etc. Again, it's been fine for almost exactly week - tried this morning, and it wasn't responding. Fired up the application, connected the USB, the remote started responding, but the application still showed Offline. Unplugged, and the remote went back to dead. Re-connected, and the application recognised it. The log then simply showed, <2>task_start(41): Hypnos: v4.12.26 <1>malloc_addblock(61): Heap Block: 0x20002BFC - 0x20007BFF (20k) <1>log_rcause(378): BOD33 BOD12 SYST WDT EXT POR <1>log_rcause(385): F F F F F T <1>init_remote(266): Initializing Past Profile: A <3>usb_hotplug(46): Connected <2>default_handler(163): Vol Up pressed <2>default_handler(163): Vol Up released <2>default_handler(163): Vol Down pressed <2>default_handler(163): Vol Down released Same firmware are before :- "proc" returned "{"USB":247094}" and "butt" returned {"Vol Down":{"Released":264566}} I'll keep trying to see if I can get any more information from it - I'll start to use it more and see if that helps? When you unplug the remote the leds cut off for a bit. Quote Link to comment Share on other sites More sharing options...
ajmxco Posted Sunday at 05:16 AM Report Share Posted Sunday at 05:16 AM (edited) On 4/16/2024 at 9:04 PM, jason said: Is no news good news? v4.12.26 fixed my lock-up problem. Thank you. Edited Sunday at 05:16 AM by ajmxco 1 Quote Link to comment Share on other sites More sharing options...
chrisharling Posted Monday at 01:01 AM Report Share Posted Monday at 01:01 AM Hey Jason, thanks for all your work on this. I think I have experienced the issue you posted in the video last page of the forum - remote completely locks up and is unresponsive to button press, usb, etc. To reset all I had to do was unplug USB and pull the batteries out. Then it behaves as normal with the same batteries. Got two toddlers pressing the activity buttons, they must have good timing. Was running 4.12.24, just updated today to 4.12.26 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.