Spiteful Kernel 21/06/2025
Downloads (alternative gh release)
Changelog and info
⚠️Disclaimer
"Sorry for the wait"
Downloads (alternative gh release)
Changelog and info
⚠️Disclaimer
The Best Years Of Our Lives
Spiteful Kernel 21/06/2025 "Sorry for the wait" Downloads (alternative gh release) Changelog and info ⚠️Disclaimer
This media is not supported in your browser
VIEW IN TELEGRAM
This media is not supported in your browser
VIEW IN TELEGRAM
Spiteful Kernel 31/07/2025
Downloads (gh release)
Changelog and info
⚠️Disclaimer
"Came at an inconvenient time?"
Downloads (gh release)
Changelog and info
⚠️Disclaimer
I am going to ignore all issues regarding charging, because the more I see what peeps report about "worse charging", the more I realise the cases are individualized and not reproducible
Cases including:
* Not using original cable/adapter
* Faulty cable/adapter
* Thinking it's consistent 33w charging. It never was, even in stock it wasn't constantly 33w
* Temperature differences and not charging the phone in a cool environment.
Cases including:
* Not using original cable/adapter
* Faulty cable/adapter
* Thinking it's consistent 33w charging. It never was, even in stock it wasn't constantly 33w
* Temperature differences and not charging the phone in a cool environment.
Hi, I'd like your feedback and opinions as I'm here to address the elephant in the room, the battery life.
You see, currently, Spiteful is a performance-oriented, battery-eating kernel but it wasn't intended to be that way, I may have lost the plot trying to achieve smoothness no matter what. It's because I already have a terrible battery that'll need to be replaced eventually and I just didn't care anymore about battery life.
And that's the problem, I got so carried away trying to achieve good smoothness no matter how much more battery consuming that would be, that I ended up making the kernel accidentally performance-oriented.
As such, on the next update, Spiteful will take a complete 180 degrees and will be as much battery conversing as possible with some minor sacrifices to performance to achieve a balance between smoothness and battery life.
I'll also give what you guys request such as
* KSUN and SUSFS instead of RKSU and no SUSFS
* Bypass charging
* ??? - You guys tell me 🙏
As for those who liked the performance aspect, fret not, from this point, there'll be a divergent version of Spiteful called Longtail that will be the performance-oriented kernel as advertised and intended. Longtail will not be posted in the sweet global channel and exclusively only posted on here @tbyool so stay tuned!
You see, currently, Spiteful is a performance-oriented, battery-eating kernel but it wasn't intended to be that way, I may have lost the plot trying to achieve smoothness no matter what. It's because I already have a terrible battery that'll need to be replaced eventually and I just didn't care anymore about battery life.
And that's the problem, I got so carried away trying to achieve good smoothness no matter how much more battery consuming that would be, that I ended up making the kernel accidentally performance-oriented.
As such, on the next update, Spiteful will take a complete 180 degrees and will be as much battery conversing as possible with some minor sacrifices to performance to achieve a balance between smoothness and battery life.
I'll also give what you guys request such as
* KSUN and SUSFS instead of RKSU and no SUSFS
* Bypass charging
* ??? - You guys tell me 🙏
As for those who liked the performance aspect, fret not, from this point, there'll be a divergent version of Spiteful called Longtail that will be the performance-oriented kernel as advertised and intended. Longtail will not be posted in the sweet global channel and exclusively only posted on here @tbyool so stay tuned!
The Best Years Of Our Lives pinned «Hi, I'd like your feedback and opinions as I'm here to address the elephant in the room, the battery life. You see, currently, Spiteful is a performance-oriented, battery-eating kernel but it wasn't intended to be that way, I may have lost the plot trying…»
Forwarded from Tricky Store OSS | Updates
Tricky Store OSS: A tricky of keystore they forgot to hide
Remember when someone said:
Translation: "Thanks for the PRs, I'll take it from here… behind locked doors."
- AOSP headers? Borrowed/License headers stripped.
- LGPLv3 library? Linked statically, license violated.
- "PRs welcome"? Sure — until it’s "all rights reserved."
So I built Tricky Store OSS:
- 100% FOSS (GPLv3 licensed)
- Clean rewrite, not “borrowed or forked"
- Same features, less sus
If your keystore hack locks the source along with your bootloader... maybe it’s time for OSS.
https://github.com/beakthoven/TrickyStoreOSS
Channel: @TrickyStoreOSS
Chat: @TrickyStoreOSS_Chat
Remember when someone said:
Due to the rampant misuse and the contributions received after open-sourcing being less than expected, this module will be closed-source
Translation: "Thanks for the PRs, I'll take it from here… behind locked doors."
- AOSP headers? Borrowed/License headers stripped.
- LGPLv3 library? Linked statically, license violated.
- "PRs welcome"? Sure — until it’s "all rights reserved."
So I built Tricky Store OSS:
- 100% FOSS (GPLv3 licensed)
- Clean rewrite, not “borrowed or forked"
- Same features, less sus
If your keystore hack locks the source along with your bootloader... maybe it’s time for OSS.
https://github.com/beakthoven/TrickyStoreOSS
Channel: @TrickyStoreOSS
Chat: @TrickyStoreOSS_Chat