Related
My inspire keeps powering off at ranodm times and has gotten worse. If its plugged into a power source it will stay on, but the second its pulled off theres a huge chance that it will just randomly power off. I've wiped the battery stats, factory rest a bunch of times, tried multiple roms and radios and can't find a solution. ANY HELP WOULD BE GREATLY APPRECIATED!!!!
See if ATT will give you a new battery.
Tx Redneck said:
See if ATT will give you a new battery.
Click to expand...
Click to collapse
I know it sounds like he's being an ass, but I think he's right. I have the exact same problem. Used CoreDroid, MIUI, & HoneySense 4 & 5 and they all randomly rebooted. I noticed that after I powered back on, the battery level would be significantly different. It got progressively worse as the battery level drops. Once I get to about 23%, it just turns off when I try to do anything. I speculate that the sudden increase in battery drain from the screen getting bright & the radio draws more current than the battery can provide.
To test, I got my phone to the point that it would turn off every time I booted it. It would show the homescreen & say that it had 18% battery. I then plugged it in to the USB charger & it works fine. I'll be replacing the battery ASAP.
this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries
cordell507 said:
this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries
Click to expand...
Click to collapse
Ok then, you "know" it's not the battery - so what is your speculation? Until I get the spare batteries I ordered today, I won't be able to fully test the battery theory. I can only say with certainty that the phone doesn't shutdown while plugged in.
I could also go along with another theory - The Thunderbolt got a recent OTA update that makes them randomly shutdown. Is it possible that a piece of that code made it into the new Gingerbread ROMs? I didn't note the issue running CoreDroid 6.4 (a GB build but the last to use EXT3 instead of EXT4 and was also released before the TB OTA update), but only after upgrading to 6.5. Could it be some finicky problem with EXT4?
meatrocket said:
Could it be some finicky problem with EXT4?
Click to expand...
Click to collapse
Actually, forget this part. I forgot I used HoneySense 4.0 with EXT3 & still had the random shutdown problem.
with it plugged in do a nandroid backup and then restore to stock then restore back with only restoring system and data
I know its not the battery because it will stay in CWM for several minutes and much longer than it does on without any random shutdowns. Going to try the return to stock and reflash method and post back.
Ok, so that I get this right, the test plan is to: flash back to stock, re-root & then reflash to a new ROM such as Coredroid 6.8? If that's what one of you are going to do, then I'll do it also so we can see if we get the same results.
Well, I actually downgraded to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed, went through Bubby's One Click and the damned phone shutdown upon boot to the first image of Bubby's. I figured MAYBE something was wrong with Bubby's One Click as I had originally used the ACE hack kit.
I reverted back to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed again & decided to use it for a minute to see if it shutdown and it DID!
There is either (A) a problem with my battery or (B) a problem with the charging system on my phone. This IS NOT a firmware/radio issue! It may be different for you, but I'm positive about my phone now. I'm going to wait until my new batteries come in on Wednesday and if it acts the same, I'll be replacing my phone under warranty. I should also note - I've never overclocked this phone, so I don't want anyone fear-mongering the N00BS about "see what overclocking will get you"!
Does yours stay on when its plugged in?
samftw said:
Does yours stay on when its plugged in?
Click to expand...
Click to collapse
Yes. I noticed the shutdowns started about 1½ to 2 weeks ago. It got more frequent as time went on. The phone is practically unusable now unless I leave it plugged in. I suspect that if it is indeed the battery, it may even start shutting down when plugged in since the phone will turn off if you remove the battery when it's plugged in. Just a hunch.
same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass
samftw said:
same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass
Click to expand...
Click to collapse
Well, bummer dude. I called AT&T and they said that the battery was covered under warranty & they'd be happy to send me one right out. The only problem was that they didn't have any in stock! They offered to credit my account with whatever I have to spend on replacing the battery myself. When I get the 2 batteries from Amazon & make sure they work, I'll get the credit for them applied to my account. It was only $25 for 2 batteries & charger shipped.
I called my local AT&T Corp stores to see if they had any batteries for the Inspire & they didn't either. Me thinks this widespread shortage of batteries could be indicative of a bigger problem.
WoW! Here's the feel-good part of this story....
As I posted earlier, AT&T service didn't have the battery to send me. I couldn't find a battery anywhere - I called the 2 AT&T Corp strores, BestBuy and Batteries +.
I went to the AT&T Corp store where I bought the phone & signed in for help. The girl came over to help as I was explaining to her what was happening & telling her that I wanted to take the battery out of her demo phone to make sure it was the battery. If it wasn't, then I could call service back & have them ship me a repalcement phone instead of having to wait until the batteries I ordered off of Amazon arrived.
She told me that she didn't want me to mess her floor phone up & offered to go in the back & get a phone to test with. She came back with a new battery still in the plastic. I popped it in and sure enough, it has been the battery! I told her thanks and that I felt a lot better knowing that it was indeed the battery.
She insisted that I keep the new battery since there were none to be found & she would "adjust" the phone she took the new battery from. I assume "adjust" is speak for "send it back as defective". I'm really positive about the whole experience, especially since she didn't have to do that at all. You can bet I'll be going back to that Corp store & buying from that rep when I'm ready to get my Samsung Galaxy S II!
I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.
King Askaba said:
I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.
Click to expand...
Click to collapse
Uh...did you read ANY of the thread or just post a reply? It seems rather obvious that there's a battery problem. Maybe you could do some of the same or similar testing we did to see if you have similar results?
The only thing I didn't say in all of this is that I got my phone on 2/14/11. So I've had it almost exactly 4 months before the problem really came up.
TLDR: Skip to TLDR near the end!
Well, this is probably the tipping point that will make me demand a new phone from Magenta, because this is getting out of hand. My phone will periodically stop charging, for seemingly no reason at all. Usually its when it has relatively low power already that it decides it doesn't want to recognize the cable being plugged in.
Usually, I will just pull the battery and drain the remaining power via the power button, put the battery back in and all is well. Lately, it happened that it stopped charging and didn't respond to battery pulls, then got so low that it refused to even boot (flashing empty battery icon). This lasted about a day and after I had went into the T-Mobile store (Which they MADE me drive 30 minutes to the store to be there in person so they could hand me a piece of paper saying they'd mail me a new unit. Bull**** in and of itself.) the phone decides it wants to start charging again. After a few more frustrated battery pulls and doing nothing new with it.
When I get my new phone (no new battery), I put the battery in that one and use it, and all seems fine. This one has worse screen bleed (top left corner was pretty much a spotlight), but I'll take that for a working phone at this point. A few days ago I was just heading out on a 3 hour trip for a short vacation when the phone reboots on me while I'm listening to podcasts. Never had this happen with the other 2 G2X's I've had. Yesterday, the thing decides to stop charging as well, but a battery pull while the device was still on did the trick and it charged again.
Once I got home I figured I'd use the original G2X, as that has everything still on it, and migrating those app settings and data is a pain. Also, if it has worse bleed, reboot problems, and the same battery issue, its worse than what I already have.
(TLDR)
Now to my current problem. The phone, once again, stopped charging and has again discharged to where it wont boot. My questions:
1) Is there a way to recover my battery without just letting it sit and praying it charges again?
2) What is the underlying issue here that could cause this? Bad software? Bad hardware (in the phone itself)? Bad battery?
3) What is the best way about getting a new phone for free (or as close to free as possible), preferably an upgrade like the Sensation 4G? I don't want to deal with my local store, as they have been proven to not know ****, and the first line of defense on the phone isnt much better.
Well i am not an expert here but Just by process of elimination it seems to be the battery. They gave you a new phone and not a new battery and now it is doing the same thing. It has to be the battery so I would go back to the store and tell them that they gave you a **** phone as a replacement and it was the battery that was the problem the whole time. They shold be able to give you a new phone and battery. Tell thewm the screen bleed is terrible and the phone yoyu had was really good except for the battery issue. Maybee someone else can give a second opinion about that battery though. Dont just go on my words I am not a pro. Good luck man.
Charlie
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it
If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries
i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium
spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha
I agree. It still sounds like a battery issue.
I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.
I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App
Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.
If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!
The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.
Hello,
My wife and I both have a Nexus S, which are both almost 2 years old now. She has always been running stock ROMs and only updated when there was an OTA update available. No rooting, no nothing I however tried as much as possible and currently running SlimBean 4.2.2 Build 5 :good:
Since 3 days now, the battery in my wife’s phone isn’t charging anymore. I tried the following:
- Use my charger and an old Nokia charger: doesn’t work
- Put my battery in her phone: doesn’t work
- Put her battery in my phone and charge mine: works like a charm
The last one’s the solution for now: at night I charge one of the batteries in my phone and put it in hers, while at work I charge the other battery from my PC via USB.
Based on my ideas I’d say that something in the USB-port on my wife’s phone might be broken. However, there are 2 phenomena that I find rather strange:
- When her phone says it’s time to connect the charger, I take out the battery and put it in my own phone. I power up and the battery level reads somewhere between 60 and 80 percent
- When I power off her phone and connect the charger, I’d expect to see either the charging symbol or nothing. But none of these: it powers up as soon as I connect the charger
I don’t know about the first issue, but could it be the battery stats might be corrupted? The last issue makes me believe that the USB-port is at least not completely disconnected/broken.
Has anyone got an idea what the issue could be? I wouldn’t want to work on her phone rooting it if it isn’t necessary, but on the other hand she might be better off in various other ways as well
Thanks in advance,
Pieter
stalensnuitje said:
Hello,
My wife and I both have a Nexus S, which are both almost 2 years old now. She has always been running stock ROMs and only updated when there was an OTA update available. No rooting, no nothing I however tried as much as possible and currently running SlimBean 4.2.2 Build 5 :good:
Since 3 days now, the battery in my wife’s phone isn’t charging anymore. I tried the following:
- Use my charger and an old Nokia charger: doesn’t work
- Put my battery in her phone: doesn’t work
- Put her battery in my phone and charge mine: works like a charm
The last one’s the solution for now: at night I charge one of the batteries in my phone and put it in hers, while at work I charge the other battery from my PC via USB.
Based on my ideas I’d say that something in the USB-port on my wife’s phone might be broken. However, there are 2 phenomena that I find rather strange:
- When her phone says it’s time to connect the charger, I take out the battery and put it in my own phone. I power up and the battery level reads somewhere between 60 and 80 percent
- When I power off her phone and connect the charger, I’d expect to see either the charging symbol or nothing. But none of these: it powers up as soon as I connect the charger
I don’t know about the first issue, but could it be the battery stats might be corrupted? The last issue makes me believe that the USB-port is at least not completely disconnected/broken.
Has anyone got an idea what the issue could be? I wouldn’t want to work on her phone rooting it if it isn’t necessary, but on the other hand she might be better off in various other ways as well
Thanks in advance,
Pieter
Click to expand...
Click to collapse
Being completely stock and never modified, I'd say it's the usb.. Have you tried the OEM connector for the computer?..
1. I would take it to a shop
2. You could also try cleaning the contacts
3. May do nothing but if you take the battery/sim out and hold the power button for a minute, this is supposed to completely power down the phone, and then reinstall sim/battery and reboot..
4. Use this as an excuse to modify her phone (telling her that you can put it back to stock if she doesn't like it)..
This happens a lot on my phone, .. Be careful with my solution, I hope it works for you..
Basically inside the usb port on the phone, there is a flat pin. On my phone, this pin ends up bending downwards towards the bottom of the phone.. What you could do is get a very thin knife or a swiss army blade and just try and lift the flat pin in order to make it locate in the center of the usb port (hole) .. The issue being the pin doesnt connect with the charger ..
I hope you understood this
PS: Don't snap it !
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
RomanKasp said:
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
Click to expand...
Click to collapse
ICS may just have battery stats that don't work for your batteries. Try calibrating the battery:
http://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en
If I remember the instructions properly, install the app, charge to full (or half hour past full), open the app to press the button, run it dry, and charge it fully with it turned off (note the LED on mine turns green at the 90% mark, so leave it plugged in and off for about an hour past the time it turns green).
I found with the app, it takes forever to get that last 1% after using it, and it takes a while before dipping below it again, but it seems to be more accurate than CM thinking I had the stock battery installed (I have a couple Ankers now). Hope this helps.
Thank you but doesn't work
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
RomanKasp said:
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
Click to expand...
Click to collapse
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
joel.maxuel said:
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
Click to expand...
Click to collapse
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
RomanKasp said:
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
Click to expand...
Click to collapse
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
joel.maxuel said:
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
Click to expand...
Click to collapse
I tried everything, including wiping data/cache/Dalvik cache, then installing the file, I even tried to install the GApps too. Nothing seems to happen. It just gets stuck in the bootloop. When you first turn it on, it stops at "Starting apps", then if you reboot it, it stops working at CM logo (bootloop). I waited for 10 minutes or more, no result. Luckily, I did a full backup so I went back to CM 9. Seems like my phone is simply incompatible with this mod. No luck for me here .