Koodo Community


Extend battery charge by disabling synch with Exchange Server

Userlevel 1
Many people (admittedly of the slightly older generation) don't need to be constantly connected to their email. Addiionally, those from the Palm generation are OK with syncing their calendar and contacts at the end of the day rather than needing constant sychronization with Outlook on their computer. Well. I found that if you turn off synchronization of with an Exchange Server over WiFi, the battery charge depletion crawls to zero (for all practical purposes) when the phone is put to sleep. For this to happen, one must have disabled data usage and ensured that WiFi is automatically disabled during sleep mode. I use CyanogenMod 12, and the battery depletion tracking gave a projection of umpteen days before depletion, as opposed to 1-2 days before I turned off syncrhonization. I could see the marked difference in the plot of the battery charge with time. The funny thing is that before synchronization was disabled, I still had data usage turned off, and WiFi was set to be disabled whenever the phone was asleep. The only thing I can imagine would burn up battery charge so voraciously is CPU activity. Maybe the synch routine is CPU intensive. Who knows.

3 replies

Tray clear running apps in the background may help if thay are running may slow your phone down tray clean master may help you out it can boost your phone check for virus neet app Os is cleanmster on Google play I hope answer your question best that I can
Userlevel 1
I did consider that, but I learned recently that leaving apps open is more efficient because it avoids having to start them up from scratch. This of course assumes that apps don't execute code when the phone is sleeping. The reality to me seems complicated and highly dependent on how apps behave. For now, I've stopped clearing running apps simply because the battery charge usage is so low, and I'm not experiencing what I would consider to be abnormal lag.
Userlevel 1
New info: Disabling sync is not enough. My battery usage rate went from infinitismal to highly significant mid-yesterday and that persisted past midnight. Basically sucking away all the battery charge that could have gone on for a few days more. A few possible explanations: (i) The charge monitoring is not reliable; (ii) While the metric that is monitored may be OK, the battery behaviour is highly nonlinear toward the end of its charge cycle (which sort of means that the metric being monitored isn't all *that* OK); (iii) other apps are sucking up the juice. It is common belief that leaving apps open and resident in memory is more power efficient that shutting them down after each usage, thereby requiring them to be started up again. This maybe true of the apps aren't actually active and hence burning up CPU cycles, but I believe that this is not the case for at least one app or service in my case. There aren't too many suspects. I've only installed Qumu PDF viewer and Google Apps (the latter only for the purpose of getting the former). I've prevented all the GApps services from launching using CyanogenMod's Privacy Guard. And I've been using Qumu for days on end. The *only* notable difference yesterdy from most days is that I got a slew of notifications from my calendar. So... It's either the little blinking notification LED that is the culprit, or the way that notifications are handled. Unless they use an incandescent microbulb for the LED, it's hard to see how the blinking can consume much more energy than viewing the whole screen for hours on end. I suspect it is how the notifications are managed. The cure? Empirically, it is to reboot the device. The battery usage levelled off thereafter to be nearly flatline with time.