[ROM][S][mata] Unofficial, optimized LineageOS 19.1 - August 7th

[lasuazo]

Sounds like a good idea, I will add a link to the LineageOS wiki in the first post. Yes, it is suitable for installing this ROM as well.

@Tomoms quick question in regards to installing rom, what is the boot img used for? Pardon my noobness but when I installed it I used the lineage recovery image as the boot img you linked on the 1st post wasn't actually flashing, nor as recovery and in the end I flashed the rom, then kernel (your latest version), and gapps. All with lineage recovery posted in the lineage wiki.

 

[Tomoms]

@Tomoms quick question in regards to installing rom, what is the boot img used for? Pardon my noobness but when I installed it I used the lineage recovery image as the boot img you linked on the 1st post wasn't actually flashing, nor as recovery and in the end I flashed the rom, then kernel (your latest version), and gapps. All with lineage recovery posted in the lineage wiki.

Are you sure you were flashing my bootimge into the correct slot? Anyway, the only purpose of my bootimage is to allow for signature checking. My boot image is signed with my private key, thus when you flash my ROM (which is of course signed with the same key), this security check passes. Using Lineage's official boot image to flash my ROM is perfectly fine, but you must have seen an error saying that signature verification had failed (to which you must have reacted by selecting "Yes", in order for the flashing process to proceed anyway). Another difference is that in my recovery, the touchscreen works, while in Lineage's, it does not, but it will in just a few days/weeks probably, as my patches for in-recovery touch support are being implemented right now.

 

[lasuazo]

Are you sure you were flashing my bootimge into the correct slot? Anyway, the only purpose of my bootimage is to allow for signature checking. My boot image is signed with my private key, thus when you flash my ROM (which is of course signed with the same key), this security check passes. Using Lineage's official boot image to flash my ROM is perfectly fine, but you must have seen an error saying that signature verification had failed (to which you must have reacted by selecting "Yes", in order for the flashing process to proceed anyway). Another difference is that in my recovery, the touchscreen works, while in Lineage's, it does not, but it will in just a few days/weeks probably, as my patches for in-recovery touch support are being implemented right now.

That's precisely what I did. Flashed the rom without any issues except that warning, weird though the recovery did react to touches not sure what sorcery was that, but doing so, hence the question, will this affect anything? As far as I've been doing things everything is working fine on my end so not sure how could that mess something up. Except for one thing Ota updater "please check your connection and try again". Everything else is good so far

 

[Tomoms]

That's precisely what I did. Flashed the rom without any issues except that warning, weird though the recovery did react to touches not sure what sorcery was that, but doing so, hence the question, will this affect anything? As far as I've been doing things everything is working fine on my end so not sure how could that mess something up. Except for one thing Ota updater "please check your connection and try again". Everything else is good so far

If touch worked then it was my recovery, and not the official. 100% can't be otherwise. In this case, you must have seen the signature verification error only when flashing Gapps, and not when flashing the ROM.
EDIT: in either case, it does not matter if you used my recovery or Lineage's. Nothing can be affected. Don't worry.
To everybody: the OTA updater error reported by @lasuazo means that a change in my implementation of OTA updates has messed up stuff. I will fix it in the next build, but I am very much afraid that the next build will have to be flashed manually. Sorry for the inconvenience...

 

[lasuazo]

If touch worked then it was my recovery, and not the official. 100% can't be otherwise. In this case, you must have seen the signature verification error only when flashing Gapps, and not when flashing the ROM.
EDIT: in either case, it does not matter if you used my recovery or Lineage's. Nothing can be affected. Don't worry.
To everybody: the OTA updater error reported by @lasuazo means that a change in my implementation of OTA updates has messed up stuff. I will fix it in the next build, but I am very much afraid that the next build will have to be flashed manually. Sorry for the inconvenience...

If this is the case, when you release next build please let us know if clean flash is necessary or just apply update from adb, would be really appreciated. Thanks again for your efforts Tom, provide a link to buy you a coffee. Cheers mate.

 

[Tomoms]

If this is the case, when you release next build please let us know if clean flash is necessary or just apply update from adb, would be really appreciated. Thanks again for your efforts Tom, provide a link to buy you a coffee. Cheers mate.

A clean flash is never needed, unless in very exceptional cases which I try to avoid. You'll simply have to 'adb sideload' the new update

 

[Tomoms]

Wonder if you could look into the minimum screen brightness not being low enough ? This is the main issue for me on Lineage

Hello, I'm quoting you even if it seems you are not active on XDA anymore. The next build will fix the minimum brightness issue. The minimum allowed brightness will be as low as it is on the stock Q ROM.

 

[CamoGeko]

Thank you for providing a stable ROM for this ageing device!

If anyone is interested, I NEED a Google sync so I used MindTheGapps package and sideloaded it after the ROM.

You can find it here:

MindTheGapps-12.0.0-arm64-20220217_095343.zip | by Alessandro Astone for Generic Device/Other

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

 

[Tomoms]

Thank you for providing a stable ROM for this ageing device!

If anyone is interested, I NEED a Google sync so I used MindTheGapps package and sideloaded it after the ROM.

You can find it here:

MindTheGapps-12.0.0-arm64-20220217_095343.zip | by Alessandro Astone for Generic Device/Other

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

Why on earth did you install MindTheGapps 12 on top of an Android 11 ROM?

 

[CamoGeko]

Why on earth did you install MindTheGapps 12 on top of an Android 11 ROM?

Because you're using SDK31 to build it, and that wouldn't allow the install of Android 11 Gapps. I would show you the error but I didn't bother taking a picture of it.

 

[MuddyDog]

Because you're using SDK31 to build it, and that wouldn't allow the install of Android 11 Gapps. I would show you the error but I didn't bother taking a picture of it.

Nope...

MindTheGapps-11.0.0-arm64-20220217_100228.zip​

works correctly with
Official Lineage 18.1
and
Unofficial, Optimized LineageOS 18.1, including the newest build lineage-18.1-20220408

I'm currently using the 20220408 build...

 

[CamoGeko]

Nope...

MindTheGapps-11.0.0-arm64-20220217_100228.zip​

works correctly with
Official Lineage 18.1
and
Unofficial, Optimized LineageOS 18.1, including the newest build lineage-18.1-20220408

I'm currently using the 20220408 build...

Well, maybe it works for you... But for me it wouldn't flash. While the Android 12 Gapps flashed fine. Not sure how you would explain that but yeah.

 

[Tomoms]

Because you're using SDK31 to build it, and that wouldn't allow the install of Android 11 Gapps. I would show you the error but I didn't bother taking a picture of it.

I'm not sure what you mean with "you're using SDK31 to build it".
Anyway, there is absolutely no way an Android 12 Gapps package could flash itself, let alone work, on an Android 11 ROM.
Actually, an error about mismatching SDK versions (31 vs 30) is exactly what you see if you try to flash the Gapps package you linked onto my ROM.
The only explanation that comes to my mind is that when you thought you were flashing MindTheGapps 11, you were actually flashing MTG 12, and vice versa.

 

[Tomoms]

Hey guys, just wanted to drop a line to say that April's build is definitely coming. Sorry for the delay, April's security patches have been out for one week now, but until the end of summer I won't always be able to deliver updates regularly. There are already two April builds in my SourceForge folder, but they miss one or two things I want to implement in my final April build, so I haven't pushed them via OTA. The final build should be ready in a couple of days

 

[temporarium]

Hey guys, just wanted to drop a line to say that April's build is definitely coming. Sorry for the delay, April's security patches have been out for one week now, but until the end of summer I won't always be able to deliver updates regularly. There are already two April builds in my SourceForge folder, but they miss one or two things I want to implement in my final April build, so I haven't pushed them via OTA. The final build should be ready in a couple of days

No pressure. Thanks for the dedication

 

[Tomoms]

Hello! I released a new build yesterday. I've updated the first post with the changelog. Enjoy

EDIT: I haven't uploaded the corresponding bootimage. You can use the previous release's bootimage if you're installing this ROM for the first time and you need a recovery.

 

[temporarium]

Hello! I released a new build yesterday. I've updated the first post with the changelog. Enjoy

EDIT: I haven't uploaded the corresponding bootimage. You can use the previous release's bootimage if you're installing this ROM for the first time and you need a recovery.

Thought: add the device name/code to the thread name for easier searching - here and on the web: more people will find your work

 

[Tomoms]

Thought: add the device name/code to the thread name for easier searching - here and on the web: more people will find your work

Makes sense. Done

 

[temporarium]

Dirty-flashed latest with no issues. Just had to reflash Magisk. All good

Any thoughts of A12?

 

[Tomoms]

Dirty-flashed latest with no issues. Just had to reflash Magisk. All good

Any thoughts of A12?

Our LineageOS maintainers are working on 19.1 for mata. As soon as the work will be done, I'll start building it. I'd rather delay it a little and be sure to end up having a stable & working ROM, than build it now, risking to get an unfinished product, especially in this period where I need my phone to work as reliably as possible.