yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Here's a clue:

Lines 95 and 96 in update-binary

device="$(getprop ro.product.device)";

product="$(getprop ro.build.product)";

Errors from fkm log:

/tmp/update-binary: line 95: getprop: Too many symbolic links encountered

/tmp/update-binary: line 96: getprop: Too many symbolic links encountered

Note that bypassing the device check by setting do.devicecheck=0 does work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Ah yes logs are helpful.

Are your devices running in SAR Magisk or SARCompat Magisk?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Pretty sure it's SAR, but how can I verify? I'm also running Canary. Pixel 3 XL (this device) is also topjohn's daily driver (if I'm not mistaken).

Also - check pm.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
SAR if there is no /system or /system_root system partition mounts, and instead the mount is / for system partition.

It should be SAR since Kirisakura doesn't inject anything into /overlay (which would cause Magisk to fallback), but if there were dirty flashes from other kernels or other mods involved it could go either way.

:good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Oh man, so after way too long this evening walking manually through the FKM flashing setup and AK3 Backend with the awesome help of [MENTION=4487388]jcmm11[/MENTION] (:highfive:) we came to the realization that [MENTION=3428502]Freak07[/MENTION] actually isn't using AK3 at all (or even the final revision of AK2) yet, and that this was indeed part of the problem. :eek:

Here's where the latest Kirisakura 3.4.3 zip is at: https://github.com/osm0sis/AnyKerne...r=958b2c873ab36f52c4830b3bb224c3753d5c47cd+74 (Oct 2018)

The device check happens while unmounted on this old AK2 revision, which works fine in recovery, but does not work at all with the new [MENTION=4470081]topjohnwu[/MENTION] booted flashing setup in FKM since getprop is in /system. This AK2 commit from Dec 2018 is what fixes that: https://github.com/osm0sis/AnyKernel3/commit/77fe6bffebffb7561490bec0e4998d6175f904f4

There were AK2 fixes all the way up to May 10, 2019 before I stopped for the rest of the month to focus on the AK3 rewrite, and I actually spent a lot of time in that rewrite making sure that the transition from AK2 to AK3 was about as painless as any other AK* core or Backend update, so it hurts me to see a popular kernel so far behind. :(

Honestly, pretty much all you need to do is drop the latest AK3 GitHub master HEAD update-binary and ak3-core.sh (and tools) into the current zip and it'll function.

What further made this all confusing was that it worked in EXKM, but it turns out that was a bit of a red herring because [MENTION=4684315]flar2[/MENTION] added a clever little workaround to keep /system from ever becoming unmounted, which happens to also avoid the above issue nicely. Many thanks to [MENTION=4684315]flar2[/MENTION] for sharing that workaround, and it should be added to FKM for the next release, but that said, everyone please pester your kernel devs to update to AK3 as soon as possible, you and they are missing out on a lot of important fixes and improvements. :good::)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hello everybody,

thanks to [MENTION=4544860]osm0sis[/MENTION] for the troubleshooting. also thanks to [MENTION=4487388]jcmm11[/MENTION] for the help.

I´m sorry I caused all this confusion by not updating AnyKernel to the latest state.

I was working the last few weeks on a Q kernel for the Pixel 3 XL. Sadly with the CAF SDX merge, the kernel is not booting for me. I had no success in getting it to work so far.

That´s one of the reasons why I was quiet in here.

I´m also quite busy with real life stuff, that´s the other reason.

Please test the attached kernel, so that it works correctly when flashed via EXKM, FKM or TWRP.

I cannot test it on Pie currently as my device is on Q, and I cannot constantly set up my phone freshly :(

It would be great if we all could work together here.

I apologize to [MENTION=4544860]osm0sis[/MENTION] to have wasted his time on debugging something, that was a non issue, even if it lead to some result in the end.

My fault and I hope this zip works for you all now.

I´m away this weekend, so please report back, so I can hopefully release this kernel!

Edit: uploading to XDA attachements doesn´t seem to work currently. Please use this link instead:

https://www.androidfilehost.com/?fid=6006931924117929019
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SacredDeviL666:
Thanks man as always for keeping up and fixing the bugs highlighted :good:

[MENTION=3428502]Freak07[/MENTION] least i could do, i have added the kernel as an attachment in your post now :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 123SIT:
TWRP 3.3.1-2 flashed it with no issues and it boots fine.

EXKM didn't fair so well, image attached. Appreciate you.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
I had same kernel v. 3.4.4 flashing experience as the poster above, EXKM failed with the same error, flashed with TWRP 3.3.1-2 and seems to be running fine
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
[MENTION=634006]123SIT[/MENTION] [MENTION=9595880]lukefgoogler[/MENTION]

I don't have EXKM so can't test this myself but 2 things to try.

1) make sure you're using the latest version of EXKM

2) try clearing recents to free up some memory.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Try this one guys. :fingers-crossed:

Be aware I cleaned up a lot of the anykernel.sh stuff Freak07 included for dtb and dtbo patching, so now it will actually attempt to patch both. So if that eats sh*t on custom ROMs, my apologies, just make sure you have a dtbo partition backup first and know how to restore it. :cowboy:

Let me know how it goes!

Kirisakura_Bluecross_3.4.4-fixed.zip:

https://basketbuild.com/filedl/devs...s/osmods/Kirisakura_Bluecross_3.4.4-fixed.zip

Edit: I guess flashing previous 3.4.4 in recovery would work too to restore a working dtbo. :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Well it still works under FKM. Install log attached (looks somewhat cleaner ? )
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Works with exkm. Thanks for fixing the issues
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
Installed through exkm without any problems but I got stuck on the "Pixel is starting" screen. Reverted back to the previous version by installing through twrp and I am bakc to working again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Ughhh man, we gotta fix that line spacing issue in the FKM log now that the in-app display is pretty. :laugh:

What ROM are each of you on?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
Sorry getting used to relaying that information:

Stock rom July update

Modules installed:

Viper4android legacy

Zram

System less hosts

Energized

Active edge
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Confusing, since [MENTION=4487388]jcmm11[/MENTION] was also on Stock July and it worked for him. It shouldn't patch dtbo on stock so it should always be fine. :confused:

Log would be helpful.

Try again from a clean boot.img?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Stock July
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Okay so [MENTION=817130]brandonpa[/MENTION] is the odd one out on Stock having issues. Must be something weird with his config? Definitely he should try again from a clean boot.img.

Anybody on a custom ROM that can confirm if my updated zip works or not? That was more what I wasn't sure about.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SacredDeviL666:
Blueline, AOSIP, flashed via EXKM & FKM both works fine/boots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=4487388]jcmm11[/MENTION], your zip flashed fine here running DU ??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
What about this one? :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
All good as well! Nice work ??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Awesome, so that's AOSIP and DU reported working, and 2 out of 3 Stock people reporting it works, so it probably works fine! Winner winner chicken dinner. ;)

Here's a final upload with only cosmetic changes.

Kirisakura_Bluecross_3.4.4_Release-Fixed.zip:

https://basketbuild.com/filedl/devs.../Kirisakura_Bluecross_3.4.4_Release-Fixed.zip

I'll let [MENTION=3428502]Freak07[/MENTION] know and he can hopefully upkeep the zip from here. :highfive:

Edit: Oh, just to be 100% certain, can one of you custom ROM guys show me the log from a flash of my updated zip?

Edit 2: Looks perfect. :D
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I don't know if it is kernel related, maybe does with RAM management, but my music apps (Qobuz, Soundcloud), stop playing music when switching between other apps.

*since last update and without using zRam
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
This one's for you ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=4544860]osm0sis[/MENTION], flashed and log attached.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=4544860]osm0sis[/MENTION], saw this ??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Is this for just Pie?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Yes. He's working on Q, but it's not ready yet
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
3.4.4 fixed flashed with EXK work perfectly on August update! ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey guys and girls,

So here is the next update for you guys. I´m very short on time right now, as you might have noticed... I try to give my best at updating this kernel though.

I was away the whole weekend and so [MENTION=4544860]osm0sis[/MENTION] helped me getting the anykernel 3 zip up and running properly.

A very big thanks to [MENTION=4544860]osm0sis[/MENTION] at this place for taking the time to help me!

Also [MENTION=4487388]jcmm11[/MENTION] for testing!

The last weeks I spent time on working on a Q kernel, which has also the complete CAF SDX source merged, like we have currently.

Sadly I had no success and I have to see where it´s going once Q officially drops for the Pixel 3/XL.

What further complicated things, is that I just don´t have the time to constantly jump between Q and Pie at the moment.

So I hope everything is working properly for you guys. Please report back in case it isn´t. Don´t forget to include logs and take a look at the 2nd and 3rd post :)

I wish everybody a nice day/evening! :)

Changelog:

Kernel Base Changes

- Merge August Security Update (empty commit, there are no changes in august this kernel doesn´t have already :) )

- Merge 4.9.186 and 4.9.187

- follow kernel/common

- fix incompatabilites from the Q merge

- fix random reboots introduced by 3.4.0

Important :)

All flashing errors are now fixed. If you experience the ramdisk error please take a look at the FAQ.

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

Download is below :)

Download:

https://www.androidfilehost.com/?fid=6006931924117930923

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post too :)

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 3 XL ROMs, Kernels, Recoveries, & Oth] jstoik:
3.4.5 flashed A-OK for me with TWRP on DU (Magisk, no modules). Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
Installed using exkm without a problem and so far working well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
noticed that charging while powered off no longer provides stock experience i.e. percentage
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
that´s caused by having magisk installed. pretty sure it happens on the stock kernel with magisk too.

can remember this issue from the pixel 2/xl.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] exile1ck:
Is it possible to flash this to q beta 6?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] evilryry:
I don't want to sound rude but if you read into the thread even on this same page of comments you would get your answer..this has been asked several times now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Have you removed all of Sultans commit / stuff from your kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
what exactly are you talking about?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] andrewhahalee:
A bit random, but thanks for being the only upstream crosshatch kernel developer that keeps performance close to stock. (At least on xda). A couple of kernels shipped with a custom roms often run into some scrolling lag issues and feels a little too clunky.

I'm personally fine with today's flagships and their battery life so making any "enhancement tweaks" to improve it don't really matter for me.

The one strange behavior I'm getting on the latest version is that apps in recents are re-loading when I switch back to them after a min or so as if they're opening again for the first time. This increases the app switching/opening time as the screen freezes for around 2 secs while the app re-loads.

(I'm on DU, Crosshatch, if you need any info).

Thanks again and keep up the great work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jstoik:
Do you have any Magisk modules installed, or apps like Greenify? Or maybe a regular app that is hogging all the memory? Is your phone running hot (it is summer here, and my Pixel isn't happy about it!), might be a consequence of throttling...

The reason I ask is I'm running DU/Crosshatch too and haven't noticed app reloads like you're describing. Doesn't mean much, but could be any of a million causes.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] matssa:
I too have the same issue and the phone gets ridiculously slow and unresponsive. And you're talking about greenify, is it a crappy app that hogs everything? Indeed it turns on each time the screen goes off to kill the apps and save battery but can't really know if it helps (at least it kills correctly Facebook and messenger in order to avoid push notifications).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Recent posts (now deleted) read as extremely disrespectful to a hard working community developer. Don't pressure for Q updates, please.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SacredDeviL666:
Thread Cleaned.

Keep the discussion relevant to the Op/Kernel if not keep it out of this thread.

You don't like someones response? Ignore - move ahead/Report - if its against forum rules.

Avoid cluttering a dev thread with unwanted discussion/topic so other users can benefit from the discussion happening here.

Thanks

SacredDeviL666.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Hey you did the same thing to me on rooting guide thread, and now pages of the problems I talked about months ago you deleted. I thought we are supposed to help each other here? Fact are facts. Here is what you do, email Google and tell them not to release Q and keep supporting pie on the pixel phones. Lol. See ya in few months when everyone is scrambling as to what works on Q. Lol. Being a head of schedule is not demanding or flaming anyone. Time is going to happen. But hey, keep everyone on our till last minute and not tell the truth to anyone. The new XDA way. Hey sacred devil666, should I expect emails of someone trying hack my Google account now? From 5he east coast again?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mark manning:
This is a PSA to all: Above is what happens when you don't wear your tinfoil hat like you are supposed to!!

In all seriousness, [MENTION=8563490]S8rooted&tooted[/MENTION] XDA is not Telegram so when you come back, please remember we do our very best to keep a peaceful forum at all times. We do demand that all members show respect to one another regardless if you like or agree with them. That does extend to our staff members as well. If you think a moderator hacked you, feel free to PM me and provide 100% proof rather than going on an incoherent rant in the open forum.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I updated to 3.4.5 from 3.3.4 for something like a week now and I have issues with RAM management.

As I said in a previous message, music apps sometimes kill themselves when I use other apps and today a book I was reading on Word reloaded just after I used Google app to search something about what I was reading.

Nobody noticed more RAM management issues than with previous Kirisakura kernel versions?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] matssa:
I did indeed however I was using greenify, so I disabled it and flashed again the stock factory image, then latest kernel then magisk 19.3 (was on canary before as well). For now the ROM seems fast but didn't test YouTube since then, I'm comparing first the battery drain
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
[JOKE]Uh oh! I didn't realize we were supposed to wear tinfoil hats around here! Anybody have some recommendations on where I can pick up a quality hat, or maybe a good DIY for making my own?[/JOKE]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dijia1124:
Cpu Min frequency stuck on 652 instead of 576 ?

Tried reflash the ROM and reflash magisk+kernel

Everytime after reboot it's 576 but several minutes later it becomes 652

Edited : Uninstalled Zram Enabler , back to normal

Edited : Still the same

Reedited : Sorry it's not kernel related..
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Last several versions of this kernel/android my battery life has diminished noticeably.

Before previously I was enjoying 5-6 hrs SOT and a days worth of battery, the last couple months I get 3-4 SOT and I usually need to charge towards the end of the day.

Just curious if anyone else has had similar behavior to see if I can root it out.

I have changed nothing that I can think in my setup.

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I also saw my battery life diminish by more than 10%.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
I read something about how this is related to the latest Google Play Services and is affecting all Android devices. https://news.google.com/articles/CA...9935CjCe0eYCMNLmzAU?hl=en-US&gl=US&ceid=US:en
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] glehel:
this is what I experienced! my base is 652 mhz after a while. I'm using aosip rom. With the Aosip kernel, there is no problem with the base of 300MHz.

There are times when this problem comes up, but now after 2 days of use, 576Mhz of base and stable has not come up.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I don’t think it’s the kernel that causes this. The kernel itself causes no drain. It just provides resources for apps, services etc if they request it. There were no major changes in the last few updates.

It’s best to check with an app like better battery stats if any app is keeping the phone awake constantly.

Like somebody else said play services are known to cause this behaviour occasionally.

Our SOC is intended to be used with a min frequency of 576mhz for the little cluster.

Some custom roms force this down to 300mhz, but it’s causing scrolling lag/stuttering for some people.

Qualcomm intends that 576mhz is the minfreq for the little cluster, as it’s the most efficient one.

If your device uses solely 652mhz and not 576mhz it means, that an app or a service requests resources in the background.

To determine the app go to a terminal app and type (without the “ ”):

“su” then hit enter and grant superuser access

Then type “top”

Now observe the console and try to see if a process is constantly at the top and maybe doesn’t belong there.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
Now that you mention it I am having similar issues with programs closing very quickly and with the music apps. I didn't really attribute it to the kernal but could be possible I guess.

I don't have any specific ram or memory management programs installed.

Stock rooted August update

Busybox

Active edge

Energized

Viper4android legacy

System less hosts

Zram management
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Well you have installed a module called “zram management” that’s very memory related?

No idea what exactly it changes, but that might well be the cause.

Another reason might be an app constantly sucking up resources in the background.

There were no changes to memory management in the kernel for a few releases now.

3.4.0 introduced lzo-rle as zram compression algorithm, but if you do not explicitly set it as default algorithm, it has no effects at all, since lz4 is the default algorithm.

It seems many people have issues like music apps closing in the background.

See here: https://issuetracker.google.com/issues/118347903

I tried to change a few things to make it at least a “bit” better on my kernel, but there is only so far you can do when being limited to 4gb of RAM.

I never had problems like music app being killed in the background or photos not being saved.

There are a few popular (mostly social media) apps out there which are extremely RAM hungry and might lead to problems. Luckily I don’t use any of these.

Q will introduce some big changes to memory management that rely on kernel side stuff, as well as actual rom related stuff.

It’s pretty interesting and I like the approach. There’s a patchseries, which introduce the psi monitor functionality to the kernel. The rom side lmk needs to be patched so it’s able to make use of the information provided by the psi monitor.

I ported this to my personal kernel a few months ago and also needed to compile myself a rom with the required changes. It works better in my opinion, but keep in mind 4gb of ram will stay 4gb of ram.

Q will drop soon I guess, so if Google doesn’t decide to ditch these changes last minute everybody will benefit from this (hopefully).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I had those issues even after ditching the zram module when I thought my ram management suffered because of it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes like I said there’s certainly a limitation with 4gb of RAM (plus ZRAM) that some seem to hit earlier/faster than others.

It could be a Google play services update, which introduced something that takes more ram suddenly, some other updated app, there’s a big list.

Something entirely else in the system, some change of usage that the user isn’t aware of.

I’m pretty sure it’s not the kernel, but I cannot be of more help there. :(
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lessaj:
It's not really kernel related specifically, I don't run this kernel but this morning while I was streaming music over bluetooth I opened Snapchat to see what my friend sent me and Play Music was killed, yet I left a YouTube video in the background all day and it was totally fine. It just depends what else is in the background and what LMK decides to kill. PSI should help, and even the other upcoming Low-Memory-Monitor project for the linux kernel could make its way to android too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dethknite:
IMO, disabling "usage access" for "Digital Wellbeing", as well as increasinge zram to 2GB has kept everything fluid and great in terms of RAM for months. YMMV.