yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Poesini:
Anyone else experiencing edge (and near edge) press and hold not doing anything?

For me, ProtonAOSP 12.3.2, 3.0.1, while I can move the cursor around no problem, but I noticed when I was trying to erase something in the keyboard, that I could not press and hold the delete key, but I could press it multiple times...

This only happens on the edge and near edge of the display... At least just for me...

Anyone else can replicate this?
[Google Pixel 6 Pro] capntrips:
Would you mind sharing your AK3 log from 3.0.1?

Edit: and which ROM?
[Google Pixel 6 Pro] Minnesinger:
Try rebooting into safe mode, do something to launch your keyboard, then reboot as normal. Should resolve. It's worked for me on previous versions of Proton.

Surprised you're able to run 3.0.1 on Proton 12.3.2. I thought the firmware was incompatible?
[Google Pixel 6 Pro] Poesini:
I tried rebooting into safe mode and now the phone won't start... It is stuck on the logo (not the Google one)

Is there a way to disable safe mode? (I can provide adb commands while the logo is there, but no su)

EDIT: I "fixed" it by flashing ProtonAOSP 12.3.2 again (not losing data) and, stock boot.img worked and Magisk 25001 patched stock boot.img worked
[Google Pixel 6 Pro] roirraW "edor" ehT:
The reason it wouldn't boot is because the kernel depends on the AK3 Magisk Module, and safe mode disables ask Magisk Modules.
[Google Pixel 6 Pro] Poesini:
It is weird, because now I "can't" flash the kernel right now... Well, I can, but it will be stuck on the boot logo again... Any help here?

EDIT: How can I check if it is booting into safe mode without looking at the bottom corner? (For obvious reasons, I can't)... And if possible, any way to disable it? I managed to get su working while on the working kernels, so now I can get su through adb

EDIT2: Clean flash with formatted data and kernel won't boot past logo anymore... Weird
[Google Pixel 6 Pro] Schnedi:
Rom compiled by me: https://github.com/RealSchnedi?tab=repositories

Do you mean these?
[Google Pixel 6 Pro] capntrips:
Yes, thanks. It looks like you either have either verity or verification disabled or your ROM doesn't have avb enabled in fstab, so the issue doesn't appear to be Hashtree Patcher. If you can share your ramoops after the bootloop, maybe something will pop out. Note that if you boot into fastbootd or recovery, it will wipe ramoops from the bootloop, so you won't be able to flash vendor_dlkm. In my experience it will still boot and adb will work, but you won't be able to use your touchscreen, but you only need to run that way long enough to grab the file over adb.
[Google Pixel 6 Pro] Freak07:
That might be because proton doesn't yet incorporate the qpr changes for Touchscreen on the firmware side as June firmware now does. (that's also one of the reasons why separate builds were needed for stable A12 and qpr3 beta in the past months.)

I wouldn't know if that's the cause as i don't follow development for proton and I'm a happy camper on stock.

Sorry, based on your posts i don't know what's up with that.

If you flash back the stock images as described in the FAQ, the magisk module will delete itself and everything the kernel changed should be undone. But you achieved the same by dirty flashing/ clean flashing so I have no idea sorry.
[Google Pixel 6 Pro] Poesini:
Yeah, no worries... I just like Proton because it is pretty much stock with a little bit more of privacy

Now I'm back to Magisk 23000 and 2.4.0
[Google Pixel 6 Pro] spr33:
Will the latest kernel work on 12L (12.1) SQ3A build?
[Google Pixel 6 Pro] Freak07:
That's the stable June firmware, so yes it will.
[Google Pixel 6 Pro] spr33:
Oh, interesting! Looks like Google have migrated QPR3 users away from beta now..
[Google Pixel 6 Pro] roirraW "edor" ehT:
QPR stands for Quarterly Platform Release. Four times a year, Google will supposedly release a bigger update, and have Betas for them, such as you were on. The QPR3 you were on was the Beta for the Jun 2022 update. When you're running a QPR Beta and the final, Stable version releases, you are put back on Stable since it is the next logical step from the previous QPR3 Beta you were on.

Next month there will be a Beta 1 for QPR4. You can re-opt back into it then, or manually flash it - whichever is your preferred method. It will go final / Stable with September's update.
[Google Pixel 6 Pro] Lughnasadh:
If I'm not mistaken (which happens once in a blue moon 🙃), I don't believe there is a QPR4. I think they are labeled QPR 0-3, with QPR 0 always being designated for the first major, stable OS release.

The QPR beta program for Android 12 essentially ended with the June/Stable QPR3 release. Since the next QPR release will be for Android 13 in (roughly) September, there will be no more QPR Beta releases until after that is released. That release should be QPR 0 for Android 13 and the QPR Beta program for that should start soon afterwards since Google confirmed they will continue to have a QPR Beta program for Android 13.

Hope this makes sense...
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks, yes, makes absolute sense.
[Google Pixel 6 Pro] slacker126:
Random question of the day. Tried to play Fortnite today and says during loading that it encountered an error due to the graphics driver being incompatible.

Any ideas for this?
[Google Pixel 6 Pro] slacker126:
@Freak07 any suggestions?
[Google Pixel 6 Pro] Freak07:
I tried to replicate the issue but wasn´t able to running 3.0.1.

Downloaded the whole game (seems like the size of games on android grew just like PC games during the last few years) and I´m able to get into the actual game and play just fine on my end (after disabling usb-debugging). No crash on the loading screen or other crashes for me.

Maybe try to clear cache or re-install the game.
[Google Pixel 6 Pro] slacker126:
So tried cache and storage...didn't change anything. Had to completely uninstall and reinstall. Works as advertised. No idea how I got that error...thank you sir
[Google Pixel 6 Pro] i42o:
Well this run on Android 13 by any chance?
[Google Pixel 6 Pro] jericho246:
The beta? Most likely not.
[Google Pixel 6 Pro] Freak07:
No, it's for A12 June update.
[Google Pixel 6 Pro] Israafil:
Is it possible to increase CPU max freq?? Google initially run the little cluster with 2 ghz and changed it later to 1.8 ghz etc.
[Google Pixel 6 Pro] Penguin414:
Is this a bug?
[Google Pixel 6 Pro] TotallyAnxious:
There's little to no benefit to modifying anything in entropy
[Google Pixel 6 Pro] Freak07:
It´s possible, but there´s little to no benefit except higher benchmark scores if the phone is in a cool environment.

If the ambient temps are higher, performance can be worse due to faster throttling with added OC.

Might be due to LRNG being updated to latest and an incompatibility with that particular kernel manager.
[Google Pixel 6 Pro] awarman:
Well Magisk 25.1 is out. Has anyone successfully flashed it? I updated the apk but I'm hesitant based on previous experience to update the image.
[Google Pixel 6 Pro] bleez99:
Yup, it's all good.
[Google Pixel 6 Pro] bleez99:
What could possibly go wrong :devilish:.

Actually, I was playing with Canary, had no issues, and went to Stable with no issues at all.
[Google Pixel 6 Pro] mhrussell1:
I can no longer select Canary as my update channel. Do I now have to select Custom and then put Canary in custom selection?
[Google Pixel 6 Pro] bleez99:
You're not able to do so because this is a released, signed APK. Not sure where to find the JSON anymore for the custom.

If you really want Canary, go to John Wu's github page and grab app-release.apk

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] mhrussell1:
OK. I found the canary apk. Do you know if I can install it on top of 25.1 and it will still work?
[Google Pixel 6 Pro] bleez99:
You should. It should replace what you have installed. If you have a hard time uninstall just the APK, don't do it though the manager, i think it will wipe out the data.
[Google Pixel 6 Pro] Paz9:
Loving this kernel so far, however I noticed stock is a little more fluid and snappy? Has this got something to do with the power mods?
[Google Pixel 6 Pro] Freak07:
Not the case for me. It's the other way around as i did a lot of profiling and tracing not based on feeling. Might be something going on in background, thermal throttling etc.

I guess it's not impossible that a specific app performs worse due to some scheduler changes than stock. But in that case there might be a way for me to reproduce whatever you're experiencing, then check what's happening based on that and decide if something can be done about it or not.

You can check via top command if something is hogging the CPU for example. (Please search the thread on how to do this)

That's probably the first thing I'd do, as it puts more stress to CPU slowing other things down and also causing inevitably more heat and thermal throttling causing everything to slow down further.
[Google Pixel 6 Pro] awarman:
I upgraded to 25.1 and also had no issues.
[Google Pixel 6 Pro] Paz9:
Thank you, I'll give it a check to see if a rogue app is on the loose, curious is it possible to run the msgisk module on a stock kernel?
[Google Pixel 6 Pro] jericho246:
After searching for a solution to my P6P's heat problem, I found this post

My Pixel 6 Pro gets quite warm during normal use. Normal use meaning absolutely ZERO gaming, just Telegram, Brave Browser, Instagram, YouTube, and Reddit (Infinity client). It doesn't matter how low the brightness is set, the phone's battery always reaches 39-40 degrees Celsius after around 10 minutes of my typical usage. It's my biggest gripe with this device for sure.

I have another phone that I still use, a S21U - Exynos variant. According to BatteryGuru app, the max battery temperature of the S21U is 39 degrees. However I'm pretty sure it only reaches that when charging. When I'm doing my typical thing, it only goes up to 35. That's 4-5 degrees less than the Pixel, and I can feel the difference in my hand. So... is the Pixel 6 Pro getting this warm after performing light-ish tasks, even normal?

Back to the post I quoted above, I flashed KiriSakura kernel once again and this time I enabled the battery saver #1 in the Cleanslate config app. The value of 1 stands for "medium cutback". I guess my question is this: is it recommended to keep it enabled permanently? Like I stated previously, I don't play any games on my phone, my usage is rather basic, so I don't really need the full power of the phone. Thanks in advance for any insight.
[Google Pixel 6 Pro] Freak07:
It's difficult to compare those battery temp numbers across different devices in absolutes.

The battery temp displayed by exkm, fkm, battery apps etc is just a calculated value based on whatever sensor or sensors are being used for this and is provided by the framework.

Different devices use different sensors for this.

That means a device where battery temp is being displayed with 39°C can actually "feel" cooler than one with 35°C.

It's a difficult question to answer if that's "normal" or not. It depends on ambient temperature, network coverage (mobile network will always use more power and therefore lead to more heat), your unique setup, background processes, your usage pattern etc.

If I'm using my p6pro inside (it's summer here) on wifi and ambient temp inside is around 22-25°C with light usage I'd say I'm landing at 30-33°C battery temp after 10 minutes. (Those temps are from exkm, i don't know if batteryguru uses other sensors/values)

With the exact same usage outside, mobile network in direct sunlight and 27-30°C, it gets close to 40°C quite quickly.

If the phone really heats up that quickly inside and your ambient temp is rather low, you're using WiFi and your usage is rather light, I'd suggest using top command from time to time to check if an app is hogging the CPU in background. (Check the thread here on how to do that)

Yes you can run your phone permanently restricted. On all levels. The biggest impact you'll probably notice is app opening times (especially opening an app the first time) and scrolling could sometimes be impacted.

Just try the different levels and if your usage is not impacted by running on level 3, no harm running your phone that way.
[Google Pixel 6 Pro] pianisttaoyuan@gmail.com:
Hello ！first Day using the kernel, everything is good except the mobile network battery drain was crazy ? It seems like the mobile network is keeping drain my battery during the night.
[Google Pixel 6 Pro] Freak07:
No problems on my end. Using 2-3% during 8 hours overnight.

Mobile network is mainly managed by the radio/baseband and not the kernel.
[Google Pixel 6 Pro] pianisttaoyuan@gmail.com:
Lol seems like the signal tower is under maintenance so that I got the crazy battery drain
[Google Pixel 6 Pro] Paz9:
Sorry if off topic @Freak07 is the ak3 module able to be flashed on stock rooted kernel?
[Google Pixel 6 Pro] Freak07:
No. Not compatible with the stock kernel.
[Google Pixel 6 Pro] beterman:
can i flash the kernel on SparkOS Rom?
[Google Pixel 6 Pro] jericho246:
I can confirm Kirisakura kernel works with SparkOS ROM. That's what I'm currently using on my P6P, works great.
[Google Pixel 6 Pro] sjgoel:
I flashed Kirisakura kernel using the Kernel Flasher app.

Can I delete the Flasher app after having flashed the kernel?
[Google Pixel 6 Pro] Freak07:
Yes. You just have to reinstall the app, if you want to flash again, backup or restore a backup.

Keeping Magisk installed is mandatory though.
[Google Pixel 6 Pro] sjgoel:
Thanks for the quick response.
[Google Pixel 6 Pro] Rodimus8402:
Any music I play stutters a lot when the screen is off, to prevent that do I just need to remove the powerhal Magisk module?

And is there any way to benefit from the module, and no stuttering?

Thanks!
[Google Pixel 6 Pro] Freak07:
No, you're not supposed to remove the magisk module at all. If you remove it, there will be breakage in the background everywhere.

I don't have any stuttering when I listen to music, videos, audio books etc with screen off.

So if it's any type of music playback something else is wrong. No issues here at all.

The p6 pro devices are known (at least in the past) to sometimes have problem with stuttering music when using ldac for Bluetooth playback.

Can you give me exact steps, as detailed as possible, to reproduce the issue as well as logcat and dmesg while the issue happens? (firmware, kernel version, music player app, Bluetooth (Codec)/wired connection, type of music file, mp3, flac, streaming, network type.)
[Google Pixel 6 Pro] Rodimus8402:
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)
[Google Pixel 6 Pro] Rodimus8402:
It's working correctly now, I think the issue was caused by a setting.

Either way I'm good for now, and will use Logcat if the issue pops up again, and will grab all the info you requested beforehand.

Thanks again, cheers!
[Google Pixel 6 Pro] B from C:
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.
[Google Pixel 6 Pro] Freak07:
you´re correct. enabling ttl spoofing support somehow slipped through in the 3.0.x releases. I´ll enable it for the next release.

Thanks for spotting and reporting it! :)
[Google Pixel 6 Pro] _piwaska_:
@Freak07 Can reduce TDP?
[Google Pixel 6 Pro] Freak07:
You can reduce max powerdraw by using CleanSlate battery saver feature accessible via CleanSlate config app.

Due to PMU limiter being enabled max powerdraw might be reduced in certain scenarios as well. info about that should be linked in the OP.
[Google Pixel 6 Pro] _piwaska_:
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.
[Google Pixel 6 Pro] Ghisy:
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.
[Google Pixel 6 Pro] Freak07:
In a way it is.

Straight from the Intel page:

Thermal Design Power (TDP) in Intel® Processors

Provides FAQs about Thermal Design Power (TDP) in Intel® Processors.

www.intel.com

What is Thermal Design Power (TDP)?

TDP stands for Thermal Design Power, in watts, and refers to the power consumption under the maximum theoretical load. Power consumption is less than TDP under lower loads. The TDP is the maximum power that one should be designing the system for. This ensures operation to published specs under the maximum theoretical workload.

Power saver mode or the pmu limiter does exactly that. It limits the power the SOC can draw, by restricting the SoC.

Thereby also reducing generated heat.

But if you want to change thermals per App, that's not possible.

Thermals are also "mostly" regulated outside the kernel via thermal hal.

The article mentions there are no details on the exploit yet as far as i read it. So how should I know? 😁
[Google Pixel 6 Pro] Ghisy:
Whoops, guess I read the article too fast! My bad!
[Google Pixel 6 Pro] Freak07:
No problem :) if you stumble over a link to GitHub or another similar site feel free to share :)
[Google Pixel 6 Pro] Ghisy:
Will do if I come across the actual explanation of the exploit! :)
[Google Pixel 6 Pro] Admiral2145:
Has anyone flashed the July update with this kernel yet?
[Google Pixel 6 Pro] Freak07:
kernel source is already up. I don´t see anything we don´t already have in the current kernel. So it should be fine to flash.

Just tried myself and no issues to report :)
[Google Pixel 6 Pro] bleez99:
Judging from the traffic here the July update was kind of uneventful.

I like it that way.

Thanks @Freak07
[Google Pixel 6 Pro] RogerF81:
Good to know! 🙂 In Europe, the correct factory image is the 001.B1 version, right?
[Google Pixel 6 Pro] Utini:
That depends.

Is your country officially supported by Google?

Is your carrier officially supported by Google?

Where did you buy your phone?

I have no idea myself which one to get or what the difference really are between EMEA and Global.

Last statement I got from Google was: https://xdaforums.com/t/emea-build-is-meant-for-only-these-6-countries-in-europe.4465827/
[Google Pixel 6 Pro] Freak07:
If it´s like in the past the only difference might be the added support (volte/vowifi) for a few carries. So I guess people running in the few EMEA countries with devices where fresh carrier support was added they might want to flash that build.

Otherwise I guess it doesn´t really matter.

That would also play well with the patch note for the added VOLTE support for a few EMEA countries mentioned there:

Google Pixel Update - July 2022 - Google Pixel Community
[Google Pixel 6 Pro] RogerF81:
Very interesting, Google definitely makes it more complicated than necessary. But at least all this answers my question and the answer is yes, I need the EMEA build :)
[Google Pixel 6 Pro] Utini:
Sorry to hijack this thread since it is not kernel related.

But that wouldn't make sense to me? They could just release the EMEA version then?

It would include the "global" settings + the few supported EMEA carriers?

Also, what happens if I flash the "global" build and travel to Germany? :D
[Google Pixel 6 Pro] Freak07:
I think when new "settings" for VOLTE etc are included they diverge sometimes from the main firmware for testing purposes. Since that firmware goes through the testing process as well, they just release a separate build, and merge those changes back in the combined firmware later once they know they´re fine.

You have to keep in mind those firmwares are usually several weeks old when they´re pushed as firmware updates.

Nothing happens. You´re just missing out new stuff for your carrier regarding volte etc. If your phone worked before while traveling to germany, it will continue working.
[Google Pixel 6 Pro] Utini:
Yep makes sense. I also believe that simply installing any of the both (EMEA or Global) will be fine.

Because, we travel with out phones, we might buy it in one country but live in another, and everything still has to work.

Just as you mentioned, we might miss out on a feature.

But if I understand it correctly, by simply installing EMEA we should have all possible features anyway.

Updated answer I got from google:
[Google Pixel 6 Pro] Ghisy:
Hey, so will there be a build for July or can we just flash the current Kirisakura version and be done with it?
[Google Pixel 6 Pro] Badger50:
As per the Master himself. ;)
[Google Pixel 6 Pro] Ghisy:
That's actually the post I quoted above! :P

I wasn't sure if this meant no update for this month or just that the June kernel can be used until there's an update.
[Google Pixel 6 Pro] Utini:
Flashed on july updated. Works fine so far.
[Google Pixel 6 Pro] ffuser1:
If I have an issue with a magisk module and have to reboot into safe mode, will I have issues rebooting because the AK3 Magisk Helper Module will be disabled? Trying to avoid any potential for bootloops or needing to reflash if something were to happen accidentally. Thanks!
[Google Pixel 6 Pro] roirraW "edor" ehT:
I believe so, yes. Just flash the stock rooted kernel in that case. If you hadn't already created a Magisk'd stock July rooted kernel, flash the non-rooted stock kernel, boot up normally, copy over the stock boot.img, root it with the Magisk app, copy it back over to the PC, then you can flash it and boot into safe mode to disable the Magisk Modules.
[Google Pixel 6 Pro] Gytole:
I might make a youtube video on how to do it because I ran into this problem the other day when I updated. Magisk module boot looped me then I remembered the ole safe mode trick. Works everytime.
[Google Pixel 6 Pro] Freak07:
Sounded a bit like a question for an ETA in disguise, which I´m pretty sure @Badger50 was partly replying to with the answer that was given. ;)

I know you meant no harm, yes there will be an udpate.
[Google Pixel 6 Pro] Freak07:
Nice, thanks for editing the post with more info. So more or less like I suspected just carrier stuff :)
[Google Pixel 6 Pro] Freak07:
That was true for release prior to June. Now that the changes required (on kernel and firmware side) for direct usb access to work correctly are included on stable A12 QPR, I no longer need to replace the firmware part for the kernel to work correctly.

You should now be able to at least boot the phone without the magisk module, but a lot of other stuff will be broken, like the powerhal etc. For getting the phone to work again via safe mode it should be fine however. Just don´t forget to flash the kernel afterwards again or re-enable the magisk module, otherwise the device will not run correctly.

That doesn´t change the fact that the magisk module is absolutely mandatory if you want to run the kernel daily. I don´t know why, but this question pops up from time to time.
[Google Pixel 6 Pro] Ghisy:
It may have seemed like an ETA in disguise but it really wasn't. :)

I'm always fine with waiting for you to "do your thing"! 👍
[Google Pixel 6 Pro] Badger50:
Ok fine I will! Great work as always my friend. Nice to be in the P6 crowd now since my P4XL bit the dust last week. 👍👍😉
[Google Pixel 6 Pro] Admiral2145:
Curious... Can I stay on June and flash July kernel?
[Google Pixel 6 Pro] Paz9:
Wouldn't "none" scheduler technically have the least overhead?

I'm interested in this new ssg scheduler too, will be trying it out
[Google Pixel 6 Pro] shizonic:
Thank you very much! Awesome work as always. It feels snappier overall in my opinion.