Hi All. I've been a lurker for a while but have never posted. I can't post in the beans thread until I hit my 10 post count. So here's the deal:
Verizon GS3
Unlocked bootloader
Rooted
Beans Custom ROM 10
Imo's .6 Kernel
I've run Beans version 8,9, and 10, and haven't really noticed these issues until recently. I haven't been able to fix them after trying and searching the forums, even though I've noticed a couple people with similar issues.
1) Slow Charges - I can go to sleep and plug my phone in, wake up 6 hours later and it still won't be fully charged. I could maybe get 50-60% charge. Phone will of course be off and in standby while charging. (have tried resetting battery statistics in CWM)
2) Fast charge doesn't work - I've tried opening the terminal emulator and typing in "ffc." It will tell me fast usb charging is enabled, but I will see no decrease in charge time at all. Someone on the beans thread mentioned going from 59% to 77% in 10 minutes on fast charge. I will make sure it's unplugged, run ffc, then plug it back in.
3) Overclocks won't stay. I'll run something like SetCPU and bump my max clock up to 1900 but as soon as I go to a different app or run a benchmark, I will come back and even though 1900 MHz is highlighted, 1512MHz will be the "max" setting. I've tried Antutu and quadrant. Antutu will tell me my clock is 1500 MHz after the test is run and I look at results.
4) Benchmarks suck. Now I know benchmarks don't necessarily mean anything, But it's a decent way in my opinion to compare how my phone is running to others, when they're running the same phone, rom and kernel. People running beans 10 are in the 5400-5700 range with Quadrant, while i'm in the 4000-4500 range. I ensure RAM is dumped and nothing is running while I do a benchmark test. (others are getting Antutu scores around 7500-7800, i'm getting 6600)
5) Occasional rapid battery drain. This one is a bit hit and miss, It doesn't happen all the time and I haven't been able to pinpoint a cause with it. But I will occasionally get very rapid battery drain, eg, I can just be surfing the web and lose 10% battery life within 10-15 minutes.
If anyone has any information on these, please let me know. I do apologize if fixes are common knowledge, but I have searched and haven't seen any. Although I've used droid for a while, my GS3 is my first dive into custom ROMs and the like.
Thank you for your time.
1. Any time my phone charged very slowy(turned on), all I had to do was reboot it. Now it seems different for you since you're charging it while its off. I've also found unplugging it and then plugging back in has helped when charging.
2. Never have used this so I don't know
3. Again not sure, 1500 mhz is fast enough for me lol
4. I say as long as your phone is running quick, responsive, who cares about benchmarks. They are meaningless.
5. Download either better battery stats(paid) or GSam(free) and see what is using up your battery
I haven't had any issues on Beans 10
Sent from my SCH-I535 using Tapatalk 2
I have this same problem and i don't think the Rom is your issue. I have mine rooted and that's all that I've changed.
Yesterday i had my phone plugged in charging for literally 8 hours and barely hit 60%
I got pretty pissed because I've noticed it for awhile. I ended up trying an old cell phone charger i had laying around. I think from the incredible. A different wire and wall plug. Within about an hour i was at 100%
Rapid drain i just have no idea. I use battery saving mode and still the battery lasts like 4 hours with light use. It's so frustrating. It looks like "android system" uses it all but i really don't know why. I've been tempted to wipe the phone and see it didn't seem to happen til i rooted.
Sent from my SCH-I535 using xda app-developers app
Yeah guys those definitely aren't normal results. I would full wipe and try again.
I have actually exclaimed at the speed in which the battery charges on mine. And get around 12-14 hrs with moderate use. But I'm on synergy.
I will say there seem to be some bunk batteries getting shipped with the S3. I work as tech support for Asurion, and that's an issue I have seen more than once. And these are people that have no idea what rooting.. Or even android is. So any rom or kernel combination can be ruled out.
Sent from my SCH-I535 using xda premium
Related
I purchased the Droid Charge based on the Engadget review of the device. In particular, I wanted a device that could get on the LTE network AND have great battery life. This excerpt sold me:
When it comes to battery life, there's no competition. The Charge blitzed through a full day of what we'd consider typical use, coming off the charger at about 9am and not getting slotted back in again until 9pm the next night. Yes, you read that right, two working days of what we'd consider average use with GPS and WiFi on, taking pictures and videos, all powered by a single 1,600mAh battery. Granted, we weren't running our performance benchmarks at the time, but we were hammering the LTE antenna to get some speed results.
I expected to get, at a minimum, a full day's charge using LTE on this device, considering I live in an area where LTE isn't hard to come by (Los Angeles). Alas, I was sorely disappointed when my battery drained within 5 hours with minimal use. 5 hours!!! How can Engadget claim it will last for two days and that "there's no competition." It's totally misleading. The Droid Charge has a serious battery issue which nobody can seem to get to the bottom of. I even tried installing the latest Gingerbread rom to ameliorate the issue, but to no avail. Has anyone gotten a full day's use out of the device when on the LTE network?
Stockmoose16 said:
Has anyone gotten a full day's use out of the device when on the LTE network?
Click to expand...
Click to collapse
I just got back from a full day's use on 4G with GPS on, WiFi on and Exchange and Gmail pushing mail as needed. I did not, however, text at all. One of my pages has an IP camera app that updates three feeds (snapshots) at least every five minutes. I am in a pretty consistent 4G area except when I'm at home (Philladelphia suburbs by my home is in a geographically challenged location)!
The phone just turned off as it dropped below 2% so I can't give any battery stats; I've been following the battery recalibration procedure listed here.
Keep the faith...you may not reach two days but you should be able to get a lot more than 5 hours!
rmanaka said:
I just got back from a full day's use on 4G with GPS on, WiFi on and Exchange and Gmail pushing mail as needed. I did not, however, text at all. One of my pages has an IP camera app that updates three feeds (snapshots) at least every five minutes. I am in a pretty consistent 4G area except when I'm at home (Philladelphia suburbs by my home is in a geographically challenged location)!
The phone just turned off as it dropped below 2% so I can't give any battery stats; I've been following the battery recalibration procedure listed here.
Keep the faith...you may not reach two days but you should be able to get a lot more than 5 hours!
Click to expand...
Click to collapse
Out of curiosity, which ROM are you using to get this kind of battery life? I just installed the latest Gingerbread leak and my phone is leaking battery at a rate of 15-20% per hour. I saw that re-calibration post, but I'm wondering if I can simply charge my phone to 100% and place the same ROM on top of the one I already installed. Just want to make sure I don't brick my phone.
Any thoughts?
If you wondering if you can just replace your current COM with the same one you are using by just replacing the files on the SD card then yes you can. If you're asking about re-flashing the same ROM over it again without wiping during the calibration then you can. It shouldn't harm anything.
Schneeder said:
If you wondering if you can just replace your current COM with the same one you are using by just replacing the files on the SD card then yes you can. If you're asking about re-flashing the same ROM over it again without wiping during the calibration then you can. It shouldn't harm anything.
Click to expand...
Click to collapse
I've already installed the latest Gingerbread ROM and updated all my apps and widgets on the device. Can I now charge the device to 100%, bump charge a couple of times (per the instructions in another post on the board), and then restart and wipe the battery stats in recovery mode? Or, do I have to charge to 100% and then completely reinstall the same exact ROM on top of the one I just installed?
Stockmoose.
5 hours? That's questionable that you only got 5 hours with minimal use. No Engadget did not lie, and until the 1700 mah phones are released the end of the month, there is no comparison.
Only with Altered Beast and heavy use was I able to kill the battery in under 8 hours. So I would chalk it up to a bad battery. Not everything is perfect.
Gingerbread is a leak, so trying to compare it to the stock rom does you no good.
You can wipe the battery cache without having to re-flash everything again.
Agreed, I was heavily influenced by the Engadget review and was seriously disappointed when I struggle to get a day's worth of usage out of the stock ROM on 4G.
The Gingerbread leaks have some serious battery issues. I reccomend flashing Humble v1.3 (Froyo) and undervolting. Best battery life by far. I can hammer the LTE radio for a few hours straight.
As a side note, all of Verizon's current 4G Android offerings have awful battery life due to having the dual CDMA and LTE radios. That being said, the Charge evidently has the best life out of the three of them. Future phones (when Verizon dumps CDMA altogether in favor of LTE) will have way better life.
Sent from my Droid Charge
kvswim said:
Agreed, I was heavily influenced by the Engadget review and was seriously disappointed when I struggle to get a day's worth of usage out of the stock ROM on 4G.
The Gingerbread leaks have some serious battery issues. I reccomend flashing Humble v1.3 (Froyo) and undervolting. Best battery life by far. I can hammer the LTE radio for a few hours straight.
As a side note, all of Verizon's current 4G Android offerings have awful battery life due to having the dual CDMA and LTE radios. That being said, the Charge evidently has the best life out of the three of them. Future phones (when Verizon dumps CDMA altogether in favor of LTE) will have way better life.
Sent from my Droid Charge
Click to expand...
Click to collapse
Curious while running Humble v1.3 and undervolting which kernel are you running atm. And second what undervoltage settings are your using atm currently so yo uare getting random reboots. Reaosn I ask is I just flashed v1.3 this am and updated to Imnut's newest OC kernel but have left it alone right now without touching any voltage settings. So any input would be great and I'd like to set mine nad check it out to see if I can get even better battery life out of it. Thanks
Pro tip: Never buy anything based solely on one review.
Sent from my SCH-I500 using XDA App
will2live said:
Curious while running Humble v1.3 and undervolting which kernel are you running atm. And second what undervoltage settings are your using atm currently so yo uare getting random reboots. Reaosn I ask is I just flashed v1.3 this am and updated to Imnut's newest OC kernel but have left it alone right now without touching any voltage settings. So any input would be great and I'd like to set mine nad check it out to see if I can get even better battery life out of it. Thanks
Click to expand...
Click to collapse
This should help.
I get about 12 hours with minimal to moderate usage throughout the day 4G, wifi/gps off for the majority. I might have to try this bump charging, though. Would be incredible to get a solid day out of this thing.
9 hours of using my phone to check XDA post, playing bubble buster, and texting and my phone is at 77%. Only thing different on my phone is i'm using SetCPU to undervolt. But even with that. if you are only getting 6 hours with minor use. There is something wrong.
I just did a solid 36 hours by staying on my home Wifi almost the whole time. I'm using Gummy Charged 1.8. Before everyone starts calling bull----, I probably used the phone a total of 1 hour over that period of time.
Normally, it lasts 14-18 hours with only Exchange mail and an hour of gaming (no facebook, social networks, etc.)
If I recall correctly, battery life was an issue with the gingerbread leaks.
I did the battery charging cycles as mentioned above and erased the battery stats last night. Now I'm down to 20% after 6 hours of light use. That's pretty much the same way as before. What did I do wrong?
robstamack said:
I just did a solid 36 hours by staying on my home Wifi almost the whole time. I'm using Gummy Charged 1.8. Before everyone starts calling bull----, I probably used the phone a total of 1 hour over that period of time.
Normally, it lasts 14-18 hours with only Exchange mail and an hour of gaming (no facebook, social networks, etc.)
If I recall correctly, battery life was an issue with the gingerbread leaks.
Click to expand...
Click to collapse
Not a chance I'll say bull**** that is for sure. When leaving the device on Wifi battery life will DRASTICALLY increase. The radio in the device is what is eating it up. If you want to conserve even more battery I've found and don't ask me why if you actually turn off Mobile data and then turn Wifi on it will help even more.
Ran a test last night and with over 7hrs on Wifi it dropped on 5%
robstamack said:
I just did a solid 36 hours by staying on my home Wifi almost the whole time. I'm using Gummy Charged 1.8. Before everyone starts calling bull----, I probably used the phone a total of 1 hour over that period of time.
Normally, it lasts 14-18 hours with only Exchange mail and an hour of gaming (no facebook, social networks, etc.)
If I recall correctly, battery life was an issue with the gingerbread leaks.
Click to expand...
Click to collapse
I've gotten 24 hours with about 20% to spare going in and out of Wifi and 4G. I had 3 gmail accounts sync'd to the phone and I probably streamed about 20 minutes worth of music using Google Music. But, I probably used the phone for a combined total of 1.5 hours over that period, and it was a slow day, so I actually didn't get many emails.
I think I was using one of the Froyo Gummy ROMs.
I don't think it's very fair to use custom ROMs and then complain about battery life. Was your battery life lower than 5 hours on the stock ROM? Did you even use the stock ROM?
06ms6 said:
I don't think it's very fair to use custom ROMs and then complain about battery life. Was your battery life lower than 5 hours on the stock ROM? Did you even use the stock ROM?
Click to expand...
Click to collapse
Try reading more than skimming the OP. He implied that he started stock there, and about 3 posts down said that it was ridiculous that even the stock ROM couldn't get 5 hours.
doodlebro said:
Try reading more than skimming the OP. He implied that he started stock there, and about 3 posts down said that it was ridiculous that even the stock ROM couldn't get 5 hours.
Click to expand...
Click to collapse
My apologies, I misread his second to last sentence in the OP.
Either way, 5 hours is not normal and I wouldn't blame the Charge just yet. Not sure if you guys have official 2.3 yet (I'm a Thunderbolt owner myself), but I know the Froyo ROMs on the TB have a very noticeable increase in battery life compared to the Gingerbread leak builds.
I get about 6-8 hours of heavy use on my 2.3 ROM on the TB. Probably closer to 13+ with Froyo.
Hello Everyone,
I have been asked to put together an instruction on how to correctly calibrate
your Sammy Charge battery... so here it goes.
First of all you need to be ROOTED there are plenty of roms and kernels here
for you to pick from so get the package you want Odin or Clockwork whatever you want.
-i will be referring to Clockwork Recovery Mod as 'cwr' from now on-
I am currently running IMNUTS 710 Non-Overclock Kernel and Humble 1.4.2 ROM. Humble ROM comes with a battery calibration app that you might find helpful for this task.
The kernel or rom you have doesnt matter for calibration but you must have the latest cwr witch is bundled with any of IMNUTS' Kernels.
You may have heard of the term 'Bump Charging' this only needs to be done before you calibrate (so you Chargers that are doing this every full charge, you are wasting your time). I will explain what this is if you do not know.
Here are the steps:
1.Turn your phone ON and charge it to 100%
2Turn your phone OFF and leave it plugged in. (you will notice that the battery will begin to
charge again but it will not be at 100% anymore it will show something like 95%.
3.LEt your phone get back to 100% (it will vibrate when it is done)
4.Unplug your phone, wait 30 seconds, and plug it back in.
5.WTH! it is back to 95% again!dont panic... LEt it charge again to 100% (2-5 minutes)
6.Now do it again. (unplug wait 30 seconds, plug in, let charge to 100%)
continue this until it shows 100% after 10-20 seconds on plug in. (it took me 15 times,
although i have seen upwards of 20 times)
- some users are saying that the time does not decrease to 100% while doing step 6, 20 times is good enough as all phones/batteries are not from the same mold-
7.Now boot into cwr (if you dont know how then you shouldnt be here)
8.Go to the advanced menu and 'wipe battery stats'
9.Reboot phone via cwr
(((this is where it will differ from the other posts or whatever)))'
10.Drain your phone to 0% and immediately plug it in. (others will tell you to let it die completely and shut itself off... YOUR PHONE WILL NOT LOG CHARGING INFORMATION IF IT IS OFF!!! ((I suggest you do a little troubleshooting to see when your phone will actually turn off. Mine turns off after being at 0% for a few mins. Your's may shut off at anywhere between 10%-0%. If it does shut off just turn it on again and plug it in)). Basically what u am saying is make sure your phone is ON during charging while doing these steps.
11.Charge to 100% (DO NOT UNPLUG IT WHILE IT IS CHARGING... if you get a call or a txt it is fine to use it a bit (and for clearification on 'proper charging' I contacted Samsung it is OKAY to use phone while charging (my bad)).
12.I did this full charge and full drain, plug in at 0% -ON charging, 4 times.
13.Charge it whenever you want.
The android OS logs 'battery stats' and charging habits based on a small window of use. Following these directions will let your phone lock in enough information to max out your battery life.
With strong 4G signal expect 18-20 hours of light use. If you are in a known 4G deadzone download LTE Switch from the Market, it lets you turn off the 4G radio and run only 3G. I personally turn off mobile data unless i need it and have no syncing actions automated. My best uptime was 41 hours and 12 minutes to 0%. Dont forget that all roms and kernels are different so your results will vary. If you are on your phone all the time... playing games, on the net, making calls you will of course have less time.. with heavy use i can burn 10%-15% an hour easy. Get rid of your 'antivirus' crap, your monitoring apps all that shat... it will only sacrifice your battery and it is unnecessary.
For those wondering about LAGFIX:
AlexDeGruven states-
'RFS is the bastard child of FAT and a Samsung developer who didn't understand how modern filesystems work with NAND storage. It has nothing to do with battery usage. For data access, the longer it takes to access the data, the longer the processor is waiting and running wasted cycles. The faster the data is returned from storage, the less battery gets used.'
So turn it on or leave it off, up to you.
I hope this helps everyone get calibrated.
Let me know if you have any questions.
(916) 877-4460 or forum it up!
Reserved for updates
Nice. Hopefully this will stop clogging the forums a little bit.
Sent from my Droid Charge running Humble 1.42
Why is this in the dev forum?
suzook said:
Why is this in the dev forum?
Click to expand...
Click to collapse
...because everyone asks in the rom threads. Im just trying to be helpful so we don't see the same questions over and over again by those who refuse to actually look for info. This way they don't have to go too far.
Thanks criticalhit. If the mods have a problem with the location of this thread...I'm sure they'll move it. Thanks again for the tutorial.
tkm20 said:
Thanks criticalhit. If the mods have a problem with the location of this thread...I'm sure they'll move it. Thanks again for the tutorial.
Click to expand...
Click to collapse
I pmd the mod in charge of the charge dev forums already with reasoning why it should stay.. so we shall see.
I <3 Humble 142!
I went to 100% let it die. next day i used it normal and it was "ok". today my phone has been off the charge for 16 hours now and im still at 39%. Display took 80% of my battery so I'm sure i could easily idle for a few days. the whole time i had 4g and gps on. btw im at stock voltages and oc'd to 1.1ghz
gogreenbay07 said:
I went to 100% let it die. next day i used it normal and it was "ok". today my phone has been off the charge for 16 hours now and im still at 39%. Display took 80% of my battery so I'm sure i could easily idle for a few days. the whole time i had 4g and gps on. btw im at stock voltages and oc'd to 1.1ghz
Click to expand...
Click to collapse
Yeah display burns it up fast. And if you don't have strong 4g 4-5 bars it will constantly 'look' for a better signal where is cycles from 3g to 1x to 4g... eventually someone will write an app or make a system change to combat this.. (I hope). I wish I had the knowledge to do this and make our phones satisfied with low signal strength. :/
I <3 Humble 142!
Well written post... thank you
Sent from my Fascinate (soon to be Charge) via Tapatalk
JOrtenzi said:
Well written post... thank you
Sent from my Fascinate (soon to be Charge) via Tapatalk
Click to expand...
Click to collapse
Hey thanks mang! Im going to do a 3g only all day tomorrow to see what kind of life I get... will update on findings (I usually data off completely).
I <3 Humble 142!
This is exceptional. Great job. Appreciate it man.
Sent from my SCH-I510 using Tapatalk
I am finally getting some decent life
Thanks for writing this and for all the other posts you have spread about your methods, yes I read them.
Today was my best day by far. I was 11hrs and 20 minutes unplugged today when I got home and still had 25% of my battery left. I work in a 4G market, and for the first time today I left 4G off and only had mobile data on a few times. I had 1 hr 30 minutes of cell talking ( thats a lot for me) and had my display on 1hr and 48 minutes. This is on the same ROM and Kernal CritalHits is running (with lagfix enabled).
For those of you that think you can't carry this phone around without a charger, you are wrong (glad I finally beleive this). You just can't have your foot on the Hemi throttle all day and expect to get Prius mileage.
Ya I have at least 4 bars of 4g all over my town. I saw 3g once and it changed back to 4g right away
Sent from my SCH-I510 using XDA App
Awesome post. I've read a couple other posts on battery calibration. They've been somewhat similar (except for the last part, like you pointed out), but not as clear.
I do have a question though: Are battery stats erased along with data and other stuff when you flash a new rom, for example? I'm just wondering if this is something you should do every time you flash a new rom and require a data/cache reset. I'm assuming so, since you mentioned that each rom's battery level may vary.
Anyway, thanks again!
leenephi said:
Awesome post. I've read a couple other posts on battery calibration. They've been somewhat similar (except for the last part, like you pointed out), but not as clear.
I do have a question though: Are battery stats erased along with data and other stuff when you flash a new rom, for example? I'm just wondering if this is something you should do every time you flash a new rom and require a data/cache reset. I'm assuming so, since you mentioned that each rom's battery level may vary.
Anyway, thanks again!
Click to expand...
Click to collapse
yes, every time you wipe data, cache and delvik...recalibrate. Good method. This was the same method posted a year ago or so to help the Dinc get better battery life.
If the battery is properly calibrated shouldn't it make sense to only have to bump charge once?
Sent from my Droid Charge running Humble 1.42
This is the right place for this thread. The Charge forum moderator specifically said "*Only ROM Development, Hacks, Mods, Fixes, Reference, and Tutorials go in the Dev Section"
This is clearly a tutorial, and clearly belongs here.
http://forum.xda-developers.com/showthread.php?t=1074281
criticalhit said:
(((this is where it will differ from the other posts or whatever)))'
10.Drain your phone to 0% and immediately plug it in. (others will tell you to let it die completely and shut itself off... DO NOT LET IT DIE! YOUR PHONE WILL NOT LOG CHARGING INFORMATION IF IT IS OFF!!!
11.Charge to 100% (DO NOT USE OR UNPLUG IT WHILE IT IS CHARGING... if you get a call or a txt ignore it).
Click to expand...
Click to collapse
There's a problem with your process, and it is step 10. Some Charges will shutdown prior to hitting 0% battery level. I've seen my Charge auto-shutdown at 5%, 3%, 2% and 1%.
Also, I don't see the point of letting it drain to zero then charging it back up to 100% without any use. One more thing, you didn't specify whether you wanted the phone off or on during step 11's charge process, but I'll assume you want the device on considering the fact that you mentioned getting calls/texts.
OP, please explain comments about lagfix
What does "lagfix" do? Are you saying that it causes the battery to be used at a faster rate?
I thought lagfix involved making at least some of your on-phone partitions into ext4 rather than Samsung's format.
Thanks for the clear instructions, it includes a detail that makes a lot of sense, except wouldn't the phone shut itself down gracefully when the battery was gone, saving the battery stats?
So I read that a ton of ppl has issues hitting 100% battery charge, I'm also seem to be having the issue till I got and played Plants vs Zombies...after like 1 hour playing I was about to turn on the alarm and hit the bed and I just noticed my battery level, 100%....so I thought that it was an error and I locked the phone just to see on the lock screen "charged"....btw, when I started playing the battery was at around 92% and I've never seen 100% before on my NS.
How many ppl is able to get their phones to fully charge to 100%? and, does any of u installed or did anything in particular to fix the issue?
Hm, only had mine 2 weeks and have yet to get a 100. My epic would but it was a faux 100 if anything as it. Would drop down to around 98-96 immediately.
Sent from my Nexus S 4G using Tapatalk
fenrry said:
So I read that a ton of ppl has issues hitting 100% battery charge, I'm also seem to be having the issue till I got and played Plants vs Zombies...after like 1 hour playing I was about to turn on the alarm and hit the bed and I just noticed my battery level, 100%....so I thought that it was an error and I locked the phone just to see on the lock screen "charged"....btw, when I started playing the battery was at around 92% and I've never seen 100% before on my NS.
How many ppl is able to get their phones to fully charge to 100%? and, does any of u installed or did anything in particular to fix the issue?
Click to expand...
Click to collapse
Only way to hit 100% is to use an external battery charger.
Sent from my SCH-I800
https://market.android.com/details?id=com.elondra.nexusscharger&feature=search_result
you can use that if u really want too get too 100% i used for a few weeks then just stopped caring. Its just the way samsung programmed it to pro long the overall life of the battery.
Yeah, mine caps at 95% normally. Might have a look at that program. How much shorter would battery life be if we let it charge to 100%?
If you leave the screen on (by any means, whether you were playing game, which requires you to have the screen on, or change the setting to have screen always on), it will charge to 100%.
will the battery life shorter with this trick or using that app to force to charging completely ?
Its not an issue. Samsung designed it that way. Its to help keep the battery healthy and extend its life.
Sent from my Nexus S 4G using xda premium
I honestly don't see it being noticeably shorter life span. We keep phones for a max of 2 years now days. I rather have a full battery now then it last an extra few months. Battery's are cheap so we dont need them to last forever .
Well, I have used the phone while connected to the charger but never passed 96%, only after playing PvsZ I got the 100% and then the number went down till 96% and stayed that way after I closed the game.
fenrry said:
Well, I have used the phone while connected to the charger but never passed 96%, only after playing PvsZ I got the 100% and then the number went down till 96% and stayed that way after I closed the game.
Click to expand...
Click to collapse
ya the only time ive ever seen a phone stick on 100% for longer then 10 minutes is using SBC kernels
jietzer said:
ya the only time ive ever seen a phone stick on 100% for longer then 10 minutes is using SBC kernels
Click to expand...
Click to collapse
I'm running Formels MIUI, it comes with Pete#5....still....gonna test again with PvsZ in a bit, rt now the phone has been steady at 96% for the past 2 hours....man gotta sleep soon also...
***Update: PvsZ does work to go pass the 96%, I hit another 100%....
How many times is this very topic going to be discussed? And with all the info on xda, why is there so much false/incorrect information in this thread?
Sent from my Nexus S 4G via XDA Premium
Here's some things I've discovered about my phone and thought I would post them in case some one else has the same problems.
I've had my Tbolt for a few months now. For the first month I used the stock rom and it sucked really bad, I hated the phone. It was so laggy, tap on something and wait 2 or 3 seconds for anything to happen. So I went to a GB AOSP rom. Loved it, nice and fast BUT I hate and despise the whole gingerbread keyboard experience. I loved the keyboard on my stock Incredible. I endured for a couple months with the GB keyboard.
In that time my battery started not charging to 100%, it only goes to 89%. Come to find out it is being charged all the way because I checked the voltage with a meter and it reads 4.2 volts after being charged for several hours. No big deal other than an annoyance. I get 6-7 hours of pretty much non stop use with the seidio 3500 mah battery. The other annoying thing is it drops pretty fast and when it get's to 2% it will stay on 2% for 2-3 hours of non stop use before it finally dies.
So I set out to remedy this with every kernel I could finally, several different GB aosp and sense roms, resetting battery stats in CWM, different battery calibration apps and nothing worked. So I gave up on that, after all I was still getting full use of the battery.
Then I noticed not too long after I started using GB AOSP roms that my d/l speed dropped way down. With the stock rom when I first got the phone I would consistently get 15+ mbps speed, awesome. When I went to GB AOSP it dropped to 5 mbps, usually alot less than that, but would occasionaly go up 10 mbps. The internet was slow, youtube vids were grueling to try and watch with the HQ setting on. Took at least 10 seconds before the vid would start and then it would stop and buffer constantly during playback on HQ setting. That really pissed me off so I tried every radio I could find but nothing changed. The only thing I noticed was after a fresh restart the d/l speed would go up to 10 mbps for a few minutes but would quickly drop back to 5 or less, usually around 3. I was pissed because I thought it was Verizon's fault.
So a couple weeks ago I decided screw it, I really hate the GB keyboard so I went back to my stock Froyo rom. It was slow and laggy as usual but I like the keyboard experience better and noticed my freakin d/l speed was back to normal. With Froyo it never drops below 10 mbps and is usually 15+. So I decided to install Lancher Pro and see what happened, I'll be damned if most if not all the lag was gone. Tap on something and bam there it was. I was happy....until my fully charged 3500 mah battery died after only 2-3 hours of use. I was like what the hell??? So I started installing various Froyo sense and de sensed roms in order to keep my froyo keyboard and great d/l speed but see if I could improve battery life. Every Froyo rom I tried would kill the 3500 mah battery in 2-3 hours of non stop use no matter what I did. So I decided to check the voltage on the "dead" battery and it showed 3.9 volts which is NOT dead. 3.6 to 3.7 volts should be dead. So where the GB roms would at least give me full battery use (and cut my internet speed to nothing) the Froyos won't for whatever reason, they just won't read the voltage right. And by the way, no battery app I've ever used will read the right voltage on the phone. It's usually off by .3 or .4 volts. When the battery dies the app says it at like 3.3 to 3.4 but the meter says 3.6 to 3.7 so don't trust those battery apps too much.
Anyway, so I had a dilemma, use a GB rom with full battery life but crappy d/l speed and a keyboard I hated, or use froyo with a keyboard experience I loved with great d/l speed but not full life of my battery. I would go thru 3 3500 mah batteries in one night at work and still have to put it on the charger before the end of the night. 2 were cheap ebay batteries, wouldn't last no time really with Froyo. (and Yes my job has a lot of downtime most nights so I use the hell out of my phone. lol)
So a couple nights ago I decided to try a sense 3.5 rom. Love it!! Love the keyboard experience, my d/l speed is freakin awesome with the 906 radio, and my awesome battery life is back!! And it's pretty fast too, not quite as fast as an AOSP but I can live with it. Videos on youtube with HQ on start within a couple seconds and I have yet to have one stop and buffer. Awesome devs we have here!! I just wish one of them could fix the battery issue so it would actually show 100% charge instead of 89%.
Anyway, just thought I'd share the problems and fixes I've had with this phone over the last few months.
Try wiping battery stats in recovery?
Sent from my ADR6400L using Tapatalk
That is interesting. My guess is that your issue has something to do with your hardware because of you getting different voltage readings from a meter vs phone app. At least you have found an acceptable fix to your problem for now.
Have you ever updated your radio software? That may be the answer to your dilemma.
***Just want to clarify this is Beans 6 discussed in this initial post***
Hey guys. Been a member for awhile now, but haven't posted much so can't post in Dev section. I've seen quite a bit of discussion in the Beans thread about clock speed and hot phones, so I thought I would create a quick thread to share my experience and observations.
Unfortunately at this time I'm not 100% sure about my initial observations since I didn't know what I was looking for at the time. But the basics are that Beans uses Imoseyon's Lean Kernel and it comes in clocked at 1900Mhz. The tricky bit was that at first on Beans, I was experiencing the behavior that my settings in SetCPU were not being respected. With clock set at 1512 Max it was still spending time at 1900.
So first thing I did was reflash the Kernel from Imoseyon's thread. Realized it was a test/beta kernel at that point, so was expecting it to not be completely perfect. Not exactly sure which version is in Beans 6, but once I reflashed 12.2, my setcpu setting seem to be respected. Until I plugged it in to charge. Then it once again jumped up to 1900. So I made a profile in setcpu for when on the charger and locked it down to a lower level and it's has stayed at the levels specified in setcpu since then.
Now I'm just using more battery that I want to be, but still have to track down whether is a kernel thing, an app thing, or a phone thing...guess I should have baselined the new phone before flashing...
Anyway, just updated to Beta v0.1 and will report back on my battery findings.
I had amazing battery life with beans. The thing you have to do for sure is lower the CPU. 1.9 is way to much and the phone runs extremely hot. I just started synergy 1.6 and battery script today. I'm going to compare my battery life tomorrow. I recall on beams r6 it took 3 hours of screen off time for me to even lose 1% battery!
The only thing I don't like about beans is the scrolling wallpaper..wish he'd give us a flash to remove it . Also sucks not being able to charge your phone while its off with the custom kernel.
Sent from my SCH-I535 using xda app-developers app
duarian said:
I had amazing battery life with beans. The thing you have to do for sure is lower the CPU. 1.9 is way to much and the phone runs extremely hot. I just started synergy 1.6 and battery script today. I'm going to compare my battery life tomorrow. I recall on beams r6 it took 3 hours of screen off time for me to even lose 1% battery!
The only thing I don't like about beans is the scrolling wallpaper..wish he'd give us a flash to remove it . Also sucks not being able to charge your phone while its off with the custom kernel.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
While I'm hoping for better battery life, I'm not expecting anything like that 3 hrs of screen at 1% battery would equate to 100 hrs of battery lift with the screen on. No, I'm just wanting to get less that 1% an hour drain at idle. It bugs me when the phone drops so much at night. I never did a good test on Beans 6, but there were a couple of night where in a 7-8 hour period it dropped double digit percentages....up to 15%. But I also found later I was battling an occasional wakelock issue. So I wanted to wipe and flash and try again...
So, when Beans 7 dropped, I did just that. Loaded it up last night and forced myself not to restore apps until I got some baseline information.
The initial clocks in the kernel seem good... As an aside, I almost want to install Beans 6 again and see if the overclock happens initially or if it had something to do with restoring SetCPU with data from my previous phone... This time I restored App Only and clocks look good. Even when charging, no extra profile needed like with kernel Test 12.2.
Idle battery life with just a couple extra apps installed was acceptable. Lost 6-7% over 8.5 hours. I was thinking stock was better, but now that I think back on it, the only night I was pure stock I didn't get to bed until 3am. So it lost, I think, 4% in about 5 hours...So given my fuzzy memory on the numbers, probably about the same at idle, maybe a little bit better with Imoseyon's Beta 0.1 Kernel...
So I've restored apps now and will fuss over battery life and other stuff for a few days more and then settle down and just use the thing.
Final note. Beans 7 looks awesome. The 15 toggle and notification looks nicely polished. Gone is the little nagging issue of having trouble grabbing the notification bar. So thumbs up all the way around so far...:good::good:
Im on beans b7, currently running stock settings...my device is running at 30*c, and my battery life is at 23hrs @ 49%. 1.5hrs of screen on time.