[ROM][S][mata] Unofficial, optimized LineageOS 19.1 - August 7th
- Thread starter Tomoms
- Start date
Factory-resetting implies formatting /data, which in turn implies wiping the internal storage. TWRP should be able to only wipe /data without wiping /data/media ( = internal storage), but I am unsure how that would work on a FBE-encrypted device like mata, as I have never tried it. Try it at your own risk. Also, you might experience signature-related problems if you jump from official Q to my builds without wiping /data. Again, you can try, but you're on your own. The proper way to do it is to completely format /data.
Thanks, @Tomoms and @temporarium, managed to install without a complete factory reset. The problem is google apps are not detecting the internet, the browser seems fine. Any idea how to fix? Or should I need to do a factory reset and install it again to make it work?
The only problem I have is that I cannot sync my contacts and other google settings. And there's also this weird space at the top of all settings pages unless I scroll up.
The only problem I have is that I cannot sync my contacts and other google settings. And there's also this weird space at the top of all settings pages unless I scroll up.
Last edited:
"Yes, yes, and definitively yes" to clean installs, especially when switching/trying new ROMs, and after that; what gets me going from where I left off is 'Swift Backup'. The only apps that need to have their data wiped after restore are those that use KeyStore, and that's just a couple in my case (out of ~90+).
HELP!
I'm pulling my hair right now...
My PH-1 has been having random hangs and reboots, nothing too significant and happens about twice daily. I chucked it to having a custom rom and looked past it.
Last week it had a reboot and my lock pin stopped working. I had to reboot into LineageOS recovery and factory reset. It just rebooted again (today) and pin refuses to unlock, again!
I have a lot of sensitive data I cannot afford to lose right now. I know it's possible to delete encryption pin from TWRP but I don't have that installed anymore, searched but can't find any steps to reinstall.
Will appreciate any help offered.
@Tomoms
I'm pulling my hair right now...
My PH-1 has been having random hangs and reboots, nothing too significant and happens about twice daily. I chucked it to having a custom rom and looked past it.
Last week it had a reboot and my lock pin stopped working. I had to reboot into LineageOS recovery and factory reset. It just rebooted again (today) and pin refuses to unlock, again!
I have a lot of sensitive data I cannot afford to lose right now. I know it's possible to delete encryption pin from TWRP but I don't have that installed anymore, searched but can't find any steps to reinstall.
Will appreciate any help offered.
@Tomoms
Sorry for not replying earlier. I totally missed the notification. This is extremely strange and I have no idea what could be done to fix this. Deleting the lockscreen PIN is done by removing some file in /data, but it would not solve the problem on modern devices, because all contents of /data are still encrypted, and they get decrypted only upon insertion of the correct PIN!
I also have these random hangs, and reboots, does anyone else have this? Could this be because of magisk ( I have 25.0)?
No, Magisk v25.0 works perfectly, and v25.1 should be fine too. Send me logs, please. /sys/fs/pstore/console-ramoops after a reboot should provide valuable insight.
@Tomoms
How about an updated TWRP? There is a working one available for my other device, and it has working data decryption under A11-12.1. Any chance you can work with that?
How about an updated TWRP? There is a working one available for my other device, and it has working data decryption under A11-12.1. Any chance you can work with that?
i'd love to tinker with my essential phone again, but i do need to replace the screen and i need to figure out how i can set up the stupid bootslot thing that keeps reverting every time i install gapps... ech. this rom does seem very promising already
Yes, that's been on my to-do list for a while. I know /data decryption has been fixed on A12 now (at least in some cases, need to figure out if mata's type of encryption is the one that's supported or not - I really hope it is), I promise I'll try to dedicate more time to it...
What? Slotted devices can be confusing at first, but they are really simple once you keep in mind these simple facts.
- In any given moment, only one slot is the active one. The other is the inactive one.
- Simple recoveries (such as Lineage recovery - do not use TWRP, it's old and broken, so let's not talk about it here) flash all zips onto the active slot, except for ROM builds. Thus...
- ...When you flash a ROM via its recovery (e.g. my builds via Lineage Recovery), it is installed in the inactive slot.
- The active slot has not changed yet. When flashing normal zips, the recovery will continue to operate on the same active slot. In order to change active slot after a ROM flash, you need to reboot to recovery (only then is the active slot switched).
So it happened again, but this time the phone went on a reboot loop. It loads the lock screen and keeps rebooting. After a few tries, I somehow managed to reboot to safe mode before it restarted again, but get this, my pin was not accepted, it kept saying the wrong pin haha. So I now wiped my phone again, will try a different ROM now. This was working perfectly for me until this happened, so strange, I hope it's isolated to my device for some weird reason, and I can't provide logs anyway as you can see!
Edit: I actually see that @jabia had the same problem, so maybe it's not isolated, I hope you can fix it
Last edited:
So it happened again, but this time the phone went on a reboot loop. It loads the lock screen and keeps rebooting. After a few tries, I somehow managed to reboot to safe mode before it restarted again, but get this, my pin was not accepted, it kept saying the wrong pin haha. So I now wiped my phone again, will try a different ROM now. This was working perfectly for me until this happened, so strange, I hope it's isolated to my device for some weird reason, and I can't provide logs anyway as you can see!
Edit: I actually see that @jabia had the same problem, so maybe it's not isolated, I hope you can fix it
I'm not a wizard. Without logs I cannot understand what goes wrong, let alone fix this issue.
Hello, a new build with lots of updates and optimizations is available. It includes code updates, tweaks and optimizations applied to the most critical system components (ART, libcore, internal frameworks, memory management routines); July's security patches; my kernel is now finally built-in, as in 18.1. Available via OTA right now
OK, finally had a chance to give this a bit more time. Tested GPS, Bluetooth, Wi-Fi, mobile. All working fine. ROM is stable and smooth. Keep up the fine work, bro! 
This is my first ROM with microg and it is superb, everything works as it should if you take the time to set it up.
Thank you very much for keeping this old device alive.
Cheers.
Thank you very much for keeping this old device alive.
Cheers.
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.
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.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5Hello, 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. -
14In 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
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 nightliesswiping up on the lockscreen is difficult (a very long swipe is required)- fixed/improved in my 2022-05-24 build, and in later official nighliesminimum 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
- 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 buildsdistorted 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
recovery "Back" button is difficult to press- workaround: press a little bit above it- fixed in the 2022-01-07 buildspeaker 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
- 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)
- 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
- synced with LineageOS
- touchscreen support in Lineage recovery
- kernel now supports Kcal and Klapse
- 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.7A 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.7New 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.6A 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.
