Database Develop

[Q] Captivate Reboot and Battery Loop problem

Hello everyone, long time reader, first time poster (with a real query).
Actually last Friday my cappy started to show 100% of the battery after being for some time in use, so I reboot it trying to solve the issue.
After the boot, the cell shows the Initially Battery screen for 2 seconds with the battery without charge then turns off. Tried several times and also using a second battery with full charge and same problem persisted.
10 minutes later without having a battery inside the phone, it boots but when I rebooted the problem arises again.
This weekend I installed Illuminance 3.01, after that I have installed CM9 (very nice ROM) and the battery problem still is happening. I am able to use the phone but I don´t know for how much more.
Any suggestion?
Thanks,
Martin

have you tried to wipe battery stats in recovery ?

Felixcm88 said:
have you tried to wipe battery stats in recovery ?
Click to expand...
Click to collapse
Yesterday night I did a wipe battery stats and the problem still is there.
It starts with the loop and the only way I can start the phone is plugging it then it shows the actual charge of the battery and after that I can boot.
It must be something "deeper" than the rom...
Anybody?
Thanks

Somebody can help?

I am having the exact same issue, stock froyo 2.2 rooted 5 months ago. I'm trying everything before updating to 2.3, I'll let you know if I find a fix, please do the same.
Searching google is not working this time, it's been 3 days...
Things I've tried:
1- From recovery, boot phone. Problem persists after phone is turned off.
2- Boot from revovery, then reset to factory settings, after rese, same issue.
3- Wipe cache from recovery. Problem still there.
4- Wipe cache+user data from recovery. Same thing.
5- repeating 1-4 without SD card or SIM card.
- Wipe battery data... nothing...
- Unrooting, same issue, rooted again.
- Run root fixes with Titanium backup. Same...
- Removing battery for hours, while charging it externally, replace battery, same issue.
All to no success. Things yet to try:
- Update to 2.3 using kies
- Update to beta 2.3.5 using odin
- Update to custom rom, maybe try 3 or 4 different...
- Cry, then save and buy a new phone, use cappy as shiny paperweight...
Please let me know if you could fix it...

I'm not sure what you mean when you say "initial battery screen."
But if I am to understand the rest, your problem is:
initial boot - runs fine, but battery stays at 100% no matter how long it runs.
reboot - phone now says the battery is suddenly dead, and shuts-off.
further reboots - same
You can't get the phone to fully boot till the battery is left out for a while and the phone is fully de-energized.
You have tried a different battery and it behaves the same.
- - - - - -
Have you tried using a known "good" battery? (a new one or one from someone who's phone works fine)
Also, what happens if you plug in the USB while the phone is off? (after the inital boot, when it is stuck in the "dead battery loop.")

Still dead after installing update and 2 custom roms...
Yes I tried a good battery from another cappy, if I plug in the cable it does the same, instead of normally booting, it displays an empty battery and goes off.
I am able to make it work but only entering the restore mode, so I cannot for example be on a trip and reset the phone for whatever reason...

have you tried using a different kernel?
Sent from my SGH-I897 using XDA App

sorry, but how can I try a different kernel? do i need to change the rom?

Nah, kernels can be flashed independent of ROMs just look through development for topics that have "[Kernel]" as the fist word in their title.
If you have gone and loaded two custom ROMs and it still persist then it's not a kernel issue. As the kernel is always changed along with the ROM.
That said, I can only think of two other possibilities: one being dirt or such making a short in the contacts of the usb (does it sometimes think it is plugged in when it's not), two something in the circuitry for the battery randomly went bad.
Try cleaning the socket for the usb. If that does not fix then assume the worst
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.

Ok, here's the thing, I left it without the battery for 24 hrs, then it was worst. The phone would not turn on at all. However, after that I tried putting the battery in while holding the power button, it worked!!! it's better than having to connect to the computer, but still, I don't want to have to do this every time... flashing roms now to try again.
We're getting somewhere now...

DaNaRkI could be right about it being a circuitry problem (which would suck). With that in mind, have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
When you flashed the roms, are you doing complete wipes? (wiping the cache/dalvik/data)? It might be worth it to go one step beyond that and format all the partitions and then reflash. I think if you do that, you could basically rule out any software problems.
Be sure to back up your data!
P.S. When you do all this wiping and formating and reflashing, boot up and check to see if the problem is still there before you put your data back on jic there is some weird corruption in your data which is causing this.

ok.
have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
yes I have, they're perfect
When you flashed the roms, are you doing complete wipes?
many times, actually
I have yet to format all partitions, how can I do that?
Thanks!!
and yes, all my data is well backed up in my PC and cloud...
---------- Post added at 12:31 AM ---------- Previous post was at 12:09 AM ----------
this is rather odd, just tried to factory reset again, then restarted using the battery method, then... turned it off, and now it boots normally!!!
Thanks for your help !!!

I have the same problem. What exactly did you do? I use a custom rom, and I flashed stock gingerbread 2.3.4.

Formatting the partitions won't do anything, since the phone won't even turn on sometimes. So when exactly did this problem start happening? Was it after a particular flash or other incident?

Bootloop / Lost Recovery

Apologies for opening a new thread for this. I am unable to reply on the dev thread as I have less than 10 posts. So in reference to the following post, I'd like to contribute some experience I had in the last two weeks.
http://forum.xda-developers.com/showthread.php?t=1627689
Across the space of two weeks, I have had a chance to note this symptom on three devices.
Device 1 SGS i9000
Rooted phone and have been on CM9 for as long as I can remember. Wake up one morning to find phone with BLN on, but no ability to wake the phone (power button, home button, volume buttons, nothing works). Popped the battery out, and the bootloop / no recovery went on forever. Had to Odin flash back to Stock 2.3.6 to start again. Since then, any CM9 (nightlies or RC2) attempted always end up in the bootloop, i.e. stock > flash rom, first boot = bootloop. I figured then if I had to go back to 2.3.6, I'd rather go to JB. First JB tried was HellyBean, and the same thing happened. It was only trying pawitp's current alpha CM10 that it worked. Days later reverted back to ICS (Paranoid Android v1.6) due to lags and bugginess.
Important to note, the CWM kernel I have gone through are 6.0.0.3, 6.0.0.8, 6.0.1.0. And Paranoid Android put me back to 5.5.0.4.
Device 2 SGSi9000
Rooted phone and have been on CM9 for as long as I can remember. Phone cut off and rebooted in the middle of a phone call and ended up in bootloop with no recovery. Exactly the same symptom attempting to get the phone back into any of the CM9 roms (nightlies or RC2). Ended putting the phone on Paranoid Android as well.
Device 3 HTC Sensation
Had a lot of trouble trying to flash CM9 on this using CWM. Random bootloop with no recoveries. CWM at that time was 6.0.0.8, which I had lots of trouble flashing Gapps on. More on this device posted here: http://forum.xda-developers.com/showthread.php?t=1786703
And finally, one other observations across all these devices. Somehow with CWM v6.x.x.x I had rather poor battery life. For instance, on CM9 Nightly 07/23, say I started with 100% charge in the morning at 8am, by 12pm, I would be looking at 80% left. Once a week, I will let the phone shut itself down on low power, and charge without switching the phone on. On any other evenings, I would plug the phone and leave it charging overnight, e.g. at 10pm with only 30% left. I have constantly noticed that within a few minutes, it jumps back to 40%, which is rather odd. A 10% charging achieved within minutes is rather unusual.
I have also noted that, when the SGS i9000s ended in the bootloop / no recovery situation, the phone can never be charged. Plugging the phone for charging will the a blank battery icon lit up, with the swirly thing on top of the icon appeared frozen and it stays that way.
Being on lower version of CWM, in this instance, v5.5.0.4., I can observe the units (observed being the keyword here) charges "normally", i.e. no funny 10% charge achieve within minutes. Also, battery life are much better as well, i.e. only 10% drain between 8am (100%) to 12pm (90%).
So, not being a developer but someone that likes to tinker and observed:
- Is it possible that newer version of CWM potentially have some impact to battery life?
- Is it possible that how CM9 is being flashed onto a phone has potential issue? I find it a bit disturbing on an initial flash from stock to CM9, I had to pop the battery out after the flash initially loads a new CWM onto the phone. Then start the flash again with the newly loaded CWM.
I am hoping all these I have experienced in a short amount of time can be helpful to potentially looking into where issue might be. Most people have one phone and tested across different kernels and ROMs. I had the luxury of testing across three devices on a narrower choices of kernels and ROMs.

For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium

AlwaysDroid said:
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yup, on every occasion I mentioned above, wipe (system/data/cache) are part of the ritual. Just didn't mention them.
I just think the battery-pulling feels rather odd. Can understand why it's needed, but just feel odd. Wondered if it'd be better to keep kernel and ROM separate, e.g. flash new kernel via Odin, then simply do ROM. This might be a 'cleaner' method perhaps? It feels almost like flashing kernel as part of the process is like modifying Windows files whilst still in Windows, then do a reboot.
For now I have fear against v6.x.x.x kernels. But will likely go back to it once CM10 is stable. We'll see.

I installed Eryigit's Android 2.3.6 ROM onto my SGP 5 and have this battery charging boot loop. Are there any solutions for this yet?

Busted note?

So,
My partners note is running CleaNote v4, with NoteCore v13 standard. Today, after shutting off Automatically through empty battery, she plugged the phone in for half hour and tried turning it back on. ever since.. its simply not starting, the boot screen is active but not proceeding beyond it for anything up to an hour.
and therefore..
ive tried the usual, let it charge full, nothing. wiped dalvic, cache and battery stats.. nadda.
when i choose to wipe dalvic now however, i get the message .. E: unknown volume for path [/sd-ext]
im hoping its not as serious as it looks, ive searched it and there doesnt seem to be a solid solution anywhere, should i just factory reset?
ive reflashed CleaNote v4 via CWM.. been booting again.. for a long, long time.
afraid im all out of options, factory reset? flash stock rom and return to sammy?

You can do factory reset as you are on safe Kernel OR you can try flashing some other custom rom using cwmr, but best way is to flash stock GB rom using odin.

I agree with the post above.. but better try to go first to CWM, wipe cache partition, wipe data, wipe dalvik cache, reboot recovery and reboot system... if the phone's still stuck on 'Samsung's' bootlogo... then go to the last option of downgrading to Sammy's Stock GB and work your way up again to flash CleanNote after.

Oi
Cheers fellas,
Sorted it, just a factory reset fixed it.. still get the same error message in CWM when wiping dalvic.. BUT..
restored the wifeys ice age village save from nandroid backup before i wiped.. my nuts are safe, so are her ingame nuts!
i flash my note every few days, and face the odd hiccup, hers has never had a single hiccup on the trusty CleaNote/NoteCore combination..wonder what caused it? thanks anyway!

I read somewhere before that you shouldn't run your battery juice out completely... Always leave a little juice out and charge it back again to full. Never leave it to run dry... Li-Ions are not designed to be completely drain out.. with a small juice left, you need to recharge it back again. It's not good for the battery itself to leave it completely drained.

Battery drain on my Note after flashing XXLS7 rom

Hi,
I recently flashed my XXLS7 ROM and while doing so, I was asked to wipe battery stats too, after then I see that my battery % is getting reduced drastically and the worst is that whenever I am in normal mode it shows me 75% but after getting into recovery mode it shows 55% or so. Now I am completely confused whether 100% is actually 100% or not. Any ideas on how to get this problem rectified?
Thanks in advance.

may be you need to do a clean install of the rom again.
use format/system and format /data this time

nokiamodeln91 said:
may be you need to do a clean install of the rom again.
use format/system and format /data this time
Click to expand...
Click to collapse
Thanks, I have tried that option too, but still no help..........

Be patient
Mine was discharging like crazy when media scanner was doing its thing -- just keep a charger handy and stick it on when it gets low. Eventually it should sort itself out.

boot into recovery and wipe battery stats again.. then charge the phone to 100 % and test again.

I had this problem in almost every xxls7 ROM... I tried everything, literally EVERTHING.... i made 3 wipes, format preload format system etc etc... Result is DEVICE IDLE eats battery... I CAN NOT figured out which causes this... But finaly, SweetROM solve the problem... I do not know how but it solved... I tried RR3, Alliance and Stock xxls7... All of them causes battery drain for me but i do not know if it is a problem of all... Anyway, just in case you can try Sweet ROM... At least it does not cause drain when you do not use it...

I have this problem too..
Nokia 3210 with PA Utacka

after restarting the phone go to settings>application>all>media storage and stop it.
on every bootup, media storage process consumes %5-10 battery to scan media files.
you can disable it but the gallery wont work.
you can use Quickpic instead.

[Q] [XPERIA T] Incorrect % battery indicator [SOLVED]

Hi,
I have the Xperia T, my battery indicator % remain 100% after use, when i power off my device and turn on again the battery have a big fall (to 70-80% deppend of hours of use) and over time it turns to 100% without charge, its crazy. It happens in T_Hybrid_V17 but not happens from beggining of install the ROM... one day suddenly occurs...
My bootloader is locked, the phone is rooted and ROM is stock based with a CWM for locked bootloader.
Ok, I read about the problem, i have not the option of wipe battery stats in my CWM, i read about "battery calibration" and installed and followed instructions of apk "battery calibration", dont works for me... I manually do the same process... i deleted the batterystats.bin at 100% charge... let the device power off on discharge... charge again to 100% and let it discharge... it dont works for me...
Well... i think ok... there are a new ROM with another Kernel included... new CWM included in XDA I try to change from JB 4.1.2 to JB 4.3 Ultimate Pure XT 4.0... and later OTA 4.1 and 4.2 well, the problem changes... is similar but not same... I do it "the calibration" and try the same as past... the new problem is... battery 100% and after a lot of use maybe it drops in real time to... maybe 97% ok... power off and on... 76% I use the device the bateery lvl drops to 73% after time and still there, it dont go up to 100% this is the difference, but the battery dont drop in real time correctly I attach an image of battery graphic. What can i do? i read similar problems on other devices, like SGSII, that is solved with "wipe battery stats" in CWM but my new CWM included in Pure XT (touch Philz 6.X) still not having this option in advanced...
I have Xposed installed now, but not when problem begin, i dont know what more to do. The battery duration appears to be correct but the % is not real.
I search in XDA forums about it, i see "solutions" on other devices, I read and read, but dont work for me.
Sorry for my english, i hope that you can understand this.
EDIT: SOLVED
-------------------
The problem was a hardware issue. I leave it in a technichal assistance , and they repaired it in 2 weeks, a main board problem, new mainboard and new IMEI... solved.

Have you tried to wipe cache and dalvik from recovery?

nlooooo said:
Have you tried to wipe cache and dalvik from recovery?
Click to expand...
Click to collapse
Yep. Everytime I installed/uptated ROM.
And when install a new ROM also made a "factory reset" from CWM. :/

No, I thought to reboot to recovery now and clean just cache and dalvik cache.

nlooooo said:
No, I thought to reboot to recovery now and clean just cache and dalvik cache.
Click to expand...
Click to collapse
I cleared dalvik and cache 3h ago, battery indicator not move. It is at 30% since then same problem

No idea? im gona crazy wit this issue. Im searching in web but nothing helps :-/