My Zuk Z2 Plus was previously running 7.1.2 based Viper OS 3.1 . I then flashed Oreo 8.1 based custom roms (AEX, Pixel Experience and RR 6.0). Since the update my phone is not getting charged. The battery percentage is stuck at 65% and its not charging. And when i restart the phone in recovery mode, thats when it start charging and the actual battery % is displayed. Also, phone doesn't charge in offline/powed-off mode. After shutting down the phone and when the the charger is connected the phone restarts automatically, without getting charges while its shut down.
Reloading it back to Viper 3.1 and it works just fine without any issues.
After flashing the F1xy kernel , on each of the above mentioned custom ROMs i am getting a SOT of barely 2-3 hours, as compated to 5-6 hours i was getting on Viper 3.1 and the battery drains with a rapid pace.
I posted this query on AEX's Google+ page, and was suggested to use Batter Calibration app or resetting the batter stat file. None of them have worked. Kernel has helped to resolve the charging and calibration issue, but the battery backup has worsen.
Is this because 8.1 doesn't have any official Gapps?
Let me know if anyone is able to identify the problem and have a solution for it. This doesn't seem to be problem with all devices, just a few. I wonder what it might be.
I am using AEX 5.2, and battery charging is working. It would be charged to 100%.
I have the same problem.
I have the same problem.Have you found a solution?
Offline charging is now working on latest Aex 5.2 version and some Custom rom doesn't have a Offline charging then, try to wipe /delete batterystats.bin if you stuck on 65%
Mr.CCH said:
I am using AEX 5.2, and battery charging is working. It would be charged to 100%.
Click to expand...
Click to collapse
I tried the same version with no luck. Only time it works is with F1XY custom kernel. And as i mentioned in my post the battery drains rapidly.
JanLezterGrate said:
Offline charging is now working on latest Aex 5.2 version and some Custom rom doesn't have a Offline charging then, try to wipe /delete batterystats.bin if you stuck on 65%
Click to expand...
Click to collapse
I don't know how to wipe batterystats.bin, can you help with the steps and also let me know if doing it has any adverse impact on device or its performance.
I have read some posts where folks have tried it but that has not helped either. Appears to be an issue with no root cause found so far.
Sounds like you have 1)not done a clean install, 2) wrong baseband 3) have some issue with some app
Im currently running AeX 5.2, phone charges 100% but it automaticly drops to 98-99% when i unplug, last cycle was 2.5 SoT and around 60h standby. (rough estimate from memory)
I charged yesterday, , 25 min SoT and 27h standby, 84% battery left.
Aevum said:
Sounds like you have 1)not done a clean install, 2) wrong baseband 3) have some issue with some app
Im currently running AeX 5.2, phone charges 100% but it automaticly drops to 98-99% when i unplug, last cycle was 2.5 SoT and around 60h standby. (rough estimate from memory)
I charged yesterday, , 25 min SoT and 27h standby, 84% battery left.
Click to expand...
Click to collapse
I have done clean install. Could be the last 2. Whats the correct baseband and how to change it if its incorrect.
I have checked battery consumption but haven't noticed any app eating up battery abnormal. It was mostly the apps that i used.
Have you flashed with the latest twrp-3.2.1-0?
https://twrp.me/zuk/zukz2.html (check download section)
johnnyjoe said:
Have you flashed with the latest twrp-3.2.1-0?
https://twrp.me/zuk/zukz2.html (check download section)
Click to expand...
Click to collapse
Yes, i have that version installed.
The have all the prerequisites in place.
JanLezterGrate said:
Offline charging is now working on latest Aex 5.2 version and some Custom rom doesn't have a Offline charging then, try to wipe /delete batterystats.bin if you stuck on 65%
Click to expand...
Click to collapse
No that doesn't make a difference I have faced the same issue
It is some Kernal related issue for some specific devices this problem gets solved by flashing f1xy Kernal
shripad_phadke said:
I tried the same version with no luck. Only time it works is with F1XY custom kernel. And as i mentioned in my post the battery drains rapidly.
Click to expand...
Click to collapse
You are right, it happend. I have to change the stock kernel to AR kernel, and battery charging works again.
No battery drains on AR Kernel. the SOT would be more the 5 hours.
Mr.CCH said:
You are right, it happend. I have to change the stock kernel to AR kernel, and battery charging works again.
No battery drains on AR Kernel. the SOT would be more the 5 hours.
Click to expand...
Click to collapse
I will try that. Now that you have mentioned you are using it, can you let me know if there any known issues or bugs you have experienced.
Mr.CCH said:
You are right, it happend. I have to change the stock kernel to AR kernel, and battery charging works again.
No battery drains on AR Kernel. the SOT would be more the 5 hours.
Click to expand...
Click to collapse
I tried AR Kernel but ran into the same issue. This is what i did-
- full wipe (system, data, cache, dalvik)
-Flashed - AEX 5.2 (AospExtended-v5.2-z2_plus-20180225-1552-OFFICIAL.zip), Unofficial Gapps for 8.1 (Micro) and AR Kernel R4 - NewTrees(For other Roms namely aosip, pixel experience, aex, los15.1, cardinal etc)
-All this while had 93% batter (and charging)
-After completing installation, it was back to displaying 65% and charging has stopped
Can you share your steps or correct if i missed anying.
One thing i notices that the installation stps on *AR_Beast* Kernel R4 (3.18.93) (Feb 04 2018) {CLANG) thread are as follow -
1.Boot into recovery.
2.Wipe cache and dalvik cache
3.Flash Kernel
4.Reboot to system
6.Done
Do you know if this is what i did wrong? Should i first install the rom and gapps and then flash AR Beast kernel
Something i did with my Mi4C when it was having this issue, the reseller installed some shoddy rom on it, i did a total format, the phone ends up with NOTHING on it, you do it from advance wipe in recovery.
But make sure you can mount it easly from recovery and have all the files to rebuild it first.
As for the basebamd usualy installing the latest ZUI updates it, but theres also a flashable img and zip,
carefull with the img and zip as some distributions relock your phone, and if there isnt a bootloader supported OS (as in a original ZUI) then the phone bricks (but there is a restore process)
Voilà! its working
Yesterday i flashed AEX 5.2 (AospExtended-v5.2-z2_plus-20180225-1552-OFFICIAL.zip) and Unofficial Gapps for 8.1 (Micro) at first and then *AR_Beast* Kernel R4 (3.18.93) (Feb 04 2018) {CLANG), with below steps -
1.Boot into recovery.
2.Wipe cache and dalvik cache
3.Flash Kernel
4.Reboot to system
This didn't work.
I then did a clean wipe and just installed AEX 5.2 (AospExtended-v5.2-z2_plus-20180225-1552-OFFICIAL.zip) and Unofficial Gapps for 8.1 (Micro) , without any custom Kernel, and to my surprise it started working.
The batter indicator displayed the correct % and when it drained that was pretty consistent. I did not feel any rapid dip.
As i was installing and reinstalling i couldn't track the exact SOT. I will try to track it today and update some screenshots.
I still don't know what was wrong and how it got resolved, but i am glad that its working.
I recommend you using aex 5.2 with stock kernel and akt profile - fusion balanced. Perfect combo between performance and battery
shripad_phadke said:
I tried AR Kernel but ran into the same issue. This is what i did-
- full wipe (system, data, cache, dalvik)
-Flashed - AEX 5.2 (AospExtended-v5.2-z2_plus-20180225-1552-OFFICIAL.zip), Unofficial Gapps for 8.1 (Micro) and AR Kernel R4 - NewTrees(For other Roms namely aosip, pixel experience, aex, los15.1, cardinal etc)
-All this while had 93% batter (and charging)
-After completing installation, it was back to displaying 65% and charging has stopped
Can you share your steps or correct if i missed anying.
One thing i notices that the installation stps on *AR_Beast* Kernel R4 (3.18.93) (Feb 04 2018) {CLANG) thread are as follow -
1.Boot into recovery.
2.Wipe cache and dalvik cache
3.Flash Kernel
4.Reboot to system
6.Done
Do you know if this is what i did wrong? Should i first install the rom and gapps and then flash AR Beast kernel
Click to expand...
Click to collapse
Try f1xy Kernal same happened with me 65% problem but doesn't happened on f1xy kernal
Aex 5.2 stock kernel with fusion balanced akt profile.
Rikul said:
I recommend you using aex 5.2 with stock kernel and akt profile - fusion balanced. Perfect combo between performance and battery
Click to expand...
Click to collapse
Can you provide a link to download this and installation/configuration steps.? The one i found on google was for OnePlus 3.
Related
Hi, I've been suffering some random reboots (about 3 per battery cycle) and after every reboot battery goes down drastically. I've changed the ROM and kernel and it still happens. I attach a photo of the battery life (you can see when the 3 reboots happened in the interruptions of the graphic) and a catlog (it's my first catlog so I'm not sure what to do). If you need any more info or the previous part of the log just tell me and I'll provide it.
Mine is a GSM gNEx and now I'm on Rootbox ROM (31/01/13 version) with ak 670.42 dummy kernel but as I said, it also happened in CM 10.1, AOKP, PA and with ak purity, leankernel and franco kernel.
Thanks in advance and sorry for my english.
it could very well be the phone itself. i had something similar happen on my toroplus and havent had the problem since i replaced it.
It could be your chip, but let's look at a couple of things first.
1) Are you dirty flashing by any chance?
2) Have you gone 100% stock and see if it happens there?
Nope, I haven't tried 100% stock, will try tomorrow (after doing my last exam of my degree). Also I've just had a reboot at 82% battery and the first one yesterday was at 82-81%. Is it a coincidence or can it be a hint? Maybe it's the battery...
Also I've been doing a full wipe between ROMS, no dirty flashing except for upgrades on the same ROM (just upgraded rootbox to latest JOP40G)
binlalo said:
Nope, I haven't tried 100% stock, will try tomorrow (after doing my last exam of my degree). Also I've just had a reboot at 82% battery and the first one yesterday was at 82-81%. Is it a coincidence or can it be a hint? Maybe it's the battery...
Also I've been doing a full wipe between ROMS, no dirty flashing except for upgrades on the same ROM (just upgraded rootbox to latest JOP40G)
Click to expand...
Click to collapse
Well I would do 100% stock boot, recovery, ROM etc... and see what it does.
I doubt it's your battery.
My random reboots stopped after I stopped flashing custom kernels. Try a clean install and keep the kernel that came with the ROM and see if you still get them.
Thanks, then tomorrow I'll try going back to stock ROM + kernel and see if it gets solved, if not I'll try with full stock.
Hello all,
I'd like to post directly in the thread [PRO][KERNEL] LuPuSv13 [LINARO 4.7.3][STOCK ICS/GB], but I'm new so I cannot...
So I hope someone using Lupus with the pro will see my message.
I was using Lupusv12 and all was perfect. I updated 2 days ago on the v13, and I noticed my battery lasted 2 times less longer.
So I rollback to the v12 and all is back to normal.
I wanted to know if I am the only one in this case, and noticed the kernel developer of my problem.
And i'd like to notice the developer the v12 is no longer available neither on his page nor on his repository. I needed the google cache to retreive it.
Thanks for any help.
none have reported any issues with battery drain in the thread... also according to revision log, there are no changes that could affect battery.
I can only think of retrying like this:
*flash lupus v13
*reboot to CWM
*wipe dalvik (always wipe dalvik when flashing only kernels)
*start phone
*use the phone heavily until battery dies and it turns off by itself
*do a full charge of the phone all the way to 100%... i think it doesnt matter whether it is on or off.
emptying and full charging the battery usually makes android recalibrate its readings... so there's a slight chance that battery drain is just misreadings. I just did this yesterday and the indicator stayed at 1% quite long before turning off... longer than 10% to 2%.
If you still find battery drain issue, you can go back to v12 as you did, or you could try other kernels...
I hope this helps.
Thanks for your answer ! Sorry for the late I was on holidays...
The creator of the kernel answered me kindly by private message. Indeed I'm the only one in this situation.
Because I absolutely need that my battery last one entire day, I prefered rollback to the v12, which works fine for me.
But I note your recommendations. I didin't wipe dalvik because, on my old device, the internal memory is very limited, so I use link2sd to "link" my applications on sd card, including the dalvik. But when I clean dalvik, the files of the dalvik cache are recreated on the internal memory and I must relink manually the dalvik of all my apps... boring !
Just for the info, I noticed on the battery section, that it was the operating system which drained my battery, especially "maintain activated" (not sure if it's this in english, it's "maintenir activé" on my french phone). I don't have this with v12.
I'll remember your advices for my next upgrade. thanks.
I have been using my I9190 for 6 months. Battery life was going down with original stock rom (I9190XXUAMF7).
I have tried all battery optimisation tips and apps. Nothing helped.
Last week i tried Greenify. Made some settings. It was the first time it had 36 hours standby time with medium usage.
Then i have installed newer official rom (I9190XXUBNA1), made all greenify settings and bought new original samsung battery (1900 mAh).
But standby time was (with no usage) 18 - 20 hours. I tried old battery again, it was 16 - 18 hours.
I tried 2 more original samsung battery (19000 mAh). Unfortunately same bad result
I formatted everything again and again. Reinstalled rom. Wipe data cache, wipe dalvic cache, format system - data etc..
recovery-clockwork-6.0.4.6, recovery-clockwork-6.0.3.7-serrano3gxx.tar, philz_touch_6.12.8-serrano3gxx.tar
Odin3 v3.04, Odin3 v3.07, Odin3 v3.09
I formatted external sd card. I removed it...
No improvement...
I do not think that it is a hardware problem. Because - 1 week ago - old dead battery had 36 hours standby time with medium use..
Any recommendation?
Thanks in advanced
draligus said:
I have been using my I9190 for 6 months. Battery life was going down with original stock rom (I9190XXUAMF7).
I have tried all battery optimisation tips and apps. Nothing helped.
Last week i tried Greenify. Made some settings. It was the first time it had 36 hours standby time with medium usage.
Then i have installed newer official rom (I9190XXUBNA1), made all greenify settings and bought new original samsung battery (1900 mAh).
But standby time was (with no usage) 18 - 20 hours. I tried old battery again, it was 16 - 18 hours.
I tried 2 more original samsung battery (19000 mAh). Unfortunately same bad result
I formatted everything again and again. Reinstalled rom. Wipe data cache, wipe dalvic cache, format system - data etc..
recovery-clockwork-6.0.4.6, recovery-clockwork-6.0.3.7-serrano3gxx.tar, philz_touch_6.12.8-serrano3gxx.tar
Odin3 v3.04, Odin3 v3.07, Odin3 v3.09
I formatted external sd card. I removed it...
No improvement...
I do not think that it is a hardware problem. Because - 1 week ago - old dead battery had 36 hours standby time with medium use..
Any recommendation?
Thanks in advanced
Click to expand...
Click to collapse
New battery require couple of full charge before it can reaches it maximum efficiency. Different type of custom recovery won't change or affect your battery. Optimization and greenify can only do so much as well.
The power heavy drain problem from day one of S4 mini is the kernel's default profile for CPU governor. So, if you want to stay with the TW rom, you may alternatively use a custom kernel: http://forum.xda-developers.com/showthread.php?t=2545244 and change the CPU governor. Any other method is just treating the symptom but not cure the root.
Note if you haven't tripped knox already (if you have knox), flashing a custom kernel will.
TNCS said:
New battery require couple of full charge before it can reaches it maximum efficiency. Different type of custom recovery won't change or affect your battery. Optimization and greenify can only do so much as well.
The power heavy drain problem from day one of S4 mini is the kernel's default profile for CPU governor. So, if you want to stay with the TW rom, you may alternatively use a custom kernel: http://forum.xda-developers.com/showthread.php?t=2545244 and change the CPU governor. Any other method is just treating the symptom but not cure the root.
Note if you haven't tripped knox already (if you have knox), flashing a custom kernel will.
Click to expand...
Click to collapse
Thanks for your message.
I installed the same system, same apps, same optimization methods, greenify with same settings. Everything is same.
My phone was rooted. And it is rooted now, too.
Nothing changed.
I have installed setcpu, one hour ago. I will try it for 24 hours. I hope it will help.
Thanks again
Any other help?
Hi again
I have showed my s4 mini to samsung service.
They told me that there is no hardware problem.
Problem is software.
I have tried two more batteries.
The last one is zero lemon 5100 mAh.
But nothing changes.
I have tried carbon, cm, slimkat, mokee, stock rom, two more roms...
Battery drains too fast.
Sometimes while percentage is 75 %, i restart phone, it becomes 81 % or 69 %
Sometimes while percentage is 75 %, i enter recovery mode, it shows 85 %
Any help please
Have you tried flashing the custom kernel as mentioned before?
Redflag rom has vikinger kernel
It is my current rom
any help?
Hi guys!
So, as you can read in the thread, I want to know how long your phone can run without charging it. I am asking, because I see on my phone with Lineage OS 18.1 (without any custom kernel), that for example in night it only drains 1%, but when using it it drains 1-5% per hour. I don't know, if it is normal for this rom. And I am only checking this after first booting to the system (after flashing).
EDIT: If somebody asks, yes I have Gapps package (MindTheGapps)
EDIT 2: Gsam shows around 2,8%/h while using phone
I lot depends of gapps , I use Core , and also over night I lose 1% . 2% when I check notification .. but I am on CorvirusOS unoficiall
Since the last few updates, even on a fresh install with nothing installed. My LineageOS in Alioth has been using 7% to 11% /hr of battery on a fresh install with no extra apps added. Tried doing a clean install, reset to factory, even tried reseting battery stats. Sadly cant do anything about it and I'm not being able to go back to versions I knew worked OK (19.1-20220723 for example since i dont have an img to use and lineage page only have the latest).
Most battery, about 55% is consumed by Kernel. Has anyone had the same issue?
Not sure what else to do and really don't want to go back to MIUI.
I got similar issues a few Updates back, it was related to some Magisk modules I used. After removing them the battery drain stopped.
Try getting the logcat output and see if something is reported there.
Also make sure you are using the right firmware.
Thanks for the advice Boracho, but this is happening on a 100% clean install. Not even gapps on it.
Did clean installs of both OS and recovery versions 19.1-20220917, 19.1-20221001 and 9.1-20221008... all had the same problem. Finally remembered I had 19.1-20220723 in a pendrive. Installed it. Works just fine. Battery problem is gone.
Disabled auto updates. The end.