Related
Hi guys.
I have a strange problem. My Gio charges from 3% to 100% in 3 minutes. It says fully charged...
Of course it's not real charging, if i unplug it, and start to play a game or just see my mails with wifi, it consumes that 100% on 5-10 minutes...
I've tried to charge the phone all night and the result is 2-3h of working time. If i use power consuming apps, like games, than it's just half an hour... I think that the phone stops somehow the charging process if it reaches to 100%.
I've tried to calibrate the battery, with program from market, and wiping batterystats from CWM too... It didn't help...
The strange thing is, that last week it worked well. Now something happened and it's ruinig my life...
I had THIS ROM when it started.
I've changed to THIS ROM, and it didn't solve the problem. All caches were wiped during flashing...
Any ideas?
Thanks for any help!
Anybody? Please...
Kuyte said:
Anybody? Please...
Click to expand...
Click to collapse
Hm you said you tried to calibrate the battery so it`s weird. I have sometimes the same problem but after a calibration it is fixed. I can only recommend to charge it overnight , make sure you`re not overclocking it , make sure you don`t use wifi , mobile data , gps , see if there`s an improvement keep it only with calls and messaging for 1 day see how that goes. Check also the battery maybe it has a spillage altough i don`t think that`s the case. Sorry that`s all i can say
Thanks for the advices.
I've just set the CPU governor to smartassv2. It was on Ondemand. Now I can discharge the phone with playing within 15 minutes. It's better than it was on ondemand...
I will try to use it like a regular phone, let's see how it works...
R: [Q] Battery charging too fast
Also, how old is your battery?
Sent from my GT-S5660 using xda app-developers app
ItachiSama said:
Also, how old is your battery?
Click to expand...
Click to collapse
The phone is 1.5 years old. On the battery the date is: 2011/07/26
Flash a stock rom with odin if doesn't solve the issues buy a new battery maybe your's dead.
Sent from my GT-S5660 using xda app-developers app
also remove any apps or games you have installed since you encountered this problem, I have tried enhanced rom it gives a stable battery life, but its worth changing to a different rom like cm 7.2 by phiexz, I am currently using it and it gives a good battery life.
Kuyte said:
The phone is 1.5 years old. On the battery the date is: 2011/07/26
Click to expand...
Click to collapse
I've a battery old as yours (04.05.2011)
With any custom ROM my battery life is of 3 hours...
With stock is kinda 5 hours with 2G connection activated.
I'm waiting for a new battery, but if you want to keep your phone alive up to then:
- flash a stock ROM
- install as few apps as you can (I've G+, Stream (FB client), FB messanger, Viber, WhatsApp, App Cache Cleaner, AppZorter and xda app, nothing else T_T)
- do NOT use kernel different from stock
- hope you good luck because first times battery will be strange, after some full usage and discharge now I've the battery life I told before
Hope this could help
I have galaxy gio and it problem is whaen i charge my galaxy gio 3 min later to touch to 100 percent and then i plug out and on it then it show battery is zero
My battery life is considerably worse on jellybean aosp roms (I tried both the 4.1 and 4.2 version) than it was with stock ICS, and stock jellybean with sense, I'm sure that the battery lasted at least twice as much than it does now. I'm getting around 7-8 hours with a screen time of 2 - 2.5 hours at maxiumum, screen brightness at 50%, location turned off. It's clearly a software problem since the battery life with stock rom is so much better. Something must be wrong since everyone is reporting great battery life with the latest jellybean aosp rom.
Constantine. said:
My battery life is considerably worse on jellybean aosp roms (I tried both the 4.1 and 4.2 version) than it was with stock ICS, and stock jellybean with sense, I'm sure that the battery lasted at least twice as much than it does now. I'm getting around 7-8 hours with a screen time of 2 - 2.5 hours at maxiumum, screen brightness at 50%, location turned off. It's clearly a software problem since the battery life with stock rom is so much better. Something must be wrong since everyone is reporting great battery life with the latest jellybean aosp rom.
Click to expand...
Click to collapse
I think you maybe hurrying to a conclusion.
After you flash the flash the ROM, wipe battery stats in cwm. Then let the ROM settle ( atleast 2 charge cycles ) .
Then see if you have the same battery problem
Constantine. said:
My battery life is considerably worse on jellybean aosp roms (I tried both the 4.1 and 4.2 version) than it was with stock ICS, and stock jellybean with sense, I'm sure that the battery lasted at least twice as much than it does now. I'm getting around 7-8 hours with a screen time of 2 - 2.5 hours at maxiumum, screen brightness at 50%, location turned off. It's clearly a software problem since the battery life with stock rom is so much better. Something must be wrong since everyone is reporting great battery life with the latest jellybean aosp rom.
Click to expand...
Click to collapse
I'm on ice cold jelly 2.2 with the XML kernel #141repacked for the ROM. I get a steady 3 hours screen on time. Give that combo a try. Also the first few days the kernel and ROM have to settle so don't be too quick to judge it.
Sent from my HTC One X using xda premium
{< r o N o $ said:
I think you maybe hurrying to a conclusion.
After you flash the flash the ROM, wipe battery stats in cwm. Then let the ROM settle ( atleast 2 charge cycles ) .
Then see if you have the same battery problem
Click to expand...
Click to collapse
Thank you so much! I have deleted the battery stats file in cwm and it is immediately obvious that the battery life has improved.I can't believe how easy the fix was.
Sorry for the replies, but: the battery stats wipe is useless...
The file that you've removed is a file which contains the statics of battery.
It has nothing to do with the battery life, Google has confirmed this.
In fact, in TWRP and 4EXT recovery this wipe there isn't.
However, i think you have to calibrate your battery with some charge cycles
Guich said:
Sorry for the replies, but: the battery stats wipe is useless...
The file that you've removed is a file which contains the statics of battery.
It has nothing to do with the battery life, Google has confirmed this.
In fact, in TWRP and 4EXT recovery this wipe there isn't.
However, i think you have to calibrate your battery with some charge cycles
Click to expand...
Click to collapse
Guich, what i talked about was not fixing battery, just fixing the readings.
Example : especially on AOSP roms, if u put on charge, after some time green LED shows (meaning charge full) BUT battery bar is stuck at a lower level ( Example 76 ) .
And the bar doesnt move forward even after you keep it on charge even longer.
So i tried a battery stats wipe in cwm and then when i booted back, it properly showed 100%.
So what i recommended was to delete previous stats ( of different ROM which were carried into this one).
So now the phone starts monitoring battery anew (with no cache).
Sorry if you misunderstood me.
R: [Q] Terrible battery life on jellybean aosp roms
{< r o N o $ said:
Guich, what i talked about was not fixing battery, just fixing the readings.
Example : especially on AOSP roms, if u put on charge, after some time green LED shows (meaning charge full) BUT battery bar is stuck at a lower level ( Example 76 ) .
And the bar doesnt move forward even after you keep it on charge even longer.
So i tried a battery stats wipe in cwm and then when i booted back, it properly showed 100%.
So what i recommended was to delete previous stats ( of different ROM which were carried into this one).
So now the phone starts monitoring battery anew (with no cache).
Sorry if you misunderstood me.
Click to expand...
Click to collapse
I think this fact is random.
In fact, all aosp rom that i tried didn't have this problem
And, teorically, this file was delete when you made a full wipe.
In fact in TWRP recovery there isn't the wipe for the battery
Sent from HOX
I can't fine the battery wipe in CWM
Constantine. said:
Thank you so much! I have deleted the battery stats file in cwm and it is immediately obvious that the battery life has improved.I can't believe how easy the fix was.
Click to expand...
Click to collapse
How I could find batt wipe in cwm?
Guich said:
I think this fact is random.
In fact, all aosp rom that i tried didn't have this problem
And, teorically, this file was delete when you made a full wipe.
In fact in TWRP recovery there isn't the wipe for the battery
Sent from HOX
Click to expand...
Click to collapse
Battery stats file should be deleted each full charge, though I have noticed my phone crash (my fault messing about with UV) and then my batter jump from 8% to 45% which is quite a jump lol
Sent from my HTC One X using xda app-developers app
eezwanlee said:
How I could find batt wipe in cwm?
Click to expand...
Click to collapse
I believe its under advanced - wipe batt stats
I can't find it
Constantine. said:
Thank you so much! I have deleted the battery stats file in cwm and it is immediately obvious that the battery life has improved.I can't believe how easy the fix was.
Click to expand...
Click to collapse
Mr Hofs said:
I believe its under advanced - wipe batt stats
Click to expand...
Click to collapse
I'm familiar with CWM, but I cannot find it in advanced menu.
Is it because after I upgrading my HumberOS CM10.1 to AOSP 3.15?
I did a wipe clean. Everything. Fresh install.
It happened after I finished upgrading to AOSP ROM 3.15. My battery shows nothing even I charged it for a whole night.
Only 2% batt left while I'm typing this message. I have to connect my SGT7 to charger but nothing happened. It shows that it's charging but too bad, its not.
I've never encounter this problem before. It would be nice & I would be grateful if you sir can help me through this problem.
Thanks for replying.
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crayonslayer said:
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Generally these issues are user related and not ROM related.
I was so frustrated with some of the ROMs when I first started out but then realized I was doing a few things wrong (mainly because these ROMs, including CM10 have very decent battery life).
First, I would recommend a clean reflash:
factory wipe / reset
wipe cache (some say twice)
wipe dalvik cache
install ROM
after rom loads, wait 5 minutes (don't touch at all) then reboot
now you must wait.. sometimes it takes 24 hrs or so for a ROM to correctly load.
Not sure how true it is, but some say to now drain battery down, then fully charge.
At any rate, I follow these steps all the time and works great!
Also, keep in mind that most of battery issues are user related.. so think about what settings, apps and kernels are being used on your end before question a ROM. This is why waiting 24 hours or so before installing all of our "crap" will give give the ROM more time to settle.
Hope this help!!!! Happy Flashing
Thanks for the reply. However, I have looked at what apps and processes are draining my battery. And it appears it is the "phone" process that is doing this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Just to piggyback on spenny88's reply, exactly what did you come from (stock?) and how did you wipe and flash?
This is all key as to how well your device will perform.
xBeerdroiDx said:
Just to piggyback on spenny88's reply, exactly what did you come from (stock?) and how did you wipe and flash?
This is all key as to how well your device will perform.
Click to expand...
Click to collapse
I have noticed something similar. I am coming from stock. I am going to guess my battery life is in the neighborhood of 10% less. I wiped everything before I installed CM. That said, this feels so much faster than stock.
Same Battery Issue on p1 (TMobile original Galaxy Tab 7.0)
spenny88 said:
Generally these issues are user related and not ROM related.
I was so frustrated with some of the ROMs when I first started out but then realized I was doing a few things wrong (mainly because these ROMs, including CM10 have very decent battery life).
First, I would recommend a clean reflash:
factory wipe / reset
wipe cache (some say twice)
wipe dalvik cache
install ROM
after rom loads, wait 5 minutes (don't touch at all) then reboot
now you must wait.. sometimes it takes 24 hrs or so for a ROM to correctly load.
Not sure how true it is, but some say to now drain battery down, then fully charge.
At any rate, I follow these steps all the time and works great!
Also, keep in mind that most of battery issues are user related.. so think about what settings, apps and kernels are being used on your end before question a ROM. This is why waiting 24 hours or so before installing all of our "crap" will give give the ROM more time to settle.
Hope this help!!!! Happy Flashing
Click to expand...
Click to collapse
Having the same issue with my Samsung Galaxy Tab P1000 (p1 in Cyanogenmod). "Cell Standby" is taking as much juice as "Screen", and I am using Wifi only. I don't even have a sim card in the device. Wish there was a way to disable Mobile Networks without disabling Wifi via Airplane Mode.
I installed through Rom Manager as upgrade from CyanogenMod 9.1 with wipe. I will try the recommendations above and report back.
Try the latest nightly (or RC4) of CM10.1. The battery life has definitely improved a bit.
Samsung Galaxy s3 intl battery drain cm10.1
I recently installed cm10.1 nightly on my international S3, it has cut the battery life down drastically and seems to drain over 10% an hour, even when not being used.
I've tried everything that i've came across by searching and still haven't had any real gain on battery life. Doing a full wipe and reinstalling doesn't help, and i've given it time for battery to calibrate; no difference. Even with wi-fi and location services off i'm getting a big drain. I've even tried switching to Slim Bean, if anything the battery was worse still.
Firstly i'm getting that Android OS is eating up a large chunk (usually above 60%) and using BetteryBatteryStats i don't see anything out of the ordinary in terms of partial and/or kernel wakelocks. I really don't wanna have to put the stock Touchwiz rom back on but that seems like the ways it's going. Any help would be greatly appreciated. Is there anything else i can try?
i find i get terrrible battery life on AOSP when i restore google through the setup. i skip thru the installation and open the play store to enter my gmail. then, before restoring my apps, i let it charge to 100%. honestly AOSP still doesnt have decent battery life, but it does improve if you play with it and try different things
hapticxchaos said:
i find i get terrrible battery life on AOSP when i restore google through the setup. i skip thru the installation and open the play store to enter my gmail. then, before restoring my apps, i let it charge to 100%. honestly AOSP still doesnt have decent battery life, but it does improve if you play with it and try different things
Click to expand...
Click to collapse
I would respectfully disagree with you. I have run a number of ASOP based ROMs and find them better than stock in terms of battery life. Certainly better in terms of not making my eye bleed (as I hate touchwiz, but that is a personal preference). I find that SlimBean gets me the best battery life of the CM based ROMs.
To clarify, I get just over 1%/hour battery drain, when idle (as measured by BBS) with GPS and google sync enabled, mostly on LTE. My phone happily spends almost all the time I am not actively using it in deep sleep.
The recipe to achieve this is to disable google location reporting and history, avoid tons of widgets that constantly update themselves, disable samsung services that you do not use, and monitor battery usage to look out for rogue apps that do stupid thengs, like hold wakelocks when they should be idle. Dropping the minimum frequency to 192 MHz, and going to ASSWAX (CPU scheduler) and ROW (I/O scheduler) also helps.
To get decent performance you do need to install things properly. Which means ensuring that you don't have conflicting settings or random leftovers. I tend to dirty flash updates but you reallly do get better and more consistent performance going through the pain of a complete clean install (format system, clear cache, reload apps from the store) when you are switching ROMs. Only use TiBu to restore app data. Once you do this, in my experience rogue wakelocks are the biggest cause of lousy bettery perfromance, and you can track down and eliminate these. I have around 150 apps loaded and do not run any task manager/autokiller. My phone typically runs without any reboots or power cycles between ROM updates which equates to rebooting every couple of weeks to a month. I have seen over 2 months of uptime.
Certainly should be able to go 16-20 hours between charges which I would consider real world all day functionality. I guess my point is that rock solid stability and all day battery life is possible if you are systematic about how you do things.
crayonslayer said:
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem..... Battery lose 1 % every 2 mins thats terible. :crying:
How could i find a fix ? plz if u have fix yours tell me ???
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
Hi,
I follow the forums here for years but have not posted yet, hence not allowed to post on the dev forum in the appropriate thread, had to open a new one
A couple of days ago I installed "[ROM][JB][4.3.1][JLS36I] CyanogenMod 10.2 Alpha (Build 3)" on my wife's phone. Until then she was still using the stock GingerBread ROM. The phone got so slow to the point of not being usable at all.
After I flashed to CM 10.2 it feels like a new phone. Lightning fast, good looks, everything works - fantastic, very much appreciated and thank you very much @ Devs!!! :good::good::good:
One big problem though:
When running the stock ROM the battery usually lasted about 2 days. Now, with CM10.2 it is empty after half a day. Since I did a full wipe before she is using less Apps as compared to before and there is no single big consumer. Just the typical mail apps, facebook etc.
When I look at the wakelocks there is one app consuming most CPU which is CSipSimple. But that app was also running before the upgrade when the battery lasted 2 days.
The screen seems to consume more power though, is that possible? Anyone else with similar experiences?
Thank you very much!
nuukee said:
Hi,
I follow the forums here for years but have not posted yet, hence not allowed to post on the dev forum in the appropriate thread, had to open a new one
A couple of days ago I installed "[ROM][JB][4.3.1][JLS36I] CyanogenMod 10.2 Alpha (Build 3)" on my wife's phone. Until then she was still using the stock GingerBread ROM. The phone got so slow to the point of not being usable at all.
After I flashed to CM 10.2 it feels like a new phone. Lightning fast, good looks, everything works - fantastic, very much appreciated and thank you very much @ Devs!!! :good::good::good:
One big problem though:
When running the stock ROM the battery usually lasted about 2 days. Now, with CM10.2 it is empty after half a day. Since I did a full wipe before she is using less Apps as compared to before and there is no single big consumer. Just the typical mail apps, facebook etc.
When I look at the wakelocks there is one app consuming most CPU which is CSipSimple. But that app was also running before the upgrade when the battery lasted 2 days.
The screen seems to consume more power though, is that possible? Anyone else with similar experiences?
Thank you very much!
Click to expand...
Click to collapse
try to flash madridi kernel .. and install greenify app from playstore to greeinfy apps which run in background
Ahmed.ragab said:
try to flash madridi kernel .. and install greenify app from playstore to greeinfy apps which run in background
Click to expand...
Click to collapse
ok thanks let me do some reading.
Also yesterday I deactivated the SIP app and that helped of course. Still strange that the app consumed to much less power on Gingerbread compared to CM10.2
Thanks,
Sven
You can try out battery calibration app before new kernel. Cause there is no "wipe battery stats" on cwm 6.0.4.4. I had same problem, and its a bit effected on cm 10.2. It's free. Maybe it will solve your problem.
Battery Calibration
That sounds very good, let me try that!
I have the same issue with increased battery drain. Yet I've not been able to identify the source. I disabled a lot of services (with Disable Service), also deactivated unnecessary system apps.
Cell standby is also shown as a huge drainer, although I usually have a good signal and no losses (checked with Better Battery Stats). There are no wake locks out of the ordinary.
Now I'll try battery calibration to see if that helps at least some amount.
Actually for me nothing really helped.
I eventually identified the 3 apps that drained the battery via Wakelock detector.
Those apps are Facebook, GMX Mail (based on K9 mailer) and CSipCimple.
Before the update to 4.3 my wifes phone was running the stock gingerbread and did not have an issue at all with those apps.
Yet on CM4.3 they are draining the battery.
Once I uninstalled the apps the batter life is back to normal. Which is sad, because she needs those apps. But no other solution so far from my side....
nuukee said:
Actually for me nothing really helped.
I eventually identified the 3 apps that drained the battery via Wakelock detector.
Those apps are Facebook, GMX Mail (based on K9 mailer) and CSipCimple.
Before the update to 4.3 my wifes phone was running the stock gingerbread and did not have an issue at all with those apps.
Yet on CM4.3 they are draining the battery.
Once I uninstalled the apps the batter life is back to normal. Which is sad, because she needs those apps. But no other solution so far from my side....
Click to expand...
Click to collapse
maybe if ur wife want to use fb checjlk her email... myb use broeser is okay... u can download opera mini or uc browser... it very fast and smooth browser.... or u can flash other rom like oneofakind.... growl (battety) version),,,,, hope this will help you!
hotriffs said:
You can try out battery calibration app before new kernel. Cause there is no "wipe battery stats" on cwm 6.0.4.4. I had same problem, and its a bit effected on cm 10.2. It's free. Maybe it will solve your problem.
Battery Calibration
Click to expand...
Click to collapse
Again the myth with whiping battery stats / battery calibration. Make a full charge and unplug the charger. This will whipe your battery stats.
And for the ones who never get this. The stats are just some data about apps consumption collected while the battery gets discharged. The ROMs are whiping them by itself on each full charge and after shuting down the phone.
This data has no Infulence to how long a battery lasts. It´s just collected to show you visually the statistics.
honeyx said:
Again the myth with whiping battery stats / battery calibration. Make a full charge and unplug the charger. This will whipe your battery stats.
And for the ones who never get this. The stats are just some data about apps consumption collected while the battery gets discharged. The ROMs are whiping them by itself on each full charge and after shuting down the phone.
This data has no Infulence to how long a battery lasts. It´s just collected to show you visually the statistics.
Click to expand...
Click to collapse
+10
honeyx said:
This data has no Infulence to how long a battery lasts. It´s just collected to show you visually the statistics.
Click to expand...
Click to collapse
Thanks ... yeah well did not really expect it, but when you're desperate
At least I thought it helps with the effect that the first 50% of the battery last 3 times as long as the last 50%, but not even that changed
nuukee said:
Hi,
One big problem though:
When running the stock ROM the battery usually lasted about 2 days. Now, with CM10.2 it is empty after half a day. Since I did a full wipe before she is using less Apps as compared to before and there is no single big consumer. Just the typical mail apps, facebook etc.
When I look at the wakelocks there is one app consuming most CPU which is CSipSimple. But that app was also running before the upgrade when the battery lasted 2 days.
The screen seems to consume more power though, is that possible? Anyone else with similar experiences?
Thank you very much!
Click to expand...
Click to collapse
I had the same problem with my S4 running CM 10.2 stable. The battery was empty after 8 hours. What I did was to change the theme, and today i got 12 hours and only 20% of the battery gone and wi-fi/3g all the time. Well, I still have only one hour of screen up time, but that is how it was before... I don't know, i'm just saying! Maybe it helps. The theme i added is LunarUi 2.
All the best!