Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.
thenext1 said:
Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.
Click to expand...
Click to collapse
I have never experienced such a problem... So it just freezes while it sleeping? I have one idea but it's kind of stupid, there is an option under display, that says lock in pocket. Try unchecking that, I've had other people tell me that their phone freezes up afterwards...
You might have to do a warranty exchange.
Sent from my MB865 using xda premium
tmease1 said:
You might have to do a warranty exchange.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.
100-60 overnight is a bit on the high side for drain if you are not using the phone. I would do a warranty swap.
thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.
Click to expand...
Click to collapse
It's probably something to do with the CPU govener. Try rooting, install bootstrap, then flashing the deodexed version of 2.3.6 found here. Just be sure to flash as a backup by placing it in \sdcard\clockworkmod\backup\. Select restore in clockwork and it should be there.
See if that gets rid of the problem You don't mid rooting right
Yes I mind rooting! Sorry!
I was just seeking for your experience, to know if you did by chance notice this behaviour/glitch... you keep telling me to do an exchange but it's obvious it's not an option for me, as you can see from the flag under my user name. Otherwise I would have got me a new atrix already. (Because of other minor annoyances)
I once had an acer liquid that started getting nuclear-fusion-hot and discharged in 2 hours each time, without the software taking a hit. Now that was hardware related.
As to my atrix2, I am sure it's not hardware related, because it happens only sometimes and in certain circumstances. One time, I turned it off and back on 5 secs after and it was already frozen. No way, we're not talking of hardware fault here.
Thats major drain overnight! I leave my phone on overnight and generally get about 1% drain per hour.
Sent from my MB865 using XDA App
WTF, either I can't speak my mind, or you don't read my posts!
It's not that I get a 40% drain every night. In fact I got it only once, last night, when I decided to leave the phone in deep coma after I found it unresponsive after just a few minutes it was turned off and in airplane mode (the time of brushing teeth and coming back to bed, FYI). In that circumstance I got the 40% drain, but otherwise i get a normal 5% drain like yours.
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Thank you.
I have never heard of this happening on the A2.
When the phone freezes up, does it get hot at all? It's possible that your problem is hardware-related, but the only way to be sure of that is to make sure that it's not software-related...
It may possibly be one of the apps that you're using. If you're OK with it, then I highly recommend to begin with a hard reset. I write down all of the apps that I know I will need and then I reinstall them after the reset, then if I realize I need to use an app I don't have I install it.
Another thing to try is flashing the fxz. This will clear every single bit of data on your phone and reinstall stock 2.3.4. Then you can update to 2.3.6 and gradually regain your (necessary) apps as with the hard reset.
Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37
thenext1 said:
WTF, either I can't speak my mind, or you don't read my posts!
Click to expand...
Click to collapse
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night.
Click to expand...
Click to collapse
thenext1 said:
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Click to expand...
Click to collapse
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks
kirkgbr said:
Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37
Click to expand...
Click to collapse
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?
916x10 said:
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks
Click to expand...
Click to collapse
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!
thenext1 said:
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?
Click to expand...
Click to collapse
Not sure what fixed it. I have done a couple things since then.
1.) Rooted <- not sure how this could fix a problem like this.
2.) Froze several apps with Titanium Backup. <- This one makes the most sense.
I never use airplane mode.
The other user (dk-v1) says that his softkey lights come on while the screen stays black.
I don't remember about the lights, probably one time they turned on, but don't remember right now.
About the black screen, I'm not sure what he means, but mine stays black and with backlight off.
From reading the OP...I would suspect that it could be an app that is trying to sync while in airplane mode. I would try troubleshooting (uninstalling one by one to see if the problem goes away) apps that sync, preferably the ones you installed. But if it still persists do a factory reset and start over. Good luck man!!!
my wife actually started having this problem with her inspire recently. I tracked it down to the no led app she was using. deleted it and everything has been fine since. so your issues could most definitely be app related.
thenext1 said:
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!
Click to expand...
Click to collapse
I never said it was the primary issue......u said this thread wasnt about the draining issue, but since u brought it up in your op and subsequent posts its clear it was an issue so when somebody responds to one of the issues you're having, don't be a douchebag about it by saying "thats not what this thread is about". Trying to insult me by insenuating I don't read before I respond is no way to show appreciation for my attempt at helping you. It seemed you were under the impression that a 40% discharge overnight wasnt a major drain so I shared with you my experience thinking it would put yours into perspective.
But apparently explaining my thought process and posting your own quotes for you to see how/why I'd think what I thought isnt enough to knock you off your high horse so I'm over it, carry on. If you feel the need to respond any further you can pm me, no sense cluttering the thread any further.
Sent from my MB865 using XDA App
Related
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
What have you done to be getting random shutdowns? I've flashed multiple roms and used modded framework files and still I never get a random shutdown.
NeoXerO said:
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
Click to expand...
Click to collapse
Not bad. Wouldn't you want to have the convenience of NOT worrying about random shut downs (with or without) the app tho? I guess its just me, but those things would really irk me. lol
cappysw10 said:
What have you done to be getting random shutdowns? I've flashed multiple roms and used modded framework files and still I never get a random shutdown.
Click to expand...
Click to collapse
It's just pure luck. Some phones will randomly shutdown regardless what ROM you use. Some don't.
The only true solution so far is get a warranty replacement, or maybe couple replacements (the refurbs you get back may still suffer the same problem). Samsung itself has no clue what's the cause of it yet last time I checked.
NeoXerO said:
Hey everyone!
My problem with random shut-downs on the captivate became unbearable, and I kept searching through threads for a solution, and I finally found this:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
This app doesn't let your CPU completely turn off when on standby.
I used it for a whole day and no shut-downs.
Usually, I'd get at LEAST 3 shutdowns a day.
I hope this helped you all.
Click to expand...
Click to collapse
CKA is a possible solution for one of the anomalies that causes shutdowns. For additional information, use the forum's "Search" function and look for "Captivate Keep Alive."
i just starting to get shutdown once a day started 4 days ago. i trying to uninstall 1 app at a time to see what happen. just uninstall dolphin browser v4.0.
Jack45 said:
CKA is a possible solution for one of the anomalies that causes shutdowns. For additional information, use the forum's "Search" function and look for "Captivate Keep Alive."
Click to expand...
Click to collapse
Really? Well, this worked for me, and I had it pretty bad with those random shutdowns (even happened to me on stock 2.1 before flashing).
I think some people might be getting random shutdowns due to certain apps.
I 2nd that. I installed Keep Alive because my would shut down once a day after full charge but only if GPS is on. Mine doesn't shut down if GPS is off. Now it's been 3 days without any shut down and I leave GPS on continuously.
my phone shut down (1 time) daily, and i'm unable to reproduce the shutdown. maybe it' a memory leaks, it shuts down when it runs out of ram. going to reboot my phone (1 time) daily to see what happens...
NeoXerO said:
Really? Well, this worked for me, and I had it pretty bad with those random shutdowns (even happened to me on stock 2.1 before flashing).
I think some people might be getting random shutdowns due to certain apps.
Click to expand...
Click to collapse
I concur, I never had any shutdowns until I went to cog 7... And for the first week I didn't have any shutdowns, only after installing apps did this problem start. So I think you are correct that out has something to do with certain apps. Probably an app that is not fully compatable with android 2.2... I just wish I could figure out which app is causing this issue.
Sent from my SAMSUNG-SGH-I897 using XDA App
My phone keeps shutting off also. At first thought it was software, but even with a clean install of 2.1 with Odin and nothing added to it, it still did it. Then I thought it was the SD card, but still not it. I started noticing a pattern with it doing fine for 11-16 hours with a full charge depending on how much I used it, but it eventually shuts off. Every time I turned it back on, the battery is at <65%. I completely drained the battery last night and charged it back up and now it's doing it at 70%.
Anyone in this thread that has had at least 1 random shut down, or more, should look into a warranty replacement. A perfectly good working phone shouldn't shut down for the hell of it or because it "runs out of memory"
I went through this before and messed with the phone for a few days taking off apps, re-flashing etc... ultimately the problem went away when I simply just asked for a replacement unit.
Hello all,
I'm encountering a very unusual situation with my Captivate. I use my phone as my alarm clock, etc and I leave it charging overnight since that's, well, the most convenient time to leave it charging.
This weird trend developed over the last three nights; my phone would strangely shut down over night once it was fully charged. Now, what is even weirder is that when I wake up and notice it is off I can't even turn it back on by using the power button. I have to remove the back of the phone, remove the battery, re-insert and only then will my phone turn on. Over this time period I have not updated anything or made any changes to my phone's settings. It's just.... happened.... which is what I find to be very puzzling.
Any ideas? Thoughts?
Thanks!
This question has been posted a million times before. Please use search!
But regarding your question, that is a widely known problem for older captivates out there and your better off just getting a replacement from att.
Here is a huge thread just on that particular problem
http://forum.xda-developers.com/showthread.php?t=884289
noside12123 said:
This question has been posted a million times before. Please use search!
But regarding your question, that is a widely known problem for older captivates out there and your better off just getting a replacement from att.
Here is a huge thread just on that particular problem
http://forum.xda-developers.com/showthread.php?t=884289
Click to expand...
Click to collapse
Thanks,
Although my issue is that I am with Rogers in Canada and the day Robbers takes customer service seriously I'm going out and buying a lottery ticket!
The other problem too is that the only way to turn my phone on is to PULL THE BATTERY out first, I can't just turn it back on by hitting power.
I had Rogers replace mine for the random shutdown problem.
Sent from my SAMSUNG-SGH-I896 using XDA App
Download the app Load Monitor that app will keep it awake without really draining any battery, set it for monitoring, every 5 minutes....my phone use to shut down every at least 20 times a day or more, now never....
NewbDroid said:
The other problem too is that the only way to turn my phone on is to PULL THE BATTERY out first, I can't just turn it back on by hitting power.
Click to expand...
Click to collapse
Had the same problem with my random shutdowns. Replacement was the only fix.
NewbDroid said:
the day Robbers takes customer service seriously I'm going out and buying a lottery ticket!
Click to expand...
Click to collapse
Actually, Rogers is pretty good with replacements if your phone is under warranty, I had both my old HTC Dreams replaced without question due to a bad e911 update and the other due to the slide out keyboard being slightly misaligned when in the closed position.
Rogers isn't all that bad when compared to Bell and Telus, they're the better carrier of the 3 when it comes to customer service, even though people seem to hate on them a lot.
One thing I should probably clarify is that the shutdowns only happen when I am plugged in to the charger overnight. When I'm not plugged in my phone doesn't shutdown randomly, which is why I am so confused.
I do have Captivate Keep Alive installed but it does Nothing for when you're plugged in.
Ideas? Thank for everyone's help so far!
Sent from my SAMSUNG-SGH-I897 using XDA App
NewbDroid said:
One thing I should probably clarify is that the shutdowns only happen when I am plugged in to the charger overnight. When I'm not plugged in my phone doesn't shutdown randomly, which is why I am so confused.
I do have Captivate Keep Alive installed but it does Nothing for when you're plugged in.
Ideas? Thank for everyone's help so far!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I would get a replacement.
Hey guys. I'm trying VERY hard to understand this, but I can't make sense of it at all.
I'm coming to this phone from the MT4G and besides this one having a dual-core cpu and being made by LG...it's not TOO much different from that phone in terms of specs. However I am having horrible battery life. Like I've actually sat and watched the battery drain by 10% after only being on for 2min. And this was from a complete charge w/ phone being off.
So now I'm wondering if I've maybe done something wrong when I rooted my phone because no one else seems to be experiencing this at all.
I followed all of the steps located here:
http://forum.xda-developers.com/showthread.php?t=1054492
Following the set of directions for the installation of "CWM 4.0.0.2".
I'm also using the EaglesBlood v1.3 ROM located here (No other mods):
http://forum.xda-developers.com/showthread.php?t=1124522
Now I've made this post because last night, before I went to sleep, my phone was fully charged and so I took it off of the charger. At 2a.m. it was at 100%. At 8:30a.m. (6.5hrs later) I got woken up from my house phone. My phone was right by my head on my pillow and furiously hot. I attempted to turn it on, but it refused. I thought the phone burned out while I was sleeping, but when I plugged it into the charger...guess what showed the LG logo?
So how, in 6.5hrs, could this phone go from 100% to being dead WITHOUT use? Did I do something wrong with my root process? Was I supposed to do something else?
I've never experienced this kind of behavior from a phone ever. And I doubt that I need to be living on a charger with it either.
I rooted my phone recently...used NVflash and stuff...but I HAVENT loaded cm7 or anything on it...i have, however, loaded some launchers and customized my phone alot...so with all the launchers and custom screens running my phone does die quicker...but not at the rate you say yours does...have you tried resetting to stock system and the root it again?
Sent from my LG-P999 using XDA App
Psionicsin said:
Hey guys. I'm trying VERY hard to understand this, but I can't make sense of it at all.
I'm coming to this phone from the MT4G and besides this one having a dual-core cpu and being made by LG...it's not TOO much different from that phone in terms of specs. However I am having horrible battery life. Like I've actually sat and watched the battery drain by 10% after only being on for 2min. And this was from a complete charge w/ phone being off.
So now I'm wondering if I've maybe done something wrong when I rooted my phone because no one else seems to be experiencing this at all.
I followed all of the steps located here:
http://forum.xda-developers.com/showthread.php?t=1054492
Following the set of directions for the installation of "CWM 4.0.0.2".
I'm also using the EaglesBlood v1.3 ROM located here (No other mods):
http://forum.xda-developers.com/showthread.php?t=1124522
Now I've made this post because last night, before I went to sleep, my phone was fully charged and so I took it off of the charger. At 2a.m. it was at 100%. At 8:30a.m. (6.5hrs later) I got woken up from my house phone. My phone was right by my head on my pillow and furiously hot. I attempted to turn it on, but it refused. I thought the phone burned out while I was sleeping, but when I plugged it into the charger...guess what showed the LG logo?
So how, in 6.5hrs, could this phone go from 100% to being dead WITHOUT use? Did I do something wrong with my root process? Was I supposed to do something else?
I've never experienced this kind of behavior from a phone ever. And I doubt that I need to be living on a charger with it either.
Click to expand...
Click to collapse
No....this phone does have higher usage rates that the phone you come from. But, it should not be as bad as you indicate.
Check on this forum for threads about Batteries....there are indications that some bad batteries are in play here. You may want to follow up with TMobile to replace your battery. Some have invested in OEM batteries and gotten more steady battery performance.
You may also wish to try some factory resets with your device, just to seeif your performance may change. You may find some relief there.
If nothing works, you may wish to do some application management and see what is using your battery. Work with the settings on those apps to make sure they are constantly checking for data. Another common battery drain is signal. If you're in a weak 4g area, try setting to 2g for a day or 2, to see if that helps.
The programs others mention like setcpu, might be ok. But, speaking only for myself, have not been able to figure out how they work, and explanations here, are over my head. So I choose to not use them until I better understand them.
With a stock setup, you should see better battery life. Having to change roms, to achieve that....indicates there is something wrong.
Ok guys let's see you work that voodoo that you do so well...
I got the idea to come here when someone of a T-Mobile support forum for Samsung Galaxy S 4G said they gave up on getting any help from those people but the guys from XDA were great and her phone has worked right since speaking with them. So here I am.
I own a Samsung Galaxy S4 G since July 2011, no real issues at all aside from a few random freeze ups from various programs. Well, a few days ago it starts turning itself off randomly. Sometimes it turns itself back on when I press the on button, sometimes I have to plug it back in, sometimes it says the battery is way less than it was right before it shut itself off. So I do what any savvy computer person does that's still a noob at anything technical- I learn how to reset the phone to its factory settings, delete all data and start fresh, figuring I had some bug in the system. This did nothing to help.
So I go online and discover all these different web forums with people complaining about the same problem. They all say the same thing, update the phone, don't update the phone, reboot, don't reboot, nothing fixes it. I even considered there being the "impossibility" of a loose battery connection and cut a thin strip of a business card to shove between the phone base to push the connection end tighter together.
The only place on any forum that anyone seemed to find an answer, albeit the answer was not discussed, mentioned coming here.
I apologize in advance if I don't immediately understand any technical details people may offer up as help, but please please please if anyone has an idea of how to fix this issue let me know.
Thanks in advance to everyone for their thoughts or suggestions :cyclops:
Sounds like it might be your battery. Have you tried switching batteries?
Sent from my SGH-T959V using xda app-developers app
that could be it I remember when I had the g1 and it was doing that it wouldn't charge and it wouldn't stay on
Sent from my SGH-T959V using xda premium
HolyGhostBoy1 said:
that could be it I remember when I had the g1 and it was doing that it wouldn't charge and it wouldn't stay on
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
My g1 did the same thing, after I swapped the battery it stopped.
Sent from my SGH-T959V using xda app-developers app
pisherthefisher said:
My g1 did the same thing, after I swapped the battery it stopped.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
yeah mine did that too new battery helped... my my touch also had a problem with the battery staying in place; so try the business card trick and leave your phone on a flat surface with no movement and for a day without charging... Don't blow money on the battery if you aren't sure, unless you've wanted a backup battery anyway.
one more thing
Good ideas so far...
One more thing, I've noticed the few times today its lasted for awhile and then I go to show someone something on youtube, it will play part of the video like 30 secs or so and then 'blip' we're back to automatic shut down again. Does this spark any different ideas?
another interesting discovery
oldandronicus said:
Good ideas so far...
One more thing, I've noticed the few times today its lasted for awhile and then I go to show someone something on youtube, it will play part of the video like 30 secs or so and then 'blip' we're back to automatic shut down again. Does this spark any different ideas?
Click to expand...
Click to collapse
Ok so I mentioned before about the 30 secs of video and then dead right? Based on the theories so far, which I'm also leaning towards and praying is correct, I ordered a new battery, won't be here for 3-5 days, but I decided to test an idea...
I thought perhaps if its the battery, if I plugged in the charger, things that kept shutting me down should 'in theory' continue to work.
So I plugged it in and tried to watch the same video 'Cat man do' again and see if it died in the same place it had done 3 or 4 times before or if it would work on through. And guess what, it played through the whole video, no random shut downs.
So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link.
Still happy to hear any other ideas, but as soon as I get and test the new battery I will repost on here and let you guys know if that did the trick.
Thanks again so much!
oldandronicus said:
Ok so I mentioned before about the 30 secs of video and then dead right? Based on the theories so far, which I'm also leaning towards and praying is correct, I ordered a new battery, won't be here for 3-5 days, but I decided to test an idea...
I thought perhaps if its the battery, if I plugged in the charger, things that kept shutting me down should 'in theory' continue to work.
So I plugged it in and tried to watch the same video 'Cat man do' again and see if it died in the same place it had done 3 or 4 times before or if it would work on through. And guess what, it played through the whole video, no random shut downs.
So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link.
Still happy to hear any other ideas, but as soon as I get and test the new battery I will repost on here and let you guys know if that did the trick.
Thanks again so much!
Click to expand...
Click to collapse
I would also suspect the sdcard. Have you tried another sdcard?
bhundven said:
I would also suspect the sdcard. Have you tried another sdcard?
Click to expand...
Click to collapse
Hadn't thought of that. Sure hope not though, been using this 32 gig sdcard since a week after I bought it and haven't experienced any issues with it during that whole year. Do you suspect anything on the sd card or just the card itself, just in case this battery issue isn't the culprit.
Sdcards go bad from time to time. Even get brand new ones that are flaky. When was the last time you reformatted it and started fresh.
eollie said:
When was the last time you reformatted it and started fresh.
Click to expand...
Click to collapse
Don't forget to backup first
eollie said:
Sdcards go bad from time to time. Even get brand new ones that are flaky. When was the last time you reformatted it and started fresh.
Click to expand...
Click to collapse
Reformatting the sd card itself? Never, hadn't even thought of it, nor ever learned how. Certainly happy to try it you have a couple of quick step instructions.
Again, apologies for being such a noob, but I love learning more to help for the future so all this info is great.
oldandronicus said:
Reformatting the sd card itself? Never, hadn't even thought of it, nor ever learned how. Certainly happy to try it you have a couple of quick step instructions.
Again, apologies for being such a noob, but I love learning more to help for the future so all this info is great.
Click to expand...
Click to collapse
First back up your sdcard. Copy all of its contents to your computer.
I do this every now and then, because if my phone eats my sdcard, I keep all my pics and music.
Second, reboot to recovery: Advanced -> Partition sdcard
It should then ask about ext partition size and swap partition size. I usually set ext partition to 2048 and swap to 0. We don't use swap. ext is the sd-ext partition, but iirc, recoveries with voodoo lagfix will use that to backup partitions it is converting. It has to be 2048 or it will fail. Unless you will never use older voodoo lagfix (which none of my roms/kernels do) you can use any size you wish.
Repartitioning sdcard can take a while, so be patient.
"So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link. "
I am 110% sure its your battery. Same exact thing happened to me battery was swollen and it kept randomly shutting off whenever I used internet based apps. I ordered a new factory Galaxy s 4g battery from amazon for about $8 popped it in and it stopped shutting off and battery life was actually way better. I suspect the swollen battery is caused by stuffing the business cards in the battery compartment.
oldandronicus said:
Reformatting the sd card itself? Never, hadn't even thought of it, nor ever learned how. Certainly happy to try it you have a couple of quick step instructions.
Again, apologies for being such a noob, but I love learning more to help for the future so all this info is great.
Click to expand...
Click to collapse
Hey, sorry to revive a dead thread but did getting the new battery work for you or not? I am having the exact problem that you described with my Galaxy S. I would love to hear how it turned out for you.
tyrst5544 said:
Hey, sorry to revive a dead thread but did getting the new battery work for you or not? I am having the exact problem that you described with my Galaxy S. I would love to hear how it turned out for you.
Click to expand...
Click to collapse
I had the very same issue 2 months ago, and it was the battery. I think the telltale sign of what is happening is that when your phone reboots, it has gone from almost a full charge to just a few percent. The issue as I understand it is that basically, when higher processing loads are being placed on the battery by the phone, at some point, it cannot provide the level of requested power, at which point, your phone believes the battery has died, and shuts down.
I swapped the SGS4G stock battery (1650 mAh) for the Anker 1800 mAh battery, and had great success and no issues. Best part is, you can buy 2 of them (which includes a wall charger as well) for $20 bucks on Amazon. http://www.amazon.com/Anker-Batteri...2126170&sr=8-2-spell&keywords=anker+1800+s4+g (Free 2 Day shipping if you have Prime) Things are almost disposable at that price, but the Ankers have worked great, and not had the reboot issue since.
oldandronicus said:
So I believe this might go a long way to proving your theories on the battery are correct, also the battery itself seems to be slightly swollen through the middle, which could cause a host of different issues, not the least of which would be slightly changing its size and therefore its connection to the power cup link.
Click to expand...
Click to collapse
And for the record, ANYtime your battery ends up swollen and distorted, you can guarantee that it's on its way out. At work a few years ago, had an issue where we were supposed to support PDAs and their battery life went down to seconds rather than the days they were supposed to last. Turns out their cells were swollen, sometimes enough to actually distort the back of their case. Replace the battery pack and get back to normal life. Without exploding batteries.
Random news story from 4 years ago with swollen battery pictures:
http://www.engadget.com/2009/01/28/sony-ericssons-bst-33-li-polymer-batteries-swelling-into-a-laws/
Great- thanks for the advice. Glad to hear from a few others as well that this should take care of the problem.
ariesgodofwar said:
I swapped the SGS4G stock battery (1650 mAh) for the Anker 1800 mAh battery, and had great success and no issues. Best part is, you can buy 2 of them (which includes a wall charger as well) for $20 bucks on Amazon. http://www.amazon.com/Anker-Batteri...2126170&sr=8-2-spell&keywords=anker+1800+s4+g (Free 2 Day shipping if you have Prime) Things are almost disposable at that price, but the Ankers have worked great, and not had the reboot issue since.
Click to expand...
Click to collapse
Wow what a deal..
Just ordered mine Free Shipping..
Great find Thanks for the link..
Sent from my SGH-T959V using xda premium
My God. I remember my g1. A new battery did not help its situation. I would charge, within 20 minutes, dead.
Sent from my SGH-T959V using xda premium
First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.
Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.
hollovoid said:
Sounds like there is an issue with your phone man, If you have already done FDR n whatnot and it still behaves the same, then not sure what else you could do to rectify that. If you have insurance on it you could put in a claim, it would cost money, but not as much as getting another phone.
Id say at this point though, why not unlock, root, try other roms, whatever. If for some reason it clears up running something else, then great! If not then you haven't lost anything but the time spent doing it. Id go for the 4.1.2 roms If you do, since they will have everything functioning, 4.2 roms are nice but not everything works yet (camcorder, HDR photos, voice search/transcribing, GPS issues, etc.)
I agree on the moto employees being lazy, they have 3 solutions to everything, FDR, reboot, FDR a ton of times in a row, its kind of insulting when they do that even after you say you already did it. "Hey I got a problem, I FDR, cleared this, rebooted, etc" - me "Did you FDR, clear that, reboot, etc??? Mine runs fine, must be something you did!" - Moto guy
Either way, let us know how it goes, and good luck, hope your issue gets resolved.
Click to expand...
Click to collapse
To put it simply, if there's ANY way I can determine if it's a software issue, I'd like to try it. A phone this expensive really has no excuse to have a hardware issue. I've heard the SIM reader can sometimes cause system problems, so I'll try blowing in the slot like an old N64 cartridge and seeing if maybe it misreads while charging and shuts off because of a speck of dust, or something ridiculous like that..
greydelta38 said:
Would it be worth reflashing the stock Motoblur 4.1.2? I used to run CM10 on the old GNexus, I'd love to use that again on my HD, if it's available.
As for a new phone, if need be, my upgrade happens to be right after the GS4 is released on Verizon so I might as well get that and then not have to worry about F-ing up my primary phone. I'm a little wary of rooting whatever my primary device is, because I've bricked a Bionic with a stupid mistake I made when I was new to Android.
Click to expand...
Click to collapse
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.
hollovoid said:
You could try reflashing the stock rom, and there is a couple CM10 unofficial builds floating around in the roms section. Of course there is always risk in doing anything, but they have a pretty good method for rooting/unlocking, so id say if you feel up to it, go for it.
Click to expand...
Click to collapse
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.
greydelta38 said:
I changed that post after I found a little more info, btw.
I usually don't go for unofficial. The only 10.1 I could find was a 4.2 but call audio, camera, nfc, and wifi weren't working. I wish they had a timeframe on an official release. Moto phones never have enough support.
Click to expand...
Click to collapse
At this point, all CM builds are unofficial. All 10.1 builds are 4.2, 10.0 is 4.1. We are only going to get official when a proper kernel is ready and we have full functionality. 10.0 should have most everything working though, as the official moto builds are on 4.1.2. It does suck, Imagine if moto had never developed that ridiculous bootloader of theirs, we would be in great shape! But it is getting better, just everybody is starting from scratch now that its unlocked, so the pace seems slow.
If you don't mind the camcorder not working, the AOKP and Xenon HD builds are pretty awesome for 4.2. Best way to try them out is to put TWRP on and backup your stock, then you can switch between roms very easily and see if anything improves. The other recoveries should work the same as well, but ive only had experience with TWRP on this phone, and it works very well.
greydelta38 said:
First of all, I'm happy to be a part of the site now. I'm not new to Android in any way, but have only decided to join a forum because Motorola tech is no help at all, and I can't figure it out on my own.
So here's the story. When I plug my Maxx HD in at night, it functions perfectly, and seems normal. Normal temperature and charge rate. Let's say for example it was at 50% when I plugged it in just before I went to bed at midnight or so. But when I wake up in the morning, the phone is powered off and doesn't register as charging. I unplug it, and it won't power up regularly, so most of the time I have to soft reset just to get the screen on. When it boots up, it runs smoothly like nothing happened. The battery is usually 5% or 10% higher than it was when I plugged it in many hours ago, so it's safe to assume it locks up and shuts down fairly quickly after I fall asleep. I have yet to be able to recreate this problem while I am awake. I have tried disabling, reenabling, and uninstalling just about everything, and the problem doesn't seem to relate to anything in the software. The curious thing is that this problem does not occur regularly. Sometimes, it will happen 3 nights in a row. Other times, it won't happen for a week.
A side effect of this, it seems, is that when it does decide to hold a charge, it will run from 100% to 90% and hold there for an hour or so, no matter how lightly or heavily I use it. Then, out of the blue, it will drop to around 60% or 70%, and the rest of the day will drop at a regular rate.
I've been searching for a solution for this problem for weeks and haven't found a valid answer other than "use a Motorola charger" "get a new phone" the always relevant "Have you tried an FDR?", and the typical answers from a bored Motorola employee about whether I've turned the phone off and on again.
To reply to those answers, yes, I've used a regular Motorola charger, Verizon's most powerful and expensive speed charger, and even the cheapest charger I can find and it still shuts off and won't charge no matter the charger. I currently use the Verizon charger because it is the most convenient and fastest charging.
No, I can't return it because the RMHD was a trade. I don't have the receipt of any documentation of the purchase. I had an S3 that I disliked because, let's be honest, Touchwiz is intrusive and irritating at times, and I was too lazy to try and find a working rom for it. I cold traded some guy that lived near me for his RMHD, phone for phone. No chargers, no receipts. just straight up trade. His still had the plastic on the screen, and he claimed he changed his mind about it as soon as he took it out of the box and thought it was too thick, and wanted an S3.
As for the FDR, yes I've done that 4 or 5 times now with no change.
So my question is, is this a hardware problem or a problem with the battery sensor? I'm tempted to say that the battery sensor is defective and protects the phone from overheat by shutting it down even when it's at normal temperature and won't take any more charge. But if that was the case, why doesn't it happen every night? Any help is appreciated, and I'm prepared to hear someone say "suck it up until the S4 or the Motorola X is released". Thanks for your help, and if I need to root my precious HD to fix it, I'm prepared to do so.
Click to expand...
Click to collapse
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD
jfriend33 said:
You could always ask Verizon and see if it's under warranty. These phones aren't a year old yet if I am correct. Rooting your device is not the best idea because it technically can void your warranty.
Keep calling. Email Motorola support. Contact your carriers Cs. Or just sell the thing on ebay.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
As I said in my post, I don't have a warranty, and I don't particularly care about a warranty. Motorola CS is pretty awful, they're all bored and don't really give a crap about your problems, unlike the friendly and caring service I've gotten from Samsung before. I don't want to sell it, seeing as how the RMHD is arguably the best phone on the market for the time being.
UPDATE: I uninstalled a RAM booster called Memory Booster - RAM Optimizer a few days ago, and have yet to have a charging problem. I had the booster set to auto clean the system garbage when the screen was off. I'm making an educated guess here, but I'd be tempted to say that it was killing one of the Android processes that keeps the phone awake while charging, and it would bug out and crash.
Long story short, if you're having a problem with an HD shutting down overnight, UNINSTALL ANY APP KILLERS, TASKERS, OR RAM BOOSTERS.
Hope this works.
Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app
greydelta38 said:
Okay, so I thought I was in the clear. I was wrong. It definitely is less frequent, but my RMHD still continues to totally die every night. I've determined that it's definitely NOT a hardware problem. I'm convinced that it may be overheating at night and Android shuts it down for safety, and somehow locks it up in the process. Last night, I went to sleep with 20% battery, and plugged in. This morning it was totally dead and would only respond to a soft reset, booting into recovery, where I prompted a reboot. It started fine, showing 44% battery.
What the hell is going on? I went so far as to reflash Motoblur, and I tried Eclipse 4.1.2 and still had the same problem. Is it maybe an app that is hostile? Someone has to know how to fix this huge annoyance.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2
Yeah sounds like hardware.
Sent from my XT926 using xda app-developers app
scoobaspeaz said:
Not hardware but it gets hot and shuts down? Sounds like hardware to me.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
It's not hardware. I reflashed stock 4.1 AGAIN, and have yet to have it screw up. It's been about a week and a half since. Motorola sent me a new charger just in case. I know you guys think it's hardware but for some reason I'm totally convinced that it was an app screwing with Android. I guess I'll find out sooner or later. Thanks for the feedback.
Sent from my Galaxy S4 using xda app-developers app