General [SHARED] [OSS] [MIUI] [KERNEL] newest sweet/in quantum, vantom, sleepy, yuki, delta, doraemon, kewl, aghisna kernel, another kernel, darkkernel

[aLcaTr4z]

moving over to the latest PixelOS

Would be nice when u drop an update about battery then with that rom.

 

[aLcaTr4z]

Oh well,... Just thought about: have ****ty battery life, lets try sleepy. But uff...



This doesnt feel right. Im kinda clueless but think that the Sweatcoin App could force the phone to keep awake,..

Only WIFI, no Sim Cards, no NFC, no Bluetooth. Havent touched the Camera ever since loading up to 100%. Basicly just a ipod. lol - Also was just laying around with zero use the last >8 Hours.

 

[Case_]

I've tried the Aghisna kernel, but my phone doesn't pass SafetyNet with it. I assume it has something to do with that kernelSu stuff someone mentioned?
Anyway, current sleepy works fine.

 

[BigChungus321]

I've tried the Aghisna kernel, but my phone doesn't pass SafetyNet with it. I assume it has something to do with that kernelSu stuff someone mentioned?
Anyway, current sleepy works fine.

Regarding the passing safety net, Google recently pushed an update that made it so that cts would require the correct device fingerprint to match before it passed. Meaning, custom roms with Pixel spoofing, or roms that use Pixel 6 Pro, Pixel XL to spoof the device to unlock exclusive pixel features can not pass safetynet. This has been a big issue recently, and many people are complaining about the push (possibly shifting to the new integrity api). So really, the issue is not with the addition of kernelsu. In fact, KernelSU (ksu) is a kernel-based root and no app can touch that, only another root (aka magisk) can, meaning that it can intercept (hide) itself from any app that calls su binary so it is well-hidden by default, at least as of now.
Anyway, there is a temporary fix to it, Displax made a modded safetynet fix that attempts to fix the cts issue, which can be found here:

GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

github.com

It's a magisk module so be sure to enable zygisk for it. If you have the normal safetynet fix module, be sure to remove it first.

 

[Case_]

@BigChungus321 No idea what is the actual cause of the issue, and I originally thought it might be due to some Google update, but purely swapping between the latest Aghisna kernel and the latest sleepy kernel makes the difference between not passing or passing SafetyNet. So it would seem there's at least more to it than just a Google update.

 

[Atrumitos]

@BigChungus321 No idea what is the actual cause of the issue, and I originally thought it might be due to some Google update, but purely swapping between the latest Aghisna kernel and the latest sleepy kernel makes the difference between not passing or passing SafetyNet. So it would seem there's at least more to it than just a Google update.

I installed Lineage OS 20 with Sleepy and for some reason, Wallet was not working from the get-go. It wouldn't let me add my cards. I figured I'd give magisk a shot with the module @BigChungus321 mentioned. After installing Magisk and the module, I was able to add cards and it seems to work with both Sleepy and Aghisna. Haven't tried using it to pay yet.

 

[Laptapper]

I've tried the Aghisna kernel, but my phone doesn't pass SafetyNet with it. I assume it has something to do with that kernelSu stuff someone mentioned?
Anyway, current sleepy works fine.

Regarding the passing safety net, Google recently pushed an update that made it so that cts would require the correct device fingerprint to match before it passed. Meaning, custom roms with Pixel spoofing, or roms that use Pixel 6 Pro, Pixel XL to spoof the device to unlock exclusive pixel features can not pass safetynet. This has been a big issue recently, and many people are complaining about the push (possibly shifting to the new integrity api). So really, the issue is not with the addition of kernelsu. In fact, KernelSU (ksu) is a kernel-based root and no app can touch that, only another root (aka magisk) can, meaning that it can intercept (hide) itself from any app that calls su binary so it is well-hidden by default, at least as of now.
Anyway, there is a temporary fix to it, Displax made a modded safetynet fix that attempts to fix the cts issue, which can be found here:

GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - GitHub - Displax/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

github.com

It's a magisk module so be sure to enable zygisk for it. If you have the normal safetynet fix module, be sure to remove it first.

I installed Lineage OS 20 with Sleepy and for some reason, Wallet was not working from the get-go. It wouldn't let me add my cards. I figured I'd give magisk a shot with the module @BigChungus321 mentioned. After installing Magisk and the module, I was able to add cards and it seems to work with both Sleepy and Aghisna. Haven't tried using it to pay yet.

Did someone tried this procedure?
For me it's working for cts, certified and banking...


Next time try to hide Magisk (MagSet is my hidden app) force deny list, all tics in google playstore and google services. All tics in banking apps (not only one, open the subfolder hit all) Then delete cache and data of google playstore and google services, reboot immediately to recovery and delete dalvik caches. Reboot in system.

 

[Atrumitos]

Did someone tried this procedure?
For me it's working for cts, certified and banking...


Next time try to hide Magisk (MagSet is my hidden app) force deny list, all tics in google playstore and google services. All tics in banking apps (not only one, open the subfolder hit all) Then delete cache and data of google playstore and google services, reboot immediately to recovery and...

I didn't have Magisk at all when the problem occurred. I installed Magisk with the module and followed that procedure you mentioned, in order to solve it Thank you for your clear instructions in the Lineage thread, btw!

 

[Case_]

Yeah, I take what I said back. Even though initially it seemed that reverting to sleepy made SafetyNet (Wallet, really) work again, when I tried to pay while shopping, Wallet didn't work and it's back to how it was.

So it really wasn't the kernel after all. Though no idea why it seemed to work for a while after swapping it.

Will try the CTS fix next.

 

[Laptapper]

Yeah, I take what I said back. Even though initially it seemed that reverting to sleepy made SafetyNet (Wallet, really) work again, when I tried to pay while shopping, Wallet didn't work and it's back to how it was.

So it really wasn't the kernel after all. Though no idea why it seemed to work for a while after swapping it.

Will try the CTS fix next.

Please try this first
Post in thread '[SHARED] [OSS] [MIUI] [KERNEL] newest sweet/in quantum, vantom, sleepy, yuki, delta, doraemon, kewl and aghisna kernel' https://forum.xda-developers.com/t/...kewl-and-aghisna-kernel.4398423/post-88171195

 

[BigChungus321]

A thing to note: there is no need to add Google Play Store to the denylist, as it is not detecting any root or abnormality. It is a common misunderstanding, and many people still add Play Store to their denylist (which, frankly, just adds to more checks on Magisk's side and increases consumption). As for Google Play Services, only gms and gms.unstable are needed to be added to the denylist to pass device integrity. Nothing more.

As for hiding the presence of root, well, Magisk does not do a good job at it. It's on the name, DENYlist. It only denies the root, not actually hiding it. So some of you might get the "device is rooted" message on some apps even though the app is on the denylist and the device passes the safety net. You could use shamiko magisk module to better hide the root but it's closed source. It could also be that the app is checking for any pixel spoofing, aka custom rom spoofs, and thus will prevent you from using the app even without root and a passing safetynet. At that point, the only option is to change the rom.

 

[Laptapper]

A thing to note: there is no need to add Google Play Store to the denylist, as it is not detecting any root or abnormality. It is a common misunderstanding, and many people still add Play Store to their denylist (which, frankly, just adds to more checks on Magisk's side and increases consumption). As for Google Play Services, only gms and gms.unstable are needed to be added to the denylist to pass device integrity. Nothing more.

As for hiding the presence of root, well, Magisk does not do a good job at it. It's on the name, DENYlist. It only denies the root, not actually hiding it. So some of you might get the "device is rooted" message on some apps even though the app is on the denylist and the device passes the safety net. You could use shamiko magisk module to better hide the root but it's closed source. It could also be that the app is checking for any pixel spoofing, aka custom rom spoofs, and thus will prevent you from using the app even without root and a passing safetynet. At that point, the only option is to change the rom.

For me in lineage20 and non additional Magisk module (with described procedure):

 

[Case_]

@Laptapper Yeah, I did actually try that (though I already had it set up like that, so it essentially meant deleting the cache/storage for the apps and dalvik cache), and pretty much the only thing this achieved was that the phone still didn't comply with SafetyNet, but my card was removed from Wallet

But noticing there was a new LOS 20 update, I then installed that instead of going for the CTS fix, and that made the phone compliant again (tested this time, paying with Wallet went fine). Might be that something was downgraded during the update and it's only temporary, but we'll see.

 

[ottili81]

@Laptapper Yeah, I did actually try that (though I already had it set up like that, so it essentially meant deleting the cache/storage for the apps and dalvik cache), and pretty much the only thing this achieved was that the phone still didn't comply with SafetyNet, but my card was removed from Wallet

But noticing there was a new LOS 20 update, I then installed that instead of going for the CTS fix, and that made the phone compliant again (tested this time, paying with Wallet went fine). Might be that something was downgraded during the update and it's only temporary, but we'll see.

Fixing safety net issue was a point of pulkits changelog for the latest build.

 

[Case_]

Good. I didn't find any changelog, but I wasn't trying that hard to find one, admittedly. Though the question of how long will it last still remains, which I guess depends on how he fixed it. Not that I'm doubting him, not in the slightest, it's just that that's the nature of any SafetyNet fix.

 

[OFProzo]

Aghisna Kernel is amazing man (using latest PixelOS here)

 

[fobtob387]

Aghisna Kernel is amazing man (using latest PixelOS here)

Yup I love it, 90hz is amazing.

 

[OFProzo]

Latest PixelOS + Vantom I don't know if this is good or bad

 

[aLcaTr4z]

Looks solid to me. Now i want to test PixelOS even more...

 

[StOrmCatz]

As it Looks like Sleepy kernel is no longer supporting SWEET (as per a post in Telegram), I've compiled the code with the last set of changes as of Feb 22, 2023.
The following changes/issues were made/addressed from the original code:
- ZRam set back to 2GB (it was increased to 3GB starting Scarlet Witch build)
- Fixed incorrect colours when using 120hz (issue in XXX build)

Notes for anyone who uses this:
- This is only for OSS
- Choose the file with ln8000 if your device has that charger
- This includes some updates and fixes from the last official XXX build
- I'm not liable for any issues/damage to your device