I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Nobody?
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
denzel09 said:
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
Click to expand...
Click to collapse
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
rogeriorp said:
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
Click to expand...
Click to collapse
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
fabus said:
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
Click to expand...
Click to collapse
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
rogeriorp said:
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
Click to expand...
Click to collapse
Try catlog, i don't remember if need root honestly
Alright, got the guidances. Thank you both for the help, will leave some feedback later on.
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
rogeriorp said:
I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Click to expand...
Click to collapse
I just unlocked, rooted, flashed recovery and custom ROM on a refurb unit. I had kinda the same issue with this phone out the box stock. Mine will work perfect as long as its plugged in to either PC or wall charger. Once unplugged, pushing power to wake causes screen to shutoff after a few seconds or freeze, then reboot. Doesn't seem to be software related, as a clean install of pacman did nothing different. Touchscreen gets very unresponsive, also causing reboots.
sent from my Gs3
rogeriorp said:
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
Click to expand...
Click to collapse
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
rogeriorp said:
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
Click to expand...
Click to collapse
yes, you should see "Updating Android" with application number every time you switch DALVIK<->ART.
Cheers,
fabus said:
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
Click to expand...
Click to collapse
Waiting on Motorola charger to come in, then if no change, I'll pull a logcat.
sent from my Gs3
I also experienced the last 3 days complete freezes. No idea what was going on...
Unfortunately I couldn't pull any log messages from the phone by that time. Half an hour later it just responded normally... Didn't see if it rebooted in between or what exactly happened
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
rogeriorp said:
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
Click to expand...
Click to collapse
I never even checked to see which one it was using when I first got it.
sent from my Gs3
joeyhdownsouth said:
I never even checked to see which one it was using when I first got it.
sent from my Gs3
Click to expand...
Click to collapse
By deault it is Dalvik. If you have new phone so it will be Dalvik.
Did you said two posts before that you were using some 3rd party charger (not Motorola cable)?
Funny, but yesterday I had similar issues with freezes and random reboots. I was using some cable taken from Friend (not Motorola) and weird things started to happening:
- It was indicated on a screen that phone is charging (probably discovered usb cable plugged it), but it was discharging faster and started rebooting (because it reached below 1% battery state) and after some reboots battery was so discharged that phone couldn`t come up.
This usb cable was attached all the time to my phone and a computer.
- Next I connected phone to my reglar charger for night (from Zte Tablet, but really good and charges fast, never had issues with it) and it was fully charged.
On the morning I played music for 15 minutes by loudspeaker and then put phone into my pocket for 10 minutes (walk to take a bus).
When I took my phone back into my hand battery was dropped to 1%! (from over 95% to 1% in 10 minutes), but phone didn`t shut down.
This 1% remain for couple of hours (something like 2-3) without shutting phone down.
I took another charger and connected to it again - phone was charged to 100% in less than 30 min (usually takes up to 3hrs) and now works like before (no huge and weird battery drain).
Btw. I`m on faux kernel 007m.
Weird... looks like moto g doesn't like be connected to a PC by other cable than Motorola
Related
Hey all,
My wife and I both have Nexus S phones bought together sometime in Jan. Both phones are running stock Android 2.3.2, no rooting or anything done yet.
Right now her phone is behaving weirdly, while mine is perfectly normal. I suspect that her battery is messed up somehow, but I can't figure out what to do.
For the last day or so, when her phone hits <15% battery, the low battery warning pop-up appears.. and just keeps reappearing. No matter how many times the pop-up is acknowledged, the pop-up just does *not* go away until we connect the phone to a charger. Sort of an aggressive warning
This means that the phone won't let itself be put to sleep, keep the screen turned off or anything -- unless we connect the phone to a charger. I feel as though the battery is charging slowly, but I can't be sure.
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display. This behavior goes away if the phone is connected to the charger. My phone does not show this behaviour - display goes off the moment I press the power button, regardless of charging status.
Any thoughts?
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S? We removed the battery and put it back in (which is basically a soft reset apparently) and now it seems as though the battery has lost calibration or something. Have not done a hard reset yet -- should I go ahead and try that too?
Thoughts/help much appreciated. This is very worrisome!
satishev said:
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display.
Click to expand...
Click to collapse
Sounds like it has a glitch in the software. Try wiping everything. Go into settings, unmount the USB memory, erase the USB memory, then do a factory reset. That will reload the firmware back into active memory for the phone and wipe anything out of the USB memory that might be causing this issue. I usually do a factory reset with a new phone after I play with it for a while anyway, and it doesn't hurt the phone at all. You simply lose your texts, contacts, photos, etc. Just copy or backup anything you need to keep and wipe it clean.
If that doesn't fix it, then you need to get it replaced.
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S?
Click to expand...
Click to collapse
Once you do a factory reset, turn off the phone and fully charge it using the supplied AC charger (don't use the computer port to charge), unplug it and wait a minute then re-connect the charger again for another hour, unplug it, turn on the phone and start using it.
Let us know if the reset fixes the issue.
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
satishev said:
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
Click to expand...
Click to collapse
Well a factory reset is a lot easier and faster than a return/exchange and accomplishes the same thing.
A new symptom has just surfaced -- right now, when my wife tries to lock the phone, it locks the screen but won't switch off the display. No matter how many times the phone is restarted, or the lock button is pressed, the display never actually goes off (timeout has been varied from 15 secs to 1 minute, to no avail). Phone was completely charged as of today morning, so its not popping any low battery warnings.. just not switching off display.
It definitely seems like a battery/software glitch of some kind. We've not done the factory reset yet (she's at work, and this just started happening). Just thought I'd keep the thread updated.
I went ahead and factory reset the phone, as well as manually installed the 2.3.3 update. Figured between the system reset and the update, something should get fixed
Restoring settings was relatively painless (love how everything just gets set up the way it was due to backing up everything with Google). We have the phone charging now (overnight), will update again tomorrow morning once its full charged and my wife is using it as normal.
Fixed?
Hey @satishev
I have the exact same problem, did yours get fixed?
thanks
Hey crobbie, sorry I forgot to update the thread.
After factory reset and update to 2.3.3, the phone has been working normally (so far). All issues related to battery/display are gone! Looks like it was some kind of software glitch that was causing it to read battery state incorrectly (Another symptom I had noticed was that on alarm/dock mode it would keep flashing a charging icon, despite no charger being connected). Initially after reset, the battery usage was acting wonky, but that worked itself out and everything is showing what I expect.
If interested, a blog post summarizing process/ZIPs for all updates to date can be found here.
Thanks, bfksc for all your help
Hi,
Got my phone a week back..The problem started to occur a few days ago,my phone started to freeze often.Touchscreen stopped responding.I had to remove the battery n boot to get the phone working again.
I look forward to seeing your replies. Please feel free to ask me further details . Happy New Year.Thanks in advance
Have you tried calling the fone when this happens? I'm interested if this is the same problem as with mine....
I've also had the touchscreen freeze out a couple of times but that's usually after an app has crashed or I've stressed the system, I find that locking then unlocking the scren brings it back to life
KitsumiMaru said:
I've also had the touchscreen freeze out a couple of times but that's usually after an app has crashed or I've stressed the system, I find that locking then unlocking the scren brings it back to life
Click to expand...
Click to collapse
I don't want to be a negative person here but mine started like that, I though it was just because the system was running too many apps or I haven't freed the ram. It's now shutting off by itself.
I hope yours don't progress to my problem.
Such a nice fone but these problems make me think otherwise.
Have u found out any solutions .
Sent from my GT-I9103 using XDA App
alister214 said:
I don't want to be a negative person here but mine started like that, I though it was just because the system was running too many apps or I haven't freed the ram. It's now shutting off by itself.
I thought ^ was one of the GB's features. shuts down rogue or non responsive apps.
@venkatraman did u try factory reset??
take a backup from CWM if you havent already and make a reset from there...
Tell me if that works...if doesnt that clear all the Ram from Task Manager
Click to expand...
Click to collapse
dragonknight945 said:
alister214 said:
I don't want to be a negative person here but mine started like that, I though it was just because the system was running too many apps or I haven't freed the ram. It's now shutting off by itself.
I thought ^ was one of the GB's features. shuts down rogue or non responsive apps.
@venkatraman did u try factory reset??
take a backup from CWM if you havent already and make a reset from there...
Tell me if that works...if doesnt that clear all the Ram from Task Manager
Click to expand...
Click to collapse
I already factory reset by pressing vol up+power then middle button. The thing is, my problem is not really freezing screen but auto shutdown.
Click to expand...
Click to collapse
Factory reset didnt help either..It works for a while and the problem repeats all over again
A phone with this much memory and dual core CPU shouldn't behave like this.
sometimes when you move your finger to the screen as close as possible without touching though...it can cause freezings.
I had the same problem. Initially the phone used to freeze and I used to remove and replace the battery again. But then the phone started crashing and it reached a point today where the phone would freeze upon booting at Samsung screen. I held the VolumeUP+Home button while booting and did a "Wipe cache" and its been working fine since.
Cheers!
Yep, it seems a common issue. Mine does the same. I haven't flashed any custom ROMs or kernel after I got it from service just to see if it was the problem. But it started shutting down by itself a couple of days ago with increasing frequency. I removed all recently added apps + juice defender and others that may be messing with the hardware with no change.
P.S. I have to take out and replace the battery to restart it, and there is always a battery drain afterwards.
Hi,
After I did a 'wipe cache' in recovery, my phone didnt crash for one full day. Now again it has started crashing at random.
Kindly note that its been 2 months since i bought the phone and there were no problems with it.. But few days back there was not power and hence my mobile got switched off due to battery drain.. And from the next day onwards this problem has started.
Any of you guys think its a battery issue? - battery calibration issue perhaps? Should i perform a 'wipe battery stats' in recovery?
Kindly advice.
Thanks.
Didn't work for me, I wiped dalvik cache and battery stats and it worked fine for a couple of days, but then i shut down again. I'm going for factory reset next.
BTW mine shuts down only when the screen is off, never while I'm using it.
@reymysterio7 do you get battery drain after?
Yeah mate. There was significant battery drain. Right now I've done a factory reset-flashed 2.3.6 austria-flashed titanium v2.1-wipe cache/dalvik cache-wipe battery stats. Keeping my fingers crossed
Sent from my GT-I9103 using XDA
UPDATE : My phone started its random shut downs again. But one thing Ive figured for sure is that it happens only when the network signal is low or fluctuating.
reymysterio7 said:
Yeah mate. There was significant battery drain. Right now I've done a factory reset-flashed 2.3.6 austria-flashed titanium v2.1-wipe cache/dalvik cache-wipe battery stats. Keeping my fingers crossed
Sent from my GT-I9103 using XDA
UPDATE : My phone started its random shut downs again. But one thing Ive figured for sure is that it happens only when the network signal is low or fluctuating.
Click to expand...
Click to collapse
ru using Go launcher or Go Contacts because when I've installed these i was also having random shut down very rare once in 2 weeks now I've removed both of them and i am not having random shut down now..
---------- Post added at 08:54 AM ---------- Previous post was at 08:50 AM ----------
Metatrone said:
Didn't work for me, I wiped dalvik cache and battery stats and it worked fine for a couple of days, but then i shut down again. I'm going for factory reset next.
BTW mine shuts down only when the screen is off, never while I'm using it.
@reymysterio7 do you get battery drain after?
Click to expand...
Click to collapse
no need to clear the dalvik cache, just clear the cache and do factor rest it may help you and check the recent application which you have installed and remove them..
mj.vikram said:
ru using Go launcher or Go Contacts because when I've installed these i was also having random shut down very rare once in 2 weeks now I've removed both of them and i am not having random shut down now..
Click to expand...
Click to collapse
Yeah i was using go launcher.. Now ive formatted everything.. including usb memory... and flashed stock firmware I9103XWKI5.. Its as good as a new 1st day phone now... Even now if it shutsdown then its definitely not a software issue..
reymysterio7 said:
Yeah i was using go launcher.. Now ive formatted everything.. including usb memory... and flashed stock firmware I9103XWKI5.. Its as good as a new 1st day phone now... Even now if it shutsdown then its definitely not a software issue..
Click to expand...
Click to collapse
It shut down again - When signal became low!! - When i rebooted, again it shutdown while connecting to network. I removed sim and booted it worked fine. Then i went outdoors and booted with sim, it did not shutdown.
It definitely not a software issue coz I had formatted EVERYTHING and the phone was as good as new. Its not battery issue coz phone does not have issues without sim inserted. Its either hardware (motherboard probably) or SIM card problem.. I'm gonna get a new sim on monday and check it.. This sucks!!!
UPDATE : I tried with other sim - it still shutdown after 10 mins I used my present sim on a S2 and it worked fine...
UPDATE - ISSUE RESOLVED : I took it to the service center, the issue was a faulty USB connector. They replaced it and the issue seems to have been resolved. For more have a look at http://forum.xda-developers.com/showthread.php?p=24263158#post24263158
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.
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
---Edit---
I should note that I can have all the radios on when it is plugged in, I just can not have them on when unplugged right now.
mikeoconnor said:
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not?
If you're rooted/on a custom ROM, I would make a backup of all non-system apps and settings and try to start over. The fact that you dont get that when in recovery is the biggest indicator.
First, back up all NON-SYSTEM apps/settings with Titanium backup (or something similar).
Then follow my fix >>>HERE<<< and see if that helps
I am currently on CM-10-20130728-NIGHTLY, I should also note one thing I did try was to update the ROM yesterday AFTER the problem started (problem started at 4pm I updated the ROM at 7pm), it use to be CM-10-20130526-NIGHTLY. I will look at your link and see if that works.
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I hope you are wrong, but I fear you are right. But I am going to do the steps cited above and see if that helps, right now I am doing a second back up (first was Titanium backup, now is the CWRM backup) and I am going to do the flashing stuff who knows. Don't have much to loss, and I am still open to other ideas, if any one else has them.
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
That's a distinct possibility, but not the only cause for what he's experiencing. Jumping the gun and buying new hardware usually results in money spent on hardware that wasn't needed a good portion of the time.
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
mikeoconnor said:
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
Click to expand...
Click to collapse
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
jparnell8839 said:
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
Click to expand...
Click to collapse
It is white (indicating no water damage) also the other indicators on the phone are white. I hope you are right on that that would be sweet, I will stop by the tmo store before I head home tonight. And thanks for all the help (I now have to go back and "Thank" all the posts by you two, it is appreciated)
Funny part is I took the battery out to double check the sticker (even though I was sure it was still white) and the phone died even though it was still plugged in (so I guess I need both the battery and power plug for now)
mikeoconnor said:
It is white (indicating no water damage) also the other indicators on the phone are white.
Click to expand...
Click to collapse
you might get lucky and get a free one out of it. cant hurt to ask
Thanks all I picked up a new battery today and I looks like it is working. Sadly T-Mobile did not replace it for free but the phone is working again.
Sent from my Thrive using Tapatalk 2
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Cappelletti said:
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Click to expand...
Click to collapse
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Mr.Ak said:
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Click to expand...
Click to collapse
I'm fairly sure that there is no local shop that could check it.
Right now, before checking this thread, I let the battery completely drain and now it's on the wall recharging. I'll enter recovery when it's 100% charged and do a factory reset. Then install everything back and use it for a few hours.
Let's see it that helps.
Thanx for the reply.
- phone battery completely drained
- phone battery completely charged
- booted to recovery and factory reseted
- initial COS configuration done without any freeze and/or reboot
- updating Google Apps
So far, so good.
And it rebooted twice, during apps update.
Although it updated main Google apps, it was not supposed to reboot.
:/
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
iPusak Gaoq™ said:
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
Click to expand...
Click to collapse
It does not get stuck. At times, it reboots during boot. Some times (rarely) it does that for two or three times and then turns off. But most of the time it freezes, reboots and I can use it normally for hours and hours.
seanwlk said:
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
Click to expand...
Click to collapse
I'm "almost" fine with the way it works for me. As most of the time it's fully operational.
I found a OPO with damage screen for sale here. He guy didn't want too much $ for it. I bought it and will receive next week. Will try to swap logic boards.
Let's see what happens.
Was able to have logcat running when the device froze (during game) and rebooted.
Is anyone able to see any error on the log that could make the device freeze and reboot?
Got the broken screen OPO two days ago. Yesterday my phone was impossible to be used. Rebooting like hell.
I swapped logic boards and all is fine. No freezes and reboots (of course, it's pratically another phone). I kept only my screen, housing and battery.
My logic board had a 2.5 sticker on it. The one I got now has a 2.1 sticker. Does anyone know what's that about?