Database Users

There is a huge bug on LINEAGE OS. The bug is when your device has 25% battery or les

There is a huge bug on LINEAGE OS. The bug is when your device has 25% battery or lessthan 25% the phone dead within 1 min. why. in stock rom it will run aronud 1 hour lineage need to fix this

Do you THINK it might help for you to provide some obscure information such as which device, what ROM 14.1, 15.1, etc.. and maybe, just MAYBE, a log? Developers are NOT all known for their psychic prowess, despite what you have heard. FYI - NONE of my Lineage devices exhibits this problem.

Device ASUS ZENFONE 2 ZE550ML
LINEAGE OS VERSION 14.1

I have also suffer this problm

Is that an official build ?
asik_alom_rahman said:
Device ASUS ZENFONE 2 ZE550ML
LINEAGE OS VERSION 14.1
Click to expand...
Click to collapse
Don't own that device but also don't seem to see it on the LOS downloads page. If it is an unofficial build, you are not going to get a whole lot of official love on this issue. ASSUMING it is an unofficial build, I would send a log file to the dev and see what can be done about it. Never hurts to ASK, after all. Good Luck.
---------- Post added at 10:23 AM ---------- Previous post was at 10:22 AM ----------
titans.raid said:
I have also suffer this problm
Click to expand...
Click to collapse
Same device ? Same build ? Difficult if not impossible to offer more assistance without specifics.
ALSO, HOW OLD IS THE BATTERY ?? One of the symptoms of a failing battery (in my limited experience) is sudden death below a certain assumed level of charge. If the battery is trashed, no ROM in the world will save it.

This isn't a software issue but a battery issue. Changing it will fix the problem. It could, however, be related to CPU clock.

you can solve it by installing a custom kernel. i have a redmi note 3 (kenzo), ive put franco kernel and it works like a charm - at least for me, no more problems. franco kernel you cand find it on goole (cant let the link here, newbie issue )

Will we get Treble for GSI ?

Hello,
after testing out lots of ROM with Treble, I used some GSI and some of them worked more some less. In the Treble Development department I found a working AOSP 9 GSI. The ROM did work quite good and I would use it as a daily driver, but sadly the battery consumption was the greatest I ever had.
Maybe it is because of the ROM, but after all the vendor image should also be good. The only one we can use is from nfound and he left us...
So, what do you think? Will there every be a vendor image we can use for GSI?

yes.

Did you try this one: [AOSP 9.0] [EXPERIMENTAL] [2018-08-22] Phh-Treble ?
Cause this is the one, that gives me a SOT of about ~ 5h , which is ok for me right now ...
(altough, using AEX 5.8 SOT was 6-7h for me ...)
But it is in development ...
Mart Son said:
Hello,
after testing out lots of ROM with Treble, I used some GSI and some of them worked more some less. In the Treble Development department I found a working AOSP 9 GSI. The ROM did work quite good and I would use it as a daily driver, but sadly the battery consumption was the greatest I ever had.
Maybe it is because of the ROM, but after all the vendor image should also be good. The only one we can use is from nfound and he left us...
So, what do you think? Will there every be a vendor image we can use for GSI?
Click to expand...
Click to collapse

timmtomm8 said:
Did you try this one: [AOSP 9.0] [EXPERIMENTAL] [2018-08-22] Phh-Treble ?
Cause this is the one, that gives me a SOT of about ~ 5h , which is ok for me right now ...
(altough, using AEX 5.8 SOT was 6-7h for me ...)
But it is in development ...
Click to expand...
Click to collapse
There is another one based on this one, because this one gave me to much errors. Maybe the new GSI got better...
Did you flash some post GSI zips or did it work out of the box?

So at the moment we only have nfounds vendor image which boots up most gsi, but there are problems not solved. My great hope was that we will get a good vendor image with lineage, but it does not boot any gsi at the moment.
Nfounds vendor seems to be compatible with Oreo and pie. At the moment there is no sign for a pie only vendor image what would be great

Do all the GSIs available for the A7 get the irritating "vendor image mismatch" or "there's an internal problem with your device" on every bootup? I know it can be ignored but it's just annoying as hell. What causes this? I read that it has something to do with the boot/vendor signature/fingerprint not matching what the ROM expects to see. Is there a solution that makes these messages go away? I'm interested in trying a Treble Oreo GSI, but I need a daily driver that can be counted on, and so far I've had very little luck with getting GSIs to boot.
Which vendor image and boot image is correct for an A7 running a Treble ROM? The ones by Nfound? Or LineageOS? Or something else? It would be nice if ZTE would update our device to official Oreo and officially adopt Treble and a vendor partition. The A7 is classified by ZTE as an end of life/support device, with the Axon 9 due soon, the least they can do is bless us with this one last gift as a farewell.
I wouldnt mind running Pie, but I like using Xposed modules, so no go there. On the Oreo GSIs I've tried, exFAT MicroSD usually shows up as corrupt. This is unacceptable to me. And I must have my cache and data partitions as F2FS, for best performance. And a custom kernel.

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

Linage os 17.1/18.1 running on nitrogen

Hi.
I don't know why, but information about unofficial release of LOS never have been posted here. If there's some legal issues, just delete my post. I have 18.1 running perfectly on my nitrogen. Maybe this is good moment to revive some of our old big nitrogens
Enjoy. It's really great.
Download and Install Lineage OS 18.1 on Xiaomi Mi Max 3 (Android 11)
In this tutorial, we will show you how to download and install Lineage OS 18.1 on Xiaomi Mi Max 3 (nitrogen) device. The Google-owned
www.getdroidtips.com
Cheers

linus207 said:
Hi.
I don't know why, but information about unofficial release of LOS never have been posted here. If there's some legal issues, just delete my post. I have 18.1 running perfectly on my nitrogen. Maybe this is good moment to revive some of our old big nitrogens
Enjoy. It's really great.
Download and Install Lineage OS 18.1 on Xiaomi Mi Max 3 (Android 11)
In this tutorial, we will show you how to download and install Lineage OS 18.1 on Xiaomi Mi Max 3 (nitrogen) device. The Google-owned
www.getdroidtips.com
Cheers
Click to expand...
Click to collapse
Can't you detect any bug?
It would be good to follow up on its correct operation
Thanks for the info

Voretmv said:
Can't you detect any bug?
It would be good to follow up on its correct operation
Thanks for the info
Click to expand...
Click to collapse
I can't detect any bug. Everything is just great. I highly recommend los. It's way more smooth and battery friendly than miui 12.

Does gcam work?

landsome said:
Does gcam work?
Click to expand...
Click to collapse
It's actually default camera app.

linus207 said:
It's actually default camera app.
Click to expand...
Click to collapse
I've just installed it myself - the latest JoysKo version from 4pda.ru. Have not tested it thoroughly, though. Will report more soon. But...
GCam works. After having tried some two dozen versions (which either stopped immediately or did not install at all), I used MGC_6.2.030_FinalRelease_Bulkin043_V9Q, which is known to work on AOSP-9 based custom roms. I am not entirely sure it's perfect, but the basics work. (One may have to change the saving location, though.)
The only issue so far once fully booted - but I barely tested it - is that I seem to have deep sleep problems with third-party launchers (Nova, Lawnchair 2 etc.); Trebuchet works. It does not seem to be caused by widgets - but I need to explore more.
Another problem is common from AOSP9-based 3rd party roms: sometimes, on rebooting, the phone gets stuck (the "Unlocked" logo phase). A simple restart resolved it.
I have not sorted out passing SafetyNet yet (Magisk props fingerprints are apparently not enough).
Happy to report the terrible scrolling issues plaguing AOSP9-based roms here on XDA are completely absent.
Finally, battery life, even without deep sleep, is very good.

How did you recognized deep sleep issue? I am currently running Lawnchair 2 having 94% deep sleep while screen off.
Maybe it's gapps issue/play services? I am using open gapps test version for 11.

linus207 said:
How did you recognized deep sleep issue? I am currently running Lawnchair 2 having 94% deep sleep while screen off.
Maybe it's gapps issue/play services? I am using open gapps test version for 11.
Click to expand...
Click to collapse
Same gapps here. I use Accu Battery and it reports it. I have the same problem if very unreliable sleep on two other phones using los18.

This thread deserves more views. I happened to try the android 11 based Havoc rom from April 2021 and it runs smooth. Everything works perfectly, and I've been using it as a daily driver for the last week.
Thank you JoysKo!
If anyone can point me how to replace the stock cam with gcam- it would be much appreciated!

Voretmv said:
Congratulations on your work. I have this Rom installed on my Mi Max 3, and I am very happy.
Do you have any evolution of this Rom that I am not aware of?
I currently have Lineage-18.1-FORK-vanilla-20210124-nitrogen-JoysKo installed
Click to expand...
Click to collapse
I tried the more recent versions of LOS uploaded by JoysKo and reverted to 0124. For me, it's the best. With the 2 others I had janky scrolling, malfunctioning gestures.

Vandetta187 said:
This thread deserves more views. I happened to try the android 11 based Havoc rom from April 2021 and it runs smooth. Everything works perfectly, and I've been using it as a daily driver for the last week.
Thank you JoysKo!
If anyone can point me how to replace the stock cam with gcam- it would be much appreciated!
Click to expand...
Click to collapse
With the LOS 20210124, I just installed one of the few working gcams. Specifically 6.2.030 Final Bulkin043 V9Q.

landsome said:
With the LOS 20210124, I just installed one of the few working gcams. Specifically 6.2.030 Final Bulkin043 V9Q.
Click to expand...
Click to collapse
Yeah I tried that one you mentioned however I get app not installed error message.
Is there another version that might work?

Vandetta187 said:
Yeah I tried that one you mentioned however I get app not installed error message.
Is there another version that might work?
Click to expand...
Click to collapse
I tired several that did not. Works for me on Lineage-18.1-FORK-vanilla-20210124-nitrogen-JoysKo, though. (I installed both newer versions of the ROM and as far as I remember it worked on them too - but I replaced them later.)

Thank you so much for this thread. Installing Lineage is like a walk in the park like this. The only problem I come across is when I want to play back videos in some apps or Chrome. I get errors like video can not be played and SOURCE_STREAM_TYPE_NOT_SUPPORTED. I think this might be a firmware issue or is there another solution available?

Hello together
With last Lineage OS 18.1 fork-vanilla I've problems with loosing fingerprints after a while and GBoard-function with full NikiGapps is buggy.
Now I'm back to preversion and fingerprint problems are solved. Only changing to GBoard was not so good idea

linus207 said:
Hi.
I don't know why, but information about unofficial release of LOS never have been posted here. If there's some legal issues, just delete my post. I have 18.1 running perfectly on my nitrogen. Maybe this is good moment to revive some of our old big nitrogens
Enjoy. It's really great.
Download and Install Lineage OS 18.1 on Xiaomi Mi Max 3 (Android 11)
In this tutorial, we will show you how to download and install Lineage OS 18.1 on Xiaomi Mi Max 3 (nitrogen) device. The Google-owned
www.getdroidtips.com
Cheers
Click to expand...
Click to collapse
I installed arrow and Los but all meet same problem. The message can not be received. Try to install global FW+ vendor at first but Stuck on the boot screen . Any good suggestion?

Hi, I was also very pleased to see Lineage on the Mi Max 3, still using this device due to the large screen I love.
Has anyone exerperienced bluetooth connection issues?
It connects to my speaker and then immediately disconnects and of course then wont play any music?
ROM version I used is lineage-18.1-20210608-nitrogen-experimental-PRGroup.zip
Any known fix as yet?
Previous versions do not have bluetooth issues like this?
Thanks.

dhodson7171 said:
Hi, I was also very pleased to see Lineage on the Mi Max 3, still using this device due to the large screen I love.
Has anyone exerperienced bluetooth connection issues?
It connects to my speaker and then immediately disconnects and of course then wont play any music?
ROM version I used is lineage-18.1-20210608-nitrogen-experimental-PRGroup.zip
Any known fix as yet?
Previous versions do not have bluetooth issues like this?
Thanks.
Click to expand...
Click to collapse
Update on this bluetooth issue....
I have wiped and installed this rom now
Lineage-18.1-FORK-vanilla-20210124-nitrogen-JoysKo.zip​all works fine now....
still interested if anyone has a resolution to the BT issue though?

The latest of the latest versions of Lineage 18.1: https://t.me/MiMax3Update/211
Many problems have been fixed in it. It is advisable to install cleanly...
Regard, JoysKo.
P.S.: For DT2W use this module…

JoysKo said:
The latest of the latest versions of Lineage 18.1: https://t.me/MiMax3Update/211
Many problems have been fixed in it. It is advisable to install cleanly...
Regard, JoysKo.
P.S.: For DT2W use this module…
Click to expand...
Click to collapse
Thanks. Got it from Telegram a few days ago. I can confirm it works great. Better than the January version, which was the best before in my view. Do try to install from Orange Fox, however, not TWRP.