UPDATE:
It seems that something not related to this driver relies on the old wakelock and it's now causing some partial wakelocks and causing some failed attemps to suspend:
Code:
PM: Device power.0 failed to suspend late: error -11
Restore the old module if you think your battery life is worse than before.
You can do that by flashing your favourite kernel, your current ROM or restoring the backuped module as explained here below.
I'll see if I can solve the problem.
_______________
I did some changes to decrease samsung-battery wakelock total time doing some optimizations, getting good results.
Ideally, the changes I made would save some battery, but I didn't properly verify this.
What I'm sure about is that samsung-battery wakelock total time is now very low, which means less time spent awake when the screen is off.
BetterBatteryStats screenshot after 3 and a half hours of use: 2 seconds of total time for samsung-battery. Not bad considering that the fixed duration of a single wakelock request was 3 seconds.
The driver had never been directly built into the kernel (EDIT: Adi_Pat did it in his kernel, read the notes below), we had always used a module, so you don't need to change kernel or ROM in order to use this, it shouldn't matter which ROM you are on as long as it's a CyanogenMod (9+) based ROM. You just need to flash the zip attached, which will replace the module in /system.
Flashing this on stock ROMs won't do anything.
If you can't see the battery percentage after you've flashed the zip attached, it simply means that the module is not working as it should and you need to restore the original one.
A backup is automatically created after the flash, you can find it in:
Code:
/sdcard/backup-battery/m-d-y-H.M.S/samsung_battery.ko
To restore it, simply copy samsung-battery.ko in /system/lib/modules/ overwriting the existing one, set its permission to 644 and then reboot.
There's a backup copy for each flash you made, each copy is in a different subdirectory. The name of the subdirectory is the time and date of the flash.
Or more simply reflash the ROM or restore a CWM backup.
I've tested the changes for some time, but I can't guarantee everything is working correctly. Flash at your own risk.
Source code:
battery-monitor: minimize awake time
battery-monitor: make polling timer deferrable
battery-monitor: don't use boot_complete flag
battery-monitor: add wakelock...
Notes:
A reflash of this zip could be required after flashing custom kernels.
I had to add an additional wakelock (samsung-battery-charge), but it's only used when charging the battery. It behaves as the old samsung-battery wakelock.
I looked around and I can say that Adi_Pat's SIRI kernel is the only incompatible kernel. The driver is inbuilt and my module will be ignored. Flashing this zip won't do anything, you need to rebuild the kernel with the above changes.
loSconosciuto said:
A reflash of this zip could be required after flashing custom kernels.
Click to expand...
Click to collapse
Maybe i should try this but sir what do you mean by this? You mean a custom kernel for CM is required before flashing this? Cant we flash this with the stock lets say CM10 kernel?
marshygeek said:
Maybe i should try this but sir what do you mean by this? You mean a custom kernel for CM is required before flashing this? Cant we flash this with the stock lets say CM10 kernel?
Click to expand...
Click to collapse
What my zip does is to replace a kernel module located in /system.
Custom kernels usually include modules in their flashable zips, so if you first flash my zip and then a custom kernel, my modified samsung-battery.ko will be overwritten.
Custom kernels are not required for this. They could actually be incompatible with this module (to know whether it's working or not, read the OP), but in that case you can restore the original module as written above.
Ohhhh hahaha. I've read again today, i was confused a while ago. LOL. That was a dumb question of mine. Sorry. Ok ill try and feedback after few cycles.
---------- Post added at 09:22 PM ---------- Previous post was at 09:11 PM ----------
loSconosciuto, can you check what ive noticed before. I was on Alpha 3 and im using BetterBatteryStats. I just tried freezing the Calendar sync and Contacts sync. I dont know if its just my mind saying or it was really a lucky try and i got INSTANT noticeable battery performance for the whole cycle.
Flashed! So far so good....
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Flashing it now. Will report back with impressions in the morning. Will check night time battery drop. CM10A4, crackersizer! kernel.(1200-300, Smartassv2,NOOP)
EDIT: First impressions, night time battery drop was 30 % as compared to usual 50-60 % in my case. Also due to some network issues the testing was halted. Will report back when i get a couple of battery cycles done with this tweak.
EDIT: Testing halted as installed the SIRI kernel of adi!!!
Did anyone try this with Siri Kernel v2?
Does it work correctly?
Thanks!
BachuArg said:
Did anyone try this with Siri Kernel v2?
Does it work correctly?
Thanks!
Click to expand...
Click to collapse
Mate, the OP said it doesn't work on Siri Kernel. I doesn't know about Siri Kernel v.2 but I think it's not a bright idea.
Sent from Galaxy SL Powered by JellyBam
BachuArg said:
Did anyone try this with Siri Kernel v2?
Does it work correctly?
Thanks!
Click to expand...
Click to collapse
adi pas insert the module to siri kernel v2
loSconosciuto said:
I did some changes to decrease samsung-battery wakelock total time doing some optimizations, getting good results.
Ideally, the changes I made would save some battery, but I didn't properly verify this.
What I'm sure about is that samsung-battery wakelock total time is now very low, which means less time spent awake when the screen is off.
BetterBatteryStats screenshot after 3 and a half hours of use: 2 seconds of total time for samsung-battery. Not bad considering that the fixed duration of a single wakelock request was 3 seconds.
The driver had never been directly built into the kernel (EDIT: Adi_Pat did it in his kernel, read the notes below), we had always used a module, so you don't need to change kernel or ROM in order to use this, it shouldn't matter which ROM you are on as long as it's a CyanogenMod (9+) based ROM. You just need to flash the zip attached, which will replace the module in /system.
Flashing this on stock ROMs won't do anything.
If you can't see the battery percentage after you've flashed the zip attached, it simply means that the module is not working as it should and you need to restore the original one.
A backup is automatically created after the flash, you can find it in:
Code:
/sdcard/backup-battery/m-d-y-H.M.S/samsung_battery.ko
To restore it, simply copy samsung-battery.ko in /system/lib/modules/ overwriting the existing one, set its permission to 644 and then reboot.
There's a backup copy for each flash you made, each copy is in a different subdirectory. The name of the subdirectory is the time and date of the flash.
Or more simply reflash the ROM or restore a CWM backup.
I've tested the changes for some time, but I can't guarantee everything is working correctly. Flash at your own risk.
Source code:
battery-monitor: minimize awake time
battery-monitor: make polling timer deferrable
battery-monitor: don't use boot_complete flag
battery-monitor: add wakelock...
Notes:
A reflash of this zip could be required after flashing custom kernels.
I had to add an additional wakelock (samsung-battery-charge), but it's only used when charging the battery. It behaves as the old samsung-battery wakelock.
I looked around and I can say that Adi_Pat's SIRI kernel is the only incompatible kernel. The driver is inbuilt and my module will be ignored. Flashing this zip won't do anything, you need to rebuild the kernel with the above changes.
Click to expand...
Click to collapse
I have one question. What is normal discharging time of battery,moderate use,stand by n normal use what so ever .As i saw in my case it wont lost more than 4 hour of continues use of net both wen i was on stock rom and after custom rom.
Sent from my GT-i9003 using xda premium
loSconosciuto said:
I did some changes to decrease samsung-battery wakelock total time doing some optimizations, getting good results.
Ideally, the changes I made would save some battery, but I didn't properly verify this.
What I'm sure about is that samsung-battery wakelock total time is now very low, which means less time spent awake when the screen is off.
BetterBatteryStats screenshot after 3 and a half hours of use: 2 seconds of total time for samsung-battery. Not bad considering that the fixed duration of a single wakelock request was 3 seconds.
...
Click to expand...
Click to collapse
Question: Are you referring to this line if you talk about the standard wakelock length of 3 seconds? Because I would think that this actually means that the wakelock length is 3*HZ with HZ=1/128 s (see config entry), resulting in 0.0234375 s. This, in turn, gives roughly 2.8125 s of battery monitor wakelock every hour if the system wakes up every 30 s. Am I wrong?
Anyway, your patch is very cool and should result in improved standby times
XDA_Bam said:
Question: Are you referring to this line if you talk about the standard wakelock length of 3 seconds?
Click to expand...
Click to collapse
Yes.
XDA_Bam said:
Because I would think that this actually means that the wakelock length is 3*HZ with HZ=1/128 s (see config entry), resulting in 0.0234375 s. This, in turn, gives roughly 2.8125 s of battery monitor wakelock every hour if the system wakes up every 30 s. Am I wrong?
Anyway, your patch is very cool and should result in improved standby times
Click to expand...
Click to collapse
That's what I thought too, but then, I can't remember why, I opened wakelock.c to verify this.
This is what conveinced me that the they are 3 seconds. See how timeout is converted when it's printed.
With timeout=3*HZ, the result of that operation should be 3.000.
Because I'm lazy, instead of reading the rest of the code I looked for commented piece of code on the internet and found few examples that confirmed my hypothesis. Here two examples I've just found: 1, 2.
I've also tried something. I plugged in the phone, waited for "samsung-battery-charge", unplugged it and got this in /proc/wakelocks
Code:
name [COLOR="Blue"][B]count[/B][/COLOR] expire_count wake_count active_since [B][COLOR="Red"]total_time[/COLOR][/B] sleep_time max_time last_change
"samsung-battery-charge" [COLOR="Blue"][B]1[/B][/COLOR] 1 0 0 [B][COLOR="Red"]2988677920[/COLOR][/B] 825195313 2988677920 957372533720
I assume those are nanoseconds: 2988677920 ns = 2.989 s.
I'm still not sure of this, because it doesn't make so much sense to me, I mean, what's the purpose of this?
By the way the battery is checked more often than I thought, sometimes I have even less than a second of interval between two checks. Not a big deal with this patch .
You can easly see how often the battery is checked with:
Code:
dmesg | grep "monitor BATT"
loSconosciuto said:
Yes.
That's what I thought too, but then, I can't remember why, I opened wakelock.c to verify this.
This is what conveinced me that the they are 3 seconds. See how timeout is converted when it's printed.
With timeout=3*HZ, the result of that operation should be 3.000.
Because I'm lazy, instead of reading the rest of the code I looked for commented piece of code on the internet and found few examples that confirmed my hypothesis. Here two examples I've just found: 1, 2.
I've also tried something. I plugged in the phone, waited for "samsung-battery-charge", unplugged it and got this in /proc/wakelocks
Code:
name [COLOR="Blue"][B]count[/B][/COLOR] expire_count wake_count active_since [B][COLOR="Red"]total_time[/COLOR][/B] sleep_time max_time last_change
"samsung-battery-charge" [COLOR="Blue"][B]1[/B][/COLOR] 1 0 0 [B][COLOR="Red"]2988677920[/COLOR][/B] 825195313 2988677920 957372533720
I assume those are nanoseconds: 2988677920 ns = 2.989 s.
I'm still not sure of this, because it doesn't make so much sense to me, I mean, what's the purpose of this?
By the way the battery is checked more often than I thought, sometimes I have even less than a second of interval between two checks. Not a big deal with this patch .
You can easly see how often the battery is checked with:
Code:
dmesg | grep "monitor BATT"
Click to expand...
Click to collapse
Ahhh, I think I got it, thanks! The kernel expects all time values in jiffies. Therefore, X*HZ gives you the value of X seconds converted to jiffies (and HZ actually is 128, not 1/128).
Re: Optimized Samsung battery driver [CM]
If you can't see the battery percentage after you've flashed the zip attached, it simply means that the module is not working as it should and you need to restore the original one.
Excuse me what do u mean by battery percentage here i flashed zip now how will i know it is working? Thanks alot
Sent from my GT-i9003 using xda premium
Re: Optimized Samsung battery driver [CM]
Just set permission
Sent from my GT-I9003 using xda premium
I sadly discovered, not so much time ago, that this module is making "Android System" use more battery than normal. At first I thought it was a roughly made app, but I then found that the problem is this module.
From my kernel logs I can see that sometimes when the device tries to enter into deep sleep right after it woke up, it can't because there's something blocking the process (I don't know what yet) and it has to try again before it succeeds. This is causing increasing the number of alarms (Partial wakelocks in BBS) and the saved time is not as much as I hoped.
I don't think the problem is in this module, because the same thing happens when the module is not loaded. I'd say is something which normally would require a wakelock, but not in our case because of the omnipresent samsung-battery (correct me if I'm wrong). I did some changes here and there, but the resulting driver is not so different from the original one, so, for the moment, if you think your battery is worse than before (the mentioned problem was pretty random on my device) just restore the original module as explained in the first post.
I'll maybe look better into that when I'll have some time and in case I'll discover something, I'll let you know.
latief.makhdoomi said:
If you can't see the battery percentage after you've flashed the zip attached, it simply means that the module is not working as it should and you need to restore the original one.
Excuse me what do u mean by battery percentage here i flashed zip now how will i know it is working? Thanks alot
Click to expand...
Click to collapse
Sorry for the late reply. To check if it's working, just look for samsung-battery-charge inside /proc/wakelocks. If it's there, it's working (plug and unplug your phone if you can't see it immediately).
With "can't see the battery percentage" I meant that you can't see how much battery is left: instead of the usual icon you have the battery icon with an exclamation point in it and you can't see the percentage from the settings.
hi losconoscuit i got a problem,when my phone screen is off or in standby mode am getting IM messages late i mean in watsapp or any IM messages are delivered to me late or at time wen i unlock my screen at least 10 mints late is it related to wake lock or anything else .please help.
Sent from my GT-i9003 using xda premium
latief.makhdoomi said:
hi losconoscuit i got a problem,when my phone screen is off or in standby mode am getting IM messages late i mean in watsapp or any IM messages are delivered to me late or at time wen i unlock my screen at least 10 mints late is it related to wake lock or anything else .please help.
Sent from my GT-i9003 using xda premium
Click to expand...
Click to collapse
Which rom/kernel are you on? Maybe something to do with the new sync bug workaround...
Sent from my Samsung Galaxy SL on CyanogenMod 9 !
Ehndroix ROM with Dhiru's kernel
Sent from my GT-i9003 using xda premium
Related
So I was investigating loadable kernel modules on the Droid 2 this weekend. One of the modules I tried loading was the smartass governor module and to my surprise it worked. From what I can tell it appears to be working with no problems.
The module itself is from a Milestone Cyanogen ROM. Given how close the Milestone is to the Droid 1 and how close the Droid 1 is to the Droid 2 it seemed like a safe try to see if it would load.
Requirements:
You must be rooted. This really should go without saying but I'm trying to cover all the bases here.
You must have busybox installed.
You must be able to boot into clockwork recovery.
I've tried this on Fission ROM but since we can't change the kernel on the Droid 2 this will probably work on any other Droid 2 ROM. D2G users, YMMV.
NOTICE: By installing this you assume any and all risk for what might happen to your phone. I am not responsible if this mod causes your phone to stop working, catch fire, steal your significant other, and/or hijack a plane. Basically I haven't had any issues but that is not a guarantee that you won't have any issues.
Attached is the update.zip. Boot into clockwork recovery and choose this zip to install. Once you reboot you'll be using the smartass governor.
So what has this done for your battery life?
Anecdotally I believe my battery life has improved. With the ondemand governor and data and wifi off I've seen my battery drop 10% in a night. With the smartass governor under the same conditions my battery appears to be the same. Now given that Motorola phones report the battery in just 10% increments my totally non-scientific analysis might end up being nothing.
Really you'd have to try it yourself and determine if things are better. From what I've read online the smartass governor is better at conserving battery than ondemand but it really depends on how you use your phone.
Download circle battery widget from the market. Its free and somehow it reports 1% increments. I have been using it for a while now and it seems to be spot on.
Sent from my DROID2 using Tapatalk
It just guesses
Well, there is a way to get an accurate battery reading. Reading /sys/devices/platform/cpcap_battery/power_supply/battery/charge_counter will give you the battery level in 1% increments. However, the system reads from /sys/devices/platform/cpcap_battery/power_supply/battery/capacity which provides the bounded 10% increments. Some widgets, Minimalistic Text for example, will read from charge_counter on Moto devices.
Ideally a kernel module could be written that changes what is written out to capacity so the entire system could take advantage of 1% battery increments. If I had the time I would take a crack at it, but it's been awhile since I've done any C coding.
Looks interesting. I'll wait until a little more feedback is given before I try it. How is the performance after the install?
I'm guessing you have to sbf to go back?
tbaker077 said:
How is the performance after the install?
Click to expand...
Click to collapse
No different than using the ondemand governor. Smartass takes a clever approach to CPU scaling: instead of polling CPU usage like ondemand it detects when the phone comes out of sleep and sets a timer to go off in two ticks. Once that timer goes off it looks at CPU usage and scales if needed. What does all this mean? Well, if you turn on your phone to quickly check the time and then turn it back off the smartass governor will never ramp up the clockspeed. So far after a few days of light usage I've been quite pleased.
rtfield said:
I'm guessing you have to sbf to go back?
Click to expand...
Click to collapse
Nope. If you want to revert just chmod 644 /etc/startup/smartass.sh and reboot.
Sweet
Thanks
I wonder if they could modify this to work with the new gingerbread kernel.
I know when I had an HTC Eris, Conap used a smartass gov on his kernel and it was awesome.
So I took a shot and flashed the smartass governor a second ago on my GB d2, and seems to be working just fine. I'll report later with battery stats and anything else i notice.
Spitemare said:
Well, there is a way to get an accurate battery reading. Reading /sys/devices/platform/cpcap_battery/power_supply/battery/charge_counter will give you the battery level in 1% increments. However, the system reads from /sys/devices/platform/cpcap_battery/power_supply/battery/capacity which provides the bounded 10% increments. Some widgets, Minimalistic Text for example, will read from charge_counter on Moto devices.
Ideally a kernel module could be written that changes what is written out to capacity so the entire system could take advantage of 1% battery increments. If I had the time I would take a crack at it, but it's been awhile since I've done any C coding.
Click to expand...
Click to collapse
I took a look at this and found some stuff that might be encouraging.
Here is the source for the battery driver. Line 397 reads as such:
Code:
val->intval = sply->batt_state.capacity;
If line 397 is changed to this
Code:
val->intval = sply->batt_state.batt_capacity_one;
then battery level should be reported in 1% increments. I've posted the updated driver code here.
The problem is the gorram encrypted bootloader. It's not easily possible to swap a built-in hardware driver with a compiled module. If someone with more Linux kernel experience than I wants to take a crack at it then by all means...
Do we really need busybox to uses this?
tbaker077 said:
Do we really need busybox to uses this?
Click to expand...
Click to collapse
Busybox's insmod is a little more robust then the insmod that's on the Droid 2. You can try editing the file /etc/startup/smartass.sh to remove the references to busybox and see if it works; I just stuck with busybox since that was what worked for me when building this thing. I'd try it myself but I can't at the moment.
I'm running an experiment now to see how long this governor will take me. I charged my phone to 100% last night (really 100% and not just to when the charging light went off) and turned it off. I turned it on this morning and will let the phone run until 5% battery is left. At that time I'll take a screenshot showing how long the system has been up. A few guidelines:
ROM is Fission 2.6.1 which of course means Froyo. I've been thinking about switching to the leaked Gingerbread ROM but I've decided to wait a little longer
Data must remain on. I usually turn data off when I'm not using it but to get results closer to worst case I'll keep data on. The only time it will go off is when I turn on Wi-Fi at home.
No turning off the phone at any time nor plugging it in. I guess I'm going to be using Dropbox a lot during this to transfer files but I don't want to reset the time since plugged in at all.
No overclocking, underclocking, or undervolting. Clockspeed and voltage are stock.
Usage will be light to moderate. I tend to use my phones for calls, chats, and web browsing. I'll throw in some YouTube videos and maybe download Angry Birds.
No apps that try to maximize battery life. That means no SetCPU, Tasker, Superpower, etc. This is supposed to be about how well the smartass governor does for battery life.
Again, once I reach 5% I'll try to take a screenshot of how long the phone went without being recharged.
Spitemare said:
I took a look at this and found some stuff that might be encouraging.
The problem is the gorram encrypted bootloader. It's not easily possible to swap a built-in hardware driver with a compiled module. If someone with more Linux kernel experience than I wants to take a crack at it then by all means...
Click to expand...
Click to collapse
Is this difficult to swap in simply because of the nature of what we'd be switching out, or does the eFuse chip and whatever other protection play a role here? I would try compiling your modified code and putting it on my device, except I'm afraid there will be some protective measure or something like that would brick my phone if I try. That and the fact that I have no idea what libraries and stuff I would compile this against.
So unfortunately my phone rebooted halfway into the experiment so there is no screenshot for you all. I will say my phone made it just under 36 hours (6:30 Friday to 18:15 Saturday) on this governor. With some moderate internet browsing and way too many YouTube videos I'm quite happy with the outcome using this governor.
ZaneKaminski said:
Is this difficult to swap in simply because of the nature of what we'd be switching out, or does the eFuse chip and whatever other protection play a role here? I would try compiling your modified code and putting it on my device, except I'm afraid there will be some protective measure or something like that would brick my phone if I try. That and the fact that I have no idea what libraries and stuff I would compile this against.
Click to expand...
Click to collapse
I've already compiled the modified module and tried to load it. The phone just prevents it from loading since the hardware interrupts are already bound to the compiled in driver.
eFuse doesn't prevent new kernel modules from being loaded. Since a kernel module can alter almost anything not being able to change the kernel isn't too much of a problem. What a kernel module can't really do, however, is change device drivers. There's not a really clean way to unload a device driver module since it binds to hardware interrupts and you can't really unbind that once the phone is up and running. If you want to replace a device driver with an alternate module you have to load the module before the original module is loaded sometime during the boot process. With compiled in device drivers though that's not really possible.
Basically we're in a situation where we need to load an alternate version of the device driver in module form before the compiled in device driver binds to the hardware interrupts. That would take some sort of ramdisk containing the altered driver module and we can't do that with eFuse.
The other option would be to write a module that hijacks calls to the particular function in the device driver and replaces that call with an alternative. That's got loads of problems though and is potentially dangerous. It would take someone with a lot more kernel experience than I have to write such a thing.
I installed this and didn't see any improvement in battery life until I ran
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
It said it was still ondemand. I checked scaling_available_governors and smartass was not in there, so I went ahead and installed the zip again... still doesn't work.
I went ahead and took a look at /etc/startup/smartass.sh. The permissions were right, so I ran /etc/startup/smartass.sh. I then checked /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and it was set to smartass.
Can anyone shed some light on why this script is not running on boot? I'm running the leaked Motorola Gingerbread ROM if that makes a difference.
Spitemare said:
The other option would be to write a module that hijacks calls to the particular function in the device driver and replaces that call with an alternative. That's got loads of problems though and is potentially dangerous. It would take someone with a lot more kernel experience than I have to write such a thing.
Click to expand...
Click to collapse
I see. I'm guessing the way to hijack said calls would be through directly modifying memory, right? That definitely is not something that sounds easy to do.
I tried running smartass.sh through an init.d script... still nothing. I actually had to make the /etc/init.d/ directory, so I figured that init.d scripts aren't supported on the Motorola Gingerbread rom... strange. I'll look for somewhere else where I can run stuff on startup.
Look for /etc/install_recovery.sh. That file is run by /init.rc if it exists. It's how the overclock stuff gets loaded on Fission. What the update.zip does is back up that file if it exists and then append /etc/startup/smartass.sh to the end. Just add the following to the end of /etc/install_recovery.sh if the update.zip doesn't add it:
Code:
/etc/startup/smartass.sh
Hey all
First time poster long time lurker
I finally took the plunge and rooted my phone (using Revolutionary)
Sadly, I'm stuck!
nb. On the boot screen (volume+Power), it says S-OFF
What do I do now, if I want to install a ROM (or revert back to my old build)?
Thanks in advance
ps. I've downloaded and tried to use fre3vo, etc. but can't get my head round it
pps. sorry for the long winded post
Zofu said:
HOn the boot screen (volume+Power), it says S-OFF
What do I do now, if I want to install a ROM (or revert back to my old build)?
Click to expand...
Click to collapse
Christ, that wasn't a long winded post....!
Next step is to install a custom recovery and root your STOCK ROM.
Although if you choose to download and install CWM as part of the revolutionary process you may already have the custom recovery installed. In which case simply download a custom ROM (which all come pre-rooted) to your SD and then flash it, although ensure that you read all the installation instructions first.
If you didn't install CWM as part of the S-OFF process then look at my signature where there are a couple of links
1) adb & fastboot
download this and extract contents onto PC
2) Flash CWM & su via fastboot
follow instructions in this thread to flash both the custom recovery (ensure that you get the version for your device SAGA)
Then I'd suggest you enter CWM and take whats known as a Nandroid backup of your device.
Then you should be able to download any custom ROM you like.
Any questions then ask, you should never do any steps that you are unsure or uncomfortable with as you can do damage to your device!
Cheers for the reply, ben_pyett!
I'll make a start now
I know it's not that complicated a prcoess, but I kinda jumped in assuming it'd take 5 minutes, I guess
I've flashed the Cyanogen 7.1.0 RC by NeoLogix onto both mine and my wife's handsets... and I have to say it's VERY impressive!
Initially it doubled the battery life, and with some clever settings tweaks (which I'm more than happy to post here, menu by menu, if you end up using the same ROM) I've more than quadrupled the effective battery runtime.
ben_pyett said:
1) adb & fastboot
download this and extract contents onto PC
Click to expand...
Click to collapse
Ok I did this
ben_pyett said:
2) Flash CWM & su via fastboot
follow instructions in this thread to flash both the custom recovery (ensure that you get the version for your device SAGA)
Click to expand...
Click to collapse
I followed the instructions ("fastboot flash recovery recovery.img" -- where "recovery.img" was the Desire S CWM recovery) via my USB with the phone in Fastboot mode (white screen)
ben_pyett said:
Then I'd suggest you enter CWM and take whats known as a Nandroid backup of your device.
Click to expand...
Click to collapse
How do I enter CWM?
Do you mean turn my phone on normally and CWM app will be installed?
Seems I seriously need walking through this!
Grr
Here's the way I find best.... switch your phone OFF, but leave it plugged in via USB.
From your command prompt, type "adb reboot recovery"
The phone will then boot to recovery
Zofu said:
How do I enter CWM?
Do you mean turn my phone on normally and CWM app will be installed?
Seems I seriously need walking through this!
Grr
Click to expand...
Click to collapse
Sounds like you've made huge progress...
I'm assuming that you've also push'd the SU file while in fastboot? if not do that as well.
At this point you should decide which custom ROM you wish to install and download that and all its add-ons and place them on you SD card so that you are able to use them once you're in RECOVERY. You should probably take the time while the ROM downloads to read the install instructions that come with the ROM, that often involve running additional WIPE scripts etc....but each ROM is different.
Anyway back to the question you asked, how to enter CWM (clock work mod) which is your custom recovery.
You should normally boot your phone and then go into Settings->Power->fast boot and ensure that its un-ticked.
Easy Way
Install ROM Manager from the market and then choose the Reboot into Recovery Option (second one down from top) and voila!
Manual Way
Power Off your phone.
Turn on your phone by pressing Power button + Volume Down button together.
You should now see the white HBOOT screen, using the volume up & down buttons to flick through options and Power button as enter you should be able to find the RECOVERY option. go into that.
Don't worry once you have a custom ROM things will be easier as most customs have an Advanced power Menu which has reboot into recovery as an option.
Quick update:
ben_pyett said:
I'm assuming that you've also push'd the SU file while in fastboot? if not do that as well.
Click to expand...
Click to collapse
I have no idea what the above^ means!
Ok, I got into Recovery manually (black Revolutionary screen with menu)
What do I choose in the menu to install a ROM?
- reboot system now
- apply update from sdcard
etc.
Does the ROM have to be at the root of the SD?
Can the ROM be named anything you wish, or does it have to be named "update.zip"?
Still a little confused!
Cheers guys for your super help so far
Zofu said:
Quick update:
What do I choose in the menu to install a ROM?
- reboot system now
- apply update from sdcard
etc.
Does the ROM have to be at the root of the SD?
Can the ROM be named anything you wish, or does it have to be named "update.zip"?
Click to expand...
Click to collapse
This is the option that you need install ZIP from sdcard
The ROM can be called anything you want, I never bother renaming the ROM files that the cooks call them, so that I can easily identify which is which and it can be position in any location on the SD not just the root directory. Although try to avoid directories with spaces in for now.
Update.zip is something else so don't use that option.
Once you've done this I'd also download and install the CUSTOM recovery EXT4 as its much easier to use....you can do that by simply installing the following APK which you'll find in this post and that will install the new recovery for you.
best of luck...back in two hours.....got to go and watch MANCHESTER UNITED NOW!
Cheers Ben
Have fun!
*edit: fixed issue with ROM install*
I decided to give Cyanogen 7.1.0 RC by NeoLogix's ROM a try and it seems to be working fine
Thanks for the helps, guys!
ps. if wanted to install another ROM, do I need to uninstall the previous one (wipe it again?), or can I just copy another ROM over and install like I did before?
Zofu i suggest you flash virtuus unity! its a great sense 3 rom. i love it! it has brought my desire s to life!!
You shouldn't be swayed by any of our opinions with regards which ROM to choose, I'd suggest that you install all of them one after each and decide for yourself which one suits you most
Although first question is sense or no sense.
The reason why there are so many roms is because we all have such differing tastes
Enjoy
PS
There is no UN install task, but each ROM will have its own install instructions in the first post of the thread which will have it's own wipe recommendations
Swyped from HTC Desire S using XDA Premium
LaKraven said:
I've flashed the Cyanogen 7.1.0 RC by NeoLogix onto both mine and my wife's handsets... and I have to say it's VERY impressive!
Initially it doubled the battery life, and with some clever settings tweaks (which I'm more than happy to post here, menu by menu, if you end up using the same ROM) I've more than quadrupled the effective battery runtime.
Click to expand...
Click to collapse
I just got my Desire S as a gift not 3 days ago and it is my first android phone.
As soon as I realized that there is something wrong with it's rapid battery depletion - I started reading up on it and presently I have red led/green led tried to calibrate battery(i think it helped some), turned off all syncing to manual, changed themes to black and no animations, turned off bluetooth etc...Basically I have stopped everything "smart" on this smart phone following dozens of advice pages on this and other forums...Which then brings me right back to battery consumption of my DISPLAY - still, even after reducing brightness to under 40% it is using around 80% of all battery per charge.
I have rooted the phone today and really need your advice on:
what ROM
kernel
radio
OS
, or anything else in terms of apps and widgets to install in order to try and at least double my battery life so I can be safe without charging for at least 12 hours of i.e.( if I'm in a train to be able to watch a movie, listen to music 3 hrs, surf 1.5 hrs, do 3 or 4 15 minute calls , text and read books for couple of hours and still have battery left in standby) - or is it just a pipe dream of mine lol...
P.S. maybe avoid flashing ROM if there is another way to reduce Display consumption(80%)
Thx much, btw, is Cyanogen is the way to go???
To add to ben_pyett's suggestion... I wouldn't exactly just "install each one, one after another" as there is actually a finite number of times the ROM can be flashed before you start to damage the internal memory (sure, it's a high number, but why cause more wear than you have to, right?)
I'd suggest you read up on the ROMs before you decide to try them out! Take a look at what features they have, what people have to say about them (particularly looking for bugs and potential problems).
Hell, if you're lucky, you may even find an introductory video to some ROMs on YouTube, which will give you a little more insight into what to expect.
As Ben said, the first question is "To Sense, or not to Sense?"
As a matter of personal opinion, I've chosen "not to Sense" in favor of better battery runtime and the "cleaner" GUI.
Bombastc said:
I just got my Desire S as a gift not 3 days ago and it is my first android phone.
As soon as I realized that there is something wrong with it's rapid battery depletion - I started reading up on it and presently I have red led/green led tried to calibrate battery(i think it helped some), turned off all syncing to manual, changed themes to black and no animations, turned off bluetooth etc...Basically I have stopped everything "smart" on this smart phone following dozens of advice pages on this and other forums...Which then brings me right back to battery consumption of my DISPLAY - still, even after reducing brightness to under 40% it is using around 80% of all battery per charge.
I have rooted the phone today and really need your advice on:
what ROM
kernel
radio
OS
, or anything else in terms of apps and widgets to install in order to try and at least double my battery life so I can be safe without charging for at least 12 hours of i.e.( if I'm in a train to be able to watch a movie, listen to music 3 hrs, surf 1.5 hrs, do 3 or 4 15 minute calls , text and read books for couple of hours and still have battery left in standby) - or is it just a pipe dream of mine lol...
P.S. maybe avoid flashing ROM if there is another way to reduce Display consumption(80%)
Thx much, btw, is Cyanogen is the way to go???
Click to expand...
Click to collapse
I spent days trying to tweak the stock Desire S ROM (and again after the update I applied ~ a week ago) with quite literally no success!
Even with the most riggorous (performance and feature restricting) power management setup, I still couldn't get the thing to pass the 18 hour mark (which I only achieved with the help of Tasker, used to toggle Airplane Mode during my sleeping hours etc.)
Having switched to the CM7 ROM linked previously, and using nothing but a combination of changing its default settings, and SetCPU (to scale the CPU clock for superior power saving with literally NO performance hit), it'll now run for almost 48 hours between charges (more than sufficient, wouldn't you agree?)
I'll post a separate thread in here with a complete battery optimization guide for the aforementioned ROM.
Just to clarify, after more than 4 hours running on the battery (at least half of which with the display on and the phone in use) it has gone from full to just 90%, which in itself averages to about 40 hours of runtime.
Coupled with my SetCPU scaling, this adds ~8 more hours!
This means that, with moderately heavy use (though I haven't yet had time to test absolute runtime with HD 720p video playback just yet) you can expect a screen & WiFi ON time of 24 hours, with a standby time (again, with WiFi on) of a further 24 hours!
La Kraven - can you teach me how to dougie lol? You really quadrupled your batt? :O
Bombastc said:
La Kraven - can you teach me how to dougie lol? You really quadrupled your batt? :O
Click to expand...
Click to collapse
Yes.... and just to give you some comparrative reference:
Battery Use:
Mobile Standby: 74% (that's the GSM radio)
Wi-Fi: 12%
Phone Idle: 9%
Display: 4%
Android System: 2%
EDIT: The GSM registers heavily on "Mobile Standby" because I cannot get any cell reception where I live (AT ALL), so the GSM is idling, constantly looking for a carrier. If you're in a GSM (or better) environment, you can expect the "Mobile Standby" value to be substancially lower, most likely with other feautres such as Wi-Fi, Bluetooth or GPS leading the consumption values (dependant on what you've got enabled)
LaKraven said:
I spent days trying to tweak the stock Desire S ROM (and again after the update I applied ~ a week ago) with quite literally no success!
Even with the most riggorous (performance and feature restricting) power management setup, I still couldn't get the thing to pass the 18 hour mark (which I only achieved with the help of Tasker, used to toggle Airplane Mode during my sleeping hours etc.)
Having switched to the CM7 ROM linked previously, and using nothing but a combination of changing its default settings, and SetCPU (to scale the CPU clock for superior power saving with literally NO performance hit), it'll now run for almost 48 hours between charges (more than sufficient, wouldn't you agree?)
I'll post a separate thread in here with a complete battery optimization guide for the aforementioned ROM.
Just to clarify, after more than 4 hours running on the battery (at least half of which with the display on and the phone in use) it has gone from full to just 90%, which in itself averages to about 40 hours of runtime.
Coupled with my SetCPU scaling, this adds ~8 more hours!
This means that, with moderately heavy use (though I haven't yet had time to test absolute runtime with HD 720p video playback just yet) you can expect a screen & WiFi ON time of 24 hours, with a standby time (again, with WiFi on) of a further 24 hours!
Click to expand...
Click to collapse
Thx so much, HALF of that would be fine with me lol!
Bombastc said:
I just got my Desire S as a gift not 3 days ago and it is my first android phone.
As soon as I realized that there is something wrong with it's rapid battery depletion - I started reading up on it and presently I have red led/green led tried to calibrate battery(i think it helped some), turned off all syncing to manual, changed themes to black and no animations, turned off bluetooth etc...Basically I have stopped everything "smart" on this smart phone following dozens of advice pages on this and other forums...Which then brings me right back to battery consumption of my DISPLAY - still, even after reducing brightness to under 40% it is using around 80% of all battery per charge.
I have rooted the phone today and really need your advice on:
what ROM
kernel
radio
OS
, or anything else in terms of apps and widgets to install in order to try and at least double my battery life so I can be safe without charging for at least 12 hours of i.e.( if I'm in a train to be able to watch a movie, listen to music 3 hrs, surf 1.5 hrs, do 3 or 4 15 minute calls , text and read books for couple of hours and still have battery left in standby) - or is it just a pipe dream of mine lol...
P.S. maybe avoid flashing ROM if there is another way to reduce Display consumption(80%)
Thx much, btw, is Cyanogen is the way to go???
Click to expand...
Click to collapse
We are new to Android at some point, this is my first Android device.......but I've had many HTC Sense Windows mobile devices beforehand and most of the same things tend to apply.
I'd suggest as a first port of call you read this thread which is a GUIDE, and sticky for a reason kindly written by wnp_79, I learnt loads from reading this alone.
Don't expect to learn everything in a days....it takes weeks or months.....
just enjoy....and remember that we're all different have differing expectations and uses for the same devices so what suits one of us doesn't always suit the other.
ps
you shouldn't really go off topic like this.....if you need specific help say so and create a new thread or read the sticky threads which contain GUIDES and links to many useful resources. Don't expect to become an expert over night and attempt to learn as much as possible by simply reading before you risk damaging your device!
i lose around 40 precent overnight everyday
its really frustrating knowing that i have to work with it full day afterwards
so is there any fix for this?
No idea what youre talking about. Mine only drains 20% with wifi and wifi apps running overnight.
Maybe you should look over what you got running, and if you got a custom kernel, reduce the lowest frequency of the cpu. Im running mine at 450Mhz or something.
Ooooor maybe 'overnight' for you is like 26h ?
You could also............
.
.
.
.
.
suspense!
.
.
.
.
.
.
.
.
Leave it on the charger over nite! I know. Shocking.
Download "BetterBatteryStats" from here and check which app is causing it. If you need assistance, just head over to BBS thread. Remember to attach your log file so it's easier for them to help you.
Hearmeman said:
i lose around 40 precent overnight everyday
its really frustrating knowing that i have to work with it full day afterwards
so is there any fix for this?
Click to expand...
Click to collapse
First thing, you should get CPU Spy from the market. This will tell you if your TF is going into deep sleep or not.
If you were experiencing the same issue under HC then ICS most likely wouldn't fix the issue anyhow.
Prior to ICS I was loosing about 25% over night which just shouldn't happen. I was rooted but stock otherwise. I unrooted my TF & completely wiped before flashing ICS. One cool thing about ICS is there is an intergrated task manager widget. You can see what programs are running at any current time. There were three programs that were constantly running that I disabled. Those were PixWE, Netflicks, & My Uploads. Netflicks kept wanting me to update but I don't use it so why update it? I simply disabled it and there are a whole host of other programs that can be disabled too.
With all this being said I am only loosing 3-4 percent over night running ICS completely stock.
Try airplane mode
There's an app in the market that simulates airplane mode, but allows wifi still. After I installed it I stopped losing battery overnight. It's basically a wake-lock issue.
2easilyamused said:
There's an app in the market that simulates airplane mode, but allows wifi still. After I installed it I stopped losing battery overnight. It's basically a wake-lock issue.
Click to expand...
Click to collapse
+1 This worked for me too but for a different reason. My TF tends to leave wifi switched on, even when told to turn off when the screen does. It could also be a rogue app as described above. Once you sort it out, overnight drain should only be a few percent at the most.
2easilyamused said:
There's an app in the market that simulates airplane mode, but allows wifi still. After I installed it I stopped losing battery overnight. It's basically a wake-lock issue.
Click to expand...
Click to collapse
Could please tell me the name?
How to diagnose here
I lose ~20% overnight in flight mode.
If I go Settings > Battery I see it's a lot of Android OS. But widgets must be included in that. So then I go settings > apps > running and see a few apps running, but I can't tell which of these is killing the battery and I don't know which app would tell me ((can I run top on the the commandline?)). I will experiment more and report back. I suggest you do that same.
This should go in the first post of this thread:
To diagnose this charge before sleep, put into flight mode overnight and look in the morning to see if the Android OS has been the culprit.
Perhaps you don't need any 3rd party apps for diagnose but if you need to be available for early morning calls use a profile scheduler.
Get a new Kernel
The main problem is the kernel in ICS, a way to fix this is changing your kernel, I do recomend the Test kernel from Guevor, install from version 11 to up, test it and keep the one you like. My tf is lasting fully with keyboard, around 30hrs.
I use test 13
but on .17 and not .23
I'm on ICS 4.0.3 with 3.0.8-NEO though
werewolferx said:
The main problem is the kernel in ICS, a way to fix this is changing your kernel, I do recomend the Test kernel from Guevor, install from version 11 to up, test it and keep the one you like. My tf is lasting fully with keyboard, around 30hrs.
Click to expand...
Click to collapse
My Nook got stolen and I'm waiting for a DroidPro to arrive so this would be on my main phone. When I've tried to flash just the kernel on it's own I've had problems before. This time I'll give it a go but am I missing something in terms of flashing a new kernel on?
I'm on ICS 4.0.3 with 3.0.8-NEO-3.0-TeamICSSGS-257174-g197c9a1-dirty (build *07)
Other than the possible battery problem it's been good. I just want to check to see if yo uhave anything more concrete to backup your decision... that a different kernel really might make any difference because that Test kernel from Guevor is very much in flux... I'd no idea which one to choose.Up to test15 now.
(thread for reference here: http://forum.xda-developers.com/showthread.php?t=1565519 )
For convienience it would be nice to backup the current kernel first as other than battery it's working well...
update, edit instead of bump:
ok, I lost 1% an hour last night in flight mode (6% over 5 hours) with all background apps and services killed. Does that seem about right? The interesting thing was that not all processes/services/backgrounded showed the same on different task killers...
I bet there's lots of people updating kernels when actually it's an app, or the left over effects of an app or something like that.
Hearmeman said:
Could please tell me the name?
Click to expand...
Click to collapse
Use Auto Airplane Mode by DON this fixed my problem with battery drain from the wifi staying on.After 4 days of use I still hade 35% battery left!
ROM: CM9 latest nightly
Kernel: CM9's own
Radio: T-Mobile's UVLC8 (yes, I'm on T-Mobile)
Brightness: Auto (shown in screenshot)
Synced Gmail accounts: 3
Accounts in Email app: 0
My battery drops 20% in 42 minutes, which means it will be depleted in 3.5 hours. And this is mostly due to the screen. Why? I use the phone moderately and ALWAYS press the Power button to turn the screen off whenever I'm done replying to a text or doing anything with it.
Any suggestions?
Well judging from your notification bar you have bluetooth, WiFi, fb sync all on and you aren't even connected to a WiFi network or Bluetooth device. Try turning those off when they are not needed. Also go into the Facebook app and go to settings and change you sync time to a little longer than an hour (if you can stand it). Try that for now and see what happens
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Some info on screen on time would help, 3.5hrs screen on time is barely below average. I would expect that if FB is always syncing and blue tooth.
Also I would verify you don't have a wake lock going from charging. You can check with CPU Spy, better battery stats, as well as some others. Cpu spy is likely the easiest way.
Sent from my SGH-I727 using Tapatalk 2
Every once in a while I'll get a flash that does this, the battery just seems to be losing its will to live. I don't understand it myself but I restore my last nandroid backup, and then flash again. After that all goes back to normal.
ckck543 said:
Well judging from your notification bar you have bluetooth, WiFi, fb sync all on and you aren't even connected to a WiFi network or Bluetooth device. Try turning those off when they are not needed. Also go into the Facebook app and go to settings and change you sync time to a little longer than an hour (if you can stand it). Try that for now and see what happens
Click to expand...
Click to collapse
I always keep WiFi and Bluetooth on. I thought neither one of those really used a lot of power unless actually connected. I use BT only in my car and WiFi only at home (evenings). My FB refresh interval is set to 1h. I hardly think this is draining my battery.
lnfound said:
Some info on screen on time would help, 3.5hrs screen on time is barely below average. I would expect that if FB is always syncing and blue tooth.
Also I would verify you don't have a wake lock going from charging. You can check with CPU Spy, better battery stats, as well as some others. Cpu spy is likely the easiest way.
Click to expand...
Click to collapse
Better Battery Stats wasn't free, so I installed CPU Spy and Battery Spy, I am letting the phone charge to 100% and then, I'm going to unplug it and report after about 30 minutes.
meet2x4 said:
Every once in a while I'll get a flash that does this, the battery just seems to be losing its will to live. I don't understand it myself but I restore my last nandroid backup, and then flash again. After that all goes back to normal.
Click to expand...
Click to collapse
I will flash last night's CM9 nightly and see if I notice a difference.
Thank you all!
Razor1973 said:
I always keep WiFi and Bluetooth on. I thought neither one of those really used a lot of power unless actually connected. I use BT only in my car and WiFi only at home (evenings). My FB refresh interval is set to 1h. I hardly think this is draining my battery.
Click to expand...
Click to collapse
Might want to think of picking up some NFC tags and setting profiles so stuff like Bluetooth will automatically turn on when in your car, and off when you leave. And BT and Wifi do drain power when not connected because they are searching for connections.
Better Battery Stats wasn't free, so I installed CPU Spy and Battery Spy, I am letting the phone charge to 100% and then, I'm going to unplug it and report after about 30 minutes.
Click to expand...
Click to collapse
It's free to XDA members: http://forum.xda-developers.com/showthread.php?t=1179809
dakpluto said:
Might want to think of picking up some NFC tags and setting profiles so stuff like Bluetooth will automatically turn on when in your car, and off when you leave. And BT and Wifi do drain power when not connected because they are searching for connections.
It's free to XDA members: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
But wouldn't WiFi and Bluetooth show in the battery usage screen with a high percentage? They would show by themselves or under radio and those aren't high at all. It's all on the screen. That's the problem, it seems. And what I explained earlier is that I don't use it much. I will get a text message, I'll reply and automatically turn the screen off before I set the phone down. I never forget this. I'm actually anal about it. LOL
I just installed Better Battery Stats (thanks for the tip!!!) and will test with all 3 apps as soon as I unplug my phone to go to lunch. I haven't been able to do this yet. Crazy day here at work.
Thanks again.
Razor1973 said:
But wouldn't WiFi and Bluetooth show in the battery usage screen with a high percentage? They would show by themselves or under radio and those aren't high at all. It's all on the screen. That's the problem, it seems. And what I explained earlier is that I don't use it much. I will get a text message, I'll reply and automatically turn the screen off before I set the phone down. I never forget this. I'm actually anal about it. LOL
I just installed Better Battery Stats (thanks for the tip!!!) and will test with all 3 apps as soon as I unplug my phone to go to lunch. I haven't been able to do this yet. Crazy day here at work.
Thanks again.
Click to expand...
Click to collapse
that's covered under android system I believe. Most important, it causes wake locks that keeps your phone from deep sleeping.
Flash Instigators Kernel with Smartass/Badass scripts (not a joke....)
It will help you tremendously. You must reflash with every nightly update you do.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
OK, so 4.5 hours and battery discharged 38%. I guess that's not terrible, but my screen was only on for 26 minutes of that time and the phone is reporting 55% of the battery drain came from screen use. I feel battery life could be a lot better just because of this.
What else do these screenshots tell you guys?
I noticed KIK Messenger and MailDroid there. They both sync a lot. I do have a couple of IMAP accounts on MailDroid that I forgot to mention in my OP. But, still, I go back to the fact that most of the drain comes from the screen. These aren't related.
onealvideo said:
Flash Instigators Kernel with Smartass/Badass scripts (not a joke....)
It will help you tremendously. You must reflash with every nightly update you do.
Click to expand...
Click to collapse
Oh, true!!! I flashed InstigatorX's kernel when I first started flashing the nightlies, but, since I flash them every 2-3 days, I completely forgot to reflash the kernel. OK, it's more like I didn't know it was getting overwritten and I had to reflash it. Thanks for the reminder!!! By the way, do you go with stable (4.0b) or the latest experimental (5.3.2)? Also, do you just flash the kernel? What are those scripts and what do you do with them? I did not understand his instructions. Maybe I should be asking there, but since I already have you here... LOL
Razor1973 said:
OK, so 4.5 hours and battery discharged 38%. I guess that's not terrible, but my screen was only on for 26 minutes of that time and the phone is reporting 55% of the battery drain came from screen use. I feel battery life could be a lot better just because of this.
What else do these screenshots tell you guys?
I noticed KIK Messenger and MailDroid there. They both sync a lot. I do have a couple of IMAP accounts on MailDroid that I forgot to mention in my OP. But, still, I go back to the fact that most of the drain comes from the screen. These aren't related.
Click to expand...
Click to collapse
For one, turn your screen brightness down. I use auto-brightness and never have a problem seeing it, and my battery drain is ok that way.
Two, you've got the AudioOut_1 wakelock. Turn off system sounds in the settings menu (keytones, touch sound, screen lock sound, vibrate on screen tap) and that will take care of that.
Any type of instant messenger service (Skype is well-known for doing this) will wakelock your phone while it searches for IMs. No way around it other than an uninstall. You can't control IMAP pushing, but you can control folder polling, which eats up a lot of battery. I'd set your MailDroid accounts to not poll folders automatically more than once a day.
And definitely turn Bluetooth off when you're not actively connected to something. You might as well be using your phone as a flashlight with how much power BT burns through.
I am currently on RC2. I went to the 21/22 nightly but was not liking how it was behaving so I went with the RC for now.
In INSTIGATORS forum you will see in the links to the kernel one that says <-------- works with RC2.
I used that one and I am happy. Sure you could do the newer ones but I am happy where I am at currently.
Just boot into recovery and install from zip.
(Assume u download the zip on your phone....)
Its easy as pie!
You can play with the settings if you want but the default settings work pretty freaking good!
I would for sure recommend going to that forum as Instigator himself can answer ALL your questions in depth.... I am merely a messenger and user of his kernel.... wish they would just merge it into the cm9....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
T.J. Bender said:
For one, turn your screen brightness down. I use auto-brightness and never have a problem seeing it, and my battery drain is ok that way.
Two, you've got the AudioOut_1 wakelock. Turn off system sounds in the settings menu (keytones, touch sound, screen lock sound, vibrate on screen tap) and that will take care of that.
Any type of instant messenger service (Skype is well-known for doing this) will wakelock your phone while it searches for IMs. No way around it other than an uninstall. You can't control IMAP pushing, but you can control folder polling, which eats up a lot of battery. I'd set your MailDroid accounts to not poll folders automatically more than once a day.
And definitely turn Bluetooth off when you're not actively connected to something. You might as well be using your phone as a flashlight with how much power BT burns through.
Click to expand...
Click to collapse
Screen brightness: I use auto as well. It's in one of my first screenshots in this thread.
AudioOut_1 wakelock: Done. Thanks. I'm going to miss the touch and screen lock sounds. LOL I left dial pad touch tones and volume rocker music controls in that same secton checked, by the way.
MailDroid: I went through all the settings, both general and for the e-mail accounts and couldn't find a place to specify folder polling interval. Do you have it installed? If so, could you tell me exactly where to find this please?
Bluetooth: I'll try my best to turn it on only when I needed. I could also follow dakpluto's suggestion with the NFC tags. But then, I'd have to leave NFC on. Doesn't that drain battery too?
And you see, although all of these will help, don't you agree based on my screenshots that the biggest offender here is the screen and this is the area I should really be looking at?
onealvideo said:
I am currently on RC2. I went to the 21/22 nightly but was not liking how it was behaving so I went with the RC for now.
In INSTIGATORS forum you will see in the links to the kernel one that says <-------- works with RC2.
I used that one and I am happy. Sure you could do the newer ones but I am happy where I am at currently.
Just boot into recovery and install from zip.
(Assume u download the zip on your phone....)
Its easy as pie!
You can play with the settings if you want but the default settings work pretty freaking good!
I would for sure recommend going to that forum as Instigator himself can answer ALL your questions in depth.... I am merely a messenger and user of his kernel.... wish they would just merge it into the cm9....
Click to expand...
Click to collapse
Here's what I just did:
1) Installed latest (7/23) CM9 nightly.
2) Installed InstigatorX's 5.3.2 experimental kernel using CWM.
3) Installed InstigatorX's BadAss script using CWM on top of the kernel (I guess that's how you do it).
I will see how my battery behaves. It'll be difficult to know which of the many things I did is the one that yielded the biggest improvement, however. Oh well.
Thank you all!
I'm testing aokp w/ stock kernel ondemand 192/1512 and it actually is working decently for me so far. Streamed like 1 1/2 hr of video last night and 2hr of Pandora today at the gym. :good:
Sent from my SGH-I727 using Tapatalk 2
You see? Why can't I get HALF of that?
InstigatorX CM9/AOKP Kernel - Which One?
Razor1973 said:
... do you go with stable (4.0b) or the latest experimental (5.3.2)? Also, do you just flash the kernel? What are those scripts and what do you do with them? I did not understand his instructions. Maybe I should be asking there, but since I already have you here... LOL
Click to expand...
Click to collapse
That's what I'm trying to figure out:
Which version (e.g. 4.0b or latest)?
Which script(s)?
Anything else?
(There's tons of information in these forums, but finding it buried deep in threads is like looking for a needle in a haystack.)
From the looks of that screen shot. The phone is barely being used, see how the blue isn't solid for most of the running time?
Sent from my SAMSUNG-SGH-I727
kr3w1337 said:
From the looks of that screen shot. The phone is barely being used, see how the blue isn't solid for most of the running time?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Yep I have power saving stuff such as turn off wifi when idle, I dont have GPS on 24/7 and I dont have wakelocks, I also set mine to use 3G/4G rather than LTE. If it was a solid blue that means something will be constantly on draining the battery.
I'm testing aokp w/ stock kernel ondemand 192/1512 and it actually is working decently for me so far. Streamed like 1 1/2 hr of video last night and 2hr of Pandora today at the gym.
Click to expand...
Click to collapse
Those are the two lines from the front and the end. The blanks are deep sleep over night. Remember I said "testing aokp" "stock kernel"
If you want my "light" use then here it is lol.
Trinition said:
That's what I'm trying to figure out:
Which version (e.g. 4.0b or latest)?
Which script(s)?
Anything else?
(There's tons of information in these forums, but finding it buried deep in threads is like looking for a needle in a haystack.)
Click to expand...
Click to collapse
For performance I prefer smartassv2 for power saving I would go for badass governor. With badass it doesn't jump clocks to max but goes by phases thus not aggressive and doesn't eat a lot. Test them out read the change log to see if changes pertain to you :good:
Sent from my SGH-I727 using Tapatalk 2
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
TheHighLife said:
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Click to expand...
Click to collapse
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
lotherius said:
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
Click to expand...
Click to collapse
You don't need to downgrade TWRP to flash a modem. You can very easily flash a modem without TWRP even installed; fastboot. It isn't even certain that the modem is causing this drain either.
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Roughy said:
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Click to expand...
Click to collapse
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
f41lbl0g said:
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
Click to expand...
Click to collapse
Correct, with the Xposed Mobile Radio Active fix applied.
bacon_firmware_update_2015_04_03.zip from ... <10 posts and am not allowed to post links yet.
It's on Exodus' 5.0.2 download page along with the roms.
As usual the modem will not flash in TWRP, and has to be done manually via fastboot.
Paresh Kalinani said:
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
Click to expand...
Click to collapse
I did all of this but it's still draining battery, should I post new screenshots?
TheHighLife said:
I did all of this but it's still draining battery, should I post new screenshots?
Click to expand...
Click to collapse
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Mr hOaX said:
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Click to expand...
Click to collapse
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
TheHighLife said:
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
Click to expand...
Click to collapse
Boot your device into safe mode https://support.google.com/nexus/answer/2852139?hl=en
Just post some screenshots of the battery (complete overview of graph screen and app list screen) after using your OPO in safe mode atleast for one charge cycle (90%+ down to 10%)
This will help us to figure out what is the exact issue you are facing.
If you are not interested in troubleshooting, just flash fastboot images of this build(CMOS12.1) using following guide
forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
For OnePlus One, about a month ago after systems update, my battery started draining fats and it has gotten worse over the past week. The battery barely holds four hours of after a full charge and the phone gets very hot. Also, over the past week, my main SMS messaging app (SMS) crashes nine out of 10 times -- I can start the app but when I click any of the messages I was to read or type, it freezes and crashes. Also, since yesterday, my phone dilaer crashes very often. Any thoughts/help? I am not familiar with how to flash ROM, etc. Also, since yesterday, charging has been very slow -- overnight, the charge went from 35% full to 74% full. I tried safe mode as well and no luck -- battery still keeps draining at 1% every three minutes.
I have the same issue. Any fixes which work ?