Development [ROM][OFFICIAL][sake][12.1] LineageOS 19

[Mario545]

It is, for official Lineage. MicroG does not ship firmware in their builds like officials do, so it makes sense why it would crashdump on updating to 19.1 since it did not update the firmware. If you want to use MicroG builds then you'll need to make sure you're on Android 12 firmware beforehand.

Oh, oh. Thanks for the info.
I think there is a reason why custom ROMs lost a bit of traction ins the last couple of years. Because no one makes good decisions anymore. The reason why we need Lineage for MicroG fork in the first place is because LineageOS made the wrong decision to not allow MicroG installation in their builds. And now MicroG made the wrong decision to not include the firmware...

 

[CircleCode]

It is, for official Lineage. MicroG does not ship firmware in their builds like officials do, so it makes sense why it would crashdump on updating to 19.1 since it did not update the firmware. If you want to use MicroG builds then you'll need to make sure you're on Android 12 firmware beforehand.

Thanks for the explanation, it makes sense, even if it is sad (not criticizing developers choices, I am really thankful for the hard work!)
Is there a known way to upgrade firmware from microg build without losing data?

 

[ZVNexus]

Thanks for the explanation, it makes sense, even if it is sad (not criticizing developers choices, I am really thankful for the hard work!)
Is there a known way to upgrade firmware from microg build without losing data?

Sideload 19.1 build, reboot to fastbootd to flash all firmware partitions to both slots, then reboot.

 

[Malko007]

Ok I flashed los19. It works but tried to flash los4microg after but got error. And could not apply update in recovery

 

[CircleCode]

Sideload 19.1 build, reboot to fastbootd to flash all firmware partitions to both slots, then reboot.

hum, it seems I am missing something…
I extracted the zip, and then the `payload.bin` file, expecting to find some xml about the different img to know what to flash for "all firmware partitions" (and the corresponding fastboot commands), but I only have a bunch of img files, and I have no idea which ones I should flash…
Is there any reference documentation where I could start?
Thanks for the help
---
edit: here is the list of files present in the lineageos zip and not present in the microg build… should I flash all of them?

$ comm -3 lineage-19.1-20220505-microG-sake/microg-files lineage-19.1-20220506-nightly-sake-signed/lineage-files
    abl.img
    aop.img
    bluetooth.img
    cpucp.img
    devcfg.img
    dsp.img
    featenabler.img
    hyp.img
    keymaster.img
    modem.img
    multiimgoem.img
    qupfw.img
    qweslicstore.img
    shrm.img
    tz.img
    uefisecapp.img
    xbl.img
    xbl_config.img

 

[ZVNexus]

hum, it seems I am missing something…
I extracted the zip, and then the `payload.bin` file, expecting to find some xml about the different img to know what to flash for "all firmware partitions" (and the corresponding fastboot commands), but I only have a bunch of img files, and I have no idea which ones I should flash…
Is there any reference documentation where I could start?
Thanks for the help
---
edit: here is the list of files present in the lineageos zip and not present in the microg build… should I flash all of them?

$ comm -3 lineage-19.1-20220505-microG-sake/microg-files lineage-19.1-20220506-nightly-sake-signed/lineage-files
    abl.img
    aop.img
    bluetooth.img
    cpucp.img
    devcfg.img
    dsp.img
    featenabler.img
    hyp.img
    keymaster.img
    modem.img
    multiimgoem.img
    qupfw.img
    qweslicstore.img
    shrm.img
    tz.img
    uefisecapp.img
    xbl.img
    xbl_config.img

Yes, flash all of those partitions to both slots.

 

[CircleCode]

Yes, flash all of those partitions to both slots.

Thanks, I'm leaving on vacation this evening and might not try this before I leave, but I'll keep you updated.
Again, thanks for the endless time you spend here helping us!

 

[Mario545]

and the corresponding fastboot commands

Given the information to "flash on both slots", I guess the commands will be like this:

fastboot flash <image_name>_a <image_name>.img
fastboot flash <image_name>_b <image_name>.img

for each of the images you listed.

This actually matches the available partitions on the device. You can find out the partitions with "adb shell ls -l /dev/block/by-name". And indeed, for each <image_name>, a corresponding _a and _b partition is available.

At least that's how I would interpret the available information. Taking aside the huge typing effort for in total 36 commands, looks like a much better option than to wipe everything and go though stock ROM. Thanks for working out this solution!

 

[noamazulay24]

TNKS!!
BUT, the instructions are way more complicated than other devices i know. i must flash this ROM in sideload mode? cant i just flash this ZIP from TWRP normal flashing?

 

[ZVNexus]

TNKS!!
BUT, the instructions are way more complicated than other devices i know. i must flash this ROM in sideload mode? cant i just flash this ZIP from TWRP normal flashing?

It's not really complicated, flash boot/vendor_boot (these are the recovery partitions), then sideload in recovery. It's the exact same as what you'd do in TWRP. I've never validated TWRP, if it works cool, it's just not supported.

 

[ZVNexus]

Given the information to "flash on both slots", I guess the commands will be like this:

fastboot flash <image_name>_a <image_name>.img
fastboot flash <image_name>_b <image_name>.img

for each of the images you listed.

This actually matches the available partitions on the device. You can find out the partitions with "adb shell ls -l /dev/block/by-name". And indeed, for each <image_name>, a corresponding _a and _b partition is available.

At least that's how I would interpret the available information. Taking aside the huge typing effort for in total 36 commands, looks like a much better option than to wipe everything and go though stock ROM. Thanks for working out this solution!

Yes, that would be a correct interpretation.

 

[CircleCode]

Given the information to "flash on both slots", I guess the commands will be like this:

fastboot flash <image_name>_a <image_name>.img
fastboot flash <image_name>_b <image_name>.img

for each of the images you listed.

This actually matches the available partitions on the device. You can find out the partitions with "adb shell ls -l /dev/block/by-name". And indeed, for each <image_name>, a corresponding _a and _b partition is available.

At least that's how I would interpret the available information. Taking aside the huge typing effort for in total 36 commands, looks like a much better option than to wipe everything and go though stock ROM. Thanks for working out this solution!

This solution worked flawlessly: I have upgraded from LOS4Microg 18.1 to LOS4Microg 19.1 without losing data using this solution.
Thanks guys for your help

 

[CircleCode]

This solution worked flawlessly: I have upgraded from LOS4Microg 18.1 to LOS4Microg 19.1 without losing data using this solution.
Thanks guys for your help

It's not as perfect as I thought at first: it seems I don't have location anymore... (I never get a fix)
Does anyone have an idea of what could be wrong?

 

[merautaluca14]

location green notification occasionally turn on and off even if location is turned off completely.

 

[jaalai]

location green notification occasionally turn on and off even if location is turned off completely.

yes same behaviour on the last build. PhoneServices using it, wasn't the case on previous builds.

 

[ibolito]

Hello, I went back to full stock for now because of the Phone services using location every seconds. It was so annoying bein spammed by the location access green dot on the top right corner. The phone was constantly warm and battery life was awful. I'll go back to Lineage once this bug is solved or when there's a stable release.

 

[ZVNexus]

Hello, I went back to full stock for now because of the Phone services using location every seconds. It was so annoying bein spammed by the location access green dot on the top right corner. The phone was constantly warm and battery life was awful. I'll go back to Lineage once this bug is solved or when there's a stable release.

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/331362

Comments on the change explain why it occurs, but it's fixed now for the next release.

 

[Yuri..]

Does LineageOS for Zenfone 8 carries over stock features regarding the options to limit battery charge? That's to slow battery degradation over time. I love custom roms but this is a nice feature stock has.

 

[Mario545]

Does LineageOS for Zenfone 8 carries over stock features regarding the options to limit battery charge? That's to slow battery degradation over time. I love custom roms but this is a nice feature stock has.

No, not if it is a custom ASUS feature. What is currently missing is: Battery Charge Limit and the option to activate DC dimming (mitigate flicker in low brightness). For both are workarounds available though, but they have their caveats. Battery Charge Limit can only be done with root and DC dimming requires to install an app that is no longer maintained (removed from Play Store), you can still get the APK somewhere on the internet. I too would love to have thouse features build-in in LineageOS, but doesn't look like this is going to happen soon.

See:
How To Guide Battery Charge Limit on custom ROM
Activate low brightness dimming in custom ROMs

Also the option to change refresh rate is missing, you need some adb commands for this: https://forum.xda-developers.com/t/rom-official-sake-11-lineageos-18-1.4325059/page-18#post-86784441

 

[ibolito]

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/331362

Comments on the change explain why it occurs, but it's fixed now for the next release.

Thanks so there's no overheating and battery drain anymore? I didn't get past 4h of SoT with the last build. I manage to get at least 5h30/6h with stock firmware.