yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 2] arter97:
A major beta update is up.

I'm not expecting this to be unstable, but I'm marking this a beta as a lot changed.

Starting off with most important changes: 2 hardware driver issues were fixed.

First one has been present since r9. Backported vmalloc patches from r9 was causing several hardware-related memory (qcom,secure-cdsp, qcom,secure-sp-modem, qcom,secure-sp-tz) to not initialize properly. This is now fixed. (The effect of this is unknown.)

Another one is USB, where Qualcomm-specific code was not being called at all due to CONFIG_KPROBES disabled. This is also now fixed. This may fix several USB issues people might have had before (which may include power-consumption-related stuff).

There has been a ton of backports from Linux mainline:

- Enablement of kmap_local(), avoiding unnecessary locking overhead

- Entire workqueue subsystem backported

- dm-verity/fs-verity backported including latest performance improvements: https://www.phoronix.com/news/DM-Verity-Multi-Buffer-Hashing , https://www.phoronix.com/news/Linux-6.10-FSCRYPT

Besides the backports, there are some other notable changes:

- dm-verity is relaxed to only check once to accelerate future reads (increases system-related partitions' read performance)

- KernelSU v0.9.4

Other minor changes:

- Wi-Fi drivers updated to 2.0.9.22

- Linux v5.10.213 merged

- KERNEL.PLATFORM.1.0.r3-04600-kernel.0 merged

- Switched to LLVM 18.1.6 compiler
[Nothing Phone 2] whatsek:
Nice update! Thanks!
[Nothing Phone 2] attitude12:
It's the same with AlphaDroid. :(
[Nothing Phone 2] Sharma Venkatesh:
Arter's stuff is made for Stock NOS or NMuch at this point. This works with other AOSPs as well, but does break some minor stuffs here and there
[Nothing Phone 2] arter97:
Stable r18 is up.

r18

Hardware device driver issues fixed: qcom,secure-cdsp, qcom,secure-sp-modem, qcom,secure-sp-tz memory initialization (from r9), Qualcomm-specific USB callbacks (from r1)

Enablement of kmap_local(), avoiding unnecessary locking overhead

Entire workqueue subsystem backported

dm-verity/fs-verity backported including latest performance improvements: https://www.phoronix.com/news/DM-Verity-Multi-Buffer-Hashing , https://www.phoronix.com/news/Linux-6.10-FSCRYPT

dm-verity relaxed to only check once to accelerate future reads (increases system-related partitions' read performance)

KernelSU v0.9.4

Wi-Fi drivers updated to 2.0.9.22D

Linux v5.10.214 merged

KERNEL.PLATFORM.1.0.r3-04600-kernel.0 merged

Switched to LLVM 18.1.6 compiler
[Nothing Phone 2] dlads:
The previous one literally gave me an extra hour SOT, so if this one's more stable then that's superb..

Thanks for your work on these, definitely appreciated..👍🏼
[Nothing Phone 2] dlads:
Proof in the pudding..

This is the beta.
[Nothing Phone 2] Noryakky:
Is it just me, or the /sys/class/leds/aw_vibrator/custom_gain is missing in R18?
[Nothing Phone 2] mollex:
arter97-kernel-r18-boot works beautifully in my crDroid 10.5. (y)
[Nothing Phone 2] dlads:
FP and brightness all working?

That means it should work on most if not all custom ROMs.

That's huge news tbh
[Nothing Phone 2] mollex:
I do not use FP. In quick settings brightness all works OK.

I don't use FP. In quick settings Decreasing and increasing brightness is OK.
[Nothing Phone 2] Sharma Venkatesh:
It works just fine, attaching for reference
[Nothing Phone 2] dlads:
Jumped to R18.. so far so good, aiming for around 10 hours from a full 100%

I've turned zRAM off.
[Nothing Phone 2] Noryakky:
I can confirm, flashed now and it works nice. Maybe I did something wrong last time.
[Nothing Phone 2] arter97:
A hotfix r18.1 for KernelSU variant is up.

The newly updated KernelSU required devpts to be patched, which was left out in r18.

Please update to r18.1 for those using KernelSU r18.
[Nothing Phone 2] Noryakky:
Would you mind sharing your config from Franco kernel manager?
[Nothing Phone 2] dlads:
Quite simple really.. some of it works, some doesn't.

Turn zRAM off from the memory page (2nd tab)

Lower the max frequency on all but the small cores on the CPU page, then select the set on boot switch next to each of them..

I sometimes have to choose the lowest CPU speed as it can set itself to 1000MHz for some reason.

That's literally all I change.
[Nothing Phone 2] dlads:
Has anyone tried this on PA? Would it have the same issues as CRdroid has?

Fingerprint issues and auto brightness?
[Nothing Phone 2] arter97:
r19 is up.

r19

Binder driver optimization from Linux v6.6 to reduce app kills from OOM

BBRv3 updated to bbr-v3-2024-02-22-01

Several fixes backported from upstream

KernelSU v1.0.0 merged

Switched to LLVM 18.1.8 compiler

KERNEL.PLATFORM.1.0.r3-04900-kernel.0 merged

Wi-Fi drivers updated to 2.0.9.22H

Linux v5.10.218 merged
[Nothing Phone 2] SonicKiller:
First of all, thanks a lot @arter97 .

Made a small script to change vibration strength at boot for kernelSU, without the need to install any application.

# Assuming kernelSU rooting
# As mentioned in: https://kernelsu.org/guide/module.html#boot-scripts
# This script can be executed at boot if placed in /data/adb/boot-completed.d, as the safest option.
# Do not forget to also mark it as executable.

# arter97 Nothing Phone 2's kernel allows to customize the vibration strength of the phone
# More details at: https://xdaforums.com/t/r19-arter97-kernel-for-nothing-phone-2.4631313/
echo 160 > /sys/class/leds/aw_vibrator/custom_gain

# DEBUG
# Adding the creation of a file on the current folder to indicate if the script executed
#touch ./exec_proof

As I wrote in the script, you can simply drop that script in /data/adb/boot-completed.d (you will likely have to create that folder), and it will execute at boot time after all the modules are loaded and the boot phase has completed.

Don't forget the mark the script as executable with:

Currently it's set at 160, after a few tests this seems to be the sweet spot, for me at least.

Attaching a copy of the script too.

I haven't tried but for people still using Magisk, the same script can be dropped in /sbin/.magisk/img/.core/service.d/ instead (reference: https://github.com/topjohnwu/Magisk/blob/master/docs/guides.md#boot-scripts).
[Nothing Phone 2] MacTavishFR:
Hello everyone. I have a question (maybe dumb)

What's the difference between the boot.img and the kernelsu-boot.img?

Thanks
[Nothing Phone 2] dlads:
The boot image you can patch and use with magisk or just as a non root boot image containing the kernel.

The KSU is for use with the root method kernel su.. you can't switch from magisk to KSU and use the features like modules should you wish if you've flagged magisk previously, iirc magisk remains in stone form and KSU detects it.

For this reason I stick with magisk..

Download, patch with magisk then boot it

Flash with Franco or copy to your computer and fastboot boot it then direct install using magisk.

There's little to no difference between the two afaik
[Nothing Phone 2] ffejy462:
The regular one can be used on stock (or stock based roms such as nothing much) os and be patched with magisk whereas the kernelsu one is intended to be used with kernelsu root method.

Edit:

Both can be used on stock or stock based os, but regular boot is intended for unrooted or magisk and kernelsu boot is intended to be used with kernelsu.
[Nothing Phone 2] dlads:
Both magisk and kernelsu can be used on stock ROMs mate
[Nothing Phone 2] dlads:
Superb battery life on latest kernel.

I've made some changes to governor and limits.
[Nothing Phone 2] ffejy462:
Thank you. Edited my post with that clarification.
[Nothing Phone 2] buu'buu:
hi,

r19 ksu boot img won't boot for me after r15 super img flash. red dots animation don't stop. but with stock 2.6.0 boot image all fine but no root :cry:
[Nothing Phone 2] buu'buu:
LOL

Problem solved, it didn't come from the image files but from my USB cable and my PC. I constantly had a device detected in the device manager even though my phone wasn't connected to the PC. when I connect it and run the command 'fastboot devices' the result gives me '???????? fastboot'.

I changed the cable and now I get:

???????? fastboot

f95692c3 fastboot

I changed the cable, restarted the computer and everything was back to normal. Flash successful

When I flash my device I never execute the first command which is 'fastboot devices'. Now I know that this step is very important and that it would have allowed me to detect the origin of the bug and save time.
[Asus Zenfone 9] arter97:
/*Changelog */

r5

Backported lazy RCU to improve power consumption

Switched to LLVM 18.1.1 compiler

Wi-Fi drivers updated to 2.0.9.21U

KernelSU v0.8.1 merged

LA.VENDOR.1.0.r2-09300-WAIPIO.QSSI13.0 merged

Other minor bug fixes and changes from Google

r4

2024-02-05 security patch merged

WireGuard merged from Linux v6.8

KernelSU v0.7.5 merged

KernelSU change merged to avoid detection

Linux v5.10.209 merged

Fail-safe software driver pwrkey-sync added to minimize data corruption

Optimizations applied to display and camera driver to lower overhead

A workaround for Google Play integrity API's kernel name check implemented

f2fs merged from Linux v6.8-rc2

KERNEL.PLATFORM.1.1.r1-01500-kernel.0 merged

Wi-Fi drivers updated to 2.0.9.21N

Fixes several memory leaks with lazy initcall and KernelSU

Fixed some coding mistakes from Qualcomm

vmalloc backported from Linux v6.8 for some major performance improvements - https://www.phoronix.com/news/Vmalloc-vmap-Lock-Contention-v3

SELinux backported from Linux v6.8 for efficiency improvements

Other minor performance improvements

TCP improvements backported from Linux v6.8 - https://www.phoronix.com/news/Linux-6.8-Networking

sbitmap library backported from Linux v6.8

Several backports made to block subsystem to improve IOPS - https://www.phoronix.com/news/Linux-Caching-Time-Block-IO

r2

Fixed minor device initialization issue

2023-12-05 security patch merged

r1

First stable release

Switched to LLVM 17.0.6 compiler

LA.VENDOR.1.0.r2-07200-WAIPIO.QSSI13.0 merged

LRNG v52 random driver added (improves RNG performance by 30%)

r1b4

f2fs mismerge fixed to fix encryption issue that leads to unusable user data upon reboots

Fixed USB tethering not working

Fixed touchscreen not working in recovery environment

Switched to LLVM 17.0.4 compiler

KERNEL.PLATFORM.1.0.r3-03700-kernel.0 merged

Linux v5.10.198 merged

Wi-Fi drivers updated to 2.0.9.20M

2023-11-05 security patch merged

r1b3

f2fs backported from mainline Linux v6.6

r1b1

Initial beta release
[Asus Zenfone 9] arter97:
/* Known issues */

None.
[Asus Zenfone 9] arter97:
/* Special thanks */

The unit was provided by ASUS.

Thanks to ASUS for the generosity. ASUS phone has been surprisingly easy to work with.

With nothing missing from the kernel source release and relatively clean kernel source from the Qualcomm BSP, this was easy to work with and I hope others can learn from how ASUS handles source releases.
[Asus Zenfone 9] arter97:
Reserved
[Asus Zenfone 9] jons99:
I hope you can add twrp support (y)
[Asus Zenfone 9] arter97:
New beta build is up. There were some important fixes that helps reducing data corruption.

r1b2

Latest Qualcomm BSP tag KERNEL.PLATFORM.1.0.r3-03700-kernel.0 merged

Linux v5.10.197 merged

Wi-Fi drivers updated to 2.0.9.20A

f2fs backported from mainline Linux v6.6
[Asus Zenfone 9] arter97:
r1b3 is up.

r1b2 had a defect where process randomly hangs. r1b3 only picks necessary f2fs patches on top of r1b1.

r1b2 changes will be revised later.

r1b3 (changelog from r1b1)

f2fs backported from mainline Linux v6.6
[Asus Zenfone 9] svenagain:
works fine with custom roms, but I had an issue with the touchscreen in twrp, tried to reflash recovery, but I had to revert to backup boot.img : (
[Asus Zenfone 9] Captain_Throwback:
Maybe you should've read the "Known Issues" in the first few posts?
[Asus Zenfone 9] arter97:
r1b4 is up.

This fixes data corruption issue and should make it daily drivable (I've been daily driving the first beta release ever since it came out, only without encryption), but make sure to back up all data before trying this release. It is a beta after all.

r1b4

f2fs mismerge fixed to fix encryption issue that leads to unusable user data upon reboots

Fixed USB tethering not working

Fixed touchscreen not working in recovery environment

Switched to LLVM 17.0.4 compiler

KERNEL.PLATFORM.1.0.r3-03700-kernel.0 merged

Linux v5.10.198 merged

Wi-Fi drivers updated to 2.0.9.20M

2023-11-05 security patch merged
[Asus Zenfone 9] arter97:
I'm now marking this kernel stable. r1 is up.

r1

First stable release

Switched to LLVM 17.0.6 compiler

LA.VENDOR.1.0.r2-07200-WAIPIO.QSSI13.0 merged

LRNG v52 random driver added (improves RNG performance by 30%)
[Asus Zenfone 9] sendashano:
Thank you sir, the only issues im on voltage os latest build, the issues is sometimes power button does not respond when tried to lock the device, and first time install i need to remove the pin first, but overall the perfomance was great on this kernel thank you
[Asus Zenfone 9] arter97:
r2 is up.

r2

Fixed minor device initialization issue

2023-12-05 security patch merged
[Asus Zenfone 9] adeklipse:
Thanks for the kernel! Feels like I have better standby time compared compared to the stock kernel.

I am encountering a really weird glitch, though.

After a few dozen hours or so, several apps crash, most notably Firefox, Bitwarden, and the encryption feature in Solid Explorer.

My guess is that the glitch has something to do with the fingerprint secrets storage or something similar, since Bitwarden and Solid Explorer both have problems if they request biometric auth.

The Firefox crash, however, I believe has something to do with root; it crashes when I encounter the fingerprint auth bug, just like it would if I put Firefox on Magisk's Enforce DenyList.

A reboot solves the issue, fortunately.

I didn't have similar problems before with the stock kernel or other custom kernels before, so I'm guessing this is an arter kernel specific issue?
[Asus Zenfone 9] svenagain:
January 11 update per telegram, that's supposed to say r3b1:
[Asus Zenfone 9] arter97:
r4 is up.

r4

2024-02-05 security patch merged

WireGuard merged from Linux v6.8

KernelSU v0.7.5 merged

KernelSU change merged to avoid detection

Linux v5.10.209 merged

Fail-safe software driver pwrkey-sync added to minimize data corruption

Optimizations applied to display and camera driver to lower overhead

A workaround for Google Play integrity API's kernel name check implemented

f2fs merged from Linux v6.8-rc2

KERNEL.PLATFORM.1.1.r1-01500-kernel.0 merged

Wi-Fi drivers updated to 2.0.9.21N

Fixes several memory leaks with lazy initcall and KernelSU

Fixed some coding mistakes from Qualcomm

vmalloc backported from Linux v6.8 for some major performance improvements - https://www.phoronix.com/news/Vmalloc-vmap-Lock-Contention-v3

SELinux backported from Linux v6.8 for efficiency improvements

Other minor performance improvements

TCP improvements backported from Linux v6.8 - https://www.phoronix.com/news/Linux-6.8-Networking

sbitmap library backported from Linux v6.8

Several backports made to block subsystem to improve IOPS - https://www.phoronix.com/news/Linux-Caching-Time-Block-IO
[Asus Zenfone 9] arter97:
r5 is up.

It includes a major change in RCU by Google that improves power consumption.

r5

Backported lazy RCU to improve power consumption

Switched to LLVM 18.1.1 compiler

Wi-Fi drivers updated to 2.0.9.21U

KernelSU v0.8.1 merged

LA.VENDOR.1.0.r2-09300-WAIPIO.QSSI13.0 merged

Other minor bug fixes and changes from Google
[Asus Zenfone 9] svenagain:
Bluetooth results in fatal crashes with the latest omnirom ><
[Asus Zenfone 9] briank6932:
@svenagain I experienced a good number of problems with OmniROM and this kernel as well r5

Crashing apps due to inaccessibility of their own `/sdcard/Android/data/<package name>` dirs · Issue #4 · arter97/android_kernel_asus_zenfone9

For some reason lots of apps are complaining about a lack of access to their own /sdcard/Android/data/<package name> dirs, after updating to omni-14-202403121645-zenfone9-GAPPS. This causes tons of...

github.com

Infrequent random freezes followed by a shutdown · Issue #3 · arter97/android_kernel_asus_zenfone9

Didn't have this before installing the kernel, it's very infrequent (~once a day), but sometimes the OS just freezes, and then turns off after a minute or so. There's no correlation with high load ...

github.com

Power button and fingerprint reader can be unresponsive · Issue #1 · arter97/android_kernel_asus_zenfone9

Sometimes it's ok, but a lot of the time you have to try multiple times to get any activation/read. Particularly when holding the power button to get the power menu. ROM: omni-14-202403121645-zenfo...

github.com
[Touch Pro, Fuze General] TomasNM:
Hello.

Is there a way to disable autorotation to landscape while sliding keyboard out? It is very annoying for me,because it takes ages to write few words in ICQ(for example).

Also I want to keep the power-on function using keyboard out.

Thanks.
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] INCENDIOCODM:
<Moderator Edit>:

Thread closed and content removed! - @roirraW "edor" ehT
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] INCENDIOCODM:
Thanks !!

The dono that people gave made this possible 🌚
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] ZG_DEV:
Bro can u join my team for developing a rom for oppo a5s ?

All details are here : Click here
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] Varkos:
Amazing ROM and experience. Smooth and responsive. For the week I've had it there has only been one but, more of a visual glitch really, that kind of mixes up the 'recent' apps preview when closing the most recent one.

One thing that i noticed just today is that this does not have the multi audio output via Bluetooth that MIUI had and i kinda' used to use it. Will that be patched in or will it never be a thing?
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] Varkos:
So two weeks in and i have some opinions;

1. The ROM itself has kept up being smooth and flawless when using and navigating. Everything that you expect it to do visually and every effect works as it should.

2. This one is a big problem for me. For some reason after the first week the battery optimization just stopped working all together, or so it seems. I now am barely able to get home before i dip below the 20% while after the 3rd to the 6th day it was around 30-35%.

3. WiFi auto connect does not work when returning home or to any often visited location like work.

4. Gaming on this is excelent.
[Xiaomi Mi 11i / 11X Pro / Redmi K40 Pro+] Varkos:
BIG PROBLEM. NEED HELP

As of a few hours ago 'Contactless payments' have stopped working.
[Samsung Galaxy Tab A8 (2021)] fitrockx:
Hello, has anyone been able to boot a gsi on their x200 running X200XXS3CWG2 firmware?

I have tried flashing a few and none boots.
[Samsung Galaxy Tab A8 (2021)] kevinco1:
Yes, I've been on it for a few weeks and have had no issues. Are you flashing the stock recovery right after the GSI?
[Samsung Galaxy Tab A8 (2021)] fitrockx:
Can you share what TWRP version are you using and the GSi build you are running without issues? I would like to try it. Yes, I have installed stock recovery (through Odin) after GSi but still no luck.
[Samsung Galaxy Tab A8 (2021)] kevinco1:
The version posted in the TWRP thread and the GSI list is based off test results from using WG2.

When are you getting a bootloop exactly and which GSIs are you having trouble with. And to confirm is the recovery you are flashing the one that was extracted from the WG2 firmware? That must match
[Samsung Galaxy Tab A8 (2021)] Maxim-Root:
can you please send me a link to this Twrp I will be very grateful
[Samsung Galaxy Tab A8 (2021)] kevinco1:
[RECOVERY][UNOFFICIAL] TWRP 3.7.0 for 2021 Galaxy Tab A8 10.5 [SM-X200]

Notes: What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet. This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you...

xdaforums.com
[Samsung Galaxy Tab A8 (2021)] Maxim-Root:
I used this Twrp but when I tried to install gsi my sm-x205 went into a bootlap and loaded Twrp. with an error
[Samsung Galaxy Tab A8 (2021)] Maxim-Root:
sir, if it’s not difficult, please write detailed instructions on how to properly flash my Sm-x205 device and how to fix the error, I will be very grateful
[Samsung Galaxy Tab A8 (2021)] kevinco1:
Pretty sure the version in the header is an older one that might not be compatible anymore if you're on newer firmware. If you glance through the thread there should be a newer release to use instead
[Samsung Galaxy Tab A8 (2021)] TheStylus5Gmodder:
Flash the stock recovery after flashing the ROM.
[OnePlus 9 Pro] spiramedia:
I know it is not good to ask, but. Can someone help me to build PE13 for our device? I have a powerfull PC with Linux enviroment on Windows 10. Sorry for asking this, but I can't use OOS. And I bought the 9 Pro without verifying the PE rom availibility.
[OnePlus 9 Pro] netboost:
https://xdaforums.com/t/rom-official-oos-cam-black-iron-rom-v3-4-android-13-0-lemonadep.4595245/

Check this.
[OnePlus 9 Pro] spiramedia:
i want clean pixel rom, with little customization, like pe+ version. that is why i wanna try to build pe rom
[OnePlus 9 Pro] Z-Blade:
I have no idea how to build a custom rom but I would say Google and YouTube will be the best place to start to learn. I did you a favour and had a quick look:

https://wiki.pixelexperience.org/devices/martini/build/ - Not the same device but its a start

- again not for your device but its specific to PE

https://www.youtube.com/playlist?list=PLQcIdsw6jRy2Et-TES3BVitOQKx733WkG - A playlist for Intro to Custom Rom

Good luck.
[OnePlus 9 Pro] spiramedia:
Dear devs! please try to build PE for our device. I just don't have enought knowledge to build roms. A14 source of PE are out now.
[OnePlus 9 Pro] RexSonic:
Would be nice to have pe for this device
[OnePlus 9 Pro] spiramedia:
i tried building, ended up dead ubuntu. then tried in linux enviroment for windows. i killed windows. that is why my knowledge is very low at this point.
[Lenovo Z6 Pro Questions & Answers] georgar:
Hi there,

I want to unlock the boatloader (to install TWRP). So I go to the zui website (https://www.zui.com/iunlock) and fill in all the required details.

After the popup (ok, send the mail with the file) I wait for the mail with the file. I have been waiting for 5 days now, tried different email accounts and checked the spam folder.

Is the unlock website still working? Or is there another way to get the file or unlock the boatloader?

Thanks in advance for any help!

Kind regards

George
[HTC Vox] frauhottelmann:
Well, I don't think it belongs here, but anyway:

Merry Christmas to all of you!

:D
​
[HTC Vox] FeareX:
Thx, and the same to you frauhottelmann! And merry christmas to everyone else on the forum too!!
[HTC Vox] birdibird:
Thank you!!!

The same from me,

a great christmas and a very good 2009!!!!!

greetz from Porto :)
[HTC Vox] liamhere:
merry christmas

all you vox users :)

all the best for 2009
[HTC Vox] BjarniMaron:
Merry christmas to everyone here!

Greetings from Iceland :D
[HTC Vox] tipu2185:
Merry Christmas to all and have a wonderful 2009. :cool:
[HTC Vox] Dom_LC:
Merry Christmas to all Cookers and Testers!

Thanks again for all your great job:D!!
[HTC Vox] parthabhatta:
:) Merry christmas to all members and a wonderful and very happy 2009 :)
[HTC Vox] Hakem:
Merry Christmas!
[HTC Vox] matrix77:
Merry Christmas to all!
[HTC Vox] Addicted2xda:
Marry Xmas and a happy new to all the members of this GREAT community.
[Samsung Galaxy Tab A7 Lite] rohitrss:
I was flashing stock firmware using Odin but it stuck/failed at "Only official released binaries are allowed to be flashed : super" error. Now every-time I am trying to boot into system I am getting "an error occurred while updating the device software" error.

How can I unbrick this T225 if all I have access to is Download Mode. Odin flash giving same error I mentioned above.
[Samsung Galaxy Tab A7 Lite] tom.android:
please show your download mode
[Samsung Galaxy Tab A7 Lite] rohitrss:
I have attached the screenshots.