Database Info

sudden battery drain?

I've never had a problem with my captivate since I got it back in August. I could easily go two days on a single charge with no problem. Now all of a sudden my battery wont last even 8 hours. I know there are tons of battery threads but my problem just started like last week. I tried to isolate the problem by removing some apps that have been recently updated and still no luck. I even went through the phone looking for running apps and services but nothing out of the usual. I'm totally lost because like I said I have never had a problem with my phone...this is totally out of the blue. Is anyone else having problems?

is ur "use wireless networks checked"? coz last tym I forgot to unchek it and I feel the draining of my batt. it solved mines..,or maybe you are using a custom roms? cos mine is the stock, never tried any rom yet and my batt last for 24hrs still.
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm 100% stock. I literally haven't done anything to the phone at all since I got it...
The "use wireless networks" box is unchecked. I only use that when I have GPS on because for some reason it tends to work a little better.

Annoying boot loop issue

This one has got me baffled and annoyed. So ive updated to fp1 as ive noted in past posts. Ive tried pjb (fp1 version) and the stock ota update, both with tweaked 2.0. I have multiple batteries so wen 1 dies i swap it out for a fresh one. Everything will be working fine til i need to swap out batts, wen i do and try to reboot i get stuck in a damn bootloop and have to wipe data to get the phone to wrk. As u can imagine its pretty annoyin, even wit TB, to have set up my stupid shortcuts n widgets every othwr day.
Before anyone asks i went back to stock first, then the ota update, the fashed rom and kernel. Never had this problem on ep4. U might think tht i should just go back to ep4 then. Well, the problem there is that my email wont sync rite becuz of ozmail notifocation (yes i typed STOP, yes i contacted vzw, they said it should be fixed but it wasnt. Only thing that fixed it was goin to fp1)
So that is my problem. This is my 4th time starting from scratch, so hopefully this time will stick. We shall see.
If anyone has any advice i am all ears.
Sent from my SCH-I510 using XDA

Check out post #585 in the [FP1H][Rom][Cwm][Odin]Tweaked v2.0 thread under the Dev forum. Sounds like the same issue reported there.
EDIT: oops, that was you!

I can't for the life of me think of why that would happen. I also have an extra battery and have NEVER had that happen when swapping them. Has it been the same battery inserted when this happens or does it happen with both? Are they the exact same battery? After turning the phone off to switch do you wait about 30 seconds or so before pulling the battery? Happened with stock kernel and custom FP1 kernel? Stock rom and custom rom? Those are the first things that come to mind that MAY be a factor.

I actually have 3 batteries, 2 oem 1600 and 1 extended life 3600. It makes no sense, just went through the whole thing again, flashed to stock, started it up and all was well. flashed to fp1, started it up and was well. flashed pjb and tweaked 2.0 and im stuck on the samsung logo. this is really pissing me off!

cnoevl21 said:
I actually have 3 batteries, 2 oem 1600 and 1 extended life 3600. It makes no sense, just went through the whole thing again, flashed to stock, started it up and all was well. flashed to fp1, started it up and was well. flashed pjb and tweaked 2.0 and im stuck on the samsung logo. this is really pissing me off!
Click to expand...
Click to collapse
Did you test between flashing the kernel and rom on fp1? Might be interesting to see if you can isolate the issue further. I'm at a loss for what I could've done to cause the issue, but I can try to look into it if all signs point to tweaked.

How are you replacing the batteries? It sounds like you just pull it out with the system running. Power off the phone if you aren't, then replace the battery. Also, are all batteries stock Samsung batteries meant for the Charge?

imnuts said:
How are you replacing the batteries? It sounds like you just pull it out with the system running. Power off the phone if you aren't, then replace the battery. Also, are all batteries stock Samsung batteries meant for the Charge?
Click to expand...
Click to collapse
I doubt the 3600 is oem because samsung hasn't heard of batteries that big yet :S

I have tweaked running right now with stock fp1 so we'll see what happens on next batt swap.
I have 2 oem 1600 batts and a 3rd party extended batt. I always power down before pulling the batt. I marked the oem batt that i swapped in wen the prob happened today. Its possible i took it out to early, though i doubt it. But ill make sure to leave it in a few min after powerin down before pullin. Ill try flashing pjb over the weekend, gta work in a few hours n just needed to get things up n running.
Sent from my SCH-I510 using XDA

cnoevl21 said:
I have tweaked running right now with stock fp1 so we'll see what happens on next batt swap.
I have 2 oem 1600 batts and a 3rd party extended batt. I always power down before pulling the batt. I marked the oem batt that i swapped in wen the prob happened today. Its possible i took it out to early, though i doubt it. But ill make sure to leave it in a few min after powerin down before pullin. Ill try flashing pjb over the weekend, gta work in a few hours n just needed to get things up n running.
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
OK so if you swap batteries and get bootlooped, does the phone work again if you put in the original battery?

Nope. Once in the bootloop the only way Ive found to get out of it is to reflash.
Sent from my SCH-I510 using XDA

I just tried to reproduce you issue by shutting down and swapping in my spare 1600mAh battery. The phone booted up fine.
Not sure if it would have any impact, as I'm not sure exactly what it does, but have you tried wiping battery stats in CWM before booting with the new battery?

I am going to do the wipe battery stats this time around. I always do anyway on a fresh flash just to try n calibrate the battery.
DW I dont think it is Tweaked, its prob my phone or possibly i am screwin up the flash somehow (though i dont know what I could be doing wrong) If no one else has had this issue it cant be the rom.
Heres a few questions that answers could possibly explain the problem. Does it matter what is flashed first? ROM or kernel? And after you power down the phone there is that Team whatever animation, when that goes away is the phone powered down or does it take more time afterwards to be completely powered down? I always wait til the animation turns off, then pull the batt, but maybe the phone is fully off?

I always flash ROM first, then kernel. When shutting down, when the button back-lights go dark, it's off. That should be 5 seconds or so after the shutdown animation, not immediately after.

sbradley07 said:
I always flash ROM first, then kernel. When shutting down, when the button back-lights go dark, it's off. That should be 5 seconds or so after the shutdown animation, not immediately after.
Click to expand...
Click to collapse
Unless the ROM you are flashing includes a kernel (AFAIK only the ones based on leaks did), there should be no difference in order (just saying).

Sad to report that it happened again! Just went to switch out batteries, powered down phone, waited at least a minute before pullin battery, put in the new batt and stuck on samsung loop. Im pretty f'n over this crap! Have to be up for work in a few hours and I have to waste time that should be for sleep flashing back to stock, reinstalling fp1, etc. how do other ppl get replacement phones from verizon? anyone know a problem i could tell verizon that theyd give me a new phone? lol

cnoevl21 said:
Sad to report that it happened again! Just went to switch out batteries, powered down phone, waited at least a minute before pullin battery, put in the new batt and stuck on samsung loop. Im pretty f'n over this crap! Have to be up for work in a few hours and I have to waste time that should be for sleep flashing back to stock, reinstalling fp1, etc. how do other ppl get replacement phones from verizon? anyone know a problem i could tell verizon that theyd give me a new phone? lol
Click to expand...
Click to collapse
That sucks it happened again. Does it happen when you're completely stock? Luckily I've never had to get a replacement (knock on wood) but I would just tell them that when you switch batteries it factory resets and that should probably be a good enough reason. Good luck

THEbigSWEEN said:
That sucks it happened again. Does it happen when you're completely stock? Luckily I've never had to get a replacement (knock on wood) but I would just tell them that when you switch batteries it factory resets and that should probably be a good enough reason. Good luck
Click to expand...
Click to collapse
never happened until i updated to fp1. i havent tried just using stock fp1 cuz stock is just horrible on this phone. im all reloaded (once again) so we'll see, but if it happens again i will contact verizon about it and see if they will send a replacement.

BRICKED! Never thought it could happen to me

Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.

d_phekt said:
Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.
Click to expand...
Click to collapse
Take it off charge and pull the battery out. Let it sit for a while (1 hour at least) without the battery. Put your wife known working battery in and cross your fingers.

polobunny said:
Take it off charge and pull the battery out. Let it sit for a while (1 hour at least) without the battery. Put your wife known working battery in and cross your fingers.
Click to expand...
Click to collapse
Tried that and still no dice. So yeah... It's done.

d_phekt said:
Tried that and still no dice. So yeah... It's done.
Click to expand...
Click to collapse
This is paranormal stuff, you have no recollection of having messed around with it flash-wise?

dinuvali said:
This is paranormal stuff, you have no recollection of having messed around with it flash-wise?
Click to expand...
Click to collapse
LOL Yeah I'm a crackflasher, but I hadn't flashed anything for a few days. It was working just fine and POOF... done.

Try odin.
Sent from my Nexus S using xda app-developers app

d_phekt said:
LOL Yeah I'm a crackflasher, but I hadn't flashed anything for a few days. It was working just fine and POOF... done.
Click to expand...
Click to collapse
I don't imagine it shows as charging when plugged in? Otherwise I'd send it for repair or just buy a new phone. :/

polobunny said:
I don't imagine it shows as charging when plugged in? Otherwise I'd send it for repair or just buy a new phone. :/
Click to expand...
Click to collapse
No it doesn't show as charging at all. Won't find device in adb, no lights, no vibration when trying to power on, nothing. It does get warm when the battery is in it tho. And it is discharging somehow, because I tried my battery in my wifes phone and it showed 33 % when I know it had a full charge before it died. GNex is on its way.

i just have had same problem days ago , unfortunately i tried all , even Odin , just non-responsive
i also tried that unbrickable tool run under Ubuntu , still no good ...
i just send it to repair... Gosh

qtwrk said:
i just have had same problem days ago , unfortunately i tried all , even Odin , just non-responsive
i also tried that unbrickable tool run under Ubuntu , still no good ...
i just send it to repair... Gosh
Click to expand...
Click to collapse
Yep, I tried the unbrickable tool also... didn't find device there either. SUX!

nexus s GT-I9020T Bricked after JellyBean
d_phekt said:
Well I think I finally bricked my Nexus S. What's weird is that it's been working fine. Had JellyBro 20120817 installed for the past few days with no issues. Last night I plugged my phone in to charge and went to bed. Woke up this morning and clicked the power on button to see what time it is and it showed just fine. 20 minutes later I went to check the time again and NOTHING. Pulled battery, tried every button combo, everything. My wife has a Nexus S also, so I tried her battery with the same results. No lights, vibrations, nothing. Plugged it into my computer to see if I could get any response and still nada. Tried Fastboot and device is not found. UGH. If anyone can give me any advice on what to try feel free to chime in. I've been around long enuff to realize that I'm pretty sure it's toast. Either way... it's been a nice run.
Click to expand...
Click to collapse
Same Problem here. It was working fine on jelly bean and rooted with clock work recovery. I removed the battery out to change the sim and now it wont power on, fastboot doesn't work and the USB JIG also doesn't work, doesn't show the charging animated when plugged in.
i tried AdamOutlers Resurector tool, it didnt detect the phone, so i made the hardware mod and now it detect the phone, but still dead after the tool loads the files. but when i choose GALAXY S from the drop down menu, the tool and the phone, both shows download mode, heimdall detect the phone but doesnt work as it is not a GALAXY S.

At least now you have a reason to upgrade. But that sure sucks, if you still want to revive it you could give this a shot... http://www.youtube.com/watch?v=Ecp8jKmm48k

Three people with Nexus S's with Jelly Been roms just spontaneously get bricked phones? Just flashed mine to CM10 Nightly yesterday...
Hmmmm

I'm not sure if I would call mine a true bricking since most bricks happen directly from a rom flash. Mine was actually working fine for a couple of days after my last flash and then suddenly stopped working. It was an almost 2 year old phone and heavily abused internally with almost daily rom/kernel flashes and overclocking. I think maybe it just got tired LOL. Oh well...we have 2 other Nexus S's in our house, so now we have a decent parts phone since externally the phone is flawless.

Try cleaning your the phone's usb slot with a toothbrush and medical alcohol. also after removing your battery, try pressing the power button for 10 Secs(without battery) this cleans any extra charges in your phone. Gd luck!

Sounds more like hardware failure than bricking.
Sent from my Crespo using xda premium

i read something that is problme of bootloader that messes with hummingbird CPU or something , i don't know
i had flashed the latest bootloader and 4.1 once it came out , but then i back to 4.0.4 and decided wait for AOKP JB.
and , my phone was also unable to power up after i pull out and change a new battery ! , first of all i was thinking battery's unstable output current damaged hardware or something , but now i am more convinced it should be the problem of bootloader as i read before

Sensation ''randomly'' shuts off

Hi guys and girls, i've been having some trouble with my Sensation, i've had it for 1 year and 2 months (+/-). I've rooted it probably after 2 months of having it. It was working normally until this last month when It started shutting off randomly, sometimes 7/8 times in 15min. It does not reboot it just shuts off.. I then turn it on and it's fine. I was using ARHD ICS 4.0 ROM for probably 3 months and it was a great rom never had any problem, until now it started shutting off.. I thought it was some kind of problem with the rom and yesterday I've flashed Jellybam (best rom i've had so far) and I thought the problem would end... Well it didn't shut off for a whole day, until 30min ago..I then tried to play Dead Trigger and it shut off 3 times during the game.. I have no idea what could it be... I already reset batery stats but its still happening.. I wiped everything before flashing JellyBam. Any help would be great.

probably your battery is dying
check with another battery
or see also if it connects properly

Either what rzr said.. or u can try putting a piece of cardboard paper between the
Chassis and the battery. Search in the forum there is a thread about it. And it has been mentioned in countless threads
Sent from my HTC Sensation

Thanks for the help guys, truth is, after having posted this it never happened again...

[Q] Hard-brick? :(

Hi All,
I think I might have hard bricked my phone but I'm not sure. I had Synergy r56 and IMOSEYON's kernel for several months and stayed on that even after the JB releases came out. This past weekend I decided to upgrade to the latest release, r147. I wiped data/cache, flashed r147, and it booted up fine. The only problem was that it would appear to reboot about twice an hour (or more). I read that it could be the kernel that was included (Ziggy). So I decided to try KT747 but before that I flashed the newest radio (VRKL3), then flashed KT747 but that didn't help with the reboots. This was late last night and I had to wake up early for work so I decided to work on this in the morning. Woke up to a dead phone -- it wont charge!
With the power plugged in, I pull out the battery and put it back in and the phone vibrates and a red LED comes on. I see the display turn on and I see the battery image (with zero charge) that you usually see when you charge the phone while it's switched off. This image last less than a second and then it's gone. I tried going into download mode but that doesn't work either. I'm wondering if I get a fully charged battery, would that help me boot up. Any ideas??

Yes get a new battery from someone that's charged. If your seeing life with the screen coming on then you are not hard bricked. I would recommend having everything ready to Odin back to stock when you get the battery and go ahead and put it to stock.
Sent from my VS920 4G using xda app-developers app

Guess that's good news. Now to find someone who has an S3...if I can't, can it take it in to a Verizon store? Or is that a bad idea? Thanks for your response!

Not on this phone but I know people would take the droid x into verizon and they would let them use one of their batteries to see if it would boot. Wouldn't hurt trying. And you can get batteries pretty cheap on amazon, external chargers too. Good luck.

Just placed an order on Amazon for a battery/charger set. Will update this thread tomorrow! Thanks again guys!

This has been happening to me since I got my s3. If I let my battery die it's a pita to charge it back up as I have to keep pulling thwarted battery and or get lucky. The battery charging icon would show up and disappear and the red led light would show up, That doesn't mean its charging. The battery charging icon has to stay put to know it's charging. This hasn't really bothered me enough to get a replacement. So my 2 cents
Sent from my SGH-i535 using xda premium

I'm curious have you just left out plugged in for a couple hours? Also what about recovery mode?
Sent from my VS920 4G using xda app-developers app

The no charge after battery dead is a bug in CWM.

Both CWM and TWRP? I just installed TWRP and haven't had this issue before with CWM.
prdog1 said:
The no charge after battery dead is a bug in CWM.
Click to expand...
Click to collapse

Update:
Got my extra batteries less than 10 minutes back. Stuck one of the batteries in the phone and it booted!!!! I'm stoked! lol...anyway, if someone could guide me through what I'd need to do to get back to the latest Synergy JB rom (r147 I believe it is) after I go back to stock because I'm pretty sure I screwed something up with everything I did to get to where I am.
What I've done so far:
Unlocked bootlader
Flashed the latest radio (RLK3 I think it is)
Flashed the KT747 kernel over the one that came in Synergy r147
What do I need to do to get back to Synergy r157? Do you think it's best to go back to stock and re-do everything or is there an easier way? I'm a little paranoid cos I've been out of this game for a while and am not sure what effects my flashing kernels/radios will have on anything I try to undo. Also, if I do flash the Synergy ICS nandroid (r56) that I took prior to flashing r147, will that revert the kernel to Ziggy's?
Thanks in advance guys!

Nevermind. On Synergy r155 now and am having several unrelated issues. Thanks for the assistance.