How is that even possible?
I have attached 2 screnshoot of a Galaxy Nexus battery drain.
My phone is 100% stock, I just restored the nexus official image. The battery should be new, I already sent the phone to the manufacter last month and I think they changed the battery.
I didn't even setup a google account, no app installed, wifi off and there is good signal.
There are no wakelocks. Screen was off all the time. The battery just go down.
(Some translation. Segnale rete mobile = mobile network signal, Attivo = active, Schermo Acceso = Screen on)
What should I do? Call samsung again and stay another month without my phone? Is there any other solution?
Well, for starters you could let it charge for another cycle or two to be sure about.Also I see the Network reception is not so good.That may be responsible for the drain, though I highly doubt it !
dhruv52004 said:
Well, for starters you could let it charge for another cycle or two to be sure about.Also I see the Network reception is not so good.That may be responsible for the drain, though I highly doubt it !
Click to expand...
Click to collapse
Yes, I'm trying to do some complete charge/discharge.
I have similar result in Airplane mode, network reception is not the problem.
Thanks for the answer. :good:
Anyone else with some advices?
No one?
I don't want to spend another month without my phone because of RMA :crying:
supermario3 said:
No one?
I don't want to spend another month without my phone because of RMA :crying:
Click to expand...
Click to collapse
I have the *exact* problem (or at least, similar).
I have RMA'ed my phone 2 times, teling me they had done a "mechanical repair" (in Italian, as per repair center label, "riparazione meccanica").
Don't ask me about the meaning of this. It could be everything, but one thing is certain: serial number of the phone is the same, so they did not change the motherboard at all.
Back to topic, I'm experiencing serious issues:
1) huge battery drain in airplane mode, even after complete stock and several ROMs (the service center restored 4.0.4 on it, funny)
How did I test: the day I received back my phone, I have simply fully charged it, switched to airplane mode overnight and I have lost more than 30% battery with NOTHING at all installed, I even left the wrong date/time !!
2) before RMA'ing it, it did not matter if I used 3G / WiFi or nothing at all: I always got a similar battery discharge curve.
BUT today I noticed something odd:
while testing for the (1) issue above, I noticed that the "Awake" (aka "Attivo") bar under the battery graph was pretty full blue colored, which is NOT normal actually. How can it be after a full wipe (or so, as per after sale service) ????
Let's try to troubleshoot this problem guys, because I'm really fed up
...and I don't want to sell this Nexus, I simply love it hehe
TODO:
1) Wipe and test again -> charging the phone right now
2) analyze dmseg (maybe there is an hardware issue that keeps interrupting the CPU) -> after a quick look it seems that actually my interrupt idea could be true ( "Resume caused by IRQ 39, TWL6030-PIH". This is the power management unit) but I have to see during the airplane mode test, not while charging (that might be correct)
3) measure the current and compare results against a nice study of another guy (that reported power consumption on different scenarios)
4) ??
LorenzNexus said:
I have the *exact* problem (or at least, similar).
teling me they had done a "mechanical repair" (in Italian, as per repair center label, "riparazione meccanica").
Click to expand...
Click to collapse
The same. They changed the battery in my case. I did a mark with a marker pen on the battery before sending it and the mark is not there after RMA, so they changed it. Phone serial is the same.
They also put 4.04 on my nexus, what a shame!
I did not experienced the "active" thing on the battery statistics. I had several wakelock from "RILJ" but after a full restore the disappeared.
I restored (again) the phone with nexus image, and even locked the bootloader, removed the sim card and disabled wifi, gps and everything. It always discharge by itself in a too short period of time.
Is there something I can tell to RMA to make them change my phone? I don't think it's a software problem.
supermario3 said:
The same. They changed the battery in my case. I did a mark with a marker pen on the battery before sending it and the mark is not there after RMA, so they changed it. Phone serial is the same.
They also put 4.04 on my nexus, what a shame!
I did not experienced the "active" thing on the battery statistics. I had several wakelock from "RILJ" but after a full restore the disappeared.
I restored (again) the phone with nexus image, and even locked the bootloader, removed the sim card and disabled wifi, gps and everything. It always discharge by itself in a too short period of time.
Is there something I can tell to RMA to make them change my phone? I don't think it's a software problem.
Click to expand...
Click to collapse
I agree, this must be an hardware problem.
To say, I have tried a long list of ROMs and kernels, as well as updating radio and all other sort of stuff.
Now the awake "problem" has gone, so today I'm gonna retry the (1)st experiment.
Let's see...
In any case tomorrow I'm going to go to the shop and ask them if they could be so gentle lending me a fresh battery to test out.
Some clues here?
http://androidforums.com/samsung-ga...drain-since-i-started-using-wifi-hotspot.html
I don't know if it might be related or not, did you ever use tethering?
Pernsonally speaking, yes I did.
Today I try to wipe radio and flash another one...
LorenzNexus said:
Some clues here?
http://androidforums.com/samsung-ga...drain-since-i-started-using-wifi-hotspot.html
I don't know if it might be related or not, did you ever use tethering?
Pernsonally speaking, yes I did.
Today I try to wipe radio and flash another one...
Click to expand...
Click to collapse
No, I never used tethering.
My phone is at RMA again, I asked to fix it FOR REAL, I'm just hoping.
I've had a similar experience since first getting the phone. While with light usage, I used to get anywhere between 16 hours to a full day of battery life, I'll only get between 4 and 6 hours of screen-on time. Whether full stock or ROMs, it's always been the same. I've eventually just chalked it up to hardware being the issue and made sure to always have a spare battery and charger with me at all times.
I got my phone back.
They said that they changed the motherboard. On the package the note is "sostituzione board unit".
In the next few days I am gonna do some test to see if they really solved the problem, I really hope so.
supermario3 said:
I got my phone back.
They said that they changed the motherboard. On the package the note is "sostituzione board unit".
In the next few days I am gonna do some test to see if they really solved the problem, I really hope so.
Click to expand...
Click to collapse
Nice to hear
Today I was suprised of my phone's duration (still no serviced again): more than 1 day (of course without doing much) and only 10% drain during the night.
I don't know what happened BUT i can say also that I'm experiencing now a problem with the network (GSM, 3G): the network crashes sometime also while calling or while idling.
Today it did not crash in a > 10min call, so let's see also the battery drain during this night
...because strange stuff happens!
try update to the latest new radio.. flash radio.img
galaxy nexus i9250
I think that the problem is solved.
It was a hardware problem.
I'm on CM10.2stable now.
Latest radio and bootloader.
Now my phone last enough .
I called Samsung a lot of times to urge them to fix my phone.
EDIT: I'm now on 20h20m on battery with 3h23m screen on and 4% left. Goood
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
Related
A few things:
- running kavanna's WM6.1 080408 ROM
- the phone is pretty much idle (I'm not actively using it when this happens)
- I am *not* overclocked (stock cpu clock)
- the phone/battery is probably 2-3 months old
- no strange processes other than the stock ones that come with the ROM that run on startup
- I carry my phone in my pocket, so it typically happens when I am carrying it like that.
Every once and a while, my phone suddenly gets very warm (on the battery side). At that point, it typically becomes un-responsive/freezes and I have to take the battery out to reset it. During this time, while the battery/phone case is hot, I can drop 20-30% battery charge in a manner of minutes.
Since I have to do a hard reset typically, I can't tell what process is stuck (if there is one) and/or what else might be happening behind the scenes. I take the battery out, reset it, power back up and all is fine.
This doesn't happen often, but it happens enough to where I would like to see if anyone else has this strange gremlin pop up every once and a while.
ruinertt said:
A few things:
- running kavanna's WM6.1 080408 ROM
- the phone is pretty much idle (I'm not actively using it when this happens)
- I am *not* overclocked (stock cpu clock)
- the phone/battery is probably 2-3 months old
- no strange processes other than the stock ones that come with the ROM that run on startup
- I carry my phone in my pocket, so it typically happens when I am carrying it like that.
Every once and a while, my phone suddenly gets very warm (on the battery side). At that point, it typically becomes un-responsive/freezes and I have to take the battery out to reset it. During this time, while the battery/phone case is hot, I can drop 20-30% battery charge in a manner of minutes.
Since I have to do a hard reset typically, I can't tell what process is stuck (if there is one) and/or what else might be happening behind the scenes. I take the battery out, reset it, power back up and all is fine.
This doesn't happen often, but it happens enough to where I would like to see if anyone else has this strange gremlin pop up every once and a while.
Click to expand...
Click to collapse
I had this exact same issue beginning of last year. Come to find out, it was the battery
pudgedaddy said:
I had this exact same issue beginning of last year. Come to find out, it was the battery
Click to expand...
Click to collapse
Yeah, I did a search but I couldn't find any definite answer given that my battery/phone were basically brand new.
Hopefully the solution is that simple. What's odd is that when this doesn't happen, my battery holds a good charge for days. Go figure. I wonder if I can convince T-Mobile to send me a new battery...
ruinertt said:
Yeah, I did a search but I couldn't find any definite answer given that my battery/phone were basically brand new.
Hopefully the solution is that simple. What's odd is that when this doesn't happen, my battery holds a good charge for days. Go figure. I wonder if I can convince T-Mobile to send me a new battery...
Click to expand...
Click to collapse
i had only had my phone for about 2 months when this started happening. Since i did not know what the issue was, i naturally called them to troubleshoot, they ended up sending me a battery as a replacement, no charge.
pudgedaddy said:
i had only had my phone for about 2 months when this started happening. Since i did not know what the issue was, i naturally called them to troubleshoot, they ended up sending me a battery as a replacement, no charge.
Click to expand...
Click to collapse
Yeah, looks like I am going to have to BS a little being that I have a cooked 6.1 ROM on it. I doubt that they will support that given that they only have 6.0 out right now (officially that is, yes?).
ruinertt said:
Yeah, I did a search but I couldn't find any definite answer given that my battery/phone were basically brand new.
I wonder if I can convince T-Mobile to send me a new battery...
Click to expand...
Click to collapse
You shouldn't have to get them to "send" you one. Just go to your nearest T-Mobile Store and tell them that you've been having trouble with your battery overheating. After enough banter, they should be willing to give you a new one free of charge. I got a new one out of them last year with hardly any effort.
ruinertt said:
Yeah, looks like I am going to have to BS a little being that I have a cooked 6.1 ROM on it. I doubt that they will support that given that they only have 6.0 out right now (officially that is, yes?).
Click to expand...
Click to collapse
how are they going to know which ROm you are using? just tell them that the phone locks up and when it does, you feel the phone getting very warm, also tell them that you've already done a hard reset and let the phone set after the hard reset without any 3rd party software and it still locks up
pudgedaddy said:
how are they going to know which ROm you are using? just tell them that the phone locks up and when it does, you feel the phone getting very warm, also tell them that you've already done a hard reset and let the phone set after the hard reset without any 3rd party software and it still locks up
Click to expand...
Click to collapse
Just called and here is the status:
- The battery is only warrantied by T-Mobile for 3 months (I've had the phone for 3.5 months, so they cannot warranty it). However...
- The battery is warrantied by HTC for 1 year, so I have their number.
- T-Mobile is sending me a new phone in case this is a hardware issue (does not come with a new battery, however).
So, I'll try the new phone with the original battery. At least I will get a new phone with no scratches on the screen (can put my screen protector on). If the problem still persists, I'll then contact HTC (have their support #) and have them replace my battery.
So, all should be well 'cept for the fact that I have to reload my ROM again along with all of the settings. Oh well...
ruinertt said:
Just called and here is the status:
- The battery is only warrantied by T-Mobile for 3 months (I've had the phone for 3.5 months, so they cannot warranty it). However...
- The battery is warrantied by HTC for 1 year, so I have their number.
- T-Mobile is sending me a new phone in case this is a hardware issue (does not come with a new battery, however).
So, I'll try the new phone with the original battery. At least I will get a new phone with no scratches on the screen (can put my screen protector on). If the problem still persists, I'll then contact HTC (have their support #) and have them replace my battery.
So, all should be well 'cept for the fact that I have to reload my ROM again along with all of the settings. Oh well...
Click to expand...
Click to collapse
make sure that you re-install the original t-mobile ROM on the phone you're sending back. otherwise they may end up billing you later on, for "non warranty" part
pudgedaddy said:
make sure that you re-install the original t-mobile ROM on the phone you're sending back. otherwise they may end up billing you later on, for "non warranty" part
Click to expand...
Click to collapse
*noted*
I figured that might be an issue. I'll do a search for it (I think I remember a thread that had it a while back).
ruinertt said:
*noted*
I figured that might be an issue. I'll do a search for it (I think I remember a thread that had it a while back).
Click to expand...
Click to collapse
Or...you can just go to T-Mobile.com and download the original ROM.
Rip Syntaxx said:
Or...you can just go to T-Mobile.com and download the original ROM.
Click to expand...
Click to collapse
That's too much work. Found it in Mikey's repository instead.
From searching, it looks like tons of people are having random reboot issues with the HTC EVO. Let's make one thread to put everything so maybe we can figure this out.
Side note, it looks like the HTC desire has the same issue:
http://forum.xda-developers.com/showthread.php?t=676402&highlight=rebooting
So post what you've tried that hasn't worked.
If you think you have a solution, share
One thing I've noticed is it seems heat related.
I've installed temperatures monitors and it seems around 32 degrees Celcius is around when it reboots. It will reboot loop usually. This can be cured by pulling the battery and waiting for it to cool down, or just put it in the freezer for 4-5 minutes.
I've tried underclocking it with the screen dimmed way down, and running it without the back cover and it still overheats.
For me, the problem came out of nowhere. I had the device for over a month with heavy usage and no problems. My current GUESS is it must be a physical problem. Not enough thermal grease or something...
It looks like the HTC Desire users may be getting replacement motherboards to fix their issue.
Does the HTC EVO and Desire share parts?
From other threads it looks like:
Root or Stock - Doesn't matter
Radio version - Doesn't matter
Rom version - Doesn't matter
GPS Fix - Doesn't matter
GPS turned off - Doesn't matter
3G data, 4G data turned off - Doesn't matter
Hard Reset - Doesn't matter
Found this on the HTC Desire reboot thread:
Latest test list for HTC Desire RR (Random Reboot) problems:
-All phones with s/n HT03 to HT07 can get this problem (Minor problem from SH09 so far)
-Starts around 1.5 to 3 months after use
-Reboots get worse over time
-Firmware and android version doesn’t matter which you have
-Force apps2sd doesn’t matter if you use it or not
-PVT1 or PVT3 or whatever doesn’t matter
-Screen type, doesn't matter if you have AMOLED or SLCD
-There seems to be an antenna/radio/simcard issue also
-Overheating causes reboots too
-Reboot is not always temp related
-SD card size doesn’t seem to matter
-Having apps on SD or not doesn’t matter
-Size of files on SD doesn’t matter
-Rooted or not doesn’t matter
-Motherboard changed after repair doesn't always fix it
-Sim locked or not doesn't matter
-Provider doesn't matter(vodafone, kpn/hi, T-mobile etc all got it)
-Most likely hardware issue, sense flashing won’t fix it, yet changing motherboard will
-Restarting doesn't fix it
-Factory resetting doesn't fix it
-Changing/buying new battery Doesn’t fix it
-Using app killers or shutting down some services yourself doesn't help
-Leaving all settings on default doesn't fix it
-Plugged into car charger in the past doesn’t matter
-Hboot version probably doesn't matter (still not fully tested)
-Having a phone cover or not doesn’t matter
Click to expand...
Click to collapse
wifes phone has been doing it very bad...one that has never been rooted...
was going to root it and try new rom but seems to be a hardware issue.
any other comments on this subject?
My stock rooted Rom just rebooted for the first time today. I really don't rememebr what I was doing st the time....but this has never happened before. I assume there's no event log to check.
Sent from my PC36100 using XDA App
I had been facing this with increasing frequency. I got the phone on launch day, and the problem started over the last month, getting worse all the time. I agree with the OP that there does not seem to be any obvious cause -- sometimes it is heat related, sometimes not. Any time I push the phone (run psx4droid, or navigation + anything else), and sometimes even with lighter usage, like on a phone call. Unrooting did nothing to stop the problem.
After extensive searching, I found three possible causes: bad battery (I tried a new one and the problem continued, but this seems a good starting place), bad memory blocks, or bad processor.
I was unable to find any solution to this problem. I took my phone to Sprint today, and they told me that their tests didn't show a problem. Then I made it happen in front of them (launch navigation to anywhere, then a couple more apps, then boom, reboot) a couple times (really, after the first time, letting it turn back on pretty much caused it to happen again).
After that, they agreed to replace it. I do have the TEP, but they assumed that the problem was hardware related so I don't know if you have to have it for them to replace it.
Strangely, they gave me a white one as a replacement.
I haven't had any problems with the new (well, re-manufactured) one, and I hope it stays that way, but I guess only time will tell.
I'm currently experiencing the problem as well, funny thing is every time it happens, the phone is NOT in use, simply sitting on table or desktop in standby. This happens about once every two days.
Currently running rooted evio2 1.3.1
Wow, I was about to start this thread, when I saw this. I guess I was like 10 minutes late. Either way, i believe something messed with the hardware. My little bro cracked my screen badly, so I am getting a new evo anyway, but will I be able to get one free bcuz of this? This is really a terrible problem. Somebody needs to de-assemble their precious evo and see if there is an obvious problem. thanks a bunch. Subscribing.
same here.
happens mostly when on the charger and i am using it at the same time. so heat related seems likely.
can anyone get a logcat of it happening?
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Sprint replaced mine for $35 [a refurb]. That's the end of that.
But now, I can only use the speaker to hear my callers. Gotta go back and get another!
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
thlinx said:
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
.jond said:
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
Click to expand...
Click to collapse
Actually I just had a reboot lol.
Sent from my PC36100 using Tapatalk
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
I bought my EVO on launch day (HW Version 002), and have not had any problems until around Oct 13.
I took the phone on a trip to Orlando, and as soon as I got off the plane and turned on the phone, the problems started happening. It has been happening ever since, even since I returned home.
I bought my phone at Best Buy, and have had their Geek Squad send it back to try to fix it. I also added the complaints about screen separation to the workorder so that they would be more likely to replace the device. Hopefully, this fixes the issue.
I also think it is heat related, but I don't know why it is just now becoming an issue. Just to make sure the folks at BB could see the issue happening, I put the phone in front of my car's heater for a few minutes, then started up Google Earth, and was able to make the phone start boot looping while I walked into the store.
I tried hard reset, soft reset, update prl, underclocking, GPS Reset, new battery, new SD Card, and none of those things worked. I wonder if the removal of the 30 fps limit in the last update caused some type of heat damage?
I just had a reboot last night while trying to look at a picture I'd just taken in the Camera app on CM6.0.0. Only the 2nd or 3rd time it's happened. Still annoying though. Hope it doesn't get worse.
.jond said:
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Click to expand...
Click to collapse
How much they charged you?
Sent from my PC36100 using XDA App
MedSchool26 said:
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
Click to expand...
Click to collapse
I reset mine back to stock. Unrooted it and everything.
Didn't fix the issue for me.
Now I did try erasing all the stuff that's erasable inside recovery and it seemed to go a few days without a reboot. Not sure if that was a fluke or not.
I've reviewed some solutions on here regarding the UK rom version and loading it to the device. My concern is for the warranty on the device does anyone have the T-Mobile rom available to load on the defy? I'd assume that'd fix my issue where the phone has a boot loop and a wipe is not fixing it. I tried talking to motorola and that was a complete fail (see conversation below).
Reymer: Hi, my name is Reymer. How may I help you?
James: i am using a motorola defy. all of sudden today it stopped working. it boot loops showing the motorola boot screen and tmobile screen but then keeps doing this over and over again. i tried to do a factory reset but still failed. is there anyway for me to manually update with the original rom again with an update.zip similar to the motorola cliq?
Reymer: I am sorry to know that.
Reymer: Are you referring to a bootloader screen?
James: not exactly. it acts like it's booting up as normal but keeps repeating the process. i help down the volume and pwr button to get to the other screen can't remember what it's called so i can attempt a factory wipe on the device.
Reymer: Can you please take out the battery, return it after a few seconds and turn the phone back on? Let's try to see then if the phone is still doing the same thing.
James: i tried that already. still the same thing.
Reymer: Were you able to use a different battery?
James : why would a different battery change anything if it's software related? i know from all the research i've done so far it's needs to software reloaded to it however i cannot find the software for this device on the motorola website. it's a tmobile usa phone.
Reymer: We need to determine first if it's a phone or battery issue.
James : okay but explain to me what the battery has to do with the phone software? that's like telling me to put gas in my car to fix a flat tire they have nothing to do with each other.
Reymer: How did you know if that's a software issue?
Reymer: We are doing every means to isolate the case.
James : because it powers on and starts to boot up but just boot loops it doesn't power off. the battery is brand new and has a full charge i got the battery today so i know it has nothing to do with the battery. i've also worked with android development and understand isolating the issue checking for hardware concerns first which i did prior to getting on this chat.
Reymer: I suggest that you send in your phone at our repair facility and have it evaluated by our repair technicians. If proven that it did not suffer physical or liquid damage, that will be repaired for free.
Let me just inform you of the repair time frame, it will be 5-7 business days from the date we receive your item before it will be sent back to you.
Reymer: All Motorola phones and accessories have a standard one year warranty barring physical or liquid damage from the date of purchase.
I ended the conversation after that
Use my debranding/debricking guide in the dev section. If you are a US customer you will lose 3g and wifi calling as the US firmware is not available at present so you have to use UK - there are fixes for this about.
Sent from my Defy using XDA App
My first response to your phone call is... well, when I'm asked to do something absurd with my gear (and why would you have an exta battery anyway?) I always say, "yes, done that." "Have you tried jumping out the window with the phone up your ass singing "God Save the Queen?" "Yes, twice. No go." However... there do seem to be some whacko battery issues related to rebooting issues on Motorola phones. Example:
"I just got a new battery for my Droid, and the battery came 60% charged. So I did the battery drain until it powered off. I then put it on the dock to do a full charge, and now the phone is in a constant boot loop."
Same guy then:
"I just tried the old battery, and it does not go into the loop with the old one."
So..?
scrannel said:
My first response to your phone call is... well, when I'm asked to do something absurd with my gear (and why would you have an exta battery anyway?) I always say, "yes, done that." "Have you tried jumping out the window with the phone up your ass singing "God Save the Queen?" "Yes, twice. No go." However... there do seem to be some whacko battery issues related to rebooting issues on Motorola phones. Example:
"I just got a new battery for my Droid, and the battery came 60% charged. So I did the battery drain until it powered off. I then put it on the dock to do a full charge, and now the phone is in a constant boot loop."
Same guy then:
"I just tried the old battery, and it does not go into the loop with the old one."
So..?
Click to expand...
Click to collapse
As far as I know, Li-ion batteries hate depletion, they shouldn't be totally depleted.
"Depletion below the low-voltage threshold (2.4 to 2.8 V/cell, depending on chemistry) results in a dead battery which does not even appear to charge because the protection circuit (a type of electronic fuse) disables it." -
en.wikipedia.org/wiki/Lithium-ion_battery#Prolonging_battery_pack_life
TPGamer said:
As far as I know, Li-ion batteries hate depletion, they shouldn't be totally depleted.
"Depletion below the low-voltage threshold (2.4 to 2.8 V/cell, depending on chemistry) results in a dead battery which does not even appear to charge because the protection circuit (a type of electronic fuse) disables it." -
en.wikipedia.org/wiki/Lithium-ion_battery#Prolonging_battery_pack_life
Click to expand...
Click to collapse
Not sure what you mean. That a bad battery can cause problems? That IS the point, even if it's something produced by the user. It's probably not the cause, but it might be worth a try? This rebooting issue, though not tiny, does seem to be limited to some Euro (UK?) phones. Maybe a release of a bad batch of batteries? I realize that that poster probably should not have depleted his battery (though... don't we all once in a while?) maybe by crapping out his battery he induced his re-booting issue. But that still could be the cause of others' problems.
Hi !
I have this problem too.
My Defy always reboot in loop
This is a french Vodafone branded phone with Blur_Version.2.21.0.MB525Blur.Vodafone.FR
The only thing I see is when I received the phone I started it without charging the battery.
I know that was noticed in big font but i was hurried and didn't think that can be a problem for the battery
every body i need help.
i have somthing wrong with my cell phone motorola defy
my cell phone do not turn on, but when i conected to computer i could install new rom ,
and again do not work with new cell phone and do not turn on again
Hi.
I have a Blur_Version.2.51.1.MB525,T-Mobile.en.GB is it rootable and is there a stable UK based custom rom?
Oyeah any Cynogen Mod 7 for the future?
Skillganon said:
Hi.
I have a Blur_Version.2.51.1.MB525,T-Mobile.en.GB is it rootable and is there a stable UK based custom rom?
Oyeah any Cynogen Mod 7 for the future?
Click to expand...
Click to collapse
I would love to see that also.
i have the same problem and tmobile is pretty much like screw you ive tried rsdlite and nothing all to no avail i think im just chalking 399.99$ and i promise im never buying another motorola product again
scrannel said:
"I just got a new battery for my Droid, and the battery came 60% charged. So I did the battery drain until it powered off. I then put it on the dock to do a full charge, and now the phone is in a constant boot loop."
Click to expand...
Click to collapse
that actually happened to me and i dont know what to do its really annoying.
Hello Guys,
so i got my new one x yesterday and im not very happy with it.
1. It does some random reboots, just lying around and reboots sometimes.
2. Phone "hangs up" with black screen and blinking buttons. As far as i know this is a "kernel panic"
This happened about 5 times now, last time as im writing this.
3. Battery drain is huge, seems like a result of the above problems. Android OS has about 90% battery usage and it dropped to 82% after 54mins without charging and just lying around.
On the both screens you can hopefully notice it, 26mins and it lost 10% battery.
After this kernel panic the battery drain changed and the Android OS stopped to drain so much battery.
This is the "out of the box" state of my phone. I changed nothing beside from charging the battery and installed some apps (normal stuff, angry birds and such).
Does someone have a idea about this? I hope or assume these a software related problems. But im not sure with the kernel panic thing can this be due to hardware issues? Should i ask for a replace?
You said you installed a few apps and games. Try going back to factory settings first, wait a while and see if the pattern repeats, if the phone behaves normally, then it must be something you installed, not all apps are optimised for ICS.
Good luck!
Dreist said:
Hello Guys,
so i got my new one x yesterday and im not very happy with it.
1. It does some random reboots, just lying around and reboots sometimes.
2. Phone "hangs up" with black screen and blinking buttons. As far as i know this is a "kernel panic"
This happened about 5 times now, last time as im writing this.
3. Battery drain is huge, seems like a result of the above problems. Android OS has about 90% battery usage and it dropped to 82% after 54mins without charging and just lying around.
This is the "out of the box" state of my phone. I changed nothing beside from charging the battery and installed some apps (normal stuff, angry birds and such).
Does someone have a idea about this? I hope or assume these a software related problems. But im not sure with the kernel panic thing can this be due to hardware issues? Should i ask for a replace?
Click to expand...
Click to collapse
check your kernel version pls
Ok thanks for your first impressions and help. Im trying the factory reset now.
I have done a screenshot of the kernel version.
First of all, and probably most important is to leave your phone charging for 6-8 hours without turning it on.
Then its spend the battery time where you do whatever it takes to.empty the battery completely until the phone is ready to shut down. Shut it down. Repeat charge process from above with device off. Turn it on and then you can be ready to test it for real. As far as reboots, you really should let the system settle down a bit. Give it a day or 2 without some extra heavy usage and I'm sure it will be just fine.
Sent from my HTC Desire HD using XDA Premium HD app
i hope this isnt a joke
joke or not, normal stuff apps can cause problems. the whole Android OS battery usage is because of apps you installed. it's a brand new phone and i wouldn't be too worried about it. i switched from Samsung to HTC because Samsung releases broken source code and doesn't seem like they really know how to do anything but stick hardware together. if i'm not happy with HTC, then maybe Motorola is making the next Nexus phone and i'll give that a try.
Please do keep us updated on how's everything working out ? Did the factory reset solved the issue? Hope this ain't an April fool joke ! Anyways hope everything goes well for you mate. Kept my fingers crossed on mine one x
So ok, i tried the factory reset twice. Seems Not to work atm. Im going to try it again. I hope Arhd and s-off is working soon
Im curios, maybe there are more ppl with this Problem after monday / tomorrow.
Ill keep you up2date.
Sent from my HTC One X using XDA
Return it.
There's no way a factory-reset device should be behaving that way. My guess would be hardware problems.
First wave of a new phone is always more risky, you can get a faulty device
catachresistant said:
Return it.
There's no way a factory-reset device should be behaving that way. My guess would be hardware problems.
Click to expand...
Click to collapse
Agreed, it sounds screwed to me.
I can't speak for the rest of the world - but I don't really know why people panic. If the phone ends up being unstable it's going back and they'll be refunding my contract - it's really that simple.
There was a similar problem on the original Desires. Linked to overheating especially with GPS.
djolebih said:
First of all, and probably most important is to leave your phone charging for 6-8 hours without turning it on.
Then its spend the battery time where you do whatever it takes to.empty the battery completely until the phone is ready to shut down. Shut it down. Repeat charge process from above with device off. Turn it on and then you can be ready to test it for real. As far as reboots, you really should let the system settle down a bit. Give it a day or 2 without some extra heavy usage and I'm sure it will be just fine.
Sent from my HTC Desire HD using XDA Premium HD app
Click to expand...
Click to collapse
I'm not going to say your wrong but could you post some evidence? Ok the first part is per the user manual so I will agree with that one. However there should be no need to empty and re-charge the battery should there? According to this site: http://batteryuniversity.com/learn/article/how_to_charge_when_to_charge_table Deep discharge wears the battery down. It also says no priming is needed.
Then the second point letting the system settle down? what? let what "settle down"? I don't even understand this statement. If you explain what you mean and again if you can provide some evidence that would be great. Thanks.
same problem
I experience the exact same problem. Random reboots and crashes.
What did you end up doing?
same problem too
Me too.
Get the phone for 2 days, and randoms reboots.
Get the same kernel that Dreist.
Try yesterday a factory reset, but no change.
I have the same problem. Constant reboots out of the blue. I'm back on my nexus which is super reliable. Probably gonna return it.
Got 3 reboots in a row yesterday but it was after flashing bricked kernel and battery under 23%, plugged the AC cable and no more reboots,perhaps the battery level is false with bricked kernel...
Just swapped mine out for a new one but now the new one has a yellowish screen. (sigh)
unrooted, locked, Xperia Ion LT28at, ATT ICS (not sure of the latest version number, the update came just last week)
Last thursday i received the notice for an update from AT&T for my Ion. It was a ~3.8Mb file, and the phone seemed to go through the update process perfectly fine.
Friday i noticed the phone lasting an abnormally long time, though. The battery seemed to get a very noticeable bump in life between charging. No complaints, so i didn't look into it. After nearly 40 hours of not charging (and some fairly 'normal' use, a few calls, texts, some browsing, etc.) the phone was down around 35% and i charged it before bed. The 35% was what was surprising, as i'd often skip a day between charges without much trouble...its just the 2nd day i'd be hanging around 3%, not 35...
So it charged fine, no issues, left it on there for about 2 hours. checked it the next morning (it was not charging over night)/ Then i noticed what was going on. The phone would stay at 100% for nearly 10 hours? This is illustrated in the status section of settings, as well as through my battery widget thing, and it seems to line up with the battery icon in the notification bar as well. Also, its not like each percentage takes that long. After it finally breaches 100% down to 99%, the indicated battery level changes like it used to.
So it seems to be some pretty off in terms of scaling. I purposely drained the phone to see what was happening. As soon as the phone hits about 29% its over. No warnings, no anything. It just does its dead battery boot down. If i reboot before recharging...it gets through the boot process mostly, but shuts off within a few seconds of 'preparing internal storage'. Then it has to charge for a few minutes before i can boot it again, in which case its already reading 34+% in a matter of minutes.
I've read all the debates on battery status wiping on rooted devices, but none of the people doing that seemed to have this problem. Its usually a phone that will say 100% then drop to 60 or something as soon as the plug is removed. I did a few hours of research and couldn't find one example of what i'm having haha, but sorry if i missed something obvious.
I apologize for the length, just trying to be as specific as possible, and any help would be greatly appreciated. I'm up for anything as far as reflashing, rooting, whatever. I just figured i'd wait for all that until the JB update next month, rather than doing some of it twice. Has anyone come across anything close to this, though?
Thanks, and here is a screen shot of the battery status. Look how many hours it too to drop from 100 to 99...
https://docs.google.com/file/d/0B9wG_iZEqPQNSXR5aDdIWjlmNFU/edit?usp=sharing
It's a OTA update bug. Update your phone with PC Companion or SUS.
Sent from my LT26i using xda developers-app
thanks man, thats what i figured.
I'll reflash it around lunch today and report back. should be fine, overall battery life has not changed at all. Still get 14 hours of regular use.
So the only option i had through PC companion was a 'repair', as it was simply saying my phone was up to date otherwise.
Ran the repair, which reinstalled 6.1.0.111 AT&T ICS firmware...and it doesn't seem to have changed anything. Phone hasn't been charged in nearly 24 hours other than when it was plugged into my PC for the repair...and its held 100% for 50 minutes so far, which is definitely not accurate.
I'm downloading the newest version of flashtool now, going to go back to the original ICS version before this update...and see if that changes anything.
EDIT: you can see the original quote in the post below.
recently got off the phone with AT&T about returning my refurbished Ion, which i ended up not needing. The new tech had listened to the recorded info i was given, and claimed it was inaccurate, and that there is no internal evidence of a mass returning of Ion's...This isn't really important, just didn't want to cloud up any future searches if someone happens to run into a similar battery bug.
to reiterate. Battery status was messed up, phone was turning off at ~30% posted battery level. tried flashing, rooting, etc. no luck. Was given a refurb'd ion, with instructions on what to do to return my bugged device. First thing was simply booting the phone without a sim card (and then doing a full factory reset and storage format coming after). the sim-less boot up wiped the bug. may be coincidence, may be not.
in either case, i've been fine ever since with the original Ion. So if you end up with a goofy battery status, the rooting and battery recalc thing didn't work for me...at least didn't do anything for multiple charge cycles...but it went away immediately with a simless boot.
jtr165 said:
ok, so anyone still using an LT28...be advised...
Just got off the phone with AT&T, and a cool chick by the name of Dallas informed me that my issue has been well documented throughout the company. Warranty claims to the point that Sony is now on the burner for it. According to her, the Ion has had more warranty replacement claims than any other phone from 2012...a lot of which is from what i'm having.
As soon as i mentioned an erratic battery status, she described exactly what the problem is...based on her personally handling over 20 calls recently for the same issues. She claims her paperwork describes it as a design issue, that some sort of OS controlled chip begins to corrode and loses 'sight' of the embedded battery. A common problem on lots of smart phones, its just most of them allow battery removal and terminal cleaning....of which we're not lucky enough to easily do. Since mine just started, it begins as just incorrect battery life readings...but will quickly turn into random boot downs due to the OS receiving incorrect information.
She also confirmed what many others have stated...the Ion WILL NOT get an update from AT&T for JB, you'll have to run a generic firmware with this phone. She blatantly said AT&T wants nothing to do with this phone anymore, its no longer even listed to any degree (fyi there is now a fire sale on the official dock for the Ion...$10)
I take all that with a grain of salt though, as i've witnessed next to nothing of this issue with this specific phone on this forum, as well as others. I guess its possible that people having problems just did the warranty, and never posted on forums...but the facts don't lie...repairing through PC companion did nothing...Unrooted battery calibration apps did nothing (said i can run video for 30 minutes with zero battery usage...awesome)...reflashing to previous AT&T ics did nothing....reflashing to AT&T GB did nothing...reflashing to LT28i did nothing...rooting LT28i ICS and running various battery 'cleansers' did nothing (it just reset my 'since charge' information...)
My ion has never been dropped...never been submerged...while i doubt the situation is as bad as she was saying...I've dealt with AT&T customer support a lot, and never had someone so specific and creepily accurate with a problem i had...
I'm in the warranty claim now, but will wait a bit and see how much worse it gets. I'm not ranting or anything, just advising those interested to keep an eye on their battery info. According to one source at least; its something that could effect every LT28 out there.
Click to expand...
Click to collapse
While it's great that she was able to help you, her description of the cause is a flat out lie. It doesn't make any sense for the chip to become corroded or that cleaning contacts would help if we could only remove our battery. This isn't the 1980's with leaking batteries and copper contacts. While it could be a chip issue, her reasoning is wrong.
I'd also like to point out that if this was as big of an issue as she claimed then I think tech websites would have picked up on it and reported.
I haven't seen anyone with the international versions reporting the issue, which leads me to think it's an at&t issue. Or at least that's my hope. We just have to wait and see.
Sent from my LT28at using xda app-developers app
I should've emphasized a little more that the reason for the problem didn't sound all that accurate, but she was dead on with explaining the symptoms, which was enough for me...So i did take the warranty claim, as apposed to just messing with it more...
Agreed though, thats what i was getting at earlier...if the problem really is as bad as she said, it wouldn't stay so quiet in various forums. We would've definitely hear of it by now.
interestingly, i had no luck finding the OTA .111 update when i tried to returned the phone to stock for return. I could only find .111 through PC companion, even though the day before the OTA prompted me immediately...they might have pulled it down?
That's possible. I haven't been prompted for the update, but I'm sim unlocked and in Poland.
Sent from my LT28at using xda app-developers app
So its been a weird week, smart phone wise, for sure...
Friday night i got the replacement Ion in the mail from AT&T. I didn't mess with anything until yesterday afternoon, when i had a few free hours to transfer everything over.
My original Ion was at about 40% battery. I figured i'd send it back to them 'close' to when it does its 30% shut down thing. I took out the sim card and SD card, and turned it back on to connect to my PC to finish getting any residual pictures/files off the internal storage...and finish with a 'sim-less factory reset', per the AT&T directions.
This Ion had been reset multiple times, had been reflashed at least 5 times...rooted, unrooted, then rooted again...etc...the ONLY thing i had not tried...was removing the sim card and turning on the phone (it had been out several times, just never started it)...and at this point the phone was still on the newest .111 AT&T ics build. I just never thought of that, i guess...
figures...as soon as the phone started without a sim, the battery icon flashes...disappears...then reappears at ~10%...which is exactly where it should've been...I checked the battery status in settings and it showed that cliff, only this time falling from 40 to 10% and holding...normally it would fall from 30 to 0, and then go straight up to 30 again as soon as charging starts...
I have no idea if this was just a coincidence, but i had rebooted this phone so many times i figured it would've reset by now. 24 hours later and its remained ok for now...kind of happy though, i'd rather keep my 'worn in' ion than the replacement haha...