Since the 5.0.2 update (First with the .690 generic baltic version and now the US .726 version) charging has become nothing short of enigmatic.
Almost every night when I charge it, I wake up to between 75 and 90% battery, with the charging LED completely off and no charging occurring. For some reason, twice (one randomly and one the night after updating to .726) it charged fully and normally showing the green LED in the morning, but I cannot for the life of me figure out what I did differently.
This isn't a make or break issue since I still get 3+ hours of screen on time and a full day's use, but my OCD wants to kill everything because of it. I've tried downgrading to 4.4.4 (/314 version I believe) and it worked perfectly and charging was normal each time I tried.
If I try replugging the cable in after it has stopped, the LED flashes on and off and the charging notification does as well rapidly. The phone begins to heat up and any open apps begin to "refresh" as if they've been reloaded from memory.
Any help would be appreciated, since I've already tried draining to 0 and recharging. I haven't seen any other issue like this on the internet at all, and I've been searching since day 2 of the 5.0.2 update.
Shayded said:
Since the 5.0.2 update (First with the .690 generic baltic version and now the US .726 version) charging has become nothing short of enigmatic.
Almost every night when I charge it, I wake up to between 75 and 90% battery, with the charging LED completely off and no charging occurring. For some reason, twice (one randomly and one the night after updating to .726) it charged fully and normally showing the green LED in the morning, but I cannot for the life of me figure out what I did differently.
This isn't a make or break issue since I still get 3+ hours of screen on time and a full day's use, but my OCD wants to kill everything because of it. I've tried downgrading to 4.4.4 (/314 version I believe) and it worked perfectly and charging was normal each time I tried.
If I try replugging the cable in after it has stopped, the LED flashes on and off and the charging notification does as well rapidly. The phone begins to heat up and any open apps begin to "refresh" as if they've been reloaded from memory.
Any help would be appreciated, since I've already tried draining to 0 and recharging. I haven't seen any other issue like this on the internet at all, and I've been searching since day 2 of the 5.0.2 update.
Click to expand...
Click to collapse
No one?
Have you tried a clean install?
i've been using .690 for a month and i'm currently using .726 and i have no problem with charging.
myrums said:
Have you tried a clean install?
Click to expand...
Click to collapse
I have on multiple firmware versions, even reverting back to the original out of the box one (4.4.2).
So far, 5.0.2 is the only firmware that gives this issue (although 4.4.2 had completely separate overheating issues unrelated to charging)
what charging method u use? magnetic or just a normal usb charging? Have you try with another charger/plug/usb cable? And one more thing, try clean install to avoid any bug from previous rom. I prefer using flashtool. :good:
yuskhayru said:
what charging method u use? magnetic or just a normal usb charging? Have you try with another charger/plug/usb cable? And one more thing, try clean install to avoid any bug from previous rom. I prefer using flashtool. :good:
Click to expand...
Click to collapse
I've tried both magnetic as well as usb, same results.
I've tried every combination of cables and wall plugs that I can, still no dice.
And I tried a clean install, nothing changed. Honestly it feels exactly like a firmware specific bug, yet no other person has had this problem. I think I'll just end up dealing with it until 5.1 comes out for the Z2.
try to completely discharge the battery, just keep using it until it completely dies, and chage it a full charge with a good charger and see
karim-ps said:
try to completely discharge the battery, just keep using it until it completely dies, and chage it a full charge with a good charger and see
Click to expand...
Click to collapse
That was the first thing I tried, no change.
Same here! Netherlands non-brand version, I have issued a repair with sony. But I think it is a software bug.
why don't you back up your data and do a complete wipe and flash a 4.4.4 ftf, if it doesn't help then it's your battery pack started acting up, I have come across multiple defect batteries this week.
karim-ps said:
why don't you back up your data and do a complete wipe and flash a 4.4.4 ftf, if it doesn't help then it's your battery pack started acting up, I have come across multiple defect batteries this week.
Click to expand...
Click to collapse
As stated before, I've done complete wipes already (I don't keep much on local storage so backing up important files is simple) and 4.4.4 has never had this issue. 5.0.2 is the only ftf that gives this issue, whether it's a clean wipe install or done as an "update" so to speak.
For now, you'd better stick to 4.4.4 as there is nothing special about 5.0.2, and also 4.4.4 is a perfect, bug free FW
karim-ps said:
For now, you'd better stick to 4.4.4 as there is nothing special about 5.0.2, and also 4.4.4 is a perfect, bug free FW
Click to expand...
Click to collapse
Tried to downgrade back to 4.4.4 (the same version that had no issues before) and ended up seeing the exact same issue.
Still not sure of the cause, because once every now and then it DOES decide to charge to 100% without issue, but I have a free extended warranty through my work (we sell phones lol) so I'll just deal with it until it's unbearable and get it "fixed" (we mostly just get a new device).
Related
I'm hoping someone can shed some light on this problem.
I've been using my X10 Mini running CM7-2.2.0 for internet access (both USB tethered and Wi-Fi hotspot) for the past couple weeks while traveling. About a week ago I started having problems with the phone randomly shutting off during an internet session (usually preceded by a single vibrate). It's gotten progressively worse. Whereas at first it was only happening after surfing the internet for awhile, now it's at the point where I can power on the phone in airplane mode and use it for awhile, but as soon as I turn on the GSM or 3G radio, the screen simply goes dark and the phone is off.
I suspect it's one of two problems: either there's a power issue, or the phone (particularly the GSM/3G radio) has become defective. To back up the theory that it's a power issue, I've noticed some strange things with the battery and it's reported charge level. Today I left the phone plugged in while off (charging from the USB charger for my Kindle, which outputs 850mAh). After a few hours the screen showed it as being fully charged. Then I turned on the phone and it said the charge was 33% percent. Still, even if it was only 33%, as soon as I turned on the 3G radio, it died.
I've tried charged with 2 different microUSB cables, one supplied with my Amazon Kindle, one from a Nokia phone, so both are quality cables. I don't have the original charger and cable with me to try those, but it seems like I should be able to get a charge between 2 decent cables, 1 wall charger and the USB ports on my Thinkpad laptop.
I did try doing a wipe and factory restore of the MiniCM7 ROM just in case, and also tried reverting to a previous MiniCM7 version just in case that one would be problem free, but it's no different.
I guess there's a 3rd option: could it be an issue with the nAa kernel?
Any help or input is appreciated.
Something similar happened to me when i was on MiniCM7-2.2.0
It's definitely an issue with the ROM, not the kernel.
I went back to stock with xrecovery and did a couple of battery-calibrations (drain the battery, charge it on the wall-charger and do a battery-stat wipe when starting up the phone again)
I still can't get a 100% full charge and when the batterylevel sinks below roughly 30 percent getting and making calls results in the same behaviour as your phone (forced shutdowns), but i have a half-decent batteryperformance again.
I have a strong feeling that MiniCM7-2.2.0 doesn't like usb-charging very much, but i don't have any hard evidence to back that up, but i know some other people have the same sort of issues.
It's definitely not the kernel itself, becaue i'm using it now with a different rom for testing and the battery behaves roughly the same as on stock firmware. If you get your battery back to decent performance (don't think it will ever be completely good again), earlier versions of MiniCM7 don't seem to have this particular issue, so stay away from MiniCM7-2.2.0.
That's about all i could advice you, it seems to be the only rom that displays this particular behaviour.
Great to hear at least someone has had this problem. Have you tried other Gingerbread ROMs, such as GingerDX?
Thanks very much for your input.
Yes, i've tried GingerDX, quite like that one too, and i've tried MiniCM7-2.1.9, which is one version older than the 2.2.0, I'm testing a new one now GIngerZaraki, and none of those seem to have this particular issue.
Did you post in the MiniCM7 thread regarding the issue? Just wondering if I should pos there about this. This seems like a very serious issue if it is to do with the ROM. I just tried restoring MiniCM7 2.1.7 and I'm having the same problem though (although ometimes the phone just shows no signal rather than crashing). I also tried reflashing the kernel, but no luck. Right now I'm thinking stock ROM is my best bet.
It needs some time to get it back up working well, let the battery drain till about 10% and then charge it in one go until 100, that will probably take a short time because your battery won't accept full charge yet. Turn the phone on and reset the battery-stats in recovery, if you boot into the rom you can see the percentage, you can charge it again to 100 and repest the process, it took me about a week.
And i think there are posts about battery-issues in the MiniCM7 thread, but i'm not sure how much work still goes into that, since nAa is busy with MiniCM9 and the new kernel for ICS.
I've restored it back to original 2.1 ROM in factory restored state and thankfully the GSM/3G radios are working again. Only problem now is that Wi-Fi won't turn on, giving me an "unable to start Wi-Fi" error when I try to turn it on. Did this happen for you, SmG, in that first week of battery recovery?
kentchristopher said:
I'm hoping someone can shed some light on this problem.
I've been using my X10 Mini .........Any help or input is appreciated.
Click to expand...
Click to collapse
Well i think you are totally new to using this ROM so this issue is raised i have been using this ROM since the release.
There is no such Issue.
The actual issue that might happen (also happened in your case) is Flashing error, that means Bootloader is cracked, Kernel is flashed and rom is flashed but there was some minor glitch which got skipped and Flashing got successful, so you will have the problem even after factory resetting.
Here is what you should do Download Bootloader, kernel, ROM again. Delete old Files and use new ones to Unlock BootLoader Reflash the MiniCM Kernel and Flash The ROM, then go to recovery Wipe dalvik Cache,Battery Stats and then factory reset via recovery, after doing that everything should work fine.
also Xperia X10 Mini is not made for Tethering so if you use it you might get those problems again, try to avoid it.
if the problem persists install SEUS factory reset your mobile and update it by the SEUS or PC companion even if it says you have latest version, it will make your mobile factory reset.
I've been using CM7 since last year and 2.2.0 since its release. I have tethered before without problem though that was probably 2.1.7 and with less extensive use.
I ca say that the problem persists even though I am now back on stock 2.1 ROM. Wiped system before restore, wiped Dalvik cache, wiped battery stats, restored 2.1 and flashed stock kernel. I guess this means the problem has to be the bootloader?
As for repair with SEUS or PC Companion, I tried both and there is no way to force repair -- at least with CURRENT versions, and the versions I have won't run without an internet connection and you are forced to update. When run, both said I have the most curent version of the software on my phone and no option to repair anyway. I think this is a change from previous versions, but if you don't believe me, please try it yourself. Maybe I need to relock the bootloader?
Thanks for your input.
To follow up on this, the underlying issue seems to have been a my battery. Having just swapped out the original battery for my own self-built replacement, it seems to be working absolutely fine.
My battery life was fine before this issue. My theory right now is that the extensive tethering and internet use I was doing on the CM7 2.2.0 ROM and, most importantly, the heat that it was creating (I remember the phone getting hot) brought about a rather sudden death to my battery (heat being a known killer of battery health).
Download the battery calibration app,charge to max and leave it plugged in. Enter the app and see how many mv the battery is emitting. It should be 4200 at full charge.
Sent from my E10i using xda app-developers app
aloy99 said:
Download the battery calibration app,charge to max and leave it plugged in.
Click to expand...
Click to collapse
I assume you mean that I should do this with the old battery? Not really an option anymore since I clipped its cable to use on my new DIY replacement battery. However, back when trying to solve this problem, I did wipe the battery stats both from Battery Monitor (app) and from CWM recovery (separate occasions) and did full discharge/recharge cycles to calibrate. Obviously it didn't help, and I think it may have actually made the problem worse.
Same problem here, wifi Not working after relocking bootloader on my x10mini.
:crying:
After updating to ICS I cannot charge my phone while it's off.
I always charge the phone during the night and never let it fully die but today I didn't see that the battery level is so low and my phone died now I cannot turn it on to charge it. I get constant reset, my LED flashes blue/red and it resets non stop.
2 nights ago forgot about that problem and woke up at 3 o'clock to find out that my phone has been restarting for about 4 hours.
Give any advice.
P.s. My girl's also with Neo, also updated to 4.0.4, same problem there...
A quick video to show the issue: http://youtu.be/ajwFwEeg0gY
DNDimitrov said:
After updating to ICS I cannot charge my phone while it's off.
I always charge the phone during the night and never let it fully die but today I didn't see that the battery level is so low and my phone died now I cannot turn it on to charge it. I get constant reset, my LED flashes blue/red and it resets non stop.
2 nights ago forgot about that problem and woke up at 3 o'clock to find out that my phone has been restarting for about 4 hours.
Give any advice.
P.s. My girl's also with Neo, also updated to 4.0.4, same problem there...
A quick video to show the issue: http://youtu.be/ajwFwEeg0gY
Click to expand...
Click to collapse
I just found out after reading your post that I have the same problem but I removed some app so don´t know if has anything to do with removed app!
Downgraded to GB and you can charge your phone normally. After be careful to don´t let your phone battery complete drain.
I am trying some roms besides official to see if I found out one that can allow charging in off mode. Is annoying this….
EDIT1: I just made a clean update from GB to ICS without removing any app or installing any different kernel and is charging in off mode.
So this behavior any something to do or with removed app or with different kernel installation!
Have to find out.
EDIT2: No. Is not Kernell issue or Super User that I just flash by CWM. So last option is any removed app or eventually any combination of factors.
Yes, I am in the process of downgrading, good thing is that we have two Neo's so I can use the other one's battery
Dudes! I managed to charge my phone but darn it wasn't easy.
Now one of these is on the way: http://www.ebay.com/itm/190586739151?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649
Are you sure it's a hardware issue, because I've tried 4 different ICS ROMs (Stock ICS, JJDoctor's, KA20 and AOSP 4.0.4) and I've been able to charge my phone while off in all of them.
Maybe getting your phone to a service center will find the culprit.
Akath19 said:
Are you sure it's a hardware issue, because I've tried 4 different ICS ROMs (Stock ICS, JJDoctor's, KA20 and AOSP 4.0.4) and I've been able to charge my phone while off in all of them.
Maybe getting your phone to a service center will find the culprit.
Click to expand...
Click to collapse
Is not a hardware issue.
I also had the same problem but now I don´t!!!
I downgrade to GB and flash ICS again and problem is gone.
Why? Don´t know.
Probably is a combination of things.
I never said anything about hardware issue. At least don't remember it.
After flashing back to GB and upgrading to ICS the problem was gone until I removed all apps that don't use directly from system/vendor/app
Now I cannot charge again but hopefully I won't leave my battery to totally die again.
chargamon file nuff said
Sent from my Xperia neo using xda premium
Chargemon, if I'm not mistaken, is replaced when installing cwm. This means I should be facing this problem as well. Let me check...
Sent from my MT15i using XDA
EDIT: I couldn't replicate the problem. The phone started charging normally when off. A few seconds in the light went from green to red, but I think it recalculated the battery from 90% to 89%, hence the switch. Perhaps this only happens when the battery is fully drained?
I upgraded to JellyBean 4.1.2 using the recently released Spanish version. All seemed fine at first, but in the last week or so, the phone has taken to switching itself off without warning. On restarting, it claims to have no battery left, no matter how much was actually remaining. After one or more reboots - or after plugging it into to a charging source, it will revert to normal working, with the previous charge level.
This could be a hardware fault, a failing battery - or could it be a consequence of a flaw in the upgrade process? All suggestion welcome.
Try factory reset, fresh install or another kernel.
Also try searching.
alecxm said:
I upgraded to JellyBean 4.1.2 using the recently released Spanish version. All seemed fine at first, but in the last week or so, the phone has taken to switching itself off without warning. On restarting, it claims to have no battery left, no matter how much was actually remaining. After one or more reboots - or after plugging it into to a charging source, it will revert to normal working, with the previous charge level.
This could be a hardware fault, a failing battery - or could it be a consequence of a flaw in the upgrade process? All suggestion welcome.
Click to expand...
Click to collapse
I have had same problem some time ago. Phone was restarting or switching off with no reason. Also weird battery levels.
Restarts and switching off issues has been resolved by changing to different kernel. Reflashing should help too.
Weird battery levels i have sorted out by reseting battery gauge available in STweaks. I did it when phone was fully charged. Then i've discharged it to 0% and charged again. I have no problems since then.
alecxm said:
I upgraded to JellyBean 4.1.2 using the recently released Spanish version. All seemed fine at first, but in the last week or so, the phone has taken to switching itself off without warning. On restarting, it claims to have no battery left, no matter how much was actually remaining. After one or more reboots - or after plugging it into to a charging source, it will revert to normal working, with the previous charge level.
This could be a hardware fault, a failing battery - or could it be a consequence of a flaw in the upgrade process? All suggestion welcome.
Click to expand...
Click to collapse
Run the batt till it's off, charge it while it's off till 100%, remove the battery for 90 + seconds, insert batt and you should be fine.
Sent from the little guy
alecxm said:
I upgraded to JellyBean 4.1.2 using the recently released Spanish version. All seemed fine at first, but in the last week or so, the phone has taken to switching itself off without warning. On restarting, it claims to have no battery left, no matter how much was actually remaining. After one or more reboots - or after plugging it into to a charging source, it will revert to normal working, with the previous charge level.
This could be a hardware fault, a failing battery - or could it be a consequence of a flaw in the upgrade process? All suggestion welcome.
Click to expand...
Click to collapse
Thanks to all who have replied, also apologies - TheATHEiST, you are right, although I had searched, I obviously didn't do a very good job, as after I tried a second time, I found a thread with many references to this problem and some possible solutions.
It seems that both in this thread and others, any of the possible causes - and any of the claimed successful solutions - may work. So I guess my best plan is to work through them, starting with the least disruptive.
Thanks again - this is without doubt the definitive forum for issues with these phones.
AW: [Q] battery cutting out
Hy i have a problem i can not understand speaking so good english my answer is
I intsall the new software from foxhound 2.0 version and on the new software i become not warning about the battery when is under 15% on the version 1.9 was normal when is under 15% or 10% or 5% i become warning tone
What must i do to become warning when is under 15% ?
Please write me in a easy english or when is going in german language thanks very much
Sent from my GT-I9300 using xda app-developers app
Is anyone else experiencing this on LP roms?
I'm currently on 5.1.1 and if I unplug from the charger, the LED stays on and the battery percentage icon continues spinning as if it is charging.
When this happens, the battery drains abnormally quickly unless I reboot to get rid of it.
It also stops it from charging if I plug it back on the charger.
Extremely annoying, I might try reverting to an older 5.0 ROM and see if it still has the problem, maybe it's my device and not the ROM but would love to know if anyone else has come across this problem...?
obviously you're on a custom rom since the Z2 doesn't have 5.1.1 yet, so which one ?
I've recently tried multiple 5.1 roms, but never had this issue, but maybe it came up in newer builds, not sure.
You could try using other 5.1.1 rom to see if you still have the same issue. If it doesn't then you can inform the developer of your rom
thanks people's
Yes, a custom rom, I tried several other new roms and they are all exhibiting this problem for me.
I also tried reverting to a previous backup of a different 5.0.1 ROM and the problem still exists, and I'm sure the problem wasn't in that ROM when I originally used it so maybe it's coming from somewhere else.
I might try reverting to a stock rom and see what happens
behelit said:
thanks people's
Yes, a custom rom, I tried several other new roms and they are all exhibiting this problem for me.
I also tried reverting to a previous backup of a different 5.0.1 ROM and the problem still exists, and I'm sure the problem wasn't in that ROM when I originally used it so maybe it's coming from somewhere else.
I might try reverting to a stock rom and see what happens
Click to expand...
Click to collapse
Repair with PC companion or flashtool with stock ftf
I have this LED problem even on my stock phone 4.4.4 and 5.0.2. haven't noticed battery drain
I think i have narrowed it down to a bad usb cable(s) not supplying enough power to charge the phone. I have replicated this many times
I don't think it's the cable, I've tried multiples and it will charge fine using the magnetic adapter, I can also access the device files without a problem (MTP/ADB).
I've flashed the latest stock ftf (specifically D6503_23.1.A.0.726_UK+Generic.ftf) and it now shows the newer charging screen when the phone is off and plugged in, but it still has the same problem. Even when powered off it doesn't charge properly, the percentage just goes down even though the LED is on and the screen says charging. If I unplug the usb cable the light stays on and it still indicates as charging and drains abnormally.
Thought I should also mention, no matter what ROM I use (stock/custom) the auto-rotate behaves weirdly and the screen will auto rotate even when the setting is off.
Edit:
If anyone else if having this problem, it is most likely due to the magnetic charger damaging the board:
http://forum.xda-developers.com/xperia-z2/help/usb-charging-data-connection-t2845629/page2?nocache=1
Hopefully this is covered by warranty
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.