Database Users

[Q] Battery Drain in slimbean

Hello
I recently installed my first rom - SlimBean 4.3.1 bulid 2.2
The rom works fine but after 1 week i noticed my battery start to drain very quickly.
I check with GSam Battery Monitor and i found out that *kernel* eat most of my battery.
I want to change the kernel.
which kernel will save my battery in a better way?
My current kernel is: 3.0.80+
Dan

danavon said:
Hello
I recently installed my first rom - SlimBean 4.3.1 bulid 2.2
The rom works fine but after 1 week i noticed my battery start to drain very quickly.
I check with GSam Battery Monitor and i found out that *kernel* eat most of my battery.
I want to change the kernel.
which kernel will save my battery in a better way?
My current kernel is: 3.0.80+
Dan
Click to expand...
Click to collapse
Dan,
Can you give a little more information? Type of phone, which version of Android you upgraded from etc?
I can't say that I've encountered any battery drain issues with Slimbean in the past..... it's only ever helped things.
The only question I'd ask is did you follow the correct instructions when flashing? (deleting / formatting all of the cashes etc don't just do a factory reset). Your probably a very clever guy who did everything correctly - but it's the only thing I can think of.
I'd try re-flashing following the instructions on the slimbean website to the letter......
Hope this helps
MD

monkeydogger said:
Dan,
Can you give a little more information? Type of phone, which version of Android you upgraded from etc?
I can't say that I've encountered any battery drain issues with Slimbean in the past..... it's only ever helped things.
The only question I'd ask is did you follow the correct instructions when flashing? (deleting / formatting all of the cashes etc don't just do a factory reset). Your probably a very clever guy who did everything correctly - but it's the only thing I can think of.
I'd try re-flashing following the instructions on the slimbean website to the letter......
Hope this helps
MD
Click to expand...
Click to collapse
So, does this mean, there is no option to use a custom kernel for Slimean 4.3 build 2.2? I am on i9300 on Slimean 4.3 build 2.2...

Shonilchi said:
So, does this mean, there is no option to use a custom kernel for Slimean 4.3 build 2.2? I am on i9300 on Slimean 4.3 build 2.2...
Click to expand...
Click to collapse
He didn't say that. He was asking Dan did he correctly followed the installation procedures or not, because issues sometimes caused from previous rom installations leftovers (not properly wiped).
And to your question, custom kernels is just a matter of individual preference. You may install any kernel as long as they are compatible with slimroms.
Although any issues caused by other kernel shouldn't be discussed in slim threads. But if you're using stock slim kernel and having problems then you may report to the devs, but make sure that problems aren't listed on the OP's Known Issues, and also provide feedback support files such as logcats or screenshots so the devs could identify the problems right away ?

Battery drainage issues
Hello,
I have recently installed SlimBean 4.2.2 on my Xperia S.
This is my first custom ROM and my previous OS was Stock 6.2.B.1.96.
Needless to say I've rooted my phone (using DoomLord's Technique), have CWM Recovery 6.0.3.0 and Unlocked the bootloader.
I had cleared data, cache, dalvik Cache before flashing the Slim-nozomi-4.2.2.build.8-OFFICIAL.zip and Slim_Gapps.4.2.2.build.8.zip
Issues:
Heavy battery drain - I left my device overnight with all radios off (Airplane mode) and the device registered a loss of 10% in battery level [ 2 Screenshots attached ]
The GSM network radios doesn't turn on when I change the Airplane Mode toggle in Notification Bar
Unrelated - How do I use the AIO_Addons.zip and AIO_Aroma.zip?
Unrelated - Does flashing a Custom ROM mean that Google Apps won't be updated via Play Store? ( Tried once - got invalid signature error )
Steps taken to remedy this (Beginner level):
Installed WakeLockDetector app to find what's up with the ROM. Turns out Google Search had maximum wakelocks [ Attached Screengrab ], despite me Greenifying the app.
I've greenified Google Search app and couple of other network accessing apps (like feedly, pocket, FalconPro (twitter client) )
Dear XDA-ers, kindly help me remediate this issue, as I truly like the ROM..but I'm sure such issues can be solved. Otherwise It wouldn't be the stable ROM that it is.
Please let me know if any other information would be helpful.
First post here, apologies if I may have offended anyone's sensibilities.

[XT1033 INDIA] Issues with 5.0.2 solved in 5.1, as Tested by me

A. Phone, Router & Firmware info:
1. My Phone : MotoG XT1033 Asia [Nov 2013 Model INDIA]
2. My WiFi Router : DSL-2750U_ADSL_Modem (U1, IN_1.08)
3. Root/Mod Status : No Mods, Not Rooted (Normal)
4. Old Firmware : Lollipop 5.0.2 [220.21.28] Stock
5. New Firmware : Lollipop 5.1 [221.21.56]
6. Update method :
a) File "Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip" downloaded in PC. (file md5-checksum = 94856deaaa3f23a1163120b362cbaef10, 208.7 MB )
b) File copied to phone's sdcard/Internal memory.
c) "apply update from sdcard" thru phone's BootLoader/Recovery menu.​effect same as update thru OTA file, but safer.
7. Updated Date : Sep 12, 2015.
8. Status : Update successfully installed.
9. Post update actions : wiped cache partition (thru fastboot & recovery menu)
-------------------------------------------------------------------------------
B. Issues with 5.0.2 solved in 5.1 (Sep-2015), as experienced/Tested by me
1. WiFi re-connection issues after disconnect, with Channel-13 or auto-channel, earlier in 5.0.2.
(eg: when enforced WiFi disable/enable or by moving out/in of Wifi range).
These issues are solved in 5.1, even with Channel-13 selected (either manually or auto).
2. When an incoming call, is not picked-up even after screen timeout time (say 15 secs), then ringing stops, & display switches off. Accepting the call after this is very difficult. This issue is solved in 5.1
3. Gallery Application fails/ Misbehaves.
Albums/Videos, shows blank squares/Tiles. Problem temporarily solves on reboot, but only for one invocation. This issue is solved in 5.1
4. Two Photo icons in App Drawer. This issue is solved in 5.1.
5. The phone lagging response issues seems to be improved, if not altogethor solved.
At least it is more responsive (response time faster), and smoother to operate, than in 5.0.2.
But the final verdict on this can only be provided after some extended time of usage (say few weeks or more).
Earlier with 5.0.2 it was horrible, especially as time went by, and I was planning to revert to stock Kitkat-4.4.4.
So I want to know others experience regarding phone resposniveness w.rt 5.0.2 in 5.1
6. I am not facing any early Battery drainage issues in 5.1 w.r.t 5.0.2, as reported by some others.
In my opinion, if only it is better. But not sure (feedback only with couple of days usage)
Anyway surely not very bad than earlier.
7. CPU SpyPlus now reports 300 Mhz as min scaling freq, as against 787 Mhz in 5.0.2.
I am sot sure how significant this is. But some people reported this as a problem in 5.0.2
The highest reported freq is 1190 Mhz.
Incidentally some people are referring to this update as 5.1.1 instead of 5.1, here in these & related forums.
I am only seeing Android Version as 5.1 in : Settings --> About Phone Menu.
with Baseband version = MSM8626BP_1032.3116.98.00R and
Kernel version = 3.4.42-g89906d6
So I dont know whether Motorola is released or releasing any newer version 5.1.1 other than this one.
I think people are confusing this with 5.1.1.
I would like to hear other experts comments regarding this.

Even i updated my moto g XT1033 (India) model yesterday. Was running on CM12.1 before so had to flash 5.0.2 stock and then got the OTA update directly.
The changes are minor but what matters is performance and RAM Management and Battery Life.
1. The performance as mentioned by the OP has really improved. Device feels snappier and more usable then 5.0.2
2. I see many people even after updating to complaining about memory leaks but personally in my device i have 300-400mb of memory free (I have downloaded and updated all the apps and many apps like facebook whatsapp etc are running in background)
3. Another major change that i was able to notice was the battery life has improved (comparing to both cm12.1 based /AOSP based/ 5.0.2 stock) specially the stand by time went to bed with 90% and woke up with around 84% (where in cm12.1 it was used to be 70%)
am personally happy with this update even though it was too late. I'd appreciate if motorola could push the 5.1.1 update too since that does not contain any major changes (security patches).
PS: YOUR BOOTLOADER WILL GET UPDATED TO 41:1A this doesn't mean you cannot flash or root. You can flash and root by the same procedures but make sure to use the latest TWRP AND SUPERSU ZIPS.

Hey OP thanks for the post.
Can you also check if the Screen going completely black issue has been solved as well?
If you check Adaptive Brightness in
Settings>Display and reduce the brightness via the slider the screen goes black. It's like the phone is off, but it's really not. (be careful, don't forget where the slider is so you can crank it up again).
Can you confirm if this is still present in 5.1?
Thanks a lot!

Do you experience any battery drain bug such as Google Play Store or the infamous mobile standby drain ? Would love to hear your feedback about this. Last time I've tried some 5.1 custom roms they had this bug, which prompted me to switch back to 4.4.4.
Thanks.

Hi guys, thanks for your reports.
Could you please comment about the "mobile data active" issue? Is it solved or, at least, mitigated in 5.1?
Thanks!

enban said:
Hi guys, thanks for your reports.
Could you please comment about the "mobile data active" issue? Is it solved or, at least, mitigated in 5.1?
Thanks!
Click to expand...
Click to collapse
no its solved in android 6.0. Its google bug.

That problem solved too
Mustajab Is'haq said:
Hey OP thanks for the post.
Can you also check if the Screen going completely black issue has been solved as well?
If you check Adaptive Brightness in
Settings>Display and reduce the brightness via the slider the screen goes black. It's like the phone is off, but it's really not. (be careful, don't forget where the slider is so you can crank it up again).
Can you confirm if this is still present in 5.1?
Thanks a lot!
Click to expand...
Click to collapse
Screen goes to black problem is solved too. now we can use adaptive brightness on an lower the brightness to minimum..

gmp009 said:
no its solved in android 6.0. Its google bug.
Click to expand...
Click to collapse
Well... It seems like I'm going to skip 5.1 also...
Thanks!
E.

How to root it ? Any link for updated supersu and TWRP is helpful.

enban said:
Well... It seems like I'm going to skip 5.1 also...
Thanks!
E.
Click to expand...
Click to collapse
Well, there won't be official 6.0 for 1g Moto G, if you want to stay in stock firmware, you should update.

moralesnery said:
Well, there won't be official 6.0 for 1g Moto G, if you want to stay in stock firmware, you should update.
Click to expand...
Click to collapse
Obviously I was talking about custom ROMs. CM13, maybe? ?

performance upgraded too. its about 4 days I'm running it and found no issue. except battery. I just expected more battery backup.

ant24x7 said:
How to root it ? Any link for updated supersu and TWRP is helpful.
Click to expand...
Click to collapse
TWRP : Please select stock Non-theme version to avoid problems
SuperSU: After flashing TWRP with mfastboot through bootloader use this zip to get root
PS: YOU CAN FLASH ANY 5.1.1 ROMS OVER IT WITHOUT ANY PROBLEM

thuva06 said:
TWRP : Please select stock Non-theme version to avoid problems
SuperSU: After flashing TWRP with mfastboot through bootloader use this zip to get root
PS: YOU CAN FLASH ANY 5.1.1 ROMS OVER IT WITHOUT ANY PROBLEM
Click to expand...
Click to collapse
You only need to install TWRP on your device and enter recovery mode.
Once there, you go to "Reboot" and then "System", TWRP will ask if you want to root and will run SuperSU script.
When you boot to Android again, TWRP will update itself over Play Store.

thuva06 said:
Even i updated my moto g XT1033 (India) model yesterday. Was running on CM12.1 before so had to flash 5.0.2 stock and then got the OTA update directly.
The changes are minor but what matters is performance and RAM Management and Battery Life.
1. The performance as mentioned by the OP has really improved. Device feels snappier and more usable then 5.0.2
2. I see many people even after updating to complaining about memory leaks but personally in my device i have 300-400mb of memory free (I have downloaded and updated all the apps and many apps like facebook whatsapp etc are running in background)
3. Another major change that i was able to notice was the battery life has improved (comparing to both cm12.1 based /AOSP based/ 5.0.2 stock) specially the stand by time went to bed with 90% and woke up with around 84% (where in cm12.1 it was used to be 70%)
am personally happy with this update even though it was too late. I'd appreciate if motorola could push the 5.1.1 update too since that does not contain any major changes (security patches).
PS: YOUR BOOTLOADER WILL GET UPDATED TO 41:1A this doesn't mean you cannot flash or root. You can flash and root by the same procedures but make sure to use the latest TWRP AND SUPERSU ZIPS.
Click to expand...
Click to collapse
thuva06 said:
TWRP : Please select stock Non-theme version to avoid problems
SuperSU: After flashing TWRP with mfastboot through bootloader use this zip to get root
PS: YOU CAN FLASH ANY 5.1.1 ROMS OVER IT WITHOUT ANY PROBLEM
Click to expand...
Click to collapse
Wow! I was worried that when the next update will come I need to flash stock recovery.

I don't know why but my Moto G with 30-35 apps installed (Facebook,messenger, swiftkey etc...) sometimes it's just freeze for like 10-15 seconds and that wasn't happend in 5.0.2.

Is Static Wi-Fi working?

Mustajab Is'haq said:
Hey OP thanks for the post.
Can you also check if the Screen going completely black issue has been solved as well?
If you check Adaptive Brightness in
Settings>Display and reduce the brightness via the slider the screen goes black. It's like the phone is off, but it's really not. (be careful, don't forget where the slider is so you can crank it up again).
Can you confirm if this is still present in 5.1?
Thanks a lot!
Click to expand...
Click to collapse
It has been fixed in 5.1 for me. I put slider to the extreme left and there was flickering it screen going black at all.
Moto G XT1033 @ Android 5.1

OREO ROM DISCUSSION (Please Share Beta ROM here;if available)

<Mod Edit>
Thread closed.

Any final version release date announce?

Since Oreo official release is somewhat obscure, need some enlightment before flashing this :
1. Kindly confirm I will not lose any data
2. It's WW/Global version
3. In case the official ROM becomes available, can we use the same recovery method to flash it.

All those who are eager to try out this rom but are skeptic as how will it work ,and the the bugs.
To them i will say that go ahead and flash this rom & u will never regret.
No whatsapp bug encountered,its fixed.
The rom is perfect without any bug, no lags infact it is quite stable as an official rom.
and yess the battery backup is better than any of the roms i ever installed on this device,let it be marshmallow or noghat. i usually on my usage would get around 5 hrs sot on noughat, but on this i am glad to inform that i get aroung 6 hrs of sot.
this rom doesnt seem to be a beta.........it is perfect to release officially.
Go ahead and try out the rom guys, and you will thank me the for the advice.

Just installed, seems to be ok for now
Thanks

sanctitude888 said:
Since Oreo official release is somewhat obscure, need some enlightment before flashing this :
1. Kindly confirm I will not lose any data
2. It's WW/Global version
3. In case the official ROM becomes available, can we use the same recovery method to flash it.
Click to expand...
Click to collapse
1) On this new update, please backup all of your data because you will lose it.
2) It's WW version (CN,TW, JP will NOT WORK)
3) I will suggest you to downgrade your phone to Nougat (WW 14.2020.1712.85) and upgrade to Official Oreo ROM by ASUS; if available)

fabiosusej said:
Very good man, the bug whatsApp was fixed? This version works in the west?
it equals the WW version?
Click to expand...
Click to collapse
The bug on WhatsApp is fixed. Remember, it doesn't matter if you are staying in Europe , Japan etc if your phone is WW SKU.
This ROM is for WW SKU ONLY!!!
Have fun flashing

ehbm said:
Any final version release date announce?
Click to expand...
Click to collapse
Probably on February/ March

abbassbhai said:
All those who are eager to try out this rom but are skeptic as how will it work ,and the the bugs.
To them i will say that go ahead and flash this rom & u will never regret.
No whatsapp bug encountered,its fixed.
The rom is perfect without any bug, no lags infact it is quite stable as an official rom.
and yess the battery backup is better than any of the roms i ever installed on this device,let it be marshmallow or noghat. i usually on my usage would get around 5 hrs sot on noughat, but on this i am glad to inform that i get aroung 6 hrs of sot.
this rom doesnt seem to be a beta.........it is perfect to release officially.
Go ahead and try out the rom guys, and you will thank me the for the advice.
Click to expand...
Click to collapse
1) The battery backup isn't great on this Oreo ROM (because it overheats our devices). Marshmallow is way way better in terms of battery life. Nougat ROM is pure sh*t.
2) This ROM contains bugs (for example OIS stabilization, overheating, 2nd row of status bar touch problem (hit or miss), APK installation problem from Telegram etc. So it's partially stable I would say.

Has anyone else realised that battery lasts longer with data saver on

I did not lose data when updating... Even my chrome tabs are there

BulletV2 said:
1) The battery backup isn't great on this Oreo ROM (because it overheats our devices). Marshmallow is way way better in terms of battery life. Nougat ROM is pure sh*t.
2) This ROM contains bugs (for example OIS stabilization, overheating, 2nd row of status bar touch problem (hit or miss), APK installation problem from Telegram etc. So it's partially stable I would say.
Click to expand...
Click to collapse
Well thats wierd because i didnt encountered any of the above problems you have listed.
my phone doesnt gets heated even on heavy usage. battery backup is great (3 cycles with 6 hrs sot each)
no apk installation error i got, even ive installed telegram.
only one bug i encountered was while using twin app feature for whtsapp, the twin whatsapp profile pic was not able to upload, but thats nothing.
i love the fluidity of the rom.

The lock screen clock is the worst looking clock I have ever seen on Android. Is there a way to change it?

Treble ROMs and sh*t battery life: suggestions to improve?

Right now I've testing Phh Treble 8.x (based on pure AOSP) for the past 2 weeks, and I'm mostly liking what I see.....except the battery drains too fast. I'm getting about 4 to 6 hrs SOT. Drain when idle/dozing isn't too bad, except when my 4G LTE signal gets weak in certain areas.
Some basic info:
Kernel: Schwifty v5
SELinux always permissive (by unpacking boot.img with Android Image Kitchen, making a few edits, then repacking)
ROM is pre-rooted with Phh's Superuser (already built into ROM, not by me, I wont touch Magisk)
ROM is deodexed, I did this manually with SuperR's Kitchen, the GSI as provided is odexed by default
Xposed installed, with 2 modules (ForceDoze for doze parameter tweaking, and GravityBox O)
Data/cache are ext4 (I gave up on F2FS after getting some extreme corruption/instability on other devices I own)
Bootstack: I have tried @Oki's modded B12 bootstack, as well as LOS 15.1 bootstack
Modem: LOS 15.1
boot.img/vendor.img sourced from LOS15.1
No GApps package/components are installed (I do, however, use MicroG, Play Store, and F-Droid for apps)
I currently charge twice a day, I use Battery Charge Limit to limit charging to 80/85%, and start charging between 10 to 20%. I dont charge in between at all, except maybe for short emergency sessions when I cant afford risking the battery dying. I use the ZTE stock power supply and a Anker PowerLine braided cable (original ZTE cable shorted out months ago and couldnt reliably transfer data to/from PC). Ampere shows my battery capacity to be 3100mah, which I believe is normal and healthy for an A7.
I have tried with the stock boot.img (patched by Schwifty), and my modded img that sets SELinux permissive, no difference in battery life. I need it set that way because my dalvik cache directory doesnt populate after deodexing, SElinux blocks something when enforcing, making for long boot times (up to several mins). I have also tried without Schwifty. I tried Hellsgate as well but there are too many app forced closed that does not occur with Schwifty.
I deodexed the ROM because I use MicroG, it requires a patched framework.jar for signature spoofing support. But you cannot patch an odexed framework.jar.
In regards to bootstacks, there seems to be no discernable difference in battery life, regardless of whether I'm using modded B20 BS or LOS15.1 BS. It is said that B12 BS isnt battery efficient, but LOS BS doesnt seem to be any better.
As for the modem, maybe I will try with B12/B20 stock A2017U modem instead of LOS, I personally believe that the modem may be playing a role in this, since battery seems to drain much faster in low signal areas.
I chose LOS boot.img/vendor.img as the best choice, because they are updated regularly, whereas our other devs dont update these images (required by Treble ROMs) very often. ZTE never blessed up with official Treble support, so the onus is on the dev community to carry the mantle and keep these up to date.
At this point I am about ready to go back to AOSP Extended Nougat and call it a day, SOT there was much better with Radioactive kernel. But Phh Treble is smooth, stable, no lags or crashes, and I have found alternatives/workarounds for all the functionality I need. I am a minimalist by philosophy, I dont like to install lots of apps or unnecessary stuff, preferring to keep things to the essentials. But I would like to continue testing for awhile longer before turning back.
I started this thread to solicit suggestions in regards to better battery life on Treble ROMs.
A few absolutes:
1. I will not use Magisk under any circumstances
2. Pie ROMs wont be considered, since Xposed doesn't support Pie
3. I will not use LOS as my ROM, because it gets too many OTA updates (almost every day). I like to make direct changes to the system partition (no Magisk systemless mods), frequent updates mean I constantly have to undo/redo my changes. Phh Treble gets updates once every couple of months, I can deal with that cycle.
Thanks!

AnonVendetta said:
I started this thread to solicit suggestions in regards to better battery life on Treble ROMs.
Thanks!
Click to expand...
Click to collapse
Did you try raystefs new crDroid build?

What has a other build to do with battery life? Change your Battery lol.And 4 - 6 hours sot is good,not something to complain about i think.And maybe check your fuel gauge as more people report they gauge is of

This thread makes me laugh very hard. Thank you for making me live another day from laughing. ?

@EBeatFLA: crDroid, while being as good as any other 8.x ROM for the A7, has one major flaw:
It is only rootable with Magisk. I tried rooting it by flashing SuperSU, the standalone versions of Phh, and the Treble flashable Phh root zip, none worked. All of these are supposed to patch sepolicy, normally located in the ramdisk within boot.img, but it seems that with Treble sepolicy has moved elsewhere, probably to /vendor. With Treble these zips cant patch sepolicy since it isn't in the expected location. There is also a LOS su addon which might work, but many of my root apps dont work with it, and it doesnt support automatic script execution on boot. In short, I won't use a ROM that locks me into Magisk as the only root solution.
@Predatorhaze: Have you been using Android very long? I have, since 2009. That is long enough to know that what ROM you choose will have a major impact on battery life. Some ROMs are good for this, others not so much. There is nothing wrong with my battery, 3100mah is normal for our device, and I've verified this number with several apps. In fact, ZTE returned to me a refurbished device a little more than 2 weeks ago, so I assume the battery is fine and not degraded. Refurb means, basically, a used device that has been tested and is certified to (theoretically) work as well as a new device of the same model. 4 to 10 hrs SOT isnt very good, not to me, not when I was previously getting 8 to 10 on AOSP Extended N. Besides, the battery drain issues with Treble have been voiced by many others, I'm not the only one.
@SaintZ93: I have to ask what you find funny. I start a serious discussion, you drop in with a 2 sentences post that offers no useful info and adds nothing useful. It's too bad there isn't a dislike/not thanked button below every post, because I would be clicking it right now.
I'm currently testing Resurrection Remix 8.x official GSI, under similar conditions, battery life is a bit better, but not by much. One thing I have noticed with both ROMs is that when the % drops, oftentimes it will be more than one, like from 85 to 83 almost as soon as I unplugged it, with the device idle on home screen and not being used.

You want info? SuperSU is way old and out dated so you have no choice but to deal with magisk.

@AnonVendetta:
I'm currently testing Resurrection Remix 8.x official GSI, under similar conditions, battery life is a bit better, but not by much. One thing I have noticed with both ROMs is that when the % drops, oftentimes it will be more than one, like from 85 to 83 almost as soon as I unplugged it, with the device idle on home screen and not being used.[/QUOTE]
i have these same problems with battery %,and my battery from 1 year old still sits on 2800mah.Everyone has the same problem

Recommendation

NEED rom Recommendation Battery+Performance+Customization (if possible)
Doesn't matter if its oreo or pie based
Currently On Stock Oreo January Security patch
Performance is Not Good,Battery hardly survives
3hrs on screen Time

3 hours screen on time - battery needs replacement. Its just 10 bucks. Get a new battery for 10 bucks and swap it or get used to run everywhere around with a powerbank connected to your phone.
I got 2 days with fresh battery and latest stable LineageOS image clean installed (with ./flash-all.sh and TWRP)

@abdullahk6809
Alright, so i figured it would be easier to post via my computer rather than my phone.
TLDR : If you don't want to read all of this then stick with 8.1 roms for the best battery life and no issues. Cr droid and Resurrection Remix both posted their final 8.1 builds and both have run flawlessly for me. The same goes for AICP and AFAIK they are still merging up stream changes though minor with their weeklies.
As far as 9.0, we do not have official support, so it's still being worked on to get the best experience/no issues. AICP 9.0 has worked out the best for me with 9.0 then followed by Resurrection Remix.
There is a huge thing you need to be aware of if you're not already, that being our 9.0 roms currently use two different types of encryption. AOSIP, AICP, Resurrection Remix, CR Droid all use full disk encryption. (FDE) which is the same encryption we have always used. For that you just use the offical TWRP. All of the 9.0 stock roms currently are using file based encryption(FBE) and for that you need to use a specific TWRP that was made for it, and if you are currently on FDE (which you are) you need to format data after flashing the rom, meaning you will WIPE ALL OF YOUR INTERNAL. IF you decide to go back to an 8.1 rom, or try one that uses FDE, you will need to do the same process. Switch back to the offical TWRP, and format data after you flash the rom. If you go to FBE and stay on it, then you do NOT need to format data/switch twrp going one from FBE rom to another FBE rom, or updating the current rom.
So when choosing what to flash, you need to read the OP of each rom and know which encryption it uses, or it will not boot. Roms that run FBE AFAIK always have the twrp needed linked in the OP.
With 9.0, as i said, it is still a work in progress since we have lost official support. So if you read the threads some people are reporting issues with calls, Volte, issues with whatsapp etc.. So read the threads at least the last 15 or so pages to see if people are currently having issues. Like i said previously i could tell you to go flash x rom, because it works the best for me. But then you have issues because you use whatsapp and can't send voice messages or w/e and i don't use it. With people using the device for different reasons, you need to take time to see what works for you versus just a one word answer that will work for you.
A lot of people are having issues with 9.0 because of battery life, but I do not see a huge decrease in battery life, but i don't use battery killing apps like face book, whatsapp, or play games or anything. If you really are only getting 3 hours SOT you might want to see what is using your battery via better battery stats or gsam, because it's possible apps could be doing it, and no rom will change that. If you find out that no rouge apps are really killing your battery, as was just stated, depending on how old the device is, you might need a new battery. This phone is a good device but they used pretty ****ty components on it, thanks China. I myself have not had battery issues but i bought my device like three or four years ago, some devices are older.
Anyways, that's about all i can really offer for advice, i don't spend nearly as much time on this forum as i used to because i end up getting into confrontations with people that spread misinformaation, or refuse to follow simple courtesy that are not rules such as asking for eta's etc..
If you end up having any questions i might be able to answer, send me a PM. It might take me some time to respond as i don't use the app as much as i used to, but i'm always willing to answer even the dumbest question when asked via private message.

Lawlrus said:
@abdullahk6809
TLDR : If you don't want to read all of this then stick with 8.1 roms for the best battery life and no issues. Cr droid and Resurrection Remix both posted their final 8.1 builds and both have run flawlessly for me. The same goes for AICP and AFAIK they are still merging up stream changes though minor with their weeklies.
Click to expand...
Click to collapse
Hi Lawlrus, I'd just like to have a stable rom. Like you said 8.1 rom might be my best choice, but RR has stopped updating the 8.1 version so what I worry about is it's lacking security patches.
So would you suggest some roms that's stable and and getting updates as well ?
What I might need is :
1. dark theme 2. night light (blue light filter) 3. probably fling nav bar