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

[Verizon] !&$^! google talk

jkc120

jkc120

Android Expert
I tried freezing google talk (due to the known wake lock bug sucking battery). I tried REMOVING it. It is STILL showing up in better battery stats! What gives?!?!

(BBS dump attached).

Prior to this reboot (and attempt at removing it), of the 47 "awake minutes" it had accounted for almost 10 minutes. :mad:

Also, google maps accounted for 15+ minutes of said "awake" time. I have been experimenting with leaving GPS enabled, but due to this I've set the google services location stuff both OFF but kept the GPS enabled. I don't have any apps that ask for location, so if google maps is still showing up, I'm not sure what to make of it.

Anyway, for google talk, how do I get rid of it for good and keep it from sucking battery? I have no need for it on my phone.

And for the location services stuff, what is the bare minimum I need to keep enabled to aid in GPS lock in a timely manner?

Thanks!
 

Attachments

Have you tried uninstalling and then wiping battery stats? Sometimes you get things showing up that shouldn't be until you do that. Just a thought.
 
I'm not sure why you are having issues with google talk. Mine has only caused 3 seconds of partial wakelock in the 3+ hours its been unplugged. I have never had a problem with gtalk. Google+, yes. Google backup, yes. But never an issue with gtalk.
 
There has to be something else at play here. I sync three google accounts to my phone and use google talk as my main phone number (calling in and out) as well as for voice mail. I have a couple of GTalk entries under Partial Wakelocks, but nothing more than 2-3 seconds each.

Looking at your stats, I don't see anything that jumps out at me anyway. Your phone as been awake for 31 minutes at 29 seconds while your screen has been on for 25 minutes and 12 seconds. That means your phone was awake while the screen was off for just 5 minutes and 17 seconds over a 2 hour and 10 minute period of time. That isn't excessive IMHO.

Not only that, but even though the GTalk service kept the phone awake the longest, the "wake lock" period of time was only 1 minute 30 minutes. So that isn't outrageous either.

Personally I think you are overanalyzing this stuff. You are never going to get wakelocks down to zero. Plus the stats will always be different depending on what happened during that period of time. Did you get a voice mail, or a GV text message, etc. All that will increase the wakelock periods of time.

EDIT - I reread the OP and realized that your previous wakelock times were higher. Still, I would monitor the situation more before trying to live without GV.

PS - I also leave my GPS on 100% of the time and never have anything show up under the stats that appears to be related to GPS. So I would tend to agree that there is some app that is getting location data. Perhaps a weather widgets, or a social app, or shopping app, etc.
 
Google talk works great on my phone. I don't obsess over wakelocks (don't even know what they are :p). Talk has never showed up in my batt stats or under "apps" as "running" when I'm not on it and I use it quite often. My phone lasts 12-15 hours on stock aokp kernel M4. If my phone lasts 8 hours, then I know it will because I was using it talking on the phone for 2 hours and had screen on for 2+ hours.

Is your phone actually not performing the way you want it to 'battery efficiency wise' because of one app Talk, or are you just ocd'ing about wakelocks?

As far as GPS acquiring a fast lock mine always takes a while after a new ROM flash. After that one time it locks within 5 seconds every time unless I'm deep inside a building/house and it's storming/cloudy outside.
 
I wonder if this is a bug/problem in the newer gapps? I flashed the 0304 (I think) ones. I should go back to the 0224 ones and see if it changes it.

As for signing out of google talk, I would have to remember to do that after each reboot, right?

I want to know how the hell google talk sync shows up at all in BBS after Talk.apk was deleted entirely. How does that happen?
 
Yeah try the older gapps, although you might run into other compatibility issues there. When I sign out of google talk, I remain signed out through a reboot until I actively go back in and sign in. ymwv I'm sure. Maybe Talk is such an integral part of the OS that it shows as some kind of service idk guessing here
 
jbdan said:
Yeah try the older gapps, although you might run into other compatibility issues there. When I sign out of google talk, I remain signed out through a reboot until I actively go back in and sign in. ymwv I'm sure. Maybe Talk is such an integral part of the OS that it shows as some kind of service idk guessing here
Click to expand...

True...ok here's what I'm trying:

- re-flashed gapps (0304)
- rebooted
- opened talk, signed in, signed out and showed "offline"

I'm plugging in since I was only at 90% anyway, so I can unplug and see BBS from a full charge.
 
jbdan said:
Is your phone actually not performing the way you want it to 'battery efficiency wise' because of one app Talk, or are you just ocd'ing about wakelocks?
Click to expand...

Yes, it was draining battery much worse than previously. I wasn't sure if it was AOKP b26 vs. M4 or perhaps the kernel (franco 18.6 -> M1). But it looked apparent that gtalk and location services were to blame. Unfortunately, I don't have the BBS from the longer period. So no, not just OCD'ing. ;)
 
sic0048 said:
PS - I also leave my GPS on 100% of the time and never have anything show up under the stats that appears to be related to GPS. So I would tend to agree that there is some app that is getting location data. Perhaps a weather widgets, or a social app, or shopping app, etc.
Click to expand...

I don't have any social apps on the phone. No FB. No twitter. No g+. :(

About location services...

So there are 3 options:

- 1. Google's location service
- 2. GPS
- 3. Location & Google search

Does #1 contribute to GPS lock time? Or is it purely a way to get a 'rough' location for apps that ask for location data? If it doesn't affect GPS lock time in any way, I'd prefer to leave it off.

I think the issue was #3 causing a lot of location service wakeups/battery use. But is it possible #1 was also contributing to that?

I don't particularly care if the phone knows my location as I don't every search for things via google search in which I need it to find something nearby. If I do that, I go in via google maps and let GPS do its thing to help me (e.g. if I wanted to find a starbucks "near me" or whatever).
 
jkc120 said:
I don't have any social apps on the phone. No FB. No twitter. No g+. :(

About location services...

So there are 3 options:

- 1. Google's location service
- 2. GPS
- 3. Location & Google search

Does #1 contribute to GPS lock time? Or is it purely a way to get a 'rough' location for apps that ask for location data? If it doesn't affect GPS lock time in any way, I'd prefer to leave it off.

I think the issue was #3 causing a lot of location service wakeups/battery use. But is it possible #1 was also contributing to that?

I don't particularly care if the phone knows my location as I don't every search for things via google search in which I need it to find something nearby. If I do that, I go in via google maps and let GPS do its thing to help me (e.g. if I wanted to find a starbucks "near me" or whatever).
Click to expand...

So turn #1 and #3 off. I have before with no ill affects whatsoever on GPS.
 
jbdan said:
So turn #1 and 2 off. I have before with no ill affects whatsoever on GPS.
Click to expand...

You mean #1 and #3? :) That's what I did yesterday...I'll test the GPS lock tonight when I leave work (I'm leaving GPS enabled for now).

Thanks!
 
jkc120 said:
True...ok here's what I'm trying:

- re-flashed gapps (0304)
- rebooted
- opened talk, signed in, signed out and showed "offline"

I'm plugging in since I was only at 90% anyway, so I can unplug and see BBS from a full charge.
Click to expand...

google talk was still the #1,#2 and #4 in wake locks for various things. Argh.

I'm going to flash back to the old gapps, I think these are hosed.
 
jkc120 said:
google talk was still the #1,#2 and #4 in wake locks for various things. Argh.

I'm going to flash back to the old gapps, I think these are hosed.
Click to expand...

So since google talk was still there, I decided to freeze it in TB again. Rebooted, wiped dalvik (and cache just to be safe) so google talk should be gone.

Awake (): 1 h 23 m 35 s (5015 s) Ratio: 7.9%
Screen On (): 30 m 2 s (1802 s) Ratio: 2.8%

But note the google talk wake looks and that google talk is #2 and #3 :eek::

=========
Wakelocks
=========
*sync*_gmail-ls_Account {name=my.email@gmail.com, type=com.google} (com.google.android.gm.Gmail): 3 m 30 s (210 s) Count:76 0.3%
GTALK_ASYNC_CONN_my.email@gmail.com/android_talk29102f8b46fa (Google Services): 3 m 18 s (198 s) Count:27 0.3%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 43 s (163 s) Count:745 0.3%
ActivityManager-Launch (Android System): 1 m 51 s (111 s) Count:444 0.2%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 m 20 s (80 s) Count:127 0.1%
RILJ (Phone): 1 m 17 s (77 s) Count:420 0.1%
SyncLoopWakeLock (Android System): 1 m 9 s (69 s) Count:3366 0.1%
MMS Connectivity (com.android.mms.Messaging): 1 m 7 s (67 s) Count:4 0.1%
AudioOut_1 (1013): 56 s (56 s) Count:25 0.1%
GFE wake lock (com.good.android.gfe.Good): 55 s (55 s) Count:364 0.1%
sleep_broadcast (Android System): 52 s (52 s) Count:719 0.1%
AlarmManager (Android System): 47 s (47 s) Count:2868 0.1%
DownloadManager (Media): 33 s (33 s) Count:4 0.1%
SMSDispatcher (Phone): 23 s (23 s) Count:7 0.0%
ConnectivityService (Android System): 16 s (16 s) Count:2878 0.0%
*sync*_com.android.calendar_Account {name=my.email@gmail.com, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 14 s (14 s) Count:6 0.0%
Checkin Service (Google Services): 14 s (14 s) Count:889 0.0%
GTALK_AUTH_TOKEN (Google Services): 13 s (13 s) Count:115 0.0%
*sync*_subscribedfeeds_Account {name=my.email@gmail.com, type=com.google} (Google Services): 11 s (11 s) Count:719 0.0%
*sync*_com.google.android.music.MusicContent_Account {name=my.email@gmail.com, type=com.google} (com.google.android.music.Google Play Music): 10 s (10 s) Count:2 0.0%
GTALK_CONN (Google Services): 10 s (10 s) Count:717 0.0%
Click to expand...
So google talk is 384s of my 5015s of awake time (nearly 8%) and it's set to not sign in AND it's frozen.

Ok, so it's probably not affecting battery that much, but still kind of bugs me that it's waking the phone up when I don't even use it and it's frozen!
 
So google talk is 384s of my 5015s of awake time (nearly 8%) and it's set to not sign in AND it's frozen.

Ok, so it's probably not affecting battery that much, but still kind of bugs me that it's waking the phone up when I don't even use it and it's frozen!
Click to expand...

8% of total wake time doesn't sound bad. But consider this:

google talk was nearly 28% of ALL partial wakelocks, while being "frozen". :cool:
 
Question 1. How long will your battery last from full charge to totaly dead with normal use? (No checking on bbs or any of that stuff)
Question 2. Have you thought that maybe bbs is causing the battery drain and not reporting itself? I mean, it IS monitoring EVERYTHING that could be affecting battery life.
Question 3. How often do you check your battery percentage? The more often you turn your screen on to check that, the more battery you drain.
 
I also get GTALK in my BBS logs even though I dont use it and have signed out of the app. I dont know why it is - i'm thinking it is used as a service for some other google app. maybe gmail. try disabling gmail sync (or other google sync types) and see if it makes a difference
 
there's some posts about this async gtalk wakelock on xda. basically, it's not documented anywhere, google won't tell us what's causing it. it's not related to gtalk specifically, even though gtalk is in the name. i've read that in addition to gtalk, people get rid of google maps and make sure the play store has update notifications off, and is not running in the background as it tend to do after boot.
 
You must log in or register to reply here.
Back
Top Bottom