I recently installed this kernel and some question came up. I hope someone can help me answer them
1. I installed the kernel in CWM 6.0.4.4. It said "install complete" When i chose reboot system now it gave me an option to fix root permission i chose go back. It restarted, my n7 boot normally. Did something go wrong during install?
2. I chose BLE=4.2. My n7 would charge to 92% Usually it takes 3h to full charge. So if i charge to only 92% would i need less time to do so? Cause i noticed the charger would cool down when it finished.
3. If i want a full charge i change the value to 0 in the config file right?
4. I can't find the kernel log file. Already tried in /data/tmp but no luck. Even though the settings were applied (checked with cpu spy).
Edit: my mistake. i used a file manager without root access.
5. Can i set different auto voltage for lowest cpu speed 384Mhz without reinstall the kernel and use trickster mod or kernel tunner? Btw i chose 800mv and is it too low? I havent seen any weird problem since then. Just 1 random reboot so far.
P/s1: Thanks for the great kernel @flar2. It worked flawlessly :good:
P/s2: Can someone tell me how to reset the usage time under battery setting because my n7 will never reach a full charged anyway
dichton said:
I recently installed this kernel and some question came up. I hope someone can help me answer them
1. I installed the kernel in CWM 6.0.4.4. It said "install complete" When i chose reboot system now it gave me an option to fix root permission i chose go back. It restarted, my n7 boot normally. Did something go wrong during install?
2. I chose BLE=4.2. My n7 would charge to 92% Usually it takes 3h to full charge. So if i charge to only 92% would i need less time to do so? Cause i noticed the charger would cool down when it finished.
3. If i want a full charge i change the value to 0 in the config file right?
4. I can't find the kernel log file. Already tried in /data/tmp but no luck. Even though the settings were applied (checked with cpu spy).
5. Can i set different auto voltage for lowest cpu speed 384Mhz without reinstall the kernel and use trickster mod or kernel tunner? Btw i chose 800mv and is it too low? I havent seen any weird problem since then. Just 1 random reboot so far.
P/s1: Thanks for the great kernel @flar2. It worked flawlessly :good:
P/s2: Can someone tell me how to reset the usage time under battery setting because my n7 will never reach a full charged anyway
Click to expand...
Click to collapse
I'm not a big fan of cwm, I prefer twrp myself, but I do have an old phone with cwm and it used to ask me the same thing, after I flashed just about anything, whichever option I chose made no difference, my root was never broken. As long as aroma didn't bomb out on you, I'd say your good.
The elementalx.config file is located in system/etc.
My minimum voltage is 750, and I haven encountered any instability, but I've heard such things can very from device to device. CPU binning etc.
Not sure about changing minimum voltage, without reflashig kernel, as I'm a set it and forget it kinda guy, but I would look somewhere in sys/devices/system
The battery stats will reset when the tablet completely dies, probably another way, but I don't use the battery saver, so idk. And yes its 0 under the elementax.config to disable (it has instructions in the file). I believe that it actually changes the charging voltage, but I'm not sure about that, if it does tho it would take the same amount of time to reach 92% as it would to reach 100 with it disabled don't quote me on that one tho
And yes the elemenalx kernel is pretty sweet, flar2 is a kernel god.
thisguysayswht said:
I'm not a big fan of cwm, I prefer twrp myself, but I do have an old phone with cwm and it used to ask me the same thing, after I flashed just about anything, whichever option I chose made no difference, my root was never broken. As long as aroma didn't bomb out on you, I'd say your good.
The elementalx.config file is located in system/etc.
My minimum voltage is 750, and I haven encountered any instability, but I've heard such things can very from device to device. CPU binning etc.
Not sure about changing minimum voltage, without reflashig kernel, as I'm a set it and forget it kinda guy, but I would look somewhere in sys/devices/system
The battery stats will reset when the tablet completely dies, probably another way, but I don't use the battery saver, so idk. And yes its 0 under the elementax.config to disable (it has instructions in the file). I believe that it actually changes the charging voltage, but I'm not sure about that, if it does tho it would take the same amount of time to reach 92% as it would to reach 100 with it disabled don't quote me on that one tho
And yes the elemenalx kernel is pretty sweet, flar2 is a kernel god.
Click to expand...
Click to collapse
I have found a way to reset battery usage: delete batterystat.bin file. so simple
P/s: Please close this thread. :good:
dichton said:
I have found a way to reset battery usage: delete batterystat.bin file. so simple
Click to expand...
Click to collapse
This has no use whatsoever :good:
dichton said:
I have found a way to reset battery usage: delete batterystat.bin file. so simple
P/s: Please close this thread. :good:
Click to expand...
Click to collapse
Sounds like you enabled battery extender when you set up the kernel. What this does is stop the charging around 94% (or so) to extend you batteries life. It does this by stopping the battery from getting to full charge and saving a cycle as the battery is good for only so many cycles.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
dichton said:
2. I chose BLE=4.2. My n7 would charge to 92% Usually it takes 3h to full charge. So if i charge to only 92% would i need less time to do so? Cause i noticed the charger would cool down when it finished.
Click to expand...
Click to collapse
Yes, it will be faster. It will actually need less than 92% of the normal time, since the charge current tapers off towards the end.
3. If i want a full charge i change the value to 0 in the config file right?
Click to expand...
Click to collapse
Yes. Or if you want to do it temporarily, you can just write 4300 to
/sys/devices/i2c-0/0-006a/float_voltage
That will get reset to the config file value during the next reboot.
5. Can i set different auto voltage for lowest cpu speed 384Mhz without reinstall the kernel and use trickster mod or kernel tunner? Btw i chose 800mv and is it too low? I havent seen any weird problem since then. Just 1 random reboot so far.
Click to expand...
Click to collapse
Don't bother. It doesn't help with power consumption, the Snapdragon does automatic voltage scaling. You can get instability though, since this will be the starting point for the voltage scaling.
Pfeffernuss said:
dichton said:
I have found a way to reset battery usage: delete batterystat.bin file.
Click to expand...
Click to collapse
This has no use whatsoever :good:
Click to expand...
Click to collapse
IIRC, the hardcoded reset conditions in the battery manager service are 100% reached or 80% charge performed (e.g. going from 12% to 92%). Deleting
'/data/system/batterystats.bin'
will also do a reset, but you must do it in recovery. If you do it while booted up, it just gets rewritten. TWRP recovery has a file browser under 'Advanced' that you can use to delete the file.
Related
I just started running the latest (not sure what it is, but I got it this weekend - 10/30/10) version of XDAndroid.
I am a little disappointed with the life of the battery... I charged it fully last night and drove to work with it in the car charger. I don't take my cell phone into work, so I put into airplane mode and left it in a cool area (like have always done with the same phone running WinMo 6.5.) I checked to make sure there were no apps running also.
When I went out for lunch, I was surprised to find that the phone was still warm and the battery indicator was down 25%. After lunch (I did not even use it) the phone was warning me that it only had 15% life left (and it was still warm.)
I put it into airplane mode after lunch - we'll see where is stands on my way home, but my guess is that it will be completely dead.
The same phone running WinMo 6.5 (and the same battery) can last for days like this...
Is this a common problem? (I have not found anything to this effect other than the battery meter being unreliable.)
Is there something I could check or do?
I am using the app to launch the OS and it has my over-clocking set at "Medium" ("Hi" froze my phone.) I'm planning on trying "Normal" tomorrow to see if there is any difference in battery life.
thanks in advance,
Jordan
There's gotta be something running in the background, otherwise the phone would be cool.
Make sure you're completely up to date - some of the bundle packages have old pieces in them. Sometimes it's OK, other times it means your build is very outdated.
I dropped back to the overclocking level before medium, made absolutely sure that all processes were stopped, and the battery was completely dead. It had been on charge until around 10:00 and in Airplane mode with all processes stopped. I checked it around 5:00, but the battery was already dead, so I don't know when it actually died.
Format SD card using any other third party program like Panasonic SD Formatter or what have you > Go here http://sites.google.com/site/androidport/downloads/archive and download any old Android build (Except for Sense 2.1) > Manually update kernals and rootfs > Uncheck Ovclock (Or take out the OC command line in the startup.txt and check the manual startup.txt from the launcher app) > Boot.
You should have great battery life now and phone should stay cool and go into deep sleep (Green LED light).
So are you saying that overclocking is causing the battery life to drain quickly? I can turn it off with the installer that I am using.
jordanthompson said:
So are you saying that overclocking is causing the battery life to drain quickly? I can turn it off with the installer that I am using.
Click to expand...
Click to collapse
Well it would stand to reason that OVERclocking a processor would degrade battery life & stability.
well to be honest you are not going to get great battery life out of android on the tp2...yet. On WM with normal use I get about a little over a full day, android max is like 7-8 hours. The battery life has made great strides though recently and I'm sure will eventually be usable for a full day.
Try a program from the market called juice defender, it literally doubles my battery life when running android, should help with your heat issues as well
Thanks very much for the helpful advice - I'll look for it tomorrow and let you know how I make out
iamterence said:
Format SD card using any other third party program like Panasonic SD Formatter or what have you > Go here http://sites.google.com/site/androidport/downloads/archive and download any old Android build (Except for Sense 2.1) > Manually update kernals and rootfs > Uncheck Ovclock (Or take out the OC command line in the startup.txt and check the manual startup.txt from the launcher app) > Boot.
You should have great battery life now and phone should stay cool and go into deep sleep (Green LED light).
Click to expand...
Click to collapse
Is it really necesarry to manually update the kernals and rootfs or can sov's XDAndroid startup utility be used to update them?
slapshot30 said:
Is it really necesarry to manually update the kernals and rootfs or can sov's XDAndroid startup utility be used to update them?
Click to expand...
Click to collapse
Its not really necessary, but you'll know for a fact that your build's up to date. Thats what I do anyways.
iamterence said:
Its not really necessary, but you'll know for a fact that your build's up to date. Thats what I do anyways.
Click to expand...
Click to collapse
Am I correct with these steps on how to do it manually?
1) Download the latest kernal and rootfs that you want to update
2) Unpack the rootfs file to desktop and copy it into andboot and rename it rootfs and delete the old one.
3) Unpack the kernal to the desktop and send the module into andboot but DO NOT rename (Delete old).
Rename the zImage file to just zImage and put it into andboot and delete the old one.
lemeiux1 said:
well to be honest you are not going to get great battery life out of android on the tp2...yet. On WM with normal use I get about a little over a full day, android max is like 7-8 hours. The battery life has made great strides though recently and I'm sure will eventually be usable for a full day.
Try a program from the market called juice defender, it literally doubles my battery life when running android, should help with your heat issues as well
Click to expand...
Click to collapse
My tp2 oc'ed at 768 runs for days in android. maybe its cuss i got the rhod400?
immson said:
My tp2 oc'ed at 768 runs for days in android. maybe its cuss i got the rhod400?
Click to expand...
Click to collapse
Days? In Android?!? You must not be doing... anything. Plus have every radio turned off or something.
Wistilt2 was saying he was getting around 36 hours at peak, but that was basically all sleep.
I get 10 hours if I'm lucky, but lately it's just been dying out of nowhere and shutting off completely. Not sure what's up with that...
lemeiux1 said:
well to be honest you are not going to get great battery life out of android on the tp2...yet. On WM with normal use I get about a little over a full day, android max is like 7-8 hours. The battery life has made great strides though recently and I'm sure will eventually be usable for a full day.
Try a program from the market called juice defender, it literally doubles my battery life when running android, should help with your heat issues as well
Click to expand...
Click to collapse
The settings in that app are kind of confusing. Which settings do you use and do you use the free version or paid version. It seems some features are blocked out on the free version, do I really need the ones blocked out?
Manually Updating XDAndroid & Power Management
slapshot30 said:
Am I correct with these steps on how to do it manually?
1) Download the latest kernal and rootfs that you want to update
2) Unpack the rootfs file to desktop and copy it into andboot and rename it rootfs and delete the old one.
3) Unpack the kernal to the desktop and send the module into andboot but DO NOT rename (Delete old).
Rename the zImage file to just zImage and put it into andboot and delete the old one.
Click to expand...
Click to collapse
Your post may seem OT but since current updates can be related to better power management its very relevant.
1) Yes, if you are getting:
Kernels & modules from dev glemsom: http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Rootfs from dev stinebd: http://files.xdandroid.com/rootfs/
2) After unpacking / extracting rootfs-xxxx.zip either on desktop or Rhodium (using 7-Zip for WM [it's Free]) rename it "rootfs.img"
3) Yes. You can also unpack / extract the kernel & module archive htc-msm-linux-xxxx.tar.bz2 on Rhodium using 7-Zip for WM.
Equally important is using latest XDAndroid System. If your using Sov's Startup utility (make certain your using latest version as of this post 1.3.1) and his latest "reference" build, not Blazin, you will be current with the latest XDAndroid System [2.2] [25-10-10] (Oct. 25, 2010) FRX02 aka system.ext2 NOTE: If you update the system file you will need to delete the data.img file and that means loosing all your configs, downloads, & customizations. Using Titanium Backup makes this a little less painful.
Battery life is directly related to how you use your device. Some power hogs include overclocking, videos, and services such as GPS, WiFi, Data, & Voice. Many concerned with extending battery life underclock. Personally I don't subscribe to OC or UC.
arrrghhh said:
Days? In Android?!? You must not be doing... anything. Plus have every radio turned off or something.
Wistilt2 was saying he was getting around 36 hours at peak, but that was basically all sleep.
I get 10 hours if I'm lucky, but lately it's just been dying out of nowhere and shutting off completely. Not sure what's up with that...
Click to expand...
Click to collapse
mine too, i updated it like half a month ago. i guess somehow it glitched and had super battery. anywhere from 6 to 8 hours is what i get until out of no where, nothing.
jordanthompson said:
I just started running the latest (not sure what it is, but I got it this weekend - 10/30/10) version of XDAndroid.
I am a little disappointed with the life of the battery... I charged it fully last night and drove to work with it in the car charger. I don't take my cell phone into work, so I put into airplane mode and left it in a cool area (like have always done with the same phone running WinMo 6.5.) I checked to make sure there were no apps running also.
When I went out for lunch, I was surprised to find that the phone was still warm and the battery indicator was down 25%. After lunch (I did not even use it) the phone was warning me that it only had 15% life left (and it was still warm.)
I put it into airplane mode after lunch - we'll see where is stands on my way home, but my guess is that it will be completely dead.
The same phone running WinMo 6.5 (and the same battery) can last for days like this...
Is this a common problem? (I have not found anything to this effect other than the battery meter being unreliable.)
Is there something I could check or do?
I am using the app to launch the OS and it has my over-clocking set at "Medium" ("Hi" froze my phone.) I'm planning on trying "Normal" tomorrow to see if there is any difference in battery life.
thanks in advance,
Jordan
Click to expand...
Click to collapse
As long as I observe, in my case at least, the screen's backlight never turns OFF. The screen became black, but the light behind it is always ON, the only way to see this is in complete dark, otherwise all you can see is a black screen. Try it. In my case I'm shure this is at least one reason for short battery life under xandroid on my tp2. Interesting under windows the screen backlight is turning OFF in stand by mode.
As long as I observe, in my case at least, the screen's backlight never turns OFF. The screen became black, but the light behind it is always ON, the only way to see this is in complete dark, otherwise all you can see is a black screen. Try it. In my case I'm shure this is at least one reason for short battery life under xandroid on my tp2. Interesting under windows the screen backlight is turning OFF in stand by mode.
Click to expand...
Click to collapse
I'm know what you mean i also have this same problem. When I first loaded Android 2.2.1 onto my SD card the sleep mode was working correctly for around 1 week or so. During that time I had a few crashes of Android, due to applications etc, and now its like u said. The screen is black but still 'on' in sleep mode.
Sent from my MSM using the XDA mobile application powered by Tapatalk
Just to add another field report...
I installed the "Battery Left" Widget, wich logs battery life and calculates an average. I'm always running on 3G or even WiFi if I am at Home and my average is about 30 hours a charge. If i'm doing nothing it gets this maximum battery life. But in normal day use with writing an email sometimes and doing a call it's about 10-12 hours. If i am at work and i use Navigation between my customers (between 1 and 3 hours one way), i always charge the phone while navigating and deactivate GPS when i'm not using it, i get 10 hours with a full charged battery at the morning. Currently i'm using the 11/24 kernel and the 11/08 rootfs modified to fit my german keyboard layout. Furthermore i'm using the newest combination of [ACL]'s tweaked 3D Driver and gralloc. No overclocking (no need for that, caus android is running good at stock speed) and pm.sleepmode set to 1.
Hope that is not a useless reply
Cheers
Hi sounds Nice.
Can u send me your updates files ?
German keyboard is nice for me.
Mit freundlichen grüssen
i'm having battery consumption issues, and somewhere on the forum the guys talked about a widget that shows current battery discharge amount in ma (miliamps). so i installed the widget and it shows 44ma no matter what i did, i turned on everything, and then all off, changed radios, changed roms(was using leedroid2.2f then flashed opendesire4.0.36)...
what ever i did, 44ma was the number showed by the widget. i installed another widget, and it gave the same number...
any one has any clue about this?
also yesterday i charged the phone to the point where the lock screen said it was "Charged". but i didn't unplug the charger, 30 minutes later "CurrentWidget" changed the number from 44ma to 8ma, so i thought, maybe now its fully charged.
used the phone for a while(maybe used up 10% or a bit more), and then "CurrentWidget changed back to 44ma, and its been the same since then.
now my battery's at about 40%, and its the same still...
anyone??!!
BumpbumpBumP.
search for power tutor in market
mariosraptor said:
search for power tutor in market
Click to expand...
Click to collapse
I installed it and it gave the same reading (44mah).
The problem is i want to know what it means for the reading to be the same at any given point. Whether the screen is on or off, or the cpu is at 1Ghz or at 652Ghz(using setcpu).
Can someone shed some light here please?
mean no disrespect!! do you wipe when you flash roms? try to wipe battery stats also. do you use a task killer that somehow prevents the system from reading correctly? i know that this might sound dumb but you never know, i have seen alot of weirdness from the last expected.
edit:do you use setcpu profiles? if yes try and deactivate profiles or change governors.
jaikat said:
I installed it and it gave the same reading (44mah).
The problem is i want to know what it means for the reading to be the same at any given point. Whether the screen is on or off, or the cpu is at 1Ghz or at 652Ghz(using setcpu).
Can someone shed some light here please?
Click to expand...
Click to collapse
mariosraptor said:
mean no disrespect!! do you wipe when you flash roms? try to wipe battery stats also. do you use a task killer that somehow prevents the system from reading correctly? i know that this might sound dumb but you never know, i have seen alot of weirdness from the last expected.
edit:do you use setcpu profiles? if yes try and deactivate profiles or change governors.
Click to expand...
Click to collapse
i really appreciate the help you guys are offering... thanks.
alright, i'll tell you what i did:
1- i wiped everything (data, cache, ext, dalvik)
2- flashed the rom (defrost 6.1a)
3- after everything was up and running i charged the phone to the point where clarus battery(battery info widget) showed the phone was charged, also current widget changed the reading from 44 to 8 mah at this point.
4- rebooted into recovery and wiped battery stats
after i used the phone for a while and the battery lost about 10% or more, current widget went back to showing 44mah, all the way to the moment my phone turned off by itself cause the battery was empty (this was almost 18 to 20 hours later)
i use setcpu, the cpu speed is set to 245-728 using the On-demand governor. and there's one profile set for when the phone is on standby(screen is off), that one is set to 245-530(approximate) using either the conservative or the On-demand governors.
another thing is autobrightness, which i have turned OFF.
and lastly, i don't use a taskkiller, and i advise anyone not to use one as i got better battery life without one...(anyone who reads this, try it and see for yourself)..
the amount of the mah current being used by my phone is whats bugging me, i'v read another topic where people who were using Desire phones and the current widget were getting 25-40 when using the phone, and 3-8 when the phone was idle. but in my case, the number is always the same...
too much talking i know, forgive me, but this is in case anyone who wants to help has other questions ...
Hello.
I've just installed android on my HTC Tytn II (Not so Super Froyo Release).
It is very nice but the battery life is very short. I don't think that i can manage for one day without recharging. I think a couple of hours just. Is there something i can do to improve this? When i entered the #*#*4636*#*# it says that the android system is the one that keeps the processor running when in stand by. what can i do?
And another question. How is it better to install. On nand system and data? For now, i've installed data on external data.img. But there is not much room for aplications. Is it better if i install data on sd partition? And if so....how do i do that?
blacki3 said:
Hello.
I've just installed android on my HTC Tytn II (Not so Super Froyo Release).
It is very nice but the battery life is very short. I don't think that i can manage for one day without recharging. I think a couple of hours just. Is there something i can do to improve this? When i entered the #*#*4636*#*# it says that the android system is the one that keeps the processor running when in stand by. what can i do?
And another question. How is it better to install. On nand system and data? For now, i've installed data on external data.img. But there is not much room for aplications. Is it better if i install data on sd partition? And if so....how do i do that?
Click to expand...
Click to collapse
If the processor is still running while in standby then that means you have a widget or program running that's preventing the phone from going to sleep. When you install an app in Android always look for "Prevents Phone from Sleeping" where the app installer says what the app requires to access.
Also, as I have said in the help thread, there is nothing you can do about the battery life. It's Kernel related and being investigated, so until that time unfortunately battery life is very short because the phone's CPU while not in standby runs at 100% speed, unlike all other android phones which decrease their CPU speed and voltage when they are idle (sitting at the home screen or even checking emails).
Also, if you are installing into a data.img file on your SD Card, you should have about 256MB of usable space in /data, if you are running out of space with just a few applications, then you are still installing on NAND, as it only has about 90-100MB available depending on how you have your NAND partitioned, please verify that you have fstab set correctly in atools and re-flash your firmware so that it reads the /data partition under data.img instead of NAND p3.
BEst thing to do if you are wanting to install /data on SD Card (or data.img), is have /system on your NAND for best performance when Android is loading from boot. For quick performance, you should have /data and /system on NAND. For more space and stability, go with /system on NAND and /data on either SD Card partition or data.img.
Thank you for the answer.
I have another problem...when i'm recharging the phone...it says that it is fully charged at 90%.
blacki3 said:
Thank you for the answer.
I have another problem...when i'm recharging the phone...it says that it is fully charged at 90%.
Click to expand...
Click to collapse
That means there is a incorrect battery calibration number in the kernel. Run atools and check under Battery Settings > Advanced Settings. If you have a 1350mAH battery (noted on the battery itself), input 2160 units.
If you have any other type of battery, take that battery's mAH and multiply it by 1.6 to get the battery units. If the battery continues to stop at 90% after making that change, and the battery is old, then the battery may be losing it's charge and can only sustain up to 90% of it's core charge.
Thank you. now i'm trying with 2160 set in atools. i will inform you if something is wrong
Another question. How can i see the battery status in %?
i think now it's ok. but still the battery life is very short. and somethig is keeping the android from sleeping but i don't know what. when i enter in the *#*#4636#*#* it says that the "android system" is the one that prevents from sleeping.
And another question. What is the difference between panels. If i am installing with panel 1 the screen looks very bad. Now i've installed with panel 3 but i don't see any difference from panel 2. It is ok that i've installed with panel 3 or should i use panel 2?
I need to know how you set your phone up, including kernel, system/data partitions, which build you used, what radio you're using, anything that could help me investigate further.
I have 2 AT&T Tilt phones, one for daily use and the other for testing purposes only. (nice to have friends with connections, I got them both for free).
My current "daily use" phone will use about 1/2 battery per day with moderate use (texting/Pandora/phone calls) and will last 3 1/2 days if I just let it sit in standby. 3G is enabled and I use Rogue Tools to O/C to 480. I get almost no FC errors and everything works as it should. (The only FC I get is with ADW, which I press "wait" and it comes right back). I was able to set up my phone on the wireless domain at work and ported my work email to it.
Again, I would need to know what you're running as it sounds like your phone is not actually "sleeping" when it should.
PoXFreak said:
I need to know how you set your phone up, including kernel, system/data partitions, which build you used, what radio you're using, anything that could help me investigate further.
I have 2 AT&T Tilt phones, one for daily use and the other for testing purposes only. (nice to have friends with connections, I got them both for free).
My current "daily use" phone will use about 1/2 battery per day with moderate use (texting/Pandora/phone calls) and will last 3 1/2 days if I just let it sit in standby. 3G is enabled and I use Rogue Tools to O/C to 480. I get almost no FC errors and everything works as it should. (The only FC I get is with ADW, which I press "wait" and it comes right back). I was able to set up my phone on the wireless domain at work and ported my work email to it.
Again, I would need to know what you're running as it sounds like your phone is not actually "sleeping" when it should.
Click to expand...
Click to collapse
So...the radio is 1.70.09.1 or something like that, the latest 2.6.32 kernel. android build is valentine. I am using system on NAND and data on data.img. now i can use the phone for a full day of use but i have other problems. when i charge the phone it freeze and white screen appears. Usually i left for charge at night so in the morning i find it with white screen.
Can u please tell me what are you using so i can use to?
Thank you in advance
Battery life
blacki3 said:
So...the radio is 1.70.09.1 or something like that, the latest 2.6.32 kernel. android build is valentine. I am using system on NAND and data on data.img. now i can use the phone for a full day of use but i have other problems. when i charge the phone it freeze and white screen appears. Usually i left for charge at night so in the morning i find it with white screen.
Can u please tell me what are you using so i can use to?
Thank you in advance
Click to expand...
Click to collapse
I've the same problem of battery life, can you tell me how to improve the fix for this issue...thanks
Hi all,
I am using CM7.2(FXP106) on my Xperia arc, with the kernel that comes with it. But I find out that battery drain is much more worse than the stock. 42 ROM. I usually charge the phone to 100% before I sleep, and the phone only uses 3% during my sleep with stock ROM. (stock kernel, cpu is downclocked to 768MHz when screen is off, using conservative governor.) However with CM7.2 my phone consumes more than 10% during my sleep. I also downclock the cpu to 768MHz when screen is off the cpu governor is smartassv2. In battery usage, mobile standby and phone idle consume the most. lol (It used to be display with stock rom) Is there any possible workaround? thanks a lot.
Ivan
ok, i try to give you a view points to check:
read and install this on your phone. I had also a battery-drainer on my phone. i found it and now i´m happy
One time, on my x10miniPro the facebook app drain my battery.
Have you clear dalvik-cache before you install the rom? full wipe?
I installed many custom-roms at my x10 miniPro. Sometimes i have also fast battery drain. Then i made a second time a full wipe, clear dalvik cache and install the rom new. This fixed most of the problems.
try this and report
I had the same issue, but they closed the Issue at the project-page:
http://code.google.com/p/freexperia...tatus Priority Milestone Owner Summary&id=155
for this reason i changed to Arconium, and.... 1% during a whole night in flight mode, with FXP it was about 10%!
i really miss the additional settings from CM7 but as long as this Problem exists , even if they say its normal, i wont switch back.
I had exactly the same problem whith CM7.2 FXP107
It was "Cell standby" (I'm not sure it's how it's called in english) that was anormally draining battery. It may be linked to baseband (I was using 64 one).
I had wiped everything possible before, flashed with CM7.2 kernel.
So I swiched to Arconium 7 + DoomKernel 0.18 + baseband 36 with patches. No problem since.
I don't know where the problem came from, it didn't took time to investigate, it was to much of a drain to keep my phone like this.
Boudin said:
It may be linked to baseband (I was using 64 one).
I had wiped everything possible before, flashed with CM7.2 kernel.
.
Click to expand...
Click to collapse
i also tried Baseband -36 and -56 no difference, Full Wipe Battery Calibration and so on, but nothing changed.
There is no excssive battery drain on CM7.
Flash latest kernel, try different basebands, calibrate the battery sometimes (correct calibration !) and you won't have battery drain anymore.
I lose about 1,5 % in deep sleep and about 5 % with heavy (e.g. streaming, gaming).
dp94 said:
I lose about 1,5 % in deep sleep and about 5 % with heavy (e.g. streaming, gaming).
Click to expand...
Click to collapse
per hour?
now i lose 1% in 8h flight mode, with FXP it was 10 times more!
drcyber said:
per hour?
now i lose 1% in 8h flight mode, with FXP it was 10 times more!
Click to expand...
Click to collapse
Of course per hour.
I haven't tested flight mode yet (completely useless, imo).
I don't expect any wonders, I can use my device a whole day with everything I want to do without a fear of battery dead.
dp94 said:
Of course per hour.
I haven't tested flight mode yet (completely useless, imo).
Click to expand...
Click to collapse
as i use my Phone as alarm clock its very usefull
I don't expect any wonders, I can use my device a whole day with everything I want to do without a fear of battery dead.
Click to expand...
Click to collapse
but for me a whole day in 3g was not bossible with fxp, after 10 hours of medium use, it was over.
(with 3 you cant switch to 2g in bigger cities in Austria)
drcyber said:
as i use my Phone as alarm clock its very usefull
Click to expand...
Click to collapse
Okay, then I'll understand you.
I miss those old devices, where the alarm worked, even when the device was powered off.
drcyber said:
but for me a whole day in 3g was not bossible with fxp, after 10 hours of medium use, it was over.
Click to expand...
Click to collapse
Really? I've constantly 3G on.
Try the things I've described above.
drcyber said:
(with 3 you cant switch to 2g in bigger cities in Austria)
Click to expand...
Click to collapse
Switch to the best operator in your country.
I don't want to avertise here.
dp94 said:
Okay, then I'll understand you.
I miss those old devices, where the alarm worked, even when the device was powered off.
Click to expand...
Click to collapse
in this case: YES
Really? I've constantly 3G on.
Try the things I've described above.
Click to expand...
Click to collapse
what type of calibration do you mean? the app? i tried both , the app and i found somwhere here a description with full charge, cwm and so on, but i did not help , not even a bit.
Switch to the best operator in your country.
Click to expand...
Click to collapse
and pay the double Price of my package? No Way.
drcyber said:
what type of calibration do you mean? the app?
Click to expand...
Click to collapse
No, there's somewhere a description.
I don't really remember right now and too lazy to describe.
I'll look it up for you, when I get home from work.
drcyber said:
and pay the double Price of my package? No Way.
Click to expand...
Click to collapse
It's a pity that's an argument.
Sent from my LT18i using xda premium
Today when i came home i got a letter from your best provider, but adsl-section.. > they want more money...
Gesendet von meinem LT15i mit Tapatalk
drcyber said:
Today when i came home i got a letter from your best provider, but adsl-section.. > they want more money
Click to expand...
Click to collapse
PM me, I work at this very operator (in IT Outsourcing, but company is company).
EDIT: There you go (instead of xRecovery use CWM).
If this doesn't help either, here are more options.
ooidort said:
STEPS:
1. Download and install xRecovery from here.
2. Charge your phone to 100%
3. Turn off the phone and boot into recovery
4. In recovery, go to Advanced options --> Wipe Battery Stats --> Yes
5. Take the battery off
6. Insert the charger chord
7. Put the battery back and wait for the phone to boot
8. Once the phone boots up, you will notice that the battery percentage is around 88% instead of 100%
9. Charge the phone back to 100%
10. Repeat 4-5 times, seems to be the sweet spot
11. Enjoy your hopefully better battery life and report!
Click to expand...
Click to collapse
Sent from my LT18i using xda premium
Thx for the Guide , but this doesnt work for me, once i had 82% after the first reboot , but now my phone doesnt boot automatically when i re insert the Battery, there is just a charging Symbol. when i boot manually , i have 100% battery.
You can use Toggle 2G with CM ROMs, pretty good in saving battery, you can set data to switch to 2G after certain minutes after the screen is off.
http://forum.xda-developers.com/showthread.php?t=739530
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
TiTAN-O-One said:
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Well, try to discharge your phone until it fully drained, and charge your phone until it reaches to 100%, should be powered of,unplug, then use it the normal way, until it fully discharge and do the same, for at least 3 charging cycles.
Or charge your phone to 100% then before unplugging, go to /data/system and removed batterystats.bin.
I hope it will help, the first step is I think the most accurate, than using such apps.
Thank you,
TiTAN-O-One said:
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
jakelq said:
Well, try to discharge your phone until it fully drained, and charge your phone until it reaches to 100%, should be powered of,unplug, then use it the normal way, until it fully discharge and do the same, for at least 3 charging cycles.
Or charge your phone to 100% then before unplugging, go to /data/system and removed batterystats.bin.
I hope it will help, the first step is I think the most accurate, than using such apps.
Thank you,
Click to expand...
Click to collapse
honeyx said:
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
Click to expand...
Click to collapse
Good stuff here! thanks! Gonna try these stuffs out!:thumbup:
Sent from my GT-S6500 using xda app-developers app
honeyx said:
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
Click to expand...
Click to collapse
thanked for the info on latest cm9 battery performance
TiTAN-O-One said:
Good stuff here! thanks! Gonna try these stuffs out!:thumbup:
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
You might take a look on this one too when speaking of battery calibration:
http://forum.xda-developers.com/showthread.php?t=1460553
Calibration with apps by wiping battery stats is useless.
Battery in cm9 eol and cm9 rc3
Does battery of cm9 eol same like battery of cm9 rc 3 with honeyx's kernel and also how long the battery can last from 100% to 0%?
Bcoz I feel like my battery drop frm 100% until 87% in about 1 hour use cm9 rc3 with honeyx 's kernel...
Sorry my English so BAD
w4nkh4iri said:
Does battery of cm9 eol same like battery of cm9 rc 3 with honeyx's kernel and also how long the battery can last from 100% to 0%?
Bcoz I feel like my battery drop frm 100% until 87% in about 1 hour use cm9 rc3 with honeyx 's kernel...
Sorry my English so BAD
Click to expand...
Click to collapse
It´s nearly the same. Not exactly the same, but nearly the same, so it will not become better if you switch to CM9 EOL but probably a little bit worse. All depends to your battery health and how you are using your device.
I find the 2.6 kernel still a little bit better when it comes to battery life than the one in the final CM9, but since the differences are really small I´m already using the final release with a modified kernel.
This kernel has a few more optimizations for battery life and I will launch it quite soon after some more tests are done.
Don´t know how you are using your device and what apps are installed on your phone, but if your WiFi and Mobile Data is always on, there are a lot of apps running in the background and you are very often using your phone, your results are still very good.
Else better replace your battery with a new one, as there is no kernel that will turn a bad battery into a shiny new one.
honeyx said:
It´s nearly the same. Not exactly the same, but nearly the same, so it will not become better if you switch to CM9 EOL but probably a little bit worse. All depends to your battery health and how you are using your device.
I find the 2.6 kernel still a little bit better when it comes to battery life than the one in the final CM9, but since the differences are really small I´m already using the final release with a modified kernel.
This kernel has a few more optimizations for battery life and I will launch it quite soon after some more tests are done.
Don´t know how you are using your device and what apps are installed on your phone, but if your WiFi and Mobile Data is always on, there are a lot of apps running in the background and you are very often using your phone, your results are still very good.
Else better replace your battery with a new one, as there is no kernel that will turn a bad battery into a shiny new one.
Click to expand...
Click to collapse
Ok,mybe i install all of apps that i use...Can i use ur kernel that ur modified with final cm9?? ..just wanna use it...and thanx
Sorry my English so BAD
w4nkh4iri said:
Ok,mybe i install all of apps that i use...Can i use ur kernel that ur modified with final cm9?? ..just wanna use it...and thanx
Sorry my English so BAD
Click to expand...
Click to collapse
Sure, you just have to wait a bit till I release it as i need to test it for stability before launching it and am doing this for a couple of days to be 100% sure.
honeyx said:
Sure, you just have to wait a bit till I release it as i need to test it for stability before launching it and am doing this for a couple of days to be 100% sure.
Click to expand...
Click to collapse
Great,thanx u for share ur kernel..i can't waiting to using it
but i dont understand to battery life extender
" Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions."
Mean that change value before flash kernel??
Sorry my English SO BAD
w4nkh4iri said:
Great,thanx u for share ur kernel..i can't waiting to using it
but i dont understand to battery life extender
" Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions."
Mean that change value before flash kernel??
Sorry my English SO BAD
Click to expand...
Click to collapse
No problem, but wrong thread. You can´t change this value before flashing the kernel as it doesn´t exist before flashing a kernel that supports battery life eXtender. So only possible to change this after flashing it.
honeyx said:
No problem, but wrong thread. You can´t change this value before flashing the kernel as it doesn´t exist before flashing a kernel that supports battery life eXtender. So only possible to change this after flashing it.
Click to expand...
Click to collapse
Sorry bcoz ask u in wrong thread. Mean that, after i flash kernel,go to rootexplorer and change it and last reboot...if i wrong please correct to me
Sorry my English so BAD
w4nkh4iri said:
Sorry bcoz ask u in wrong thread. Mean that, after i flash kernel,go to rootexplorer and change it and last reboot...if i wrong please correct to me
Sorry my English so BAD
Click to expand...
Click to collapse
Just change it without rebooting afterwards. If you reboot after changing this value, it will be reset to the default value (100).
So to permamently change this value on each reboot you need to use a tool that will do this for you at each booting. Don´t remember which app is actually supporting BLX, but there is one that will do this for you.
honeyx said:
Just change it without rebooting afterwards. If you reboot after changing this value, it will be reset to the default value (100).
So to permamently change this value on each reboot you need to use a tool that will do this for you at each booting. Don´t remember which app is actually supporting BLX, but there is one that will do this for you.
Click to expand...
Click to collapse
So flash kernel and reboot.After that,go to rootexplorer and change value...but how about after flashing the kernel whipe your cache and dalvik cache and fix permissions???
w4nkh4iri said:
So flash kernel and reboot.After that,go to rootexplorer and change value...but how about after flashing the kernel whipe your cache and dalvik cache and fix permissions???
Click to expand...
Click to collapse
No. Go to CWM recovery. Flash kernel. Stay in CWM Recovery, whipe cache, whipe dalvik cache and fix permissions. Reboot. Then you can use root explorer to change the BLX value once it has booted.
honeyx said:
No. Go to CWM recovery. Flash kernel. Stay in CWM Recovery, whipe cache, whipe dalvik cache and fix permissions. Reboot. Then you can use root explorer to change the BLX value once it has booted.
Click to expand...
Click to collapse
Mean that,that BLX exist when after flash kernel and whipe cache,whipe cache, whipe dalvik cache and fix permissions.
Now,I feel like i see that how to use BLX. Thanx u.
So my English Bad