Challenged_101
Newbie
Bought the S3 off craigslist a few years back and probably the last year have experienced this problem. It's a AT&t phone running on T-mobile, rooted but running Android 4.1.1.
First off, I hardly use the phone. I don't do any social media, don't play games and very seldom use the internet, too damn slow. A usual day is half a dozen short calls.
There are days when the phone functions as it should with a 15 percent drain at the end of the day. But more often than not, it will need to be charged in 4 to 6 hours. When this happens, the phone is always warm when idle and the screen is off.
I downloaded the free version of DS Battery Saver, set it on slumber where the unit is suppose to be in deepsleep when the screen is off to no avail.
Wakelock Detector shows 4% awake and statistics compiled for almost 8 hours. Right now the battery is down to 39% and I made 6 short calls. Reviewing the log under screen wakelock, the biggest number is Phone @ 3h 4m.CPU wakelock, Android system @ 12m41s, Wakeup triggers, largest volume being Samsung push @107 times and Kernel wakelocks it's delete_wake_locks @ 53m47s.
I've tried a new battery with the same results. Do I inherit this problem if I install a custom rom?
Thanks for any help.
First off, I hardly use the phone. I don't do any social media, don't play games and very seldom use the internet, too damn slow. A usual day is half a dozen short calls.
There are days when the phone functions as it should with a 15 percent drain at the end of the day. But more often than not, it will need to be charged in 4 to 6 hours. When this happens, the phone is always warm when idle and the screen is off.
I downloaded the free version of DS Battery Saver, set it on slumber where the unit is suppose to be in deepsleep when the screen is off to no avail.
Wakelock Detector shows 4% awake and statistics compiled for almost 8 hours. Right now the battery is down to 39% and I made 6 short calls. Reviewing the log under screen wakelock, the biggest number is Phone @ 3h 4m.CPU wakelock, Android system @ 12m41s, Wakeup triggers, largest volume being Samsung push @107 times and Kernel wakelocks it's delete_wake_locks @ 53m47s.
I've tried a new battery with the same results. Do I inherit this problem if I install a custom rom?
Thanks for any help.
