yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] theincognito:
I have been running it on LOS 20.0 since the first public build. Runs fine. No issues.
[Google Pixel 7 Pro] don.nasco:
I think that the problem comes with sideloading the zip.

Does anyone now if I can `dd` the dtbo.img and Image.lz4 from a running device (over adb root shell)?

Also, are those two files the only thing needed, or there is something "hidden"?
[Google Pixel 7 Pro] 5.1:
Hi,

This should take no more than 5 minutes (10 if you gotta extract init_boot from payload.bin):

Downlod magisk > patch ROM init_boot > flash patched init_boot > reboot > install kernel with kernel flasher > reboot into bootloader and reflash rom init_boot > BOOM, done :cowboy:

Cheers,

Sébastien.
[Google Pixel 7 Pro] don.nasco:
Thanks for your suggestion, but I need to do that without Magisk.

I do not want to root my phone because of a few Apps that might detect it, even though I remove the Magisk later.
[Google Pixel 7 Pro] Locoman_:
Why don't you root, install, then unroot?
[Google Pixel 7 Pro] dr.wtf:
I flashed android 14 over the kernel and it behaves weirdly. Can someone confirm that when flashing a new rom the kernel is removed without any residue?
[Google Pixel 7 Pro] Nekromantik:
not correct thread as this is about the kernel and not updating to A14 but yes if you flash A14 then sultan kernel from a13 will be replaced with stock kernel unless you installed it again as part of the install
[Google Pixel 7 Pro] HipKat:
Yes, the stock kernel replaces the custom kernel. You should be able to see this in your About Phone or Kernel flashing utility
[Google Pixel 7 Pro] androin11qq:
Hello. The kernel description states that it improves gaming performance.

Is it so? If so, how much?

Is overheating and throttling reduced?

Will 60 fps be stable in Genshin?

P.s. owner pixel 7
[Google Pixel 7 Pro] DepressedDead:
I installed this kernel on top of crDroid (Android 13 for cheetah, latest release from September 26th) and while performance is great (everything is buttery smooth), thermal performance is a disaster.

I tried to charge my phone with both wired & wireless chargers and the phone powered itself off after some 15-30 minutes due to the battery reaching 50°C. I had never experienced anything like that when using stock rom or the stock crDroid kernel.

Ironically, this only happens when the phone's screen is off, so there's either 1. something doing shady things in background (very unlikely) or 2. the suspend logic is broken on LOS-based custom roms. I'm running the latest October firmware btw.

By looking at the dmesg logs it looks like something is waking up the device too often (every 10s or so), and when the phone wakes up all CPUs remain pegged for ~5s. The two big cores (the 2.85GHz ones) also remain at the highest frequency (2.85GHz) at all times.

This makes the phone feel EXTREMELY hot when the screen is off, and it drains about 10% battery every 15min.

I didn't change any kernel parameters and I don't run any "weird" magisk modules (other than adaway and the hosts module).
[Google Pixel 7 Pro] DepressedDead:
Here's my dmesg. Hopefully this helps.

I'm really looking forward to using this kernel on crDroid! Performance is great but there's probably some rom-kernel issue causing it to perform badly when the screen is off.
[Google Pixel 7 Pro] allenjthomsen:
I am currently running crdroid 9.9 and with sultans latest kernel and have not run into this issue you are describing. I would use matlog and pull a log cat to make sure it is not an app of yours causing this issue. Also his latest update is 10/04. I have my reasons to believe this is an app issue causing wakelocks and causing the phone to overheat while charging. Just to confirm i went back to september 26th build and clean flashed both rom and kernel and was unable to reproduce what you have stated was happening.but im sure once he looks at the dmesg he will be able to tell for sure if its kernel or app related...
[Google Pixel 7 Pro] wheelbarrel:
I installed this kernel over a week ago, haven't had any issues, and I noticed a big difference in my battery life from the very first day it was installed. I work in construction, and use my P7 for music all day, and before this kernel was installed, my phone would be dead by 5pm. Now it literally last all day!

I usually just stick with stock, but since I use my P7 all day with YT music, I noticed in the past few months the battery drain had been getting worse and worse, so I wanted to try out a new kernel. Very glad I did!

Thank you for your time and work put into this!
[Google Pixel 7 Pro] DepressedDead:
Thanks for the reply!

Well... I don't think it's an app causing my phone to go bork. I didn't experience any of this with crDroid's stock kernel. BTW, I tried the latest kernel release from October 4th on crDroid 9.9 (september 24/25th release), Before flashing crDroid I flashed the latest October firmware, so I don't know if that's causing any issues.

I tried rebooting into safe mode just to make sure it's none of my apps (or magisk modules) causing any weird behavior and the phone literally drained itself to death in 1 hour (from ~30% to 0%). That was in airplane mode.

And lastly, I tried going back to stock kernel just so I reflashed the entire ROM + gapps only to find this is still happening (I didn't notice any overheating, though). Absolutely none of this happened before I flashed this kernel thru Kernel Flasher, so I'm wondering if I need to re-flash everything all over again.
[Google Pixel 7 Pro] allenjthomsen:
Based on what your telling me im thinking it could be the bootloader baseband from a14 build causing issues with the a13 base idk havent flashed a14 base firmware yet still using september a13 stock bootloader and baseband it could be the baseband causing wakelocks while charging. Im not a kernel dev so im throwing guesses at the wind on that one.

Try with a13 bootloader and baseband and see if the issue goes away.
[Google Pixel 7 Pro] DepressedDead:
Yeah I just flashed the latest September A13 update using Google's official flash tool. Then flashed crDroid 9.9, gapps, magisk and the kernel but the issue is still there.

I went back to my previous setup (everything minus Sultan's kernel) and the issue persists, on a CLEAN flash. And yes, I flashed the stock rom, installed crDroid, wiped data, etc. I only installed Ampere to see what the power consumption was and oh boy: it's syphoning ~600mA with 0% brightness on a clean flash + airplane mode turned on. 1% battery drain every 5 min or so.

I don't see anything weird in htop. Not even the kernel is using CPU so I guess something permanently damaged the battery or some other internal circuitry. The phone always feels a little bit hot, like 30-35C. I'm either being targeted by someone or the kernel caused some permanent damage (lol)
[Google Pixel 7 Pro] benoboa:
Start with a clean flash leave sim card out skip all log in and don't set up wifi and see what idle drain is, if it improves try just logging into wifi if that's good add sim card if that's good log in but don't restore apps if that's good then it's a rouge app
[Google Pixel 7 Pro] DepressedDead:
Thanks for the advice.

This is what I did, I didn't restore any app. I only connected to wifi, installed Ampere and that's it. I also installed Termux to use the top command with root and see what is using CPU, but NOTHING is using it (all cores remain below 5% usage). The phone literally feels warm even if top says there's only 2% CPU usage, which is weird.

I'll test again on stock to see if the same thing happens, but it looks like this kernel triggered some thermal-related bug in the hardware, because now even with the stock crDroid kernel the same thing happens. None of this happened until I ran into the "Phone turned off due to heat" warning with this kernel installed.

EDIT: I just installed stock (https://flash.android.com/build/10750268?target=cheetah-user&signed=true&wipe=true&forceFlash=true / `TQ3A.230901.001 (10750268)` ) and the issue is still there. 700mA battery drain at 0% screen brightness, with no google account and no apps installed. I guess it's perfectly fine to say that some permanent hardware damage has occurred. :(
[Google Pixel 7 Pro] reo101:
Hey man, thank you for the great kernel, it works wonders!

I wanted to ask about how would one go about imtegrating a custom patch into your version of the kernel and mimicking your compilation process.

The patch I'm talking about is this (or a modernized verson of it), it should enable the `mass_storage` capability which will, in turn, enable us, Pixel 7{, Pro,a} users to use software like `DriveDroid` and `UMS Mounter`.

Regarding the integration/compilation process, I feel comfortable with anything, as long as it runs on linux, or, preferably, nix (dream would be to separate the commit in a real .diff and use something like this to easily build an ISO/kernel). I'm ready to fire up vim and get my hands dirty with C, if need be. :D

* Phone stats if somehow needed:

Model: Pixel 7 Pro

ROM: Stock (13)

Kernel: Stock/yours

Build Number: TQ3A.230705.001

P.S.:

Sorry if this is a noob question and not the right place to ask, I just wanna host ISOs from my phone :D (was able to do it on stock kernel on my Lenovo P2 back in the day, good old times....).

Sincerely,

reo101
[Google Pixel 7 Pro] Sultanxda:
Turn off WiFi, wait a few minutes, and then check if the excessive drain persists. If it does, please capture another dmesg and upload it.
[Google Pixel 7 Pro] danielk2555:
could also be hardware related. The first P7 phone I ordered from google as soon as I turned it on with literally nothing in it and just connected to Wifi was running hot af. Straight out of the box when the P7s came out

Contacted google support they told me if it was OK for them to grab some logs from it - I said yes. Then they replaced it and didn't give any details. I would assume it was faulty from a hardware standpoint
[Google Pixel 7 Pro] Sultanxda:
Use "uname -v" or "uname -a".

Yes. It's in testing on Telegram right now.

Correct. Work on the kernel itself takes priority, so I haven't got around to this yet. I'll hopefully fix it SoonTM.

Overheating and throttling are reduced, but there's no way to eliminate them.

Gaming performance should be significantly improved. I'm told by users on Telegram that Genshin performs quite well. If you use a cooler on your phone, then Genshin should sustain about 60 FPS at high graphics (from my own testing using a cooler).

Download the latest version of GCC if your Linux distribution doesn't have it.

Extract x86_64-gcc-13.2.0-nolibc-aarch64-linux.tar.xz if you downloaded it. Skip this step if you already have the aarch64-linux-gnu-gcc command on your system (and it's GCC 13.2).

Download the kernel source with this command:

git clone https://github.com/kerneltoast/android_kernel_google_gs201.git

cd into android_kernel_google_gs201

If you downloaded x86_64-gcc-13.2.0-nolibc-aarch64-linux.tar.xz, then run:

export CROSS_COMPILE=$HOME/Downloads/gcc-13.2.0-nolibc/aarch64-linux/bin/aarch64-linux-

Run:

make gs201_defconfig

Run:

make -j$(nproc)

Run:

cat out/arch/arm64/boot/*.dtb > out/dtb

You should now have the following files:

out/arch/arm64/boot/Image.lz4

out/arch/arm64/boot/dts/google/dtbo.img

out/dtb

You can copy the 3 files specified in the previous step into the .zip file I use to distribute the kernel (e.g., Sultan-kernel-gs201-U-20231008.zip), and then install it as you would install my kernel.
[Google Pixel 7 Pro] DepressedDead:
Yes. This could be a possibility... but I've been using my phone for about ~6 months and I never faced high battery drain. The phone was never hot or warm either.

Battery drain overnight was about ~10% for 7-8 hours and 2% with battery saver on. Now it's 70% with battery saver on, with any kernel, be it stock, stock crDroid or Sultan's.

I don't think Sultan's kernel is directly causing the issue because I see htop "stabilizing" (i.e. all cores won't go past 5%) after some 5-10 minutes. The slightly loosened thermal restrictions is most probably what triggered the hardware bug. I also see a constant 500mAh power draw with the screen off and with negligible CPU usage.

I'll post another dmesg tomorrow with wifi & mobile data off.
[Google Pixel 7 Pro] Sultanxda:
What "slightly loosened thermal restrictions" are you referring to? If you're referring to the kernel, I actually have not altered the thermal restrictions in any way. All of the thermal throttling limits are untouched.
[Google Pixel 7 Pro] DepressedDead:
I saw this in the OP:

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

...so I naturally thought some thermal restrictions had been lifted. This made sense for me, because 1. now my phone is constantly warm and 2. I had never seen the "phone turned off due to heat" message, and 3. everything felt significantly faster and smoother (lol), so I instantly assumed the thermal restrictions were a bit more lenient.

I know this isn't necessarily the case, but please bear with me. I now have a phone with a broken battery, and I'm trying to find a fix. I think some sort of hardware bug is triggered once the battery temperature reaches a certain threshold so this would've happened sooner or later in a beach trip with or without your kernel.
[Google Pixel 7 Pro] danielk2555:
Hmmmm... did you drop the phone or expose it too much to sea water? Salt water will ruin them slowly... and even though these phones have some waterproofing abilities nowadays -> never test that ability with seawater... it will eat through everything overtime...

I ruined a few Nokias that way cuz I'd forget they were in my pocket and I'd dive or go for a swim... I'm old af I know lol....

But the first one to go after sea water exposure was the battery - it'd overheat by just letting the phone sit and then the keyboard keys would start dying one by one since the motherboard was getting corroded over time .
[Google Pixel 7 Pro] allenjthomsen:
You ruthless person ruining nokias lol jk
[Google Pixel 7 Pro] Sultanxda:
New build is up with the random reboots finally fixed. Turns out they were caused by a bug that Google introduced over 2 years ago.

Idle battery drain specifically has been improved, and overall responsiveness + battery drain should be improved with the complete removal of Google's massive scheduler additions.

There is now a build available for Android 14, which is compatible with the QPR beta.
[Google Pixel 7 Pro] Sui77:
The kernel is also suitable for QPR1, right?
[Google Pixel 7 Pro] Sultanxda:
Yes.
[Google Pixel 7 Pro] miimaa:
I'm running rooted A14 with stock kernel.

Flashed the kernel with FKM and I ended up in a bootloop of two screens: unlocked bootloop warning and logo of Google. Solved it with PF.

Was the A14 version only for QPR?
[Google Pixel 7 Pro] Locoman_:
Running fine here on A14 stock. Edit: stock rom with kiri. Flashed this kernel with PF over kiri with no issues
[Google Pixel 7 Pro] chrisz5z:
bootloop here on A14 stock as well. What's PF?
[Google Pixel 7 Pro] miimaa:
Pixel Flasher.
[Google Pixel 7 Pro] chrisz5z:
you saying you reverted back to stock with PF or you successfully flashed Sultan Kernel with PF? If it's the latter, how did you do that?
[Google Pixel 7 Pro] miimaa:
Sorry, went back to stock with PF.
[Google Pixel 7 Pro] jhjhjhjhjhjh:
To O.P i wish i could try a few kernels including this one but the preferred way for pixel devices is to flash a kernel similar to flashing a stock kernel.

Curious to know if here are different programs each dev uses to build the zimage??

I could only boot a custom kernel successfully in fastboot/fastbootd...

fastboot reboot bootloader

fastboot flash dtbo dtbo.img

fastboot flash boot boot.img

fastboot flash vendor_kernel_boot vendor__kernel_boot.img

fastboot reboot fastboot(Now in fastbootd)

fastboot flash vendor_dlkm vendor_dlkm.img

Any chance of building with these images to flash rather than a kernel flasher app??
[Google Pixel 7 Pro] reg66:
I'm not on A14, so can't say for sure but... I recall trying to flash a pixel 7 pro kernel quite some timeago with FKM and got bootloop. Installed Kernel Flasher from playstore and no issues - seems superior to me. Could try with that
[Google Pixel 7 Pro] chrisz5z:
I'm on A14, Kiri & Radioactive flash fine for me with FKM. I get a bootloop with Sultan using FKM or Kernel Flasher.
[Google Pixel 7 Pro] sawdoctor:
How hard would it be to port to the pixel fold? Same chip so hopefully not hard
[Google Pixel 7 Pro] sklaes:
I would also love to see a version that can be flashed without root.
[Google Pixel 7 Pro] pwn1ca:
Runs great on A14 Qpr beta. Thank you very much for your work 🙂
[Google Pixel 7 Pro] Yeedatoy:
I respect your experience with varying devices and your contributions to those devices that lack development such as the Motorola MTK devices and Various devices which with only GSI support. In these areas, you typically lead the discussions, as you often have more experience than many of the other members involved in them. That being said, it's okay to be on the other side and still enter different areas with a willingness to learn. There have been kernels for Pixel devices that are flashed via Fastboot, but more often than less it's been to just Fastboot boot the image, and this is typically during the beginning stages of development for these devices after release, and applies more so to older pixels. Anykernel zips are going to be used for pixels 95% of the time. It's my understanding that Sultans way around Dm-verity and verification is his kernel doesn't touch vendor_dlkm. If Monolith...zimage, dtbo & dtb is overwritten but no other partitions are touched. This is being adapted by most other kernel devs ever since Sultan brought it to our P7s first, as verified boot has been an issue ever since Hashtree patcher could no longer function as it used to due to changes implemented by Google.

There's really no reason to flash using any other methods unless you aren't rooted, and if that's the case you should look at CleanSlate kernel. It's much easier to just flash a zip to install a kernel, and as long as you've adhered to the devs instructions there usually won't be any issues. The people who are getting stuck, it's likely due to a failure in the program they're using to flash, an issue caused by a previous flash, devs using an outdated Anykernel package, or incorrect firmware as a base.

FKM is becoming too outdated to be reliable compared to other programs. EXKM is updated regularly so my recommendation would be to flash with either it, Horizon Kernel flasher or "Kernel Flasher" which you'll likely find on these threads.
[Google Pixel 7 Pro] dr.wtf:
Will there be a kernel for every monthly update of the roms? Would I "downgrade" the kernel when flashing it over the newest stock Rom?
[Google Pixel 7 Pro] scorpio76r:
I flashed this with FKM on Rising OS beta 14 and, my phone has been running like a champ. Thermals are definitely cooler than stock kernel and, battery has been wonderful.
[Google Pixel 7 Pro] Dark_Eyes_:
OMG a sultan's kernel for P7Pro!

Haven`t flashed a custom kernel in years, and I see people bootlooping. What would be the best way to flash on pure stock Android 14? I have both Franco and EX, never tried Kernel Flasher though.

Thanks for the tips, guys!
[Touch Dual, MDA Touch Plus ROM Development] gullum:
I've taken this one ofline there is a gullum TF2D III released already
[Touch Dual, MDA Touch Plus ROM Development] gullum:
bug and updates

To get default conacts back

open advanced task in setting/system

scoll to regedit and find this reg

change this

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:MSCONTACTS]
"0"="Contacts"
"1"="Windows/iContact.exe"
"2"=dword:1
"3"=dword:0

To

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:MSCONTACTS]
"0"="Contacts"
"1"=":MSPOUTLOOK contacts"
"2"=dword:1
"3"=dword:0

get battery inticator working and showing corretly delete the 2 lines in red

[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BaseId"=dword:00000000
"BaseDll"="phcanOverbmp.dll"
[COLOR="Red"][B]"BatteryIconIdStart"=dword:000003e9
"BatteryIconLevels"=dword:00000015[/B][/COLOR]

Tanks to ViNZ! for the info

Special Thanks to

hma4 - APBilbo - Cloudyfa - maxniper - itje - Laurentius26 - P1Tater - anja31 - pinobigbird - wmn79 - Duttyroy - dsixda - udk - Noonski

all the DEV's that have made it possible to dump,port and cook roms with their unbelivable tools

Extra special thanks to bepe for putting together some of the best tool around XDA into the DEV kitchen that I use for several devices
[Touch Dual, MDA Touch Plus ROM Development] gullum:
changelog

for updates

the next beta will be CE OS 5.2.20764(build 20764.1.4.3) For Polaris, Nike and Kaiser maybe I'll make one for Prophet and Wizard too
[Touch Dual, MDA Touch Plus ROM Development] venelar:
looks good, i may try to steal the wife's niki tomorrow and load it up.
[Touch Dual, MDA Touch Plus ROM Development] animelover:
Sounds good, will give it a try!
[Touch Dual, MDA Touch Plus ROM Development] vcdwelt:
Tested Rom.

Stable and Fast

Bugs:

- Internet Tab always open Opera Mini (not Mobile)

- If i tab the batterie in System Bar no text appears on akku status

- Photos and Video Tab, missing the up/down button, appears only on pushing

Nothing bad found...
[Touch Dual, MDA Touch Plus ROM Development] gullum:
Thanks

Internet tab my fault forgot to remove the regs that made it open mini will fix for next same with up and down images in picture tab

battery is a missing mui file but will also add it back.
[Touch Dual, MDA Touch Plus ROM Development] twolf:
Will test it, thanks. :)

--edit--

Does the camera really work? The older version seemed fine but wouldnt take pictures.

Whats the adviced radio to use?
[Touch Dual, MDA Touch Plus ROM Development] obsydian:
Has the same BT issue (will not disconnect once connected to a BT source), the last Lilly and BD ROM's had which is so annoying, only solution is the soft reset the device, switching BT on/off does nothing :mad:

BUT otherwise the ROM is pretty awesome, is VERY quick and responsive.
[Touch Dual, MDA Touch Plus ROM Development] djharty:
Camera works. But many thinks didn't work.

-The hardware keyboard didn't work correctly. (Wrong letters, 20key nike)

- Headset connection over bluetooth aren't disconnect correctly. I must always make a restart to use the phone normaly.

- Graphic glitches by using the "Phone Keypad"

That's all for the moment.

For a beta, is it a good stable and fast ROM.
[Touch Dual, MDA Touch Plus ROM Development] joaosousa:
Same prob here with 20 keys niki... Keyboard not working correctly...
[Touch Dual, MDA Touch Plus ROM Development] twolf:
Any way you could release or point us to the correct cab for the camera only?

Pretty please? :D
[Touch Dual, MDA Touch Plus ROM Development] 1scariot:
Sorry for offtop and my bad english, but where can i find a cab or something else of calendar like this.
[Touch Dual, MDA Touch Plus ROM Development] mitchelleersel:
Okay

Looks pretty awesome downloading right now and flashing it in t minus 1 minute. (that last sys from Niki rom kitchen didn't do it for me)

Will be back with my findings tommorow.

Pz
[Touch Dual, MDA Touch Plus ROM Development] rling:
I've been using the Nike Kitchen Nike camera 5.06.31844 without any problems. Granted I rarely used the camera, but the brief testing I've given it to date has not revealed any problems.
[Touch Dual, MDA Touch Plus ROM Development] twolf:
Oh, I thought I read Camera 6.8, that 3mpx Raphael camera, like the one on your older rom:

http://xdaforums.com/showthread.php?t=428346

Sorry.
[Touch Dual, MDA Touch Plus ROM Development] obsydian:
Not keen on the contacts software, quite annoying prefer the standard menu.
[Touch Dual, MDA Touch Plus ROM Development] looking-g:
used the rom for a day now and must say thank you because it is awsome fast and very nice so thanks
[Touch Dual, MDA Touch Plus ROM Development] gullum:
Check post 2 on how to get back default contacts
[Touch Dual, MDA Touch Plus ROM Development] gullum:
This is actualy my fault :( it's the version 6.08 in the screenshots but 5.06 is in the rom