http://www.addictivetips.com/mobile...-issue-on-a-rooted-android-device/#more-50317
check this out .. but the problem is when i load into recovery those same options dnt come .. if ne1 can do this procedure please explain me ..
rrohanjs said:
http://www.addictivetips.com/mobile...-issue-on-a-rooted-android-device/#more-50317
check this out .. but the problem is when i load into recovery those same options dnt come .. if ne1 can do this procedure please explain me ..
Click to expand...
Click to collapse
Check this out:
# Wipe Battery Stats. The following screenshots demonstrate how to wipe battery stats in ClockworkMod Recovery v2.5.0.7. Select advanced > Wipe Battery Stats > Yes – Wipe Battery Stats.
Click to expand...
Click to collapse
AFAIK, ClockworkMod Recovery is not available for Milestone.
Alternatively delete it manually.
Search for batterystat in milestone forum there's a lot to read.....
Good luck,
scholbert
Hi,
If you are root on your device you can use the terminal emulator to remove the batterystats.bin file yourself...
su [enter]
rm data/system/batterystats.bin [enter]
Beware, for the first few charge cycles your battery life may actually be worse, but it will improve. Ensure that you reboot straight after too.
Thanks for the tip.
Sent from my Milestone using XDA App
Sometimes 100% charged is not really 100% but actually it is only 60% charged. This mismatch happens when flashing new rom. Have you done the battery calibration either using zeppelinrox's method
http://forum.xda-developers.com/showpost.php?p=11803458&postcount=10
or my method below:
Step 1:
Boot up your phone normally and charge your phone as how you would normally do until it says "charged".
Step 2:
Once your phone charging status says "charged", unplug the wall socket cable from the phone. Shut the phone off.
Step 3:
While the phone is still off, plug back in the wall charger cable. Switch on the power of the wall charger.
Step 4:
You should then see the M logo for a while and then it shows the 100% green battery icon in the middle of the screen.
Step 5:
Open the battery cover and pull out the battery and wait for awhile until you see the "?" icon in the middle of the LCD screen.
Step 6:
Put the battery back in.
Step 7:
If your battery is OK (properly calibrated) then it would show 100%. If it is not properly calibrated, then it would show 60% and it will continue to charge your battery until 100%.
Step 8:
Once your battery has reached 100% (while phone is still off), leave it there to charge for another 15 minutes or until the battery is no longer hot. When the battery is cool to the touch, it means the charger has stopped charging the battery.
Step 9:
Unplug the charging cable and do the "3 finger boot" (x button + camera button + power button) to boot into recovery and flash the new ROM.
Doing so will calibrate the new ROM to the current state of the battery as 100% charged.
Somebody actually posted a video of it... I think it was androidve.com
I should find it again and update my post hehe
Ah... http://androidve.com/2011/03/androidcast-episodio-ocho-calibrando-la-bateria/
ther aint ne folder called system in the data folder .. i cnt find the batterystats.bin file to delete
you can use clockworkmod on milestone
just copy update.zip to /sdcard/OpenRecovery/update and run it
Related
So I know you can clear battery stat via Clockwork Mod Recovery... but how would we accomplish this for froyo builds when 2e recovery is not enabled?
Does anyone know how I would do this?
I used adb shell with the following steps:
Launch Termnial.
su
cd /data/system
rm batterystats.bin
exit
exit
jslee1020 said:
So I know you can clear battery stat via Clockwork Mod Recovery... but how would we accomplish this for froyo builds when 2e recovery is not enabled?
Does anyone know how I would do this?
Click to expand...
Click to collapse
Get terminal emulator from Market then launch it. Once at blue screen, issue the following commands:
su
rm /data/system/batterystats.bin
Restart phone (maybe not necessary but won't hurt)
The first day I was not happy with the battery life as it was draining pretty fast but today it has been great. At 100% at 0530 and 19 hours later I am at 52% with a lot of use.
Sqdnguns said:
The first day I was not happy with the battery life as it was draining pretty fast but today it has been great. At 100% at 0530 and 19 hours later I am at 52% with a lot of use.
Click to expand...
Click to collapse
Did you do anything special or did this just happen over time?
keitht said:
Did you do anything special or did this just happen over time?
Click to expand...
Click to collapse
Nothing special at all..............I was about to blow out Cog2.2 v5.5 today because the battery was getting drained but after today, it seems to be good to go.
EDIT: I have WiFi and BT running all the time as well........
Marvel, Zeus and another "G" key Recovery Roms
1. Shutdown the phone
2. Plug it on the charger
3. Wait until charged
4. Start the Phone and go directly into recovery with the G key.
5. Advanced - Mound SD Card
6. Advanced - Wipe Battery Stats
7. Reboot the Phone
8. Disconnect the charger when you're input on the pin.
9. Ready
use simply "battery calibration", download it from market
Dragusdrake said:
use simply "battery calibration", download it from market
Click to expand...
Click to collapse
that's not the best method.
The file is created when you start the Phone.
There's no battery calibration. Do you research.
dflt said:
There's no battery calibration. Do you research.
Click to expand...
Click to collapse
Exactly.
The "wipe battery stats" only deletes the file that contains the data about what used how much of the battery. The phone doesn't contain any "calibration" data related to battery, it's just an urban myth, deleting that file won't affect your battery in any way, only what's listed in the "Settings->About phone->Battery use" dialog.
For more info look at the following thread : https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT (or better yet read the XDA thread related to the issue : http://forum.xda-developers.com/showthread.php?t=1460553 )
Dear Friends
i have galaxy tab 8.9 inch 32Gb
i need to downgrade from 4.0.4 to 3.2 because of battery problem
i did to 3.2 but still the same
now i need to flash 3.1
but
my device is 32gb should i use the same PIT.file labled P7300_P7310_p5_0614.pit or what
if i used former one it will not decreast the internal SD from 32 to 16 g
where i can get 32g pit file
thanks
For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app
lrcquest said:
For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app
Click to expand...
Click to collapse
Nothing usefull from that
Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium
lrcquest said:
Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did but the battery voltage show 0.004V
i think there is a problem my be fixed with full rom
Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium
lrcquest said:
Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did inside android
many program show this results as shown
Have u charged with phone off?
yes i did many times after i discovered this matter
Have u tried to take volt measurement in adb after charging?
yes correct measurement of voltage appear in 50% appear 3881
The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium
lrcquest said:
The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )
somaare said:
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )
Click to expand...
Click to collapse
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks i will try again today
lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks alot
i did that using my current installation just need to mount system to work on recovery mod
i downgrade to 3.1 using 5 files and update to 3.2
and i did the previous instruction and the battery now is very good and no fake percentage
But still fake voltage even using adb
see the attachment
i think my be some fail in files measure voltage
today morining to disconnect battery for 10 minute but the same problem
any program for the battery show voltage in MVor 0.00? V
U can use battery monitor widget. Always good measurements & worth timeline also.
The second voltage from the s2 might be divided by 1000 to get the right value.
Sent from my GT-N7000 using xda premium
Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.
phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?
souravipc53 said:
phone is overheating whenever I am using whatsapp or simply playing games. Is there anyway to rollback to W1.16.40.763 ?
Click to expand...
Click to collapse
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
reddevilx said:
Do you have 1.17.40.1234 or 1.17.40.1106 ?
I think that they might have corrected the issues with the 1234 version.
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
On the asus forums a number of users said the latest 1234 update made the overheating and battery much worse.
reddevilx said:
If you want to rollback just copy the update in the phone renaming it with a upper version, for example 1.18.40.763, remember that the procedure is at your own risk.
Click to expand...
Click to collapse
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.
souravipc53 said:
.
method doesn't work. Even though updater notifies me about new update but fails . Shows older version cannot be used or something like that.
Click to expand...
Click to collapse
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers
heywheelie said:
From the asus forum try this:
1. Download the firmware to your PC
2. Rename it to MOFD_SDUPDATE, enable the view extension of the files option and check that the file has only .zip, .zip.zip is not accepted and the procedure will fail. (you should have MOFD_SDUPDATE.zip)
3. Now format the sd card in windows with default settings (fat32)
4. Copy the MOFD_SDUPDATE.zip on the newly formatted sd card
5. Shut down your phone and insert the sd card
6. To boot in recovery mode you need to:
a. Hold the power button and volume down key all together
b. When the first Asus logo appears, release the keys.
7. Go to update from sd card and located the MOFD_SDUPDATE.zip
8. Then flash
9. You can format the cache partition if you like (recommended)
cheers
Click to expand...
Click to collapse
Tried this method. Doesnt work. Better use cyanogen mod and TWRP
Or try this:
1.0 [Preparation of your PC]
Download the ADB Tool HERE.
Click on the setup executable and type in "Y" for all the entries. (for the prompt on driver installation, simply click "Next", "Install", followed by "Finish").
1.1
Download the ASUS Software Update HERE.
Once completed, move the update file to C:\adb (where C: is the root drive where the ADB Tool was installed at).
2.0 [Preparation of Device]
Turn off your phone.
Press the "Volume Down" button followed by the "Power" button.
Keep holding the two buttons until the recovery screen appears, then release both AT THE SAME TIME.
Plug your phone into the PC.
On your phone, press the "Volume Down" button to select the option "apply update from adb".
Then, press the "Power" button once to select.
3.0 [Flashing]
Open the command prompt (Windows Key + R, type in "CMD" and enter).
Type in cd C:\adb (take note).
Then, type in adb sideload "downloaded file name".zip
4.0 [Finish]
Upon completion, make sure that the option "reboot system now" is selected on your phone.
Then, press the "Power" button once.
Is anyone using this update that is not experiencing any problems especially battery and heating?
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
I downgraded to V1.16 due to bugs and lag on v1.1.7.40.1234
Posted using a calculator and delayed by AT&T.
---------- Post added at 01:31 PM ---------- Previous post was at 01:29 PM ----------
shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
Mine keeps on overheating and it lags very bad. I downgraded mine to v1.16.
Posted using a calculator and delayed by AT&T.
shubham41 said:
No feedback anyone?
Sent from my GT-S7582 using Tapatalk
Click to expand...
Click to collapse
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
UPDATE: I don't know if it was caused by the update or not but I was on a call and the flashlight came on and Firefox and Settings opened.
willcall said:
I've only been using it for a week on my ZOOTD but I haven't noticed any overheating or significant loss of battery life
Click to expand...
Click to collapse
Thanks. I wonder if the overheating and battery life problems only affects the Z00LD?
heywheelie said:
Seems that very few have updated to this firmware. I haven't and won't until a stable update comes out. In the meantime I'm happy with 1.16.40.763
Click to expand...
Click to collapse
Judging by the fact that a new update has not been released for quite some time now, the next update *should and hopefully, be marshmallow.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
heywheelie said:
Anyone using the new 1.17.40.1234 update please post your impressions and more particularly any bugs encountered.
Overheating, system slowdown and poor battery life have been mentioned by a number of users on other sites.
Click to expand...
Click to collapse
No issues on my ze550kl, no heating issue, no major bugs on 1.17.40.1234. But it becomes warm when I don't close any game and tap home button but that's normal.
1.17.40.1234 came with Wi-Fi and carrier network improvements. I guess people from certain region might be facing heating issue due to changes in modem. I am from India. No issues for me
I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.
dominati said:
I can confirm there is an issue. I just got the phone and immediately updated it the latest firmware. I am getting abysmal battery life and the phone does get quite warm at times. I charged my phone last night and when I went to bed it was at 95% battery. When I woke up the battery was at 33%. I looked at the battery logs and the flashlight app and cell standby consumed 22% each. I have no clue why the flashlight app would be using battery for no reason.
Click to expand...
Click to collapse
Try using the auto-start manager and making sure the flashlight app does not start automatically then reboot the phone. High standby usage can sometimes be caused by a faulty microsd card. If you have one, try unmounting and then remountiing it and see if that helps. If it doesn't try reformatting it.
Hello,
Days ago I tried to uninstall from my Touchpad since I wanted a clean reboot to reuse the tablet. However I realized that the tablet wasn't turning on, and she wasn't able to get in USB Mode.... The thing is that to get a clean wipe I need to use ACMEUninstaller2, but it says that the device is not found, so I guess that It's the USB Mode that's breaking everything. I tried quite a few things but nothing works, the tablet just don't want to get in USB Mode.
By the way, when I connect with USB the Touchpad to the PC, the PC recognizes it, but tolds me that "The drivers of this devices aren't installed", which is strange since I installed all Novacom drivers I could find...
Also, I'm asking if you could help me with that, since I searched everywhere I haven't found anything on this.
The novacom driver is what communicates to the HP Touchpad and is use to load any boot uImage into memory.
( It does mount or allow the use of the USB drive ) The USB drive is a partition formatted in vfat that gets mounted by TWRP or any other Recovery and also Android.
To load any boot uImage into memory.
Boot Tablet and select ((( boot WebOS Recovery ))) from the moboot 0.3.8 menu
If there is no moboot 0.3.8 menu, then press power and volume key closes to the power key and the same time until the big white USB symbol comes up.
Plug the tablet into PC using USB.
On the PC unzip the Recovery file you will like to use.
Go to the extracted folder and open a terminal window or command prompt.
Type:
novacom boot mem:// <
after < ( place the name of the uImage file)
Example for TWRP will be
novacom boot mem:// <uImage.TWRP
If you want to load the ToolBox, then unzip TPToolbox-2015-01-08-v42.zip
rename the file TPToolbox-2015-01-08-v42.bin to uImage.TPToolbox
Open a terminal window in that directory and load it:
novacom boot mem:// <uImage.TPToolbox
Thank you for you answer !
I followed everything you said but my tablet isn't getting on USB Mode, I tried so many things but it don't wan't to.... When I do Power + Volume UP, I'm getting a charging icon, but when I try to charge the tablet, as I don't have any official charger, it tolds me I need to get one, but I don't really have 15 dollars to use in a charger, since I remember that I could charge the tablet without the official one when she was still working...
Patahuete said:
Thank you for you answer !
I followed everything you said but my tablet isn't getting on USB Mode, I tried so many things but it don't wan't to.... When I do Power + Volume UP, I'm getting a charging icon, but when I try to charge the tablet, as I don't have any official charger, it tolds me I need to get one, but I don't really have 15 dollars to use in a charger, since I remember that I could charge the tablet without the official one when she was still working...
Click to expand...
Click to collapse
To charge the HP Touchpad you need any charger that will meet this specifications:
Output: 5.3volts, 2.0amps
For all of you that think your tablet is Brick or not functional or having issues:
No electronic device known to man existence can work without been properly charge or connected using the proper power source.
Even for a car, if it does not have a full working battery it will not start no matter if you replace the engine.
It is a basic procedure to follow.
1. Check for proper charging.
2. Start trouble shooting.
Thank you for your answer.
I see. I searched and I'm still searching for that charger, but, just to know, if I connect the tablet to the USB ports of my computer, will it charge it even if there's a message telling me that I need the official charger ? Also, does USB 3.0 or 2.0 changes anything to the charging speed ?
Because I don't see any LED or sign of the tablet charging so I'm a little bit confused on how it works...
Patahuete said:
Thank you for your answer.
I see. I searched and I'm still searching for that charger, but, just to know, if I connect the tablet to the USB ports of my computer, will it charge it even if there's a message telling me that I need the official charger ? Also, does USB 3.0 or 2.0 changes anything to the charging speed ?
Because I don't see any LED or sign of the tablet charging so I'm a little bit confused on how it works...
Click to expand...
Click to collapse
The HP TOUCHPAD will ONLY CHARGE using a charger providing the following:
Output: 5.3volts, 2.0amps
It will not take enough charge to make it boot from no other source, NO USB connected to PC.
It will be the same as using a 9volt battery to start your car.
An inexpensive option:
https://www.ebay.com/itm/5V-2A-AC-Charger-Power-Adapter-Supply-for-HP-Touchpad-16GB-32GB-Tablet-PC-Tab/122752649546?hash=item1c94a0c94a:g:~ygAAOSw9-FZ3wWS
Ok ! I've got something ! So I managed to get the tablet charged, and so I used ACMEuninstaller2, the thing is that it told me something like "ERROR : unable to.... When the tablet will boot, it will fail to launch, and then use webos doctor !" So I did it and I'm struggling with a 8% error, wich tells me that webos doctor is unable to reset the phone... I tried wikipedia and every xda thread I could see and nothing works... I'm desesperate, It's really the kind of things that happens to me and just me....
Do you want to use WebOS or Android on the HP Touchpad Tablet?
** The information is to be use on a Tablet not a Phone **