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

[SOLVED]GTALK_ASYNC_CONN Wakelock and some Battery Saving Tips

J

Jeepmaster

Well-Known Member
I thought I'd share my finding which finally got rid of the GTALK wakelock that doesn't seem to go away. Thanks to TEAM KERNELIZERS for their post on XDA which is where this fix came from http://forum.xda-developers.com/showthread.php?p=39425794 see post #2.

So here the problem I've been having for ever. From BetterBatteryStats, it showed that I have a wakelock from GTALK_ASYNC-CONN-com.google.andriod.gsf It is related to GoogleTalk which I do not use what so ever. I've disabled and freezed anything that's remotely resemble GTALK, but the wakelock just keeps coming back. My DriodWall is already blocking everything GTALK related.
On a regular day, I was having 150+ counts of wakelocks. Even though it doesn't use that much battery (about 1%), but still if I don't use it, it shouldn't even be there. I've searched everywhere online and no one seem to know how to stop it. Until I saw a thread by TEAM KERNELIZERS and saw they have tons of battery saving tips and one of them was about how to disable the GTALK wakelock.

Basically, the instruction asks to add a line that reads "0.0.0.0 mtalk.google.com" to the host file under /etc/hosts
But because I use AdAway and it updates the host file constantly, it will get overridden every time. So instead of editing the host file manually, inside AdAway I have an option to add my own list. So I just added "mtalk.google.com" to it and it blocks it like an Ad.

Since then, I have 0 count on GTALK wakelock and its using 0.0% battery. YAY!!!!! FINALLY!!!!

I hope you guys will find this helpful for those that have the same problem.

On that XDA thread, there are many more tips on battery saving and modding with KT747 kernel too...which I think is the best battery saving kernel around.
 
I've just made an account on this site to say THANK YOU! I had this wakelock that was making Google Services eat 44% of my battery, and BBS told me it was 'GTALK_ASYNC_CONN'. After adding that exception in AdAway (which I was also using), it's all fixed!

You're a genius!
 
I'm glad this helps some of you guys. Just sharing the knowledge that's all. As long as someone find it useful, then I didn't wasted my time typing it out. :D
 
While this seems to get rid of the wakelock, it does seem to also remove functionality. I noticed that my network icon stayed grey instead of blue, which means my phone was not connected to google services and was not getting push notifications. I also noticed that seekdroid couldn't locate my phone anymore. I'm not sure about any other loss of functionality, but this does not seem like a good fix :/
 
I have read the:
"0.0.0.0 mtalk.google.com" hack in several places, but, for instance, PushBullet doesn't work any more, and I suspect Whatsapp notifications are lost as well....
Has anybody checked the "side effects" of this hack?
Too bad, because if I solved this wakelock, I would have a wonderfully working ViperS 5.2.0...

gio
 
You must log in or register to reply here.
Back
Top Bottom