Im not sure why this isnt a bigger issue with everyone. I have 4G in my city but dont use it much because after i turn it on, the phone continues to search for a signal even after i turn it off until i reboot my phone. This drains my battery like crazy. I d/l'd alogcat and saw that the 4G radio keeps scanning non stop after it is turned off.
It seems like it should be a simple fix to have the 4G radio stop scanning once 4G is turned off. If this could be fixed then i would most certainly use 4G. As it stands now, i hate knowing that my battery is going to be sucked dry even after i turn off 4G.
Do other people not experience this? Is this problem isolated to just a few phones and thats the reason its not brought up more?
If anyone knows a fix for this then please share.
PS: posted this on another forum also. would really like to figure this out.
- 01-14-2011, 03:10 PM #2
This issue seems to have been resolved for most people's phones with the last update, check your settings/About phone/software information and check to make sure you have software build # 3.70.651.1 This adds a widget to turn off the 4g scanning until you tap to scan.
The 4g radio on, but not scanning constantly, doesn't seem to use much battery, IMO.
have the latest software 3.70.651, not rooted, hw 0004. i get the widget at the top if i turn on 4g. my problem is when i turn it off completely, it continues to scan unsuccessfully until i reboot. using alogcat i get this wimax error repeatedly once 4g is shut off completely, not using the widget.
- 01-14-2011, 04:58 PM #4
- 01-14-2011, 05:03 PM #5
- 01-15-2011, 11:16 AM #7
Pre 3.70 - phone scans non stop until reboot. Battery dead faster than "Unnamed ensign" On a Star Trek away mission.
Post 3.70 - Phone will scan once after 4g connestion is lost (Will not scan if manually turned off) and then wait for you to manually force a new scan. But you will still see the "connection refused" error in alogcat.
The post 3.70 scenario uses very little additional battery compared to the pre 3.70 one.
Thanks for the info.....
The only problem i have with this is that it seems like not everyone gets this connection refused error. ive asked others and some have said that they dont see this error using alogcat after shutting off 4g?????????????????
Also, i can confirm, at least on my phone, that the battery definitely takes a hit because of this. At one point i had switch pro on my phone which would turn 4g on and off at the start of every boot up. This caused the connection refused error to run right from the beginning of a newly charged battery. When that was occurring, i would get about half the normal battery life i would normally get. Once i figured this out and stopped 4g from being started up and thus stopped the connection refused errors, my battery life doubled.
Can others confirm that they do/don't have this error message using alogcat??????
- 01-15-2011, 02:09 PM #9
- 01-17-2011, 02:11 PM #10