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:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
jt.61 said:
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
122ninjas said:
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
Click to expand...
Click to collapse
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
mistabeo said:
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
Click to expand...
Click to collapse
Try to go to stock and see if the problem persists. If it does obviously a hardware issue
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
mistabeo said:
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
Click to expand...
Click to collapse
you know samsung has factory warranty for that kind of stuff.
i got my phone refurbished, about 9 or so months ago.. it only came with 3 months for the warranty. i guess getting a returned phone ended up biting me in the ass.
now the phone is overheating when im charging it.. looks like it's going to crap out on me soon.
Download the stock 2.3.4 firmware from the download repository. Do a full wipe including system data cache and dalvik. Boot into download mode hook up Odin and flash the stock firmware. If its a hardware issue your problems will persist in which case u could sell it on eBay for parts. If its a software issue that will fix it.
Sent from my SGH-I777 using xda premium
that's what i'll probably have to do tomorrow. if i remember correct, rooting the phone on 2.3.4 wasn't that straight forward, so i'd have to read up on how to do that again. but im just gonna leave it as is right now.
the phone acts really weird. when i took out the battery and replaced it with another one, it would keep doing the same thing. so then i plugged the phone into the USB charger and tried turning it on - that worked.
if it's a hardware thing, it's got to be something to do with the battery sensor. the phone is simple to remove, so i wonder if i can replace it myself.
i believe my phone is now semi-FUBAR.. it still runs, but seems like the battery sensor issue is a hardware one. i just tried doing a stock flash/odin thingy, and it still has the same issues... also, the phone is now permanently showing as MTP connected. i am also seeing decreased battery life.. only lasts about 1/2 a day now.
i guess i learned my lesson.. don't switch out the batteries too often, or your phone will die.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
Click to expand...
Click to collapse
is this a big deal? i'm also having samsung i9100? im using ucle5 AJ's rom/kernel.
i'm also having issues with charging the phone. it seems to charge forever, i have to unplug and plug the charger again to properly charge it.
When it says i9100 it means you tripped the flash counter. If you want to reset it use a triangle away app.
Sent from my SGH-I777
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
bubuty said:
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
Click to expand...
Click to collapse
No the same principle does not apply. Battery state wiping has no effect on this phone.
Sent from team Pirate! Using Tapatalk 2
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Are you undervolting/ under clocking this can cause a sod
Hi. Nothing like that, just used neat Rom or disaster Rom as they come.
sent from my Westcrip powered S2
Your phone(battery) has insane gauge chip search for this it answer in your question(it's only for battery)
Happy new year
Paulius
Hi, thanks for the reply. I'm not sure my issue is to do with the guage chip directly, as my phone will switch itself off at any battery level. The issue designed in the other thread its having something like 56% and then having a much lower value after an intended reboot.
Shutdown it's called sleep of death( scary name) but it not death it's just sleeping forever... it problem with your kernel and battery problem is insane gauge chip...
Happy new year
Paulius
I've just charged to full charge, unplugged - and within 2 minutes, the phone froze, could not do anything - so i pressed the power button until it went off, and it booted back up again without me doing anything - when it booted, it showed i had 2% battery. Then it did the same thing, froze, i had to reboot - then it showed 37% battery.........no idea what's going on apart from maybe a faulty battery...
Buy new battery. It was here on the forum a few times.
Yes. When phone hot(sometimes not) it take battery about 50-60%(I don't know exactly) but sometimes it add battery...
If you flash siyah kernel with stweaks(5 version) you can reset it but chip do funny thing even you reset...
Happy new year
Paulius
try Battery caliberation app ...
if it doesnt work buy a new battery
What are you talking about ? It's not battery Fault it's Insane Gauge Chip.... And Battery Calibration not helping...
I decided to go the whole hog and go back to a stock unrooted ICS, after wiping everything, then CFRoot - then reinstalled Neatrom light - currently restoring apps via Titanium - fingers crossed...
I think you don't have anymore BSOD But if you have flash Syiah kernel
Try new kernel and reset fuel gage
Try installing a new kernel like siyah or dorimanx and then reset your battery log this should resolve your problem if not buy a new battery.
karfeef said:
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Click to expand...
Click to collapse
I think I have a very similar issue. The randomly reboots happens several times a day, it does not happen though when charging (never). By now I'm on jb leak and still have the issue. When it shuts down, the sreen dims a bit and then it's gone, the weird thing is that often I have to pull the battery or charge the phone before reboot is possible, the battery shows different values after rebooting, sometimes close to what was before (especially when rebooting on charger), and sometimes way off the values before. I came initially from slimrom with siyah or dorimanx kernel, I really hoped jb leak would help (also tried different kernels), but it didn't. It also seems to me that it happens more often with the sd card (32gb) and without the phone seems more stable, but still it happens from tme to time. Once the screen dim (only one or two steps) and shut down even happend when in CWM recovery, is it maybe hardware related? It's very hard to find the source of the problem, anybody else experience similar issues? By the way the shutdown I have is not a proper shut down, the phone doesn't show the message "is shutting down".
I've completely wiped, used Odin to go back to ics stock, installed cfroot, then installed neatrom light. Had the same issue, so I've installed siyah, and used stweaks to reset the battery fuel gauge. I've only been off charge for 10 mins so far, but normally it would have shut down by now, so here's hoping...
sent from my Westcrip powered S2
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
karfeef said:
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
Click to expand...
Click to collapse
I had the same problem - SOD several times a day. I change the batery with a fresh new samsung 2000 mA one.
Unfortunatelly SOD came back, but I found a trick: turn off WiFi. Use it only manually.
For the past 3 months I succeded to have 0 SOD's.
I know that manual WiFi is a setback but it works with those experiencing SOD.
Hope it will be usefull.
Secuence of events that happened BEFORE the problem started:
1-Had a working rom of CM7.2
2-Battery was going out too quickly (7 hours or so) therefore I tried wiping battery data
3-Charged the phone
4- Unplugged it, took a picture
Problem:
One hour later I realised it was turned off...
I turned it on again, it turned off soon afterwards
for a moment it had a problem turning on (it wouldn't go past the cm logo)
afterwards it was even worse; it turned off before even passing the first logo, I couldn't even get it to recovery mode.
Solution Attempt no.1
Tried to get it to stock rom with Odin.
I was able too... but the problem persisted in the new Rom.
Solution Attempt no.2
Tried to get another rom
My situation NOW
I'm back on stock Rom. If I leave my phone alone for like an hour or so it works for 20/30 secs before turning off... After that the problem gets worse till I cannot boot.
Any ideas guys?
How old is the battery? There are apps on playstore to check your battery, thats where I would start. It doesn't sound like a Rom problem, sounds like hardware.ie battery first. Gluck.
Sugartibbs said:
How old is the battery? There are apps on playstore to check your battery, thats where I would start. It doesn't sound like a Rom problem, sounds like hardware.ie battery first. Gluck.
Click to expand...
Click to collapse
Can't have the phone on for 1 minute, forget about downloading and using an app from the store...
I don't know if it's a hardware problem since it happen really suddenly...and just the day after I resetted the battery stats ..... Maybe it is a hardware issue but I want to be sure I tested everything first
Hey, maybe you moved on but I was having the same issue on every ROM.. stock or not. being the detective I am I investigated and inspected.
One of my battery connecting pins is loose even though it's pressed tightly in the case any moderate amount of force or impact loosens it from the contacts.
My temp solution for you would be to add something to the back cover to apply enough pressure to keep the battery still or resolder the copper connectors. The first being easier.
Hit thanks if that helps.
Invest in a new battery. Simple solution.
Sent from my SGH-T959V using xda app-developers app
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.