yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I'll attach two screenshots. One is of what you mentioned. The other is when I click on the Android version 14 there, and then it shows Android 14 at the top, then lineageOS version within that. All of them seem to say the older version.

If the boot image is the only place this is coming from, then I understand why it's not working. It's possible that I have done this a little differently before. I mean, I may have installed the 21 boot image then over wrote it with the one from 20. This time I did not do that. I just left the existing boot image alone, and flashed system and vendor.

Is there something else I can check to see that I installed your changed system/vendor?

On a completely different note, I've had a problem forever with Microsoft SwiftKey Keyboard with this ROM. I do all this input by talking to the device by hitting the microphone. It doesn't work lots of the time. In fact, it was hard for me to get this written! I prefer this keyboard to others, but I haven't tried others in a long time, so I don't know if others have the same problem. I have not mentioned it before because I always can get it to work by hitting the microphone multiple times.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
You are not running my latest build. Perhaps you flashed the system and vendor images in the wrong slot, or booted the wrong slot?

The boot image has nothing to do with this.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I mentioned the boot image because we had to patch it in order to get the PIF stuff to work for 20 rom.

I'm still trying to figure out what is wrong. I definitely am flashing to slot A. That's the only slot where I ever flash a rom. I'll keep trying.

Does the Microsoft SwiftKey keyboard issue ring any bell with you? I have no idea if you or others are using that keyboard.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Well, I fixed it, but I don't understand. I've been using OrangeFox lately. But after using it multiple times to flash vendor and system, I just used fastboot instead. Now it's good. Weird!

EDIT: So sorry to waste your time. On the device, after unzipping the ROM zip, I use payload-dumper-go to get the images from payload.bin. But somehow, I used the older payload.bin instead of your new one. Sloppy.

At least it has nothing to do with OrangeFox, which seems to be working well with the 20 boot image.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Good to know that you've found out what was wrong. I can't help you with the SwiftKey issue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] barfood:
Thanks for your continued support of the Essential phone! Is there ever a need to update GAPPS? I did a clean flash in Jan 2024 with MindTheGapps-14.0.0-arm64-20231025_234300.zip and have done OTA update recently to your May 22 version. I'm wondering since I no longer pass Device Integrity and seem to remember it passing before. Just to be sure I reinstalled PIF_20240301.APK and rebooted but can only pass Basic Integrity.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Normally there is no need to update Gapps. I've uploaded a new Pif apk which will allow you to pass Play Integrity again: https://mega.nz/file/ZxUCgZAJ#lMoxMLdiK_2BbY5u3XcZe75_assjsSNAQoKuq6dlq6A
[Essential Phone ROMs, Kernels, Recoveries, & Other] DAE1964:
Great work. Been running for a week now and battery life is good with moderate usage.

Main use is UAPP for music. This is my backup device so phone and messaging not used.

Quick boot up and smooth scrolling with edge browser.

Thanks for keeping this great phone alive.
[Essential Phone ROMs, Kernels, Recoveries, & Other] mervinb:
Excellent work, keeping my 2 PH-1s so useful. Unfortunately some banking and ID apps don't like Lineageos, even non-rooted, otherwise one of the PH-1s would be a viable daily phone. Thank you!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
You might be interested in this trick: https://xdaforums.com/t/rom-r-unofficial-optimized-lineageos-18-1-january-13th.3693223/post-86340279
[Essential Phone ROMs, Kernels, Recoveries, & Other] johnjeandoe:
This ROM has to be the best one I've used for this phone so far.

Wondering for a few things:

Any plans for Android 12 when Lineage 19 comes out?

Adding support for stereo speakers seen in: https://xdaforums.com/t/magisk-mod-6-11-v1-stereo-speaker-mod-for-essential-phone.3863403/

Updating Adreno 540 GPU drivers for games (Genshin stutters occasionally / AetherSX2 crashes if Vulcan is selected)

Supporting more accent colors in the settings under Display>Styles & Wallpapers

A little nit picky- Other than that, really appreciate your work on the Essential as well as the Oneplus ROMS!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Android 12: sure

Stereo speakers: interesting, will look into it.

Adreno updates: are you actually sure there are updates for our Adreno 540 GPU? Have you seen them on other devices, or are you just saying "games lag, please do something"?

More colors: not gonna happen.
[Essential Phone ROMs, Kernels, Recoveries, & Other] johnjeandoe:
Regarding the GPU, theres a magisk module that supplies them: https://xdaforums.com/t/driver-9-0-adreno-500-series-opengl-vulkan-drivers-v-474-0-1-1-128.4042619/

I've installed the v2.5 package and received a sizeable FPS increase in some cases, was wondering if they could become integrated with the ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Interesting. Let me look into it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] danz852:
Hi, thanks for this ROM, I like it.

At the moment I only found a very minor issue. I already installed the update but after installation i cannot delete the update package.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Diresh:
Could you maybe also have a look at this game ?

GRID™ Autosport Custom Edition - Apps on Google Play

High-octane racing, your way.

play.google.com

It works fine on the stock rom but seems to crash while loading in this rom. ( I can also send some logs if you'd like)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It also happens on my phone every now and then. Don't know what to do about it... The updater app is about to be cleaned up and reordered a bit by the Lineage team, maybe they will get rid of this issue as well.

Yes, please, send me a logcat.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Diresh:
Here is a logcat for the grid autosport crash
[Essential Phone ROMs, Kernels, Recoveries, & Other] danz852:
I also found System UI randomly freeze and then crashing. Restart the phone will fix this, but not sure if this method will fix it permanently.

Anyway... I will keep using this rom and hoping to see it running Android 12 in the future.

Once again i would like to thank you for your work and keeping this phone alive.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Seems to be an uncommon crash that is not really related to the OS, but happens randomly on certain devices and certain Android releases. No one on Stackoverflow/Github has a clear idea about why it happens and a number of possible causes exist. This is hardly something I can fix in the OS. However, it would be interesting to know whether it happens on other Android 11 devices, or other LineageOS devices and versions.

Something in your setup must be causing that. I've never had a SystemUI freeze nor crash, not even once.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Diresh:
Thanks for taking a look at the problem. (On other android 11 roms like pa, carbon, statix and also some gsi's (like phh_aosp, lineage 18.1) the game works fine). It seems like it happens mostly with roms that are similar to lineage (like mokee, havoc)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Interesting. If you have the chance to test it on any other LineageOS-powered device, please do. I have a couple of old devices, will try it on them soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] madwyn:
Thanks for your effort.

My PH-1 runs smoothly with your release. I don't use banking stuff on it, this phone as a crack app test bed is perfect.
[Essential Phone ROMs, Kernels, Recoveries, & Other] johnjeandoe:
I can also confirm, apps like geforce now, aetherSX2, ppsspp have graphical issues or just flatout crash. These issues never happened on the official lineage for mata. Currently the only fix for me is just sideloading older version APK's where the targeted android version is not android 11.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Let me look into these issues. So are you 100% sure that all of those apps run fine on official LineageOS 18.1 on mata? Are you available for a few tests?
[Essential Phone ROMs, Kernels, Recoveries, & Other] madwyn:
I dirty flashed "lineage-18.1-20220207-nightly-mata-signed.zip", PPSSPP doesn't work neither, it quits immediately.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Mario3DS:
GeForce now and aethersx2 work fine for me, yes they're fully updated
[Essential Phone ROMs, Kernels, Recoveries, & Other] barfood:
Thanks! That took care of it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] malerocks:
Will this only work on your ROM or can I use it on the official Lineageos one as well?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It only works on my ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Zargone:
In preparation for reflashing this great OS, I tried to restore the phone back to stock to a very early image using one of files from mata. At the moment it seems to be a brick. This is how far the batch file went before hanging:

fastboot flash system_a system

target reported max download size of 536870912 bytes

Invalid sparse file format at header magi

erasing 'system_a'...

OKAY [ 0.625s]

sending sparse 'system_a' 1/4 (524284 KB)...

OKAY [ 2.282s]

writing 'system_a' 1/4...

OKAY [ 16.078s]

sending sparse 'system_a' 2/4 (523781 KB)...

OKAY [ 2.157s]

writing 'system_a' 2/4...

OKAY [ 20.769s]

sending sparse 'system_a' 3/4 (524286 KB)...

OKAY [ 2.235s]

writing 'system_a' 3/4...

OKAY [ 20.282s]

sending sparse 'system_a' 4/4 (267630 KB)...

OKAY [ 1.126s]

writing 'system_a' 4/4...

^CTerminate batch job (Y/N)? y

The phone seems totally dead as a brick.

I have tried the following:

Vol Up + Power, Vol Dn + Power, Vol Up + Vol Dn + Power each for 30 seconds. Somewhere on the Internet was the suggestion to hold the power button and plug in the charger ... I tried that for 30 seconds also. Now, if it is caught in a loop I suppose I can wait a week for the battery to be dead and see if it will charge and boot to the bootloader.

Any other suggestions? Thank you
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I have a very fluky PH-1 that has had problems since I bought it off eBay 5 years ago. But somehow, I've always been able to get it back.

That last 4/4 step for system always takes very long for me. So maybe you should not have terminated it. It's smaller than the other 3 pieces, so I don't know why it takes so long, maybe 5 minutes? I don't know exactly how long. But you probably should have waited longer.

As strange as it seems, after getting into a bad state, I've sometimes left it alone for days (maybe battery was still alive), then it would boot to bootloader with Vol Dn + Power. Or maybe just Power alone. I also may have plugged it into a laptop when trying those buttons. So even though system (and maybe recovery) may be screwed up, I would think you could still get the bootloader up. So I would suggest not giving up! I have read very old posts where people had strange issues like ours and finally got it up.

One fairly common situation for me was getting fastboot errors after booting to bootloader. Many times, just hitting the button to reboot bootloader would work, but usually that would take a minimum of 2-3 attempts.

Good luck!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I'm not sure how to recover your phone, but you're complicating a simple process for no reason. Installing my ROM does not require flashing any firmware. Just follow the instructions on the official LineageOS wiki: https://wiki.lineageos.org/devices/mata/install/
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, a new build is available, based on Android 14 QPR3 (with June's security patches) and bringing several improvements and fixes for the kernel.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
@Tomoms, you may remember that I use the 20 boot image with your 21 ROM. That's because I want to use TWRP (or OFox) recovery, and injection into the 21 boot image causes it not to boot to system. (You said this problem was introduced with Android 14 changes).

You mentioned improvements and fixes for the kernel in your latest release. I'm wondering whether those changes might be important for me to have. If so, I wonder how I could get them. You can tell me which of these choices, if any, make sense.

1. I can just ignore your improvements and continue to use the 20 boot/kernel (with your flashable zip for PIF string change and exFAT support).

2. I could unpack/repack the 20 boot image and replace the 20 kernel with your new 21 one. I have no idea if this would work.

3. You could create another flashable zip for the 20 kernel that includes your new changes, along with the prior ones in your last flashable zip.

4. This one is probably silly to mention. Fix TWRP or OFox to work with Android 14. I know you tried, changing OFox for me, but it didn't work. (I found that guy's email and wrote him. He answered and said he was at school and not working on that lately).

Please let me know what you think. If none of your changes are "important", I'll just go with 1. Or at some point, I'll give up on a recovery with backup/restore capability. But I sure don't want to do that!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Option 3 is the way. I might be able to send you a new flashable kernel in a few hours.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Oh my, I'd really appreciate it! You are aways so responsive and helpful. If it's easy enough, can you tell me what some of these improvements are? Or maybe you've listed them already, and I should go find that.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Let me know if it works: https://mega.nz/file/Y5VGlY5I#VMjBTlfq0eZUfn721tBOevG-l_y75cCAMJg1A6gxAPA

You can check the commit message on this page (and the previous one) to learn more about the improvements (focus especially on commits by developer "kerneltoast"): https://github.com/Tomoms/android_k...e=0cebb575d8a3d62984d0d6a161a818ed7a6c53f6+35
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Very quick work! I've checked very little. But I did see your prior changes, i.e. the string to change Lineage string for PIF is still fixed and exFAT works. Otherwise, I haven't looked at commits enough to understand it well.

You pointed me to Lineage-21-cip. Those commits have today's date and earlier ones. I'll look through those soon. But when you said "previous one", do you mean Lineage-21 in the pulldown? Or where it has previous and next at the bottom of this page? Previous won't go back since this is the most recent page, but I can click next. Let me know a little more about exactly which pages to look at.

I assume you did not go back and put every fix from when 21 started. That would be tons of work to go backwards to put it in the 20 kernel. You can tell me exactly what I'm getting.

Finally, is this something you can continue to do, i.e. putting the 21 kernel fixes into the 20 kernel and making a flashable kernel zip for me? If that's too hard or a ridiculous question, I understand. It may not be feasible for you to continue. Your work is greatly appreciated and is above and beyond.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I meant that you should click Next (which will show you chronologically older commits).

This kernel is 100% identical to the one bundled in my 21 ROM/boot image. You're getting everything :)

It is super easy to keep building these kernels. The difference between a 20 and 21 kernel is only 5 commits that are needed to boot 21 but break 20, so I just have to take my 21 kernel source, revert those 5 commits and rebuild the kernel (which takes 5 minutes).
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
That sounds perfect! So glad to be getting everything. I'm glad it is not a monumental task for you. Thanks so much, I will look forward to getting these flashable kernels when you think it is appropriate.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
A new build including July's security patches is available :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, all sensors are broken on the latest build, sorry about that. While you wait for a new update, you can apply the fix manually:

adb root
adb remount
adb shell cp /system/lib64/libpower.so /vendor/lib64/
adb shell cp /system/lib/libpower.so /vendor/lib/
adb reboot

USB debugging and Rooted debugging must be enabled in Developer Options before running these commands.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks, since I must have not needed the sensors yet, I had not seen a problem. I got those commands done but did some of them separately since I got this error below. Is this expected?

C:\WINDOWS\system32>adb remount

avb_user_verity.c:97: ERROR: Data from 'boot_a' does not look like a vbmeta footer.

Error setting verity state

Kernel does not support overlayfs

Overlayfs setup for /vendor/lib/dsp failed, skipping

Cannot mount overlayfs for some partitions

Remounted /vendor as RW

Remounted / as RW

Remounted /vendor as RW

Remount failed

Also, I have never turned on "Rooted debugging" before now, so I don't know about it. Is it necessary in this case? I mean, I think I could go into adb, issue su, etc.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Entering an adb shell and then issuing su yields the same effect, but those who are not rooted can't do that, thus I provided the most general instructions. That error message on adb remount is safe and expected, all is good, just ignore it :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I guess I have been rooting for so long that I didn't even realize this Rooted debugging command existed. And that it could be used to do "root-like" things, even when not rooted. Thanks for the explanation.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I've released a new update with the fix for the sensors issue and several other updates and improvements.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hi, this is a kernel you can flash on top of the latest build to improve the strength of the vibrator, which has been crippled since the very first LineageOS 21 builds.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
I'm guessing this only works for Lineage 21, and you'll have to do a separate one for me for my Lineage 20 boot image (with 21 ROM)? Since I'm not worried about the vibrator strength, maybe you don't need to do this until there are more reasons to.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I will provide you with a flashable kernel that works for you tomorrow.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Sorry, I forgot to send you the new kernel. Here it is: https://mega.nz/file/h8NnxZYD#uk8Q2F9O31Q-MHnUR9qGGh4a-72LBDf7-7NOX60bt6A
[Essential Phone ROMs, Kernels, Recoveries, & Other] sga999:
Thanks! knew you'd get to it soon, and I was in no hurry.

I'm assuming you keep combining all of these kernel fixes into the latest. I mean, if I was "starting over", I would only have to install the latest, not prior ones you have given me.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Exactly. Kernels are not overlayable, if you flash ten of them you're only actually using the tenth. And the latest I provide you always contains all the previous enhancements and features.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Mario3DS:
thank you for your work<3

a question, is this newer kernel more battery intensive because of the performance optimizations? I want to try it but my battery already lasts barely a day x__x
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Not at all. The performance improvements in this kernel come from:

improved memory copy/comparison algorithms. These algorithms are used at a low level by the kernel, I have replaced the generic versions with better implementations that are highly optimized for 64-bit ARM processors (these implementations are provided by the ARM company itself)

updates for the task scheduler. Scheduling is one of the most critical tasks performed by the kernel, so avoiding useless computation by stripping out unneeded code can help.

backports for the memory allocation routines. I have applied some patches from Linux 5.2 that are supposed to improve performance when allocating big chunks of memory. Some guy from Phoronix has stated, regarding this backport: "Personal tests are showing that the device is more responsive when memory pressure is high and when huge allocations are to be done, it's also noticeably faster in this case, like when starting Chrome with more than 100 opened tabs after a system reboot."

So as you can see, none of this stuff has a negative impact on power consumption, quite the opposite! Power consumption might be improved at a microscopical level, because stuff is done more efficiently, wasting as little CPU cycles as possible on useless computation.

For other technical details, you can take a look at my kernel repo.
[Essential Phone ROMs, Kernels, Recoveries, & Other] tlxxxsracer:
For the life of me I can't get Gapps to work. I follow the LOS instructions to a T (rebooting back into recovery after flashing the ROM in LOS recovery.

GAPPs flash but during setup I just keep getting Google Play services keeps stopping and never can continue on through the setup during "setting up phone. may take several minutes". It errors out.

suggestions?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
What's the name of the Gapps zip file you are flashing?
[Essential Phone ROMs, Kernels, Recoveries, & Other] luigy95:
What is the most recommended Gapps Pack?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Latest MindTheGapps, arm64 of course: https://androidfilehost.com/?fid=17825722713688288529

Freshly updated today.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
For Android 11 the only version of GAPPS recommended by Lineage is MindTheGapps.

Here is the link:

MindTheGapps-11.0.0-arm64-20220217_100228.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
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
New build available with a couple of bug fixes. More info in the first post. The new improved kernel should still be flashed separately, it's not bundled in the ROM yet.
[Essential Phone ROMs, Kernels, Recoveries, & Other] itsita:
Flawless work, Many thanks!

Looking forward for the kernel bundling.