Updated my rooted samsung galaxy s via odin, first time using odin, and now battery percentage doesn't go to 100. Even when left overnight. Anyone else with similar issues?i was on stock firmware before switching with eugenes daily update once in a while. Did a data and system wipe to start fresh...
Sent from my SGH-T959 using XDA App
have you tried doing the "reset battery statistics" via Clockwork Recovery?
BTW, it's J I 5 not J 1 5 and this is not the Q&A forum.
Anyway, you might try resetting your battery stats through the clockworkmod recovery menu. Then reboot and see who it goes.
You may also want to consider flashing one of the many supported battery meter mods.
oh, sorry bout jI5 and the thread, will try clockwork battery reset. =)
Related
I rooted my Hero a long time ago and installed Cyanogen's Recovery Image 1.4 on at the same time.
Over the last couple of days I've finally got hacked off waiting for an official 2.1 ROM to be released and decided to have a play with some of the Custom ROMs. The problem I've run into is that all of the guides talk about erasing data from different directories and partitions but none of them discuss how to do it !?
All I really need to know is if this is something that must be done via adb and what/where the directories are that need to cleared out.
I have searched and trawled but I get the feeling that this step is something that is done antomagically by the newer Recovery Images. If that's the case, would you suggest I upgrade mine ? And to what ?
Thanks for the help
(Really looking forward to playing with VillainROM 6 )
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
[Recovery ROM] [07-Mar-2010] RA-hero-v1.6.2
Thanks ddotpatel, I guessed it might be due to the age of the Recovery Image I've got
I'll upgrade this evening
ddotpatel said:
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
Click to expand...
Click to collapse
Any idea exactly what stats are erased by the battery stats & rotation settings options?
No idea pal,... but if Im flashing a new ROM without having 100% battery I leave the battery settings wipe.
I assumed that wiping battery stuff makes your phone think your battery is full after the wipe,...
So say its actually at 50%, then you wipe stats and flash a new ROM, then your phone thinks that battery is at 100% so will only charge upto that level.
The only thing I'm basing this on is I have read people say that when flashing a ROM when battery is not 100% they seem to lose battery capacity. But who knows, it could be psychological?
AFAIK battery stats deletes stuff like which programs have been using your battery as well as the currently stored battery figure. I assume that on next boot it checks the battery capacity afresh and goes with that figure.
Rotate one - i assume is to do with application rotation and the g-sensor.
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
Lithium Ion batteries don't have the "memory" problem of older batteries where they forget any charge that is left in the battery when it is put on charge and assume when its removed from charge that it is 100%. They should always stay the same capacity for their entire life duration. Again this is all AFAIK
Aahaaa,...
I always take what you say as gospel BTDAG.
Might have a read up on batteries later,... If I remember,... If I can be arsed!
Do you ever flash ROMs without having 100%?... No problems?
btdag said:
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
[snip]
Again this is all AFAIK
Click to expand...
Click to collapse
I took the same cautious view as ddotpatel. I figured if it's important enough to store in it's own private flash, it's probably holding data related in some way to the physical state of the phone, or an estimate thereof. I'm wary to touch them without ever having seen any solid info on what's there.
I've noticed one or two new ROM threads where the user is told to wipe these stats. I hope no one gets burned as a result.
BTW Also all afaik. It's just that in my case that isn't very far.
I have a Droid Pro running 2.2.1 version rooted with superoneclick (had to turn anti virus off as it was picking up a false positive)
running rom manager
titanium backup
droid2 bootstrapper working great
installed 808 and gapps on sd
wiped all data and cache even dalvik
installed 808 and gapps
but when trying to reboot system got stuck on moto m screen and had to get back into recovery via comp and restore and reboot system without rom
i need any suggestions
just a note i let phone try to reboot for about 30 minutes
idk if you did or not but in the things you posted that you did you did not say you did a factory reset before installing. Did you do a factory reset after installing CM7
CrackMonkey91 said:
idk if you did or not but in the things you posted that you did you did not say you did a factory reset before installing. Did you do a factory reset after installing CM7
Click to expand...
Click to collapse
i did a backup and wiped everything
i did no reset until i got it out of bootloop and back in recovery to reboot to stock with root
I don't have an answer but I would like to say that if you manage to fix the problem, do keep in mind there is a 902 version for our phone
Sent from my DROID Pro using XDA App
dutchbastard said:
I don't have an answer but I would like to say that if you manage to fix the problem, do keep in mind there is a 902 version for our phone
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
i have fixed it and successfully installed gingerbread and rooted
am curious about new cm7 for this phone as a custom rom would be nice because battery life is terrible
Well battery life already greatly improved with GB on both my own and my sons phone.
I have cm7 on mine and now its even better.
I had to folllow a tip to delete batterystats.bin after a full charge but itt lasts well over a day now.
Of course using the phone heavily will deminish that life but with moderate use you should be good for your day to day stuff.
Sent from my DROID Pro using XDA App
dutchbastard said:
Well battery life already greatly improved with GB on both my own and my sons phone.
I have cm7 on mine and now its even better.
I had to folllow a tip to delete batterystats.bin after a full charge but itt lasts well over a day now.
Of course using the phone heavily will deminish that life but with moderate use you should be good for your day to day stuff.
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
please elaborate on batterystats.bin action
where can i find cm7 that will work and instructions link
The link for the 902 download is http://www.mediafire.com/?cwignib2ksgwuev
Posted by jackpotclavin on droidforums: http://www.droidforums.net/forum/droid-pro-hacks/154369-gonna-build-cyanogenmod-7-pro-59.html
There is a nice blog by him with instructions here: http://clavinsup.blogspot.com/
Though I don't see the 902 download there so the instructions are a bit outdated, but still apply.
Just use the 902.zip from that mediafire link (4th post on second link) and the instructions from that blog.
When it comes to batterystats.bin I was told to google it, which I did.
I came across various instructions about letting the battery run dry, then charge til full, delete batterystats.bin though filemanager, then charge for 2 more hours....other instructions said something different.
Basically I got: Charge til full, delete file, run dry until phone turns off, then use normally.
CM7 gives us the option to delete the batterystats in there. (recovery/advanced/wipe battery stats)
So that's it.
Now I don't know if I did it wrong, all I know is it gave me longer life.
ho hum
and boo
Ok I'm on tasks aokp Rom and it works great. I have tried a couple of times to flash a new rom. I make sure that the battery is charged to 100% and flash the rom (tried with several different roms). It will work for a while, then it will crash to 0% and will boot loop because the battery reports 0%. I plug it in and it will boot up and start charging. At some point it will jump right back up to 100%.
I've tried battery calibration and no dice. The only thing that works is restoring my nandroid of tasks Rom.
My next step is doing a full wipe or going back to stock. I would like to avoid this if possible
Any help would be appreciated.
Sent from my Nexus 10 using Tapatalk 2
That is a very weird problem to have. Supposedly Android generates new battery stats at each boot, so not sure what is going wrong with your device.
Which ROMs have you tried flashing? If you are just trying to flash between different builds of AOKP then perhaps you should try a CM based ROM. Or if you are flashing from AOKP to a CM ROM, then try other AOKP based things only and see if the problem is still there or not.
EniGmA1987 said:
That is a very weird problem to have. Supposedly Android generates new battery stats at each boot, so not sure what is going wrong with your device.
Which ROMs have you tried flashing? If you are just trying to flash between different builds of AOKP then perhaps you should try a CM based ROM. Or if you are flashing from AOKP to a CM ROM, then try other AOKP based things only and see if the problem is still there or not.
Click to expand...
Click to collapse
It's happened with Mr Robinsons and rasbean and rassabre.
I always do a full wipe (dalvik, cache, factory reset)
Sent from my SGH-I747 using Tapatalk 2
There is something called battery calibration, try that. PM me for more info
shaker2k said:
Ok I'm on tasks aokp Rom and it works great. I have tried a couple of times to flash a new rom. I make sure that the battery is charged to 100% and flash the rom (tried with several different roms). It will work for a while, then it will crash to 0% and will boot loop because the battery reports 0%. I plug it in and it will boot up and start charging. At some point it will jump right back up to 100%.
I've tried battery calibration and no dice. The only thing that works is restoring my nandroid of tasks Rom.
My next step is doing a full wipe or going back to stock. I would like to avoid this if possible
Any help would be appreciated.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
what about the kernel did you try resetting or uninstalling the kernel tweaker apps before you installed a new ROM.
I wiped everything and flashed back to stock using the nexus toolkit.
Everything is working great now.
Sent from my SGH-I747 using Tapatalk 2
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
I also think there's a problem with your battery, it might need to be replaced.
ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped
So I flashed mako-jb-kernel-028u-JWR on my nexus 4 and when I rebooted the notification light was flashing red. I booted back into TWRP and flashed mako-jb-kernel-027m-JWR to try and fix it. After I rebooted it was stuck on the boot animation with the flashing light. Whenever I started up TWRP the light would start flashing and the phone would turn off before I could reflash carbon rom. The light wouldn't flash when I was in fastboot . Now it won't even turn on, even if I plug it into power. I looked around and couldn't find anyone else with this problem. I'm assuming the battery ran out of power and I need to let it charge before I can do anything. Though last time I booted into TWRP the battery was above 90%. If someone could suggest something to do it would be great.
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
simms22 said:
if nothing else works http://forum.xda-developers.com/showthread.php?t=2250454
Click to expand...
Click to collapse
I'm hoping I won't need to do that since I don't have a T5 screwdriver and I don't trust myself with manually charging a battery with a power supply.
I should also mention that I used this https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en about an hour before flashing the new kernel.
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
RASTAVIPER said:
Try first to flash stock kernel.
If this doesn't work then reflash whole factory image.
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
The problem is that it won't even turn on. I think it ran out of battery and its refusing to charge.
Alright so I did some searching and found this post http://forum.xda-developers.com/showpost.php?p=43291951&postcount=27 I did that and my phone can actually boot up now. Also I should mention that you need to hold the buttons for EXACTLY 60 seconds or it won't work. I'll let it charge and attempt to reflash Carbon Rom after.
TWRP kept closing on me before I could reflash Carbon, so I restored to the stock rom and kernel using WugFresh's toolkit. I couldn't boot into the rom until I went into fastboot, went into stock recovery, and restarted my phone. Now I can boot up perfectly fine! Also I flashed the latest faux kernel again just to make sure it was the problem, and after flashing mako-jb-kernel-028u-JWR I got the red led again, So I'm advising everyone to stay away from that build.