Related
My sensation has a very bad habit and I would like to ask you guys if you know why it is happening..
My phone shuts down about once a day and then when it is turned back on the battery has dropped about 20 - 35 %.
I have taken few screen shoots of the battery level and they are attached with this thread.
Im not using any other ROMs or anything like that. I have taken about Juice Defender which I used for about 2 weeks.
I know three others Sensation users and they have never experienced something like this.
I have asked the sales people and the technical people and they have no idea and say that this is prob some app that I have put on but I havent put anything on it that can mess this up.
Any solutions ?????
wow, I've never seen any android phone do that, have you tried restoring to factory settings and then trying it out?
It could also be something HTC needs to fix on your particular phone, so I might contact them about it.
First I wanted to ask if someone knows the answer to this but if I dont get any answers I will do that and see what will happen.
Try uninstall juice defender. I had it last time for 3 days. Nothing it do unless harm my mobile data 3G connection connect & disconnect & battery life goes crazy up & down!!
Sent from my HTC Sensation Z710e using XDA App
juice defender is not for gingerbread devices
yeah i agree i think your best bet would be to uninstall any apps that have to do with the battery and see what that does.
if that doesnt work restore it
I have uninstalled everything and i did that before all the images that I attached above. I have over 10 pic like the once above.
Thanks for the advice I will wait a little bit longer before restoring it.
Does it a shut down or a restart?
if it shuts down, so that you must press the power button to turn it on again, it's the same problem i had, and maybe still having...
This problem became stronger and stronger (did shut down 4-5 times a day at the end, but always with "low" battery, <65%)
I've returned my device to HTC and they sent it back with no failures found
after 3 days the problem appeared again. Then i bought a new battery (a original one), since then phone didn't shut down except one time, but that could have been the new kernel i flashed . So I'm very confidently that this was the failure.
My phone shuts of and does not restart. So I guess it might be the same fault as you had.
Yes I would take it back and demand for a new one or you can contact HTC and they will charge oh about $250. But first contact tmo customer service first and see if they will replace it with a new one that way you won't have to pay $250 to htc . Your sensation shouldn't be rebooting on its own oh by the way make sure you demand a replacement they may try to get get out of it good luck
Sent from my HTC Sensation 4G using XDA App
I had the same problem, I recalibrated the battery 3 times one after another (is it english? lol). The problem has improved but continued.
So I tried that [MOD] Battery jumping and accurate reading Fix 2.3.x.
Since I had the problem that 2 or 3 times in 2 weeks.
If I buy a new battery does it will fix it?
(Sorry for my bad english!)
I have the same problem too. I tried everything. I tried factory reset , flashing new roms, talking with htc but i cant fix this. It still randomly turns off. I think only new battery can solve this. One guy said that he buys new battery and 1 month passed still have no problem. So i ordered anker battery. I hope new battery solve this...
I have a theory here.
Difference kernel will give difference control and usage of current and voltage signal. Therefore if you are using wrong kernel for a long time, maybe it will damage the hw especially small small ic which very sensitive and cause it to malfuction which cause shutdown or restart and in the end burn etc.
Just my 2 cent and please ignore me if im wrong.
Sent from my HTC Sensation Z710e using XDA App
phone stutting down
Ok now your talking what kernel are you useing I'm useing a faux kernel v2.6.35.14-bricked -v1.2-gpuoc [email protected]#6 and lve had know problem's fast smooth you should check it out you can't go wrong with a faux kernel
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
Okay, so yesterday, my friend comes to me saying his Nexus S (Sprint) just randomly quit working for no reason. And then his phone is totally stock, no root, no bootloader unlock, and no custom recovery. So I go home, plug this Nexus S into the charger, but the screen remained blank. I unhooked it from the charger, then decided to plug it into the computer. The computer made no sound, did nothing at all. I tried all possible key combos in existence. The only thing the Nexus did was to become warm. I furthermore researched about this issue all over Google, and I've found plentiful Nexus S users report that their Nexus S quit and won't give any sign of life this month. Today, ANOTHER friend came to me, but this time, it was because he forgot the pattern lock to his Nexus S (Sprint). No biggie. I just went into the recovery, and wiped data (since he also forgot his Google account). I wanted to use this Nexus to see if I can diagnose the other Nexus. So in my hands, I hold 2 Neuses. One bricked HARD. The other healthy and free. I just want to confirm, there IS AN ISSUE W/ OUR NEXUSES that makes them die, and we have to figure out what is causing this to happen. We need a solution. I need other Nexus S users to confirm this issue by commenting within this thread.
Just the past couple days my Nexus S has been on the fritz. I've always been able to overlock/underclock, but now if I touch the clock settings, it reboots. I cant even set the max frequency to 800mhz any more. I've tried nearly every rom and kernel and I believe its the just the hardware finally degrading. Also the responsiveness of the device is hugely slower than when I first purchased the it, I have to wait about 10 seconds after unlocking the screen to be able to do anything, and Im on completely stock now.
Really hoping for a good nexus phone to come out this year.
Looks like there are some design flaws with this device like the power button. Not sure there are any solution beside using your warranty if you have one and buying a different phone.
Sent from my SGH-T959
eksasol said:
Looks like there are some design flaws with this device like the power button. Not sure are are any solution beside usjng your warrenty if you have one and buying a different phone.
Sent from my SGH-T959
Click to expand...
Click to collapse
Agree with you there. I don't believe there's a point trying to look why exactly some Nexus S die. It's specialized electronics and without the knowledge you could pretty much be poking your finger at everything and nothing for the rest of your life. And even if you find out the issue, doesn't mean you can fix it yourself... :/
Easier to just send it for repair and be done with it.
Edit: When I first got my Nexus I sent it for repair to Samsung. Came back with "BGA failure" on the work sheet. Bad soldering? Who knows.
Maybe, maybe its the CPU, this thing cannget hot sometimes. Maybe a contact messes up. Samsung is notorious for good hardware just dieing.
Sent from my A100 using Tapatalk 2
I am somewhat of a n00b when it comes to android phones. I have had my maxx for about a month. Installed the leaked JB version and everything was working fine.
Today I decide to go back to 4.0.4 with the utility and something went wrong. I am stuck in a AP Flashboot loop. It sucks. I have tried everything....at least what I think is everything.
I have tried multiple utilities and RSD lite, etc. with no success.
Am I missing something?
Thank you!
Have you had any success yet?
projekt8e said:
Have you had any success yet?
Click to expand...
Click to collapse
negative.
same issues?
Fortunately no, but I have been searching around a little because I am new to Motorola (fresh out of samsung) and I have had some issues like this in the past that were rather frustrating, but as far as I can tell, considerably less frustrating than what one might experience with our phone.
so for my own sake, since I can't see it, is your phone essentially just going into fastboot and automatically rebooting or can you access any of the menu options?
projekt8e said:
Fortunately no, but I have been searching around a little because I am new to Motorola (fresh out of samsung) and I have had some issues like this in the past that were rather frustrating, but as far as I can tell, considerably less frustrating than what one might experience with our phone.
so for my own sake, since I can't see it, is your phone essentially just going into fastboot and automatically rebooting or can you access any of the menu options?
Click to expand...
Click to collapse
Yes it is extremely frustrating.
Said something about not being able to write to partition. Any option that I pick comes up to the fastboot menu. It seems to fail anytime it attempts to write to the phone.
One thing that I have noticed is that battery level seems to be important. (above 50% specifically)
not that this will fix your problem, but it might be preventative maintenance from further problems. Have you seen this?
http://forum.xda-developers.com/showthread.php?t=1549625
It covers charging in a scenario like yours, because it sounds like it might be nearly impossible to get anything down without a decent charge.
projekt8e said:
One thing that I have noticed is that battery level seems to be important. (above 50% specifically)
not that this will fix your problem, but it might be preventative maintenance from further problems. Have you seen this?
http://forum.xda-developers.com/showthread.php?t=1549625
It covers charging in a scenario like yours, because it sounds like it might be nearly impossible to get anything down without a decent charge.
Click to expand...
Click to collapse
Thanks! Ill keep that in mind. I think I was about 40 percent when I did it..... I doubt if that was the issue. I think as long as you dont lose power you should be OK... well what do I know... I will most definetly keep this in mind and make sure I use a full charge. My replacement phone should be here tomorrow morning...
Yeah, I think as long as you have power it should be ok, this was more of a measure to consider if your battery might be getting too low now after trying to fix it. But I guess if you have a replacement phone on the way, that will be easier, but maybe not as much fun! haha. Do you have to return the bricked one right away then?
projekt8e said:
Yeah, I think as long as you have power it should be ok, this was more of a measure to consider if your battery might be getting too low now after trying to fix it. But I guess if you have a replacement phone on the way, that will be easier, but maybe not as much fun! haha. Do you have to return the bricked one right away then?
Click to expand...
Click to collapse
Yup has to be returned within 5 days. I am making sure the battery is completely dead before i box it up. So they would have to at least charge it before they see the error.
They said something about being charged 299.00 if I messed with the image, software or something like that.... I think that it would be very hard for them to prove that point though in all actuality. Not much option.... Yeah.. not the way I really wanted to go but it is what it is..
fair enough. Yeah, leave it dead.
projekt8e said:
fair enough. Yeah, leave it dead.
Click to expand...
Click to collapse
This is exactly what i needed.
http://forum.xda-developers.com/showthread.php?t=2035131
All is working well. Perfect, perfect, perfect.
right on, so what did you end up doing then, if you don't mind explaining?
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