-
Many people would probably like to personalize and stylize their phone, and a screensaver is a way to do that, but people also want to avoid wasting battery power by keeping the backlight on longer than necessary.
Feedback is needed from the user community on how much difference a properly-configured time-limited screensaver makes to battery life with the various devices and usage patterns out there.
5 screensavers are offered, free using coupon SCRTEST841 (up to 40 uses):
Bat Screensaver
Star Clock-Screensaver
Ankh Clock-Screensaver
Cross Clock Screensaver
USA Flag Screensaver
These screensavers wait until the display times out normally as configured in Options/Screen, then show themselves and hold the backlight on for a specified length of time (which may be zero), then wait for the timeout period specified in Options/Screen to expire again, and then the screen turns off. The default behavior is to extend the 2nd timeout by 1 minute.
The request is that the users who download for this study configure their screensaver however "feels right" to them -- just long enough to be noticed and stylize the phone, but not so long that it's sure to waste the battery.
This is a study of whether users buying such products would end up actually keeping them (because they stylize the phone without ruining performance), or if customers are more likely to discard the product because a practical balance of style and performance couldn't be found.
Thank you in advance for your valuable feedback.10-23-09 08:35 PM - Here's my theory. There are two ways I know of to keep the backlight on. One keeps it on continuously, the other allows it to fade or flick out periodically and then re-activate immediately. My theory is that bblight is using the latter method, which would -for sure- cause the exact phenomenon you're seeing. It works like this:
1. The Flag terminates itself one way or another -- if it was in screensaver mode, the backlight would turn off at the moment of termination, or if it was in charging monitor mode the backlight would not turn off immediately, just begin counting down toward its normal timeout.
2. Whether immediate or deferred, the backlight does time out and try to turn off, and then (in my theory) bblight turns it back on. The Flag notices that and assumes you are again using the phone. Then the backlight times out, and both bblight and the Flag get notified of that. Both turn it back on, and to the Flag that looks like it's time for the screensaver to come up again -- it appeared that you were using the phone and then put it down and it timed out, and that's exactly when a screensaver should appear.
3. Then we're right back to #1.
If you have "Show on relight" checked, that's where the screensaver would flick out for a moment and then reappear but stay on -- the screensaver times out, bblight turns the display back on, and the screensaver shows itself again just as it's been configured to.
If you have "Show on relight" off, that's where the homescreen would show and then after the backlight times out again, the screensaver reappears.
The Flag in screensaver mode is not compatible with an app that keeps the backlight on, but if bblight only does that when plugged in, the Flag would be in chargemon mode at that time. In that case it should be compatible with an app that keeps the backlight on by the continuous method, but would not be compatible with an app that keeps the backlight on by the reactive method (turning it back on immediately when it tries to turn off).
----------
As for combining I Charge Cool and a screensaver, just uncheck "Charging Monitor" in the screensaver but leave "Start Automatically" and "Screensaver" checked, and then turn I Charge Cool on with "Start Immediately", and they should integrate fine -- when you plug in, the screensaver will cede to I Charge Cool, and when you unplug, ICC will disappear and the screensaver will reappear after the next timeout.
And I think that's the answer in 5000 words or less.
Last edited by LSphone; 10-25-09 at 07:24 AM.
10-25-09 07:15 AM
