Develop Bugs

[Q] Problem with Omega 12 + Perseus 33.3 start up screen lasts forever

HI Guys
I'm an old iOS user but switched to android 2 months ago with a wonderful Note 2 International running android 4.1.1
​
after one month of use I decided to root my device for VPN service and custom ROM benefits
​
Everything went fine. First rooted with odin 3.07, then decided as most of users recommended to flash ARHD 11.2
After using my device for 2 weeks I noticed poorer battery performance. 4 days ago, After a lot of searching online I decided to flash Omega 12 then Perseus 33.3 for better battery performance and better control of my CPU.
That's what I did. First, wiped all data through CWM then installed Omega 12 ---> Perseus 33.3 ---> clean cached data ----> restored my apps through titanium ----> fixed permissions ---> charged my mobile to 100% then wiped battery stats ---> set gpu to 440mhz and cpu scaling --> frequency responsiveness to 600mhz === every thing went very good with wonderful performance and battery life with 40 hours battery life ,more than 7 hours onscreen and also did couple of successful restarts to change SIM card .I thought that's it "I will stick with this system forever no matter what."
:highfive::highfive::highfive::highfive:​
As I said, after 40 hours of battery life my battery died so I put my note 2 with the recharger while off because it was night time. Next morning, I unplugged my phone then turned it on but my startup screen keep showing the big robot walking with no ending for 30 minutes. Tried to restart the phone couple times, searched online for a similar issue but nothing related to omega and Perseus, wiped cache, dalvik but still the same.
:crying::crying::crying::crying:​
Finally, I restored an image through CMV contains my 4.1.1 old stoke ROM + factory kernel just after rooting. My smartphone now is working fine.
My question now is "Why did it happened? Did this happen with anybody before with the same circumstances? and what is the possibility of this happening again if I tried to flash a custom ROM or a new kernel?
I'm ready for any questions​

haniwilliam7 said:
HI Guys
I'm an old iOS user but switched to android 2 months ago with a wonderful Note 2 International running android 4.1.1
​
after one month of use I decided to root my device for VPN service and custom ROM benefits
​
Everything went fine. First rooted with odin 3.07, then decided as most of users recommended to flash ARHD 11.2
After using my device for 2 weeks I noticed poorer battery performance. 4 days ago, After a lot of searching online I decided to flash Omega 12 then Perseus 33.3 for better battery performance and better control of my CPU.
That's what I did. First, wiped all data through CWM then installed Omega 12 ---> Perseus 33.3 ---> clean cached data ----> restored my apps through titanium ----> fixed permissions ---> charged my mobile to 100% then wiped battery stats ---> set gpu to 440mhz and cpu scaling --> frequency responsiveness to 600mhz === every thing went very good with wonderful performance and battery life with 40 hours battery life ,more than 7 hours onscreen and also did couple of successful restarts to change SIM card .I thought that's it "I will stick with this system forever no matter what."
:highfive::highfive::highfive::highfive:​
As I said, after 40 hours of battery life my battery died so I put my note 2 with the recharger while off because it was night time. Next morning, I unplugged my phone then turned it on but my startup screen keep showing the big robot walking with no ending for 30 minutes. Tried to restart the phone couple times, searched online for a similar issue but nothing related to omega and Perseus, wiped cache, dalvik but still the same.
:crying::crying::crying::crying:​
Finally, I restored an image through CMV contains my 4.1.1 old stoke ROM + factory kernel just after rooting. My smartphone now is working fine.
My question now is "Why did it happened? Did this happen with anybody before with the same circumstances? and what is the possibility of this happening again if I tried to flash a custom ROM or a new kernel?
I'm ready for any questions​
Click to expand...
Click to collapse
Firstly, NEVER let you battery die completly, it is not good for the overall life of the battery.
Secondly if that ever happens boot to recovery and clear dalvik cache and fix permissions. This will usually help.
It's hard to say exactly what cause this issue without a log.
Also, please keep regular backups through your preferred recovery, as this will help if you need to go back.
Cheers,
Evil.

Thanks for the tips.... really appreciated
Sent from my GT-N7100 using xda app-developers app

same
same thing happened to me exactly .
same rom same kernel
i couldnt even restore a previous backup of omega from a week ago - it just wouldnt restore without rebooting !!
also, for my note 2 to work again i had to reflash my recovery (twrp) via odin and reinstall my rom.
i had a whole load of other issues and in all honesty im almost thinking i may have a broken NAND chip - sudden death - not quite, but im patched for that, but may be a small fail on the chip had caused this event , i really dont know.
im back to normal now but im stll very worried about the next few days - please read my other post where i explained this fault at the time it happened.
http://forum.xda-developers.com/showthread.php?p=38697185#post38697185
thanks.
.

I will look at it... but I think in the mean time I will stick with my original stock and kernel for a while till I have the courage for another rom/kernel trial
Sent from my GT-N7100 using xda app-developers app

[Q] [PRO] Lupusv13 drain my battery

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.

[Q] Debug Battery Drain - com.android.systemui

Hi,
I'm using s4 mini LTE I9195 with CM11 M6, f4ktion 1.4.0 kernel, BN3 modem, TWRP 2.7 recovery
All was working fine, average battery drain on idle was 1%-2% (not great, but fine), and suddenly it rocketed to drain 15%-30% per hour.
I usually use Android Tuner's battery measure stats to track drain statistics over time.
After checking it, I"ve noticed that it () the drain) started in the middle of the night.
So it's not due to "I launched this App, and then..." It just went nuts on it's own...
I've checked which process is to blame and the first one with max battery consumption is:
com.android.systemui (with KitKat logo) followed by Android System, then Screen, and then all the usuals.
I tried to do reboots, disable wifi/nfc/rotation/data/sync/anything else/kill user apps - no effect ...
It still drains about 20% per hour on system and systemui for the whole day now :crying:
And I have no idea what causing it / how to revert it...
So, do you have any suggestions on how to trace this bug?
What to search for in logs?
Any thing else?
I'm not a big pro on android OS subsystem, so advises are welcomed!

I'd love to help, but I actually stumbled upon this thread while googling to help myself
I'm using Note 2 (N7100), running CM11 - newest nightly (although I flashed it today, after slightly recharging the battery once I noticed the problem) and Devil3 kernel.
I'm having the same issue - yesterday everything was fine, I've left the phone to charge over night and display time as usual and in the morning nothing seemed out of the ordinary, until 6 hours later. After those 6 hours my battery was fully depleted (whereas normally lasts whole day and is not even close to being depleted). com.android.systemui and Android System seem to be the problem for me too.
I've also tried turning off some functions, uninstalling some apps, turning off notification privileges for others. Even, as said earlier, flashed newest nightly. Nothing helped. Using phone with without flashing Devil3 kernel didn't help.
Anyone have any ideas?

Just try to flash stock software and again CM.

Try a older version of CM11, and if stability is a priorty stay on CM 10.2

OK, so I've tried a few things, and had a few surprising outcomes:
I've analyzed the CPU load with various tools, as Android Tuner, OS Monitor, and All-In-One Toolbox.
Most of them reported Android System using 30% CPU, and com.android.systemui using 25% CPU, all on the highest frequency.
But All-In-One Toolbox recognized top process instead of Android System as Lockscreen android process, so maybe there is a hint there...
(and I don't use any custom lockscreen stuff beyond stock CM's one)
So, backed up the current troublesome system (let's call it BKP_NEW), just in case, and decided to restore a full NANDroid backup I had from a week ago (and the issue is just from yesterday).
Restored all 6 partitions (/system, /boot, /cache, /efs, /modem, /data), rebooted, and....
...The issue was still present! Crazy battery drain just as before!
Very confusing... Then I went for a factory reset - it fixed the issue, but I have to start from scratch with all the SW installs and config, and I don't have a week to waste setting everything up again, and potentially running into the same issue some time later.
So, I've decided to move further back, and restored a two week old NANDroid backup > reboot > No issue presents
But it was just too weird, since the delta between 1-week old and 2-week old backup is infinitesimal.
So, out of curiosity I've decided to restore the BKP_NEW (the one of the system with the issue present)... and after the restore it works just fine! (WTF?!?!)
After thinking on it for a while, my conclusion is that there was some problem with some part of system that was wiped/fixed in TWRP's Factory Reset, but is not touched/overwritten during the NANDroid 6-partition restore.
But again, this is just my assumption, need someone more knowledgeable to confirm this possibility...
(maybe @ne0zone75 can advice on this?)
Since that, all is working fine (at least so far).
And if my assumptions are correct, @Ksenios, you can try to do this, and still have working system with all apps and configs (If youre comfortable with recovery / backups management).

hi,
(passing bye from google - just a note)
com.android.systemui cpu high usage (about 37%),
on my huawei media pad x2 (gem702l) but only while charging (and just sometimes), if that gives something for someone, any clues why ?

Permanent wakelock

HTC One X 32GB GSM
I've had it for a year as a backup phone for just browsing with wifi and listening to music. Which it did fine under CM11 until a month ago. Now it simply stays awake 100% of the time and the battery is empty in 6 hours of no use.
Tried:
Reflashing the CM11 rom with all partitions formatted
Switching to a 5.0 rom with the new layout
Flashing back to CM11
Flashing a new kernel
Without success. Right now it's running a clean CM11 rom with faux123 kernel. Android says it's a 50/50 between Android OS and Google Services. I've used wakelock detector, which shows the highest user with 2m (phone) and the kernel wakelock as "main".

Battery issue on Oreo 8.1 based custom roms

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.