[ROM][T][mata] Unofficial, optimized LineageOS 20 - May 5th

Search This thread
By:
Advanced…
Tomoms

Tomoms

Senior Member
Feb 15, 2014
2,844
6,758
OnePlus One
Essential Phone
morphius88 said:
@Tomoms

For some reason after flashing the 3/11 build, there is an update available for the same build. Same size too. Updating doesnt change anything. It goes through the whole process but the build stays the same and the same update is available again. The updater is showing 2/17 as the current build. Weird.

Screenshots attached.
Click to expand...
Click to collapse
Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.
I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.

LineArc said:
Has anyone tried the dual speaker mod on lineage 20? Need to know before going forward with it.
Click to expand...
Click to collapse
Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.
 
L

LineArc

Senior Member
Apr 26, 2013
361
41
Sharp Aquos R6
Tomoms said:
Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.
I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.


Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.
Click to expand...
Click to collapse
Thank you, I am very much interested. Can't try coz I am using my essential as my main phone.
 
M

morphius88

Senior Member
Dec 12, 2010
293
95
OnePlus 8T
Sony Xperia 1 III
Tomoms said:
Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.
I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.


Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.
Click to expand...
Click to collapse
I dont really care either as long am I am on the latest build. I will try the dual speaker mod shortly as I am interested in that as well.
 
Tomoms

Tomoms

Senior Member
Feb 15, 2014
2,844
6,758
OnePlus One
Essential Phone
Hi,
a new build is available, now LineageOS has integrated the latest Android T QPR2, which also brings March's security patches.
Unfortunately a new visual bug has appeared, and I have no idea why: there is no black/gray background in the pull-down notification menu (below the quick settings tiles). The background is transparent, and as a consequence the notifications are superimposed on the currently active app. It doesn't affect functionality but is quite ugly to see. I apologize for the annoyance, I'm trying to address this as quickly as possible.

@morphius88 I suggest that you don't flash the stereo speaker mod at the moment. I've checked it out and it could potentially introduce audio-related issues in your phone, as the modifications it introduces are not tailored to the PH-1. I will write a better version of the mod in a couple of days, and post it here.
 
  • Like
Reactions: MarSOnEarth, temporarium and MuddyDog
M

morphius88

Senior Member
Dec 12, 2010
293
95
OnePlus 8T
Sony Xperia 1 III
Tomoms said:
Hi,
a new build is available, now LineageOS has integrated the latest Android T QPR2, which also brings March's security patches.
Unfortunately a new visual bug has appeared, and I have no idea why: there is no black/gray background in the pull-down notification menu (below the quick settings tiles). The background is transparent, and as a consequence the notifications are superimposed on the currently active app. It doesn't affect functionality but is quite ugly to see. I apologize for the annoyance, I'm trying to address this as quickly as possible.

@morphius88 I suggest that you don't flash the stereo speaker mod at the moment. I've checked it out and it could potentially introduce audio-related issues in your phone, as the modifications it introduces are not tailored to the PH-1. I will write a better version of the mod in a couple of days, and post it here.
Click to expand...
Click to collapse
Sounds good. I will be on the lookout for that. I think I will also hold off on the new build for now or maybe I can try to fix the background issue by messing around with something like Project Themer.
 
temporarium

temporarium

Senior Member
May 16, 2012
1,186
664
Samsung Galaxy Note GT-N7000
Nexus 7 (2013)
Tomoms said:
Hi,
a new build is available, now LineageOS has integrated the latest Android T QPR2, which also brings March's security patches.
Unfortunately a new visual bug has appeared, and I have no idea why: there is no black/gray background in the pull-down notification menu (below the quick settings tiles). The background is transparent, and as a consequence the notifications are superimposed on the currently active app. It doesn't affect functionality but is quite ugly to see. I apologize for the annoyance, I'm trying to address this as quickly as possible.

@morphius88 I suggest that you don't flash the stereo speaker mod at the moment. I've checked it out and it could potentially introduce audio-related issues in your phone, as the modifications it introduces are not tailored to the PH-1. I will write a better version of the mod in a couple of days, and post it here.
Click to expand...
Click to collapse
Thank you for your continued work on this device, and for the heads-up on potential issues. I'll also hold off till this is resolved. 🙂👍🏻
 
Tomoms

Tomoms

Senior Member
Feb 15, 2014
2,844
6,758
OnePlus One
Essential Phone
morphius88 said:
Sounds good. I will be on the lookout for that. I think I will also hold off on the new build for now or maybe I can try to fix the background issue by messing around with something like Project Themer.
Click to expand...
Click to collapse
temporarium said:
Thank you for your continued work on this device, and for the heads-up on potential issues. I'll also hold off till this is resolved. 🙂👍🏻
Click to expand...
Click to collapse
Well, you guys need not wait any longer. I've released another build which addresses that issue :)
 
  • Like
Reactions: mateusxd, temporarium and MuddyDog
D

danz852

Member
Jan 24, 2021
23
7
Hi, thanks for the rom. I have problem when using WhatsApp video call. I can hear the voice of ppl on the opposite but they can't hear my voice. I need to end the video call and restart the call to make it work.

And one more thing related to WhatsApp. When using WhatsApp's Fingerprint Lock, sometimes it work the other times it's not working.

Does anyone have the same problems with voice on WhatsApp video call and WhatsApp's Fingerprint Lock?
 
Tomoms

Tomoms

Senior Member
Feb 15, 2014
2,844
6,758
OnePlus One
Essential Phone
danz852 said:
Hi, thanks for the rom. I have problem when using WhatsApp video call. I can hear the voice of ppl on the opposite but they can't hear my voice. I need to end the video call and restart the call to make it work.

And one more thing related to WhatsApp. When using WhatsApp's Fingerprint Lock, sometimes it work the other times it's not working.

Does anyone have the same problems with voice on WhatsApp video call and WhatsApp's Fingerprint Lock?
Click to expand...
Click to collapse
While I was sure I had addressed all audio issues in the past, a few users (such as you) are still facing some. I'll check and see what I can do. If you could provide me with a logcat taken after a WhatsApp video call, it'd be great.
It seems weird to me that WA's fingerprint lock works only sometimes. I've never used this feature, but I'll enable it now to test it.
 
  • Like
Reactions: danz852
D

danz852

Member
Jan 24, 2021
23
7
Tomoms said:
While I was sure I had addressed all audio issues in the past, a few users (such as you) are still facing some. I'll check and see what I can do. If you could provide me with a logcat taken after a WhatsApp video call, it'd be great.
It seems weird to me that WA's fingerprint lock works only sometimes. I've never used this feature, but I'll enable it now to test it.
Click to expand...
Click to collapse
Thanks for the reply.
At the moment, I think WA video call audio issue gone after I restart the phone several times. I hope it stay that way.

WA's fingerprint lock still randomly working. Not a big deal as I can still use Lineage Hidden & Protected app.
 
MuddyDog

MuddyDog

Senior Member
Sep 3, 2019
69
40
hi, as @Tomoms said, a dirty upgrade from his 19.1 to his very early 20 build worked smoothly.

but... i'm not reckless enough to have done that without a complete backup on hand. i don't recall whether i used Google Backup or Swift Backup.

also, @Tomoms current build has merged QPR2 and the Updater installs this build correctly. But, both @Tomoms and i found that going back to a previous build to do some checks (pre-QPR2 to QPR2) resulted in a lot of breakage. i think @Tomoms rolled back, while i just switched slots and rebooted.

so, @Tomoms newest build is really great, the Updater works fine, and i can't think of a reason to downgrade back to 19.1.
but be advised that going back to an earlier build will require a clean reinstall... and keep a healthy backup handy.
 
Last edited:
  • Like
Reactions: temporarium
temporarium

temporarium

Senior Member
May 16, 2012
1,186
664
Samsung Galaxy Note GT-N7000
Nexus 7 (2013)
MuddyDog said:
hi, as @Tomoms said, a dirty upgrade from his 19.1 to his very early 20 build worked smoothly.

but... i'm not reckless enough to have done that without a complete backup on hand. i don't recall whether i used Google Backup or Swift Backup.

also, @Tomoms current build has merged QPR2 and the Updater installs this build correctly. But, both @Tomoms and i found that going back to a previous build to do some checks (pre-QPR2 to QPR2) resulted in a lot of breakage. i think @Tomoms rolled back, while i just switched slots and rebooted.

so, @Tomoms newest build is really great, the Updater works fine, and i can't think of a reason to downgrade back to 19.1.
but be advised that going back to an earlier build will require a clean reinstall... and keep a healthy backup handy.
Click to expand...
Click to collapse
Thanks for the feedback. Yes, backups without question. Just want to save time by not having to reconfigure everything again.
 
Tomoms

Tomoms

Senior Member
Feb 15, 2014
2,844
6,758
OnePlus One
Essential Phone
temporarium said:
Thanks for the feedback. Yes, backups without question. Just want to save time by not having to reconfigure everything again.
Click to expand...
Click to collapse
Yes, I have faced strange problems when rolling back after the QPR2 merge.
Sometimes I also faced visual glitches after normal 20->20 updates, but this only happened on some private testing builds I keep for myself. Builds released on xda are always free from these issues.
So in the end, I'd say you have a 95% probability of success. This is not official LineageOS, I don't want nor can give absolute guarantees of any kind, this is why I'm saying 95% and not 100%.
 
  • Like
Reactions: temporarium
temporarium

temporarium

Senior Member
May 16, 2012
1,186
664
Samsung Galaxy Note GT-N7000
Nexus 7 (2013)
Tomoms said:
Yes, I have faced strange problems when rolling back after the QPR2 merge.
Sometimes I also faced visual glitches after normal 20->20 updates, but this only happened on some private testing builds I keep for myself. Builds released on xda are always free from these issues.
So in the end, I'd say you have a 95% probability of success. This is not official LineageOS, I don't want nor can give absolute guarantees of any kind, this is why I'm saying 95% and not 100%.
Click to expand...
Click to collapse
Well, the dirty upgrade went smoothly - all seems to work... EXCEPT: no DNS resolution! As a result, no network at all! This is with the latest stable (March 21), though I also tried latest beta (March 26) with same results...

Mobile works, and Wifi connects and shows strong signal. I can ping my router by IP, but can't ping any hostname. I've tried different options under Private DNS (including Off and Automatic, of course). I've restarted numerous times. I've cleare the cache. I've uninstalled and reinstalled Adguard (which updates the filters correctly - must be by direct IP).

Any thoughts/suggestions?
 
I

izombiev

Member
Jan 6, 2017
23
2
Tomoms said:
While I was sure I had addressed all audio issues in the past, a few users (such as you) are still facing some. I'll check and see what I can do. If you could provide me with a logcat taken after a WhatsApp video call, it'd be great.
It seems weird to me that WA's fingerprint lock works only sometimes. I've never used this feature, but I'll enable it now to test it.
Click to expand...
Click to collapse
I would say that every single custom rom for this phone has suffered from this. I used your version right after facing such bugs on another LOS maintainer, but your visual bugs drove me nuts (no offense).
Yeah, such bug seems to disappear right after a reboot but it's just a matter of time before you're again at it.
Regarding this, I've been using LOS 19.1 for as long as a week and I can guarantee that this does not exist here.
Restarting the phone every time this happens is not a big deal, but it does happen like 10 min. after the phone boots up xD
 
Tomoms

Tomoms

Senior Member
Feb 15, 2014
2,844
6,758
OnePlus One
Essential Phone
temporarium said:
Well, the dirty upgrade went smoothly - all seems to work... EXCEPT: no DNS resolution! As a result, no network at all! This is with the latest stable (March 21), though I also tried latest beta (March 26) with same results...

Mobile works, and Wifi connects and shows strong signal. I can ping my router by IP, but can't ping any hostname. I've tried different options under Private DNS (including Off and Automatic, of course). I've restarted numerous times. I've cleare the cache. I've uninstalled and reinstalled Adguard (which updates the filters correctly - must be by direct IP).

Any thoughts/suggestions?
Click to expand...
Click to collapse
Side note: don't flash the beta builds unless you're told so. They can be potentially dangerous. Though you've been lucky: it is not the case of the 03-26 one.
We can surely fix your problem.
Can you ping by IP a server outside your local network?
Please reboot the phone and grab a logcat after it has booted up.
izombiev said:
I would say that every single custom rom for this phone has suffered from this. I used your version right after facing such bugs on another LOS maintainer, but your visual bugs drove me nuts (no offense).
Yeah, such bug seems to disappear right after a reboot but it's just a matter of time before you're again at it.
Regarding this, I've been using LOS 19.1 for as long as a week and I can guarantee that this does not exist here.
Restarting the phone every time this happens is not a big deal, but it does happen like 10 min. after the phone boots up xD
Click to expand...
Click to collapse
What visual bugs are you talking about?
I'm waiting for the log :)
 
I

izombiev

Member
Jan 6, 2017
23
2
Tomoms said:
Side note: don't flash the beta builds unless you're told so. They can be potentially dangerous. Though you've been lucky: it is not the case of the 03-26 one.
We can surely fix your problem.
Can you ping by IP a server outside your local network?
Please reboot the phone and grab a logcat after it has booted up.

What visual bugs are you talking about?
I'm waiting for the log :)
Click to expand...
Click to collapse
I will install your rom once again, Sir, in order to get logs and get this bug (audio one) fixed once and for all. I was talking about the transparent notification panel and the one that made me wanna cry was lock screen messages, which, despite being fully charged/disconnected from the charger, the phone kept showing "unlock to use all functions"; "charged" messages.
 
You must log in or register to reply here.

Similar threads

invisiblek
[ROM][UNOFFICIAL] LineageOS 15.1 for the Essential PH-1 (mata)
Replies
2K
Views
263K
rophiroth
rophiroth
R
[ROM][10][UNOFFICIAL] LineageOS 17.1 for the Essential PH-1 (mata)
Replies
331
Views
47K
robsonline
robsonline
O
[ROM][10.0][MATA][OFFICIAL] Evolution X 4.3 [05/05/2020]
Replies
410
Views
47K
G
guliver365
6
[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps
Replies
1K
Views
241K
N
necross_o
return.of.octobot
[MATA] [CAF] [UNIFIED] [EAS] [4.4.166] [CLANG 8.0] Neutrino Kernel (hercules)
Replies
520
Views
55K
Bobbaloo
Bobbaloo

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 9
    Tomoms
    Tomoms
    Hi, a new build is available, with May's security patches and, *drumroll*... Fixes for all of Klik's issues! Everything is working now, including the 360 cam, and there are no more crashes when switching to B&W mode or to the front cam.
    View
    3
    Tomoms
    Tomoms
    This post is of interest for everybody.
    LineArc said:
    Is it only me or is it a rom error. I can't get audio in Whatsapp and messenger (the audio isn't recorded at all). Need solution please
    Click to expand...
    Click to collapse
    Sorry, this is my fault. I forgot to mention that in my latest build, I've modified the audio configuration of the device, to bring it closer to the stock ROM's. This is intended to fix the speakerphone issues some people were still facing, and it indeed fixes some speakerphone/video calling use cases, but unfortunately breaks mic input in some other scenarios. I've included these modifications because I estimated that the number of use cases they fix is greater than that of the use cases they break.
    You can easily revert the modifications by yourself. Just enable USB debugging and debugging with root access in the Developer options, then download & unpack this archive: https://mega.nz/file/AtMAFYJb#b_0ttoLO6h2ZyxiIsXA70AaD6LnP1Vs6dMyy9bIgjf0
    Then run the following commands:
    Bash: 
    adb root
adb remount
adb push mixer_paths_tasha.xml /vendor/etc/
adb shell sed -i "s/fluencetype=fluencepro/fluencetype=fluence/" /vendor/build.prop
    You'll want to copy-paste them and not type them by yourself, to avoid making mistakes.
    Mind that you do not need to be rooted, you just have to enable the "deugging with root access" option in the Developer options.
    Then reboot, and the audio situation should revert back to that of my previous build.
    I apologize again for the inconvenience! Eventually I'll find a final fix that addresses all issues at once...
    View
    3
    Tomoms
    Tomoms
    Just leaving a quick note to say that the 360 cam has been broken in the last few builds, but the next one, which will be released as soon as May's security patches are published, will finally fix not only this issue, but all the other issues of Klik's that were left to fix!
    View
    1
    Tomoms
    Tomoms
    jionny said:
    My apologies first. Might as well say I am new to this since I have not done anything to this phone since 2019. It is unlocked and rooted. How do I install this ROM? I didn't see the installation procedure. It was probably right in front of me but I did not see it. Can someone please point me in the right direction. Thank you
    Click to expand...
    Click to collapse
    Hi, my fault, I've never explicitly specified it in the first post of the thread: since my ROM is simply an unofficial flavour of LineageOS, Lineage's official installation instructions apply. https://wiki.lineageos.org/devices/mata/install
    Simply, you use my builds (available here) and my recovery image (available here, you can pick the most recent one, even though it doesn't match the date of the build you're flashing) instead of the official ones :)
    Everything else stays the same (including the recommended Gapps package)
    View
    1
    temporarium
    temporarium
    Tomoms said:
    Hi, my fault, I've never explicitly specified it in the first post of the thread: since my ROM is simply an unofficial flavour of LineageOS, Lineage's official installation instructions apply. https://wiki.lineageos.org/devices/mata/install
    Simply, you use my builds (available here) and my recovery image (available here, you can pick the most recent one, even though it doesn't match the date of the build you're flashing) instead of the official ones :)
    Everything else stays the same (including the recommended Gapps package)
    Click to expand...
    Click to collapse
    Since we're on the subject, I've been sideloading TWRP after every ROM flash so as not to lose the custom recovery (TWRP installs itself on both slots), then rebooting into TWRP (after selecting the other slot) to sideload Magisk. Did I explain myself? 😁

    With the lineage recovery, is all this still required? Is just sideloading the ROM enough? Need to sideload Magisk all the time as well? Need to change slots?
    View
  • 18
    Tomoms
    Tomoms
    In this thread I'll share with you my personal builds of LineageOS 20, 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 20 features:
    • support for MicroG (signature spoofing) - read the 2nd post!
    • support for Sandboxed Google Play (taken from GrapheneOS) - read the 2nd post!
    • Klik and Aperture are both preinstalled
    • built with global -O3 optimizations and ThinLTO
    • some debugging/tracing instructions have been removed from ART
    • loads of updates from AOSP master for ART
    • improved bionic routines + ARM optimized routines
    • in-built support for many DNS providers
    • support for 3-finger swipe to screenshot
    • PixelPropUtils, to unlock Pixel-only features in Google apps and pass SafetyNet
    • Mulch System Webview (from DivestOS) replaces the default Chromium WebView
    • "deGoogling" tweaks: GrapheneOS's captive portal URLs and SUPL server, Cloudflare's DNS nameservers, pool.ntp.org NTP servers are all used by default to replace their Google counterparts
    • updated 3rd-party libraries: SQLite
    • in-built F-Droid Privileged Extension
    • support for poweroff alarm

    KERNEL FEATURES
    • updates for zram/zsmalloc (and for the LZ4 compression backend too)
    • 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 in other scenarios
    • DriveDroid support (not tested)
    • Wireguard support (not tested)
    • lots of patches to improve memory allocation-related overhead
    • hardening against buffer overflows (thanks to the GrapheneOS team)
    • USB controller driver updated (MTP speed improvements)
    • memory routines optimized for the arm64 architecture
    • built with -O3 optimizations
    • binder driver 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 19.1 features:
    • support for MicroG (signature spoofing) - read the 2nd post!
    • built with global -O3 optimizations
    • 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
    • support for poweroff alarm
    • inbuilt F-Droid privileged extension
    • integrated Cloudflare and AdGuard (recommended) private DNS
    • PixelPropUtils, to unlock Pixel-only features in Google apps and pass SafetyNet
    • 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
    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/Nolen's builds as well (when officials are released):
    • NFC quirks (payments with Google Wallet are working, other usecases might or might not) - fixed in the 2023-03-11 build
    • Updater shows wrong percentage during OTA package installation - fixed in the 2023-04-11 build
    Specific of my builds:
    • Klik misbehaves when rotating the phone while viewing a previously taken picture (low severity bug); Klik sometimes quits when switching to front cam or B&W mode (high severity bug) - under investigation, read more about Klik's status here - updated 2023-04-12
    • the fullscreen dark background in the notification pull-down view is now transparent - notifications are displayed directly on top of the currently active application. This doesn't affect functionality but is indeed unpleasant to the eye fixed in the 2023-03-21 build

    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 - fixed in my 2022-11-16 build, soon in officials too
    • Klik often lags a lot - work in progress
    • bad sound quality in video recordings - fixed in my 2022-08-07 build and in officials too
    • wrong time on boot until you connect to a network - fixed in my 2022-12-24 build, hopefully 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 - fixed in 19.1
    • 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 20:
    May 5th:
    • synced with LineageOS (including May's security patches)
    • all of Klik's bugs are finally fixed! Hooray!
    • support for call recording
    • updates for some system components
    • misc. sepolicy fixes and other fixes for small issues under the hood
    • minor kernel bug fixes

    April 11th:
    • synced with LineageOS + April's security patches
    • fixed Klik's lags/freezes and the crashes after taking pictures
    • misc. updates and improvements for several system components
    • improved Monet color engine
    • fix for the Updater showing a wrong percentage during update installation
    • minor misc. visual updates (icons, animations, etc.)


    March 21st:
    • fix for the visual bug of the previous build

    March 20th:
    • synced with LineageOS (March's security patches + Android T QPR2)
    • kernel bug fixes and minor tweaks

    March 11th:
    • synced with LineageOS
    • built with -O3 and ink-time optimization
    • many updates for ART and bionic taken from AOSP master
    • more privacy! More links with Google were broken (SUPL & NTP servers)
    • GPS performance improvements
    • fixes for NFC
    • in-built support for many private DNS providers
    • many kernel bug fixes taken from the Civil Infrastructure Project's backports

    February 26th:
    • first public build
    • all the feaures listed above are present

    January 6th:
    • synced with LineageOS, including January's security patches
    • support for poweroff alarm
    • a few kernel tweaks to improve the responsiveness (taken from Zen kernel)
    December 24th:
    • system clock is correct on boot, even with no network connections
    • WiFi kernel drivers updated from the official Android 11 kernel for the Pixel 2
    • other minor fixes in the kernel

    December 8th:
    • synced with LineageOS, including December's security patches
    • kernel hardening against buffer errors
    • many vulnerabilities affecting several Qualcomm kernel drivers have been patched
    • minor optimization for jemalloc (Android's memory allocator)

    November 16th:
    • synced with LineageOS
    • HDR & Portrait modes in Essential's camera app now work
    • kernel: several fixes and updates
    • the kernel now is built using a full LLVM toolchain (even the integrated assembler)

    November 5th:
    • synced with LineageOS + November's security patches

    October 17th:
    • PixelPropUtils + patches from PixelExperience to unlock Pixel-only features in Gapps and pass SafetyNet
    • a few improvements and fixes in the kernel
    October 9th:
    • synced with LineageOS (+ October's patches)
    • fixed log spam related to VoLTE (thanks Ricky Cheung)
    • kernel: disabled debugfs (reduces debugging overhead for many drivers)
    • kernel: updates for ZRAM and the LZ4 compression driver
    • kernel: other minor tweaks and updates
    • kernel: security fixes (thanks to our maintainer Kevin)

    September 9th:
    • synced with LineageOS + September's patches
    • integrated Cloudflare and AdGuard private DNS
    • built with global -O3 optimizations

    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 20: starting from April 2023, my builds are hosted here on Github - older builds on SourceForge
    20 recovery images: SourceForge
    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, the GrapheneOS team, the YAAP team, the DivestOS team and the xda user MuddyDog. I hope I have not forgotten anyone.
    View
    9
    Tomoms
    Tomoms
    Hi, a new build is available, with May's security patches and, *drumroll*... Fixes for all of Klik's issues! Everything is working now, including the 360 cam, and there are no more crashes when switching to B&W mode or to the front cam.
    View
    8
    Tomoms
    Tomoms
    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 :)
    View
    7
    Tomoms
    Tomoms
    POST-INSTALLATION ADVICE

    RECLAIM SOME PRIVACY AND BLOCK LOTS OF ADS
    19.1 & 20: Open Settings > Neworks & Internet > Advanced > Private DNS and choose "AdGuard DNS"
    18.1: Manually set "dns.adguard.com" as the Private DNS.

    SETTING UP SANDBOXED GOOGLE PLAY
    Open the "Apps" app, tap on the three dots in the top right corner, tap on Show all packages, then choose Google Play Store, and then tap on the install button. This will install Google Play Services, Play Store, and Services Framework as normal, sanboxed user apps, while allowing for an almost complete compatibility with Google Play APIs.
    A few notifications will appear, shortly after, asking for some permissions. Just allow what they ask for.

    INSTALLING MICROG VIA MINMICROG
    Refined MinMicroG package prepared by me: click here
    System mode (mandatory for those who don't want Magisk): you must remember to mount /system in Lineage Recovery before attempting to flash MinMicroG.
    Systemless mode: just flash MinMicroG as though it was a Magisk module.

    SETTING UP MICROG
    If you have installed MinMicroG as a Magisk module, just open its Settings, and in the Self Check screen do what is required to enable all tickboxes.
    In the Location Modules list, enable all the modules you're interested in using (usually all of them), but be careful that enabling some of them will make a pop up window appear, asking if you want to allow constant access to the location to a given provider. Do not click on the pop up window's main button (which denies access), instead, click on the underlined text, which will take you to a Settings screen in which you can allow the module unconstrained access to the device's location.
    I also suggest disabling the "Apps" application, that is bundled in the system, as it will try (and fail) to replace MicroG with normal Google Play Services.

    If you have installed MinMicroG in system mode, open an ADB shell and run the npem command, then reboot. It should grant all the necessary permissions.

    SETTING UP VIPER4ANDROID

    GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.

    A refined ViPER4Android installer. Contribute...
    github.com github.com

    PASSING SAFETYNET
    You need to have MindTheGapps or microG installed in order to pass SafetyNet. If you choose microG, enable its SafetyNet toggle in its settings.
    That's enough, you should pass SafetyNet out of the box.

    The following steps are needed only if you decide to flash Magisk on your phone:
    1. In Magisk's settings, enable Zygisk
    2. Reboot
    3. In Magisk's settings, tap on Configure DenyList
    4. In the three-dot menu, tick Show system apps and Show OS apps
    5. Scroll down and look for Google Play Services.
    6. Tap on it (don't tap on its checkbox!), the list item will expand and show additional sub-items
    7. Tap on the Play Services' main checkbox: all of its sub-items should automatically become enabled
    8. Look for Google Services Framework and tap on its checkbox (there are no hidden sub-items here)
    9. Return to Magisk's settings and enable Enforce DenyList
    10. Reboot
    You should now pass SafetyNet!
    View
    7
    Tomoms
    Tomoms
    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.
    View

New posts