[Q] Phone/CPU gets hot after ICS upgrade - Galaxy S II Q&A, Help & Troubleshooting

Hi.
Havnt seen this problem described here so ill just ask and hope to be shown in the right direction.
When i, either through KIES or Odin, upgrade my phone to ICS (4.0.3 XXLPQ) it gets quite varm by just sitting at the homescreen doing nothing, I have tried both antutut's and SetCPU's apps to check the CPU-speed and it is almost constantly at 1000-1200Mhz and it is just for a few short seconds now and then that it drops to maybe 800 or 500Mhz just to get back up to 1200Mhz again.
I have wiped and cleared everything before upgrading but thing helps.
When i restore my 2.3.6 backup eberything works fine and the CPU is steady at about 100-200Mhz when i am not doing anything with the phone except having for example SetCPU open, I have also very very very rarely had any reboots or other strange things with 2.3.6 (or any of the previous versions of GB), so wouldnt expect the phone to be faulty in its hardware.
Sorry for the wall of text, but does anyone have any ideas on what could be wrong, or is it a trip to a service center that is needed for my phone? :S
I have emailed Samsung sweden about this but as i am quite sure i will get a generic response I thought i should ask here instead

I have also been getting that problem. No clue why.

unselect internet sync in google sync account.....
Sent from my GT-I9100

I've read from another thread that it can warm up because of new swype always trying to download some languages.
Sent from my GT-I9100 using XDA

karthik.shreeram said:
unselect internet sync in google sync account.....
Sent from my GT-I9100
Click to expand...
Click to collapse
Lol, what does Sync Internet Sync?
Mine was off.

in GB, it was hot. And at ICS cool device

I have the same problem and unfortunately it causes extreme battery drain. Like 70% in about 5 hours while the phone is idle.
This sucks.

Swype was causing battery drain for me after ICS upgrade. After force closing it the drain has ended and S2 does not get hot anymore. Swype was shown using 50% of battery in Settings - Battery.

Ask samsung for kernel sources
Sent from my GT-I9100 using xda premium

Install antutu benchmank and check what is the CPU frequency.

As far as I know from all the previous betas ICS takes ages to do the media scan and hence it warms up. You will know its doing it when trying to use the camera or open the gallery. It will say media scan running.
If media scan has finished but its still heating up I would recommend a factory reset.
Sent from my GT-I9100 using xda premium

girishr said:
Install antutu benchmank and check what is the CPU frequency.
Click to expand...
Click to collapse
It's always at 1200 Mhz. I can't force close Swype because it isn't even open on my device. Should I try a factory reset?

sxi200 said:
As far as I know from all the previous betas ICS takes ages to do the media scan and hence it warms up. You will know its doing it when trying to use the camera or open the gallery. It will say media scan running.
If media scan has finished but its still heating up I would recommend a factory reset.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Inoticed this also the fifth time i reflashed, I think i should wipe my phone, format SD-card and internal memory.
Sitting in meetings all day today (even right now) so I will do some testing when i get home.
Other problem i got when i had ICS and it was hot (scanning), my Phone locked up when i got a call... Saw some other bugs and problems, so maybe I should wait for the next release....

Related

[Q-ICS] Facebook too much CPU activity?

Since I'm on ICS I have this strange problem with the official FB client.
As Soon as i start FB my processor gets pumped up to the maximum of 1ghz. Even when i click the Home Button and start up Voltage Control i can see the processor is at max.
Only when i close FB (with task manager or long press back key on CM9) the processor goes down to 200mhz and stays there...
effect : as soon as i start FB and don't quit it right my battery will be drained in a short time..
Since the first ICS release I am googling this problem but can't find any information about this. Now I'm a little bit fed up with it, thats why i'm posting it here...does anyone else recognize this? is there a workaround?
thanks for the help...
check your battery info,get cpuspy to see what speed your cpu has been going at and the deepsleep and betterbatterystats for wakelocks etc
this guy has similar issue
http://forum.xda-developers.com/showthread.php?t=1571518
i already checked with all mentioned tools.
strange thing is there is no wakelock... it's only when screen is on but application is in background.
i have this problem on different ICS Roms. at the moment i am on cm9 and it is still present. when i check with "top" in terminal i can see that facebook.katana is at the top keeping the cpu pretty busy.
with samsung roms and the original samsung task manager i can see that it's always using over 50% cpu power.
i tried older versions. tried deinstalling. nothing helps.
i just dont know what it is doing in the background. cpuspy shows me that the cpu is mostly in 1ghz and deepsleep.
edit: i double checked and its also killing deepsleep. sometimes it enters sometimes not...
pmcee said:
Since I'm on ICS I have this strange problem with the official FB client.
As Soon as i start FB my processor gets pumped up to the maximum of 1ghz. Even when i click the Home Button and start up Voltage Control i can see the processor is at max.
Only when i close FB (with task manager or long press back key on CM9) the processor goes down to 200mhz and stays there...
effect : as soon as i start FB and don't quit it right my battery will be drained in a short time..
Since the first ICS release I am googling this problem but can't find any information about this. Now I'm a little bit fed up with it, thats why i'm posting it here...does anyone else recognize this? is there a workaround?
thanks for the help...
Click to expand...
Click to collapse
Same here. I've Galaxy S2 and since update to ICS official firmware have i have this problem. I noticed that all rom that have as baseline official Samsung ICS have this problem, while other (e.g. CyanoMod 9) don't have. The only fix is to kill application from task manager.
Which is your device?
NothFlo said:
Same here. I've Galaxy S2 and since update to ICS official firmware have i have this problem. I noticed that all rom that have as baseline official Samsung ICS have this problem, while other (e.g. CyanoMod 9) don't have. The only fix is to kill application from task manager.
Which is your device?
Click to expand...
Click to collapse
It happens to me on cm9 also... Every ICS Rom.
So No one has a solution for US?
Just to let you guys know that this also happens on my Nexus S with ICS 4.0.4 stock
In fact it happened also with Gingerbread... it started happening when Facebook made a major app overhaul to what is currently the new "user experience" for the past 4-5 months or so... that's when Watchdog which I have installed suddenly started complaining
Sorry for digging out this bit older thread, but have you found a solution yet ? I got the same problem since i changed to ics roms - first sammy leaks, then official, now nightlies. Tried wiping cache, dalvik, userdata, reinstalled app, ... to no effort.
Thinking about coding a facebook-killer widget. Take a look on this screens, 2 hours of cpu time for nothing...
Sent from my GT-I9100 using xda premium
I just use Watchdog what normally complains about Facebook a few minutes after I stop using it. Then I just kill the process from within Watchdog.
Using the browser is fine though.. however some things don't work so well in the mobile browser version.
To me this problem is quite symptomatic however from what I read on the internet it doesn't happen all the time.. even sometimes for me it doesn't stay clogging the cpu but most of the times it does.
I guess they will fix it one day but I wouldn't hold my breath that it will be soon. I read that on the iPhone the way they designed the app is pretty bad (it's sort of a skin over the actual mobile website). For Android it might be the same..
That the facebook devs are coding big BS (sorry) is really known.
Can you provide me a link to the google play site of Watchdog ? Too many results, i don't know which one... thanks
Sent from my GT-I9100 using xda premium
Here! This is the one I use
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite
Thanks.
Which modem do you use ? I am on XXLPS, and afaik with XXLPQ i did not have the problem - will try at home
Edit: tried, the same with lpq...
Sent from my GT-I9100 using xda premium
I'm using the XXLA2 radio that came with the yakju update. But I got the same problem with the XXKK6 yakjuxw radio
smells more like programmer error than phone configuration..
since i am using foxhound rom (sniper wolf), the facebook app (and same for all other apps that dont automatically close) is automatically ended when closed with the back button...
Seems that it's a problem with the official ICS ROMs. Try Friendcaster and see if that's any better.
drizzle1 said:
since i am using foxhound rom (sniper wolf), the facebook app (and same for all other apps that dont automatically close) is automatically ended when closed with the back button...
Click to expand...
Click to collapse
Theres a funtion which kills a process if you hold the back key.
i360* said:
Theres a funtion which kills a process if you hold the back key.
Click to expand...
Click to collapse
even by closing with a short press on the back button it will end the process
i uninstalled facebook for this
friends caster is A LOT better than facebook app
personally I didn't like Friendcaster. It was smoother in operation that Facebook's official app but it had some quirks (now can't remember them but there were a few things you couldn't do as opposed to FB's official app). But what stopped me from using it was the extended awake times I was getting even without automatic refreshes set up.
Haven't got a single problem
Sent from my GT-I9100 using Tapatalk 2

Phone acting extremely weird..

Hello,
since a few days my Xperia S acts really weird. For example when typing right now it will freeze from time to time and i will have to wait 5 seconds to type.. Or when going back from an app to the Homescreen it will sometimes vibrate twice and open the taskmanager.. I already tried a factory reset but that doesnt help.. Any suggestions?
Sent from my LT26i using xda app-developers app
I have never seen this issue before, but i'm thinking in the lines of some kind of app that is using your cpu for the full 100% or so.
Does it perhaps occur after you have installed a specific app?
I'm not sure about this at all, but i'm just trying to eliminate all possibilities.
Ive installed 2 apps after the factory reset, XDA app and whatsapp.. :/
Those apps shouldn't really give any issues.
Are you running the stock GB/ICS firmware and a stock kernel as well?
yeah everything's on stock. nothing modifyed.
I think what you could try is to flash a stock GB/ICS firmware through the flashtool with a full data wipe and all that.
Perhaps it's useful to format the storage memory of your phone too, just to be sure.
Again, i'm not sure if any of this will work but it's worth a try.
If this doesn't help, i think it's best for you to return the handset to the shop.

Please help! My Galaxy Note keeps randomly shutting off :(

Experienced this just a couple of days ago My screen will go blank, like it went to sleep but what actually happened was it just simply shut off! I installed two logcat applications, but I don't know jack about reading logs I want to know what causes these shutdowns The latest ones happened between 6:32-6:33AM and 6:54-6:55AM (it's 7:26AM now, my time). Please help
iampoch said:
Experienced this just a couple of days ago My screen will go blank, like it went to sleep but what actually happened was it just simply shut off! I installed two logcat applications, but I don't know jack about reading logs I want to know what causes these shutdowns The latest ones happened between 6:32-6:33AM and 6:54-6:55AM (it's 7:26AM now, my time). Please help
Click to expand...
Click to collapse
check if you've installed any apps that prompt the auto shut-off of your phone
previously I had this problem before by then I realized it's due to the installation of one of my fault apps.
felixtom said:
check if you've installed any apps that prompt the auto shut-off of your phone
previously I had this problem before by then I realized it's due to the installation of one of my fault apps.
Click to expand...
Click to collapse
Really hate to sound like a total noob, but how do I do that?
iampoch said:
Really hate to sound like a total noob, but how do I do that?
Click to expand...
Click to collapse
first of all,i think this is happening because of any new app,try to remember when it was started(maybe that time you installed any app and now that app shutting down mobile? or just go to task manger and clear each app that was running and also clean memory. if problem is gone and its occur again after rebooting mobile its maybe a Rom Bug,you need to change your Rom,but before doing that try to clear apps through task manger. and see what happens
i hope that helps you
Well first of all ...
Are you rooted? What is your Rom/kernel?
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Thanks for the replies guys ok, here are some more info and observations.
I was originally using CyanogenMod 9.1 when this happened. At first, I tried wiping cache and dalvik cache. But it was still the same. After a few more shut downs, it got worse. It got to the point that it shuts down after the boot animation. So, I used Clockwork Mod to revert me back to rooted stock ROM. It's not as worse as CM9, but I still get shut down. Now, here are the observations I made:
1. This only happens when my phone is unplugged. It works fine otherwise.
2. This consistently happens when I connect to the Internet, for example via a browser, didn't matter whether it was Chrome or Dolphin. Offline reading via RSS or Pocket is fine. I opened FB unplugged and I got shut down as well, so I guess it's safe to say that connecting to the Internet triggers it. When accessing the Internet while unplugged, shutdown is immediate and imminent. Plugged, I can surf just fine.
3. It also gets triggered when I play a game, but my shutting down is not immediate, unlike the one above. I am playing only one game at the moment (Great Big War Game). And I am able to play a long while before getting shut down (around 30 mins)
It wasn't like this a couple of days ago, and I didn't install anything new outside Google Play updates, this is not counting the two logcat apps I installed this morning to try to diagnose the problem.
Is there a way for me to find out what's wrong via the logcat?
Sent from my GT-N7000 using Tapatalk 2
for your Help
iampoch said:
Thanks for the replies guys ok, here are some more info and observations.
I was originally using CyanogenMod 9.1 when this happened. At first, I tried wiping cache and dalvik cache. But it was still the same. After a few more shut downs, it got worse. It got to the point that it shuts down after the boot animation. So, I used Clockwork Mod to revert me back to rooted stock ROM. It's not as worse as CM9, but I still get shut down. Now, here are the observations I made:
1. This only happens when my phone is unplugged. It works fine otherwise.
2. This consistently happens when I connect to the Internet, for example via a browser, didn't matter whether it was Chrome or Dolphin. Offline reading via RSS or Pocket is fine. I opened FB unplugged and I got shut down as well, so I guess it's safe to say that connecting to the Internet triggers it. When accessing the Internet while unplugged, shutdown is immediate and imminent. Plugged, I can surf just fine.
3. It also gets triggered when I play a game, but my shutting down is not immediate, unlike the one above. I am playing only one game at the moment (Great Big War Game). And I am able to play a long while before getting shut down (around 30 mins)
It wasn't like this a couple of days ago, and I didn't install anything new outside Google Play updates, this is not counting the two logcat apps I installed this morning to try to diagnose the problem.
Is there a way for me to find out what's wrong via the logcat?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
maybe its a cache problem of your Browser,so try to clear cache of your Browser and if its not working Flash a new stable Rom( i recommend you Sweet Rom,find it on XDA,its very stable and smooth)
and flash that rom with Hydracore kernel.
hope that helps you
have a nice day
Hi thanks for the additional info. It seems that you have the issue persisting on a stock Rom?
Have you tried to wipe on a safe kernel (if on ics)?
Do disable any overclocking or any scripts.
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Guys, just a quick update. I sent it off to the service center (reverted to stock and hid all traces of being rooted). They reflashed the phone (they say it's their standard practice to do that before considering hardware defects) but the problem still didn't go away. So, I think my issue is hardware-related
This problem is not software related. It is most definitely hardware. The phone is flawed and shuts off on it's own under various conditions, all hardware related. I am not able to post externally due to not having enough posts yet. However, I have had the same issue on 3 Galaxy Note 2's from Verizon. I made a video that shows exactly what is going on and posted it on the following website...
wwwDOTgalaxynote2shutsoffDOTcom
You will have to paste that link in to a new browser and replace the DOTs accordingly to get to it, but once you see the video, you will be enlightened. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
Take a look at the video I made here if you can't get to that site: http://www.youtube.com/watch?v=SjLn2yikYnI

S3 REALLY slow

I have just bought an S3 and I am actually quite disappointed in it's performance.
I have an S2 (Running stock ICS) and my S3 (Running stock JB) is quite noticeably slower, with terrible lag.
I am just wondering if this is normal, surely this should out perform an S2?
The 2 main area where it is considerably slower is opening up my contacts and MMS app.
From clicking the contacts icon it takes about 2 seconds to actually load the contacts, and the MMS app takes about the same time to load.
Also when opening my app drawer it is buggy and laggy when scrolling through.
I notice that I also have little to no free RAM, yes I know how android works and how it utilises RAM but it doesn't seem right to me.
Anyone else having this problem?
I'm also running JB which should be smoother than ICS!
The firmware version I'm using is XXDLJ4
Any advice would be greatly appreciated!
you are either doing something wrong or holding a faulty handset, apart from the delay in opening contacts app after heavy usage, s3 will absolutely smoke s2.
bala_gamer said:
you are either doing something wrong or holding a faulty handset, apart from the delay in opening contacts app after heavy usage, s3 will absolutely smoke s2.
Click to expand...
Click to collapse
Thanks for such a prompt reply!!
It totally smokes my S2 in benchmark tests but in real usage it doesn't.
Is there any way of checking if it's faulty?
Like maybe an app that checks all 4 cores are running properly and GPU is functioning properly?
Obagleyfreer said:
Thanks for such a prompt reply!!
It totally smokes my S2 in benchmark tests but in real usage it doesn't.
Is there any way of checking if it's faulty?
Like maybe an app that checks all 4 cores are running properly and GPU is functioning properly?
Click to expand...
Click to collapse
try disabling media service, its one among the reasons for possible lag, disable power saving mode if enabled
turn off Facebook sync and ripple effect
this helped me to get free ram
Sent from my GT-I9300 using xda premium
mine is the same it just feels slow and laggy there's a one x in the house as well and it blows away the s3.
my s3 running ics was unusable jb helped but did not fix the phone completely I am very disappointed with it, but also stuck with it.
:crying:
2531prasad said:
turn off Facebook sync and ripple effect
this helped me to get free ram
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I don't have Facebook on my phone and I turned off the ripple effect as soon as I turned it on lol
Im shocked. How is this possible?? I bought my phone 10days ago, till now I have not seen any lag anywhere except for the contacts and phone. It will be fixed though. Moreover it fly's with the JB update, I love scrolling through the screens its damn smooth.
I doubt if you got the correct handset . Surely something is wrong. Was it like this from the first day???
IntenseTorture said:
Im shocked. How is this possible?? I bought my phone 10days ago, till now I have not seen any lag anywhere except for the contacts and phone. It will be fixed though. Moreover it fly's with the JB update, I love scrolling through the screens its damn smooth.
I doubt if you got the correct handset . Surely something is wrong. Was it like this from the first day???
Click to expand...
Click to collapse
The screen scrolling is fine, it's nice and smooth. It's the opening up of contacts, phone and MMS that is really slow.
I've got the latest UK JB update so it should be a lot snappier, in my opinion.
And it's definitely a S3, no doubt there. Yup it was slow right from the get go.
It's the crazy high RAM use that is annoying the hell out of me
Oh, Then go to developer options and select background process limit to 4.That should help, but if you are freaking out about the RAM, then don't cause that's how android uses the ram.
I am currently Using Liquid smooth ROM (AOSP) . I have no contacts or phone lag. Use it if you like AOSP
Use an ASOP or miui Rom! JB onS3 is good but Sammy needs to improve.
Sent from my GT-I9300 using xda app-developers app
yes your s3 should blow your s2 away and NO you shouldn't have to tweak or remove apps, live wallpaper etc.
First try a factory reset...best and simplest advice for performance issues.
Then, and only then should you need to try to find out what apps or settings are causing problems (to be honest no settings should retard performance that badly).
Then...and its a longer shot is a faulty rom installation which a reset won't fix. In that case you'll need to reflash DLJ4 from a reliable source, here on XDA, samfirmware, checkfus etc.
If still problems then your issues are hardware related and you need to visit your provider who'll have access to a maintenance centre, or even samsung themselves...assuming you're still running stock. If not you need to use a guide to restore your phone status to unmodified and a flash a stock rom first.
Good luck
Obagleyfreer said:
I have just bought an S3 and I am actually quite disappointed in it's performance.
I have an S2 (Running stock ICS) and my S3 (Running stock JB) is quite noticeably slower, with terrible lag.
I am just wondering if this is normal, surely this should out perform an S2?
The 2 main area where it is considerably slower is opening up my contacts and MMS app.
From clicking the contacts icon it takes about 2 seconds to actually load the contacts, and the MMS app takes about the same time to load.
Also when opening my app drawer it is buggy and laggy when scrolling through.
I notice that I also have little to no free RAM, yes I know how android works and how it utilises RAM but it doesn't seem right to me.
Anyone else having this problem?
I'm also running JB which should be smoother than ICS!
The firmware version I'm using is XXDLJ4
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
you are not alone.......http://forum.xda-developers.com/showthread.php?t=1958171 ....and this is really annoying
Mine is REALLY fast. More responsive than ics for sure.
Full wipe, stock and..
That's it
Also loading a list with 50 or 100 contacts and some having photos can not be immediate unless its already in the cache..
Definetly do a factory reset, usually fixes most of your problems.
If its being all sluggish i would suggest running "Paranoid Android [ROM]" on it, which is amazing. Or if your looking for something lightweight go, "SuperNexus".
Either way, also go to " settings > dev options " and then change all the Animation Scale (From 1x) to 0.5x it will make the animations faster.
Your phone is not faulty.
The stock contacts and sms app made by samsung are too heavy and indeed open very slow. You should try exDialer or jelly bean sms app which can be found on Play store.
Sent from my GT-I9300 using xda app-developers app
arsenix said:
Your phone is not faulty.
The stock contacts and sms app made by samsung are too heavy and indeed open very slow. You should try exDialer or jelly bean sms app which can be found on Play store.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
What he said. Samsung have done something with the contacts, phone and mms app which take 2-3 seconds to load. Stupid. I think this is only on JB though, hopefully they fix it soon.
Sent from my GT-I9300 using Tapatalk 2
I only notice slowness with power saving mode enabled. Make sure its not and it should. I would use roms as close to stock as possible, IMO. Flashing and using aosp amd miui like others have stated will probably cause more niggly bits of annoyance then rectify current issues youd only replace them with new ones. Unless of course you have a rom addiction and flash every second day like me
Sent from my GT-I9300 using xda premium
No problems here, but have changed a lot.
Disabled S Voice, froze all Samsung applications. Same with services like remote controls, tracking etc. Deleted bin/kiesexe since I never use KIES and the extra ram is handy to have (ROM cooks, here is an idea, ask users if they want KIES on install, if not delete it)!.
Install a good kernel and try running a SQL optimization script to speed up databases. Lastly don't touch supercharger etc to get more free ram (that is wasted ram). It'll slow down Contracts and the Dialer since it removes them from ram. They are loaded at startup for a reason.
Also lastly, turn off unneeded Startups
You should be able to find a list of unneeded services and tasks, somewhere on the forum
You'll understand why, when you look at the list of unneeded bloatware, services etc running, why it is slow. shame on Samsung.
Swyped on GT-I9300 - XXDLJ4 - Siyah kernel 1.7b1 - JKay framework -
try wiping the cache partition in recovery mode. worked for me

[Q] Google Services Drains Battery

Since I changed to JB my battery is being drained by google services. I've tried turning off location services, all of google now, and everything that is using google to sync except for mail. I haven't found a solution anywhere online. I've also deleted my exchange and other mail accounts and I still have the problem.
I'm using MeanBean 2.3 and it also did the same thing on MB 1.4.
Any ideas?
drdamond said:
Since I changed to JB my battery is being drained by google services. I've tried turning off location services, all of google now, and everything that is using google to sync except for mail. I haven't found a solution anywhere online. I've also deleted my exchange and other mail accounts and I still have the problem.
I'm using MeanBean 2.3 and it also did the same thing on MB 1.4.
Any ideas?
Click to expand...
Click to collapse
I am also seeing this and sometimes Maps or Poynt do the same thing as well. If I look in my power history it will show GPS ON as a full blue line. I also see a solid blue line in the wake portion sometimes when the phone has been sleeping. Both issues will cause the battery to drain very quickly. If I don't catch them in time, my battery won't make it all day. If I go a day without seeing these, the battery lasts all day with plenty to spare. A quick reboot fixes them but I never had these issues before Jelly Bean. My wife has an EVO LTE too and sees these issues as well. Anyone know what is causing these issues? Neither of us have turned on Google Now yet fearing that will make it worse.
Did you do a factory reset after the upgrade to jelly bean? Many reported that helping.
Sent from my PC36100 using xda app-developers app
NaterTots said:
Did you do a factory reset after the upgrade to jelly bean? Many reported that helping.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
No, but my wife just got hers and I updated to Jelly Bean before installing or setting up the phone. Guess I will try factory reset after installing Jelly Bean. Thanks for the help!
I did super wipe (factory reset) last night with clean install and today I'm not having issues yet
Sent from my EVO using xda app-developers app
It didn't work. Google services turned on again and keeps my phone awake and is draining the battery. Does anyone else have an exchange account? I just deleted mine to see if that might help.
Sent from my EVO using xda app-developers app
In case anyone ever comes upon this thread and wants an answer, I think the problem is with exchange. I made it manual DL and the Google services stayed on but didn't drain the battery. Reset, location, and other changes didn't seem to help.
Sent from my EVO using xda app-developers app
Maybe exchange cuz I don't have the issue...its not even on the history
Sent from my EVO using xda app-developers app
drdamond said:
In case anyone ever comes upon this thread and wants an answer, I think the problem is with exchange. I made it manual DL and the Google services stayed on but didn't drain the battery. Reset, location, and other changes didn't seem to help.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I am having the same problem, but I don't have exchange. Just got my phone a week ago, not rooted, completely stock. Today was the first day that the battery abnormally drained, with google services using 50%. Not sure what changed or what happened. Trying to do some research into this as there seems to be a lot of questions out there, but haven't found any answers yet.
chopstxnrice said:
I am having the same problem, but I don't have exchange. Just got my phone a week ago, not rooted, completely stock. Today was the first day that the battery abnormally drained, with google services using 50%. Not sure what changed or what happened. Trying to do some research into this as there seems to be a lot of questions out there, but haven't found any answers yet.
Click to expand...
Click to collapse
I am having this problem every so often also. The phone stays awake 100% of the time due to the google services. I kill it a couple times and usually it stops for awhile. Very annoying, still looking for a fix.
-Matt
The best way to figure out what is draining your battery is to install Better Battery Stats from the play store. Let it run in the background for a day or two and then check out partial wake locks and alarms. See if there is an app or process that is running out of control. Check all of your settings for syncing gmail, chrome, news and weather, etc. If you can't find some app that is keeping your device awake when it should be resting, then it could just be the phone.
Is there any REAL solution for this issue?
"Google Services" keeps my phone awake 100% of the time sometimes and I get maybe 4 hours of bat till completely dead. I've tried turning off sync, gps, mail, etx still does it. I think it really the Play Store but I cant be sure.
Bountyhunter1000 said:
Is there any REAL solution for this issue?
"Google Services" keeps my phone awake 100% of the time sometimes and I get maybe 4 hours of bat till completely dead. I've tried turning off sync, gps, mail, etx still does it. I think it really the Play Store but I cant be sure.
Click to expand...
Click to collapse
Turn off Autosync then turn it on again and force a full sync, then reboot, I've read somewhere I think in the sense 5 port thread about something like this and I think scottspa or Finz posted this as a solution, try it and let us know...
I've been having hella issues with this recently. Some of the fixes out there work some of the time. Best one I've found is to sign out of Google EVERYTHING, wipe caches, reboot, then resign in. Even sometimes that won't release the wakelock. Yesterday for instance I had to do that, then take it a step further and delete my data from everything with the word Google on it and do 2 reboots before it would go the hell away.
disable
I disable mine.
Use titanium backup. Make the services and play store user apps. Then use greenify on them.
Sent from my EVO using Tapatalk 2
jocarog said:
Turn off Autosync then turn it on again and force a full sync, then reboot, I've read somewhere I think in the sense 5 port thread about something like this and I think scottspa or Finz posted this as a solution, try it and let us know...
Click to expand...
Click to collapse
I am running MeanBean with latest firmware. I had this issue yesterday and I tried your fix. So far today, google services has only used 2%. I am curious to see if it stays that way or if the issue will come back.
Thanks
clearing cache and delvik cache seems to work for a little while that it just starts again ok. I only staredt having this issue about 2 weeks ago. That's why I think its the Play Store cause that's when the Play Store updated. Also rebooting seems to relieve the situation temporarily. Its just a pain in you don't look at your phone for a few hours notice 75 percent of your battery is gone.
I had the Google services drain too. I was looking high and low for the cause. Finally solved mine by going to Quick Event app, clicked setting icon (top right), set both Default Reminder and Default Duration to none.. That solved my problem.
So I did a few things and have not had a problem in a week(ish) now. I cleared cache and dalvik cache. I also forced a sync then turned off sync tried to sync again then turned it back on.
I have not had a problem since. In fact I left this phone sitting all weekend from sat morning to this morning and it only used 22% battery. (there was NO use by me)
Just incase anybody is wondering I am on the latest Mean Bean with over clocking and over volt.

Categories

Resources