
02-04-2012, 08:44 AM
|
| | CrackBerry Master Device(s): 9810, 9800, HTC Tilt2 Carrier: AT&T/Cingular Pin: ned to the Cross! | | Location: Baltimore, MD Join Date: Aug 2010 Posts: 1,147 Likes Received: 242
Thanked 79 Times in 71 Posts
| |
Quote:
Originally Posted by khl I installed the trial version of SixTools and loved the features but ran into a serious problem the next day. The backlight would not automatically dim. I locked the device with the lock button to turn off the screen, but after a second, the screen will light up again. This problem persisted after a battery pull, so I uninstalled SixTools.
After uninstall and a reboot, my 9860 would show the ‘busy’ clock every 20 seconds, as if it’s polling something. This happens whether or not I’m using the phone. My battery is draining 10x faster as a result.
I’ve tried reloading OS 7.1.0.205, but the problem still persists.
Has anyone had this problem or have suggestions on how to fix? Perhaps Shao128, the SixTools developer, can help. Thanks. | I have SixTools on my 9810, also running 7.1.0.205. No such problems. IIRC, SixTools doesn't continue to run unless you leave it open. As far as I know, it changes settings, then leaves them alone. By removing SixTools, you only eliminate the way to change them back.
Have you tried Setup -> Options -> Device -> Advanced System Settings -> Blackberry Device Analyzer? It comes with 7.1 and will run under 7.0 -- there's a separate DL link in the forums for those still on 7.0. Run the battery test and let it go for several hours. It'll show (among other things) the top 5 apps for battery use. In my case, 2 of the three were related to universal search.
More important. OS 7.1.0.205 is a memory hog. Not doing anything, I get 3.5-4% battery use. And I'm not certain that OS 7.1 correctly reports drain, particularly on the lower end. I've often had 20+% drops just by opening an app that shouldn't use that much. And if you read the 7.1.0.205 thread in the Leaked OS section, there are lots of reports of large battery drains.
SixTools is NOT your culprit, the OS version you're running is!
|