yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 20 X Questions & Answers] thinhdang6789:
Tks for ur reply. i have tried hisuite, it didnt work with Harmony 3.0. but i know for sure someone can do it. they asked for $18. that would be my last option. tks anyway
[Huawei Mate 20 X Questions & Answers] hyellow:
once, i've downloaded original firmware files that could be flashed through recovery. i might still have them, but it is only for evr-l29.

that might be your next best shot, finding the firmware files to downgrade through recovery.
[Huawei Mate 20 X Questions & Answers] zlaer:
What company can do that for you for $18?
[Huawei Mate 20 X Questions & Answers] rimkhan1:
Google Ministry of Solutions, he converted my Chinese to Global remotely. He is based in America
[Huawei Mate 20 X Questions & Answers] zlaer:
But with the current version?
[Huawei Mate 20 X Questions & Answers] rimkhan1:
yes, check with him. no harm contacting.
[Huawei Mate 20 X Questions & Answers] ivanox1972:
I think it can go just with newest hisuite, nothing paid there. To emui 11 Chinese. And for globalization, that is paid service. But I would think why to do that?
[Huawei Mate 20 X Questions & Answers] zlaer:
Why to do what?
[Huawei Mate 20 X Questions & Answers] ivanox1972:
to go china to global version
[Huawei Mate 20 X Questions & Answers] zlaer:
So you expect someone to travel to china to buy a phone?? Smh
[Huawei Mate 20 X Questions & Answers] ivanox1972:
now I realy dont understand you and your point. realy.
[Huawei Mate 20 X Questions & Answers] zlaer:
Ditto
[Motorola One Fusion+ Questions & Answers] mike713900:
I really want to update my os from 11, esp for security enhancements and features. But i also really want to use my Google assistant button. Anyone aware of any good custom os with it? I'm sick of Android 11.i need something that'll work with my phone.
[Motorola One Fusion+ Questions & Answers] nstark13:
Try the MYUI 5.0 port. It is built to function like stock and should give you similar mileage with all Moto goodies.

Here's the link to forum: https://xdaforums.com/t/rom-android-13-myui-5-0-stock.4548101/

Or you can also try statixOS, it gives more of a Pixel experience vibe.

All of these are on A13 with latest security patches
[Motorola One Fusion+ Questions & Answers] mike713900:
I'm trying the LineageOS. its the only site thats giving me clear instructions and how-to
[Google Pixel 7 Pro] Sultanxda:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/

This is a no-frills custom kernel for the Pixel 7, 7 Pro, and 7a. It is designed to be used with the stock Android 14 ROM and custom Android 14 ROMs. It's intended to be a simple replacement for the stock kernel that brings several under-the-hood enhancements. This kernel is not meant to be customized by users.

This kernel works with dm-verity/verification enabled! You don't need to disable verity or factory reset to use this kernel.

Changelogs for each update can be found in the 2nd post of this thread.

Features:

Works with dm-verity/verification enabled

Capacity Aware Superset Scheduler (CASS), a custom CPU scheduler that improves battery life and performance

Tensor AIO, a custom DEVFREQ driver that dynamically controls RAM speed for better battery life and latency

Simple LMK, a custom low memory killer that improves memory management

Improved thermals, so the device runs cooler

Improved single-core and multi-core CPU performance, especially when the CPU is thermal throttled

Improved idle battery drain when the device is in deep sleep

Improved touch latency

Improved GPU and gaming performance

Improved stability: fixed dozens of random reboots, freezes, memory leaks, and performance bugs which exist in the stock kernel

Compiled with GCC 13.2 and Link Time Optimization (LTO)

Many other advanced improvements not listed here

Source code:

Android 14: https://github.com/kerneltoast/android_kernel_google_gs201/tree/14.0.0-sultan

Credits:

Over 100 beta testers who helped make this kernel stable

osm0sis (for AnyKernel3)

If your name should be here and it isn't, then let me know

Installation instructions:

You can flash this kernel in any kernel manager app, such as Franco Kernel Manager, EX Kernel Manager, and Kernel Flasher.

Sideloading in a custom recovery such as LineageOS Recovery isn't currently supported, but support will be added in a future update.

Telegram group:

https://t.me/sultanskernel

Downloads:

Latest kernel
[Google Pixel 7 Pro] Sultanxda:
Changelog:

May 12, 2024:

*Updated to May security patch

*Updated to Linux 5.10.212

*Added Tensor AIO, a custom DEVFREQ driver that dynamically controls RAM (improves battery life and latency)

*Improved performance in Unity-based games such as Wild Rift

*Fixed random reboots when the device boots up

*Fixed a significant memory leak in the Broadcom WiFi driver

*Fixed high power consumption when the CPU is throttled

*Fixed high power consumption during video playback

*Improved fluidity when the CPU is heavily throttled

*Fixed poor performance during heavy multi-core workloads

*Improved CPU energy efficiency by wiring CASS deeper into the scheduler (CASS now manages real-time processes)

*Fixed several issues in SBalance, my kernel-based IRQ balancer (improves performance)

*Made several improvements to CPU idle (improves battery life)

*Improved the CPU governor to select better CPU frequencies (improves battery life and latency)

*Made the scheduler aware of the CPU's DynamIQ technology (improves battery life and performance)

*Increased the minimum RAM frequency from 421 MHz to 546 MHz (improves battery life and performance)

*Fixed Play Integrity failures due to the kernel's name

Old changelogs:

October 20, 2023:

*Added support for Android 14, including the current QPR beta

*Fixed random reboots, freezes, and screen not turning on sometimes, all caused by a 2-year-old Google bug in the Emerald Hill zRAM driver

*Further improved idle battery drain

*Removed all of Google's Pixel scheduler additions, improving responsiveness and battery life

October 4, 2023:

*Fixed device not waking up sometimes, caused by the Emerald Hill optimizations introduced in the September 13 build

October 3, 2023:

*Updated to September security patch

*Disabled PREEMPT_RT due to stability issues and slightly higher battery drain

*Overhauled the scheduler for significantly improved multi-core performance and battery life (Geekbench 6 result)

*Fixed several issues caused by a memory management bug when available memory was low

*Fixed a major bug that caused Pixel 7 and Pixel 7 Pro to not use the correct thermal management settings, which hurt overall performance

September 17, 2023:

*Fixed random reboots caused by a bug in the Emerald Hill enhancements from the previous build

*Fixed GPS randomly dying and requiring a reboot in order to fix it

*Fixed random reboots on custom ROMs which use EROFS

*Fixed bugs in the EAS scheduler enhancements, improves overall performance

September 13, 2023:

*Significantly improved the Emerald Hill zRAM offload driver's efficiency and speed. Improves overall performance when RAM starts to get full, or after the phone reaches a few hours of uptime.

September 3, 2023:

*Initial release
[Google Pixel 7 Pro] Sultanxda:
Reserved
[Google Pixel 7 Pro] krakout:
Ooh interesting!
[Google Pixel 7 Pro] Fishawy:
I think 7 months of Sultan's kernel was the longest period I ever beta-tested something 😄

Congrats on the release, finally!
[Google Pixel 7 Pro] krakout:
Ahhh darn just noticed it's 13 only... Any chances for 14 support down the road?
[Google Pixel 7 Pro] GabbaGandalf42:
Incredible work, giving my p7 around 9-12h of sot depending on usage. Also heat is not a problem here anymore. Sensational.
[Google Pixel 7 Pro] ada12:
Amazing work , will re-compile it for pixel 6/6pro
[Google Pixel 7 Pro] w_tapper:
am hyped for a 6 series version, but from what ive heard you cant just recompile it for 6 series, it wont work without editing some stuff in the kernel source first
[Google Pixel 7 Pro] ada12:
I know need regenerate defconfigs in minimum, for google modules I looked it's same it's will be no hard to port

For EAS need recalculate for gs101 soc also by freqbench of sultan
[Google Pixel 7 Pro] HipKat:
Definitely a major plus for the heating issue.

That alone makes this a great kernel!
[Google Pixel 7 Pro] halfbytecode:
Thanks for all the hard work, and sharing it here on XDA!
[Google Pixel 7 Pro] murphyjasonc:
Just downloaded and installed. I've been waiting for a Kernel that doesn't need Verity disabled. Just for curiosity is how you got around needing dm-verity disabled specific to this kernel or is it something other developers can use in the future? Either way Kudos for figuring it out! If this reduces my phone overheating I'll be overjoyed. Nothing worse than taking pictures outside and having phone overheat after a couple minutes. I've been using your Kernel for years and have missed it on my 7 Pro. Thanks for all your hard work and time invested @Sultanxda !
[Google Pixel 7 Pro] Paz9:
Thank you for this great kernel, been a while since I used one of yours!
[Google Pixel 7 Pro] Not_Purgatory:
If I remember correctly - Sultan made it possible by getting rid of the GKI stuff, if I am not mistaken?
[Google Pixel 7 Pro] binoysankar:
Thanks for bringing in the kernel. Few queries from my side.

1) Currently i am using another kernel for which i had disabled dm-verity/verification. Do i need to enable it to flash this kernel again or can i flash this kernel by having these disabled already?

2) Can I flash it on top of the existing custom kernel or need to be first on the stock kernel then flash this kernel.
[Google Pixel 7 Pro] dmbardal:
Just flash it as any other kernel through a kernel-flasher like FKM, EXKM etc.

Doesn't matter that you've already disabled verity/verification. I always do no matter what.

I've also flashed it on top of a few different kernels (that have required verity/verification disabled), and haven't encountered any issues.
[Google Pixel 7 Pro] Daihogo:
Without root on a custom ROM i cant flash this kernel, right?
[Google Pixel 7 Pro] Techboyz97:
Unfortunately I flashed A14 beta 3 weeks ago. I can't wait to test this kernel A14 variant!!
[Google Pixel 7 Pro] Locoman_:
You do need root.
[Google Pixel 7 Pro] chrisz5z:
Franco, EX, or Kernel Flasher will work fine.

If you bootloop you can just flash the stock boot.img, dtbo.img, & vendor_kernel_boot.img in fastboot to get back into the OS.

Only a few people bootlooped (including myself) on stock. I'm on RisingOS now & didn't bootloop when flashing Sultan.
[Google Pixel 7 Pro] miimaa:
Don't know why but I got a bootloop using FKM. EX worked well, no bootloops.
[Google Pixel 7 Pro] scorpio76r:
Franco work

Did you have any magisk modules enabled before flashing the kernel? I'm asking because if you did, that would have been most likely the reason for your bootloop.
[Google Pixel 7 Pro] miimaa:
Yes I did, on both times.
[Google Pixel 7 Pro] scorpio76r:
Good rule of thumb is to disable modules before flashing a kernel. To avoid any issues.
[Google Pixel 7 Pro] sncsnc:
Hi.

For A14 andorid I flashed it using the core flasher. I have bootloop. I was able to open it with the stock image.
[Google Pixel 7 Pro] vagenrider:
just flashed with fkm on my new 7pro without problems
[Google Pixel 7 Pro] sncsnc:
Have you disabled Magisk modules?
[Google Pixel 7 Pro] 02ranger:
Is it safe to disable Magisk modules, install the kernel, and then re-enable them? I'm just not sure if there will be problems from disabling modules that are currently in use. I've only recently come back to Android and Magisk wasn't a thing last time I was involved in "the scene".
[Google Pixel 7 Pro] scorpio76r:
Yes you are good to go. You can do a reboot before immediately going in to disable the modules if you want to be ultra safe.
[Google Pixel 7 Pro] vagenrider:
didnt have any,its a new phone and flashed the kernel right after get rooted
[Google Pixel 7 Pro] sncsnc:
Disabled magisk modules. I turned the device off and on. I flashed it with kernel flasher. I got bootloop.
[Google Pixel 7 Pro] scorpio76r:
Sounds like you may have a carrier branded phone. Maybe their software that they pre installed isn't playing well with the kernel flasher. This is the only guess I can come up with. I also don't know what else you could be running on your phone that you haven't mentioned. Lastly, have you tried FKM? You mentioned that you used Core flasher. I have no knowledge of that flasher. Your issue is not kernel specific related. I have flashed this kernel on multiple 7pros (phones directly from Google) with FKM and, no bootloops.
[Google Pixel 7 Pro] Shayan69:
Will this work on latest QPR2 beta 1?
[Google Pixel 7 Pro] sncsnc:
It is not an carrier branded device. I installed the kernel with the kernel flasher in the August and September updates on A13. I will try it with FKM and write the result.
[Google Pixel 7 Pro] sncsnc:
I tried with FKM and it was bootloop. I did the November update with Pixelflasher . Then I flashed the kernel with the kernel flasher and there was no bootloop.
[Google Pixel 7 Pro] Yeedatoy:
FKM is outdated. EXKM is updated regularly. It's the only app available that shows all kernel settings accurately unless smart pack updated to show all three CPU clusters and GPU. I remember it added one of those two a while back, but not the other.

Edit: SmartPack still doesn't show the GPU.
[Google Pixel 7 Pro] Yeedatoy:
Also, kernel flasher not only takes better backups of more partitions, but it makes it much easier to submit any logs to Sultan, which would probably make things much easier for him to diagnose if there's ever an issue
[Google Pixel 7 Pro] Yeedatoy:
One more thing, Bootloop is a term that seems to be used incorrectly a lot these days. A boot loop is exactly what it sounds like, the phone booting, and then rebooting over and over again. Booting up and getting stuck on the Google logo, booting up and just going to a black screen or booting up and not getting past the bootloader unlock warning is a completely different scenario than a bootloop, so being more specific when stating with of the scenarios you end up with if you run into any issues can make things easier to possibly diagnose without getting into logs, etc.

Also, Unless you have a module that would interfere with the kernel directly, I would leave them enabled. Or just selectively remove modules you think may cause an issue, and make sure that whatever module you disable or move isn't one that is meant to work codependently with another module
[Google Pixel 7 Pro] scorpio76r:
For an outdated app it does still flash kernels though. That is all most people need.
[Google Pixel 7 Pro] Yeedatoy:
I know this was a while ago but if it takes a few attempts at flashing/sideloading for it to boot, or just takes a long time to boot sideloading then I wouldn't keep doing it that way. It sounds like something doesn't flash correctly via sideload, triggering Pixel debug mode which would explain a lengthy boot time with occasional failures. the reason it may be booting for you but not for the other guy who attempted this is likely related to magisk. Also, you never want to flash a kernel after a logical partition is touched on our devices like after flashing a rom but before a reboot, and you don't want to flash magisk after flashing the kernel since ak3 already preserves magisk root, and reflashing it anyway just creates chances of issues arising that otherwise would not have occurred
[Google Pixel 7 Pro] Yeedatoy:
After being told by a bunch of people that FKM wouldn't be updated anymore, it's just been updated 2 or 3 times which is great. Still no GPU but it's nice to see he's still working on it
[Google Pixel 7 Pro] Sui77:
May there will be an update?
[Google Pixel 7 Pro] JohnTheFarm3r:
Don't ask for ETA. Whenever there is an update, it will be released.
[Google Pixel 7 Pro] Blooded_Wine:
👀 No disable-verity 👀

Flashed via FKM onto stock P7P A14 December update (UQ1A.231205.015) with no issues, if anything breaks or is bad I'll update this comment but if it's good I'll probably forget.

edit 1:

The grip rejection service /twoshay does not start properly on this kernel, meaning my palm constantly has touch inputs on the edges of the stupid curved glass. While in this might make taps more responsive by removing steps from the input chain, it makes the phone unusable for reading in bed for me, due to the aforementioned stupid curved glass sitting on my hand.

(just here for posterity, see edit 2)

Attempting to start twoshay on this kernel:

cheetah:/ # /vendor/bin/twoshay -s

Start a service!
setAlgorithmList is currently disabled until it is adapted to support TwoshayPipelineConfig.
Retry #1
Failed to open "/dev/touch_offload".
Failed to connect driver interface with ret = -13
Retry #2
...

This loops forever, presumably it starts looping on boot.

it is properly taken out back and shot before it has a chance to loop

Starting twoshay on stock.

cheetah:/ # /vendor/bin/twoshay -s

Start a service!
setAlgorithmList is currently disabled until it is adapted to support TwoshayPipelineConfig.
Retry #1
I0000 00:00:1702917655.217191 9140 twoshay_touchflower.cc:133] Creating touch shape
I0000 00:00:1702917655.217307 9140 twoshay_touchflower.cc:154] Creating touch corrector

available context: 0
required context: 0
accept: 1

I do like this kernel and noticed it made my device cooler to the touch while gaming + plugged in, but the curved glass kinda necessitates grip rejection for me.

edit 2:

This was deliberate, sucks for me I guess. The reasoning was exactly as I figured (latency).

Looking through the commits made me really appreciate the effort that has gone into this kernel, and there is a whole lot of love and dedication that went into making a poorly optimized chip perform well and not burn you to death for daring to play a game on it.
[Google Pixel 7 Pro] mTheDarkKnight:
Guys, I am on Nov 2023 patch. Currently on kirisakura kernel. Can I flash this kernel on Nov 2023 patch!?
[Google Pixel 7 Pro] Sui77:
Yes
[Google Pixel 7 Pro] Misuto:
@Sultanxda Hey man. Not asking for ETA or anything. I was just wondering if this kernel will happen to get any further updates in the future for the 7 series, since the 8 came out? Because your kernel is pretty great for these devices.
[Google Pixel 7 Pro] don.nasco:
He has already answered similar questions in this thread. Just scroll back.
[Google Pixel 7 Pro] Sultanxda:
Likely before the end of the year. I've been releasing beta updates privately on Telegram for some time now, but haven't released a public update in a while because I've been busy rewriting a large subsystem for the 8. I ported this work to the 7 kernel as well. It's a total rewrite of the code that controls the RAM's frequency, and it improves battery significantly. But it was also a lot of work :)
[Google Pixel 7 Pro] Misuto:
That's awesome to hear! Geez, yeah that sounds like a lot of work. Well, we appreciate the work you do man 👍🏻
[Google Pixel 7 Pro] reg66:
Hats off to you sir!! Really, really good to hear... Nice one dude, have a great Christmas and new year.
[Google Pixel 7 Pro] ggrks:
Sorry for the misplaced question. Will this kernel ever be ported to the pixel fold? I'm really looking forward to it, but if I don't have a plan, I'll give up...
[Google Pixel 7 Pro] Sultanxda:
It can be, but the Fold has enough hardware differences that I wouldn't attempt it without having physical access to a Fold myself. The WiFi module is different in the Fold for example, and there are some other sensors it has, too.

I don't have a Fold and I never plan on getting one, so Fold support is indefinitely off the table I'm afraid.
[Google Pixel 7 Pro] ggrks:
Thank you for your detailed explanation. I understood that the hardware is different even though G2 is common, but it seems more complicated than I thought. Unfortunately, I'm giving up on waiting on Fold... thank you very much.
[Google Pixel 7 Pro] Sui77:
This one is working fine on beta
[Google Pixel 7 Pro] Cpt Spacewreck:
Sultan kernel works great so far on my Pixel 7a with LineageOS 20 + microg. I immediately noticed the faster feedback of scrolling/swiping and phone idle is draining way less battery. Thank you so much for your work, it's awesome.

One question regarding battery usage: I'm using VR25's Advanced charging controller module and was curious if Sultan Kernel supports battery idle mode (drawing power directly from the charger bypassing the battery)? I'm not sure because testing functionality with AccA doesn't do anything. Thank you
[Google Pixel 7 Pro] scorpio76r:
Just curious, has anyone used this kernel with the latest Evo-X rom on the 7pro?
[Google Pixel 7 Pro] Sui77:
Could i join the beta 🤩
[Google Pixel 7 Pro] Sultanxda:
If you're on Telegram, sure.
[Google Pixel 7 Pro] sasha.marinichev:
Dear Sultan, can you please comment on Pixel 7's poor LDAC support? Is it caused by stock kernel or Tensor's inferior engineering? The information is easy to find: People have been complaining about audio stutters since P6 (with various combinations of codec settings selected in dev settings). It seems that Tensor-powered Pixels work fine with Aptx and Aptx HD, and LDAC, a go-to option for Snapdragon devices, remains partly broken. If your kernel happens to incorporate any fixes in this domain, I will be glad to flash it, as I used to do back in OP3 days :)I will appreciate your answer.
[Google Pixel 7 Pro] kradNZ:
Just flashed via FKM, left magisk and all modules enabled, worked perfectly.
[Google Pixel 7 Pro] kradNZ:
Experienced a random black screen today. I could feel the phone haptic feedback when pressing the power key but screen didn't turn on. Long hold of power key eventually rebooted the device. Never seen this failure mode before, unsure if its anything related to this kernel.
[Google Pixel 7 Pro] Freak07:
check sys/fs/pstore.

if a ramoops was generated that may tell what happened or if it´s related to the kernel. if you rebooted another time, the file will probably be gone now.
[Google Pixel 7 Pro] kradNZ:
Yeah nothing there now unfortunately.

Will report if I get it again.
[Google Pixel 7 Pro] kradNZ:
Reverted back to stock until kernel uname detection thing blows over.
[Google Pixel 7 Pro] don.nasco:
What do you mean? What is the problem?
[Google Pixel 7 Pro] kradNZ:
G

Google has started to fail device integrity based on certain kernel names.

This is a problem if you want to use Google wallet/gpay etc while rooted. Basically gives away that you're rooted.

"FYI to custom kernel users who are suddenly failing device attestation in Play Integrity.

The cause appears to be that Google has blacklisted certain strings from kernel version names (case insensitively).

The reason my kernel fails Play Integrity device attestation right now is because Google blacklisted my name from the kernel version string: 5.15.110-Sultan fails 5.15.110-sultan fails 5.15.110-Slutan works .

Other kernels which are affected by the Play Integrity change are likely also on Google's kernel version string blacklist."

From telegram.
[Google Pixel 7 Pro] Jonas35:
i already noticed that. lol. Flashed the kernel 1h ago. Now back to stock.

Sometimes it would be good to read beforehand. :ROFLMAO:
[Google Pixel 7 Pro] Locoman_:
How to you change the name of the kernel? I'm guessing it's not just changing the name of the file you flash..
[Google Pixel 7 Pro] badabing2003:
🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Google Pixel 7 Pro] kradNZ:
You have to recompile it I believe.