yashsingh1/xdaforums huggingface dataset:
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rickyyohanes626:
Finally, I found it, thanks.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Yes. This rom support custom kernel. This ROM is built on stock kernel values for stable and daily use. To get extra squeeze you can opt for custom kernel compromising the load which device handles. Share custom kernel links here.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Upcoming builds ( Only for volunteer testers )

* Experimental build based on CAF audio features. Dirty flash supported ( Only wipe system and vendor before flashing ) . If facing bugs switch back to stable build "lineage-17.1-20210204-X00TD-user-signed" on dirty flash.

lineage-17.1-20210303-X00TD-user-signed
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Rasyad:
installed lineage-17.1-20210304-X00TD-user-signed build since gets uploaded.

I didn't see any audio difference, but everything working great as previous stable build, no issue found so far.

Well, I think this build is rock stable 😁
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Check audio distortion at higher volumes. Previous builds has this issue. 20210304 uses CAF audio.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Orion281:
I flashed the latest experimental build but didn't find any noticeable difference in the sound output. Speaker output is as low as it had been on previous builds. One more thing that I've encountered in this build is that the sound output during calls is very loud and distorted. I lowered the volume to minimum and still could hear everything as if the speaker was on. I hope this helps. Thanks.

Edit: I found audio distortions at high volumes only during calls not while listening music or watching something. I may be wrong though. Someone else has to confirm this.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Also check bluetooth audio .

For Testers: Also check bugs on clean flash . After thorough testing I will update OTA build soon with security patch.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
17. OTA update : lineage-17.1-20210306-X00TD-user-signed

* CAF audio.

* Updated audio configs from stock 10 release.

lineage-17.1-20210306-X00TD-user-signed
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] russelldlongno:
Any plans on building LineageOS 18.1?

Also, is there a build with MicroG preinstalled?

Thank you for the ROM!
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Yes. Need assistance from testers. To test los18 volunteer testers contact me on telegram https://t.me/rajesh_xda .
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rickyyohanes626:
Mine got bootloop after lastest update, using gapps stock variant. Why this is happen?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Gapps projects are taken from latest pixel devices. Stock gapps may not work on non-google devices. It is only meant for nexus and pixel devices.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rickyyohanes626:
Previously using gapps mini variant was working perfectly, meaning that I must use mini variant of gapps? Okay. i'll try.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Captain_Kansloos:
So, just to get this straight, because I'm kind of confused by the intro of this thread. I'm on the latest WW stock Pie release. In order to flash this ROM, while maintaining Widevine L1 certification, I do have to unluck the bootloader in order to flash TWRP or similar first?

Can someone just list the steps involved?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] olzge:
You can find good instructions here: https://wiki.lineageos.org/devices/X00TD/install
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
You need to backup persist partition before flashing custom rom. Backup guide is mentioned in this thread. So you can save widewine L1 certification.

You need to backup persist partition before flashing custom rom. Backup guide is mentioned in this thread. So you can save widewine L1 certification.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Captain_Kansloos:
You must be refering to this guide: https://xdaforums.com/t/guide-dump-all-partitions-and-make-complete-backup.3791202/

So, the steps would be:

1) Factory reset on original Pie en locked stock bootloader (to prevent issues with flashing)

2) unlock bootloader

3) flash custom recovery

4) backup persist partition as stated in guide.

5) Flash custom rom + GApps via custom recovery

6) ?Restore persist?

I don't really understand what the backup persist provides. Is it just a safeguard to be able to return to stock ROM and L1 certification? Am I right? What am I missing?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Actually backup guide is a suggestion from a user from asus zenfone max pro M1 community group.

First thing i want to make clear that I haven't tested this backup method.

Explanation:

From stock android pie.

1. For backup. You need to unlock bootloader in stock rom and backup persist partition.

2. Then you will flash custom rom through twrp and will lose your L1 certification to L3.

3. If you try stock rom again by fastboot you will stay in L3 certification. To solve this you need flash persist partition to get L1.

All this backup only works on android pie.

From android 10 stock rom.

1. Unlocking bootloader from stock android 10 will lose your widewine L1 by default from very first step. No way to recover.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Captain_Kansloos:
OK. So, flashing custom ROM will ALWAYS result in (temporary) loss of L1 certification. The Pie based persist partition backup should be able to get you L1 certification again, if you decide to return to stock Pie.

OK. Makes sense I guess.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Widewine L1 certification is only available on stock rom with locked bootloader.

As mentioned in thread, unlocking bootloader from android10 will lose your L1 permanently. Reverting to stock rom wont help. Only if you did persist backup on android pie will help.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Captain_Kansloos:
Yes. Got it, thanks for the feedback.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Captain_Kansloos:
It seems the original download for the backuptool is not available anymore. Anyone got a working link?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Backup tool credits @Sudeep Duhoon

Reupload : https://sourceforge.net/projects/lineage-x00td/files/Backup tool/backup_16-5-18.rar/download

Guides and instructions : https://xdaforums.com/t/guide-dump-all-partitions-and-make-complete-backup.3791202/
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Human_Number_103909909301:
👍Thanks for all the work that you're doing. If you can and want to, please bring back to life the official release.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Hi, Thanks for your time and support great image.

I want to confirm that I had been hit by sound bug. First release which I installed was lineage-17.1-20210306-X00TD-user-signed and caller application was very loud and not reacted on sound level changes. After update to lineage-17.1-20210315-X00TD-user-signed.zip problem gone.

Another One think. May I ask you to add support for sway in the latin keyboard? Please add lib and symlinks acording to code from opengapps :

ui_print "- Installing swypelibs"

extract_app "Optional/swypelibs-lib-$arch" # Keep it simple, swypelibs is only lib-$arch

install -d "/system/app/LatinIME/$libfolder/$arch"

# create required symlinks

ln -sfn "/system/$libfolder/$keybd_lib_google" "/system/app/LatinIME/$libfolder/$arch/$keybd_lib_target"

ln -sfn "/system/$libfolder/$keybd_dec_google" "/system/app/LatinIME/$libfolder/$arch/$keybd_dec_google"

ln -sfn "/system/product/$libfolder/$keybd_lib_google" "/system/product/app/LatinIME/$libfolder/$arch/$keybd_lib_target"

ln -sfn "/system/product/$libfolder/$keybd_dec_google" "/system/product/app/LatinIME/$libfolder/$arch/$keybd_dec_google"

best regards,
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Unfortunately I have to confirm that I found another one bug. Phone connect with my car via bluetooth but microphone and speakers don't work. I tried test other options and standards in the debug options but doesnt help. I tested it today only with lineage-17.1-20210315-X00TD-user-signed.zip . BTW. I can perform more tests on your builds.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Switch to stable build https://sourceforge.net/projects/li...-17.1-20210204-X00TD-user-signed.zip/download
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Magus92:
Does this ROM have particular issues or bugs?

(didn't find them on the first post, just asking '-' )
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Thanks. :) I'll test that build. Probably you will need to update bluetooth to the relevant revision.

EDIT. I sent you via private message link to the logs.

With 20210204 bluetooth audio works ok. Sound quality is like with Experimental build so quite ok.

btw. I removed my locksettings.db and backported to older revision of the build. I think you should remove newest OTA build from OTA.

EDIT2: howto add sway library and gusture keyboard for lineageOS without google apps.

Under restore execute commands ( via phone terminal or adb shell)

copy libjni_latinimegoogle.so from pico google aps and put on your sdcard or internal data storage then:

ASUS_X00TD:/system/system/lib64 # mkdir -p /system/system/app/LatinIME/lib64/arm64
ASUS_X00TD:/system/system/lib64 # cd /system/system/app/LatinIME/lib64/arm64
ASUS_X00TD:/system/system/app/LatinIME/lib64/arm64 # ln -s /system/lib64/libjni_latinimegoogle.so libjni_latinimegoogle.so
ASUS_X00TD:/system/system/app/LatinIME/lib64/arm64 # cd /system/system/lib64
ASUS_X00TD:/system/system/lib64 # cp /external_sd/libjni_latinimegoogle.so /system/system/lib64/
ASUS_X00TD:/system/system/lib64 # chmod 0644 /system/system/lib64/libjni_latinimegoogle.so
restorecon -R -v libjni_latinimegoogle.so
chcon u:object_r:system_lib_file:s0 libjni_latinimegoogle.so

Best regards.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
I will try to add in my builds. Sound quality is ok but i am trying to fix it. Which ROM has good sound quality?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
I have good sound quality with 20210204 and Experimental 20210315. I haven't noticed any lower quality under high volume with 20210204 but maybe I'm deaf ;-)
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
I found another one problem. The kernel process [ksmd] takes on my phone cpu around 20% even when I dont use phone. My phone 4GB/128GB. We need to tune ksm or just disable it. Now it is too aggressive.

I can see line:

/vendor/bin/init.qcom.post_boot.sh: echo 1 > /sys/kernel/mm/ksm/deferred_timer

It is in the

case "$target" in
"msm8610")

We need add that same line in the relevant place.

BTW . have you disabled "init.qcom.post_boot.sh" from the boot process?

EDIT:

documentation:

Documentation/vm/ksm.txt - kernel/msm - Git at Google

EDIT2:

With these parameters ksm takes around 1% cpu.

echo 100 > /sys/kernel/mm/ksm/sleep_millisecs
echo 1 > /sys/kernel/mm/ksm/deferred_timer
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] x00tdusr01:
Hello, thakns for your work. Any chance this going official LOS build? ATM this device is no longer maintained by LOS team.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Lineage needs continued support and updates. Due to work, i cant spend more time and effort on open source and development. Read disclaimer in this thread. I will submit source to lineage team. Let lineage team decide on official release.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
In my opinion 20210204 is very stable and usable. I think only kms fix need to be implemented and then release updates with security fixes as a stable. Other problems could be fixed in the "development" branch during spare time

best regards.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Upcoming builds ( Only for volunteer testers )

* Experimental build to test audio quality. Dirty flash supported ( Only wipe system and vendor before flashing ) . If facing bugs switch back to stable build "lineage-17.1-20210204-X00TD-user-signed" on dirty flash.

lineage-17.1-20210326-X00TD-user-signed
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Last release is ok. We need tune ksm , update kernel and vendor part. Then it will be perfect.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] beitme:
My man, I like your attitude. Pragmatic, yet aspirational. See the viable end, pursue, and obtain it. Done. Bam.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
I found two problems with the latest build from 27.03.

1. Fingerprint unlock doesn't work - every time it's 'not recognised'.

2. Accelerometer sometimes stops working and doesn't react to screen rotation. But after some time it works again until it doesn't feel like working again. I haven't tried build from 04.02, but all builds after that date have this problem.

I didn't record any logs, sorry.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
These issue also noticed in stock ROM. Finger print fails to work in stock rom due to dirt. There may some hardware related constraints.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
I see. Well, that's a shame. Your build is pretty much the only Android 10 ROM with working enforcing SELinux.

Thank you for the clarification.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] russelldlongno:
Hi, I've tested the latest stable build and found a bug. Rotation sometimes not working well. When I try to view a webpage or play a video in landscape mode, the screen won't turn in 90°. Sometimes when you turn it to 90°, it just flips it over to 270°. Sometimes it doesn't work at all. Thanks!

P.S. Found out that LineageOS 17.1 won't receive any feature advancement. The team will keep updating it with security patches though.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Nitinkumar3222:
Amazing ROM unofficial ho kar bhi SBI yono bhi perfect work kr RHA h ,, baaki jitni bhi LOS ROM h kisi me bhi yono work nhi krta or selinux ka issue rehta h or device boot hone par 'internal problem' ka popup aata , lekin isme aisa kuch bhi nhi ,, specially thanks rajesh@xda sir great work,, aage bhi update dete rehna
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
First of all, it's always nice to read the thread before posting. Second, there is some sort of workaround. Locking the screen with power button and unlocking it makes the screen rotation work again for a while.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
I dont have problem with screen rotation and I dont know howto build whole android image but as a unix engineer I know what I can do with linux kernel and repack boot.img from last build (20210327).

Karnel 4.4.260-perf based on the https://github.com/travarilo/kernel_asus_sdm660 ( branch master)

config file base on the build config file 20210327 or 20210404.

additionally added westowood+ for tcp and reduced number of the kernel modules incorporated them into the kernel file.

HOWTO flash it:

1) update to the build 20210327

2) enable debug option int he mobile phone - probably enabled already

3) adb reboot fastboot

4) fastboot flash boot boot.img

Maybe it will solve some problems with sensors. I can see much less errors on the kernel level but still need to investigate some components.

best regards and Happy Easter.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
So, about fingerprint unlock...

After I had reported about fingerprint unlock wasn't working I tried ArrowOS one more time, decided I've certainly had enough with that ROM, formatted the data partition, wiped everything and clean flashed LineageOS 17.1, the build from 27.03. And since then fingerprint unlock have been working most of the times. When it doesn't work, it may be some sloppiness on my part.

Then I saw the post from @patkk and flashed his boot.img. Fingerprint scanner didn't stop working and accelerometer had the same problems as before. Although after that Orangefox recovery can't decrypt the data partition anymore. I guess it's my fault. Oh well )

And finally I've got an OTA update from 04.04, installed it through updater and now both accelerometer and fingerprint scanner are working without any problems. So, it looks everything is fixed for now.

Thank you guys.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
could you confirm that after flash of the 20210404 you still have problem with Orangefox recovery? If not then maybe you know what kind of the encryption and hash algoritm it use?

Flash from the OTA/recovery overwrite custom boot.img.

btw. I cant reproduce problem with the accelerometer on my mobilephone but I can see much less errors in the dmesg. Kernel provided by me have linux security patches until end of the february.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
Yes, the recovery still can't decrypt the data partition. I don't know about the encryption details unfortunately. And it turned out the problem with screen rotation is still there in the build 04.04.

I reflashed your boot.img anyway. Although I guess the correct order of doing it would be fresh installing the ROM, flashing custom boot.img and then enabling the encryption.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
If you want test 4.4.260 kernel then you flash boot.img as a last step. If you want use boot.img from build and check encrypted partition then flash only build from OTA and not reflash after that boot.img.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
@patkk I have good news ) It turned out the problem with encryption has nothing to do with your boot.img. The culprit is the latest version R11.0_3 of OrangeFox recovery. The devs managed to screw up decryption for everybody. After reverting the recovery back to R11.0_2 decryption works agian.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
I introduced some changes in the configuration based on the other builds . Source code not changed.

Kernel 4.4.260 (https://github.com/travarilo/kernel_asus_sdm660)

- default wifi algoritm: westwood+

- default IO algoritm: no-op instead of CFQ ( more about it https://lwn.net/Articles/674300/ )

- removed not used modules and drivers

- added more linux kernel encryption algoritms.

- added native drivers from kernel for RTL SDR (I use it for DAB radio like https://www.welle.io/ ).

HOWTO flash it:

1) update to the build 20210327 or newer.

2) enable debug option int he mobile phone - probably enabled already

3) adb reboot fastboot

4) fastboot flash boot boot.img

Maybe it will solve some problems with sensors. I can see much less errors on the kernel level but still need to investigate some components.

best regards
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Could you test my kernel and native from build? When you have already charged battery (100%) and phone still connected to the charger what kind of information you have in the battery application from the configuration (charing or something else) (lock screen will show you correct information that battery already charged).
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] russelldlongno:
Hi, once again! It's pretty stable enough for me. The only problem is the screen rotation, that's it.

BTW, Can I update the ROM if I'm encrypted through the OTA updater? Or I'll need to manually flash it?

Can "we" have a MicroG variant in the future?

Thanks! (really do!)
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Could you test last image from me?

btw. on 17.1 I can confirm problem with charging. When battery is full on my phone I can see still "charing". On other build 18.1 with kernel 4.19 I can see battery full. Ampere also showing charing status on full battery.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
OK, with your boot.img flashed yesterday:

1. Lock screen: 'Fully charged', but the battery icon in Status bar indicates ongoing charging.

2. Settings => Battery: '100% charging'.

With 'stock' ROM from 04.04 updated today by Updater:

1. Lock screen: 'Fully charged', icon indicates charging.

2. Settings => Battery: '100% charging'.

So, I see no difference.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
Chances are you are not encrypted if you are human, but the /data partition in your smartphone probably is. And yes, it's safe to update using updates received by OTA.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Thats right. I have that same problem but on the 4.19 kernel and build 18.1 (with disabled selinux) problem not occured. I'll focus on the kernel part and will try port 4.19 to 17.1 build. For now I have compilation problems related to selinux.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] ModiFlasher:
How to record internal audio with this rom using Screen Recorder (no ads)
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
I can see that test build getting worse and problem with battery charging still occur. I found for now howto solve problem with battery charging on the current builds.:

- install magisks

- install plugin acc in the magisks

- restart phone

- install from fdroid the accd app and add root access only one time

- reconfigure acc via accd and set disable charing on the 100%.

- restart phone

- uninstall accd

- remove in the magisks root access for all apps.

Maybe its a good idea add acc into the build?

best regards,
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Kernel 4.4.255 based on https://github.com/PixelExperience-Devices/kernel_asus_sdm660/commits/eleven

- changed :

PLUS:

- pixel kernel have newer driver for battery and charger and many more. Not analyzed yet.

- charing battery finish around 7 minutes after 100% status ( usb charger tested ).

- BFQ IO scheduler.

MINUS:

-NFC doesn't work. Need update vendor part.

I changed kernel source for legacy chapric driver which is use in that build.

Upper bar still showing charing icon but battery app and ampere showing information "charged". That same on the kernel level.

I think that is a problem with lineageos build.

Flash it like before:

1) update to the build 20210327 or newer.

2) enable debug option int he mobile phone - probably enabled already

3) adb reboot fastboot

4) fastboot flash boot boot.img

5) fastboot reboot
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] patkk:
Another one kernel for testing : 4.4.263 based on https://github.com/wimbiyoas/msm-4.4/commits/master

- NFC works , battery should also like with pixel one. You could check other issues too.

@rajesh@xda I tested some kernels for your 17.1 . I think it looks ok. If you want I can share repo with changes but you need to decide which kernel we will use. The best one in my opinion is the pixel one because have qcom drivers released 2020 instead of 2017. Should be much more stable but will require update vendor part for example for NFC.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Only for volunteer testers

To check OTA property of lineage-18.1 over lineage-17.1.

Download manually and update.Before installing wipe cache,system and vendor in twrp

lineage-18.1-20210413-X00TD-user-signed.zip
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajesh@xda:
Only for volunteer testers

To check kernel updates on lineage-17.1.

Download manually and update. If bootloop switch to stable build. Dirty flash supported.

lineage-17.1-20210414-X00TD-user-signed.zip
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AnotherUniqueUserName:
It looks like there is no OTA update for the new version. Are there any particular reasons for that?