Related
Hey, since rooting my Eris, the phone is running hot. It also is not charging past 30%. I have tried wiping and reloading Ivanv07 rom as well as trying the Sense-able 0.7. The phone was on the charger overnight, and now only has 13% charge. I tried setCPU to throttle it down, but it was not able to change the settings despite having root access. Has anyone else experienced something similar/found a fix?
probably a bad battery. try getting a new one.
or do you mean that is started happening immediately after rooting? if so, never heard that before so dunno....
go to add widgets, htc widgets, get more widgets
Use that batter widget and tell me the battery temp, then see if it rises or lowers with useage.
It started happening right after rooting. The battery has gotten up to 50C, and that was just while charging with all Apps closed using ATM.
The only time my battery gets over 50 C is if i am running wireless tether and usb charging. And it will not charge over about 40 %.
Go get a task killer and make sure the tether program isnt running.
It was getting up to 50C without any tasks running, the ATM I mentioned before was for Advanced Task Manager. I ended all apps and services, and it still ran hot. Did not even install wireless tether yet. I tried to reflash PB root image, but hboot tells me now that "Battery voltage is too low" to proceed.
Mine did that once yesterday on the wall charger but I was on 5.5. It acted as if it discharged the battery. It was a fluke and hasn't happened since. I have noticed that the phone when I turned it on will not charge till it is fully booted into the os.
Ok, I found that the battery does seem to charge if plugged in with the phone off, and without the heat issue. One odd thing is that when charging, the battery symbol has its little animation, but when this issue I've been having seems to be going on, it is like the animation for that symbol is frozen. Everything else on the phone seems to be working fine.
tbertoli said:
Ok, I found that the battery does seem to charge if plugged in with the phone off, and without the heat issue. One odd thing is that when charging, the battery symbol has its little animation, but when this issue I've been having seems to be going on, it is like the animation for that symbol is frozen. Everything else on the phone seems to be working fine.
Click to expand...
Click to collapse
reboot into recovery and go to wipe and wipe battery stats
see if that helps
Mine did that (not rooted latest 2.1) and I have to go in and stop the Bluetooth Share app in App Manager. Does that for each reboot. It's weird.
Ok, I think I resolved the issue. I redid the entire root, recovery flash, image load process and actually got the battery to fully charge, though it still charges pretty hot.
The 1st time, the only thing out of the ordinary was that I accidentally went into the root image's recovery console, which froze the phone. I had removed the battery, reflashed the custom recovery, and everything looked good from there, except the battery issue, the heat, and neither wireless mac or bluetooth mac would show.
After redoing the entire process, the macs are showing up for me, which seems to point to clearing up the issue. Will post more if there is still a problem.
@timmywa I did notice that too, and it kept starting the service again after I would end it.
Not 2.1 root but some battery quirks
Well I had a strange issue today, well two actually.
First has happened with my g/f eris with 1.5, and my second leak 2.1 where the battery suddenly drops to less than 30%
Far as I know, I just have to charge like normal again to clear that up since g/f's eris is fine now.
SECOND Issue is I am now stuck in headset mode its a headphone icon with the mouth-piece, when no headphones or headset are in the phone.
I put headphones in and it switches to headphone icon. unplug them and its back to the headset icon, and no sounds.
Anyone else have this? would this be hardware or the new leaks issue?
your help is appreciated, and I will keep you posted if it changes, and how.
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.
Hi all,
I don't know this issue is related to hardware or software but for last 3 weeks I have been experiencing some serious issue with battery.
Whenever I am using my phone, be it playing game, surfing web or even looking at the phone like a dumb a**:silly:, my phone suddenly turns. And when I restart the phone the battery level which was almost 90%+ before the shutdown drops to 1% and before I can do anything the phone shuts down again.
The strange thing is that after all these when I connect the phone to a charger, the battery level is displayed at the one which it was at the start and everything comes back to normal. At least for time being.
First I thought this was an issue with NeatLite 4.0 XXLSJ ROM which I was using earlier but the same issue I found on CM10.1 and Stock XWLPY ROMs, so i guess this might be the issue with hardware or battery.
Please advice what needs to be done in this case if any of you has encountered this issue.
Thank you in advance!
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.
Hello all,
Please help me identity whats causing continued wakelocks.
It started when I updated to miui 11.0.8.0
Later tried changing roms, same issue on all miui and even pixel experience rom.
Android system is whats keeping my system awake all the time and draining battery.
While I am using phone the battery consumption is normal.
What I tried so far?
- Making sure all services like location, sync, wifi scanning etc services are turned off.
- No rough apps
- Device is not rooted
- Calibrated battery by draining completely and charging to 100% in off state
- Apps are up to date
- I tried wakelock detector, could not run it as it requires rooted device
Any pointers what I can explore more?
This is an issue with miui 11.0.8 and all custom roms based on its files.
Easy way to fix it is to revert to miui 11.0.5 pie build. That solves the always awake issue completely
---------- Post added at 07:52 PM ---------- Previous post was at 07:49 PM ----------
pra300 said:
Hello all,
Please help me identity whats causing continued wakelocks.
It started when I updated to miui 11.0.8.0
Later tried changing roms, same issue on all miui and even pixel experience rom.
Android system is whats keeping my system awake all the time and draining battery.
While I am using phone the battery consumption is normal.
What I tried so far?
- Making sure all services like location, sync, wifi scanning etc services are turned off.
- No rough apps
- Device is not rooted
- Calibrated battery by draining completely and charging to 100% in off state
- Apps are up to date
- I tried wakelock detector, could not run it as it requires rooted device
Any pointers what I can explore more?
Click to expand...
Click to collapse
See this thread for further details
https://forum.xda-developers.com/poco-f1/how-to/wakelock-issues-otgdefault-usb-usbpd0-t4116103
Thanks for your reply. I am currently on 11.0.5.0 and the issue persists on this version too. I downgraded to 11.0.5.0 via Fastboot rom.
Also tried clearing cache of Google services framework and other Google services.
Could this be any hardware issue? Right after I updated to 11.0.8.0 I started experiencing loose USB connection. When plugged in, the usb connection would disconnect and reconnect frequently. Later it fixed itself.
How can I find what exactly is causing my system to stay awake in background? I can only see android system is causing this.
pra300 said:
Thanks for your reply. I am currently on 11.0.5.0 and the issue persists on this version too. I downgraded to 11.0.5.0 via Fastboot rom.
Also tried clearing cache of Google services framework and other Google services.
Could this be any hardware issue? Right after I updated to 11.0.8.0 I started experiencing loose USB connection. When plugged in, the usb connection would disconnect and reconnect frequently. Later it fixed itself.
How can I find what exactly is causing my system to stay awake in background? I can only see android system is causing this.
Click to expand...
Click to collapse
Are you rooted? Then use better battery stats to get which wakelock is causing the issue......
For me, reverting to miui 11.0.5 recovery rom solved the always awake issue.
I rooted the phone today and ran betterbatterystats.
Same issue like the other guy you shared thread of. I will take a look over there.
https://prnt.sc/t7b8fr
https://prnt.sc/t7b8m0
Update:
Flashing recovery rom didn't work.
I went to service center and changed battery, also cleaned usb port. Surprisingly it didn't work.
Went back and replaced usb port (yes just port, officially they change charging PCB. They agreed to change only port)
It solved the battery drain issue.
My happiness did not last long as I noticed the back panel fits lose and mobile network is very weak now I never face such issue as I live in strong signal area. I have another sim card of same operator and thats working perfectly in other phone.
Don't know what to do with this issue.
Anyone having this otg_default battery draining issue you got these options:
1) Clean usb port
2) Flash rom
3) Replace charging pcb
4) For some people changing battery worked
5) You may even need replacing both battery and charging pcb
6) I found a post on reddit where a guy had created some boot img to disable otg function. That was quite old post.
Update 2 (30 June, 2020)
About weak network issue: Service center guys had pulled and damaged antenna cable. Didn't want to go through all appointment and high service charges, I replaced it at local shop and now the network is strong and perfect again.
Do inspect your device thoroughly guys before you leave service center after servicing.
The same issue started on my phone today (Again) . I woke up in the morning and my phone felt unusually warm. I say AGAIN because I faced this issue around 6 months ago. Went to service center, they cleaned the port, flashed older firmware etc. The problem still persisted.
I tried new cables, new power brick and everything. My fast charging works fine but the phone never goes to deep sleep. (Awake full bar in battery stats.)
After a few days the issue fixed itself, I have no idea how or why. No updates, no anything. Just automatically fixed and it stayed fixed for past 6 months now and it has suddenly begun today.
My main suspect is the charging port.
I'll wait for additional replies on this thread before I go into service center for port replacement.
Poco f1 battery drain always Awake in background
Uninstall App Vault using Xiaomi debloater
Thank me later
Testing with a custom ROM might have been better than resorting to hardware replacement and the like. I ditched MIUI within a few minutes of getting the device and been on crDroid ever since. Its been pretty much flawless for the last 11 months or so other than a 3 week period recently where idle drain was relentlessly high. Even that was resolved by flashing an updated kernel.
MIUI is just rubbish.
Yes, full wipe and flash AOSP/CAF-based ROMs. MIUI is bugged with those USB wakelocks. You can read my thread (posted earlier) for more info.