Bug 14053 - Battery Icon on rev 4 & 5 when no battery installed
: Battery Icon on rev 4 & 5 when no battery installed
Status: CLOSED FIXED
Product: SB Radio
Classification: Unclassified
Component: API
: Include FW version in comment
: PC Other
: P1 normal (vote)
: 7.4.0
Assigned To: Caleb Crome
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-15 09:06 UTC by James Richardson
Modified: 2009-10-05 14:31 UTC (History)
2 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Richardson 2009-09-15 09:06:26 UTC
with r7571 I noticed that battery was detected when it is not installed.

# cat battery_temperature
65507
# cat power_mode
7
Comment 1 SVN Bot 2009-09-15 09:34:40 UTC
 == Auto-comment from SVN commit #6411 to the player repo by ccrome ==
 == https://svn.slimdevices.com/player?view=revision&revision=6411 ==

Fixed #14053.  have_batt was calculating incorrectly.
Comment 2 SVN Bot 2009-09-15 09:35:23 UTC
 == Auto-comment from SVN commit #7576 to the jive repo by ccrome ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7576 ==

Fixed #14053.  have_batt was calculating incorrectly.
Comment 3 Caleb Crome 2009-09-15 09:39:35 UTC
Ah, there still seems to be a bug in the lua code..
Comment 4 Caleb Crome 2009-09-15 09:43:20 UTC
Nope, really is fixed.  I got spoofed because of upgrading the MSP on the fly.
Comment 5 James Richardson 2009-10-05 14:31:46 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.