Script to Delete Battery Stats

Can this be replicated by deleting the /data/system/batterystats.bin file? If not what else needs to be done if I were trying to do this manually?
 
Is that right? OP says to install in CW and that THEN you can run it CW or Terminal.

For Terminal (I used android terminal emulator from the market)
1. after installing bstats.zip in CW boot phone back up
2. open terminal emulator, press menu button, then preferences
3. scroll down to "shell" and changed initial command to read
"export PATH=/system/xbin: $PATH
4. press back button, Terminal will close, reopen terminal
5. type "su" hit return, grant su when promt pops up
6. type "bstats" and hit return
7. phone will reboot.

I dont know if any of the above is correct but both worked for me.

This worked for me thanks!
 
Is that right? OP says to install in CW and that THEN you can run it CW or Terminal.

For Terminal (I used android terminal emulator from the market)
1. after installing bstats.zip in CW boot phone back up
2. open terminal emulator, press menu button, then preferences
3. scroll down to "shell" and changed initial command to read
"export PATH=/system/xbin: $PATH
4. press back button, Terminal will close, reopen terminal
5. type "su" hit return, grant su when promt pops up
6. type "bstats" and hit return
7. phone will reboot.

I dont know if any of the above is correct but both worked for me.

Under Shell, what is the default "Command Line" setting supposed to be? I changed this one instead of the "Inital Command" by mistake.
 
Under Shell, what is the default "Command Line" setting supposed to be? I changed this one instead of the "Inital Command" by mistake.

Command line should read "/system/bin/sh -" make sure to put a space between "sh" and the (-)

I tried the process again and found out that it's not even necessary to changes any of the default settings. So to simplify:

1. Install Android Terminal Emulator from the market (free)
2. Reboot into CW and install "bstats.zip"
3. Reboot system
4. Open Terminal Emulator
5. Type "su" then hit enter. Grant su when promt pops up
6. Type "bstats" and hit enter
7. Wait...4-8 sec....phone will reboot on its own.
 
  • Like
Reactions: Jodiuh and Jmac9
Command line should read "/system/bin/sh -" make sure to put a space between "sh" and the (-)

I tried the process again and found out that it's not even necessary to changes any of the default settings. So to simplify:

1. Install Android Terminal Emulator from the market (free)
2. Reboot into CW and install "bstats.zip"
3. Reboot system
4. Open Terminal Emulator
5. Type "su" then hit enter. Grant su when promt pops up
6. Type "bstats" and hit enter
7. Wait...4-8 sec....phone will reboot on its own.

I guess on that note... What is the default for "Initial Command" as well?

When I start Terminal Emulator, I can open the menu and preferences, but I can't type any inputs.
 
Is that right? OP says to install in CW and that THEN you can run it CW or Terminal.

For Terminal (I used android terminal emulator from the market)
1. after installing bstats.zip in CW boot phone back up
2. open terminal emulator, press menu button, then preferences
3. scroll down to "shell" and changed initial command to read
"export PATH=/system/xbin: $PATH
4. press back button, Terminal will close, reopen terminal
5. type "su" hit return, grant su when promt pops up
6. type "bstats" and hit return
7. phone will reboot.

I dont know if any of the above is correct but both worked for me.

I did what you said and it ran like a champ! I still doubt my battery will improve but it is an everlasting quest for me at this point. ;-)
Do we need to put the initial command line back to it's default? If so what was it?
 
Command line should read "/system/bin/sh -" make sure to put a space between "sh" and the (-)

I tried the process again and found out that it's not even necessary to changes any of the default settings.

Initial Command is originally set to export PATH=/data/xbin: $PATH but it won't grant me super user permissions, I type su and it says su: not found . After I changed Initial Command to export PATH=/system/xbin: $PATH when I type su and it gives me the superuser notification and terminal emulator is listed in the superuser app.

However when I launch Android Terminal Emulator i get:

export PATH=/system/xbin: PATH
$ export: /sbin:/system/sbin:/system/bin:/system/xbin
: bad variable name

Am I doing something wrong? Just trying to learn :)
 
So do we just run this in emulator and let the phone reboot? No other steps? And does the phone battery have to be at 100% for this to work?

Sent from my SCH-I500 using Tapatalk
 
So do we just run this in emulator and let the phone reboot? No other steps? And does the phone battery have to be at 100% for this to work?

Sent from my SCH-I500 using Tapatalk

I am very impatient when it comes to things like this so I ran it at 50% just to see if ran. I'll do it again when it reached 100%.
 
If you're looking for them, all the Juice Defender posts were moved here.

Now to drain the life outta this thing.

Adrynalyne: With this script, is this part still necessary? I hate to do this, as it's really hard on a battery, but I definitely have this issue and will do the drain if it's a requirement.
 
Adrynalyne: With this script, is this part still necessary? I hate to do this, as it's really hard on a battery, but I definitely have this issue and will do the drain if it's a requirement.
Wondering this as well. Ran the batt script this morning, been kinda lazily reboot-draining battery for the past 2 hours and down to about 40%. Battery % seems to be holding up better than it was yesterday, when I hit dead after maybe half a day.
 
Initial Command is originally set to export PATH=/data/xbin: $PATH but it won't grant me super user permissions, I type su and it says su: not found . After I changed Initial Command to export PATH=/system/xbin: $PATH when I type su and it gives me the superuser notification and terminal emulator is listed in the superuser app.

However when I launch Android Terminal Emulator i get:

export PATH=/system/xbin: PATH
$ export: /sbin:/system/sbin:/system/bin:/system/xbin
: bad variable name

Am I doing something wrong? Just trying to learn :)

Try using the default Shell commands. I dont think yours are right.

Defaults:

Command Line:
"/system/bin/sh -" make sure to put a space between "sh" and the (-)

Initial Command:
export PATH=/data/local/bin: $PATH
 
  • Like
Reactions: JeremytheIndian
I wanted to let folks now I am seeing better battery performance on EB01 SC 2.4 after running the bstat reset script manually (not from cwm) as posted by Adrynaline.. I getting crazy good (87% since unplugging 4 hours ago) - Contrast Min, Background and Autosync OFF..
 
Initial Command is originally set to export PATH=/data/xbin: $PATH but it won't grant me super user permissions, I type su and it says su: not found . After I changed Initial Command to export PATH=/system/xbin: $PATH when I type su and it gives me the superuser notification and terminal emulator is listed in the superuser app.

However when I launch Android Terminal Emulator i get:

export PATH=/system/xbin: PATH
$ export: /sbin:/system/sbin:/system/bin:/system/xbin
: bad variable name

Am I doing something wrong? Just trying to learn :)

For me when i open Android Terminal Emulator i get:

export PATH=/data/local/bin:$PATH
$ $
and i just type su then hit enter it says superuser permission granted and
a # populates the third line so it looks like this:
export PATH=/data/local/bin:$PATH
$ $su
#

then i paste the bstats script minus the "#!" in the front and it runs then reboots... im guessing it ran okay
 
i dont think you need to paste anything. after su is granted just typing "bstats" and hitting enter will run the script and reboot.
 
Adrynalyne: With this script, is this part still necessary? I hate to do this, as it's really hard on a battery, but I definitely have this issue and will do the drain if it's a requirement.

Wondering this as well. Ran the batt script this morning, been kinda lazily reboot-draining battery for the past 2 hours and down to about 40%. Battery % seems to be holding up better than it was yesterday, when I hit dead after maybe half a day.

I think I answered my own question. Ran the battery down to about 4% and then stuck it in my DJ05 Fascinate. Booted up and the battery was barely drained at all. So the problem isn't that it's killing the battery, it's that EB01 is reading it incorrectly (I guess).
 
i dont think you need to paste anything. after su is granted just typing "bstats" and hitting enter will run the script and reboot.

thanks... i thought that way was too round about and knew it should be easier than that.
 
I think I answered my own question. Ran the battery down to about 4% and then stuck it in my DJ05 Fascinate. Booted up and the battery was barely drained at all. So the problem isn't that it's killing the battery, it's that EB01 is reading it incorrectly (I guess).

Then I go back 10 minutes later and the battery indicator is down in the orange area, so hell I don't know. :confused:
 
Yeah, Cory, I don't know much about all this stuff.. But my first thought was that these builds aren't allowing the phone to read the battery life correctly. So say, your battery may have 30 percent left, but if it say's 0, it's going to shut down. I have been getting like 12 hours out of my battery, so it's not bad at all. I ran the script in terminal emulator, so we'll see what that does.
 
Yeah, Cory, I don't know much about all this stuff.. But my first thought was that these builds aren't allowing the phone to read the battery life correctly. So say, your battery may have 30 percent left, but if it say's 0, it's going to shut down. I have been getting like 12 hours out of my battery, so it's not bad at all. I ran the script in terminal emulator, so we'll see what that does.

Thanks. That makes sense. How charged up was the battery when you ran the script? I'm still unclear on this one piece.
 

Trending Posts

Forum statistics

Threads
956,693
Messages
6,969,517
Members
3,163,600
Latest member
Marabishi