• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] 2.08.651.2 ROM updates - post 'em here!

I was suffering this exact same thing before the update and found that tied to the Google+ app (note the GPS wakeup during blingeorkl's screen shots) - that will often tie to something bizarre under Google Maps called a Friend service. Google+ will keep looking for location, even if you're not location-sharing in G+ and even if it has to wake up the phone to do it.

So, I'm seeing the staccato pattern of awakes, but if you're seeing GPS wakeups and have Google+ installed - remove it and watch your battery life shoot right back up.
 
EarlyMon said:
I was suffering this exact same thing before the update and found that tied to the Google+ app (note the GPS wakeup during blingeorkl's screen shots) - that will often tie to something bizarre under Google Maps called a Friend service. Google+ will keep looking for location, even if you're not location-sharing in G+ and even if it has to wake up the phone to do it.

So, I'm seeing the staccato pattern of awakes, but if you're seeing GPS wakeups and have Google+ installed - remove it and watch your battery life shoot right back up.
Click to expand...

Uninstalled G+. Thanks for that! G+ is easy enough to use from the browser or my tablet. Maybe in the future, they'll fix it so it doesn't keep waking up the phone.
 
EarlyMon said:
I was suffering this exact same thing before the update and found that tied to the Google+ app (note the GPS wakeup during blingeorkl's screen shots) - that will often tie to something bizarre under Google Maps called a Friend service. Google+ will keep looking for location, even if you're not location-sharing in G+ and even if it has to wake up the phone to do it.

So, I'm seeing the staccato pattern of awakes, but if you're seeing GPS wakeups and have Google+ installed - remove it and watch your battery life shoot right back up.
Click to expand...

I don't have Google+, but have been experiencing some GPS wakeups myself. Often the satellite icon will stay on and I have to manually switch my GPS off.
 
I nandroided to 2.3.3 and haven't had any of the wake issues. I'm still using the updated radios and all the same apps so I have a feeling it has something to do with the update and possibly some interaction with the apps that's causing Sense to run rampant like that (32,500 seconds is 9 hours of use, all while the screen was turned off). I will continue investigating but it seems even on 2.3.4 ROMs I still have the issue, leaving me scratching my head.
 
After flashing freeza's kernel I went to HTC software update to make sure it was unchecked still and it force closes everytime I attempt to access the setting. Anyone else have this happen? Is it supposed to do that to prevent OTA's?
 
I can also confirm the constant wakes, though they don't seem to impact battery life significantly. Note that in the 13 hours since last charge, the phone's been waking quite a bit, but the screen has been off pretty much all day. But battery drain is very low, ~10%.

snap20110822214204.png
 
novox77 said:
I can also confirm the constant wakes, though they don't seem to impact battery life significantly. Note that in the 13 hours since last charge, the phone's been waking quite a bit, but the screen has been off pretty much all day. But battery drain is very low, ~10%.

snap20110822214204.png
Click to expand...

Dumb question, but how do you get the Phone signal, GPS on, Wi-Fi, Awake, Screen on, and Charging in your battery status?

Mine just has the top graph and a list of apps.
 
novox77 said:
I can also confirm the constant wakes, though they don't seem to impact battery life significantly. Note that in the 13 hours since last charge, the phone's been waking quite a bit, but the screen has been off pretty much all day. But battery drain is very low, ~10%.
Click to expand...

It's not so much the battery I'm concerned about, I prefer to know why it keeps waking up. Don't want all my infos to be stolen :(

EVOlution3: tap the chart and it'll open up with more detail
 
EVOlution3 said:
Dumb question, but how do you get the Phone signal, GPS on, Wi-Fi, Awake, Screen on, and Charging in your battery status?

Mine just has the top graph and a list of apps.
Click to expand...

Tap where it says "12h 6m 16s on battery" or whatever amount of uptime it says for you...that will bring up the second screen with the additional info.
 
BTW - system logs show that very frequently, the wifi is being enabled.

I had my wifi policy set to never sleep - I'm resetting to "after 15 minutes" to see if that changes anything.
 
EVOlution3 said:
LOL, now I feel dumb.
Click to expand...

And you think this makes you special how?!?! :D

We've all been there, promise! :D

BTW - a little early to guarantee - but -

I have location with GPS off, I froze the HTC IQ Agent (no effect on those) - but so far, taking wifi off of never sleeping seems to possibly be curing this staccato wake up issue.

And sometimes - that battery graph thing just gets itself all confused. Still haven't figured out what triggers that.
 
falconey said:
EM, where are you finding the option to allow wifi to sleep?
Click to expand...

Settings, Wireless & networks, Wi-Fi settings, Menu, Advanced -> Wi-Fi sleep policy

OK - so now that my battery widget got unconfused (I had to plug it in) - I'm still getting staccato wakes but the pattern has changed.

Easier to just show the picture:

15-minute-wifi-sleep-sm.jpg

So, something going on does turn around and wake wifi - but not everything.

I suspect that it's going to take going back the logs to decipher this one.
 
What logs, exactly, are you looking at? I could do some digging if I knew where to look.

For now, I'm finding it a good opportunity to try out other ROMs - at least Supra AOSP doesn't have the weird wake problems :p
 
EVOlution3 said:
LOL, now I feel dumb. I swear I tried it before and it didn't open up. Got it now though..
Click to expand...

Ha, as EarlyMon said, happens to all of us. And, on the flip side, this is one of the very rare times I got to feel smart! ;)

I'd be interested too if we can crack what's causing the wake ups. I'm getting them too, although since I charge daily and everything, I've yet to see a detriment other than that better battery life is always better.
 
blingeorkl said:
What logs, exactly, are you looking at? I could do some digging if I knew where to look.

For now, I'm finding it a good opportunity to try out other ROMs - at least Supra AOSP doesn't have the weird wake problems :p
Click to expand...

There should be a battery stats log file on your sd card. battery_history.txt
 
falconey said:
There should be a battery stats log file on your sd card. battery_history.txt
Click to expand...

Hmmm - don't have that one.

I'm looking at system logs, available via "adb logcat" or the aLogcat app, or as available in System Tuner (Process Monitor) or Android System Info by Electric Sheep.
 
EarlyMon said:
Hmmm - don't have that one.

I'm looking at system logs, available via "adb logcat" or the aLogcat app, or as available in System Tuner (Process Monitor) or Android System Info by Electric Sheep.
Click to expand...

Ok, Maybe one of the apps I'm using creates this file for me. Or maybe the rom i'm on is creating the file. I've attached my current file for clarity.

Edit: I can't upload the entire fiile so I deleted some info. When viewed from the phone the file is much more legible.
 

Attachments

Yep, that looks like a battery logging file from some app, just shows temp and juice vs. time.

System logfiles look like this:

Code: 
--------- beginning of /dev/log/system
D/WifiService(  286): acquireWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.BinderProxy@40d372f8} Mode: 2
D/WifiService(  286): enable and start wifi due to updateWifiState
D/ConnectivityService(  286): [embedded] ConnectivityChange for WIFI: CONNECTING/OBTAINING_IPADDR, default=-1
D/ConnectivityService(  286): Dropping ConnectivityChange for WIFI: CONNECTING/OBTAINING_IPADDR
D/ConnectivityService(  286): Dropping ConnectivityChange for WIFI: CONNECTING/OBTAINING_IPADDR
W/AlarmManager(  286): RXTXtriggerAlarmsLocked
D/LocationManagerService(  286): =NET= reportLocation, (normal)
D/LocationManagerService(  286): =NET= reportLocation: gpstime = 998179566725
D/LocationManagerService(  286): =NET= reportLocation: lTimeStamp_hi = 232
D/LocationManagerService(  286): =NET= reportLocation: lTimeStamp_lo = 1747154053
D/LocationManagerService(  286): =NET= reportLocation: Latitude = 3.526035615E7
D/LocationManagerService(  286): =NET= reportLocation: Longitude = -1.0669602905E8
D/LocationManagerService(  286): =NET= reportLocation: iAccuracy = 60
D/LocationManagerService(  286): =NET= reportLocation: result_field = 113
W/ActivityManager(  286): Unable to start service Intent { act=com.htc.android.iqagent.action.lc30 (has extras) }: not found
D/WifiService(  286): releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 binder=android.os.BinderProxy@40d372f8} Mode: 2
D/WifiService(  286): enable and start wifi due to updateWifiState
D/WifiWatchdogService(  286): (android.server.ServerThread) seh (00:24:7b:15:73:a0) does not require the watchdog
V/NotificationService(  286): dual Led off

The other tools tend to add timestamps - but it's a firehose flood of detailed under-the-hood info, so be forewarned, it's not super easy to deal with.
 
You must log in or register to reply here.
Back
Top Bottom