yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Zeetaa:
View attachment 5330295

aRise Kernel X2 is here for Alioth!

Initial Changelog:

- Based on Lineage Kernel

- Upstreamed to 4.19.225

- Added WireGuard Support

- Introduced Simple Low Memory Killer(And Tweaked Them)

- crypto and x86 BACKPORTS and UPSTREAMS

- kgsl BACKPORTS (To match with Fuse)

- Use 100Hz tick Rate (300Hz its too much)

- Fix in some roms vibration doesn't work

- Some Idle optimizations

- Nuked Binder Logspams

- Ext4: Fsync: Optimize Double-fsync() a bunch

- Fixed in China Miui blobs based roms wif i not working

- Kill Userspace CPU Boosting entirely

- lz4: Removed unused functions

- Fixed Alioth not changing volume levels with Headphones on

- Add cpu7 Max frequency for Sd870

- locking/rwsem BACKPORTS

- UnderVolt 670Mhz

- Introduced Dynamic Stune Boost

- Introduced Stune Assist

- Reduced alot of Latency (Smoother)

Downloads:

Download

Support Group

JOIN HERE <-- Discussion group for support

Credits:

- Thx to SM8250 https://github.com/xiaomi-sm8250-devs/android_kernel_xiaomi_sm8250 for source

- Thx to all testers

​

XDA:DevDB Information

neXus Kernel, Kernel for Poco F3

Contributors

Zeeta

Source Code: https://github.com/xiaomi-sm8250-devs/android_kernel_xiaomi_sm8250

neXus Source: https://github.com/NotZeetaa/android_kernel_xiaomi_sm8250

Version Information

Status: STABLE

Current Stable Version: Public Stable 1

Created 2021-11-20

Last Updated 2022-01-18
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] ale82to:
first of all I wanted to thanks the developer of this kernel because it solves one big issue I had with other kernels with android system suspend eating battery for no reason after stand by .

having said that unfortunately one bigger (old issue )i originally had with lineage OS provided kernel come Back with arise kernel :

i use xposed edge pro app wich can launch app or execute action by long pressing the very left /right edge of the screen (also top or bottom but them work just fine ).

with both arise and lineage kernel long pressing the very righ /left edge of the screen almost never work{unless I slitghy move from the frame of the phone }(with drunk kernel/baalm kernel long presses are registered just fine ).

I do know it may seems a stupid,personal problem but I ve used that app for literally ages and it's very hard to not be able using long press on the left /right edges .

I think it may be a very simple pref to avoid accidental touches in arise kernel that can even be toggled with a shell command ,can anyone please help ?

thank you very much !
[General Questions and Answers] srkoi:
I Need to unlock my Sony Ericsson w580i,,how would i do that,,please help me

I am a newbie and sorry if i posted in the wrong section
[General Questions and Answers] bigb252:
Hi, you have to use a program like SEToolLite2 or XS++. When you plug in your phone, it tells you a bunch of software-related stuff. If you need more help just pm me. I'm always on another phone forum too -hint- Canadian phone forums beginning with an H.
[General Questions and Answers] vannasack:
me 2

trying to unlock the same phone...need help
[General Questions and Answers] -PiLoT-:
try asking in the questions and answers forum
[Google Pixel 6 Pro] tbalden:
Changelogs:

1.1.0 - initial public release

Beta program join process:

To use the premium apps with Pixel6pro, you need to join the Beta program on Play Store for the Premium app:

View attachment 5463887View attachment 5463889View attachment 5463891

View attachment 5463893View attachment 5463895View attachment 5463897
[Google Pixel 6 Pro] wanttotree:
Oh my gosh! Here we go mate!
[Google Pixel 6 Pro] Lughnasadh:
Been waiting for your arrival 😃🙌

Thank you!
[Google Pixel 6 Pro] Lughnasadh:
Everything went great on first flash! No problems and very clear and succinct directions. Thanks again!!!
[Google Pixel 6 Pro] s3axel:
Thank you, that's great news to see you and your excellent kernel here (y)

Just a possibly stupid question: is flashing only the cleanslate boot.img (eg within Exkm kernel manager) sufficient when already rooted ?

Or do you really need all those other images as well?....

Thanks, Axel
[Google Pixel 6 Pro] galaxys:
Nice to see you here! Kudos
[Google Pixel 6 Pro] DespairFactor:
you need the other images, he has modifed modules to make some of the other features work
[Google Pixel 6 Pro] Jiggs82:
Hey @tbalden glad to see you in 6pro forums 😁🙌🏻 quick question tho can I install this kernel over the kirisakura kernel or do I need to flash stock kernel first? Thanks
[Google Pixel 6 Pro] tbalden:
Thanks for testing and the quick feedback. 👍👍
[Google Pixel 6 Pro] tbalden:
It's enough to flash over it but flash the stock dtbo image as well in the process.
[Google Pixel 6 Pro] tbalden:
Yes, just as @DespairFactor mentions, each image is needed for all the features.

Modules are not built into the boot image for a lot of things, like touch driver, haptics, camera and now most builds follow Google's gki build strategy, otherwise it would be overly complicated. So the features need those images. 👍👍
[Google Pixel 6 Pro] Jiggs82:
Great! Thanks for the quick reply you're the best bro 💪🏻
[Google Pixel 6 Pro] bs3pro:
will this work on oriole??
[Google Pixel 6 Pro] tbalden:
No, features won't. It starts but the features will not work because of the differing modules. I'm looking yet into that if it's possible to make it work
[Google Pixel 6 Pro] bs3pro:
Ugh, bummer. Thanks
[Google Pixel 6 Pro] roirraW "edor" ehT:
Wow! I *may* have installed CleanSlate on one of my previous old phones years ago - I don't remember, but this is awesome! I feel like a kid in a candy store. Love DT2S and the long-press notification shade is awesome too.

The optional location profiles is neat, too.

For my own preference, I disabled the Battery Saver Touch Limiting as it was taking far too long or just not working to recognize that I was trying to use the fingerprint reader. Edit: I turned aodNotify's experimental option for Power saving mode, to completely disable AOD when aodNotify doesn't need it, and it seems this was the culrpit. If anyone else switches it off after reading this, I recommend you reboot right away because after I locked the screen, the touch screen was no longer responding at all. I had to hold the power button in for 30 seconds to reboot. Now it's working as expected.

To be clear, with aodNotify's experimental low power option disabled, I was able to turn CleanSlate's Battery Saver Touch Limiting back on - as disabling that didn't help with aodNotify's problem anyway. 🤣

Thanks! Bought both premium apps.
[Google Pixel 6 Pro] tbalden:
Thanks for the feedback and support! Much appreciated 👍
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! OT: My mother was from Budapest - left when the Germans came.
[Google Pixel 6 Pro] tbalden:
Re OT: Those times better left in the past, remembered to learn from past mistakes. Luckily Budapest is wonderful these years.

Good to see you around, I think I recall seeing you a few years back indeed. 👍👍

Good devices lure in same minded people time to time. I really enjoy p6pro. 😎
[Google Pixel 6 Pro] rogosteve:
Does double tap to sleep work on the lock screen?
[Google Pixel 6 Pro] tbalden:
That's a good point there. Actually I rarely use it there, and I've just checked if it works.

And it's not straightforward, right now it only works the first time, but after that until you unlock it won't.

I'll have a look at this, it could be made working for all cases, but some code is there related to pixel 4 process where lock screen caused some trouble when doing that on the lock screen.
[Google Pixel 6 Pro] TrustAugustus:
Interesting! I -only- use it on the lockscreen. 8 like to tap to check time, notifications, and then put it to sleep again :)
[Google Pixel 6 Pro] tbalden:
Well, actually I have to add that what I detailed above happens only when using AOD lock screen.

Without AOD,dt2s and s2s both work every time.
[Google Pixel 6 Pro] rogosteve:
Thank you.
[Google Pixel 6 Pro] tbalden:
- Update Android SP1A A12 - 1.2.2 -​

Android S stable - December

- December sec update - google sources

- adblock hosts file updated

CleanSlate S 1.2.2 Downloads:

Android S images zip (sp1a 2021-12-05)

Pixel6/pro (not flashable, contains images) CS 1.2.2: https://www.androidfilehost.com/?fid=17825722713688250034

vbmeta inside the zip of SP1A.016 to deactivate verity checks on the custom boot image and most probably to do factory reset, DO IT BEFORE FLASHING THE KERNEL, or it won't boot

You can try to deactivate the vbmeta check before the first booting up right after sideloading the OTA , maybe that will let you boot without factory reset after vbmeta verify disabling.

Deactivate, you might need to factory reset if you don't follow the OTA-update/disable-before-first-boot procedure (fastboot -w for factory reset)

fastboot flash --disable-verity --disable-verification vbmeta stock-vbmeta-211205.016.img

How to re-activate if you need later?

fastboot flash vbmeta stock-vbmeta-211205.016.img

Read first post in thread for installation details.
[Google Pixel 6 Pro] jac0b:
If you are already updated to the December OTA. Do you have to flash all the files or can you just flash the kernel image? I am rooted as well.
[Google Pixel 6 Pro] Lughnasadh:
You need to flash all the files as he has modified them from stock to make some of the features to work.
[Google Pixel 6 Pro] Israafil:
Will there be an option to enable hbm mode in the near future??
[Google Pixel 6 Pro] tbalden:
It's on by default on stock, triggered by bright light conditions.
[Google Pixel 6 Pro] Israafil:
I meant manual toggle, where i can enable it indepently from light condition like it was possible with the pixel 4. I use the app high brightness toggle and it allows manuel activate hbm the issue with the app is activating hbm overrides all other brightness level so you can't change brightness when hbm is enforced. Thought hbm like pixel 4 wh when brightnes slider is maxed, hbm would kick in ndependently the light conditions.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You can do so now with https://play.google.com/store/apps/details?id=flar2.hbmwidget
[Google Pixel 6 Pro] Israafil:
That is the app i am using currently, as i sad has some issues.
[Google Pixel 6 Pro] scott.hart.bti:
@tbalden what's up man! Glad to see your work here in the p6p world. Not sure if you remember me... Helped test one of the recent OnePlus devices a while back (think the 7?). Looking forward to flashing.
[Google Pixel 6 Pro] tbalden:
Hey there 😄 welcome to the pixel 6 pro. Yes indeed, I remember well, on the op8 we were testing a lot before it was stable enough. I hope you enjoy the new phone 🤠

Here I'm really happy with it, except for some glitches on the software side by Google. It's strange, I never had this many UI glitches, lags before. Like it's slow to turn off the screen sometimes, and also rarely have an added layer which is empty and have to press a back to get to the normal app/UI.. very weird. Only present on p6, not on p4/p5.
[Google Pixel 6 Pro] tbalden:
Hey there folks. Just a heads-up, what I'm working on the p6pro.

With the switch to Google tensor system on chip, and its kernel , it seemed impossible to access the camera led for notification features from kernel. But recently I discovered how io control thru kernel is used to switch it on and off. I've been doing reverse engineering to see what's to do to use it and it seems to work out.

Here's a small demo, how it looks on p6pro as of now. Testing and all, next release should have it as an option. :)
[Google Pixel 6 Pro] tbalden:
Another good news, Face down screen off support is now back without the 60FPS issue on pixel 6/6 pro's proximity sensor.

The detection is now modified to use the magnetic rotation sensor of the device, while screen is on. This is a low energy sensor. When a certain inclination is detected for a relatively longer period, proximity sensor is used to check for surface proximity one time. If it is close, face down screen off can be triggered.

Both config app and companion app are being rolled out to play store. Going to update the kernel zip as well soon for all these.
[Google Pixel 6 Pro] tbalden:
- Update Android SP1A A12 - 1.3.0 -​

Android S stable - Features

- Feature: Flashlight notification setting is now added for p6/6pro (needs new config app)

- Feature: Notifications reminder setting is added for p6/6pro (needs new config app)

- Feature: companion app now fixed to support Facedown detection while screen is on (without 60fps issue)

- adblock hosts file updated

CleanSlate S 1.3.0 Downloads:

Android S images zip (sp1a 2021-12-05)

Pixel6/pro (not flashable, contains images) CS 1.3.0: https://www.androidfilehost.com/?fid=17825722713688265368

vbmeta inside the zip of SP1A.016 to deactivate verity checks on the custom boot image and most probably to do factory reset, DO IT BEFORE FLASHING THE KERNEL, or it won't boot

You can try to deactivate the vbmeta check before the first booting up right after sideloading the OTA , maybe that will let you boot without factory reset after vbmeta verify disabling.

Deactivate, you might need to factory reset if you don't follow the OTA-update/disable-before-first-boot procedure (fastboot -w for factory reset)

fastboot flash --disable-verity --disable-verification vbmeta stock-vbmeta-211205.016.img

How to re-activate if you need later?

fastboot flash vbmeta stock-vbmeta-211205.016.img

Free app versions:

(Premium playstore versions are also rolling out right now, Google is approving them...)

Config app 3.2.3: https://www.androidfilehost.com/?fid=17825722713688265360

Companion app 3.3.4: https://www.androidfilehost.com/?fid=17825722713688265361

Read first post in thread for installation details.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi! Thanks for the update. I take installation directions at face value, but I wanted to explicitly confirm with you anyway. Verity and verification still need disabled even when using with Magisk Canary 23016 (which itself doesn't require verity and verification disabled any longer)?

I've been advising folks when they asked that they only have to disable verity and verification when using "some" custom kernels that haven't been updated. I mainly want to ensure what I tell others remains accurate, and for myself when I update to the latest version of CleanSlate.

Thank you!
[Google Pixel 6 Pro] tbalden:
Well, I'm not fully sure, but never dared to try either without this step, as on p5 it was causing inability to flash custom stuff without this step and also after ota update the verity setting caused that without factory reset it wouldn't boot again. I'm not sure about this on p6
[Google Pixel 6 Pro] roirraW "edor" ehT:
Fair enough, thank you! I may have to either wait for someone else with the P6/P to verify whether it's needed or not, or sometime when I have the time, perform some comprehensive backups and try my luck. :D Or just keep disabling them regardless.
[Google Pixel 6 Pro] bobby janow:
So according to Despair both his and this kernel should work with ProtonAOSP unrooted. Whether or not it will pass SN checks is quite another thing. I will do my backups as best I can and within a couple of days grab my bottle of Jack and install one of them. According to the OPs I do need to flash all those files. Do you suggest cleanslate or despair at this time? I'll read up on both but it does look like Despair is diligently working on some updates. Damn why am I always the guinea pig? A glutton for punishment I presume.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm using CleanSlate but if I was using a different one it would probably be Kirisakura. I haven't used Despair on the P6P but I'm familiar with it and have probably used it at some point on a previous phone (Pixel 1?). I'm sure they're all good.

In the end, if you're the guinea pig, it's because you want to be. :)
[Google Pixel 6 Pro] tbalden:
Working on new update, and fixing some touch gestures related bugs. Going to publish in a couple of hours.
[Google Pixel 6 Pro] tbalden:
- Update Android SP1A A12 - 1.3.1 -​

Android S stable - January update / fixes

- Update to latest google sources

- Fix: Touch Gestures feature bug: rare single tap detected as double tap issue

- Fix: Touch Gestures feature bug: touch input blocked issue when using gesture directly after FP unlock from AOD, until screen off/on cycle

- adblock hosts file updated

CleanSlate S 1.3.1 Downloads:

Android S images zip (sp1a 2022-01-05)

Pixel6/pro (not flashable, contains images) CS 1.3.1: https://www.androidfilehost.com/?fid=17825722713688269355

vbmeta inside the zip of SP1A.007 to deactivate verity checks on the custom boot image and most probably to do factory reset, DO IT BEFORE FLASHING THE KERNEL, or it won't boot

You can try to deactivate the vbmeta check before the first booting up right after sideloading the OTA , maybe that will let you boot without factory reset after vbmeta verify disabling.

Deactivate, you might need to factory reset if you don't follow the OTA-update/disable-before-first-boot procedure (fastboot -w for factory reset)

fastboot flash --disable-verity --disable-verification vbmeta stock-vbmeta-220105.007.img

How to re-activate if you need later?

fastboot flash vbmeta stock-vbmeta-220105.007.img

If you're using Magisk rooting and patch the boot image before flashing, then you can skip verity disabling. If you do not use Magisk patching, you should always disable verification when applying OTAs from adb sideload, before booting up!

Magisk with Kernel manager installation

If using a kernel manager like EXKM or FKM, here's an anykernel installer zip

Kernel installer zip 1.3.1 (use with EXKM,FKM): https://www.androidfilehost.com/?fid=17825722713688269397

Free app versions:

(Premium playstore versions are also up.)

Config app 3.2.3: https://www.androidfilehost.com/?fid=17825722713688265360

Companion app 3.3.4: https://www.androidfilehost.com/?fid=17825722713688265361

Read first post in thread for installation details.
[Google Pixel 6 Pro] tbalden:
Based on this https://xdaforums.com/t/kernel-clea...shlight-s2s-fingpr-9dec.4192641/post-86255733 and my own experience (tried it on this Jan update) so far I concluded (and edited the instructions), that

- if using Magisk Manager latest canary to patch boot image with magisk, and flash that, you won't need vbmeta verity/verification checking disabled

- if I'm using the boot image built in the AOSP build process, the boot image won't boot without verity/verification disabling beforehand.

So if using Magisk patching + latest canary it should be fine, as you detailed.

I still need to find a way to build a boot image with Google's AOSP build env that actually doesn't need this complication.
[Google Pixel 6 Pro] sagiag:
Hi im coming from stock january with rooted device , just done the rooted method include patching the boot img with magisk and i cant boot , its but into fastboot mode , any ideas ?
[Google Pixel 6 Pro] tbalden:
Are you on the latest magisk canary version? I can only imagine that maybe the boot image you try to flash from is the non magisk-patched original one from the zip?
[Google Pixel 6 Pro] sagiag:
Hi man

thank you for your respond ,

im download the zip from your post and than i copied cleanslate-raven-boot-220105.007--131.img to my device and patched it with magisk .

after that i flash it like you mention in the instruction .

am i wrong ?

thank you for your help!
[Google Pixel 6 Pro] sagiag:
OK i tried again and now i get your data may be curropted error
[Google Pixel 6 Pro] tbalden:
Have you pulled the correct patched image from sdcard/Download folder where magisk puts the patched image under magisk_patched-<randomname>.img ?
[Google Pixel 6 Pro] sagiag:
yes ofcourse i only have one file since i deleted the rest in order to avoid a problems
[Google Pixel 6 Pro] Lughnasadh:
Are you using Canary Magisk 23016? You never really answered that question.
[Google Pixel 6 Pro] sagiag:
yes bro i am
[Google Pixel 6 Pro] sagiag:
adb reboot bootloader

PS C:\adb\cleanslate-raven-images-220105.007--131> fastboot flash boot magisk_patched-23016_ipHwv.img

Sending 'boot_a' (65536 KB) OKAY [ 1.688s]

Writing 'boot_a' OKAY [ 0.077s]

Finished. Total time: 2.074s

PS C:\adb\cleanslate-raven-images-220105.007--131> fastboot flash dtbo stock-dtbo-220105.007.img

Sending 'dtbo_a' (16384 KB) OKAY [ 0.423s]

Writing 'dtbo_a' OKAY [ 0.061s]

Finished. Total time: 0.491s

PS C:\adb\cleanslate-raven-images-220105.007--131>fastboot reboot fastboot

Rebooting into fastboot OKAY [ 0.000s]

< waiting for any device >

Finished. Total time: 16.926s

PS C:\adb\cleanslate-raven-images-220105.007--131>fastboot flash vendor_dlkm cleanslate-raven-vendor_dlkm-220105.007--131.img

Resizing 'vendor_dlkm_a' OKAY [ 0.012s]

Sending 'vendor_dlkm_a' (43412 KB) OKAY [ 1.155s]

Writing 'vendor_dlkm_a' OKAY [ 0.351s]

Finished. Total time: 1.539s

PS C:\adb\cleanslate-raven-images-220105.007--131>fastboot reboot

Rebooting OKAY [ 0.003s]

Finished. Total time: 0.005s

PS C:\adb\cleanslate-raven-images-220105.007--131>

this is what i have done ,

its the third time i done it

i got the data curroption message

i didnt disable vbmeta
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm not an authority on this subject, but from what I've seen, once you've gotten the data may be corrupted error, you'll have to at minimum factory reset the device, or possibly use one of the following two and probably start from scratch:

Official Google Pixel Update and Software Repair

Official Google Android Flash Tool

Ignore that, read the next one.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you didn't disable Verity and Verification, then you should be only flashing the copy of the kernel that you ran Magisk on. I'm guessing you didn't do that since the filename of the kernel image would be different than that, unless you renamed it.

Flash the stock boot.img and run Magisk on the CleanSlate kernel, then flash the Magisk'd CleanSlate kernel.
[Google Pixel 6 Pro] Lughnasadh:
Are you using the latest Platform Tools (31.0.3)?

Have you tried doing it from command prompt instead of Powershell?
[Google Pixel 6 Pro] tbalden:
Thanks for the detailed info.

Did you flash it over stock partitions or over another kernel? Any magisk modules active?

I'm really sorry to hear that it doesn't work out. I'm doing exactly the same here when testing the compiled kernel.

(If you got the corrupted one, you might want to check in the Bootloader if the Active partitions is still A or B.

After a few bad boots it might switch to the other partitions. After that it might not boot on Stock images either.

You can switch active partitions from fastboot to try and see if it boots then. Or you might indeed need to factory reset/use stock boot image to make it boot again. )
[Google Pixel 6 Pro] tbalden:
To make it easier for those who use Kernel managers with magisk to flash kernels, I've created an AnyKernel for the Pixel 6 Pro (later I'll check the non-pro installer too).

Here's the Anykernel zip for P6Pro, Cleanslate 1.3.1 for kernel managers (exkm or fkm):

cleanslate-raven-1.3.1.zip | by tbalden for Pixel 6 Pro

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

www.androidfilehost.com
[Google Pixel 6 Pro] sagiag:
Hi thank you for your help!

First before I started to flash anything i copied the cleanslate boot img file to my device and patched it with magisk , In the download folder I got a new file that called magisk_patched-23016_ipHwv.img

Than I copy it back to my computer and flash it

After that I flashes the rest of the files like in the instructions.

Is that ok?