yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
If you block certain things it might backfire. I'd very closely check the logcat from time to time. It might be that some google services/apps act up if they can't establish a connection, retrying again and again and again.

It's probably due to the usage pattern and the network. Checking phone more often for short amounts of time vs using it not as often but longer durations. Rather typing messages, vs reading/watching stuff. Network type, network quality etc. But there can be many other factors i guess.

Yes, if ambient temperature is high the pixel 6 pro tends to get warm easily. (Just as pretty much every other recent flagship device)
[Google Pixel 6 Pro] bgboii:
Yeah my temperature was at 95°f then went to 102°f which felt hot to touch.
[Google Pixel 6 Pro] Pipodi93:
I was reading this and tried top right away and saw "system_server" using 20~30% of CPU, being always the highest process on the list. Do you know what is causing this? I'm reading online that is what "Android OS" is called in the process list, is it right?
[Google Pixel 6 Pro] triggerhappy_:
Oh, by the way, I noticed when trying to toggle out brightness all the way from right to left and vice versa, the slider is flickering and delaying like crazy. I don't like that. It happens on both Kirisakura and stock kernels. It occurs random places on the slider. Something with refresh rate I presume.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It didn't help that XDA's article on this feature initially said Pixel 6 and Pixel 6 Pro before they corrected it.
[Google Pixel 6 Pro] Freak07:
system_server is a placeholder/wrapper for various services from the framework, that´s correct. that probably means there´s something screwed up somehow.

I´d check if a reboot solves this issue first.

If you´re using any mods or tweaks I´d try to remove them all

If you´re using my apps that modify stuff via root, or block services/apps in any way I´d try removing them and see if that changes anything.

I´d also try to look at logcat while system_server is at 30% and see if anything stands out there. (i.e an app/service spamming errors several times a second -> that´s what I would suspect)

There´s always the possibility something goes wrong when going from A12 to A13 or when mods/tweaks etc are used and can only be solved by a wipe.

I can´t seem to reproduce this on my end at the moment, but I also basically never use the slider as autobrightness works very well for me on this device.

It´s not related to the kernel in either way though. :) something google must fix on the framework side. if you have a reproducer you can post it on google issue tracker as a bug I guess.

or that double tap to wake is an "issue" on my kernel related to 1080p, when it was just a user request. but the article was corrected by now.
[Google Pixel 6 Pro] flex360:
I flashed the raven version to my Pixel 6 pro and now its completely dead. I gotta take it to a ubreakfix today and replace the motherboard. Funny that I havent rooted my phone or flashed anything in about 7 years and the first time I try again, it murders my phone lol
[Google Pixel 6 Pro] triggerhappy_:
F
[Google Pixel 6 Pro] Freak07:
Sorry to hear that...

The only thing that comes to my mind is you either triggered the anti rollback protection and haven't updated to a13 on both slots or just a random Mobo failure, which is unfortunate but can happen to every device.

Hopefully they fix it quickly for you.
[Google Pixel 6 Pro] ChongoDroid:
I had a weird issue today. Was browsing twitter and randomly phone died went from 55% to 0% in a second now slowly charging from 0% and I noticed the battery stats show 50% from about 2am last night. Not insinuating this has anything to do with the kernel (using 13 stock with 4.1 kernel) but just curious if anyone else has had this issue.

Kind of concerned because it usually indicates a failing battery and I got this phone used from bestbuy so I'm hoping it's not failing hardware.
[Google Pixel 6 Pro] ChongoDroid:
Also noticed that my battery stats don't reflect actual battery life for hours
[Google Pixel 6 Pro] ChongoDroid:
Okay so charging the battery for a while and now it shows the rapid decline
[Google Pixel 6 Pro] triggerhappy_:
Sorry for the offtop, is there any way to export logs from Termux su top?
[Google Pixel 6 Pro] shag_on_e:
Oh yeah? I plug my phone in and it stays at 100% lol.
[Google Pixel 6 Pro] NCVol:
I have a P6 and I was on Raviole for A12. I've updated to A13 and am on 4.1 kernel. My battery life has been terrible. My screen on battery use was 12.4% before the update and now it's 16.9%. Screen off used to be 2.4% and now it's 4.7%. My combined use for a full battery used to be 33 hours and now it's 13 1/2 hours. Charging also seems slower.

I don't see anything obvious in Accubattery, system battery stats, or BetterBatteryStats. Any ideas what it could be? Is my best bet to wipe and do a clean install? Or are other people having the same issue?
[Google Pixel 6 Pro] Nightf0x_007:
Yes battery is [subpar] with a13, does anybody have lsposed installled & have problems with bluetooth (ik its not kernel related)?
[Google Pixel 6 Pro] Freak07:
I´d like to ask everyone to keep the off-topic in check. Usually I don´t mind a bit off-topic as long as it´s vaguely related to the kernel and/or helps other users and the community. But the last few pages (the quoted posts are just examples) have gotten a bit out of hand to be fair as most of the posts aren´t related to this project at all and the thread has become pretty cluttered up with not much relation to anything of the kernel.

I understand this is a very popular thread, but if you have an issue please either search for a thread that already covers this topic and if there´s no thread create a new one that covers the topic. :)

Regarding the battery life topic. Some people seem to have troubles on A13, while some others don´t. My battery life is fine on A13 and the same as on A12.

I can only advise to check the post following this link here, it might help to diagnose the cause. There can still be apps that don´t work properly with A13 for example. There can be other changes in the framework from Google in A13 that don´t work well with some unique usage patterns.

Maybe a wipe is in order and something got screwed up. That can happen on stock firmware too without modifications. Wouldn´t be the first time. However I´d advice checking the linked post before wiping.
[Google Pixel 6 Pro] NCVol:
Apologies. I thought the battery issue was related to the kernel and not the OS, which is why I posted it here. I'll try to be more careful about it.
[Google Pixel 6 Pro] kiekan:
I am on the stable build of A13 (TP1A.220624.021) and when running the 4.1.0 kernel on P6 Pro, I seem to have connectivity issues. Getting excellent battery life and performance. But whenever I try to make calls, it seems to drop calls constantly. Often times after a call is ended, the signal bar shows an exclamation mark (!) for a moment as it reconnects to the network. Is there a log I can pull to help identify the issue? I have gone back to the A13 stock kernel for the time being to test if that kernel experiences the same issues. So far, it does not and I have a much more stable connection when using the stock kernel.
[Google Pixel 6 Pro] Freak07:
don´t worry about it. sometimes it´s very hard to pinpoint an exact cause, that´s why I linked you to the post.

It´s just that I replied to the same question already a few posts back. :)

And you just happened to be in the line of multi quote.

Hey :) thanks for the report.

The kernel has basically nothing to do with mobile connection. That´s mostly handled by the baseband.

It might just be your carrier at the moment this happened or some other fluke in the connection, depending on the time and place you where when it happened.

I´m usually receiving and making multiple calls per day and I haven´t had any issue since testing the kernel on A13.

You can pull a logcat and a dmesg and note the time it happened that a call was dropped. Maybe we´ll be able to see something in there. :)
[Google Pixel 6 Pro] biggiesmalls657:
@Freak07 it's not the kernel buddy, it's Google!
[Google Pixel 6 Pro] triggerhappy_:
With kernel drainage is almost as twice as faster based upon my personal experience.
[Google Pixel 6 Pro] Freak07:
A correction here: the kernel itself does not drain any battery. That´s true for the stock kernel and custom kernels as well.

Some popular battery usage apps summarize just a huge bunch of processes under the category "kernel", which is nonsense and leads users to believe the kernel itself does drain battery.

The system requests resources from the kernel and the kernel grants it. If the kernel wouldn´t grant those resources, the phone would not work. Simple as that.

I understand you have bad battery life on A13 in general as you mentioned a few pages back. Same as others unfortunately.

But I really don´t understand the need to again post about this topic referencing a post that apologies for off-topic, when I just asked to keep the off topic out. This is in not related to the development of this kernel project, as you said yourself you have the issue on stock as well. It clutters up the thread and confuses inexperienced users even further.
[Google Pixel 6 Pro] TangerineCC:
I'm not a very techy person, but my Google Pixel 6 pro keeps overheating way too fast when playing games. The only way this phone charges is if i lay it under an ice pack.

I don't quite understand the directions in order to install these packages, is there a way for simpler instructions to be added? I don't understand a lot of these terms.
[Google Pixel 6 Pro] triggerhappy_:
Being not a very "techy" person you better not try doing this, you might be ended up with a corrupted or in the worst case dead device in your hands. There is a risk anyway, no matter how good you are. Not trying to discourage you, but to warn you about possible consequences.

Here is the main thread to start with. First steps are to unlock the bootloader and get the root. Follow the white rabbit instructions step by step and try to grasp the concept.
[Google Pixel 6 Pro] Phascinate:
Hi, I just wanted to say THANK YOU SO MUCH to @Freak07. This kernel is absolutely amazing and has made my Pixel 6 Pro into a much better phone. A lot of people have complained that Android 13 has made their devices worse in some ways, and that battery life has suffered. I'm having the complete opposite experience.

Granted, I am very much a power user, and modify every app on my device so that only specific ones can run in the background. I use App Ops and Greenify for the majority of these things. Additionally, I use the Wakelock Blocker feature of this kernel to block long-running wakelocks.

Anyway, I'm now getting under 1% of battery drain per hour, which is even better than my OnePlus 7 Pro got (and I used this kernel on that phone as well). I have exactly 300 apps right now and getting battery life like this with that number of apps is almost unheard of. This is only possible because of this kernel. My phone's performance hasn't suffered in any way, shape, or form either. In fact, it's faster than ever, and I'm generally very picky about performance.

Basically, I'm very very happy with this phone all because of this kernel! It has definitely made life easier, and I'm very thankful for all the work you've put into it. I'm very excited to see what comes in the future!
[Google Pixel 6 Pro] Zetsubou Sensei:
As @triggerhappy_ said, if you're not a "techy person" I would recommend NOT doing this.

There is always a chance you may *permanently* destroy your phone. If that's a financial risk you're willing to take as someone who doesn't have the experience to try to remedy it, go for it.

To be clear, you could do everything right and still have something fail bc your computer hiccuped during a critical file transfer. Unless you're willing to potentially spend hours bringing your device back from an unwarranty-able dead, do NOT do this.
[Google Pixel 6 Pro] Phascinate:
I'm experiencing a strange bug. I'm on Android 13 and my CPU literally can't go above 1197MHz or 1436 MHz on the fastest cores, even when the screen is on. If I understand the AK3 module correctly, it's supposed to limit the CPU while the screen is off, and then go back to normal when it turns back on. This isn't happening unfortunately.

And even in EXKM, I can't change the max CPU frequency at all. It just changes right back.

Is there anything you can do about this? I can't play certain games at all. The CPU is too limited.

Additionally, I don't have any apps that are authorized to use root that would modify the CPU in any way, shape, or form (I even disabled EXKM's root access). And I just have the AK3 module in Magisk. So nothing should be causing this. Also, this happens even after a reboot. And I'm not experiencing thermal throttling. I even tried putting my phone in the freezer for a while. No change.
[Google Pixel 6 Pro] Freak07:
That's normal behaviour. You're not supposed to change the min/max cpufreqs manually.

Thermal-hal and power-hal both control these dynamically, based on device temperature and certain scenarios like touching the screen, opening apps, camera etc. If you change them, those will immediately change it back.

If you tap the live frequency view in exkm you'll see it uses higher freqs as well on the frequency distribution. Or hit reset in the frequency distribution, navigate a bit through your phone, open a few apps and check again.

If thermal-hal is active and restricts freqs constantly, you're running into thermal throttling.

Edit: @Phascinate you might have forgotten you enabled the batterysaver mode in CleanSlate config app. That restricts to exactly those freqs too.
[Google Pixel 6 Pro] scloutkst:
4.1.0 flashed and running fine for me on September patch.
[Google Pixel 6 Pro] Freak07:
thanks for the heads up! :)
[Google Pixel 6 Pro] Freak07:
Google released the sources earlier as usual it seems :)

Seems like only some minimal changes.
[Google Pixel 6 Pro] Freak07:
Soon :)
[Google Pixel 6 Pro] Freak07:
Update to 4.1.6

Hey guys and girls,

I hope everyone started into a good week. Here´s the next release. Kind of a surprise update from Google, I suspected it would drop next Monday.

But here we go, the next update including the September security patch. The updates to the main kernel we already had in advance by having upstream merged. The other change is in the bms submodule, which controls charging.

Amongst linux-stable upstream there are a few other updates in this kernel, which I´ll mention shortly in the changelog.

Kernel is compiled for stable A13, not A13 QPR Beta!

I wish everyone a nice day.

If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.

Changelog:

- Linux-Stable bumped to 5.10.141

- scheduler improvements from linux-mainline

Spoiler content hidden.

- updates from kernel/common

Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.

I wish everybody a great day/evening!

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
[Google Pixel 6 Pro] Gordietm:
Thanks for the quick update. Donation sent. 😀
[Google Pixel 6 Pro] bleez99:
@Freak07

Thank you. Have a green tea on me.
[Google Pixel 6 Pro] dd805bb:
I can confirm the frequency problems with AK3 and or kernel to stock. Just updated to see what would happen during start. Mine stayed at max frequencies on all cores then slowly came back down. With AK3 it didn't allow it to max out cores during boot. Using AK3 for me has always given problems. Mine also would hold during sleep at about middle frequency on all and not drop. My middle frequency on all cores would have most time and minimal on sleep and max. Just after updating to September patch and stock kernel, after just 10 minutes I see time on all different frequencies on all cores.. I noticed once custom kernels started using AK3, this has been an issue for me. Also, if the frequencies are dependent on system processes, why would a module be needed to hold those down? Wouldn't that conflict like changing them ourselves? System processes control it but the module limits it, right there sounds like a conflict if system processes need higher frequency with the screen off.
[Google Pixel 6 Pro] Archie k:
Thank you
[Google Pixel 6 Pro] dd805bb:
I have used this kernel on this device and many others. Like the pixel 3 xl.. I stopped using kernels once AK3 was introduced. Problems across many devices. I tried helping the issue before, but can't help someone who thinks OnePlus is the defacto on Android. I used a few different UI apps to all see the same frequency issues. Now it's been a day since I updated, and I can see without a restart since yesterday, all my frequencies have been used at one time or another. Not real time but total calculated time via UI app. Dev check to be specific. I read your post and the last frequency set you list is the only one my phone ever used.. max frequencies would be stuck at that set you list and lowest possible frequency would go to variable.. battery drop whenever using the phone with games. And hard..like 10% in 10 minutes. Maybe get a total of 2 hours screen time total all day. I am at 2 hours screen time right now and have 83% battery. That is great for me. The past month has been charge the phone by lunch if I use anything that needed high power, my theory, it didn't get to use the high power therefore it would over use battery to compensate for not being able to run higher frequencies. Also lag issues once in awhile watching movies, buffering on perfect cell reception. Most of the time the kernel worked great. But, I would get once in awhile a freeze when opening the phone(not being able to go into higher frequencies). This was never an issue before on stock and isn't now. OnePlus isn't android. AK3 dev uses OnePlus as his defacto. He should use AOSP or a Pixel as defacto. That is the biggest issue with AK3.
[Google Pixel 6 Pro] Freak07:
I can't reproduce any of those issues.

But if stock is working fine for you, just use stock. 👍

I'm sorry but this thread is not about AK3, so I won't comment on anything regarding, also due to the fact that a few of those statements have no basis in fact.

There's a thread for AK3 on XDA.
[Google Pixel 6 Pro] Badger50:
Moderator Announcement
​

Thread aggressively cleaned! A friendly reminder to all. While it is always ok to ask legitimate questions of any Developer, starting an OT slugfest is definitely not ok!

Please be aware that posting argumentative statements, and responding to these statements with your own rebuttals is disrepectful at best to the thread owner who contributes

countless hours to his kernels in order to share them for free on XDA. So please just report member misconduct, and let the Mods take it from there.

Going forward. Should this occur again, I will have no hesitation in banning members from participating in this thread out of respect for the Developer

and in accordance with XDA Rules for member conduct:

So please, keep this thread on topic and respectful to the Developer as well as towards each other. As a member of XDA for 11 years, I have seen more than one Developer

leave XDA due to this kind of behavior, which we definitely do not want to see. After all, without the Dev's, what would we have to talk about??

Thank you all for your cooperation, and a pleasant day to all.

-Best regards: Badger50
[Google Pixel 6 Pro] reddvilzz:
Hi, I was trying to restore the stock image after installing the kernel for an OTA update.

I already removed the magisk modules and uninstall magisk, then adb reboot bootloader

but on the bootloader my devices can't be detected

what seems to go wrong? I tried installing the latest usb driver from google and rebooted but when I type adb devices it won't show anything.

and now I can't start my phone, it will bootloop back to recovery
[Google Pixel 6 Pro] Freak07:
If you uninstall magisk it will restore stock boot.img. Since this kernel modifies other partitions as well (including boot.img), you need to restore those too, otherwise you end up with a Frankenstein device that won't work. (boot.img from stock firmware, other partitions from my kernel)

To restore to stock images please read the FAQ, it mentions the partitions you need to flash.

Sounds like your fastboot drivers are not up to date, if the device is not detected in fastboot/bootloader.

So the easiest now is to dirty flash the firmware you're currently on, either via factory image or try the web tool as both will restore all the partitions. If you haven't already done so, make sure to flash A13 firmware to both slots.
[Google Pixel 6 Pro] reddvilzz:
Okay I think I did wrong, because I was panicking my device not showing on adb devices, but since I'm on fastboot it should be fastboot devices.

Managed to flash everything back to stock from boot.img dtbo.img vendor_boot.img vendor_dlkm.img and now can't get pass the corrupt device screen.

I flashed the boot.img twice but it still not working.
[Google Pixel 6 Pro] Freak07:
That usually happens when the device can´t boot, due to the images not matching.

I´d try dirty flashing the entire firmware you´re currently on. That should get rid of it hopefully.

Alternatively use the trick of flashing an older boot.img like also described in the FAQ. But I think your issue is a different one, so try dirty flashing complete firmware first.
[Google Pixel 6 Pro] reddvilzz:
Dirty flashing with the meaning of?

I've flashed this 4 (boot.img dtbo.img vendor_boot.img vendor_dlkm.img) using the stock firmware from image-oriole-sp2a.220505.002

I was on this version I think, but only flashed with this kernel.
[Google Pixel 6 Pro] Freak07:
Dirty flashing means you reflash the firmware package without wiping data. (y)

I guess by restoring the backed up magisk image, and the following boots which failed something got scrambled. That's why I suggest the above.
[Google Pixel 6 Pro] reddvilzz:
But I already flashed this 4 (boot.img dtbo.img vendor_boot.img vendor_dlkm.img) even though I restore the backed up version from magisk, I reflashed the boot.img from the firmware package.

Should I just flashed the version before? Or do I wipe the data then try flashing the firmware package again?

Because I haven't wipe anything so far after restoring to stock.
[Google Pixel 6 Pro] Freak07:
I don't know what exactly happened for you. That's why I can't tell you exact steps to get you out of this.

If you don't have a problem wiping your data just clean flash the entire firmware you're currently running. That should get you up and running to take the OTA.

If you want to try keeping your data intact, dirty flash the firmware.
[Google Pixel 6 Pro] reddvilzz:
How do I clean flash?

I tried flashing april firmware back and it gave me the same corrupted error, then I flashed back the may firmware, there were no corrupted error until I flash vendor_dlkm.img, then it errors again.

Can I just flash into July firmware directly? (Requirement for the custom ROM)
[Google Pixel 6 Pro] capntrips:
Might want to include vbmeta, since it gets patched during AK3 flash.
[Google Pixel 6 Pro] reddvilzz:
Which vbmeta? all 3 vbmeta.img, vbmeta_system.img, and vbmeta_vendor.img?
[Google Pixel 6 Pro] capntrips:
only vbmeta.img