Well, what the title says. It's becoming extremely annoying. Any suggestions?
what rom are you on?
I was on stock UCLA3, but when this problem occured I completely went back to stock. Still exists.
have you tried to do a 3e recovery factory restore?
I don't know what to do, honestly. I'm open to any suggestions! I'll look that up, thanks in advance.
Flash a custom rom with good kernel!
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
MAGiK9 said:
Well, I returned the phone to its original state. Exactly how I bought it.. The problem still exists. I don't think this is a kernel/rom issue.
What does ATT look at when they do exchanges? My counter says 2, is that a bad thing? Or can I just say I was trying to restore it because it kept shutting off and I didn't exactly know what I was doing? It has to be something with the hardware.
Click to expand...
Click to collapse
Yeah thats a bad thing, but they probably wont say anything. Don't mention anything about the counter
I started having the exact same issue this last weekend, took my phone into At&t warranty center, they replaced the battery and did a reflash back to factory rom. Still had the issue after that. The problem didn't start till after I took it out of my otter box and started taking the back off to pull the battery for rooting and flashing roms. Since i have put the phone back in the otter box case I have not had it restart on my yet. I am thinking it is a loose back cover and the battery is being knocked loose and then back in place hence the restarts. Just some of my observations from my own experiances with this same problem.
Ironically, mine has never happened until I took it out of the Otterbox Commuter case.
luckily i haven't had this issue, and i have removed it like 8-10 times before learning I didn't have to...
I took my phone to the att store so they could look at it.. I explained what was going on and the guy told me he was going to check the counter.. BUT he never did. He ordered me a new battery, and if that does not work they will send me a new phone. However, i'm going to get the new phone anyway.
Reboot issues and battery
Ok, same problem here, ICS leaked 4.0.3, Samsung Galaxy S2 skyrocket. Thought it was setcpu and/or busy box, not.. I notice that when I moved my phone in an odd manner it would reboot. Removed the battery cover and noted that there was play in where the battery sat, so much so that I was able to stick my finger nail into the separation, I don't know call it a half a cm. Any way, I took some note book paper, made a wedge so the battery was nice and tight... so far so good. Will let you know.
I'm not sure if this will be any help or not. My phone has done the same thing a couple of times and at least twice I've noticed that it was because I had the phone in my pocket and I was accidentally holding down the power button when I was bending over/squatting/etc. As for the other times it has restart on its own, I have no idea. It's been at least a month since those happened though.
The issues started about 4 weeks ago when I fell in a lake with my MyTouch 4g in my pocket. The issue was that I hadn't realized that it had gotten drenched until about an hour later as I was trying to chase my daughters runaway puppy through the neighborhood at the time and she wouldn't stop for anything.
Needless to say, by the time I got home and realized what happened, my phone wouldn't unlock and the camera flash on the LED was in a permanent on state. I immediately pulled the battery, SIM card and SD card and put the phone and battery in a bag of rice (a trick I had read about here). I waited for a week and attempted to power the phone back on, but again the flash led came on and the phone did nothing.
Thinking it a lost cause I switched back to my oldest phone (an old Motorola Cliq XT) and rooted it so I at least had CM 7.2 on it, though it is so slow that I am yearning for my MyTouch back again so I can actually do things like use Reddit and surf the net on my phone again (I was without my actual computer for months at one point so I got in the habit of using my phone for about 90% of my surfing and whatnot).
The other day, however, I had a bright idea while bored at work. When I got home I attempted to turn my MyTouch back on, and to my surprise, it came to life! I quickly switched out the SIM and SD cards and flashed CM 7 onto it and tried to boot it up. To my joy it seemed to work, at first, however as soon as it went to sleep, the screen would not turn back on. It lights up, but there is no image, the touch screen works and the OS seems to be working since I can feel the tactile feedback when I unlock the phone. I was hoping that someone could tell me if I had actually killed my phone dead enough that it is beyond hope or not? If I have actually killed it I was wondering if anyone had advice for me on where I could pick up a replacement for cheap?
I already tried asking /r/android the other night and the only suggestion they had was to make the dog pay for a new phone. Amusing as that may be, she doesn't currently hold a job and thus has no way to compensate me for the damage.
Any and all advice is appreciated, thanks!
If you stalk Ebay you might find one with a cracked screen that still functions for cheap or something like that ,that will allow you to use a part from your phone to make it whole.. providing you know how to replace the screen or basic repairs,that is what i have done 4 times over the past 2 years..
Good Luck!!If you look long enough and bid right you can get one for a fair price ,I bought my last one for 20 dollars and replaced the screen after dropping it in my foyer and worked like a charm you just need to be careful opening it.I hope this helps as far as providing a potential solution to ur problem.again Good Luck!!
Sorry, you probably did. Phones can barely take a couple minutes of water, yours took a swim. Usually the rice is the only way to get it dry, if that didn't work....
Your screen could be damaged though. Your best bet would be to order a good phone at a pretty reasonable price off contract on sites like ebay or swappa, or if you're eligible for an upgrade, go for it.
Motorola Cliq XT? That was my first smart phone, can't say I miss it much lol. Of money is super tight I say get an optimus T and sell that pos. The optimus actually ran cm7 pottery l pretty well for having a 600 mghtz processor
Sent from my SGH-I747 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
Hello XDA,
A couple months ago I decided to replace the stock battery with a $12 replacement I got off ebay. For those who keep up with the Nexus 5 news, a lot of users decide to replace their batteries because they think that a fresh battery can rejuvenate the battery of life of the phone, which makes sense. Apparently, despite looking the exact same as the stock one, it is made by Samsung because on the back it says "SAMSUNG TSD1 PGF445560LT.....". Because it's a third party, I saw a few posts online that said how much problems they had. I decided to still go with it because I guess I was desperate. After I replaced it, I honestly got similar results to what I got with the originally packaged battery. I decided to leave the battery in because I thought that maybe I could get better results over a longer period of time. Since June, I was running the Marshmallow preview, updated to preview 3.
Anyways, now to the part that matters. One week ago, my phone, running M Preview 3, was having random reboots, you know things I read about before I got the battery. It was also getting hot. I don't know if this was a bug with the preview, but I decided with my gut that it may have been because of the battery. So I decided to take apart my phone to replace the battery I got from Ebay with the one originally packaged in my phone. Well bad news here, because my phone wouldn't boot at all! After a couple of tries, I was able to see light on the inside after lifting the back cover. I was able to access the bootloader, however only when my phone was charging. I was able to flash fastboot commands allowing me to factory reset my phone. I was able to achieve something similar with the ebay battery accept I kept having this problem. Now I know you're thinking that maybe I should just buy a new battery, but what's to say that I'll get another crappy defect making me have the same problem? Can someone help me figure whether I damaged the phone elsewhere. I'm having a friend check it out tomorrow, but I would really appreciate your help.
If u can send me pics of the device, ask the connections and the board I can help, but not without seeing the device, I have the nexus 5, have replaced the battery and screen/digitizer and replaced a faulty USB port, so I know it inside and out, also have the Nexus 6 and waiting on the 5x, send me pics I'll look it over, all I can really say is NEVER buy a third party battery, always make sure it's the right battery, and when u take stuff apart like that u should always disconnect it first, never touch the board with the tools and make sure u don't damage connections at all
Sent from my Nexus 6 using Tapatalk
Okay, I will get back to you. I have to use an old phone to take the photo so it will take some time.