Database Info

[Q] Help - weird battery issues with Nexus S!

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

Phone shuts off all the time

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.

[Q] Phone restarts randomly

Hi! Sorry if this was posted in the wrong forum, im new here :laugh:
I installed Fallout V 4.3.0 on my HTC DS and everything was working fine. But then suddenly my phone started to restart randomly. 1-2 minutes after booting it restarts again. If i take out the battery, wait 1 minute, and the put i back in the phone starts automatically again. Then another 1-2 minutes before restart loop.
This does not happen when the charger is plugged in. First thing i thought was a battery-issue, but this happened after flashing a ROM, so?
The phone was working fine on Fallout V 4.0.0, problem occured when updating.
-I wiped everything before installing the ROM.
-Have tried to reinstall Fallout, same problem
-Have tried to install Endimyon, same problem.
Information about the phone:
Current ROM: [Endymion V3.5|Sense 3.5|GB 2.3.5][kernel V2.2|ControlCenter]
Hboot: 6.98.1002
Radio: Default
S-off
Would appreciate some help, as my phone is useless atm! :crying:

Hello,
Maybe this should be posted in the Fallout thread (however you have to make 10 posts before being able to post in the dev section...). Up to the moderators to move your thread or not
I have had some similar issues after flashing Fallout, except my phone didnt reboot but it just went off a couple of minutes after i tuned it on. Although this just seemed to happen once. After I turned it on again, everything ok until I charged it to 100%, turned it on again - and same issue.
I then flashed CM9, same issue.
I read somewhere that it might be a charge level display issue : when you plug the phone in charge and unplug it right away, battery indicator will say it is charged to 100% - while obviously it is not...
Hope that will help you.

nuts77 said:
Hello,
Maybe this should be posted in the Fallout thread (however you have to make 10 posts before being able to post in the dev section...). Up to the moderators to move your thread or not
I have had some similar issues after flashing Fallout, except my phone didnt reboot but it just went off a couple of minutes after i tuned it on. Although this just seemed to happen once. After I turned it on again, everything ok until I charged it to 100%, turned it on again - and same issue.
I then flashed CM9, same issue.
I read somewhere that it might be a charge level display issue : when you plug the phone in charge and unplug it right away, battery indicator will say it is charged to 100% - while obviously it is not...
Hope that will help you.
Click to expand...
Click to collapse
Thanks for replying! Was going to post in the dev section indeed, but i dont have 10 posts... But i found out, if i turn on "screen always on" setting, the phone does not restart. Hmm...

superlorre said:
Thanks for replying! Was going to post in the dev section indeed, but i dont have 10 posts... But i found out, if i turn on "screen always on" setting, the phone does not restart. Hmm...
Click to expand...
Click to collapse
have you try a reflash

zerokoolmyth said:
have you try a reflash
Click to expand...
Click to collapse
Yes. Do you think buying a new battery will do the trick?

Time for the really stupid question - but it is the old one and has been a problem for many people (including me).
Have you tried to insert a piece of paper, folded so it is 3 or 4 sheets thick, in between the battery and the back of the phone when you insert it? There is a manufacturing tolerance which can cause the battery to move and lose connection to the contacts sometimes.
It's probably not the solution for you, but it's a damn sight cheaper than buying a new battery immediately.

SimonTS said:
Time for the really stupid question - but it is the old one and has been a problem for many people (including me).
Have you tried to insert a piece of paper, folded so it is 3 or 4 sheets thick, in between the battery and the back of the phone when you insert it? There is a manufacturing tolerance which can cause the battery to move and lose connection to the contacts sometimes.
It's probably not the solution for you, but it's a damn sight cheaper than buying a new battery immediately.
Click to expand...
Click to collapse
Thanks for answering, but i've tried that... The weird thing is that if i turn on the setting "screen always on", the phone does not restart. Or if the charger is plugged in. It only restarts some seconds after the screen goes black (inactivity) or if i press the power button.

Sadly I don't have an answer for you, however, I wanted to recommend that you avoid taking your battery out as that can cause damage to the emmc chip and thus brick your phone
Sent from my Desire S using xda app-developers app

mzr92 said:
Sadly I don't have an answer for you, however, I wanted to recommend that you avoid taking your battery out as that can cause damage to the emmc chip and thus brick your phone
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the warning, but i really dont care about the emmc chip now You see, if the battery is in the phone starts itself automatically...

I would have to say it's the rom. Did you back it up?
Sent from my Nexus S 4G using Tapatalk 2

PROPAIN2112 said:
I would have to say it's the rom. Did you back it up?
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Have wiped everything, reflashed Fallout ROM, didnt work. Wiped everything, restored NANDROID backup to Endimyon, didnt work either...

superlorre said:
Thanks for answering, but i've tried that... The weird thing is that if i turn on the setting "screen always on", the phone does not restart. Or if the charger is plugged in. It only restarts some seconds after the screen goes black (inactivity) or if i press the power button.
Click to expand...
Click to collapse
Don't worry about the eMMC chip that the other poster mentioned - the problem is not caused by removing your battery - it is caused by not removing it properly, or by removing and reconnecting it quickly which means there is still residual charge when it reconnects.
Given the more detailed description, I assume you have a custom ROM running? If so then try two things
1) Try to decrease the under-voltage settings by 50mV
2) Increase the minimum CPU speed.
It sounds like the phone is going to sleep, but is slowed down too much and a reboot is forced.
Sent from using the power of my mind.

SimonTS said:
Don't worry about the eMMC chip that the other poster mentioned - the problem is not caused by removing your battery - it is caused by not removing it properly, or by removing and reconnecting it quickly which means there is still residual charge when it reconnects.
Given the more detailed description, I assume you have a custom ROM running? If so then try two things
1) Try to decrease the under-voltage settings by 50mV
2) Increase the minimum CPU speed.
It sounds like the phone is going to sleep, but is slowed down too much and a reboot is forced.
Sent from using the power of my mind.
Click to expand...
Click to collapse
Tried your suggestion, but no luck. Will buying a new battery give me any chance?

It might do. I would be tempted to find a phone shop and ask them if you can test your phone with a battery from them before buying it though - just in case it is something else causing this.
Sent from <redacted in the interests of global security> using the power of my mind.

Hy Guys!
My DS is doing the same thing after I istalled the ICE DS 5.1. Funny thing is it started only after 1 day. It was working perfectly until it restarted after pressing the power button. I've tried different ROMs (CM 7.2; Fallout 5) but it happend almost instantly. Also tried the CPU voltage, no result.
I'm curious superlorre if the new battery did the trick?
Or is there a thread I missed where the problem got solved?
Thanks in advance.

Awkward freezes

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

Battery?

So I just picked up this s3, it will turn on but shuts off halfway through galaxy splash screen. Boots into recovery and Odin mode just fine, prior to purchasing we plugged it in, got it to boot and did a factory reset, to clear privious owners data, and it went fine, did it reboot and took me to setup. Satisfied with its performance I went ahead and made the purchase, upon unplugging it shut off, as I expected if battery was indeed shot. What gets me is I let it charge, unplugged, booted, shut off at splash screen, plug back in and says its still fully charged. Boot into recovery and indeed, 100% battery. I haven't gotten around to flashing twrp or rooting, was wondering if anyone has experienced this?
Sent from my HTC Desire HD using XDA Free mobile app

Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.

Phone was already on 4.4 when I got it, I downloaded and flashed stock firmware (ne1) via odin, I got the whole way to the end of setup and as soon as it started loading the homescreen it cut off and went to the green battery charge icon when phones off. Everytime I try and boot it, she'll go through all the splash screens and ill catch a very short glimpse of the homescreen and it shuts off. Also it HAS to be plugged in still, or else it just shuts off halfway through initial "galaxy s3" splash.. I don't understand...

Have you tried a new battery? Even if it's plugged in it won't run if the battery is completely shot.
Also if you indeed have a Verizon S3 on NE1 firmware you will not be able to install TWRP as the bootloader is locked. You will be able to root, however.

Muhff said:
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Click to expand...
Click to collapse
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app

XdrummerXboy said:
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.

Muhff said:
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Click to expand...
Click to collapse
I'm glad you fixed the problem!
Sent from my SCH-I535 using XDA Free mobile app