[ROM][flo|deb][UNOFFICIAL][LineageOS 18.1] -> 2020-12-11

[followmsi]

Im using latest 7.1.2 build. Recently i noticed, that idle battery consumption became much bigger. It used to be ~0,5%/hour and now its almost 2%/hour. I installed BBS and there isnt anything wrong. Tablet goes into deepsleep as it should, doze is olso working. Im using greniffy to calm down Facebook Messenger. What is eating my battery ?
Note : im using ElementalX kernel

I tried restarting it a few times - is didnt help

Keep the kernel from ROM, do not use EX Kernel and check battery life again.

Sent from my Nexus 10 using Tapatalk

 

[MikiGry]

The problem is, that I have been using EX for about a month and idle drain was around 0.5%/hour and since one week it increased :/

 

[followmsi]

The problem is, that I have been using EX for about a month and idle drain was around 0.5%/hour and since one week it increased :/

The Nougat ROM was using EX kernel sources for some time.
Due to battery drain issues I have moved to "stock" lineage kernel sources.

Already some time ago .. not since last month only.
I guess it's related to activated dt2w .. etc. .. not sure.

There are no (planned) changes for Nougat kernel anymore ..

Looking forward for the EX Oreo version ..

 

[MikiGry]

I dont use dt2w and similar features...

 

[craigholm]

With the AOSP_8.0.0_r13_OPR1.170623.027_flo-ota-eng.followmsi_BETA-8.zip ROM, I can't enter a hex key as the Wi-Fi password.

Wi-Fi allows a password between 8 and 63 characters, or the actual key itself (64 hex characters). After flashing it with this ROM, however, the connect button is disabled if the length is more than 63.

With the 7.1.2 ROM it works correctly. I have another device running Oreo and this isn't an issue.

 

[followmsi]

With the AOSP_8.0.0_r13_OPR1.170623.027_flo-ota-eng.followmsi_BETA-8.zip ROM, I can't enter a hex key as the Wi-Fi password.

Wi-Fi allows a password between 8 and 63 characters, or the actual key itself (64 hex characters). After flashing it with this ROM, however, the connect button is disabled if the length is more than 63.

With the 7.1.2 ROM it works correctly. I have another device running Oreo and this isn't an issue.

Need to check .. will take time.

Will not validate on Nougat, I assume you are right and it's working

Just tested on another device too .. Oreo AOSP ROM .. does not work either.
Only 63 digits .. does not accept 64 hex.

Which Oreo ROM is working ? .. for which device ?

EDIT:
Had a quick look ..
https://productforums.google.com/fo...ZLTTQlGJ4;context-place=forum/phone-by-google

Maybe "your" Oreo ROM has been fixed and we can cherry-pick the changes ..

 

[craigholm]

Need to check .. will take time.

Will not validate on Nougat, I assume you are right and it's working

Just tested on another device too .. Oreo AOSP ROM .. does not work either.
Only 63 digits .. does not accept 64 hex.

Which Oreo ROM is working ? .. for which device ?

EDIT:
Had a quick look ..
<removed>

Maybe "your" Oreo ROM has been fixed and we can cherry-pick the changes ..

After further investigation, it looks like my Oreo device (a Nexus 5X) actually has the same issue--it seemed to work because the networks I set up before upgrading it (from Nougat) continue to work correctly, but it isn't possible to set up new networks without running into the same problem.

So, it definitely seems like a bug in the Oreo settings app, not a specific ROM. Thank you for your quick response.

 

[MikiGry]

Flo decided to fix itself. I have fully charged it during night, unplugged it in the morning and left it connected to WI-FI. And this is what i saw a few mintues ago

After 9 hours of standby it only ate 2% battery. So drain is gone. I hope its not going to come back

 

[MadHacker]

finally got the latest version (beta 8.3) to work with opengapps pico without play services crashing all the time..... Any on else not have OK GOOGLE working ????

 

[drewski_1]

finally got the latest version (beta 8.3) to work with opengapps pico without play services crashing all the time..... Any on else not have OK GOOGLE working ????

OK Google working for me, but using Stock package with a GApps-Config file.

IIRC, you need Google Search as a system app, which isn't in Pico. you could try Nano, the next size up which has Google Search . . . or did that cause errors for you too?

 

[vagelis74]

What camera app working with rom;why after flash the rom lose twrp recovery;can boot to bootloader but cannot boot to recovery,recovery error f2fs

 

[followmsi]

There are still a few issues left .. for this reason I would like to keep the name BETA

AOSP_8.0.0_r28_OPR1.170623.032_flo-ota-eng.followmsi_BETA-9.zip
AOSP_8.0.0_r28_OPR1.170623.032_deb-ota-eng.followmsi_BETA-9.zip

Changes: (since BETA-8)
- New month .. new sources -> Nov 2017 security patches -> android-8.0.0_r28
- Launch QMUXD process as root user
- Enabled FunctionFS (USB)
- Build hidl health & thermal implementation
- Removed "earlysuspend" hack in system/core
- Added "signature spoofing" base patch (patch included; but not working yet)
- Created rild service in init.rc (deb only)
- Added HIDL radio implementation (deb only)
- Added gps.conf (deb only)

NFC: on/off toggle still buggy

Camera: We build HAL1 camera now .. like in Lineage too.
The AOSP camera app is NOT working.
Apps like the camera below are working fine ..
https://play.google.com/store/apps/details?id=com.peace.SilentCamera

RILD (deb only):
- Data connection (3G/LTE) seems still to have problems.
- No changes are done for RILD anymore .. same changes as in 8.3

New kernel -> 2017-11-06
- DT2W, Sweep2sleep, Sweep2wake: disabled per default
(Pls use EX-Manager, Kernel-Auditor or similar apps/tools to enable DT2W, Sweep2sleep and Sweep2wake)
- Security patch for "KRACK" attack
- Latest Lineage changes

Sources:
https://github.com/followmsi/manifests/tree/flo-deb-aosp-o
https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2017-11-06

Enjoy

 

[gege622]

There are still a few issues left .. for this reason I would like to keep the name BETA

AOSP_8.0.0_r28_OPR1.170623.032_flo-ota-eng.followmsi_BETA-9.zip
AOSP_8.0.0_r28_OPR1.170623.032_deb-ota-eng.followmsi_BETA-9.zip

Changes: (since BETA-8)
- New month .. new sources -> Nov 2017 security patches -> android-8.0.0_r28
- Launch QMUXD process as root user
- Enabled FunctionFS (USB)
- Build hidl health & thermal implementation
- Removed "earlysuspend" hack in system/core
- Added "signature spoofing" base patch (patch included; but not working yet)
- Created rild service in init.rc (deb only)
- Added HIDL radio implementation (deb only)
- Added gps.conf (deb only)

NFC: on/off toggle still buggy

Camera: We build HAL1 camera now .. like in Lineage too.
The AOSP camera app is NOT working.
Apps like the camera below are working fine ..
https://play.google.com/store/apps/details?id=com.peace.SilentCamera

RILD (deb only):
- Data connection (3G/LTE) seems still to have problems.
- No changes are done for RILD anymore .. same changes as in 8.3

New kernel -> 2017-11-06
- DT2W, Sweep2sleep, Sweep2wake: disabled per default
(Pls use EX-Manager, Kernel-Auditor or similar apps/tools to enable DT2W, Sweep2sleep and Sweep2wake)
- Security patch for "KRACK" attack
- Latest Lineage changes

Sources:
https://github.com/followmsi/manifests/tree/flo-deb-aosp-o
https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-oreo_2017-11-06

Enjoy

It's OK Followmsi, dirty flashed your ROM.
I've installed your photo app, it works too.
Actually, I download and install EX-Manager to test the DT2W fonction.

Thank you.

---------- Post added at 23:06 ---------- Previous post was at 22:51 ----------

It's OK Followmsi, dirty flashed your ROM.
I've installed your photo app, it works too.
Actually, I download and install EX-Manager to test the DT2W fonction.

Thank you.

Could you, please, gimme a link for a EX-Manager ?
Mine crash on my nexus

 

[SHABBYLEA]

Thanks msi. Your work is much appreciated...

Thanks again.

 

[lollyjay]

Thanks msi. Your work is much appreciated...

Thanks again.

Tru Dat!

 

[SHABBYLEA]

Tru Dat!

Indeed... ?

 

[jaucar]

Thanks for your work.
I have a problem with my device. the screen has ghost touches in a very small part down.
I can not swipe the TWRP button.
Would there be a way to install rom next to the kernel and super SU by ADB?

 

[followmsi]

Thanks for your work.
I have a problem with my device. the screen has ghost touches in a very small part down.
I can not swipe the TWRP button.
Would there be a way to install rom next to the kernel and super SU by ADB?

Yes .. either you sideload the ROM.
https://android.gadgethacks.com/how-to/sideload-flashable-zips-android-with-twrp-0176529/

Or if you have the ROM files on your device already use adb shell command ..
"adb shell twrp install /sdcard/file-name.zip"

Kernel.zip and supersu.zip should work too.

Good luck ..

 

[followmsi]

It's OK Followmsi, dirty flashed your ROM.
I've installed your photo app, it works too.
Actually, I download and install EX-Manager to test the DT2W fonction.

Thank you.

---------- Post added at 23:06 ---------- Previous post was at 22:51 ----------



Could you, please, gimme a link for a EX-Manager ?
Mine crash on my nexus

I am using kernel auditor actually ..

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en

 

[gege622]

I am using kernel auditor actually ..

https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en

Thanks a lot,

I've activated the DT2W, it works !

I'll follow the battery.

Thanks again