yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] johnnyv5:
should it be said that this should be done with a full battery?

jv
[Fascinate Android Development] agsded:
I understand why this is necessary now....had been hedging on using it.... yesterday my phone ran down to zero battery but was still working....almost every app griped about battery tho..... i ran it like that trying to wait on it to shutdown, and after about an hour, said screw it, tossed that script into the appropriate location, hopped into connectbot and ran it..... its working properly now
[Fascinate Android Development] lentm:
I installed this script file via clockwork at 0% to wipe battery stat yesterday.

At first, it seemed like battery life got longer.. but right now which is 8 hours after unplugged.. its at 50% already..

I don't think it worked properly.

Is it because I didn't run script via adb or terminal emulator after install it via clockwork?

my phone's battery could run for 111 hours with stock browser before I rooted.

After 3-4 weeks of rooting, especially in this week, my battery has been really bad compared to before.. I didn't even flash roms and theme many times.

Stock (unrooted) -> DI01 (rooted) -> DJ05 (superdark rom & stupidfast kernel) -> EB01 SuperClean 2.4 voodoo now...

It's been bad battery life from last 2 days of DJ05 with superdark & stupidfast until now.

I love my phone but this battery is killing me.
[Fascinate Android Development] BlackHoleSlam:
Terminal emulator force closes for me
[Fascinate Android Development] upsidedownaaron:
"when" does term emulator fc? as soon as you open it? after you type su then hit return? or after you try to run this script?

i would first uninstall, wipe cache, wipe dalvik (don't know why but i just do that routinely), then reinstall.

if that doesn't work, do a factory wipe, then reinstall the rom you are running.

and of course have a good backup of your apps from titanium.
[Fascinate Android Development] AlgorithmX:
I had the same problem until I switched to this one.

market://search?q=pname:jackpal.androidterm
[Fascinate Android Development] AlgorithmX:
I'm pretty sure the OP intended for this to be flashed with cwr and the following commands ran in terminal emulator.

su {enter key}

(allow superuser if necessary)

( wait for $ to change to #)

bstats {enter key}

(Wait for reboot)

Thanks Adrynalyne, you da man :)
[Fascinate Android Development] BrwnSuperman:
Thanks, this solved all my battery concerns!
[Fascinate Android Development] CGriffiths86:
So can I just charge my phone to 100%, run the script, and use the phone just like regular? I've had the problem where my phone charges all night and when I unplug the phone it says 95-96%.
[Fascinate Android Development] Mikes30000:
This really seemed to work at recalibrating the battery. Now my meter trickles down slooowwwwwlllly. Love it. Thanks a lot!
[Fascinate Android Development] mastamoon:
I got just over 22hrs of regular use after wiping battery stats after a full charge. See how the next charge goes.

Sent from my superclean froyo'd fascinate.
[Fascinate Android Development] xgunther:
Just curious. What are the ADB commands to run the script. I'm an ADB noob.

Nevermind. Hello Mister. ADB Shell.
[Fascinate Android Development] euklid:
Should this be applied when battery is fully charged or it doesnt matter??
[Fascinate Android Development] BeeDubs:
Thanks a ton, Adryn. I'll try this tonight after I load SC2.4V
[Fascinate Android Development] BeeDubs:
My understanding is that wiping batt stats when battery is fully charged is like resetting the charge counter. Think of it like a calibration.

I think the phone will "die" if the counter hits 0%, even if there is still some charge left, so I think the power down is dependent on the counter and not necessarily the exact amount of charge left.
[Fascinate Android Development] iofthestorm:
Is there a reason to use this script instead of just rm'ing the stats file using a terminal emulator? I guess convenience due to lack of a keyboard, but other than that it seems like since that's all the script does it shouldn't matter, right? Thanks!
[Fascinate Android Development] agsded:
Before I applied this, my phone's battery gauge would go down to zero, and the phone would still run at least an hour, that's as long as I was willing to wait...it was so weird seeing it on zero, normally it turns off at like 4 or 5 percent.
[Fascinate Android Development] beray5:
Yes it does matter...

When you wipe the battery stats the phone immediately begins to start collecting calibration data using the fully charge level as the starting point.

If you wipe the battery stats at some other random charge level than fully charged, the phone will not know the full charge voltage reading and use default conservative calibration table values, which will work for all battery without burning or blowing up the phone while collecting further calibration data.
[Fascinate Android Development] stereoblind:
Curious. Are we always going to be wiping the battery stats on this phone, no matter the version of android? Or is it not an OS version issue? Asking cause I never had to do this on the D1 or the Eris. Lol
[Fascinate Android Development] beray5:
Normally you don't wipe battery stats unless the DEV specifically indicated.

Battery implementation usually is 100% bug free upon device release to the public and remain the same through the full life cycle of the device.
[Fascinate Android Development] adrynalyne:
I'm sure thats what they would like you to believe.

However, unless you install EVERY OTA update at 100% battery life, or do a factory reset/wipe ONLY at 100% battery, that is simply not the case.
[Fascinate Android Development] beray5:
Typically on any phones, using standard user factory reset/wipe will not have any effect on battery calibration (this is the same on Samsung Fascinate). To wipe battery stats usually required separate procedure/pathway well hidden away from normal user access.

Can't allow people not knowing what they are doing to mess with battery calibration haphazardly from an easily accessible menu by Joe Users.
[Fascinate Android Development] TheHunterOfShadows:
Can this be installed with lag fix on, or should it be disabled first?
[Fascinate Android Development] s44:
That's not an error, it's how charging works. When it hits max while on, it stops charging until it drops back down to 95%. So unless you're awake and notice the fully charged indicator, you can pull the phone off the charger anywhere from 95% to 100%.
[Fascinate Android Development] adrynalyne:
No, that is not true. Battery stats is an XML file on the data partition on android devices.
[Fascinate Android Development] diesel43078:
Nevermind, found the same question in a previous post.
[Fascinate Android Development] beray5:
I had no idea that "batterystats.bin" is an xml file, I wasn't able to open it with any xml editors I had.

At 45% battery charge, using settings> privacy> factory data reset> phone rebooted. This had no effect on battery calibration in Samsung Fascinate as it's still at 45% charge, the phone required re-activation and re-installation of all user aps.

At 45% battery charge, using "bstats.zip" through CWM recovery> phone rebooted. Phone is at 58% charge -> default conservative battery calibration table loaded.
[Fascinate Android Development] adrynalyne:
My bad, I meant to say bin file, not xml.

You can argue all you want, but the file *IS* on the data partition, and I have found flashing ANYTHING in cwm shows the time to be different when I reboot.

You are gonna have to give me more concrete evidence than this.

Edit: I just flashed one of my patch files for the Samsung music player and booted back up. I had more battery than I had before I booted to clockwork, when it rebooted. It was not on a cable.

Edit Edit: I could go into a myriad of reasons why I think your "wipe" test was inconclusive, but I am tired of arguing. Believe what you like and move on :)
[Fascinate Android Development] Sorosy:
seriously? Adryn works his ass off daily to make all of us happy. He knows his way around this phone and you are trying to prove him wrong? Get a life bud, your so-called life now, isn't going anywhere as it stands if you are going to sit and argue with someone that actually knows what he is talking about.
[Fascinate Android Development] mAlfunkti0n:
Chill man. This is a discussion board, people are allowed to ask questions or be curious.

I installed with CWM, then in adb browsed to /system/xbin and did ./bstats

Worked just fine, we'll see how the battery goes now. :)
[Fascinate Android Development] agsded:
Battery gauge is not tied to phone turning off.....before I applied the script, my phone hit zero and ran for an hour before I got annoyed at the software tied to the meter not working, like camera app and music app...finally I rebooted, charged and applied wipe battery stats patch
[Fascinate Android Development] beray5:
I honestly thought I needed a special xml editor. :)

I'm sorry DEV, I had no intention of nor wanted to argue with you, I thought I might have provided some info you perhaps found useful. The file always shows the time to be different at different times even if you don't use CWM flashing, the calibration stats periodically updates continuously.

EDIT

The step below took 14 hrs, I flashed back to old DI01 backup, factory reset, then use the phone for a period of time to check for normal use. After which time I let it idled for 9 hrs overnight on my bed stand and it lost 5% battery charge just as it did some months ago.

"At 45% battery charge, using settings> privacy> factory data reset> phone rebooted. This had no effect on battery calibration in Samsung Fascinate as it's still at 45% charge, the phone required re-activation and re-installation of all user aps."
[Fascinate Android Development] nmyeti:
I just wanted to say thank you for this script. I was skeptical to the effect it would have, but after using it, i'm seeing more than a 100% increase in battery life. Before using this script i was lucky to get 6hrs off the charger now see below.
[Fascinate Android Development] beray5:
Once you've gone through about 3 full cycles of battery charging, you should save "/data/system/batterystats.bin" to your SDcard for future restoring when the occassional "oops" happened.

I've used the same saved "/data/system/batterystats.bin" for restoring in DI01, DJ05, DL09, DL30, and EB01. For example in the step below...

<At 45% battery charge, using "bstats.zip" through CWM recovery> phone rebooted. Phone is at 58% charge -> default conservative battery calibration table loaded.>

At this point I used "Root Explorer" to restore "batterystats.bin", the battery status would still be at 58% until I charged it up, when it charged to ~95% the battery status got corrected by the phone and dropped down to 90% and continued on.

This self correcting occurred a couple times until accurate 100% full charge achieved.

You can get faster instant final result if you pushed "batterystats.bin" with ADB. Or perhaps one of the DEVs will create a CWM backup and restore script which will allow for flash or wipe at any time with no regard to battery life problems.
[Fascinate Android Development] SmokeyDP:
I ran this script at 100% this morning because I haven't had the greatest battery life and even with a light use I am showing 68% battery life left. I'm running Super Clean 2.4.

7 hours since unplugged

Display 40%

Standby 23%

Android System 12%

Phone Idle 6%

Android OS 2%

What's odd is if I click on standby it says 'Time on 14h - 50% without signal'
[Fascinate Android Development] lentm:
could you share your saved "batterystats.bin" and explain how to restore "batterystats.bin" by using "Root Explorer" more in details? :P

I guess your method to calibrate battery will help many people who have poor battery life.
[Fascinate Android Development] beray5:
"Root explorer" is a file manager for Android root users (available in MARKET). It let you copy, paste, and move files including files normal users had no access to such as "/data/system/batterystats.bin". My "batterystats.bin" is specifically calibrated to my battery and of no use to anyone else.

You need to generate your own "batterystats.bin" specific to your battery by using the procedure in the thread below...

http://xdaforums.com/showthread.php?t=939425

Please read the whole thread to fully understand -> you need to complete 3 full charging cycles without wiping the stats for finalized optimal calibration.

EDIT: Further elaboration...

With a fully calibrated data set, my phone corrected itself 3 times while charging up to 100%. It would always corrected itself a small amount at a time to prevent burning or blowing up the phone in the event that the known calibration table was in error or corrupted (3 corrections in one single charge up).

Without a fully calibrated data set your phone will also be correcting itself, but only one correction per charge cycle hence you need to perform 3 full cycles to be fully calibrated.
[Fascinate Android Development] justinjbaron:
Just ran the bstats script for the first time after having poor battery life ever since the first time I flashed EB01. Hope this helps.

I did this with my extended battery at full charge.

However, I swap regularly between my standard and extended batteries.

Should I run the script with the standard battery as well? Is the phone smart enough to calibrate itself to use each battery properly?

Thanks.
[Fascinate Android Development] onionz:
Forgive my ignorance but is this script effective if you have an extended life battery?
[Fascinate Android Development] beray5:
It should do the same for extended batteries. But I don't have an extended battery to verify it for you.

The phone only had a single battery calibration table, it's not smart enough to handle 2 different batteries with significant different charge capacities.

There are multiple available extended batteries, for battery helps you should state what it is, for example all STDs are by default 1500mAH batteries.

Have you ever heard of short cycle calibration?
[Fascinate Android Development] justinjbaron:
I have the oem extended battery which I believe is 2200mAH. No, I haven't heard of short cycle calibration, will have to Google it.

If you were me, and flipped between std/ext batteries on a regular basis, which would you calibrate to?

Yesterday Morning I calibrated with big one and was very pleased w battery life. Interestingly the phone stayed at 20% ALL night...then lost juice as I used phone this morning. Swapped to small battery around noon today and I am approximately 70% right now.

At first this seemed like excessively fast drain on the small one, but now I am on the fence.

Overall battery performance is much better after running the script but I want to maximize things moving forward.

Edit: writing this reply, battery dropped from 70 to 67
[Fascinate Android Development] beray5:
Very unlikely it could be googled, I tried 4 given googled links and they were all wrong. The name meant exactly what it is - shorten calibration cycle but still maintaining accurate calibrated data set.

Depends on how you swap the batteries in/out, but the calibration table sooner or later ended up mangled.

You should just stick with the 2200mAH battery and keep the STD for emergency. Properly calibrated the extended alone should do the job for you.

I hesitated a lot in posting anything. I was born, raised, and educated in a non-English speaking third world country, I've never had an English class. I learned English with a dictionary and reading a lot, there're many words I could write but not know how to say them.

But if you're willing to put up with my "ENGRISH" and willing to risk, I'll show you how to do a short cycle calibration.
[Fascinate Android Development] justinjbaron:
For the purpose of keeping this post from straying from the original topic and toward my own personal battery scenario, I have elected to talk with Beray via PM.

Thanks adrynalyne for all your great efforts
[Fascinate Android Development] ragarm:
I know this doesn't pertain to the title, but seeing how it is in with the main post connected, I thought I would ask here.

Do u have to run the fix permissions through cwm?
[Fascinate Android Development] beray5:
You install the scripts with CWM and run the scripts with terminal emulator or ADB shell.
[Fascinate Android Development] peckjh:
Disable lagfix first before flashing in cwm?

Sent from my Fascinate using EB01 Superclean 2.6 with VooDoo
[Fascinate Android Development] akaine2001:
No need for that, just flash in CWM.

Then, in Terminal Emulator run these commands in this order:

su

bstats

Then phone should reboot. if it ask for permissions, allow it and try again since u prolly will lose keyboard off the screen when clicking allow.

edit: And make sure you have your battery charged all the way at 100 and says full before you do the bstats cmd. *MUY IMPORTANTE******
[Fascinate Android Development] SeatownGST:
is this embedded in the newer+tweaked+fixed versions of CWM?
[Fascinate Android Development] jonesin:
I keep getting this in terminal emulator

/system/bin/sh

cd /system/bin

./rm /data/system/batterystats.bin

sleep 5

reboot

/rm not found...

Does this men that batterystats.bin is in fact not being removed?
[Fascinate Android Development] jonesin:
*mean... F u k you swype
[Fascinate Android Development] exzacklyright:
yeah i thought you just had to flash in cwm and that's it. doh!
[Fascinate Android Development] akaine2001:
It's in the newer roms but I don't think it's in cwm
[Fascinate Android Development] hhp_211:
OK guys I have done a battery stats wipe.:)

... ... will now discharge, charge, wipe again and be good...hopefully

I am really curious as to how long it takes you to

RE-Charge

the battery.

up till this point, and the reason for me searching about the battery life topic, which my life has been pretty poor,... the charge time is ridiculously long ... like more than 4 hours either the USB [2 different usb and 2 different pc's] or Wall plugs [2 different ones], even if I have a % on there.

I have rarely seen the 100% u can unplug popup people talk about.

I have not seen any time spec on it either.

but it seems with an 800ma charger it should take approx 2 hours to charge a dead/discharged 1500 mah battery,... right?

I am hoping the wipe will help with this too, but I have not heard anyone talk about charge times long or short.

One other thing I have the 'battery indicator' program and it shows discharging from 86% when the phone said 100% and unplug.

maybe the conditioning will fix this , I did not see a place to clear it's cache or anything... ...

.
[Fascinate Android Development] Marília de Oliveira:
Please concerte the link to download impossible. Thanks
[Fascinate Android Development] skepticmisfit:
wiping battery stats actually is placebo and doesn't really do anything. it does not "calibrate the battery". if you would like to wipe battery stats, charge the phone to 100% as android wipes the file automatically.
[Omnia II General] fusioncoast:
All who would like to request developers for Win Phone 7 on their omnia 2 plzz post a request it below
[Omnia II General] Mirtma:
+1

Yes I would like
[Omnia II General] Math3s:
I would like too ;)
[Omnia II General] l3ong91:
Even though porting of WP7 has been successful on device such as HD2, however, Microsoft seems not planning to help the developers and hackers in realizing the dream of running WP7, so most likely even if the porting is successful, most or some features and applications are NOT likely to work.

Refer to: http://wmpoweruser.com/microsoft-comments-on-windows-phone-7-htc-hd2-port/
[Omnia II General] fusioncoast:
i would still like to have another OS on my phone just wna get rid of winmo 6.5
[Omnia II General] l3ong91:
LOL...aren't you satisfied with Android?
[Omnia II General] lj27416:
Omnia II Runs winmo
[Omnia II General] l3ong91:
There's a Android porting over now and I'm talking to Fusioncoast btw.
[Omnia II General] eng_tamer6:
sure I do too

bu i have read before it's not possible cause of the buttons and minimume requirements

i hope u can do it
[Omnia II General] dkjwong:
Yes please, that would be nice to play with.
[Omnia II General] alabama20:
I want it too...
[Omnia II General] liq69ers:
+1

I would like to play with wp7 on my omnia2 :)
[Omnia II General] iamwin:
i would love to have wp7 too! :) i support your team, gurus! :)
[Omnia II General] freefall12:
who wouldn't want if possible?

Omnia2 isn't in the same league with HD2 in terms of hardware specs.even if it's possible, i guess it will be extremely slow
[Omnia II General] 7827505059:
Microsoft has officiallly announced that no WM6.5 or WM6.1 operator can upgrade to Windows Phone 7....even by flashing......
[Omnia II General] mu-sensei:
count me in, i want winmo7 too...
[Omnia II General] NeoS:
This is the truth, sadly. And this thread is going nowhere.

Sorry guys.
[Nook Color General] kg_jettaIV:
So I'm booting Honeycomb off SD and all was fine and dandy. I got Market setup and all was well.

Well I decided to get a little adventurous thinking there wasn't much to lose and decided to push the system folder for all the GApps in the Froyo walkthrough. Now my Nook just boot loops, each time displaying an activation screen with LogicPD Zoom2 then immediately rebooting.

I have an idea of what is wrong, its trying to run a Google activation when it boots up, but since its the wrong device is boot looping. What I'm looking for is what apk to take off the SD card and in what directory I would find it to get myself out of this pickle. I'm trying to avoid starting over with the Honeycomb build, but it wouldn't be the end of the world.

So I'm thinking it may be OneTimeInitilizer.apk but am realizing I can't access the partition on the SD card directly from Windows. Any ideas

Edit: I may be able to get adb shell for a few seconds before reboot if that helps, I may be able to queue up the commands necessary and get them off in time.

Edit 2: Tried my (most likely wrong) attempt at the above idea. Created a batch file to mount as rw and then run adb uninstall /system/app/OneTimeInitializer.apk but it never worked. Either gave me Failure or "Error: Could not access the Package Manager. Is the system running?"
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] K33NA:
can someone please tell me how to install the most recent android 2.2 on my tmobile htc hd2....please i really need some help feel free to pm with answers
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] tictac0566:
1) I strongly recommend to clearly state your question in the title

2) I strongly recommend to read some sticky´d threads here. You´ll find great tutorials.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] K33NA:
okay thank you so much for taking the time to reply...i will look in the threads
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] omer1982:
Dear All,

I've been using T-Mobile HD2 for last 2 months and installed android, wm 6.5 and wp 7 several times without any problem (I love trying new roms).

For the past few days im facing serious issues with my device. Phone freezes/reboots at least 9/10 times a day. When it reboots it sometimes vibrates 4-5 times then hangs. I tried several radios/roms and the problem still persists. It is mostly stuck on the htc logo and i need to get into bootloader to install something new.

Today i decided to go back to stock T-Mobile Rom. I downloaded the version "RUU_Leo_1_5_TMOUS_3.14.531.1_Radio_Signed_15.42.50.11U_2.15.50.14_2_Ship". It flashed flawlessly but it took me 3-4 attempts (freezing issue) to load the device completely. While i was completing the settings the following error appeared:

"ARM 11 Fatal Error" and the device froze. The same thing is happening again and again. Please help!!!:mad:
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] axman79:
I was having similar problems with my previous hd2. Reboots, freezes ....after 1 month of use. They replaced mine. There was something wrong with the motherboard.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] mhinze:
Have you ever flashed without SD card.