yashsingh1/xdaforums huggingface dataset:
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Thanks! Actually, what I wrote previously is wrong. The improved kernel is already bundled in the latest build of the ROM, but it is built with an older compiler and without the most advanced link-time optimizations. So, even without flashing the latest kernel separately, you still get all the nice things I described here.
[Essential Phone ROMs, Kernels, Recoveries, & Other] a.faz.ago:
Hi, i'm using lineage with my huawei mediapad,

i read that i have to recompile the kernel to have the ch341 driver working with my 3d printer, can you help me, or have you a precompiled kernel with the driver enabled?? Thanks!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
New build available, with March's security patches and an important fix for T-Mobile users: audio is not distorted anymore when calling with VoLTE enabled. A huge "thank you" to @MuddyDog for helping me test many builds before finding the final fix.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Thank you for an excellent ROM. So far so good.

But I have to say, the LOS recovery is useless. No backup/restore. I had a heck of a time getting TWRP installed again...

But that's just an aside. The ROM is well done and systemless microG works very well 👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I will develop a newer TWRP for mata. Not sure when, maybe next month or maybe next year, but it will eventually come :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
The current one works with one quirk: you have to delete the /data/per_boot folder before backing up or it will fail. Just merge that fix in and you're golden 😉
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
The current one is a mess under the hood and needs to be rebuilt completely from scratch. I'll look into this issue as well.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lasuazo:
This ROM is dope so far, I was trying to stay away from LOS due to aesthetics, really didn't like it. But hey, I need something functional for this amazing phone and to keep it alive for another couple of years. Installed following the LOS wiki, using lineage recovery (hope I did the right thing) well it did boot and so far no issues were encountered. I would suggest a little guide on the main post for us noobs, would be greatly appreciated as one wonders if they are following the steps correctly following "other" guides intended for "other" ROMs. Hey many thanks for the ROM. oh BTW mindthegapps and no root. (Y)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lasuazo:
@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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] lasuazo:
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
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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...
[Essential Phone ROMs, Kernels, Recoveries, & Other] lasuazo:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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 :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hello, I'm quoting you even if it seems you are not active on XDA anymore. The next build will fix the minimum brightness issue. The minimum allowed brightness will be as low as it is on the stock Q ROM.
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Thank you for providing a stable ROM for this ageing device!

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

You can find it here:

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

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

androidfilehost.com
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Why on earth did you install MindTheGapps 12 on top of an Android 11 ROM?
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MuddyDog:
Nope...

MindTheGapps-11.0.0-arm64-20220217_100228.zip​

works correctly with

Official Lineage 18.1

and

Unofficial, Optimized LineageOS 18.1, including the newest build lineage-18.1-20220408

I'm currently using the 20220408 build...
[Essential Phone ROMs, Kernels, Recoveries, & Other] CamoGeko:
Well, maybe it works for you... But for me it wouldn't flash. While the Android 12 Gapps flashed fine. Not sure how you would explain that but yeah.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hey guys, just wanted to drop a line to say that April's build is definitely coming. Sorry for the delay, April's security patches have been out for one week now, but until the end of summer I won't always be able to deliver updates regularly. There are already two April builds in my SourceForge folder, but they miss one or two things I want to implement in my final April build, so I haven't pushed them via OTA. The final build should be ready in a couple of days :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
No pressure. Thanks for the dedication 👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hello! I released a new build yesterday. I've updated the first post with the changelog. Enjoy :)

EDIT: I haven't uploaded the corresponding bootimage. You can use the previous release's bootimage if you're installing this ROM for the first time and you need a recovery.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Thought: add the device name/code to the thread name for easier searching - here and on the web: more people will find your work 😉
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Makes sense. Done :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Dirty-flashed latest with no issues. Just had to reflash Magisk. All good 👍🏻

Any thoughts of A12?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] boko1008:
thanks for the ROM, it's amazing! performance and battery life are really good, congrats! I had some issues with Android Auto, apparently it's something common with Lineage 18.1 and MindtheGapps. For anyone else having these issues, here's the solution that worked for me: https://xdaforums.com/t/android-auto-and-lineage-17-1.4199949/post-84956085
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Thanks! I'll add this to the second post, it's not the first time I hear of this problem with Android Auto.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
I don't use Android Auto or gapps, but good on you for sharing the solution here 👍🏻

That's how forums should work: and its here for posterity, searchable on the world wide interwebs 😁
[Essential Phone ROMs, Kernels, Recoveries, & Other] boko1008:
I actually couldn't get the system partition to mount with TWRP as that solution recommends (I'm not an advanced user in any way, so idk why it didn't work) so I used a File Explorer with root to place the provided file in the system folder, rebooted the system and it worked.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jmye620:
Is there a fix for GPS? GPS hasn't worked on any custom roms
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
GPS works perfectly, I've been using it daily in the past few weeks. Are you using Gapps, microG, or neither?
[Essential Phone ROMs, Kernels, Recoveries, & Other] jmye620:
I'm using MindTheGapps. Are there better alternatives? Thank you for all your hard work on this!!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
No, it should be working perfectly with MindTheGapps, in fact, MTG is the recommended Gapps package...

I'm using microG and it's working perfectly, I can't really help you unfortunately...
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
GPS issue could be 1) hardware or 2) firmware related

You could try re-flashing the latest firmware 🤔
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hello people, I've released a new build. SourceForge seems to have some problems at the moment, so in case of slow or faulty downloads, wait a few hours and retry.

This build brings: an updated SQLite library, an important kernel fix for ZRAM (which was sometimes failing in the background since the very first build of mine, which dates back to last summer - not a critical bug but still important to have it fixed!), and a few minor tweaks for the kernel.

In order to fix the ZRAM bug, I had to revert the updates for the ZRAM driver I had applied in the kernel. Thus, LZ4 now replaces zstd as the compression algorithm (just like in official LineageOS). However, it is an updated LZ4 engine which should perform better that the older one which is present in our LineageOS kernel, so I still expect ZRAM to perform a tad better, compared to official LineageOS :)

If you want to live on the edge, you can flash this kernel: https://mega.nz/file/E9ME2R4b#sFNw-D0ZZpUMSjRMxYbzkwfhpvAfZ6KnqoEMfWDY3mQ

Source-wise, it is identical to the one bundled in the new build, but it is compiled with the latest Clang 15.0.0 and Polly optimizations. Seems to be working fine here.

Happy flashing!
[Essential Phone ROMs, Kernels, Recoveries, & Other] itsita:
So for the past two builds, dirty flashing using the lineage-recovery doesn't boot unless I factory reset.

Reflashed Mindthegapps and Magisk to both slots as well to no avail.

Am I missing something? is there a better way to flash?

Thanks
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
This is not normal. I've always dirty-flashed as usual, no issues on my device. What is your current status? Active slot has got my April 28th build, with Magisk and MindTheGapps, but it doesn't boot, because you haven't factory-reset it yet?
[Essential Phone ROMs, Kernels, Recoveries, & Other] itsita:
I was on the April 13th build, then booted to recovery and sideloaded the April 28th build. This doesn't boot for me - it fails and brings be back to recovery.

At that point i've used fastboot to change slots back and forth and flashed magisk to both of them (as the recovery flashes magisk to the other slot afaik), eventually came back to the slot of the 28th build. This doesn't boot as well.

Only after factory reset it boots as normal.

Could it be related to encryption?
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It could, but everybody's data partition is encrypted, so I cannot understand why you're having problems.

Next time, in order to flash Magisk in the correct slot after an upgrade, just enter the Advanced menu of the recovery and tap on Reboot to recovery. The phone will be rebooted to recovery and the active slot will be automatically switched to the one in which you have just flashed the new build. At this point you'll be able to flash Magisk or whatever in the proper slot. No fastboot needed.

Anyway, if as of now you have fixed the problem by factory-resetting, let's wait and see what happens with the next build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] sambow23:
What toolchains do you use to compile the kernel? I've tried Google's AOSP GCC+Proton Clang but I'm getting many errors.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
For inline builds of the kernel (i.e., kernel built during a full OS compilation), I use this clang. For standalone kernels, I use a more up-to-date Clang (Proton clang 13 until a few weeks ago, Atom-X Clang 15 currently). Take a look at the funcs.sh file in my kernel sources to see what environment variables and what make arguments I use to build.
[Essential Phone ROMs, Kernels, Recoveries, & Other] jabia:
Had this issue too! Thought I did something wrong.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
I use TWRP. It's flakey, but it works. You have to remember to flash it after every ROM update so as not to lose it. And you have to remove the /data/per_boot folder, or backups will fail.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Hello, a new build with May's security patches has just been uploaded. It'll be available for downloading (also via OTA) in a few minutes :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] 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 :)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Here we are! My first 19.1 build is available :)

It already brings a couple of bug fixes over the official builds (more info in the first post), one of them has already been pushed to our official LineageOS device tree, the other one should be approved soon.

MicroG and OTA Updates are already supported.

Lots of optimizations, tweaks and whatnot are coming in the next weeks.

Happy flashing!

EDIT: the Updater will report an error if you try to check for an update. This is "normal" for now, it'll start working fine when I publish the next update.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Trying to download today's image and no go. Anyone else? The one from yesterday (5-23) starts to download ok
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
It's working for me right now. Please retry.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Downloading now 👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Well, surprise, surprise! I did a dirty flash on top of your previous (all-configured) A11 version, and everything seems to work and kept its settings! That's a good start if I don't need to wipe/format data... But will keep testing to make sure.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
One thing that doesn't work for me is Gravitybox (LSPosed module) - to be expected as there is no A12 version.

The one (only?) reason I use it is for re-mapping the recents key. So, a request:

Please implement re-mapping, not to last app (which is there in the settings already), but to previous active app - ie., if apps are terminated/killed they're not reopened.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
And then it all went to pieces... I added fingerprint protection and that must have triggered data encryption (I had only swipe on A11). Even though I removed all security settings, TWRP can't decrypt data and system won't boot (probably can't read it either). And my TWRP backups were on that (now undecryptable?) data partition. So, I may have to wipe and start fresh after all 😕
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
IF you can point me to a custom ROM (even for another device, not necessarily for mata) that implements this feature out-of-the-box (i.e. without GravityBox)

THEN I might be able to port the feature into my ROM

ELSE it won't come, as it's probably too hard for me to implement it on my own.

Not sure about what happened here. TWRP cannot decrypt Android 12's encrypted /data partition, this is a known issue. But I cannot explain why the OS cannot boot.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Right, well I recovered by sideloading the ROM, etc.

It works, but I do miss the TWRP access to data (for backups, etc.) that was there with A10 & A11. Android really is becoming less and less usable with each new release 🙄
[Essential Phone ROMs, Kernels, Recoveries, & Other] jabia:
Flashed the 19.1 ROM over 18.1 and it works beautifully! No data lost (I used lineage recovery)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Nice! As soon as June's security patches are merged, I'll release another build with some interesting stuff.
[Essential Phone ROMs, Kernels, Recoveries, & Other] surya17:
Amazing to still see support for this cool old phone. Did anyone encounter the loudspeaker low mic volume bug on this ROM? On the official lineage 19.1, it's apparently still present!
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Low? Do you mean loud? A known issue of LineageOS for mata (and other devices) is that the loudspeaker, during calls, has got a very loud volume and it cannot be adjusted. This issue is present in my builds as well, at the moment, but I will look into it soon.
[Essential Phone ROMs, Kernels, Recoveries, & Other] surya17:
That also may be an issue, but I meant that people on the other side couldn't hear you well (or even not at all hear you) when on loudspeaker for regular calls/ WhatsApp video calls. This was also a known issue.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
That microphone issue should be fixed. Please try and let me know, if you can. I'll be glad to look into it again if you still face it.
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
I've uploaded a new build, with June's security patches; a new ripple effect that can be seen when tapping on button, menu entries, etc.; an updated and optimized SQLite library, for improved database management performance; and a few minor tweaks in the Android RunTime.

This build is the last one featuring LineageOS's default kernel: starting from the next one, my kernel will be bundled.

The new build is not available via OTA yet. It's on SourceForge, but I'll make it available via OTA tomorrow, because I can't do so right now.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Will check it out in the next few days 👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
Nice! BTW, I've just made it available via OTA.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Just to report, the latest is working well (at least the functions I've tried). Seems snappy and stable 👍🏻
[Essential Phone ROMs, Kernels, Recoveries, & Other] surya17:
@Tomoms I'm coming from official Q (Jan build). I just installed LOS recovery, and was about to format the phone before installing your build. I just saw that it would wipe internal storage as well. Is there no way to factory reset just the system without internal? Maybe I can use twrp, which has system-only reset to install the your LOS ROM? I was on TWRP recovery before LOS, which worked perfectly for me to install magisk.
[Essential Phone ROMs, Kernels, Recoveries, & Other] temporarium:
Make a TWRP backup and try dirty.

It worked for me (A11 to A12)
[Essential Phone ROMs, Kernels, Recoveries, & Other] Tomoms:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] surya17:
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.
[Essential Phone ROMs, Kernels, Recoveries, & Other] MarSOnEarth:
"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+).