Related
Is it normal to have 39% battery left with normal use after 8 hours 30 mins?
Running Opendesire 4.0 and newest radio
Just asking becasue i think it's running low fast..
OJ haven't died...
your lucky,
my battery is empty after 7 hours.
desire's battery is terrible. I couldn't manage to get 5h of using on it.
I am running the stock htc sense 2.2 rom, and my battery with moderate to heavy use would hold out for 24 hours. Something is badly wrong if you are getting less than 12. It was pretty much the same for me on 2.1 too. Getting 38+ hours now I'm using tasker.
Custom roms are supposed to be more efficient too. Have you looked to see what is using the power? A rouge app perhaps?
Sent from my HTC Desire using XDA App
I wrote this post the other day and just to update it i ended up getting 60 hours on one full charge which is pretty amazing. Some of the other posters had a go at me about turning mobile internet off and wifi off but who cares i got 60 HOURS!!!!
Hi Everyone,
I thought id share the amazing battery life im having, ive had it going for 48 hours so far and still got 45% of my battery still left, ill tell you all my set up and i wish you can get the same.
Installed LeeDroids rom (1.9a) which is absolutely amazing i must say, i love it.
Got the new radio 32.44.00.32u_5.09.05.30_2.
SetCPU running and have the normal standby on the phone at 642mhz and 245mhz when the screen is off.
I also have a task killer on set to kill most apps when the screen turns off and i have read about androids memory management but it makes me feel better when i run it and i personally think it helps.
Finally, and possibly the most important is an app called AutoKiller that interacts with androids internal memory management system and i have that set to ultimate.
I think thats it, and i have been using the phone averagely, and have turned off wifi and mobile internet and only use it when i need it.
Good luck everyone, hope this is helpful in someway.
I used to get 6 to 12 hours after I recovered my phone from being usb bricked. I'd missed a vital part of the recovery procedure! Now I get over 24 hours with heavy usage. I'm also using Setcpu.
Sent from my HTC Desire using telekinesis
Sorry bad English. I have rooted Desire + DeFrost and battery life is about 10-12 hour.
Chances are that anyone who is getting really bad battery life has a rogue app installed.
FWIW, I installed the Sky News app yesterday, and found, via Spare Parts, that it was stopping the phone from sleeping and creaming my battery life. I installed it, and things went back to normal.
Regards,
Dave
how to find which software etc is gulping the most battery?
There are two ways of doing this. The quickest is to open your dialer, and dial the following; *#*#4636#*#*
This code will open up a hidden menu. Select 'battery history'.
From here you can see what aspects of your phone are using which resources from selecting from the drop-down menu. Try looking at 'partial wake usage'. This will show up any rogue apps that are doing the phone from going to sleep. In fact, check them all out.
The second way is to download an app called 'spare parts' which gives you access to this hidden menu without using the dialer.
Hope this reveals the culprit!
Sent from my HTC Desire using XDA App
lhoang8500 said:
desire's battery is terrible. I couldn't manage to get 5h of using on it.
Click to expand...
Click to collapse
you are doing something very wrong if that is the case.
15h1m and i'm on 73%.
29 hours. 41%
I'm relatively new to android but my last two windows mobile based devices have had much longer battery life if I set the network mode to GSM only. Would this be the same for the desire or would it be better on WCDMA only?
GSM will only give you 2g bandwidth, but yes the battery will last longer. CDMA will give you 3g and HSDPA. I leave mine on this and get 36 hours typically.
Sent from my HTC Desire using XDA App
ukdj78 said:
I'm relatively new to android but my last two windows mobile based devices have had much longer battery life if I set the network mode to GSM only. Would this be the same for the desire or would it be better on WCDMA only?
Click to expand...
Click to collapse
The biggest issue with doing this is that you won't get simultaneous voice and data over the cellular network. If some tries to call you whilst your phone is syncing (and thus actively using data), the call will go straight to voicemail.
Regards,
Dave
2d 18h and on 16% with mobile internet on, sync on etc. But my usage is fairly low, about 20 mins voice, 10 texts approx, 20 mins 3G web browsing and about 10 mins of gaming.
On heavy use, it will last at least 24hrs - not bad, though I use setcpu to adjust max clock speed to about 700mhz and I have not notice any difference in terms of slow down.
Also I am not using any task killers apps.
EDIT: Forgot to mention that I use Timeriffic to automatically turn on airplane mode at night every night and off in the morning.
foxmeister said:
The biggest issue with doing this is that you won't get simultaneous voice and data over the cellular network. If some tries to call you whilst your phone is syncing (and thus actively using data), the call will go straight to voicemail.
Regards,
Dave
Click to expand...
Click to collapse
That not happen on my phone, FORTUNALLY!!! If my phone is on 2g and have the internet connection active and some tries to call me, the internet connection will stopped and i can get the call..Maybe depends on the operator? (anyway my desire is unbranded with stock froyo 2.2)
andQlimax said:
That not happen on my phone, FORTUNALLY!!! If my phone is on 2g and have the internet connection active and some tries to call me, the internet connection will stopped and i can get the call..Maybe depends on the operator? (anyway my desire is unbranded with stock froyo 2.2)
Click to expand...
Click to collapse
Yes - I probably should've mentioned that this is carrier dependent, but most carriers don't seem to be implement it.
Regards,
Dave
Does using wifi drain the battery? Is it better than using the actual 3G or 4G?
Sent from my HTC Vision using XDA App
I'm sure someone has a way more technical answer but I would think not. I have no issues with drainage on wifi, as on 2g its on the network constantly and not continually searching for towers.
Sent from my HTC Vision using XDA App
jeremyt727 said:
Does using wifi drain the battery? Is it better than using the actual 3G or 4G?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
If you are connected to a wifi network, it saved much more battery than using 3 or 4g. However, if you leave wifi on but don't connect to a network, it will drain battery
Sent from a truly Epic phone and a transparent XDA app
ok cool thanks alot man. Idk when I'm home I just like using wifi better, correct me if I'm wrong but it seems faster. Thanks again
Sent from my HTC Vision using XDA App
Turning on anything more than necessary will kill your battery faster. Not always by a lot but everything does and wifi wouldn't always be faster because it depends on the wifi's local area connection. Best way to save battery is to go in settings/applications/manage applications the force close anything you don't need running. Make sure you know what it is you're closing or you could run into some problems. If you end up killing a system app and it won't reopen itself, its nothing a reboot won't fix.
dietotherhythm said:
Turning on anything more than necessary will kill your battery faster. Not always by a lot but everything does and wifi wouldn't always be faster because it depends on the wifi's local area connection. Best way to save battery is to go in settings/applications/manage applications the force close anything you don't need running. Make sure you know what it is you're closing or you could run into some problems. If you end up killing a system app and it won't reopen itself, its nothing a reboot won't fix.
Click to expand...
Click to collapse
DO NOT DO THIS.
Android has its own automatic task management system, and its best if you just let it do what it does best: manage on its own.
Sent from my T-Mobile G2 running Cyanogenmod.
Well gee I do it all the time and it works fine. If it wasn't intended to be used I don't think it would come without root permissions and anyone who isn't an idiot will realize that force closing android system will cause problems. But if you wanna suggest a task manager that doesn't actually kill apps and adds some bloat ware, be my guest.
dietotherhythm said:
Well gee I do it all the time and it works fine. If it wasn't intended to be used I don't think it would come without root permissions and anyone who isn't an idiot will realize that force closing android system will cause problems. But if you wanna suggest a task manager that doesn't actually kill apps and adds some bloat ware, be my guest.
Click to expand...
Click to collapse
He's not going to recommend another task manager/killer, because Android already does it by itself. Plus, killing a task that is not finished just causes it to respawn. Task killers are unnecessary, and may actually hurt performance and battery life.
Its explained here: http://forum.xda-developers.com/showthread.php?t=849974&highlight=task+killer
I agree that it's best to let Android clean it's own house normally, however I'm getting a little bit jarred off with certain apps starting themselves up at boot-time.
Paypal app for some reason has installed a service on my phone, despite the fact I've never even logged into it and I can't see why it would need a service running all the time.
Also since the latest Google Maps upgrade there seems to be something under my running tasks called Rate Places. I've not used the check-in service on GMaps at all, nor will I ever.
As well as this, since I've been running a modded CM ROM (SparksMod Extra Hot Sauce) then I constantly have Wi-Fi Calling running - again this is useless to me cos I'm not on TMob US.
Any suggestions for a decent app which can stop all these things running before they ever start, and keep them stopped?
setspeed said:
I agree that it's best to let Android clean it's own house normally, however I'm getting a little bit jarred off with certain apps starting themselves up at boot-time.
Paypal app for some reason has installed a service on my phone, despite the fact I've never even logged into it and I can't see why it would need a service running all the time.
Also since the latest Google Maps upgrade there seems to be something under my running tasks called Rate Places. I've not used the check-in service on GMaps at all, nor will I ever.
As well as this, since I've been running a modded CM ROM (SparksMod Extra Hot Sauce) then I constantly have Wi-Fi Calling running - again this is useless to me cos I'm not on TMob US.
Any suggestions for a decent app which can stop all these things running before they ever start, and keep them stopped?
Click to expand...
Click to collapse
Try "Autorun Manager"
I use it, but SOME apps will auto-restart. I think you need the Pay version of Autorun Manager to prevent those from re-launching.
I use the free version, and it gets rid of some of the problem.
WiFi is definitely causing massive battery drain on my G2 with CM6.1.1. I leave it on at night, and if I have 50% when I go to sleep, I'm down to 3% in the morning. Without doing anything.
I'm not quite sure why this is happening, but it is, and it sucks. I can't go back on 3G/4G right now because I'm at just about 4.8GB, and I don't want to go over my 5GB soft cap.
I wish I knew why WiFi was causing such battery drain...
Do you have anything updating automatically (Email, facebook, etc)? That would be my best guess. I leave wifi on when I'm at home and it isn't that bad at all. Also, I'm sure theres an app out there to let you see what is using the wifi for updates and such. I just don't know of one off the top of my head. I have an app like that for 3G data but it doesn't do wifi.
I just went through every one of my apps to make sure that nothing is set to sync, except Google Voice and Email. My battery is at 50% right now, so we'll see what it's at tomorrow morning.
As you can see from the screenshot, WiFi is using quite a bit of battery. I'm not sure why, but hopefully soon (after some testing) I'll have my answer.
Sent from my HTC Vision using Tapatalk
Yup, 2 nights in a row, my battery has gone from 40% to dead, simply from sitting on my night stand. I wonder if this is why T-Mobile discontinued the G2... because they knew it would have battery issues, and they didn't want to deal with serving warranties? Hmmm...
Its a bit of a leap of logic to link your personal battery issue with T-Mob discontinuing the phone. T-Mob has a good number of Android phones coming out in the near future, with T-Mob really ramping up their support of Android devices. So its been very reasonably speculated that they are discontinuing the G2 in order to make room in their lineup (and stockrooms, etc.) for the new phones.
I get a full day of moderate usage on my Vision, and can get close to 2 days with low usage. That's very typical for a modern smartphone. I usually get in the range of 2-3% battery drain per hour when the phone is idle. And that's with WiFi always on (even when not connected to a WiFi network) and auto sync of Gmail and HTC stock and weather apps. You haven't mentioned how long "overnight" is exactly, but I'll assume 8 hours or so. So your phone draining from 40% to dead overnight seems unusual. WiFi typically uses less battery then the cell data network, when WiFi is available. I suspect there is something else going on, besides just being on WiFi. If the cell reception is dodgey in your area (or fringe 3G reception), this might run the battery down (even if you are on WiFi) as the phone is constantly searching for signal. Or your radio may be mismatched to your custom ROM. Or you may just have a bad battery. Also, was the battery drain any different when you were on the stock or other custom ROMs? I personally haven't witnessed the battery drain to be significantly different across the ROMs I've tried. But that seems to vary, as there often seem to be people complaining about this or that ROM causing more battery drain.
The reason I thought it might be a hardware defect issue is that my wife and I got G2's at the same time. I rooted mine and have been running CM6.1.1 for a few months now, and my wife has kept hers stock. However, the battery issue hit both our phones at almost the exact same time.
It sounds ridiculous, but conspiracy theories are fun to play with. The fact that I've been rooted so long, and it JUST happened weirds me out. Add my wife's phone to the equation, and it's even weirder. I kept my phone on WiFi and 2G networks only last night (yeah, about 8 hours), and the exact same thing happened.
Maybe I should just get a new battery, I don't know. But I do religiously delete apps I don't use and make sure the ones I do use are syncing as minimally as possible.
Anyone else experiencing this? I've had this going on for about 5 days now and for the life of me couldn't figure it out. I notice that whether it's my 3G or my WiFi connection, my phone was continuously streaming data. If I'm at work where I don't have WiFi activated, my 3G is on non-stop streaming, making matters worse, sucking the life out of my battery. Of course my phone was running warm. Imagine that!
I know there's got to be something running in the background and I think I nailed it down to Google's email app. There wasn't any huge file to upload/download which I think could have caused this to happen.
Luckily I may have found a remedy. Microsoft has finally gotten around to updating their Hotmail software for ICS. It's been over 30 mins since the Hotmail app install and the data transfer thingy doesn't seem to be so intense now. In fact it's down to nil.
Strange.
Hotmail.. ಠ_ಠ
yea, i dont think its hotmail.
go to data usage...thast why its there..you can see which app is taking the most data...you can also stop the background data for that app
Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
Update 2012-10-02:
OK, I have eliminated my firewall from the equation: obviously I can't necessarily just whack the work's firewall without consequences. Nothing's blocked, and all services on the phone seem to work.
As for other devices: I dug up my old Nexus One (Gingerbread, stock), and upgraded my Transformer Prime to Jelly Bean. Both do not show the error in logcat, and neither have the battery drain issue. Just for kicks, I checked the version of the Google Services Framework on all three:
Samsung Galaxy Nexus: 4.1.1-398337
ASUS Transformer Prime: 4.1.1-438695
HTC Nexus One: 2.3.6
Wanna bet there's a bug in 4.1.1-398337 that got fixed in 4.1.1-438695?
Further update:
I also tried the following with no success:
Delete app data for Google Services Framework (NOT RECOMMENDED!)
Remove Google accounts from the phone.
Re-add Google accounts to the phone.
Update: 2012-10-04
I think I found a workaround. It looks like it's a domino effect thingy that happens here:
1) I've got a Netgear N600 ADSL/Wifi router at home. On my 2.4GHz radio, I set up two access points: one for my stuff and one for guests. I made sure to delete the guest account from all my Wifi equipment to make sure there's no "fighting" or "flapping".
2) It appears that the phone ignores the Wifi-'stay connected while sleeping' setting, or the radio is broken. When the phone goes to sleep, it disconnects from Wifi.
3) When the phone disconnects from wifi, the Google Services Framework lose connection: this causes the phone to wake up.
4) When the phone wakes up, Wifi gets re-established. This makes Google re-connect.
5) The phone goes back to sleep and we return to step #2.
This causes a LOT of wakeups, lost connections and other crap. Since the phone doesn't lose connection when it's awake, it's fricken difficult to debug. Also, it's NOT a signal quality issue. My phone can be right next to the access point and it wouldn't help.
So, could you guys try different access point settings at home? I've heard WMM, QoS and some of the protocols could cause the Galaxy Nexus's radio in Jelly Bean to go a bit wonky.
-- Jan Gutter
jangutter said:
Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
-- Jan Gutter
Click to expand...
Click to collapse
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?
Petrovski80 said:
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?
Click to expand...
Click to collapse
Nope, I checked that: there's no firewall. At work there is, but it doesn't affect my phone (services are not affected visibly). Google Talk works fine in both situations.
any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!
Exactly the same
cricka15 said:
any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!
Click to expand...
Click to collapse
Does anyone have solved this.. i have got exactly the same situation as Jan. No trouble at work but only at home.
Not affecting ASUS Transformer Prime
Nothing new here, except I also cross-checked with my ASUS Transformer Prime. There's no drain on it, and also no errors in logcat about GTalkService.
I'll post an update once I've checked my trusty old Nexus One out of storage, that'll happen next week, though.
Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint
sgtlange said:
Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint
Click to expand...
Click to collapse
Just take note: in general Wifi uses a LOT less battery than 3G. A better test might be to disable Wifi AND sync.
Jan
some decent insightful ideas here. My S3 on official stock based custom has bad drain over wifi. My google services framework version is the 4.1.1-438695 which isn't affected in your case so it's not that.
Better battery stats at first put google maps as the wakelock so I realised it's location service was left on so I turned that off. Then BBS varies and shows different apps and what not causing wakelocks but the drain remains the same.
My router is an Asus with custom linux firmware Tomato with a robust plethora of functions. I updated it yesterday and put the settings back closer to default. I'll have to try disabling WMM and QoS settings as their both already on at the moment. Also the kernel developer i'm on to quote: "Made a change in wifi offload filtering to deny muticast packets but allow multicast DNS packets."
After leaving wifi on last night the drain still remains at about 10% per 3 hours. Compared to before it used to be almost 15% per 3 hours. BBS doesn't show wlan_rx_wake as the top wakelock as most common before as that's down to running for 8 minutes in 9 hours rather than the top around 45 minutes. Instead battery-monitor is the top at a little over half an hour in the 9 hours. Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
Infy_AsiX said:
Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
Click to expand...
Click to collapse
Have you tried disabling the WiFi Power Save Mode on the S3? From this article:
http://www.s3forums.com/forum/galaxy-s3-general-discussion/1329-wifi-tip.html
1. Open up the Galaxy S3 phone dialer
2. Dial *#0011#
3. Look for the “ServiceMode” screen and press the left menu button
4. Select “WiFi”
5. You should see that the “WiFi Power Save Mode” button is “ON” – turn it “OFF”'
My colleagues with the same phone has serious battery drain until they use that.
Infy_AsiX said:
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
Click to expand...
Click to collapse
I seem to recall that the Google framework sends/receives a keep-alive packet once every hour or so. LOTS of stuff in the Android framework keep TCP connections open from the server side because otherwise the service provider just kills them. Blame stateful firewalls.
What could be happening here is that the WiFi chip offloads a number of these functions from the main CPU: i.e. it's got a simple TCP offload stack that just queues data for the main CPU to wake up. If the WiFi chip receives a keep-alive TCP packet with no payload, it doesn't bother to wake up the CPU and just absorbs it. If the WiFi chip goes to sleep, rather, it never receives these, the connection dies and the CPU needs to wake up on timeout and re-establish everything (eating battery in the process). It's paradoxically cheaper to keep the WiFi chip running on full power, than to let it go to sleep. This is pure speculation, and only one of many scenarios that might fit the facts.
The S3 has the *option* to change the WiFi sleep-mode from aggressive (default) to a value that lets the entire system use less battery. The Galaxy Nexus doesn't: which means that it may, or may not have the sleep-mode built in. In any case, it seems my router can remotely trigger disconnects when the main CPU is off, and by switching settings on it, I managed to perform a workaround. Unfortunately the Galaxy Nexus (on Jelly Bean, at least) seems to have a serious bug in this respect, and other people are not so lucky: http://code.google.com/p/android/issues/detail?id=35352
It seems that the core issue (WiFi disconnect), causes a knock-on effect, raising Google Services Framework, Android OS and potentially anything that syncs's battery profile.
Jan
Getting good drain now 1% an hour compared to 3%. Seems setting WMM to auto rather than enabled in tomato fixed it. The night before I had it disabled as well as QoS and it was bad as well. I will test further to be certain what's the scenario.
I've got a second S3 that's been suffering as well. Having two to test makes testing much faster. The service menu power save mode off didn't help. It caused strange disconnects with WMM in all states. S3 wifi menu would state poor connection and wouldn't reconnect. Note the S3 already has strange disconnects to begin with I find but in this case it sometimes wouldn't reconnect. Also restarting the phone resets the power save mode to enabled.
Can't find any information on a difference between enabled and auto in tomato WMM. I'll be sure to keep testing.
Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
New Google Services Framework
Hey guys,
looks like Google Services Framework got a version bump on the latest Galaxy Nexus update: it's now listed as version 4.1.2-485486
This is for JZO54K (4.1.2).
It could be that they've fixed the knock-on effect (but the core issue is likely the same, since the radio code is apparently exactly the same).
Jan
I have this same wakelock on my evo 4g lte. Same log error exactly. Only on my works wifi. Problem is eliminated when running a Vpn on the phone. Only caveat Is all the free vpn services seem to disconnect after a period of inactivity.
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
Rawi666 said:
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
Click to expand...
Click to collapse
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium
SpinTX said:
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Try lowering this value to 10 or 8 and see if it helps.
Rawi666 said:
Try lowering this value to 10 or 8 and see if it helps.
Click to expand...
Click to collapse
Thanks, will give it a shot. Also, because of your post, I discovered that toggling wifi on and off stops Google Services from draining. It will still drain, if your wifi is set to turn off, when the device sleeps. I really think you hit the nail on the head, discovering the source of the problem. It's an issue I have been trying to fix for a long time and your post at least got me to toggling the drain. So thanks again!
Sent from my SGH-T999 using xda premium
Would love to he root cause of this... I had the same problem on my s3 and now on the s4.with and without custom roms etc. The problem only is work, and I'm putting it down to some service that the work firewall or something blocks... Only solution I've come up with is turning off the wifi when I'm at work.. Else I get in excess of 15min /hour of wakelock.
All apps etc. Up to date, sync on/off, no difference, all "location" settings turned off.
I give up.
Wifi signal strength!
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal
keltickal said:
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal
Click to expand...
Click to collapse
A friend with the nexus 4 and same problem told me to try disabling Google hangouts (formally talk).. Apparently it keeps refreshing itself once ur signed in (and it signs in automatically)... Will experiment tomorrow at work where I get the problem.
Sent from my GT-I9500 using xda premium
Hello,
I got an s4 mini about a month or two ago and I had been having a lot of issues. at first I couldn't send mms (noticed this day 1 with the phone) then later on my bluetooth stopped working. I rooted the phone, this is when i lost bluetooth, then about a week later i got the play store connection error. At the time i was using superbeam and apps from other sources as a work around but then adaway was telling me it couldn't reach any sources and i couldn't navigate past google on the internet. This is when I decided to just update my firmware, this solved my internet and playstore connection problem and even mms was working for the first time!(never checked about bluetooth, still using beam). But I still wanted root access for adaway so i followed this guide to install CWM and CM11.
http://forum.xda-developers.com/showthread.php?t=2696260
I was successful and everything is still working well, i can make calls and texts, but for some reason my battery is draining in about half the time it was before, When i look at my locksreen on the bottom most of the time it says "emergency calls only (ROGERS)". Looking at the battery under setting cell standby is right at the top of the list usually at about 34% consumption with 69% time without a signal. So obviously this is where the battery drain is coming from, the weird part is if i go to make a call or send a text or something it picks the signal up as if it had always been there..? I have great cell coverage but the phone is pretending i don't 70% of the time.
does anyone know whats going on with my phone?
Sorry for the long story but I am just looking for some help on this confusing issue, the xd forums seems pretty friendly, please prove me right!