Possible battery drain? - 4G off but the phone keep trying to connect it
I downloaded aLogcat and looked what's going on with my phone processor. To my surprise, there are numerous strings saying:
I/Wimax (87): <DC>trying to establish a connection to DC server
E/Wimax (87): <DC CONNECT> IO error: msg='/1270.1:7771 - Connection Refused'
This goes on continuously with my 4G radio button off. Does your evo do this? Might this contribute to my less than stellar battery life? My battery life is excellent in standby mode - it only goes down by a few percent over night but as soon as I start using the phone it drains over 10 percent per hour with web browsing on 3G (4G off). I turned off always on data and doing minimal syncing.
- 07-13-2010, 03:53 PM #2
- 07-13-2010, 05:24 PM #3
There's a setting to "notify me when an 4G connection is available." Perhaps that forces it to check sometimes?PLEASE, when asking for help provide as much information as possible. Otherwise, it's like calling your doctor and saying "My head hurts." Your doctor can't treat you unless he knows whether you have a headache or a concussion, and we can't help unless we know what the symptoms are and what you did before they occurred.
If I've helped you, please press the Thanks button.
Have a Galaxy S3? Click here ==> Everything you wanted to know about your Galaxy S3
- 07-13-2010, 07:49 PM #6
- 897 Posts
Got pissed and did a quick factory reset........ instantly back to 12 - 16 hours of battery life.... Some thing got hung up in the back ground and I couldn't pin point it for the life of me using all sorts of different programs...
2 days later I updated to the 6.28 update and still have had no problems... I am scared to switch out batteries.. LOL.. No clue what happened but a factory reset helped....
- 09-14-2010, 10:17 PM #8
- 09-17-2010, 01:24 PM #9
So, I was messing around killing processes randomly until those messages stopped. I am rooted and was inside a shell. I finally killed system_server. Well, interestingly enough, maybe 30 seconds later Android restarted - the phone did not reboot, rather it went to the 4g boot screen, not going all the way back to the Android boot screen. When the system came back up in maybe 10 seconds, the messages were gone.
Why did I pick this to kill? Because looking at the logs, it appeared that the process id of the process printing those errors was the system_server.
Not really a fix, but at least it rebooted faster then a full reboot. YMMV
Last edited by kaediil; 09-17-2010 at 01:25 PM. Reason: Added more detail