Jump to content
Flirc Forums

Battery does not last for more than a day


Shiv

Recommended Posts

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

  • Like 4
Link to comment
Share on other sites

  • 2 weeks later...

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

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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. 

Link to comment
Share on other sites

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

Link to comment
Share on other sites

Agreed, mine is lasting pretty much around a week before it starts to act up - again, to add, @jason thanks for all your work on this.

I'll continue to try and capture logs etc. if it is being helpful? (before this last update, I'd been taking the batteries out until I needed to use it :-) )

This time it did respond to USB and the app, and gave the attached log - I did not remove the batteries, though I did unplug the cable, and re-plug the cable - so it's given 2 sets of output.

Again, I hope this may be of some use? Any tips/hints/advice on what we could do to help?

Otherwise, I'll continue to use it with some fresh batteries! I might have to swap to rechargeable ones though!

Thanks again!

flirc-remote-control20240503.log

Link to comment
Share on other sites

10 hours ago, MoSPDude said:

Agreed, mine is lasting pretty much around a week before it starts to act up - again, to add, @jason thanks for all your work on this.

I'll continue to try and capture logs etc. if it is being helpful? (before this last update, I'd been taking the batteries out until I needed to use it :-) )

This time it did respond to USB and the app, and gave the attached log - I did not remove the batteries, though I did unplug the cable, and re-plug the cable - so it's given 2 sets of output.

Again, I hope this may be of some use? Any tips/hints/advice on what we could do to help?

Otherwise, I'll continue to use it with some fresh batteries! I might have to swap to rechargeable ones though!

Thanks again!

flirc-remote-control20240503.log 646 B · 3 downloads

I see low battery alert on yours

Link to comment
Share on other sites

On 5/2/2024 at 6:22 AM, furyflirc said:

Hello @jason ,

This time around the remote lasts about week before locking up.

Here is the info you wanted us to post.

Firmware ver: 4.12.26-0-gf661a78

 

butt_command.png

proc_command.png

skip_remote_log.rtf 1.28 kB · 5 downloads

I see a potential crash issue, and will issue a patch. However, in all likelihood, it's nearly impossible unless reading memory is corrupt, only time that could happen is if the battery goes too low.

If you ran into the prior bug before the firmware update, it could have very well drained the battery. Updating the firmware would fix the issue, but the batteries would still be low from before.

Link to comment
Share on other sites

5 hours ago, jason said:

I see a potential crash issue, and will issue a patch. However, in all likelihood, it's nearly impossible unless reading memory is corrupt, only time that could happen is if the battery goes too low.

If you ran into the prior bug before the firmware update, it could have very well drained the battery. Updating the firmware would fix the issue, but the batteries would still be low from before.

@jason

The batteries I was using were a fresh pair from the store.

Every time a new fix has been released I've put in a new pair of batteries to eliminate that being an issue, and the batteries I'm using are the normal type (not rechargeable).

I'll be on the lookout for the next patch, thanks!

Link to comment
Share on other sites

3 hours ago, furyflirc said:

@jason

The batteries I was using were a fresh pair from the store.

Every time a new fix has been released I've put in a new pair of batteries to eliminate that being an issue, and the batteries I'm using are the normal type (not rechargeable).

I'll be on the lookout for the next patch, thanks!

You have a way to measure these batteries?

Link to comment
Share on other sites

22 minutes ago, jason said:

You have a way to measure these batteries?

Unfortunately, I don't. If it helps I'm using the HDX batteries you can get at Home Depot. Family has used batteries in this same pack in other devices without issue.

Link to comment
Share on other sites

  • 3 weeks later...

Just to update, mine had been fine on Tuesday this week with the same new batteries from my last post May 3rd - it'd been behaving really well!

Came to use it today, and no response from it - connected to PC with USB, and STILL no response - windows did not acknowledge a USB connection, and the app shows Offline...

Then, to try something different - I swapped the batteries whilst it was connected to USB - and re-plugged - and STILL no response. I now have it in a state where it has new batteries, and is not responding whilst unplugged or plugged to the PC...

@jason - is there anything I can do whilst it is in this state to help debug?

Edited by MoSPDude
Link to comment
Share on other sites

5 hours ago, MoSPDude said:

Just to update, mine had been fine on Tuesday this week with the same new batteries from my last post May 3rd - it'd been behaving really well!

Came to use it today, and no response from it - connected to PC with USB, and STILL no response - windows did not acknowledge a USB connection, and the app shows Offline...

Then, to try something different - I swapped the batteries whilst it was connected to USB - and re-plugged - and STILL no response. I now have it in a state where it has new batteries, and is not responding whilst unplugged or plugged to the PC...

@jason - is there anything I can do whilst it is in this state to help debug?

If it’s not detected by the computer, there isn’t much we can do. It was probably low on battery and just hung, regardless of having a new battery or power source. 
 

Link to comment
Share on other sites

  • 1 month later...
On 5/3/2024 at 3:41 PM, jason said:

I see a potential crash issue, and will issue a patch. However, in all likelihood, it's nearly impossible unless reading memory is corrupt, only time that could happen is if the battery goes too low.

If you ran into the prior bug before the firmware update, it could have very well drained the battery. Updating the firmware would fix the issue, but the batteries would still be low from before.

Hello @jason

Do you have an update on this patch? Thanks.

Link to comment
Share on other sites

  • 2 weeks later...
36 minutes ago, frerk said:

How do I get v4.12.26 or later? My app shows 4.12.18 and no updates apparently available. The download link above no longer works. Mac App version 0.9.980.8592 (0.9.980.8592)

Try this:

Firmware Update

 

If you are not presented with update dialog, please do the following:

 

Close the software

Unplug the USB-C cable

Remove the batteries.

Press and hold the return and center key while you insert the USB-C cable (image attached)

Start the software

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...