i have cwm recovery 6.0.3.0 by Davidmarco installed on my xperia T... i want to wipe battery stats so i reboot to recovery and there is no option for that...
i also check in Advanced menu and all other menu's by there is no such option... so how to do that?? is there any fault with my recover...
i am on stock jb rom stock kernel.....
I don't have it either so its not a fault with your recovery
Iv known devs to remove it from their kernels as its "a useless feature"
Altho I liked to wipe the battery stats after a new rom and full charge whether it was useless or not
Throbin Wood said:
I don't have it either so its not a fault with your recovery
Iv known devs to remove it from their kernels as its "a useless feature"
Altho I liked to wipe the battery stats after a new rom and full charge whether it was useless or not
Click to expand...
Click to collapse
is deleting batterystats.bin file really help calibrating battery? have u tried ever?
No, wiping batterystats has nothing to do with calibrating battery. In fact, wiping batterystats.bin had almost no use except resetting the information in Settings - Power management - Battery, that's why it's removed from CWM I think.
See also http://www.xda-developers.com/andro...-battery-stats-does-not-improve-battery-life/
Sent from my LT30p using xda app-developers app
n70shan said:
is deleting batterystats.bin file really help calibrating battery? have u tried ever?
Click to expand...
Click to collapse
Sorry never tried it, I am curious tho
Have you replaced your battery?
What is it your trying to achieve?
is this any use to you? (iv never tried it)
https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en_GB
Description
Requirements: Android 2.1+ | Root permissions
Calibration needs to be done after flashing a new ROM, but you can calibrate any time you think your battery is miscalibrated. This program does it by removing the batterystats.bin system file. The OS generates a new clean batterystats file soon, thus any fake information from the previous ROM is removed.
It's suggested, but not necessary, to let the phone fully discharge after calibration, then charged to 100% without break.
The app shows your actual battery status, and only allows you to start the calibration (i.e. removes the file) when it's fully charged, unless you force earlier calibration.
The voltage meter can be useful too. Full charge is around 4200mV.
There is an option to beep when 100% is reached so you don't have to closley follow the changes.
Related
i was really confused about rooting my OB, i used my phone for about 4months and still with this stock rom V20b, and battery life sucks... will i need to format my phone and sd card before rooting? so many questions on my mind... and can someone give me steps for rooting? cause i been checking some links for rooting but it doesn't work, pushing thanks in advance...
when i had stock rom battery life was the same, but a lot of roms have this problem. you can to turn off some serwices which you dont need to use. also you can try other roms with root especially supprassed rom if you all time thinking about battery. http://forum.xda-developers.com/showthread.php?t=1487105
but if you have brand rom i think http://forum.xda-developers.com/showthread.php?t=1448803 smartflash will be good way for you.
Wysłane z mojego LG-P970 za pomocą Tapatalk
I've read some threads saying that the battery performance it's better with Zeuz but. I'm using the 10A and the battery sucks too, I use the Juice Defender app to save bat.
In a few days I will upgrade to Zeuz to test it.
Of course in the zeus too you have turn off some services for long life of battery
wifi, 3g if you do not need them
But i keep 10a on pc for warranty
i had the same problem as you. the solution for me was to install a custom rom with governors. i installed zeus. the advantage of that is that with the right governor (f.e. ondemandx) the cp does not go to 100% so often and that conserves power. also a combination of custom i/o scheduler and governor saves a lot of juice!
so to sum up what i mean. install a custom rom that have custom governors. then download system tuner (free from market) and change that governor to something that saves power like ondemand/ondemandx interactive/interactivex slavazgen(or something like that). i recommend you to install the latest zeus rom because it has a lot of tweaks it is smooth and has zeus app that you can easily change the governor/io scheduler.
also a good thing to is via system tuner to freeze a lot of system apps that you don't use google what you can unistall/freeze
i don't know if it saves battery but it makes the rom goes faster
i also have read that disabling autosync (f.e. gmail) saves a lot of energy.
finally a trick that i also used on my previous phone and worked miracles on the battery is disabling 3g and use only 2g (if you don't use 3g everyday)
ok this is my opinion on your query....
1) rooting alone dosent do anything for your battery life, it only gives you "admin access" to your phone.
2) why rooting could be important/ helpful to improving battery life; on stock roms, there are default and "bloat apps" that you cannot uninstall or stop from running in the background, after rooting(admin access) you can delete/ freeze/ replace etc these "bloat apps" which will greatly reduce the amount of background processes hence saving you battery.
3) personal advice is unless you are confident about flashing and reverting back and forth roms and knowing what and how to get out of bootloops, etc is to get root, debloat your stock rom, create a nandroid and then take it from there...
4) you wont need to format your sd but its recommended to do a factory reset/wipe cache etc to your phone
5) about rooting v20b, i think nooby covered that in his "how to" thread over at the "General" section
hope this helps
I'm confused, this way to do a nanodroid it's correct?
Open ROM Manager - Copy Current Rom Option?
Thks
lean7 said:
I'm confused, this way to do a nanodroid it's correct?
Open ROM Manager - Copy Current Rom Option?
Thks
Click to expand...
Click to collapse
Yes, that´s correct. Or you can do it directly in CWM. Sorry for the bad english.
lean7 said:
I'm confused, this way to do a nanodroid it's correct?
Open ROM Manager - Copy Current Rom Option?
Thks
Click to expand...
Click to collapse
Yes or:
Reboot into recovery> backup and restore> backup.
koila33 said:
Yes or:
Reboot into recovery> backup and restore> backup.
Click to expand...
Click to collapse
fazbarulho said:
Yes, that´s correct. Or you can do it directly in CWM. Sorry for the bad english.
Click to expand...
Click to collapse
Thanks!!
Sent from my LG-P970h using XDA
Hey guys I'm having problems with the v6 supercharger script, everything installed fine but now my battery doesn't seem to charge past 66%, I've left the phone on charge for over an hour and nothing has changed, is there a solution for this? Or anything so i can uninstall the script?
Thanks for your time
Cloud1989 said:
Hey guys I'm having problems with the v6 supercharger script, everything installed fine but now my battery doesn't seem to charge past 66%, I've left the phone on charge for over an hour and nothing has changed, is there a solution for this? Or anything so i can uninstall the script?
Thanks for your time
Click to expand...
Click to collapse
That never happened to my device. Give a little more info regarding the rom you are using.
Also try clearing cache and dalvik cache and remove the battery stats from the device. Then restart.
sarkar1990 said:
That never happened to my device. Give a little more info regarding the rom you are using.
Also try clearing cache and dalvik cache and remove the battery stats from the device. Then restart.
Click to expand...
Click to collapse
Iv already sorted it now, apparently i flashed the milestone version and then i found the original and flashed that, and now it charges,
Thanks for offering some help mind
Hi community.
(I've searched without success!)
I've 'broken' my Xperia T. It was rooted and I used Titanium BackUp to 'merge updates to ROM'. Unfortunately the phoned locked up mid process and upon rebooting my phone is failing to boot. I *think its on Android 4.2.. I'd guess I've corrupted the ROM..
I'm afraid I'm unsure if my bootloader is unlocked or not, i rooted over a year ago and cannot remember what i did.
Upon boot I see the 'sony' name for a couple of seconds, it loops doing this and then sometimes I see the symbol that is its 'fix boot thing' that tries to fix the problem. But it never does. So it is stuck in a constant loop, never getting past the earliest part of the boot sequence.
I can't get into Recovery Mode.
What method can anyone suggest I try to recover this? To me as a noob there seem to be numerous recovery methods none of which i understand at this point. What I'd really love to hear is a suggested recovery method and then i can read up and try. As i stand I'm all a bit daunted of where to start.
Thanks for any help on a suggested recovery method. If my phone is beyond repair, that is fine.
It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411
istux said:
It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411
Click to expand...
Click to collapse
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:
Watoh said:
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:
Click to expand...
Click to collapse
You're welcome... and don't mess again with Titanium backup and tools like that... instead, once you've rooted, learn to use backup/restore of recovery... it's way better
I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.
WhiteNeo said:
I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.
Click to expand...
Click to collapse
Yes, maybe you're right...
but the behaviour he reports about powering on and loops, is usually related to something wrong with the kernel.
In addition to this, he can't access to recovery anymore... and recovery is loaded before system. Why?
Or he means "recovery mode" as a lighter system mode (like windows for PC)... yes maybe he means this one... and not a recovery like CMW, etc...
He talks about "merging updates to ROM"... I actually don't know what he means exactly, I don't know how that titanium backup feature works, but if you update system files without updating the kernel, sometimes you can get bootloops because they don't match anymore.
At this point it's better he flash kernel+system together, that's why I suggested Flashtool ...and wiping all data too, is even better
istux once again thank you so much. It worked... on about the 30th time!
I would never have persevered without being given direct advice that this should fix my issue, so i'm very thankful.
I did have several issues getting it to work. For some unknown reason my Win 8.1 desktop refused to install the drivers required. It took me several attempts to realise the drivers were needed. I then switched to my Win 7 laptop and the drivers installed without issue.
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.
Watoh said:
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.
Click to expand...
Click to collapse
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!
istux said:
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!
Click to expand...
Click to collapse
To be honest I didn't actually know i was unable to power off until the instructions told me I had to and i tried without success!
So after 8 hours my battery still said 100% and even shut off due to dead battery and it still said 100% full. In TWRP it also shows 100% full. Any ideas? I have it on the turbo charger now, since it died, and will wait about 2 hours then try to reset battery stats. Not sure what else to try. Nothing new installed, phone is stock other than rooted and TRWP.
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
huh?
The phone was rooted the day I got it, Nov 9th, and it just started doing it today. So how does root automatically cause the issue?
Anyway, any ideas would be great I think resetting the batterystats has worked just curious what may have started it.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
I've never had issues from just rooting. Rooting a phone doesn't cause issues but rather installing root apps and changing things causes issues. I would try to flash back to stock (backup data first) and then root it again to see of that fixes it.
Also did you use CF-Autoroot or one of the tool kits?
I fixed the issue, after that battery died I let it charge for about 4 hours with the quick charger and then reset the battery stats by using an app that deletes the batterystats.bin file. Then did a reboot and now the battery level is no longer stuck on 100%.
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
lifeisfun said:
Same happened to me, phone is on for over 20hrs and battery is still 100%.
Waiting for it to shut off.
Click to expand...
Click to collapse
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Mr Ian B said:
This is why I stopped rooting phones. One feature breaks 2-3 things and end up flashing daily update zips.
Ian B
Click to expand...
Click to collapse
root has nothing to do with breaking your phone. all root does is give you superuser permission. what breaks phones are dirty hacks that you yourself chose to use.
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
lifeisfun said:
I'm shocked, that worked fine!
THANKS!
Is there explanation for this happening?
Click to expand...
Click to collapse
I would just put it down to "OS Confusion "
danarama said:
I would just put it down to "OS Confusion "
Click to expand...
Click to collapse
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
lifeisfun said:
But that's strange, since it reported 100% in TWRP as well, looks more like firmware problem no?
Click to expand...
Click to collapse
Yeah maybe battery firmware confusion. I don't know where TWRP gets its reading from.
Still Works!
danarama said:
You can also try the bootloader trick, though not sure if it will work here.
Boot to bootloader, change to logs menu. Hold power until reboot.
FYI, batterystats is not related to what % battery shows is left.
Click to expand...
Click to collapse
Thanks.
Since I upgraded to Marshmallow my battery life on my T Mobile LG G4 H811 has gone horribly wrong. My phone loses battery at least 20% faster than on lollipop. I am using a debloated custom Rpm since stock marshmallow was worse. Is there any fixes for the bad battery life? Any tips you guys can give me or kernel I can flash that will improve battery life? Anyone else dealing with bad battery life compared to lollipop?
Which ROM are you using? Debloated marshmallow should get you at least the same battery life as LP in my experience. Something is not right with your setup. Did you restore anything? Dirty flash?
Try clearing your cache and dalvik.
i am on genisys rom and it sips battery.
Use a file manager and go into system/bin and look for logd and rename it to lgd.bak then reboot. Battery life should be a tad better
Prolly not your problem but just to share in case:
Had the same problem, horrible battery life after upgrading to MM. No info on the system battery stats. Turned out it was the media scanner tripping out over this old QuickTime movie file I have saved. Better Battery Stats was the only thing that showed it, so if you haven't already try that to see if it can tell you what's up.
(Really curious why I had no problems with that file on LL, but guess that's another question).
mattnin said:
Which ROM are you using? Debloated marshmallow should get you at least the same battery life as LP in my experience. Something is not right with your setup. Did you restore anything? Dirty flash?
Try clearing your cache and dalvik.
Click to expand...
Click to collapse
I am on MicroMod777's "G4 H811 20i xTreme ROM" It already comes debloated. So I am not sure what is causing it. I did a clean install when I installed the rom. I will try clearing cache and dalvik.
Eddiekool12 said:
Use a file manager and go into system/bin and look for logd and rename it to lgd.bak then reboot. Battery life should be a tad better
Click to expand...
Click to collapse
What is that file used for? Will it make anything stop working?
ghagiel said:
Prolly not your problem but just to share in case:
Had the same problem, horrible battery life after upgrading to MM. No info on the system battery stats. Turned out it was the media scanner tripping out over this old QuickTime movie file I have saved. Better Battery Stats was the only thing that showed it, so if you haven't already try that to see if it can tell you what's up.
(Really curious why I had no problems with that file on LL, but guess that's another question).
Click to expand...
Click to collapse
Nice I will need to try that. System battery stats are complete BS. I usually use my phone with the screen below 15 percent and my phone says that's what consumes the most battery which is obviously false.
VileTemptation said:
What is that file used for? Will it make anything stop working?
Click to expand...
Click to collapse
I tried this and my play store stopped working.
Sent from my Android 6.0.1 LGV500 on CM 13 or my LG G4 H811 on AT&T with Android MM 6.0 eXtreme ROM v3.3
VileTemptation said:
I am on MicroMod777's "G4 H811 20i xTreme ROM" It already comes debloated. So I am not sure what is causing it. I did a clean install when I installed the rom. I will try clearing cache and dalvik.
Click to expand...
Click to collapse
Like you I felt LL to be easier on the battery than MM, but not too much. It shouldn't be 20% worse. Cant go back to LL because of stage fright. You may want to consider CM 13. That's about as debloated as it gets and even CM can be made barebones. Any of the kernels with interactive governor should help with battery life. Good luck.
VileTemptation said:
What is that file used for? Will it make anything stop working?
Click to expand...
Click to collapse
From what i read it's just used for taking logs. Like similar to if you're testing something. Ill find a link to it so you can read it.
forum.xda-developers.com/g4/help/guide-disable-logd-process-battery-drain-t3308921
Theres the link. You can read it more in depth there.