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

Search This thread

lasuazo

Senior Member
Aug 10, 2013
227
56
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

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
@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

Senior Member
Aug 10, 2013
227
56
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

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
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...
 
  • Like
Reactions: lasuazo

lasuazo

Senior Member
Aug 10, 2013
227
56
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

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
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

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone

CamoGeko

Retired Forum Moderator

Tomoms

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
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:
Why on earth did you install MindTheGapps 12 on top of an Android 11 ROM?
 

MuddyDog

Senior Member
Sep 3, 2019
59
28

CamoGeko

Retired Forum Moderator

Tomoms

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
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

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
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

Senior Member
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

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
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.
 
Last edited:

temporarium

Senior Member
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

Senior Member
Feb 15, 2014
2,697
6,452
OnePlus One
Essential Phone
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Hello, I've just realized July's build was never made available via OTA, sorry!
    Anyway, I've released a new build with lots of interesting stuff (mainly optimizations for bionic's routines). And it's of course available via OTA. Enjoy!

    EDIT: and very importantly, today's build contains a workaround for the long-standing issue of bad audio quality in video recordings :) I'm working to refine the workaround and turn it into a proper fix that can be pushed to official LineageOS as well.
  • 15
    In this thread I'll share with you my personal builds of LineageOS 19.1 and 18.1 for the Essential PH-1 (codename: mata). These builds are unofficial LineageOS builds, customized with my favorite tweaks and features, and with some interesting optimizations.

    MAIN FEATURES
    LineageOS 19.1 features:
    • support for MicroG (signature spoofing) - read the 2nd post!
    • some debugging/tracing instructions have been removed from ART
    • some UI changes from ProtonAOSP (ripple effect)
    • updates and compiler optimizations applied to critical system components (ART, memory management routines, mathematical routines)
    • bionic libc fixes and updates
    • updated 3rd-party libraries: SQLite, giflib, zlib
    • inbuilt F-Droid privileged extension
    • debugging/logging code removed from system components (system frameworks, init system) to reduce overhead
    • other minor tweaks to system frameworks and ART, to maximize performance
    KERNEL FEATURES
    • updates for zram/zsmalloc (+ zstd compression algorithm instead of lz4) reverted due to regressions
    • power-efficient workqueues are implemented in many drivers
    • simple_lmk by kerneltoast replaces standard LMK
    • Kcal & Klapse
    • maple I/O scheduler as default
    • DDR bandwidth boost when launching apps and other scenarios
    • DriveDroid support (not tested)
    • Wireguard support (not tested)
    • lots patches to improve memory allocation-related overhead
    • USB controller driver updated (MTP speed improvements)
    • memory routines optimized for the arm64 architecture
    • built with -O3 optimizations
    • binder backported from Linux 5.4
    • lots of drivers and components only useful for debugging are disabled
    • many small, miscellaneous patches to improve performance and power consumption
    LineageOS 18.1 features:
    • support for MicroG (signature spoofing) - read the 2nd post!
    • built with the latest Clang 12.0.x
    • updated & improved libraries: sqlite, zlib, libpng, jemalloc, libvpx, libyuv
    • critical system components built with -O3 optimizations (art, SurfaceFlinger, bionic)
    • arm64-optimized bionic routines
    • Android RunTime (ART) updates and improvements
    • several debugging & tracing components are removed from the system
    • partial/full screenshot QS tile
    • reduced priority of the USB connection type & USB debugging notifications
    • in-built F-Droid Privileged Extension
    • removed some links with Google: DNS nameservers & captive portal URL
    • support for OTA updates
    • signed with my own keys
    • other minor tweaks and improvements


    BUGS
    Common to official builds as well:
    • VPNs are not supported (can't configure a VPN in Settings) - fixed in my 2022-05-24 build, and in later official nightlies
    • swiping up on the lockscreen is difficult (a very long swipe is required) - fixed/improved in my 2022-05-24 build, and in later official nighlies
    • minimum brightness is too high compared to stock firmware - fixed in my 2022-06-09 build and later official builds
    • HDR+ and Portrait mode make Klik (Essential's camera app) crash
    • bad sound quality in video recordings - fixed in my 2022-08-07 build, soon in officials too
    Specific of my builds:
    • none, at the moment
    Common to official builds as well:
    • unaligned recovery logo + black bar at the right of the screen - fixed in my 2021-12-15 build and newer official builds
    • distorted in-call audio when VoLTE is enabled for T-Mobile users - fixed in my 2022-03-11 build and newer official builds
    • low microphone volume/distorted audio when recording videos
    • PPSSPP crashes on startup
    Specific of my builds:
    • recovery "Back" button is difficult to press - workaround: press a little bit above it - fixed in the 2022-01-07 build
    • speaker misbehaving when listening to voice messages in apps such as Telegram and WhatsApp - fixed in the 2022-02-21 build


    CHANGELOG for LineageOS 19.1:
    August 7th:
    • synced with LineageOS + August's security patches
    • "poor audio quality in video recording" bug has been fixed!
    • updates for ART
    • optimizations and improvements for bionic's memory routines
    • F-Droid privileged extension build in the system

    June 9th:
    • Rebased on the latest tag from Google (android_12.1.0_r7)
    • June's security patches
    • new ripple effect from ProtonAOSP
    • updated and optimized SQLite library
    • minimum screen brightness reduced
    • minor tweaks to system frameworks and ART

    May 24th:
    • initial build, 100% equal to LineageOS except for the following aspects
    • support for signature spoofing
    • some debugging removed from ART
    • device-specific bug fix: improved swipe-to-unlock experience (fix has landed in official repos)
    • device-specific bug fix: VPNs are supported (fix has landed in official repos)

    May 6th:
    • May's security patches
    • various kernel updates and fixes

    April 28th:
    • synced with LineageOS
    • updated SQLite to v3.37.2
    • kernel bug fix involving ZRAM
    • minor kernel tweaks and improvements

    April 13th:
    • synced with LineageOS, April's security patches
    • some minor tweaks and fixes in the Android frameworks
    • kernel: binder driver backported from Linux 5.4
    • kernel: simple_lmk replaces the standard LMK
    • kernel: updates for the random number generator driver
    • kernel: other minor fixes and improvements

    March 21st:
    • lots of updates and fixes for the platform code (picked from crDroid)
    • critical system components/libraries are built with ThinLTO and PGO
    • improved the energy efficiency of the WiFi chip
    • synced with LineageOS

    March 11th:
    • synced with LineageOS
    • March's security patches
    • fix for distorted in-call audio for T-Mobile users when VoLTE is enabled

    February 21st:
    • synced with LineageOS
    • a fix by the Lineage team for a telephony bug: more info here
    • a fix by me for a permission issue that caused the playback of voice messages in messaging apps not to switch properly between the main and the call speakers when the proximity sensor was covered/uncovered

    February 11th:
    • synced with LineageOS
    • kernel updated to Linux 4.4.302
    • minor bug fix in the system

    January 22nd:
    • synced with LineageOS
    • kernel updated to Linux 4.4.299
    • Google's DNS nameservers have been replaced with Cloudflare's (1.1.1.1, 1.0.0.1)
    • some security hardening patches taken from GrapheneOS

    January 7th:
    • kernel: Linux 4.4.297
    • kernel: removed debugging junk from the WiFi chip's driver
    • kernel: patches for the dwc3 driver (improve MTP transfer speeds)
    • tentative fix for the camcorder microphone issues
    • recovery touchscreen issues are fixed
    December 15th:
    • synced w/ LineageOS (incl. December's security patches)
    • kernel updated to Linux 4.4.294
    • lots of small kernel improvements and fixes
    • maple I/O scheduler is now the default
    • several user interface/user experience improvements (read here)
    • alignment of visual elements in recovery is fixed (now also in official LineageOS)
    November 5th:
    • synced with LineageOS
    • November's security patches
    • kernel: DriveDroid support
    • kernel: Wireguard support
    • kernel: DDR bandwidth boost on zygote fork
    • kernel: several other small updates and improvements
    October 23rd:
    • synced with LineageOS
    • touchscreen support in Lineage recovery
    • kernel now supports Kcal and Klapse
    October 7th:
    • initial build with all the above features
    • October's security patches are included

    DOWNLOADS
    LineageOS 19.1: SourceForge
    19.1 recovery images: SourceForge

    LineageOS 18.1: SourceForge
    18.1 recovery images: SourceForge


    SOURCES
    All my repos are on Github. In particular: device tree, kernel sources.


    A BIG "THANK YOU" TO
    the whole LineageOS team, and the multitude of great developers of the Android custom ROM scene, such as kdrag0n, kerneltoast (Sultanxda), arter97, nathanchance, neobuddy89, flar2, franciscofranco, frap129, the MSM-Xtended project, the crDroid project. I hope I have not forgotten anyone.
    8
    Hello, official LineageOS 19 nightlies will be available for mata in a couple of days circa. I'll start building my 19-based ROM in the next few weeks. Expect the first build to be available before the end of the month :)
    7
    A new build is available. It brings the latest updates from the Lineage code base and an updated kernel (4.4.302).
    I've also prepared a separate kernel that you can optionally flash on top of the new build: https://mega.nz/file/llFiBD7D#6Jsum5lcswtvgMaC6-6hLQYtvGuZLp7YPEybjoFbXT8
    This kernel features more twekas and performance optimizations, mainly related to the task scheduler and the memory management subsystem. All these changes will be included in the next build's kernel.
    7
    New build available! Featuring November's security patches plus several interesting kernel updates and improvements, such as DDR bandwidth boost on app startup (should improve app launching time a bit), memory allocation speed & overhead improvements, Wireguard support and DriveDroid support. I haven't tested Wiregaurd and DriveDroid, so try them if you can and let me know if they work.
    The speakerphone issue is still under investigation, I haven't had enough time to look at it lately.
    6
    A new build is available!
    It brings several updates to the Android frameworks and other internal components (libcore, art, bionic - mostly picked from crDroid), including advanced optimizations (ThinLTO, PGO) applied to some critical system libraries.
    There are also a few device-specific changes, notably some tweaks for the WiFi driver's configuration, which should improve the energy efficiency of the chip.