Bug 7079 - Power off Jive when the battery is low in suspend mode
: Power off Jive when the battery is low in suspend mode
Status: CLOSED FIXED
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: PC Windows XP
: -- normal (vote)
: 7.4.0
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-11 12:18 UTC by Richard Titmuss
Modified: 2009-10-05 14:32 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Titmuss 2008-02-11 12:18:45 UTC
We need to power off Jive when the battery is low in suspend mode. This is being punted from 7.0.

At the moment the key and lcd backlights are enabled on resume to provide prompt feedback to the user. This should not happen when the wake up source is the rtc timer. At the moment it does not appear easy to tell in the kernel what irq was used for wakeup, I need to ask Ben Dooks about this.

Once this is complete the suspend script needs enhancing to resume every hour (or so), check the battery and power off on a battery low condition.
Comment 1 Blackketter Dean 2008-02-11 12:50:23 UTC
I checked with Caleb and his take is that this is OK, but the current behavior will eventually wear the battery down unnecessarily. 
Comment 2 Richard Titmuss 2008-07-24 04:52:58 UTC
punting to 7.3
Comment 3 Richard Titmuss 2009-06-09 12:03:30 UTC
Fixed in jive 7.3.3
Comment 4 James Richardson 2009-10-05 14:32:42 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.