[ROM][UNOFFICIAL][9] LineageOS 16.0 [deb][flo]

[followmsi]

Build 0501, kernel from 0501: Deep Sleep = yes, 2%/hour, screen tearing

Build 0501, Unlegacy kernel with Unlegacy config: Deep Sleep = yes, 1.7%/hour, screen tearing, tablet overall slow

Build 0501, Unlegacy kernel with FollowMSI config: Deep Sleep = yes, 1.9%/hour, screen tearing



Build 0427, kernel from 0427: Deep Sleep = no, 2%/hour

Unlegacy Pie: Deep Sleep = yes, 0.6%/hour

LOS 14.1: Deep Sleep = yes, 0.25%/hour

As it looks like the kernel replacement does not improve a lot ..

Pls test lineage version before 04/21 .. here we still use CAF sources and another device tree.

Are you able to determine the service/process/app which is draining battery on your deb ?

If you use tools like betterbatterystats .. do you see the "culprit" ?


Maybe this one ..
https://forum.xda-developers.com/showthread.php?p=79439386

 

[sidamos77]

As it looks like the kernel replacement does not improve a lot ..

Pls test lineage version before 04/21 .. here we still use CAF sources and another device tree.

Are you able to determine the service/process/app which is draining battery on your deb ?

If you use tools like betterbatterystats .. do you see the "culprit" ?

At least it goes to deep sleep since 0501. BBS or GSAM point to the kernel as the culprit.

I started my LOS Pie tests with version from 04/13. This also did not go to deep sleep and drained 2%/hour.

I find it strange that 0501 does go to deep sleep and still drains 2%/hour.

 

[followmsi]

At least it goes to deep sleep since 0501. BBS or GSAM point to the kernel as the culprit.



I started my LOS Pie tests with version from 04/13. This also did not go to deep sleep and drained 2%/hour.



I find it strange that 0501 does go to deep sleep and still drains 2%/hour.

If you check kernel wakelocks in bbs ?

What about sensors section in bbs ? .. what is listed here ?

 

[sidamos77]

If you check kernel wakelocks in bbs ?

What about sensors section in bbs ? .. what is listed here ?

Right now, I have installed Unlegacy again for comparison. But I remember checking wakelocks and sensors with LOS before 0501. There were no wakelocks and only acceleration sensor usage from Nova launcher.

 

[jhford]

Deb. Am I the only one experiencing "screen tearing"? Great descriptive phrase. Wish I had thought of it yesterday.

 

[followmsi]

Right now, I have installed Unlegacy again for comparison. But I remember checking wakelocks and sensors with LOS before 0501. There were no wakelocks and only acceleration sensor usage from Nova launcher.

I don't use Nova launcher but for example Spotify app does also hook on accelerator sensors .. and does drain battery.
If I kill Spotify app to release accelerator sensors the flo device starts to sleep very well.

Back in Oreo the "earlysuspend" code got removed from kernel .. lineage, EX and "my" kernel too.
Unlegacy is still using it .. and I remember discussions about this topic at this time .. also about sensors and sleep.
For this reason we did test the Unlegacy kernels now.

Needs to be tested if Unlegacy does not have the same sensors issues.

For Deb we have the USB modem and it's wakelock issue too.

 

[tiaka1]

Won't turn off

Hi
I have just installed lineage 16 on my nexus 7 2013 wifi.
Followed all the instructions.
Every thing works fine except it won't turn off.
It keeps rebooting.
The only way to turn it off is to boot into boot mode and turn it off there.

I going to put up with it but I thought I would let you know.

Cheers

 

[sidamos77]

Deb. Am I the only one experiencing "screen tearing"? Great descriptive phrase. Wish I had thought of it yesterday.

I wrote about that a few posts above. Disable HW Overlays in developer settings. This removes 99% of the tearing. Although this setting does not survive reboots.

---------- Post added at 11:05 PM ---------- Previous post was at 10:54 PM ----------

Needs to be tested if Unlegacy does not have the same sensors issues.

With WiFi off during standby (enable Airplane mode with Tasker on screen off), Unlegacy only uses 0.3%/hour, same as LOS 14.1 with WiFi off during standby. So, it is possible with Pie.

I checked sensors on Unlegacy in BBS. Google Play Services and Nova use Accelerometer all the time also. I have made screenshots and will compare with LOS 0501 tomorrow.

 

[MaxPowerOne]

I have a bug, clean install the bottom bar glitches out graphically on the central dot (the one to go back to launcher), could you fix that? Clean install, is yours giving the same glitch?

 

[JT1510365]

I have a bug, clean install the bottom bar glitches out graphically on the central dot (the one to go back to launcher), could you fix that? Clean install, is yours giving the same glitch?

Yes this is an issue with all pie ROMs for this device for some reason I don't know what causes this or how to fix it

 

[MaxPowerOne]

Yes this is an issue with all pie ROMs for this device for some reason I don't know what causes this or how to fix it

Ok thanks, the newest update is broken, all animations are desyncronized, I tried 2 installations.

 

[ranaxda200]

Anyone facing recognisable frame drops while screen transitions?

 

[followmsi]

With WiFi off during standby (enable Airplane mode with Tasker on screen off), Unlegacy only uses 0.3%/hour, same as LOS 14.1 with WiFi off during standby. So, it is possible with Pie.

I checked sensors on Unlegacy in BBS. Google Play Services and Nova use Accelerometer all the time also. I have made screenshots and will compare with LOS 0501 tomorrow.

Yesterday I had some time to look .. Unlegacy is using different sensors wrapper.

I have cherry picked this change for testing .. looks good.
https://github.com/followmsi/android_device_asus_flo/commit/02f62fb2cc0d13afe0ba4e74ae90282d0b57c238
Sensors seems to be more "sleepy" now.

For testing you can replace the lib your self .. maybe not on 05/01 test build.
sensors.msm8960.so.zip

@ripee you may make a new build .. using "normal" kernel again.

Added wakelock group for deb as well ..
https://github.com/followmsi/android_device_asus_deb/commit/57b81be3a8c497ae7a04a324b5cd47e6a9d6e2ae

Cheers

---------- Post added at 10:47 ---------- Previous post was at 10:41 ----------

Mod edit - quoted post deleted

Pls think about your communication style.

Thanks

 

[ripee]

Changelog

2nd build 0505 for both variants
* If you flashed 0505 already, flash the one that is currently up, as it is the updated one.
* Wakelock and sensors fixes added, as per followmsi's post #233.
* NFC is tentatively fixed, as per followmsi's commits from May 5, 2019.
* Synced with LineageOS sources.

 

[sidamos77]

@ripee
@followmsi

Here is the result of my 12 hours standby comparison between Unlegacy and LOS 0501 (with kernel 0501) on my deb.
Both standby in airplane mode. Both do deep sleep. 99% (Unlegacy) and 100% (LOS 0501).

Drain:
Unlegacy: 0.3%/hour (0.6%/hour with WiFi on)
LOS 0501: 1.3%/hour (2%/hour with WiFi on)

Screenshots from BBS attached. You can see that the Amazon Kindle app does quite a lot of partial wakelocks. I do not have this installed on Unlegacy. This may be responsible for a tiny bit of difference. I will uninstall this after the next test.

Next I am testing with LOS 0505 the new sensors code.

Thanks for your work and help!

 

[shugal]

Thanks & couple of questions

First of all: many thanks for keeping my beloved Nexus 7 alive! :good:

Secondly, a couple of questions (sorry if I've managed to miss earlier answers):

1. After doing the repartition, flashing ROM and Gapps and everything works fine is it ok to update TWRP?

2. Just updating the ROM, all I have to do is a dirty flash, also having to flash Gapps again?

Thanks in advance!

 

[nmichalo]

installed latest 0505 build on my FLO and I think it is very good. The shoutdown function works properly and my imprssion is that it is a little faster than the 0427 that I use to have. Great job ripee & followmsi

---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------

First of all: many thanks for keeping my beloved Nexus 7 alive! :good:

Secondly, a couple of questions (sorry if I've managed to miss earlier answers):

1. After doing the repartition, flashing ROM and Gapps and everything works fine is it ok to update TWRP?

2. Just updating the ROM, all I have to do is a dirty flash, also having to flash Gapps again?

Thanks in advance!

I have done both things with dirty flash without a problem. But I update twrp version from recovery within twrp.

 

[sidamos77]

Yesterday I had some time to look .. Unlegacy is using different sensors wrapper.

I have cherry picked this change for testing .. looks good.
https://github.com/followmsi/android_device_asus_flo/commit/02f62fb2cc0d13afe0ba4e74ae90282d0b57c238
Sensors seems to be more "sleepy" now.

LOS 0505 now only drains 0.4%/hour with WiFi off (and NFC off).
This is pretty good, only slightly more than Unlegacy. I will check over the next days how it continues.
Thanks a lot to @ripee and @followmsi!

 

[Neur0Nerd]

I flashed the su remover and I get vendor mounting errors, anybody has the same issue when flashing zips ?

 

[ripee]

I flashed the su remover and I get vendor mounting errors, anybody has the same issue when flashing zips ?

My last few builds have not included lineage su root, so perhaps it has something to do with that, but I have never heard of the su addon remover causing those kinds of errors.

Wipe System, Cache, and Dalvik. Then flash the rom zip, gapps, and Magisk if you wish.