View Single Post
Posts: 208 | Thanked: 220 times | Joined on Apr 2010
#344
Originally Posted by No!No!No!Yes! View Post
Thanks for feedback.
Choice to have QBW update even if phone is locked was deliberate as QBW is also a monitoring tool and a background program frontend which can maintain/hold some persistency with collected info over time and which may require update even if not in sight.
However you are right about the fact that an option should be present here ... and choice to disable update if out of sight left to the user.
I'll give it a thought.
Thanks!
Actually I have setup the dbus script to underclock device when locked (no need for a fast cpu if its just gonna be sitting idle ) and I also have a widget that monitors temp at intervals and sets max overclock speed (don't want it to get too hot).
As you can imagine, after i lock the device it underclocks as intended but again overclocks due to the widget
And from what you posted, if i understood right, are you also going to provide option to disable update when that desktop is not in view (some other desktop/homescreen is)?.That would be very helpful thank you
 

The Following User Says Thank You to techie For This Useful Post: