Related
Hello all,
Not sure if anyone has had this happened to them as well.
I am looking to root the phone and this is the only thing holding me back in fears that would be a hardware issue and then can't replace. But thing that it is software.
Here is what happens, like in the mourning I will wake up and check time on device by just pressing lock once and put down (has happened even with out doing that) then will see that alarm won't go off and try and wake the phone with power button and will get no response from the device just black screen and phone is getting warm.
I will actually have to remove and reinsert the battery to get to come back on.
Has been doing this since the update. I have tried to go an uninstall all the programs I don't use and don't have anything on it that my mytouch is not running and that device has no problems. Tried master resetting the device a few times.
I have reset from the recover wipe data option and from spl neither seemed to help
Problem only seems to happen after the phone has been on for over 100 hours.
Weird thing I took notice is after a master reset it redownloads all the apps again right away. Don't know how to stop that.
Right now mine is running the stock software the shipped version manually update to official touch update from sdcard.
So my question is there anyway to have the phone keep the logs since logcat is reset when the phone is restarted to find the problem. Or if this something you all have seen. Any ideas would be appreciated.
Hopefully you have a software-only problem... and I don't know how to prevent logcat from resetting after restarting the phone... but I can recommend one possible solution...
1. Get the stock Google/HTC signed EPE54B firmware... http://forum.xda-developers.com/showthread.php?t=642811
2. Rename it to PASSIMG.zip, copy it to the root of your SD card.
3. Reboot in bootloader and select Bootloader from the menu. Your phone should start scanning for the PASSIMG.zip and ask you to apply the firmware update...
And, yeah... no you won't void your warranty by doing this, since this is a stock signed original firmware....
I get this (or a similar) problem too. I'm not yet sure if it's a hardware or software problem, and am therefore avoiding rooting my phone until I'm sure.
I have noticed that this happens more often, or at least seems to be more likely, when the phone is cold... I've not had it happen during the day (when it's nice and warm in my pocket), but when I leave it on my night stand whilst sleeping, or for an extended period on my desk at home, it seems to freeze up then.
I'm an electrical engineer and suspect that this problem may be due to silicon right on the edge of it's qualification range (similar to how some people are able to overclock to 1.2 GHz stably, mine is unstable even at 1 GHz... :-( ), I think my device is unstable at 998 MHz at whatever voltage it's running at currently (looks like Qualcomm changed the recommended voltage from 1.25 to 1.275 and finally to 1.3V over the course of early 2010).
See some of these commit comments for more details:
https://www.codeaurora.org/gitweb/q...it;h=6ede969b4418be5f8f2bd128d0cd4fbd3fd97e72
https://www.codeaurora.org/gitweb/q...it;h=ff61966464a2a2d2da36c0194d326370d3c3caeb
https://www.codeaurora.org/gitweb/q...it;h=a129aec2ec8b0b8ef9943e437415073620f15678
Based on them, I would guess we can expect more stability in the FroYo release (assuming it's using the 2.6.32 kernel, and is coming soon). In which case I'll wait.
I will try that rom next. In my tinkering I went back to erd and let it auto update to ere on its own. and will see how that does. If it fails again I will try the other rom. I can still revert back from that to erd if I want later right?
everything except the radio... i believe the radio can only be downgraded on an unlocked phone... so i've heard...
It happen to one of my nexus one too, the other one never hangs. It happen mostly when i'm charging on the dock with screen on.
I address this problem with HTC once, and they told me to try remove the micro sd card and see if it happen again. So i switch a newer sd into the phone and its running fine waiting to see if it hangs again if it does, HTC say will they come send a carrier over to fetch the phone to check it.
Running fine for 4 days already, just weird tho how can a sd card cause this?
Could also be a low memory issue with the stock ROM. My wife's does that until I kill a bunch of background apps. I look at the available memory and it's at 13MB. She also hasn't reboot her phone in weeks...so that's probably why it was low on memory. I guess the internal Android task killer doesn't do it's job very well!
Probably at least once a day I will pickup my phone and it is off...any way to diagnose what is killing it? Running stock Sense with 1.72 update (rooted however). No overclocking but SetCpu is running but think it happened before when I wasn't using. Thanks for any help.
Sent from my HTC Vision using XDA App
Is it just off, or is it the "sleep of death", where you have to pull the battery to bring it back? I had the latter problem, and it was solved by installing one of the pershoot kernels from ROM Manager, oddly enough. Someone replied to a similar question from me with a "Try using pershoot, works well for me", and I was going to write it off as a rather unhelpful response, since he didn't elaborate at all...but wouldn't ya know it. Installed it for the hell of it, and cleared up the issues immediately. Didn't chance anything else (overclocking, settings, etc...). Worth a shot!
Its actually 'off'. Hitting the power button restarts it just fine, but it takes a long time to boot as if I HAD pulled the battery (not the fast boot you get when you tell it to turn off and then turn it back on).
I saw the threads on sleep of death but my symptoms didn't seem to fit.
I have noticed though that I would get pictures missing from my album and a reboot or a dismount and remount of my sd card would get them to turn back up. So I have bought a new card and so far so good on that front, and also no more shutdowns...so thinking maybe it was the memory card...which makes sense as it wasn't happening to anyone else!
Is there a program that logs what processes where running? I was thinking that I would see what tried to run before it shut off - but hopefully not necessary now!
Thanks for the reply...
Despite setting the WiFi sleep policy to "never", HD2 becomes unpingable when the screen goes off, causing applications such as Fring/Skype/etc to lose connection. After turning the screen back on, the WiFi reconnects, and does it rather quickly, but having it off while the screen off meaning no incoming Fring/Skype calls possible on WiFi.
Any ideas ?
NOTE: i am currently using this build.
Same problem. Wi-Fi goes to sleep when screen goes off, even if Wi-Fi tethering is running. It's a reason of losing connection via Wi-Fi tethering. BUT! If at least one network service is active (ping, for example), Wi-Fi doesn't goes to sleep. I think that some of background services (Wi-Fi routing!) stops or becomes idle when screen goes off. It's a priority or policy bug, maybe... Not in a particular ROM, but in Android OS.
Using MDJ's CyanogenMod 7 NAND ROM (Android 2.3.2 Gingerbread).
or may be in power saving option check there .it looks like it saving your battery power.
shahnowaz said:
or may be in power saving option check there .it looks like it saving your battery power.
Click to expand...
Click to collapse
It is not power saving options because it also happens to my mdj 2.6 build with battery full. Power saving starts on 15% on my battery and also wifi and background data has been unchecked.
When this happens, no email updates, voip, and other app updates that needs data(because mobile data is intermittent in my area).
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Enabling all workarounds would keep the device fully awake, this is not really a solution.
Tbh, this issue smells like a power management related bug in a wifi module/driver.
Also, if you google a bit, you can see it being talked about on nexus one, mentioning cyamogen roms as ones not having this issue.
Any idea what module/driver is responsible for wifi ? Is it a part of the kernel ? Or is it a module we may try replacing ?
rafpigna said:
yeah, actually happens with all builds
I solved with this app, enabling all workarounds
http://www.appbrain.com/app/wi-fi-keep-alive/com.shantz.wifikeepalive
Click to expand...
Click to collapse
Thanks much, just installed.
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
InfX said:
The offending driver seems come in a separate module, "bcm4329.ko". Here is a Nexus One thread mentioning the issue on one of the Nexus One stock builds, and actually presenting an updated module for that stock build.
Since HD2 uses the very same BCM4329 chip, it should be possible to compile the updated module for an HD2 kernel.
Any kernel guys up to the task ?
Click to expand...
Click to collapse
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
rafpigna said:
We need the commit used to do the change. I looked at the thread and found a commit but I dont think that is the right one.. Anyway I will try to see if can be included in my kernel asap and check if the situation improves.
Click to expand...
Click to collapse
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
rafpigna said:
I checked, and the fix is already there... So at this point I think this is not our problem. I will try to address this to markinus or danijel that are far more experienced than me in kernel stuff
Click to expand...
Click to collapse
Maybe, just maybe, it's already fixed in your latest kernel, that uses the latest code base ? Note that i did NOT try & check it with every kernel available, i've only checked this with one that came with the build i am using (i think it was MDJ there, newer version uses yours, but i am not yet running it).
Anyone using latest rafpinga kernel, can you please test and respond ?
Update, rafpigna 1.7 installed, identical WiFi behaviour.
Looks like this is the solution for Desire:
http://forum.xda-developers.com/showthread.php?t=752856
Hopefully someone could adopt this to HD2.
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
InfX said:
Nice... Rafpigna, the diffs are at this post, can you apply and compile the patched "bcm4329.ko" for us to try ?
Sorry for being too dumb to do it myself, i just never ever happened to compile a linux kernel, not even once in my entire life
Click to expand...
Click to collapse
It's not our problem
Note: This isn't related to the sleep mode wifi disconnections caused by MAC addresses that don't begin 00, so far as i'm aware that's been patched for a while now. Wifi remains connected fine in standby mode, but the throughput is only suitable for very light traffic.
Click to expand...
Click to collapse
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
InfX said:
I know its not our problem, but this may still be our solution. Our problem, seemingly, starts when the driver it going down into the deepest power saving state it can. It is supposed to sustain connectivity in it, though, but it seemingly doesn't. Avoiding this deepest state (PM_MAX) may solve the problem while having little to no side effects. Well, obviously, i do understand it's going to consume more power with WiFi on, but its better than being unable to keep it on at all.
Again, i know this is not exactly our problem, but again, this CAN be our solution anyway.
Click to expand...
Click to collapse
I think it's definitely worth a try...
mishik said:
I think it's definitely worth a try...
Click to expand...
Click to collapse
Hello!
Unfortunately, I have tried this (to my detriment; I have code due tomorrow still!), and basically replaced the equivalent of this in the RAF 1.7 code (dhd_cdc.c and wl_iw.c have the PM_MAX vs PM_FAST thing).
My zImage came out almost a whole MB smaller (probably a toolchain thing), but the wifi problem while sleeping still exists, at least the symptoms that are linked in http://code.google.com/p/cyanogenmod/issues/detail?id=2403 with the similar fix of PM_MAX vs PM_FAST. That is to say, if I open the terminal and ping google.com, when the screen is off I get 300ms pings and when the screen is on I can get 3ms pings.
This happens whether I change PM_MAX or PM_FAST.
So this isn't the fix for what it's supposed to fix (or maybe I'm doing it wrong, toolchain's wrong, something), but I'll give it a few days to figure out whether my wifi drops more or less. Hopefully less.
(My symptoms are that, on campus, I have no problems with wifi, but sometimes if I leave the wifi zone and then come back, it'll report still having an IP lease and everything, but all pings and connectivity-type things such as web browsing will time-out. Not sure if this is what is being discussed here, but I thought it might help!)
Thanks,
Jeff
PS If you want the zip just to give it a spin, pm me or I might attach it here. That said, it might break everything! No obvious problems on my phone yet, though, so...
EDIT!: Of course, I invite anyone (especially rafpigna; perhaps you've tested this already?) to double check my work. It's possible I might've misplaced something!
I didn't do anything advanced; just pick up the CodeSourcery toolchain (free) for ARM (not GNU/Linux) and then install it on a Linux machine (it's possible with Windows, probably, but it'll be harder with the RAF build.sh). Then, make sure you have make and gcc packages on your Linux machine and then put your sources in the right directory and then try running the build.sh! rafpigna documents his work very well. Thanks rafpigna!
Did you remember to actually replace the .ko module, not just zimage ?
Hello,
Did you remember to actually replace the .ko module, not just zimage ?
Click to expand...
Click to collapse
Of course.
I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?
chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!
Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.
cool, thanks. I'll try this today.
chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.
Yesterday I got the ICS update via Kies.
Saw that my CPU was not going into deep sleep.
BetterBatteryStats showed the problem
fuel_alerted is forcing a kernel wakelock.
I tried searching the forums, and there are some fixes in some custom kernels.
However, I could not find out what exactly is fuel_alerted, why does this happen, and does it happen on all phones?
I believe taking out battery and putting it back in should fix the problem. Right?
Will it come again?
Whats the root cause of this problem?
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
i dont have this issue. i flash DDLP8 india yesterday.
tsk1979 said:
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
Click to expand...
Click to collapse
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
weng_cas said:
i dont have this issue. i flash DDLP8 india yesterday.
Click to expand...
Click to collapse
All ICS roms have this issue. You just have not hit it. Its a bug in the kernel. Somebody has fixed it in an open source code. I googled quite a bit, and also found the offending function
https://github.com/CyanogenMod/samsung-kernel-c1/commit/5f6d8422629002c530dcf30891c241fe3ee2e0ab
katyarevishal said:
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
Click to expand...
Click to collapse
Will do
Here is what the bug report says
"However, when the SOC starts rising, the wakelock was only destroyed"
Now what is SOC referring to? System on Chip? Does not make any sense. Can somebody look at the github page?
Try disabling the power saving mode and restarting.
Don't use power saving mode. I've only seen this Wakelock after I've checked the powersaving option.
Ironic. But true.
Sent from my GT-N7000 using XDA Premium HD app
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months.
I fixed this in I777 Gingerbread kernels back in October, I9100 kernel developers pulled in the fix fairly quickly. Despite the bug being documented and fixed by the community for months, it is still present in all of Samsung's ICS kernels.
It has been fixed in the CM9 kernel since the day I9100 Update4 sources were released.
It's also fixed in DAFUQ. (However a lot of other stuff is currently broken in DAFUQ.)
No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
I just noticed this param, I am not sure it was there before (I am on LPY)
Rebooting and it's still there!
Doing Power off now..
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
No - FM is a userspace issue, as is MHL.
For CM9, the only things the source release affects are:
1) Speakerphone (already fixed)
2) Possibly a more reliable wifi driver (although CM9 may just kangbang pawitp's great work on the Aries kernels)
3) Backporting some performance features such as improved busfreq control
Entropy512 said:
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months...
...No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Click to expand...
Click to collapse
Found this thread after seeing this causing wakelocks in my i9100 S2. Thanks for the explanation.
However, rebooting - as well as powering off and switching on again still did not eradicate the fuel_alert problem and CPU Spy was showing my phone couldn't enter deep sleep.
Only after pulling out battery (and waiting for 1 minute for good measure) and powering up again did the bug go. CPU spy then reported my phone had entered deep sleep and the fuel_alerted entry was no longer showing in BetterBatteryStats.
Remove the battery and wait for 1 minute and reboot the phone , it will fix the problem.
To avoid it from happening again , remember to wake and unlock the phone every time before removing the phone from charging(Data cable & charger both).
I never unlock the phone before plugging and unplugging, and inspite of that problem is not reappearing.
So it may be completely random. I looked at the github code, but somehow could not figure out any relation to lock/unlock while charging.
It happened to me once and i removed the battery for 15 mins and it disappeared. But today it happened again. I do have power saving mode enabled but i dont want to again and again remove the battery to fix it. I charge my phone by turning it off and once its charged i remove the charger, let the display go off and then only turn on the phone. Do i need to turn on the phone before i remove the charger?
I think the power save mode has something to do with it. I didn't check the battery history before turning it on though but after a few days the Note didn't last 12 hours with only 1 hour of usage. The processor was awake even when the screen was off.
As suggested here I removed the battery for a few mins. I reinstalled the battery and charged it while the phone was still off. After a few hours of charging I turned the phone on and date/time defaulted to base time as expected. I observed battery behavior for a few days and the processor is now sleeping when the display is off and only wakes up every once in a while maybe to sync. BTW I only have Gmail sync on everything else is set to manual. And I haven't touched the power save option since