Recognized Developer / Recognized Contributor
- Jan 2, 2011
Yes. You just have to reinstall the app, if you want to flash again, backup or restore a backup.
No, you're not supposed to remove the magisk module at all. If you remove it, there will be breakage in the background everywhere.
It's working correctly now, I think the issue was caused by a setting.Thanks for the quick reply, I'll get you the logcat & dmesg later today (I can just use Logcat Reader, right?), interestingly the issue only started after flashing June.
I'm using SparkOS, June build (spark_raven-userdebug 12 SQ3A.220605.009.B1 1655107403), latest June kernel, Spotify or YouTube Music, SBC/APTX, wireless headphones, streaming via WiFi (MP3)
you´re correct. enabling ttl spoofing support somehow slipped through in the 3.0.x releases. I´ll enable it for the next release.Is TTL Spoofing still enabled with v3.x? I use EXKM to set TLL as described in post #436. With v2.4.0 and all the others I've tried before it, TTL spoofing works great. However when I flash 3.0.0 or 3.0.1 and reboot the EXKM script fails with errors that --ttl-set and --hl-set are invalid options. I flash back to 2.4.0 and reboot and it works again.
You can reduce max powerdraw by using CleanSlate battery saver feature accessible via CleanSlate config app.
Power saving mode is not that. Let's say we have TDP 5 w and the phone gets very hot in some applications. And if you reduce TDP, for example, to 4.8 or 4.6, then throttling will come earlier and will not heat up the phone as much.
In a way it is.
The article mentions there are no details on the exploit yet as far as i read it. So how should I know?Hey @Freak07, is this already patched in your kernel? https://www.androidpolice.com/pixel-6-galaxy-s22-kernel-vulnerability-raviole/
Or can it be patched for the next update? No pressure, just wondering if we need to wait for Google to patch it or not.
No, I have no plans to support A13 beta. It will be supported once it´s stable. I don´t have the time, desire and motivation to support it.
Thanks for reporting back! Enjoy the ride!
Yeah that sounds like this is your issue. I´m fairly certain the phenomenon you´re describing isn´t caused by the kernel as I´d have been affected too and I sign in to different apps from time to time too.I have a Pixel 6 pro. Decided to root and install this kernel after the release of 3.0.17. 1. I tried using KernelFlasher Alpha 06 and it resulted in a bootloop. I successfully recovered and used FKM to flash and everything worked fine.
Notes on performance: In general, I believe this kernel provides a more responsive interface and lower battery use during idle, but I don't have any testing to prove it. I will note that, perhaps because I enabled DNS over HTTPS in magisk, that the initial setup / install of apps seems to take a lot more time than I'm used to - specifically the initial log in/authentication. Twitch, for example, took about a minuteto go from the purple screen with logo to the initial login. Subsequent launches after initial setup for everything works as quickly (possibly faster) than expected. Does anyone else experience the same? Is it because I'm using secure DNS in magisk?
Thanks again for all your work. I've lurked on this forum for months, and your work helped me chose to buy this phone over a Samsung S22 ultra. I hope my only issues encountered so far help with further development. Let me know if there is any way to produce logs to document these slow initial launches / authentications.
ACC with the AccA GUI front end. I charge to only 75% too - I also don't usually let the battery go below 25%, and I very rarely fast charge.
1. No, there's no configuration available for this kernel. I want everyone to come here, read the release post and download the kernel from there. If there's anything to know, it's at least less likely to be missed.Hey I just flashed this with FKM a few days ago and it's been going great. I have 2 questions hopefully you can help me out with this.
1. FKM supports something called a kernel download configuration which will notify users of updates. Do you happen to have one generated?
2. Would I be able to perform OTA updates with this kernel installed? With magisk there's an option to install to inactive slot to preserve root after OTA, I'm not sure if all I gotta do is reflash the kernel once I update or do I need to return to stock kernel before OTA.
Thanks in advance
If no details regarding the exploit have been disclosed how would anyone know for sure?