hey,
I'm new to all this so beer with me (my 1st smartphone)
I got a new moto g about a week ago and it worked like a charm,
but yesterday it started doing something wired, the battery indicator always shows that the phone i fully charged,
to the point where it shut its self down because it run out, and still showed battery fully charged.
any1 got any idea whats the problem?
Never meet with that kind of bug. Have you tried to re-flash the stock rom? It might fix the problem
A bit of a discussion going on in this thread. You may find something there.
well its not exactly the same problem, but anyway I did a factory reset and it solved it.
and now the phone was on all night and not connected to the charger and the problem returned, shows that the battery is fully charged again.
Related
I rooted my phone with Cyanogenmod 11 (nightly) two weeks ago, it was fine, no issues. On monday morning phone was fully charged, but with very little to no use it was completely discharged in 7 hours. When I connected phone to a charger (original and working) it didn't want to turn on, it did NOTHING, black screen. When I borrowed battery from my brother's S2 wich was charged almost fully, it booted KitKat but it showed that the battery has to be recharged. I put it back to brother's phone but it showed only approx. 15% less than before, it was okay. I tried charging my phone with brother's battery, but it was incredibly overheating , not like when you play games, I was afraid it was going to blow up. It is overheating even when phone is turned off and charging or even when normally turned on, on battery. I tried enabling airplane mode, I even installed stock ROM with Odin, but it is still overheating. It is not overheating near the camera but on the left side of the screen, I don't know what that chip is there for. Stock ROM now gives me error after 2 min. saying "Charging paused, battery temperature too high." Now my battery is discharged and phone is unable to charge it, only black screen again. Could this be done by rooting it with Cyanogenmod ? it was the only ROM that I installed through the step-by-step process on their site and for couple of days it worked fine. Is this a hardware issue that would occur even if I wouldn't root my phone, also is it somehow fixable, or would I need to change motherboard completely ? PLS HELP !
Yuki8san said:
or would I need to change motherboard completely ?
Click to expand...
Click to collapse
That.
So, I recently received my dad's old Galaxy S2. Stock JB, unrooted. My dad used to charge the phone in his car and during office time, whereas I've always been an "overnight" charger (keep this in mind as it's important). So, here's what happened -
1. I woke up really late the next day and realised that the alarm clock hadn't rung. checked out the phone beside me to see that it was really hot. The phone had shut down by itself. I turned it on and it functioned normally. That day I rooted the phone using PhilZ (mainly for the adfree app)
2. I didn't do an overnight charge for the next night cause my dad told me that "it ruins the battery". And the phone was fine the next morning. I changed to dorimanx's kernel for all the wonderful extra features.
3. That night, I decided to try overnight charging once again. Woke up the next day to a shock. It was 10am! No alarm, hot phone. I thought the phone had just shut down again, so i tried to switch it on. It showed the samsung boot screen and then the pretty "dorimanx" screen, but then.. stuck. the device wasn't starting, but recovery was working. I removed the battery, I wiped the cache, I installed another kernel (siyah)... nothing worked. FInally, I decided to try flashing a new rom. Downloaded SlimKat and flashed it through CWM. The device then booted up and has been working quite normally now. And I like SlimKat much more than stock! But that's not the point. The point is, I'm scared of charging overnight again.
None of my previous phones have faced this problem. I'm just a noob, but I have a theory. I noticed that the phone, once it reaches 100%, doesn't give any indication that it has stopped charging (like most phones do). The charging icon on the battery still shows. Does this mean that the phone is still trying to charge even after the full battery, which is causing the overheating and shutdown of the phone? I'm still confused regarding why it refused to boot up.
Is this a battery/device problem, or was this merely due to some fault in the stock rom?
You were actually stock in a boot loop (which has happened to me before(hated it). Be glad that it didntt freeze at the Samsung logo. Because then you couldn't get into the CWM.
I am not entirely sure what is wrong with your phones battery, because I have never had this problem myself, so I am sorry I can help you with that. Try going to settings/battery and see if you can turn sound on for the battery from there. :thumbup:
Sent from my SGH-T959V
Given the age of the battery it's likely to be the battery, so replace that first. Could also be the USB board, but cross that bridge when you come to it (try the easier option first).
Your old man is wrong about charging - constant charging/discharging like he did for however long is far more likely to reduce a battery's useful life than a simple use the phone during the day charge once overnight arrangement.
Hey everybody,
I am seeing strange charging issues on Lollipop, problems which are non-existent on KitKat. Every time I plug in the charger, the screen refreshes from time to time (it is way worse if I leave the DayDream function on, and worse on CM12.1 than on stock). Also the battery doesn't go all the way to 100% anymore, but it stops at around 82%. Given that I don't have this problem on KitKat, I am thinking this might be a software issue?
I am trying re-calibrate the battery and I am hoping this will fix the percentage issues. Still no idea what to do about the screen refresh thing. Any ideas?
georgecarstoiu said:
Hey everybody,
I am seeing strange charging issues on Lollipop, problems which are non-existent on KitKat. Every time I plug in the charger, the screen refreshes from time to time (it is way worse if I leave the DayDream function on, and worse on CM12.1 than on stock). Also the battery doesn't go all the way to 100% anymore, but it stops at around 82%. Given that I don't have this problem on KitKat, I am thinking this might be a software issue?
I am trying re-calibrate the battery and I am hoping this will fix the percentage issues. Still no idea what to do about the screen refresh thing. Any ideas?
Click to expand...
Click to collapse
reflash your Lollipop rom or flash another lollipop rom !
I have the same problem with lollipop. Stops charging around mid 80s percentage, with charge light flashing on and off rapidly. This is on stock 5.1.1 Rom and has been a problem ever since 5.x was released. Tried to RMA the device, but Sony says it's not faulty (after they fixed an unspecified electrical fault the first time around).
The only way I can charge to full now is using a 24 gauge USB cable to allow more power to be delivered to the tablet, but this was never necessary before with kitkat. Factory reset has no effect on the issue whatsoever.
Not sure what the exact cause is, but there is also a 44 page thread about it on the Sony support forum with pretty much no solid answers. I sincerely doubt reflashing will help us.
This is the thread btw https://talk.sonymobile.com/t5/Xperia-Z2/Lollipop-charging-bug/td-p/965384/page/44
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.
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
--yep mine too. I'm thinking it has to do with the heaying problem. Mine crashes and dies when there are many apps running/ wifi on with downloads while watching youtube., etc. another is when I recprd videos at 4k pr 720p for about 8-10 mins. My phone heats up real hard. I'll try resetting it and hopefully this fixes it. ps. Haven't done anything to my z5c yet. no unlocked bootloader, no root.,etc.
Same problem
I had the same problem
Device have charge (50,60,70 or more), show 0% and turn off.
Hardware problem maybe ???
any solution found?
hi,
I know it's been a long time you posted this but I'm currently facing that exact same problem.
Could you find any solution in the end?
Thanks
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
It looks like your battery is just dying. This was a common issue with Nexus 6p and other phones.
Resetting batterystats won't help... it doesen't have anything to do with it