Related
my g2x shut down and wont turn on..i charged it over night... it took like 3 hours to get to 99 percent...it took a while....i left it over night and this morning it was off and wouldnt come back on...i called tmobile and they told me to try to get a extra battery..but no one has em yet..and they cant exchange it cuz i bought it off of craigslist...anybody know anything that will be helpful?
Try holding down the volume down and power button at the same time beware it will wipe the device but may get it to boot not sure
Sent from my LG-P999 using XDA App
Had the same problem. Try pulling the battery out insert it back in. I had them ship me a new replacement.
Sent from my LG-P999 using XDA App
promptly go back to the person on craigslist and slap them in the face. I hope you @ least got a deal on the phone. Hopefully you shouldnt have to wait to long for replacement batteries to be made by some manufacturer. good luck
gconcepts said:
Had the same problem. Try pulling the battery out insert it back in. I had them ship me a new replacement.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
This works for me also. Happened about 4 times today.
Sent from my LG-P999 using XDA App
shovelhead83 said:
This works for me also. Happened about 4 times today.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It happened to me 3 times today, my phone shuts down and won't turn back on until I take it out and put it back in, it's because it gets overheated and the phone shuts down itselfs, it must be a defective battery that makes the phone really hot when it was in my pocket.I went home and replace it with another battery (from another G2x i was about to send back to Tmobile because of bad light bleeding from the top corners), and everything works perfectly. I start to love my phone a little better now.
That same weird thing happened to me one morning I was scared but all I did was took my battery out let it cool out for a while because I noticed my device was hot then it said system check under the LG logo then booted up
Sent from my LG-P999 using XDA App
djsteez said:
my g2x shut down and wont turn on..i charged it over night... it took like 3 hours to get to 99 percent...it took a while....i left it over night and this morning it was off and wouldnt come back on...i called tmobile and they told me to try to get a extra battery..but no one has em yet..and they cant exchange it cuz i bought it off of craigslist...anybody know anything that will be helpful?
Click to expand...
Click to collapse
its a shame you didn't just pull the battery. its not a hardware issue and this android build isn't the first to do that.. there are some issues with this build of android its obvious.. give some time more builds will come including cm7 which you will find rock solid soon enough.
I had two g2xs with the problem, and I'm pretty sure it's a hardware issue.
When I charged it, I noticed the back got really hot.
On that suspicion, I went to a different TMobile store and got one from a different batch, by looking at the manufacture date on the back of the box.
No more problems.
R
p.s. I'm pretty sure a software "fix" will involve underclocking/undervoltaging. Lame.
Probable fix
Hello,
So we’ve been working on this issue for quite a while. And have come up with a semi-practical solution. This might interest some of you, who have this issue.
Issue:
Both I and my friend opted out to purchase the new and wonderful LG g2x phone. After receiving the phones we came against a very similar issue. The cellphone unit would shutdown/turnoff during the charge [car or wall]. The shutdown would occur around 95% of battery charge. In addition the phone would get hot. After the shutdown to start the phone would require pulling the battery out of the unit and reconnecting it again, otherwise known as: Perform a battery pull.
Trials:
So after doing some research and funding out that LG is literally doing nothing about this issue, [great testament to their corporate integrity] we decided to take on this issue. At first we also believed that it is, indeed, the battery that gets heated and goes offline after reaching some temperature. After recognizing the poor quality of the battery, I’ve decided to purchase a better quality one online. No surprise really the phone would still lockup at 95% charge.
At this point I took it upon myself to resolve this issue with what resources I have available. I am an MIT student and have a high tech engineering lab available at my disposal, in addition to some free time with a winter break and all. Anyways, I pulled the phone apart and this is what I’ve discovered…
Discovery:
So inside the phone right next to the 4 connecting diodes that connect the battery to the cellphone unit are 2 semis [semiconductor hubs] that are responsible for providing battery charge information to the cellphones cpu [central processing unit] in addition theres also a line running to those semis that probably carries some sort of information [current] that the semis are also responsible for.
The first approach that we took was through the hardware, and killed that additional line and allowed the semis to only be responsible for the battery charge. The results were somewhat positive. Although the phone would freeze and glitch like crazy it would not shutdown with a subsequent necessity of pulling the battery.
We also noticed that it was the two semis that would get hot actually and lockup shutting the phone up and requiring a battery pull. The reason you need to pull the battery is because the iodes would overheat and completely glitch out, also even though the phone was now powered off there still was a current running between the battery and the phone. Only the battery pull would allow the diodes to drop the charge and reset to the position for the phone to be functional again and able to power up.
Solution:
So the idea was to find a software solution, which would free up this one line running into semis and allow them only to carry the responsibility for reporting the battery charge to the cpu. Believe it or not the first thing that came to my mind was the solution.
The app called Advance Task Killer (ATK) [available free on the market] proved to be useful. I do understand that this program is not very effective and only kills running progs in the foreground. However, that single line is also not very important to information transfer and becomes useless after you clear the cellphone’s foreground information transfer.
Basically when you run atk the line becomes inactive and you can charge the phone without any lockups. I’ve been doing that for about 10 days now. Discharging the battery to about 17% and charging it all the way up again and the phone has not yet turned off once and required a battery pull, nor has it been getting hot.
The idea is to clear the line prior to putting the phone on charge [car or wall]. So what you do is run atk few times [twice at least] then plug the phone in. this worked for both me and my boi here @ mit. After a week plus of testing we decided to release this onto the public.
We both a running stock lg g2x gingerbreads and have not tested it on any other roms, however, I suspect that it will have a similar effect on more leaner and cleaner roms like CS7.
Hope this helps those who are still struggling with this issue.
P.S.
In addition I would like to add that we did pull the battery apart in the lab and found that the stock battery was complete SHAYT! Some of the cells were cracked and overall it was just poorly manufactures. Cracked cells inside the power unit diminish its capacity to carry charge by a factor razed to n^power. Also may cause the battery to heat up during the final stages of its charge process [around 95%] due to the fact that to go the last 5% it will require higher resistance also in n^power. I suspect that in this great economy LG is cutting corners whatever place it can so there’s prolly very minimal quality control in power unit production. To those who think that they lose charge too quickly, that the battery gets too hot during charges, and possibly causing the phone to lock up: If you are using the stock battery, you may want to consider replacing it.
P.P.S.
Overall it is a hardware issue, in our opinion, that could be fixed with the use of the software, by rendering that extra line inactive for example. However, I would like to NOT compliment LG as a corporation and organization in general on their moral standing and responsibility that they carry to their customer base by doing completely nothing about this issue!
Thank You LG, I am no longer your customer.
“Making the world a better place, one action at a time.”
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
OK I HAVE searched the forums, but it seems this is a combination of a bad battery and/or the sudden death problem, however, the phone is less than 6 months old, the problems have all of a sudden appeared and I was able to get the phone back up an running so now I don't know what to think.
In the past week, I have noticed my GS3 just completely shuts off without warning even though it displays the battery at about 20%. When I plug it in and restart the phone, it shows 0% and charging. This has happened about 5 times now in the past week or so. Today, it happened again, but I was in the car. I tried to use my friend's car charger and it didn't seem to work. The phone kept buzzing like it wanted to turn on or charge but it wouldn't. I got home after a few hours and plugged it in. I tried to start it and it got past the SAMSUNG screenand then to the splash screen but it hung at the splash screen and would not boot up. I tried several times to boot, did a battery pull, even wipes the caches. No luck. Finally I went into recovery and did a complete wipe and restored a backup from March. I got the phone back up and running and all my apps are updated.
Does this make any sense?
Why all of a sudden would the phone misrepresent the battery life at 20% when its 0%?
Why would this 20% issue only start this week?
Why would the phone not even be able to boot up after going to 0%?
A bad battery seems unlikely since the phone is less than six months old and the sudden death issue is unlikely because I was able to restore with a recovery backup.
Any help would be appreciated. I am running Synergy ROM Nightly JB (r169) and the kernel is [email protected] #011013 from January 10, 2013.
Thanks,
Jim
Phone maybe not reading battery correctly? If it happens again, I would try wiping battery stats in recovery
Sent from my SCH-I535 using Tapatalk 2
Hi thanks for the reply, but I'm pretty sure wiping the battery stats doesn't actually do anything. I'm not sure why there would be the option to do it in the first place but most battery issue posts in the forums indicate that wiping battery stats is a falacy.
Thanks anyway,
Jim
deleting batterystats.bin fixed this problem for me. it wont hurt your phone.
I charged to 100%, deleted batterystats.bin, drained to 0%, charged up to 100%, never had the issue again.
youre right it doenst improve anythign battery life or anythig, but it can still fix problems.
Out of curiosity, why are you still on 169?
443 is out, and running real nice
With that being said, if this is an OEM battery (or if it's not,) it could be that the battery is the issue.
I always have a couple of spare OEM batteries on hand for extra juice if the need arises, and they come in handy if I ever have to isolate a battery issue.
You can always pick one up for about $20, and see if it is your original battery which is the culprit.
Btw, here is pretty much the gold standard on batteries.
It is an excellent reference, makes for some good reading, and can come in handy
It includes a whole lotta info on Lithium ion batteries, which is the chemistry used in modern cell phones/smartphones, and a lot of other applications.
http://batteryuniversity.com/
Biker1 said:
Out of curiosity, why are you still on 169?
443 is out, and running real nice
With that being said, if this is an OEM battery (or if it's not,) it could be that the battery is the issue.
I always have a couple of spare OEM batteries on hand for extra juice if the need arises, and they come in handy if I ever have to isolate a battery issue.
You can always pick one up for about $20, and see if it is your original battery which is the culprit.
Btw, here is pretty much the gold standard on batteries.
It is an excellent reference, makes for some good reading, and can come in handy
It includes a whole lotta info on Lithium ion batteries, which is the chemistry used in modern cell phones/smartphones, and a lot of other applications.
http://batteryuniversity.com/
Click to expand...
Click to collapse
OK I'll check it out. I am still on 169 because it works and I didn't want to fiddle around with it too much. I looked at the new features and there really isn't anything I'm missing. Also, I have Google Wallet working well without any issues and I did not want to screw up Wallet by upgrading. I'm waiting for 4.2 to come out with Touch Wiz (I actually like TW) and then I will upgrade... unless there is a new feature I'm not aware of?
Jim
calaski8123 said:
OK I'll check it out. I am still on 169 because it works and I didn't want to fiddle around with it too much. I looked at the new features and there really isn't anything I'm missing. Also, I have Google Wallet working well without any issues and I did not want to screw up Wallet by upgrading. I'm waiting for 4.2 to come out with Touch Wiz (I actually like TW) and then I will upgrade... unless there is a new feature I'm not aware of?
Jim
Click to expand...
Click to collapse
Regarding any new features in SynergyROM r443, I would recommend reading the Changelog here, as there's been a few
http://forum.xda-developers.com/showthread.php?t=1792499
If I do a dirty install, will Google Wallet remain or would I need to disable my Wallet account, and then go thru the whole install process again?
Jim
hmmm. the download for R443 doesn't seem to be working... I just get a spinning circle after the mirror link appears but the download never starts. I guess I'll try it again later.
Jim
calaski8123 said:
If I do a dirty install, will Google Wallet remain or would I need to disable my Wallet account, and then go thru the whole install process again?
Jim
Click to expand...
Click to collapse
Just to keep everything related to SynergyROM in one place, which makes it easier for others to see and for others to respond to, I'll post my answer in the SynergyROM thread linked above, and post a link
here
Please see the detailed answer here:
http://forum.xda-developers.com/showpost.php?p=40147201&postcount=20916
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,
I have searched and searched this forum to find any threads or posts that describe this problem. I have found lots of similar ones, but none like this, so that is why I have started a new thread. If I missed this topic somewhere, I apologize for not having found it.
My wife and I both have Skyrockets (GSII - I727). Stock AT&T ROM (not rooted), but both unlocked. Mine got partially wet last week (toilet incident, would rather not elaborate, but I will answer the first question everyone asks - yes it was a "clean" toilet ) Anyway, I immediately liberally rinsed all ports with alcohol and warmed gently with a hair dryer. After drying I powered up, and everything worked, except the battery percentage display (with a variety of completely fresh and fully charged batteries), would only show in the 50 - 68% charge range, and the phone seemed to die at about the rate one would expect commensurate with those numbers. Put it in a bag of rice for 2 days. No better.
So, after reading here and watching several YouTube videos, I completely disassembled the phone. cleaned all ports, ribbon connectors, mother board, etc. with CRC electrical contact cleaner spray using the spray tube and a very gentle toothbrush. I paid special attention to the micro USB charging port, and all other contacts and circuits that seemed to be related to charging, though I am by no means an electrical engineer or technician, so a lot of it was guesswork. I made sure all was dry and new looking. All contacts intact, no visible corrosion or bridging, and reassembled the phone perfectly (pretty proud of myself for not breaking anything in the process!)
The phone still works great, except for the battery percentage display issue. I have tried everything I've read on this forum about recalibrating the battery meter - discharging fully and then charging up. With the phone on, with the phone off, every permutation I can think of. I tried clearing the cache and rebooting. Still, the maximum the display will read is 68% and that's it, and the phone behaves and dies like it has a battery that is only 68% full, even though I know I am putting 100% charged batteries into it. I have verified this by putting the same batteries into my wife's identical phone and it displays 100%.
If my phone we're lasting as long as it normally would with a fully charged battery, I wouldn't be so bothered by the display being inaccurate, but that is not the case. I've downloaded CPU SPY and some other apps to see if my phone is using an unusual amount of battery resources, but it is not. So, that's the story.
I am not afraid of rooting the phone, and I have no warranties left so I don't care, it's just that from what I've read here on the forum, people with somewhat similar issues have not benefitted from rooting and then running apps or programs that are only available to rooted phones, so I would prefer not to go down that time consuming route, if all I'm going to do is hit another dead end.
So, any suggestions or comments would be greatly appreciated! Thanks in advance.
Best regards,
Ron M.
This may sound dumb, but did you try a factory reset?
sireniankyle said:
This may sound dumb, but did you try a factory reset?
Click to expand...
Click to collapse
Thank you for your post sireniankyle. Not a dumb question at all, and actually the answer is no. I have certainly considered it, but I haven't done it yet for 2 reasons.
The first is that from all the research I've done, trying to find others who had similar experiences (I have yet to find anyone with the IDENTICAL problem), they have all without exception reported that factory reset did not solve their problem.
Second, because of my previous experiences with doing a factory reset, it seems that no matter how well I am backed up, that it turns into a very time consuming process in getting the phone tweaked and with all the applications and setting back to where I had them. So, I've been holding out and saving factory reset as one of the last resorts.
The other last resort is to root the phone, because apparently there are some apps that might be able to reset the battery counter that will only work on a rooted phone. However, again in my research thus far, I haven't identified anyone with a rooted phone with a similar problem who has had succeeded in solving the problem.
Perhaps this weekend if/when I have the time and patience I will attempt one or both of the above. It's just that I have such low expectations of success that am reluctant to start down those paths.
If you, or anyone else on this forum can point to any experiences where these methods actually worked for someone in this same or similar situation, I would very much appreciate if you could direct me to the appropriate thread.
Thanks again very much for your input, and your further assistance and suggestions would be most appreciated.
Best regards,
Ron
No problem. I just try to help out where I can.
I can't say that I have had any of these issues. I understand the issues with backing up, but if you install twrp, you can create an entire backup of your phone. I've done it many times before without issue, and if resetting it doesn't work, you can still go back to your original set up.
It seems like you may be a pioneer in this particular issue. I hope you figure it out. Both for yourself, and for others who have this problem in the future.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
sireniankyle said:
No problem. I just try to help out where I can.
I can't say that I have had any of these issues. I understand the issues with backing up, but if you install twrp, you can create an entire backup of your phone. I've done it many times before without issue, and if resetting it doesn't work, you can still go back to your original set up.
It seems like you may be a pioneer in this particular issue. I hope you figure it out. Both for yourself, and for others who have this problem in the future.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again sireniankyle!
I used to like being a "pioneer", but as I get older now I just want my stuff to work, and don't have the time or the patience to go where no man has gone before Nevertheless, I absolutely hate to admit defeat, and now that you've turned me onto twrp (do I have to root first to use it?), then perhaps that will make the experiment less time consuming, so I may try this weekend if time allows.
In the meantime, the phone continues to function normally in every other way. I simply carry a couple fully charged batteries in my pocket throughout the day, which are of course 100% charged via my wall charger, but show as 58% as soon as I put them in the phone, and then die at approximately the rate one would expect from a 58% charged battery! Weird huh?
Best regards,
Ron
Was given a Skyrocket the other day which suffers from the same kind of problem (had massive water damage), but the battery percentage is stuck at 0%. So of course it will not even boot up. (Fully charged the battery in a wall charger.) Only thing the power button will do is vibrate the haptic feedback given at first power on, no screen activity. Funny thing is it'll go into Download mode perfectly normally and sit on the Odin mode screen till I assume the battery dies. However it will not go into Recovery mode. Plug in a USB charging cord to charge block or a port on a PC and the phone powers on and works perfectly fine, though forever stuck at 0% battery.
So the only thing I can think of to quickly get around this is without solving the problem, if in fact it can be, is to get a charging case. Like such, for example. http://http://www.ebay.com/itm/XPAL-Galaxy-S2-Skyrocket-PowerSkin-Case-i727-Extended-Battery-Gel-Cover-OEM-New-/310903753323 Had one similar before for another model and when installed it shows as if the phone is charging. So in theory will work for me, though powered strictly by the cases battery. Should work for you even better as you'll get the cases battery life then your own 58% worth of battery life. Edit, just realized when the last post was made, you probably have a new phone and moved on by now.
**I'm going to try to craft myself a homemade powered case yet, have tons a batteries kicking about.