Hello all. So here is my situation.
Motorola Milestone X2
Last night I successfully rooted the phone and installed CMOD 10 using these directions
http://forum.xda-developers.com/showthread.php?t=2101633
Everything went fine. Charged the phone overnight, went for a jog this morning running both Pandora and c25k app. Absolutely no issues.
So I get to work and the phone just shuts off. Will not power back on or into fastboot. When plugged into USB, green light comes on.
After several minutes it will randomly power back on. Then after using it for a few minutes, it will just shut off again. Powering on and shutting down seems to happen randomly.
Any suggestions? Thanks in advance
doogie87 said:
Hello all. So here is my situation.
Motorola Milestone X2
Last night I successfully rooted the phone and installed CMOD 10 using these directions
http://forum.xda-developers.com/showthread.php?t=2101633
Everything went fine. Charged the phone overnight, went for a jog this morning running both Pandora and c25k app. Absolutely no issues.
So I get to work and the phone just shuts off. Will not power back on or into fastboot. When plugged into USB, green light comes on.
After several minutes it will randomly power back on. Then after using it for a few minutes, it will just shut off again. Powering on and shutting down seems to happen randomly.
Any suggestions? Thanks in advance
Click to expand...
Click to collapse
Quick update. It is draining the battery. The next time it booted up I watched carefully, and the red light in the corner was flashing and it said 5% battery, even though it had a full charge just a couple of hours ago. Something must be draining it badly if it will not even run very long while plugged in. Again, any fix for this would be greatly appreciated.
doogie87 said:
Quick update. It is draining the battery. The next time it booted up I watched carefully, and the red light in the corner was flashing and it said 5% battery, even though it had a full charge just a couple of hours ago. Something must be draining it badly if it will not even run very long while plugged in. Again, any fix for this would be greatly appreciated.
Click to expand...
Click to collapse
SBF back to stock and see if it still does the random power downs. If it still does than I'm sorry to say but its your phone
TheTechnicalBoss said:
SBF back to stock and see if it still does the random power downs. If it still does than I'm sorry to say but its your phone
Click to expand...
Click to collapse
Is there a reason to think that flashing to CMOD 10 actually broke the hardware? I have never had battery issues before. SBFing back I am sure would resolve the issue but then what?
And I am not talking "I used to get 12 hours, now I get 10" I am talking "I used to get 12 hours, now I get 12 minutes."
Even when plugged in, if I use it very much, it will die. Surely this is an issue of the phone incorrectly reporting the battery levels. I ran the battery calibration app (not at 100% charge since I cannot seem to get it that high) and it seemed to have no effect.
When I try to have the OS boot into recovery to try clearing the battery data, I just get an icon that look like the little android guy standing in front of a caution sign.
doogie87 said:
Is there a reason to think that flashing to CMOD 10 actually broke the hardware? I have never had battery issues before. SBFing back I am sure would resolve the issue but then what?
And I am not talking "I used to get 12 hours, now I get 10" I am talking "I used to get 12 hours, now I get 12 minutes."
Even when plugged in, if I use it very much, it will die. Surely this is an issue of the phone incorrectly reporting the battery levels. I ran the battery calibration app (not at 100% charge since I cannot seem to get it that high) and it seemed to have no effect.
When I try to have the OS boot into recovery to try clearing the battery data, I just get an icon that look like the little android guy standing in front of a caution sign.
Click to expand...
Click to collapse
cyanogen 10 has issues on our phone. plain and simple. also check the battery stats and see whats running. i had an issue once with facebook running 99% of the time consuming way too many resources. id sbf and try again from stock. if theres still issues try running cm9 it runs nicely and its my daily driver.
...............................
Lorenzo VonMatterhorn said:
cm9 is a bit better in quite a few aspects. i would try it over cm10. for battery life alone. i have stayed on it the longest now, surpassing eclipse, which used to be my favorite. :good:
---------- Post added at 12:15 AM ---------- Previous post was at 12:13 AM ----------
battery life on cm10 is absolutely horrible. it will never be anything close to stock, and you will be lucky if you can get it to last you a whole day. even when working properly.
Click to expand...
Click to collapse
Not necessarily, I've gone two days with 3g radio on but with minimal use on cm10 it really just depends on the hardware variations. Just like how two phones of the same model over clock differently because of minor flaws and variations durring manufacturing.
Sent from my Nexus 7 using XDA Premium HD app
So I was finally able to get it to charge to 100% and then used the battery calibration app.
I could not tell immediately if that did anything, but it seems to be holding its charge today. Guess we will see how it does over the next couple of days.
Thanks!
Related
So I tried one of the tricks floating around to sort of calibrate the batter. I charged to 100% like any normal charge, then in Tenfar's I wiped the battery stats. Then, as a guide said, I have let my battery completely die. However, I plugged my phone into my WALL charger, and it immediately started booting but it booted into Tenfar's..... I thought that was weird, but then I clicked on reboot system to have it boot normally, and it just died again partway through. I turned it on again after unplugging and replugging, but it booted into Tenfar's again. Then I left it there for a sec to see if it could gather some charge while in that screen, but it just died again. I don't know why it's not working...?
Ohhh crap. You've done it now. You have to sbf flash, but honestly I don't know if you have enough charge for that.. what you did is disable the feature to charge without fully booting up, and your phone automatically goes into recovery which doesn't actually charge the phone.
I believe your best bet is to buy a new battery, or go into AT&T and use one of their batterys... switch to charge mode in tenfars recovery app, switch back to your dead battery, let it charge. Then your good. make sure your Atrix NEVER dies while in recovery mode (set from the cwm app.)
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Well, while in the CWM recovery, I clicked reboot again, but this time I quickly pulled the charger out and then plugged it back in, and it worked. It must have started taking the charge again because it finished booting up and now my phone is working well and is charged again! Crisis averted.
But really...why did tenfar's even open up right when I plugged my phone in? I hadn't been using it recently or anything..
Draining the battery down to zero does not need to be done on lithium batteries. That is a trick for NiCad batteries to keep them from building a memory.
Sent from my MB860 using XDA App
Beard, tenfars cwm is hacked so that it works on the Atrix. The way it works is replacing that charging thing with the recovery.
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
jbrussee said:
Beard, tenfars cwm is hacked so that it works on the Atrix. The way it works is replacing that charging thing with the recovery.
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Click to expand...
Click to collapse
What do you mean? What "charging thing"?
Also, Sifon, so basically the threads that gave methods of battery calibration that involved draining to zero were lying to me? those dastards! Thanks for the tip though, I'll be sure to never EVER EVER EVER do that again lol.
thebeardedchild said:
What do you mean? What "charging thing"?
Also, Sifon, so basically the threads that gave methods of battery calibration that involved draining to zero were lying to me? those dastards! Thanks for the tip though, I'll be sure to never EVER EVER EVER do that again lol.
Click to expand...
Click to collapse
Internet sarcasm doesn't work . But seriously, these Lithium Batteries physically do not gain anything from being fully discharged. Keyword physically
Battery Calibration
Sorry to hear you had a scare... right now the cwm situation is a bit sketchy but booting to recovery is a must. Now I'm not gonna start a whole "liion batteries don't need depletion because they have no memory yada yada" convo but the the results don't lie and let me explain why.
From what I've learned from my xda lurking, there is an amount of battery that is reserved so that it isn't completely dead. Now with all our meddling and rebooting this can get out of sync thus reporting wrong battery stats. The only time it has to learn new battery stats is when it has been forced manually ( calibration app found in the nexus forums) or when android reports that it thinks the battery is dead. So instead of 5% being 5% its more like 5% is 20% so from what I've observed and tested is that when bad battery drain is attributed to this you will experience 100% drain to 60% very rapidly and then it slows down. When bad battery drain is attributed to a rogue app it drains rapidly regardless of the amount of charge and doesn't really slow down at all.
Just so were on the same page I agree that the actual battery is fine ( no liion battery memory ) its android that gets a lil screwey. So in theory this doesn't make sense... I know.. but the results speak for themselves.. 4 hours up and 94% left... facebook twitter and gmail all synced once an hour. Before I would have been at 80% and then it would slow down. I hope someone can benefit from this
Alright, thanks for the replies guys. And yeah I agree, at this point CWM is a must...just a little weird that it would come on when my phone boots after dying. Oh well. And Sifon haha sorry, I was kind of afraid that post would come off the wrong way haha but really, I was actually accepting what you were saying lol.
Anyway, back on topic, since I've done all that my phone is now at 77% and it's been on for about 24 hours (maybe less, it seems the count got a little off for some reason). Does that sound pretty good? Wasn't overly using, but also wasn't NOT using it either. I tend to leave Wifi/data, etc. off when I'm not going to be using it for a while.
thebeardedchild said:
Alright, thanks for the replies guys. And yeah I agree, at this point CWM is a must...just a little weird that it would come on when my phone boots after dying. Oh well. And Sifon haha sorry, I was kind of afraid that post would come off the wrong way haha but really, I was actually accepting what you were saying lol.
Anyway, back on topic, since I've done all that my phone is now at 77% and it's been on for about 24 hours (maybe less, it seems the count got a little off for some reason). Does that sound pretty good? Wasn't overly using, but also wasn't NOT using it either. I tend to leave Wifi/data, etc. off when I'm not going to be using it for a while.
Click to expand...
Click to collapse
Well I am sorry too, because I did not realize how Android handled the battery. Since Android can incorrectly detect the battery level, these methods should work on the OS side.
thebeardedchild said:
Alright, thanks for the replies guys. And yeah I agree, at this point CWM is a must...just a little weird that it would come on when my phone boots after dying. Oh well. And Sifon haha sorry, I was kind of afraid that post would come off the wrong way haha but really, I was actually accepting what you were saying lol.
Anyway, back on topic, since I've done all that my phone is now at 77% and it's been on for about 24 hours (maybe less, it seems the count got a little off for some reason). Does that sound pretty good? Wasn't overly using, but also wasn't NOT using it either. I tend to leave Wifi/data, etc. off when I'm not going to be using it for a while.
Click to expand...
Click to collapse
Well I am sorry too, because I did not realize how Android handled the battery. Since Android can incorrectly detect the battery level, these methods should work on the OS side.
BTW, your battery life is kicking mines ass right now
Okay, my battery seems even more screwed up now. It dropped 10% in like an hour after I left my apartment this morning, and I barely used it, Wifi/data weren't on...The real kicker is I just got back to my apartment and noticed it dropped another 10% during a timespan that I literally didn't even look at my phone once, over like another hour or so...wtf?
thebeardedchild said:
Okay, my battery seems even more screwed up now. It dropped 10% in like an hour after I left my apartment this morning, and I barely used it, Wifi/data weren't on...The real kicker is I just got back to my apartment and noticed it dropped another 10% during a timespan that I literally didn't even look at my phone once, over like another hour or so...wtf?
Click to expand...
Click to collapse
You may just have a faulty battery. Id call Moto, or go to a ATT store and see if you can get a replacement.
Before you get a new battery I'd like to try something. Drain it down nice and good (say 3% - 5%) then plug into your wall, enter cwm and hit charge mode. This should charge your phone when it is off. Unless you need an alarm
If after that it still gives you grief, then its time to call moto.
Sent from my Googletron
First let me apologize in advance because I'm sure I'm not posting this properly.....but..............
My son mailed his htc hd2 to me and it just arrived in the mail. I opened it, turned it on and it all looked great except it said "no sim card". I turned it back off and inserted the sim card, and pressed the power button.................NOTHING......
What have I done wrong?
Please help me!
cheapchik said:
First let me apologize in advance because I'm sure I'm not posting this properly.....but..............
My son mailed his htc hd2 to me and it just arrived in the mail. I opened it, turned it on and it all looked great except it said "no sim card". I turned it back off and inserted the sim card, and pressed the power button.................NOTHING......
What have I done wrong?
Please help me!
Click to expand...
Click to collapse
Try the hd2 forums
Sent from my Googletron
This is now happening on my replacement phone! I got the first phone replaced because it wasn't charging but now it's happening again on the replacement. It seems to only happen when the battery gets to 20% or lower. When it does this, it doesn't matter if it is USB or wall charging. I have been able to get the new phone to charge now twice by rebooting - one time it took three reboots. The first time it happened on my first phone the battery widget stuck on 50% and I didn't get the low battery warning and the battery went to 0 before I knew it and it took forever to begin charging again. I've been on different battery modes when it happens, so that isn't causing it.
I've mentioned this on a couple other threads and there's been others that responded it happened to them, so I thought I'd start a thread on this in case Motorola is monitoring this forum (they better be). Anyone else chime in here so we can get a feel for how widespread this may be.
Just let mine go down to 20 plugged up and its charging but im only on day one
Sent from my MB855 using XDA Premium App
beartrap said:
This is now happening on my replacement phone! I got the first phone replaced because it wasn't charging but now it's happening again on the replacement. It seems to only happen when the battery gets to 20% or lower. When it does this, it doesn't matter if it is USB or wall charging. I have been able to get the new phone to charge now twice by rebooting - one time it took three reboots. The first time it happened on my first phone the battery widget stuck on 50% and I didn't get the low battery warning and the battery went to 0 before I knew it and it took forever to begin charging again. I've been on different battery modes when it happens, so that isn't causing it.
I've mentioned this on a couple other threads and there's been others that responded it happened to them, so I thought I'd start a thread on this in case Motorola is monitoring this forum (they better be). Anyone else chime in here so we can get a feel for how widespread this may be.
Click to expand...
Click to collapse
Have you tried doing a hard reset and letting the phone sit for 20 minutes. It could be some kind of bug. I know mine had some force closes on the first day. I did a hard reset from recovery and let the phone sit at first boot. Then did a reboot and have had no problems since.
Master reset for photon 4g.
http://https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/69069/~/photon-4g---master-reset-%2F-factory-data-reset
jfdebo779 said:
Have you tried doing a hard reset and letting the phone sit for 20 minutes. It could be some kind of bug. I know mine had some force closes on the first day. I did a hard reset from recovery and let the phone sit at first boot. Then did a reboot and have had no problems since.
Click to expand...
Click to collapse
jfdebo779 said:
http://https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/69069/~/photon-4g---master-reset-%2F-factory-data-reset
Click to expand...
Click to collapse
I did a factory reset on the first phone and that didn't change this problem.
I haven't seen this problem on my phone. Best thing to do is report it to the Motorola forums and have them look at it especially if many others are experiencing the same issue.
In the mean time, you possibly could have another bad unit. Not sure why it would not charge when the battery hits 20% or lower. Also what battery widget are you using?
ericdabbs said:
I haven't seen this problem on my phone. Best thing to do is report it to the Motorola forums and have them look at it especially if many others are experiencing the same issue.
In the mean time, you possibly could have another bad unit. Not sure why it would not charge when the battery hits 20% or lower. Also what battery widget are you using?
Click to expand...
Click to collapse
Good idea on the Moto forums. I have tried Battery Monitor widget, Circle Battery widget and Battery Notifier (big text) widget. No one widget was in use or installed for every instance I had a battery charge problem, but I guess it may be more than one widget with potential interferences. Has anyone else been using any of these widgets and not experienced this problem?
@Beartrap
What battery widgets etc have you installed? Sounds like a compatability issue with something that was installed. Try using the phone completely stock with no custom widgets installed. If you can get the phone back to stock out of box condition that would be the best way to troubleshoot this problem. I doubt it's another bad phone.
tx_dbs_tx said:
@Beartrap
What battery widgets etc have you installed? Sounds like a compatability issue with something that was installed. Try using the phone completely stock with no custom widgets installed. If you can get the phone back to stock out of box condition that would be the best way to troubleshoot this problem. I doubt it's another bad phone.
Click to expand...
Click to collapse
I agree it's not a bad phone, but some bug either in the phone or installed app/widget. I'd like to know what battery widgets people are using that haven't had this issue so I know what's safe.
Not exactly related to battery widgets but i have noticed that Estrong's, Astro and File Expert file managers do not work correctly on my Photon. They don't show the full capacity of my 16gb sd card and they also don't show all the files in my download folder. So I'm thinking theirs going to be more incompatability issues with this phone until app developers get some updates rolled out for this phone.
As for battery widgets, i don't use them. I use the stock battery ifo that is included with the Photon. Sorry I can't give any help with that. but I'm pretty sure the widgets in the Android Market will not be fully compatible with the Photon. Uninstall everything you installed from the market and use your phone for a day or so and see how it acts.
I'm having the same issue, i'm not using any sorta battery widget/app, just stock(non-rooted).
Its been charging for about 4 hours today and went from 20% to 30% and its hot, really hot.
I've had it since day one and seems to match what the OP is saying about once it goes below 20-30% it has a hard time charging but like i mentioned before, mine gets toasty when its failing at charging.
Also had an issue while streaming from google music beta, went from 100 to 20% in <2 hours and once again it was hot as the devil's **** then it wouldn't charge.
cobrahicks said:
I'm having the same issue, i'm not using any sorta battery widget/app, just stock(non-rooted).
Its been charging for about 4 hours today and went from 20% to 30% and its hot, really hot.
I've had it since day one and seems to match what the OP is saying about once it goes below 20-30% it has a hard time charging but like i mentioned before, mine gets toasty when its failing at charging.
Also had an issue while using streaming from google music beta, when from 100 to 20% in <2 hours and once again it was hot as the devil's ****.
Click to expand...
Click to collapse
I did fail to mention that each time I did notice the back of the phone was pretty warm but not what I'd consider real hot. The third time this happened (on second phone), I cooled it down to room temperature and it still wouldn't charge.
beartrap said:
I did fail to mention that each time I did notice the back of the phone was pretty warm but not what I'd consider real hot. The third time this happened (on second phone), I cooled it down to room temperature and it still wouldn't charge.
Click to expand...
Click to collapse
Well it got hotter the my evo 4g ever did after flashing many roms and kernels and what not and even hotter the my pre minus when simultaneously charging and tethering. Havent had a phone get that hot before, i'll try to get a temp reading when it happens again.
Just pulled the battery little while ago and it started charging again. Seems to be hit or miss with the restarts and battery pulls the get the thing going.
I havent tried just turning it off and letting it charge past 30% yet, to see if it only does it when it on vs. when it off.
It's happened again. I was running speedtest.net repeatedly to test my radios and my battery temp climbed up to 118F. I checked if the phone would charge periodically and it did until the battery got less than 30%. It seems to be this combination that causes the malfunction. I rebooted and it charged fine, but the temp also fell to 115F, so I don't know if it was the reboot or lower temp, but at least now I know how to get it to recharge and not run th and it always charged, battery down to 0.
I tried to make this happen the other night by running quadrant repeatedly, but temps never went above 115. It always charged that night, so 115-118 is the magic number together with <30% battery.
BTW - our radios may kickass, but they also generate a lot of heat, so be on the alert to high battery temps when hitting the radios hard.
My first Photon had the problem where the battery went from 50% to DEAD immediately. I remember one time the phone was red hot to the touch right before it died, it was just idling. It wouldn't accept charge until I removed and replaced the battery.
My replacement Photon doesn't have the problem (yet) or any of the first Photon's problems. I am convinced there is a bad batch of Photons out there.
Unfortunately I'm on my second photon. I exchanged the first for this reason.
Do any of you happen to use a case with a magnet in it? I've only had this happen twice and both times it was in a case. Now it doesn't happen.
Sent from my MB855 using Tapatalk
money226 said:
Do any of you happen to use a case with a magnet in it? I've only had this happen twice and both times it was in a case. Now it doesn't happen.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
I am using the black Sprint case, but there's no magnet in it. I do think the case may aggrevate the heat buildup so if I hit it hard again and feel it getting warm, I'll be sure to remove the case.
beartrap said:
I checked if the phone would charge periodically and it did until the battery got less than 30%. It seems to be this combination that causes the malfunction. I rebooted and it charged fine, but the temp also fell to 115F, so I don't know if it was the reboot or lower temp, but at least now I know how to get it to recharge and not run th and it always charged, battery down to 0.
Click to expand...
Click to collapse
This theory just got shot down. I hooked up the USB charging cable at 62% and 84F and it wouldn't charge. The phone recognized the connection and displayed the message it was in charge mode, but the battery in the notification bar didn't show it was charging nor did battery monitor widget. I then connected it to the OEM wall charger and cable and nothing. I rebooted and no change. I shutdown the phone and hooked it up to AC and it went into charge mode. I then booted and it's going into charge mode as it should. I'm back to square one again.
beartrap said:
Unfortunately I'm on my second photon. I exchanged the first for this reason.
Click to expand...
Click to collapse
That doesn't matter, you have every right to exchange it 283892 times until you get one that works. within the 30 days, It is in our contract. Not sure why people don't understand this. It doesn't matter where you get it, what store you get it from, Sprint, Best Buy, Radio ****, bob's electronics supply..you can get it exchanged. Personally, I wouldn't have even hesitated nor made this post, I would have just exchanged it.
Then made this post to say what happened to a photon I used to have. lol
EDIT: People need to speak up and let companies understand that you just won't settle. I come across customers everyday that just settle. I work for Comcast, talk to customers daily about things. I get, oh yea and then our internet sucks, and this doesn't work and oh yea this broke and we don't get this channel but we pay for it. My first question is, "Did you call?"....their answer, "Call who?"..or just "No". LOL I'm like, how the hell do you think stuff will get fixed if no one knows you have any problems? haha
You are the consumer, you have a lot of rights to the product you paid money for.
This is a great phone, but like all electronics some stores might get a bad shipment, it happens.
Good Luck with whatever you choose to do.
I have exchanged mine 2 times, 1 had a messed up screen, the other 1 had some problem that I couldn't make calls. So far this one is good to go! The Charm
-DJ
All,
I recently rooted my Rezound following the guide at (http://theunlockr.com/2012/08/24/how-to-root-the-htc-rezound-video/)
I had superuser app issues with the recovery image included with the instructions so I loaded Amon Ra 3.16 from here (http://forum.xda-developers.com/showthread.php?t=1339679) and the superuser app worked as it should. I kept the ROM stock.
Everything had been working fine but I did notice that my phone would be completely off at times when checking and I had to power it back up. Then today my phone rang but the screen was black and I could not answer. I pulled the battery and powered back up but it remained black. The phone went through its normal start up cycle from what I can tell because I felt a quick vibrate feedback upon power up. But again, nothing on the screen. I repeated this a couple of times even leaving the battery out for about 15 mins. Nothing.
Reading forums, it seemed like I was experiencing the same issues outlined here (http://forum.xda-developers.com/showthread.php?t=1339679) regarding the clockworkmod charging issue. The symptoms of seeing the orange LED for a few moments after inserting battery and trying to start up is what I see. I followed the instructions but I could not get "adb devices" to show my Rezound. I went ahead and finished the procedure thinking maybe this would work anyway. But still nothing.
I tried to get into HBOOT but cannot access.
I'm stuck...any ideas??
Thanks for your help!!
~kanin247
Is your battery charged? Do you see the charging light when it is plugged in?
joeymagnus1 said:
Is your battery charged? Do you see the charging light when it is plugged in?
Click to expand...
Click to collapse
The battery was not fully charged when I first noticed the screen would not come on when I received a phone call. Probably 40%.
And yes, I do see a charging light when plugged in...though it only illuminates for about 5 seconds and then disappears and never re-appears unless I unplug/re-plug.
I left it plugged in all night without any luck.
Thanks!
Might have a bad battery or connection. I have a PSP that will shut off after 15 minutes on the fully charged battery. But not when it's plugged in. Maybe you could go to a Verizon store and see if they have a battery to test it. Or you could pick one up on Amazon for like 8 to 10 bucks.
I'm no expert by any means. But that's what I would try
joeymagnus1 said:
Might have a bad battery or connection. I have a PSP that will shut off after 15 minutes on the fully charged battery. But not when it's plugged in. Maybe you could go to a Verizon store and see if they have a battery to test it. Or you could pick one up on Amazon for like 8 to 10 bucks.
I'm no expert by any means. But that's what I would try
Click to expand...
Click to collapse
Thanks! I ordered a battery and will see what happens.
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.