Related
I've been through 2 G2x's , both have had the same problems...
Random reboots
Random freezes
Random shutdowns
Crazy inconsistencies in battery life
I've also gone the route of rooting and trying CyanogenMod with the same results.
With the battery issues, I did the following test 3 nights in a row.
Phone wiped, 100% battery charge, signed into Google and let the apps download, rebooted phone, data connection turned off (airplane mode), unplugged the phone and set in the exact same spot in the same room 3 nights in a row at 11PM.
Come 8AM when I woke here's the results:
Day 1: 30% battery remaining
Day 2: 80% battery remaining
Day 3: 0% remaining - battery was stone cold dead - wouldn't boot until I plugged in.
Phone was fine when I started typing this post, but just now while typing this message I reached over to check my phone for text messages (I keep the alerts volume all the way down while at work) and it's locked up again...
Guess I'll be returning the phone for a refund and borrowing an old flip phone for a month until the Sensation comes out.
Sorry LG - when it works, it works AWESOME, but I need something a bit more reliable considering that work needs to contact me on the phone and I am on call 24/7 !
In the 2 weeks I've had it I've only had 2 random freezes and no other issues at all. This is my first android phone and the thing i see that's screwed up with android is it leaves applications open, there is no exit buttons on apps. I've been using juice defender and uninstalling any apps that keep popping back up after ending task on them.
Sorry to hear about your problems. You're doing the right thing by returning it and getting another phone. I don't understand why people have loyalties to corporations who could give 2 craps about you. Buy what works for you and makes you happy.
For me, the occassional reboot on the G2X is a pain but the promise of a stable CM release and an official gingerbread release on this hardware has me sticking it out. Can't wait
I haven't had any issues with my phone except battery life. Buy my battery life isn't as bad as yours. It used to be horrible but I got a new sim and that seemed to make it better.
Regarding the reboots, some apps are causing the phone to reboot. Either the apps aren't optimized for the phone or the other way around. I had one reboot and after I removed the offending app, never happened again.
Sent from my LG-P999 using XDA App
kangxi said:
I haven't had any issues with my phone except battery life. Buy my battery life isn't as bad as yours. It used to be horrible but I got a new sim and that seemed to make it better.
Regarding the reboots, some apps are causing the phone to reboot. Either the apps aren't optimized for the phone or the other way around. I had one reboot and after I removed the offending app, never happened again.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Actually, when I bought the phone I had them put a brand new SIM card as mine was getting to be a little long in the tooth - if getting a new one helps the situation I'd hate to see how it was with my old one :-D
Removing an offending app would prove to be a real problem for me though, as everything that I install has a legitimate work-related function.
im returning mine today for a newer batch one. its may 4 so i expect one that has the date of 4/24 and up as stated in other threads. mine reboots and freezes during random functions.
I ordered mine on the 20th so the day the phone was out in the store. I had to order mine online since i am a T-Mobile RSA. I have alittle screen bleed but not much. I will be doing exchanges until i get one with no bleed. Other wise i have had no problems at all. No reboots, lock ups, data problems, nothing the phone is rock solid. I love the phone. Every person that has come into my store with problems i have told them that T-Mobile is going to exchange this for you under the lifetime warranty if you have it for the life of you having the phone. So you have nothing to worry about. The phone is a great phone to have. Do the exchanges until you get a working one. I know i would do it until i did. Even if it meant doing it 100 times.
JWhipple said:
I've been through 2 G2x's , both have had the same problems...
Random reboots
Random freezes
Random shutdowns
Crazy inconsistencies in battery life
I've also gone the route of rooting and trying CyanogenMod with the same results.
With the battery issues, I did the following test 3 nights in a row.
Phone wiped, 100% battery charge, signed into Google and let the apps download, rebooted phone, data connection turned off (airplane mode), unplugged the phone and set in the exact same spot in the same room 3 nights in a row at 11PM.
Come 8AM when I woke here's the results:
Day 1: 30% battery remaining
Day 2: 80% battery remaining
Day 3: 0% remaining - battery was stone cold dead - wouldn't boot until I plugged in.
Phone was fine when I started typing this post, but just now while typing this message I reached over to check my phone for text messages (I keep the alerts volume all the way down while at work) and it's locked up again...
Guess I'll be returning the phone for a refund and borrowing an old flip phone for a month until the Sensation comes out.
Sorry LG - when it works, it works AWESOME, but I need something a bit more reliable considering that work needs to contact me on the phone and I am on call 24/7 !
Click to expand...
Click to collapse
A better test would have been to not install any apps. Then you could truly test your phone and not some rogue app, that you keep installing.
I'm about to do a complete wipe again and use a secondary Gmail account I have so to eliminate any apps from auto-installing and test throughout the day since I have my work PC handy.
or just skip the Gmail sign in process at first and add your Gmail account later from Settings. This will prevent it downloading your apps on first boot.
Also to the New Android User: Back closes apps, Home leaves them open. It isn't the OS's fault if you don't know how to use it.
To the OP: Have you rooted and flashed the Pre-Dexopt Patch from Paul?
http://forum.xda-developers.com/showthread.php?t=1051616
LG left the phone in Dev mode and doesn't dexopt the phone on initial bootup. This is why our phones boot so quickly. The downfall is after a few hours, it starts to lag out and lock up/reboot.
Sounds exactly like the problem you are having.
This patch is required for stock and EaglesBlood Roms excluding CM7. This should be fixed in the upcoming Gingerbread update. I also believe EaglesBlood and future roms will start coming with this patch included.
So do yourself a favor and patch it.
Basically, it's an awesome phone and many, if not all, of the issues should be resolved with software updates. Gingerbread is already in the works.
Sent from my LG-P999 using XDA App
player911 said:
or just skip the Gmail sign in process at first and add your Gmail account later from Settings. This will prevent it downloading your apps on first boot.
Also to the New Android User: Back closes apps, Home leaves them open. It isn't the OS's fault if you don't know how to use it.
To the OP: Have you rooted and flashed the Pre-Dexopt Patch from Paul?
http://forum.xda-developers.com/showthread.php?t=1051616
LG left the phone in Dev mode and doesn't dexopt the phone on initial bootup. This is why our phones boot so quickly. The downfall is after a few hours, it starts to lag out and lock up/reboot.
Sounds exactly like the problem you are having.
This patch is required for stock and EaglesBlood Roms excluding CM7. This should be fixed in the upcoming Gingerbread update. I also believe EaglesBlood and future roms will start coming with this patch included.
So do yourself a favor and patch it.
Click to expand...
Click to collapse
Yep, have tried without the patch initially and then with it.
I have signed in with the secondary Gmail account - only thing I imported from the original was my contacts, so, it's 100% stock with the exception of Paul's patch and recovery.
I'll be damned...
In an attempt to preemptively find out what I would need to return the accessories I ordered for the phone just in case I took the plunge and returned the phone, I was on hold with T-Mobile...
And while on hold, I grabbed my phone - and SURE ENOUGH - LOCKED UP HARD!
So, I guess this just made up my mind for me - I'll be returning this phone to point of purchase. Just need to use NAND to restore the stock backup , reflash stock recovery and unroot...
I am planing to return this phone too..
It seems the phone shut down completely for no reason, sometimes the screen doesn't wake up even tho phone is running in background.
So far i have tried to run completely stock with no apps installed no sync nothing and i was getting battery like 6-7 hrs.
I guess that was not acceptable for me.
I might have to wait till HTC Sensation comes out. What you think guys ?
Mine works fine, no problems at all, yes the screen bleeds a bit, but I can deal with that.
awesome phone, much better than my atrix
Sent from my LG-P999 using XDA Premium App
Slappy00 said:
Mine works fine, no problems at all, yes the screen bleeds a bit, but I can deal with that.
awesome phone, much better than my atrix
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
+1 Mine also works amazing... and a lotttt better than atrix....
ikm19 said:
I am planing to return this phone too..
It seems the phone shut down completely for no reason, sometimes the screen doesn't wake up even tho phone is running in background.
So far i have tried to run completely stock with no apps installed no sync nothing and i was getting battery like 6-7 hrs.
I guess that was not acceptable for me.
I might have to wait till HTC Sensation comes out. What you think guys ?
Click to expand...
Click to collapse
That's where my money is going...
my understanding is the sensation is locked down that's why cyan isn't going to get it. Which also means no dev support.
The MyTouch 4G and G2 were locked down too... Unless they are going to lock the bootloader?
ikm19 said:
I might have to wait till HTC Sensation comes out. What you think guys ?
Click to expand...
Click to collapse
HTC announced an update to the Sensation in Q3 that will include a NFC chip to match the features of the SGS2. I'm also guessing they'll increase the amount of RAM in the phone to make it more competitive. If the 2.3.3 update makes the G2X stable I may keep it until later in the year. If the Sensation comes out before they update the G2X I'll get Sensation. I need a phone that's consistently dependable and in that regard the G2X is a mess. I can't do custom ROMs because I travel globally and everyone I've ever used has always given me problems registering on foreign networks so CM7 is no silver bullet for me. It's a shame too because the G2X hardware (bleeding screen excepted) is pretty slick and it's really fast when the planets line up and everything works. Sigh.
Hi,
My Sensation (the 1.2ghz model, stock battery) has started rebooting after heavy use. I'm not sure if the phone did this when it was completely stock as I didn't use it very much before flashing.
I flashed to stock ICS first. After playing Temple Run for a solid 2-3 hours the phone gets very hot, then it randomly reboots. (and my damn stats were gone). I let the phone cool and played more yesterday, again after 2-3 hours it rebooted again.. I wondered if it was the ROM so I super wiped and installed Android HD Revolution 6.5 - exactly the same problem.
I tried plugging my phone in to my PC and looking at the logcat but it wasn't rebooting when I did get it in. It was setting CPU time or something fairly frequently - is this normal?
Has anyone else had this issue? My PC used to do this all the time when it was overheating so I think the same problem is occurring here.
Is it my phone? I bought the phone from a friend and it would be a pain in the ass to get it sent off on his insurance (especially with this problem, they might turn it on, find no issue and fire it back)
EDIT: Just to confirm - it's not only when Temple Run is on. After it rebooted the first time, I scrolled through the apps whilst it was still fairly hot and it rebooted again so its not specifically Temple Run which is making it reboot.
You can try flash sebastiankernel and see if there are any overclock, underclock, overvolt or undervolt problems. But most likely you have a defect model, send it back and describe to problem to them so they will know how to fix it.
if cellphone temp goes over 50 it automatically turn off , there is no defect in ur phone but this happens get cpu master add powr eidget on screen n keep a look out n u b fine
hit thnx if i helped
Sent from my HTC Sensation Z710e using xda premium
Thanks for the replies. I've actually been using a temperature widget. The hottest I've seen it record is 43c. Also, after it turned off it was this temp aswell so I don't think its quite getting to 50c.
So no one else has this problem after heavily playing 3D games? (or at all?)
Is there anything else I can try to fix this?
I recently flashed CMRex with Kejar's 4.1.1 gapps and was going about setting up my device. I got everything set up how I like with all the apps I wanted downloaded and running how I wanted them. I then ran the v6 supercharger mod that I had used on my past two roms with no problem whatsoever. After finishing the set up of the script, I rebooted my device and all was well. I went to browse on craigslist's mobile app, then I saw something I wanted to google, so I opened my browser. My browser took an ungodly amount of time to load my homepage(google), and wouldn't respond hardly. I couldn't get the touchscreen to respond. My hardware buttons did respond and I got haptic feedback from them, but no response on the screen. Eventually, after numerously pressing the home button, I got a message saying the browser wasn't responding, selected ok to close it, then back to the non-responsiveness of the touch screen and hardware buttons. And then another eventually later, after another multitude of home button presses, I got to my homescreen but everything was laggy. The most lag I have ever encountered with my device since I obtained it, not to mention that my device was beginning to heat up. So, I decided I would power off the device, remove the battery, let it cool down, and then replace the battery before powering it back up. Well, lo and behold, I did just that, went to power back up my device, and there was no sign of life at all. Tried to get into the bootloader, no response. Tried a normal boot, no response. Tried to plug it into the charger to see if it would charge, no response. Well, my girlfriend told me to leave the battery out for a while and leave it alone for a while before trying it again. So, I played some MW3 for about 45 minutes to an hour, repeated all the above, and still no sign of life. Can anyone help me out? (I don't know if this is supposed to go into the Q&A or here, so I just post here.) I'm so distraught at the possibility of losing my phone, that I'm finding it hard to cope at the moment. Should be thinking of ways to gain some money in order to purchase a new device or is there still hope?
what a long message.do you have any point form here?
i hope you solve the problem .
Do you have access to a separate charger? You can try charging your battery there and see if that works. Did you try connecting it to the computer? Maybe that will show some sign of life. Also, how old is your phone and did you over clock?
Sent from my Nexus S using xda app-developers app
kwibis said:
Do you have access to a separate charger? You can try charging your battery there and see if that works. Did you try connecting it to the computer? Maybe that will show some sign of life. Also, how old is your phone and did you over clock?
Click to expand...
Click to collapse
I did not overclock, I do believe that my clock speeds were at the kernel default, either 100/1k, or 200/1k. Not sure which, but definitely one of those. The only other charger I would have access to would be my mother's HTC charger, but I will try that and connecting it to the computer as well. Well, I'm not exactly sure on the age of the phone because I purchased it off of craigslist, but it's in great condition. Only had a small scuff on the top left corner, but I know that has nothing to do with the age of the hardware. ): Could it possibly be that my battery decided to die for some reason? I've been having horribly battery life lately. Granted, I had horribly battery life when I got the phone, but it's gotten worse and worse since then.
My Nexus S wouldn't start but gave a flash on the screen when the battery was first inserted. Just got it back from repair and it was a motherboard problem. Was looking at a Huawei G300 as a cheap replacement if the repair wasn't covered by warranty (which it was). Good luck!
Thing about it is, I bought the phone off craigslist so I have no idea if its covered by the warranty still. Should I try calling samsung and find out?
Sent from my SGH-i997 using xda app-developers app
Sorry for my late reply! You could try, but u guess you can get a battery from Ebay and check if that solved the problem. Or if you have a friend who has one...
Sent from my Nexus S
I'm the only person I know that has this phone. And I guess the battery will have to wait till I get a job, but if im waiting that long, I'm just going to get a new phone all together.
Sent from my SGH-i997 using xda app-developers app
Testing the battery can be done differently, do you have a multimeter? Maybe your neighbours have one, it's a common thing. You can measure whether it has any power left. If you measure low voltage (below let's say 3400 mV), then it could be battery related.
Sent from my Nexus S
DefinitiveX said:
I recently flashed CMRex with Kejar's 4.1.1 gapps ... or is there still hope?
Click to expand...
Click to collapse
Many reports on dead Nexus S with 4.1.1. Mine included after flashing CM10. Sent for repair 10 days ago and still waiting...
If you've got no warranty, perhaps time to buy a new phone? Bought myself a new Galaxy Nexus.
I would like to get a new galaxy nexus, but I have no money to do so. I'm currently trying to get a job and i m going to save up for a new phone. Im either going to get an s3, a galaxy nexus. Either one of those two or the new nexus if it comes out.
Sent from my SGH-i997 using xda app-developers app
Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down. I thought it was because the rom was not stable enough so I flashed CM9. On CM9 the phone would shut off every five minutes it was that bad. I then installed Miktouch 0.7 and the shutdowns for the most part stopped. The phone will shut down now and again and it always shuts down after I use youtube for 10+ minutes or use the camera for several minutes.
I tried to revert to stock and see if that fixed anything but when I boot into the bootloader it looks for PG59IMG and says no image found and nothing happens. I got the PG59IMG from this thread: http://forum.xda-developers.com/showthread.php?t=1878329
Any help is appreciated.
I swear it sounds mechanical...maybe battery related. Just starting out of the blue like that and it being cross ROM and all. It should just flash that file automatically from hboot though. Are you sure you copied the file to the root of your SD card? Did you relock your bootloader with *fastboot oem lock* before running it? Sometimes it doesn't like it if the usb cable is still plugged in. (for some weird reason) If you're still S-On, did you flast the boot.img file thru adb with *fastboot flash boot boot.img* after flashing your ROM?
Oh yeah, you won't be able to flash that PG59IMG if it is newer than the hboot version listed in your bootloader right now. That is until you get S-Off with the wire trick.
Check some of that stuff out & get back to us.
I agree it sounds mechanical, most likely a bad battery.
I confronted similar behavior over the weekend and a testing with a new battery allowed me to point a finger at an older, aftermarket battery as causing the shutdowns.
Sorry for the delay in the reply - real life got in the way.
I thought it was also mechanical but the shut downs are MUCH less frequent in Miktouch than on ICS roms so I thought it may have to do partially with the software.
I'm S-off, used the revolutionary method years ago. Never issued the "fastboot oem lock" command and I've never done anything related to fastboot. The stock image was in the root of the sd card.
When the phone does shut down it doesn't matter if take out the battery or do anything else, I can't get the phone to start back up until 20 mins later or so. The phone will certainly shut down if I use the camera or use youtube so if there is a way I can grab a log or something that could help let me know
I've had very similar issues, since installing a CM 10 alpha, and now on 10.1. The first couple weeks when I first rooted/flashed CM 10 were fine, but then it started rebooting one day, and never has stopped. Stock battery, no reboots prior to that, S-On, flashed the boot.img for each rom, and it's doing this with both CM 10 and CM 10.1. Does that also sound like battery, since it's the stock battery which has always worked fine? Also, it seems heat/intensity related - if I'm playing a game, using GPS, or talking a long time, that's when it tends to happen, and then it tends to happen right at/near the lock screen for a while after that until it's cooled down (perhaps that screams battery, but since it always restarts fine/has power I would have guessed it had to do with the processor or kernel). Thanks in advance for any advice!
Could be the battery...
I agree with the other posters. I had the experience of lots of random reboots a while back when I was working my way through sverhagen's 9.1r3+ ROMs. But, it just turned out that my stock battery had given up the ghost. Swapping to one of the gold batteries fixed the problem. I tried the stock battery in the interim for a brief stint and switched back to the gold, as the stock battery still caused random reboots. So maybe its time for a battery refresher
Faizt20 said:
Everything was fine on the phone until I tried out AOKP 4.2.2 alpha 2 a week ago, When I had the rom installed the phone would randomly shut down....
Click to expand...
Click to collapse
Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!
presin16 said:
Thanks, guys, I just ordered a battery, when it gets here I'll confirm whether that fixed it or not. Much appreciated, didn't realize batteries could go wonky in that way!
Click to expand...
Click to collapse
Yeah....the little suckers are on a power trip I think.
i've been having some shut down issues for a while, on different ROMs so I don't think it's that. whenever i'm using it i don't have any issues (unless it's a known ROM thing, that's separate). even during the day when i'm not using it, it hasn't shut down or anything. the issue is that a lot of times when i wake up, i find that the phone has been shut down. i charge it overnight. so, my best guess is that i should stop doing that, maybe the battery is bad, it can't handle that for that long?
idk any ideas would be helpful. i'm considering buying a gold battery anyway
Did you try the new Battery ?
I was have random shutdown and lockup problems. The phone would lock with a blank screen and I'd have to pull the battery to get it back.
Am running SilverL's CM 10.1. I might be a coincidence, but I backed off on the aggressiveness of the CPU settings (in the performance menu) and the problem went away.
I'm currently running a min/max = 128/1242.
I'm trying not to post a new thread so I'll post my very similar problem.
I got this phone about a year ago. I put Miktouch on it and was experiencing random shut downs all the time. I believe I posted on here and I can't remember the responses. As the mytouch q kinda sucks and I want a solid phone. I gave it another attempt this time with CM 9.1.0. When I used the camera once it shut down and restarted I think. Then I got a solid few days before it started going wanky again. Today alone I've had like 5 restarts. From what I've searched around it seems the problem here is the battery? This is stock battery and I got the phone used off ebay. I think I used stock rom like a week before rooting and putting Miktouch on it.
edit: For some odd reason my background also changed. Charged the phone backup. It turned off again.
If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.
WeekendsR2Short said:
If you've flashed any ROMs here to the MyTouch Q then that's your problem. It isn't this phone. These forums are for the HTC MyTouch 4G Slide. A much more powerful phone with a different manufacturer & motherboard. If you have S-Off go to their forums, wipe...wipe...wipe & reflash one of their ROMs. You're lucky you're not bricked.
Click to expand...
Click to collapse
I know. I'm talking about two different phones in the same post. I bought this phone (Mytouch 4g Slide) last summer but shortly started having problems. As I didn't want to deal with it I went back to my slowly dying touchscreen on my G2. When that finally died (touchscreen) I just bought a mytouch q as I wanted a phone that worked. This was my first new phone in a long time.
I am NOT trying to install any roms for the MyTouch Q on the MT4GS or the other way around.
S-OFF should be off on the 4G slide. Pretty sure my mytouch Q is still rooted though. It sucked at running CM 9
Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.
WeekendsR2Short said:
Sorry. Somehow I got confused. That being the case, it sure does sound like some type of a hardware issue instead of a software one.
Click to expand...
Click to collapse
Yeah, from what I read it could be a battery problem. Going to go with this Anker battery as its the only reliable battery I can find that doesn't cost an arm and a leg.
Anker Battery
Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium
demkantor said:
Yeah I'd start with a new battery myself, either a new OEM or an anker, both are cheap on eBay. Also look for a post where me and weekends were discussing the emmc of this phone, bear in mind I have zero proof, but I got a suspicion there may be multiples they put in here and some worse than others.
If the battery won't work then I would repartition the whole dang thing, either by returning to stock and the rerooting and resoff, or by at least flashing the same bootloader on top of the one you currently have.
Just some ideas, but if you want a better idea of what's causing your issue, pull a logcat
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a theory of whats causing it. If I extensively use the phone the battery warms up which gets to the point it shuts down. Thus if the battery is still too warm and I turn the phone on then it will just keep shutting down. Of course I can't do this until I'm home for the day as I'm out and about this weekend.
edit:
I used the Revolutionary way to turn s-off which is permanent.
I get random shut downs constantly. Usually atleast 3-4 times a day. It's pretty nerve racking. I honestly don't think it's the battery, I've experienced this issue on three different batteries and it happened on all of them. It's not ROM related either as I've tried probably 15 different ROMs (stock based, ICS, JB) and they all have this issue.
My buddy who has a Sensation also has this issue on his phone. Maybe it's a problem for that phone too since they are pretty similar?
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