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
Related
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?
Is there anyone facing the issue of there phone seemingly powering off but its still running and gets really hot ad you can see in the graph (also unable to wake phone up, but i know its on because it takes a good few seconds of holding the power button to turn it back on so to say) WITH CHUNKS OF BATTERY DRAIN!, ive wiped data, all caches, flashed different roms, different kernals formated SD, calibrated the battery, reset the fuel gauge chip, the lot but yet it still happens and draining massive battery percentages? It might happen twice a day, or once every two days... anytime!
Sent from my GT-I9100 using xda app-developers app
Another battery perhaps?
Sent from the little guy
Try using a different battery or calibrate the fuel gauge. Search the forum about it, these kind of threads pop up every other day.
Sent from my digital submersible hovercraft.
Hey dudes, yeah i tried a new battery and the fuel gauge chip already but it still happens i also bought betterbatterystats but it doesn't work on the ROM I'm using (jellybam 6.3)
Sent from my GT-I9100 using xda app-developers app
Jellybam? Flash another ROM.
Sent from the little guy
I updated my phone from gingerbread to ICS via kies, from there i flashed from stock ICS to a couple versions of resurrection remix, then to jellybam, and its been happening since i originally updated via kies
Sent from my GT-I9100 using xda app-developers app
Flash another ROM.
Sent from the little guy
Duplicate threads:
http://forum.xda-developers.com/showthread.php?t=2145124 "PLEASE HELP! Screen Flickering and S2 shuts down, already changed the battery."
http://forum.xda-developers.com/showthread.php?t=2169341 "S2 "powering" itself down with battery drain PLZ HLP!"
http://forum.xda-developers.com/showthread.php?t=2089248 "Battery problems after fleshing custom rom"
Looks like a lot of ppl are having this problem after going to JB.
I had same issues in my case it was ext sdcard. After changing sdcard everything is fine.
I am having the same issue! Galaxy S2 canadian international version (I9100M) with VirginMobile. I upgraded to stock JellyBean after flashing CM9 to stock ICS in order to upgrade from stock ICS to stock JellyBean via Kies.
When it happends, I can't wake the phone. The battery gets hot. I need to remove the battery in order to reboot. Also, it seems that my device is in a constant reboot cycle. Everytime I power it down it reboots, same goes when I remove the battery and put it back in, no need to touch the power button that the device is already booting. I went from about 70% down to 15%!
I can't post pictures now (seems that I need 10 message to do that).
I tried to remove my external 32gb SDCard. Will report if it changes anything!
Factory reset if you're able to get into recovery.
Sent from the little guy
I noticed my battery appears to have swollen slightly on both sides.
This is a very random thought - what if one something we've flashed (leaked ROM, bad kernel, ?) allowed the battery to be overcharged and has damaged it, or the battery controller permanently? Hence why we're all having problems.
Today my phone wouldn't finish turning on without the charger plugged in, despite saying it had ~25% battery life, it would turn off just after or just before entering the SIMcard unlock PIN.
battery swollen = near battery death
Sent from the little guy
Im also having this same problem with my battery, and I bought a new battery today but it still showed the ridiculous remaining times and even shut down on me again even tho this is a new battery, i changed to JB 4.1.2 when this started happening and i tried reflashing it with official JB through Kies but the problem is still there so it has to be something with the JB firmware itself but what exactly is causing it i dont know.
A lil help with solving this will be greatly appreciated cause it is getting frustrating having a battery at 100% but the time on the battery status shows only (2 - what ever random weird time it has) minutes remaining until it shuts down.
gennocyde said:
Im also having this same problem with my battery, and I bought a new battery today but it still showed the ridiculous remaining times and even shut down on me again even tho this is a new battery, i changed to JB 4.1.2 when this started happening and i tried reflashing it with official JB through Kies but the problem is still there so it has to be something with the JB firmware itself but what exactly is causing it i dont know.
A lil help with solving this will be greatly appreciated cause it is getting frustrating having a battery at 100% but the time on the battery status shows only (2 - what ever random weird time it has) minutes remaining until it shuts down.
Click to expand...
Click to collapse
I've been experiencing the same problem with my SGS2's battery and noticed that it is getting bloated. I purchased a new one to prevent severe damage on my mobile phone.
gennocyde said:
Im also having this same problem with my battery, and I bought a new battery today but it still showed the ridiculous remaining times and even shut down on me again even tho this is a new battery, i changed to JB 4.1.2 when this started happening and i tried reflashing it with official JB through Kies but the problem is still there so it has to be something with the JB firmware itself but what exactly is causing it i dont know.
A lil help with solving this will be greatly appreciated cause it is getting frustrating having a battery at 100% but the time on the battery status shows only (2 - what ever random weird time it has) minutes remaining until it shuts down.
Click to expand...
Click to collapse
I've been experiencing the same problem with my SGS2's battery and noticed that it is getting bloated. I purchased a new one to prevent severe damage on my mobile phone.
ielle227 said:
I've been experiencing the same problem with my SGS2's battery and noticed that it is getting bloated. I purchased a new one to prevent severe damage on my mobile phone.
Click to expand...
Click to collapse
It's worse enough you post this on every battery related tread, now you're posting it twice on the same tread? Why?
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
DubAholic said:
It's worse enough you post this on every battery related tread, now you're posting it twice on the same tread? Why?
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
Click to expand...
Click to collapse
i'm sorry, i did not notice that i've posted it twice on the same thread.
ielle227 said:
i'm sorry, i did not notice that i've posted it twice on the same thread.
Click to expand...
Click to collapse
It's enough to post it on 1 battery related tread, you're not helping anyone by posting it on every tread
Normally people search before they post, so if they have the same problem as you they will notice your post even if it's on only 1 battery related tread
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
DubAholic said:
It's enough to post it on 1 battery related tread, you're not helping anyone by posting it on every tread
Normally people search before they post, so if they have the same problem as you they will notice your post even if it's on only 1 battery related tread
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
Click to expand...
Click to collapse
thanks for the feedback, haha.. :silly:
Hello,
I bought my Samsung gs2 just over a year ago. I had issues with the battary life all the time (It sometimes lost 20% in a few minutes without reason), but many other gs2 users have similar problems, so I just ignored it. 2 weeks ago, after I unplugged it, it suddenly lost 90% of the battery in an hour, and got extremly hot (the heat wasn't coming from the top of the phone where the cpu is, but from the middle of the it). I shut it down and removed the battery. When I switched it back on it had only 1% left. Now it is completely dead.
The Battery is working properly in my brothers phone, and I reproduced this with 2 other batteries. I suspect there is some kind of hardware damage. When I try to charge it, it displays an overheating alert (both switched on and off), and doesn't charge at all. Now the battery is so low, it doesn't display anything any more.
Unfortunately I installed a custum ROM (wanam lite), because I tried to solve the battery issues, so Samsung won't repair it.
Can anyone please help me keeping the phone alive long enough to flash the original firmware?
Thanks in advance!
do you have any symptoms for a faulty usb port? as for flashing a stock rom just fully charge it (turned off) boot in download mode and fire away... or is it draining your battery in download mode too?
I have the same problem with my white S2 i9100T, sent back twice to repair, just got it back one week ago, finally the battery problem is gone! Last changed is the mainboard, first repair they swaped the battery and updated software(already latest firmware, what the hell they tried to update?).
My phone is just over a year old as well, it has battery problem since first day and only fixed now. As I know only the one made in Vietnam has this problem so yours made in Vietnam probably you will need to replace the mainboard. I am using a 2 yrs old black S2 made in Korea, exactly same model, very stable and never fail, that Vietnam one keep having unexpected behaver, another friend's Vietnam one is the same, recently another friend got one made in China, so fast so good.
Thanks for your replies. Unfortunately My phone seems to drain the battery even when switched off, and it isn't possible to charge it, no matter whether it is on or off. So my only option is to ask somone else to charge the battery, and then try flashing the original software. How long do you think flashing will take? Even if the battery is fully charged, I don't have power for more than half an hour.
Another question: Does anyone know if it is possible to reset the flash counter without booting the phone? I doubt that I will have enough time to install triangle away...
do you have better battery stats? It'll tell you what the problem is more accurately.. I just check it when I have battery issues
genesis0403 said:
do you have better battery stats? It'll tell you what the problem is more accurately.. I just check it when I have battery issues
Click to expand...
Click to collapse
BBS does not tell you a thing about hardware problems buddy.
Sent from my HTC Desire using xda premium
---------- Post added at 09:36 PM ---------- Previous post was at 09:32 PM ----------
I have the same problem recently. I am hoping it is the charging board... new one should be arriving this week. If that doesn't do it I am resigned to the fact that my phone's main board is faulty and it's time to upgrade.
Sent from my HTC Desire using xda premium
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).
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.