Hi Guys
Aplogies if this has been answered anywhere before.
I recently installed the latest version of HonamiX Essentials ROM which comes with the latest version of TWRP Recovery.
I've noticed that when I boot into recovery it seems to show completely different battery levels and system time.
Not a major issue I know, however upon rebooting back to the system the battery levels shown in TWRP seem to override the levels previously shown in the system.
For example I had 26% battery remaining and booted into TWRP to flash a mod. TWRP showed the battery level as 55%. Upon re-booting to the system I then supposedly had 54% battery remaining.
Obviously the latter is incorrect??
This proved true as the phone shut down an hours or so later due to the battery being too low, although it still supposedly had 16% remaining?
Related
Apologies for opening a new thread for this. I am unable to reply on the dev thread as I have less than 10 posts. So in reference to the following post, I'd like to contribute some experience I had in the last two weeks.
http://forum.xda-developers.com/showthread.php?t=1627689
Across the space of two weeks, I have had a chance to note this symptom on three devices.
Device 1 SGS i9000
Rooted phone and have been on CM9 for as long as I can remember. Wake up one morning to find phone with BLN on, but no ability to wake the phone (power button, home button, volume buttons, nothing works). Popped the battery out, and the bootloop / no recovery went on forever. Had to Odin flash back to Stock 2.3.6 to start again. Since then, any CM9 (nightlies or RC2) attempted always end up in the bootloop, i.e. stock > flash rom, first boot = bootloop. I figured then if I had to go back to 2.3.6, I'd rather go to JB. First JB tried was HellyBean, and the same thing happened. It was only trying pawitp's current alpha CM10 that it worked. Days later reverted back to ICS (Paranoid Android v1.6) due to lags and bugginess.
Important to note, the CWM kernel I have gone through are 6.0.0.3, 6.0.0.8, 6.0.1.0. And Paranoid Android put me back to 5.5.0.4.
Device 2 SGSi9000
Rooted phone and have been on CM9 for as long as I can remember. Phone cut off and rebooted in the middle of a phone call and ended up in bootloop with no recovery. Exactly the same symptom attempting to get the phone back into any of the CM9 roms (nightlies or RC2). Ended putting the phone on Paranoid Android as well.
Device 3 HTC Sensation
Had a lot of trouble trying to flash CM9 on this using CWM. Random bootloop with no recoveries. CWM at that time was 6.0.0.8, which I had lots of trouble flashing Gapps on. More on this device posted here: http://forum.xda-developers.com/showthread.php?t=1786703
And finally, one other observations across all these devices. Somehow with CWM v6.x.x.x I had rather poor battery life. For instance, on CM9 Nightly 07/23, say I started with 100% charge in the morning at 8am, by 12pm, I would be looking at 80% left. Once a week, I will let the phone shut itself down on low power, and charge without switching the phone on. On any other evenings, I would plug the phone and leave it charging overnight, e.g. at 10pm with only 30% left. I have constantly noticed that within a few minutes, it jumps back to 40%, which is rather odd. A 10% charging achieved within minutes is rather unusual.
I have also noted that, when the SGS i9000s ended in the bootloop / no recovery situation, the phone can never be charged. Plugging the phone for charging will the a blank battery icon lit up, with the swirly thing on top of the icon appeared frozen and it stays that way.
Being on lower version of CWM, in this instance, v5.5.0.4., I can observe the units (observed being the keyword here) charges "normally", i.e. no funny 10% charge achieve within minutes. Also, battery life are much better as well, i.e. only 10% drain between 8am (100%) to 12pm (90%).
So, not being a developer but someone that likes to tinker and observed:
- Is it possible that newer version of CWM potentially have some impact to battery life?
- Is it possible that how CM9 is being flashed onto a phone has potential issue? I find it a bit disturbing on an initial flash from stock to CM9, I had to pop the battery out after the flash initially loads a new CWM onto the phone. Then start the flash again with the newly loaded CWM.
I am hoping all these I have experienced in a short amount of time can be helpful to potentially looking into where issue might be. Most people have one phone and tested across different kernels and ROMs. I had the luxury of testing across three devices on a narrower choices of kernels and ROMs.
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
For the first SGS paragraph I can relate. EVERY ROM would boot loop. I had to flash to stock With repartition ticked. And then flashed semaphore kernel, and formatted system, data and cache. Then I flashed to whatever ROM and was okay.
Also I seem to have the problem with having to pull the battery after a flash to the new recovery. Only happened a few times, but non the less, still happened. Just make sure you flash twice afterward to make sure
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yup, on every occasion I mentioned above, wipe (system/data/cache) are part of the ritual. Just didn't mention them.
I just think the battery-pulling feels rather odd. Can understand why it's needed, but just feel odd. Wondered if it'd be better to keep kernel and ROM separate, e.g. flash new kernel via Odin, then simply do ROM. This might be a 'cleaner' method perhaps? It feels almost like flashing kernel as part of the process is like modifying Windows files whilst still in Windows, then do a reboot.
For now I have fear against v6.x.x.x kernels. But will likely go back to it once CM10 is stable. We'll see.
I installed Eryigit's Android 2.3.6 ROM onto my SGP 5 and have this battery charging boot loop. Are there any solutions for this yet?
Hi,
I recently flashed my XXLS7 ROM and while doing so, I was asked to wipe battery stats too, after then I see that my battery % is getting reduced drastically and the worst is that whenever I am in normal mode it shows me 75% but after getting into recovery mode it shows 55% or so. Now I am completely confused whether 100% is actually 100% or not. Any ideas on how to get this problem rectified?
Thanks in advance.
may be you need to do a clean install of the rom again.
use format/system and format /data this time
nokiamodeln91 said:
may be you need to do a clean install of the rom again.
use format/system and format /data this time
Click to expand...
Click to collapse
Thanks, I have tried that option too, but still no help..........
Be patient
Mine was discharging like crazy when media scanner was doing its thing -- just keep a charger handy and stick it on when it gets low. Eventually it should sort itself out.
boot into recovery and wipe battery stats again.. then charge the phone to 100 % and test again.
I had this problem in almost every xxls7 ROM... I tried everything, literally EVERTHING.... i made 3 wipes, format preload format system etc etc... Result is DEVICE IDLE eats battery... I CAN NOT figured out which causes this... But finaly, SweetROM solve the problem... I do not know how but it solved... I tried RR3, Alliance and Stock xxls7... All of them causes battery drain for me but i do not know if it is a problem of all... Anyway, just in case you can try Sweet ROM... At least it does not cause drain when you do not use it...
I have this problem too..
Nokia 3210 with PA Utacka
after restarting the phone go to settings>application>all>media storage and stop it.
on every bootup, media storage process consumes %5-10 battery to scan media files.
you can disable it but the gallery wont work.
you can use Quickpic instead.
Hey everyone:
HTC One M7 (AT&T variant). Unlocked bootloader & s-off. TWRP 2.7.0.0. HBoot 1.44.
I had Maximus 30.00 ROM on my phone up until last night. Then I downloaded Whats app plus on a questionable site application; it looked like it was taking forever to finish; so I went ahead and restarted the phone. That was a bad mistake.
The phone started boot looping. I tried in vane to reinstall the same ROM and then whatever ROM. It turned out the /data/ partition was corrupted. So I reformatted it with mkfs4 thanks to these instructions. Then I was able to install Maximus 40.00 and got the phone unbricked (yay). But I found two problems:
1) The phone battery wouldn't charge past 77%... nor did it seem to discharge.
2) The phone battery wouldn't charge when I first turned the phone off. The amber LED light would just hold constant.
I tried running that ROM with elementx kernel with no results. So I installed the latest version of this ROM (Android Revolution 71.0) with a full wipe of everything. /data/system/cache/dalvik cache etc. Still had both problems.
Then I tried installing ElementX kernel (with the fast charging option checked) with this ROM which led to the second problem going away. However the first problem still exists. I also tried clearing battery stats with no effect. Also tried doing a fastboot erase cache with no effect.
I'm not sure if the battery is really at 77%; but I have turned off the phone and am watching it charge with the same charger I've always had that charged it to 100% before... but its been going for 15-20 minutes without going up one percentage.
Any idea how I can try to get rid of this quite annoying problem? Thanks very much in advance! I would be happy to provide any additional information you might need.
I really wanted to use ICE, but I keep getting the same problem as this guy:
x000x said:
tried the most recent version ICE 8.2.2 (r99) and it went through the install process. It rebooted, and got to the setup screen where it promptly shut off my phone. Puzzled, I restarted my phone and got to see 1 second of the display before it shut off again, and got to see that it showed my battery at 1%. When I started the install i had 97% battery. then in the 5 minutes or so that it took to install and reboot it drained it all the way to 1%
I think this is a bug because when i plugged my phone back in to charge it said there was 95% of the battery left
but when i restarted it keeps thinking i only have 1% battery left
I installed from a clean wipe, choosing to wipe everything within ICE install options menu
edit:
8.2.2 (r99) kept rebooting with the 1% battery thing
8.2.0 (r78) got a hands free activation screen. took forever. eventually said it activated, rebooted and went back to hands free activation =/
8.1.0 worked but had some quirks that i didn't like (mobile data kept getting shut off for some reason on its own)
Click to expand...
Click to collapse
I just want Magisk, no superSU. Whenever I "uninstall/unroot superSU" and then try to install it in TWRP I keep getting some error saying "boot image patched by other programs." That is with BadBoyz and Viper. I know Lineage OS is an option, but I don't want Nougat either.
This thread can be deleted, I figured it out.
Hello! Be gentle, I'm a noob and I need some help. With any custom ROM I install my battery won't charge or discharge, it just stays on the same number. I have to boot to recovery to see the difference. I tried discharging it fully, which was surreal experience because it stayed on 1% for hours while I was playing games until I rebooted and it realized the battery was empty.
I am using TWRP, but I tried with Orange Fox too. I format before I flash each ROM. I tested with Lineage OS 16, Evolution, Havoc... Almost all the custom ROMs found here and the battery just won't work. What might I be doing wrong?