yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
In EXKM, flash stock boot.img (extract from Dec update and push to phone) don't reboot, then open Magisk and direct install and don't reboot, then in EXKM flash 1.8.5 and reboot. Should work if you're rooted. Good luck [emoji1696]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
How do you flash the kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] El-Lobo68:
Have theme same trouble after clean install Dez.patch.

What helps is simple not use FKM or Ex Manager for this moment.Must be wait for the Dev's updating his great App.

So reboot too BL

Fastboot Boot twrp.img new one!

Then only flash from Recovery Kernel.zip+magisk.zip 18.0 thats all and have fun
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mushages:
i am flashing all versions using exkm app and never had any issue.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I've flashed it with EX manager, but the last couple of updates I flashed in recovery.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
Do you have any magisk modules enabled when you flash through exkm?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
The last several in a row, I've easily installed with flar2's EX Manager. Simple . . . Sweet . . . ? ? Currently, I am not running any magisk modules . . . How about a side by side compare of the logs of two helpers with one passing and one failing ? Is the fail aways with the "unpack" step ? . . I have never deviated from magisk 1.7.3 - the kernel comes along and "reads the tea leaves", makes the proper determination ( ? ) and decide to pack and unpack - -or- - leaves it alone.

.

Along time ago, I made x86 app compiles with the debugger switch turned "on". . . Is there the same switch in android kernels ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
I was wondering if maybe it could be a magisk module but I tried with all of mine disabled and no joy. So I flashed boot, boot twrp, and flash kernel then magisk. Which is no big deal, I love this kernel so it is definitely worth it, I just wonder why it works for some, and not others...?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
No modules
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
Sometimes it gets through the unpack (cpio symlink error) just fine but fails during repack (gzip/cpio out of space error). Next FKM and EXKM app releases have probable fixes for both of these.

I'm looking into an AK2-side fix to see if there's a way to work around it better, especially where people are seeing issues using recovery only; it's pretty baffling, like there's something wrong in the recovery environment on this and the only 1 or 2 other devices I've seen this reported on.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Chronzy:
Weird how intermittent the problem is. In flashing 1.8.5 over 1.84, I got the ramdisk error. Same situation on P3 flashed fine. And 1.8.4 flashed fine over 1.8.3 on the 3XL.

I've never gotten the ramdisk error, or any error for that matter flashing kernels on the P3.

All flashed in twrp btw.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] :
[MENTION=3428502]Freak07[/MENTION]

Thanks for making such an awesome kernel! I'm just curious if TCP "BBR" is still included? I hadn't noticed it in the last couple of builds but saw it in your description.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Had the same experience as you. The update to .4 went fine, Upgrading to .5 gives an error. Tried Franco, EXM and TWRP.

Could go back to stock boot.img, but prefer to wait until this is fixed which is probably soon.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] altlpd11:
In my case,Once you have flashed something via magisk (including updating magisk and module ),the ramdisk error happened when flashing kernel in recovery. I only used TWRP to flash kernel,and never use EXKM or FK to flash anything.

If you download updatings from magisk and flash it via TWRP,the ramdisk error never happend again.

I am using the Canary Magisk,both the v17.4 or the latest v18.1 have the same issues.

So only using TWRP to flash anything you want ,everything will be fine for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Chronzy:
Interesting, so if you update Magisk or install a module through Magisk manager, the next time you go to install a kernel it will throw the error? Any kernel? I'll try to verify that tomorrow.

Come to think of it, it did give the error after I installed a font module...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
If you face the ramdisk error in one app or twrp you will face it everywhere.

Start with a clean stock boot.img, flash twrp.zip (optionally), flash magisk plus kernel! Then you´re good to go.

For the time being don´t flash another magisk.zip as an update afterwards. I´ll state in this thread when this issue is completely fixed and you can do that again!

Thank you :)

That´s one of the reasons why this bug went unnoticed for so long and was a bit hard to see through. It will be fixed soon. Please take a look at my other replies. I will notify everyone once it´s fixed :)

It will be included in one of the next releases. Sorry I thought I did enable it via defconfig at an earlier stage when I apparently didn´t.

Start with a clean stock boot.img, flash twrp.zip (optionally), flash magisk plus kernel! Then you´re good to go.

For the time being don´t flash another magisk.zip as an update afterwards. I´ll state in this thread when the bug is fixed and you can do that again!

You probably flashed the new magisk.zip after the update to 1.8.4 but before you attempted to update to latest 1.8.5.

Thanks for your reports! We actually think we have nailed it down. A fix is hopefully available soon for everyone. I will notify everyone on this thread once it is ready.

Then flashing business will be back to usual! For now please take a look at the other answers in this big post. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
[MENTION=3428502]Freak07[/MENTION]

Do you mind having a look at the attached screenshots from BBS (following on from our previous discussion). I'm on your latest kernel and the active % after the first charge has gone up again. Just so you know, I also use Naptime, Sysconfig Patcher and Universal GMS Doze to help with battery.

Any further insight on the idle drain rising after few charges would be much appreciated!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] blaze9090:
Guys you have to try this Kernel in combination with DU13, this is incredible!

Thx for your awesome Kernel, Used it since sailfish!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You´re very welcome! Thanks for the nice words!

Same for me although with a home brewed DU build :victory:

You have to distinguish between idle drain over night and idle drain that occurs during normal usage with for example music playback!

That´s why I find the idle drain stat a bit problematic to compare between users. The only thing that´s a bit comparable is idle drain over night when the phone is just sitting there for like 7 hours doing nothing.

Especially if you stream music, or even Hi-Res music your idle drain will rise significantly compared to just drain over night without doing anything.

Considering you did a lot of music playing with tidal and also used bluetooth as it seems an screen off drain of 1.5% is quite good?

Again idle drain, active drain or SOT are extremely difficult to compare between users.

There are simply to many factors to consider for idle drain alone while music is playing . Signal strength, Wifi strength, Bluetooth strength only being that one not really controllable at all.

Then music streaming vs local music playing.

Music streaming via WiFi or mobile network?

Music playback via dongle or bluetooth?

Which dongle was used? For example a Dragonfly red with an absurdly high output drains battery extremely quickly.

Have a read here:https://arstechnica.com/gadgets/201...sts-tracks-and-improves-android-battery-life/

That partly crosses this topic too.

The only thing standing out is your net_scheduler wakelock from google play services.

My experience was that trying to control wakelocks especially Play services with any app results in worse battery drain after a while!

This is probalby exactly what was happening to you. I don´t use any app that tries to control wakelocks at all and get very good deep sleep.

Also take a look at partial wakelocks. If you wouldn´t have the net_scheduler wakelock at the highest place the next wakelock is naptime, which should block the wakelocks! it did wake your phone for 142 times!

The tidal and youtube music playback are perfectly fine, when you listenend to music with screen off. They´re supposed to be there. If they wouldn´t the music would stop when the screen gets turned off.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dark_Eyes_:
No mirrors found on AFH? Never had this issue, but I've been trying for a few hours and I'm still getting this. Can you provide an alternative link?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] choder:
No mirrors found on AFH? Same here....
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Tried to flash the default boot.img to both slots, but got the "your system is corrupt" message.

Had to flash-all no wipe. Than flashed to TWRP, installed TWRP, installed Magisk and than installed kernel. All is good now.

Not sure why I could not get out of "your system is corrupt" Maybe I needed to uninstall Magisk. Any quick answer for the next time?

Thanks for the great kernel. Maybe I will install Magisk updates via TWRP in the short term to avoid errors when Kernel updates come out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Zetsubou Sensei:
I'm having the same issue.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] odontastic:
No AFH mirrors found

Same for me since last night and tried again after 8 hours and there are still no mirrors.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] choder:
This works

https://dc4.androidfilehost.com/dl/...868586/Kirisakura_Bluecross_1.8.5_Release.zip

Thanks to "odontastic"
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] osm0sis:
You guys were onto something. [MENTION=4684315]flar2[/MENTION] found the cpio symlink error would consistently trigger once he updated a Magisk v17 + AK2 patched boot.img to Magisk v18, and then tried to flash another AK2 zip on top of that. Magisk v17 + repeated AK2 flashes worked fine, but Magisk v18 over top of an AK2 appeared to break the boot.img, which would trigger the error upon the next AK2 flash.

Turns out it was a recent change to magiskboot (part of Magisk responsible for patching the ramdisk) that seems to have caused this issue. [MENTION=4470081]topjohnwu[/MENTION] spent some of his valuable time last evening and tracked down the cause thankfully. It should be fixed by this Magisk commit: https://github.com/topjohnwu/Magisk/commit/b245931c7902d9e0d438ba25b16a073dd138b44e

The latest Magisk Canary build includes the above fix:

Magisk (b245931c) (18002)

- Fix a bug causing `magiskboot` to create duplicate entries after flashing AK2 kernels​

And I believe [MENTION=4470081]topjohnwu[/MENTION] also silently updated the Magisk v18.0 stable zip to resolve this issue more widely. The silent update likely won't trigger an update notification however, so those on the stable channel should redownload v18 and reflash it.

Also important to note, as I'd said previously, that if your boot.img is already broken you need to start with a clean boot.img (your ROM's default boot.img) and then flash TWRP zip (optional), Magisk (either the reupload of v18 or the latest Canary), then latest AK2 zip. :good:

This was a tricky issue to reproduce and track down, so thanks everyone for their patience and time!

Please share/quote this post in any other threads/sites you guys come across where this issue is occurring so we can spread the word. :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Chronzy:
That doesn't explain why Magisk v18 + 1.8.4 --> 1.8.5 flashed successfully on my P3. I thought the problem was more device specific to the 3XL, but whatever.. I flashed the stock boot and went from there, all good.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Why do you use Sysconfing and Universal GMS Doze? First one does exactly what UGD does plus more. UGD is only about GMS which is covered by Sysconfig too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
My idle drain on 1.8.5 when using just Naptime is at .49% per hour.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I reuploaded 1.8.5 here:

https://www.androidfilehost.com/?fid=11410963190603871817
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
My experience was the more I screw with wakelocks especially from play services the worse it gets in the end. I´m getting really good drain overnight when the phone is idling for 7 hours straight.

I don´t think one generally can say he´s getting .49%/h idle drain. Drive for 7 hours with gmaps navigation turned on but screen off with music playing and you won´t get 0.49%/h. I just rather be really cautious with statements like this as they can contribute to misunderstandings!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
Again, thank you so much for the detailed explanation. I should have been clearer on the point that when I was talking about the idle drain, I didn’t mean when streaming music etc. I more meant either overnight or during the day when I don’t use the phone. OI totally understand that using the phone especially streaming will increase the idle drain. However, when the phone is idle after the streaming for 30 mins or so, should the idle drain come down? I stream both on WiFi and 4G. I’m never in a poor coverage area as I live very close to the city so reception is never an issue when it comes to it’s impact on my battery life.

I have taken your advice and have uninstalled naptime.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Thanks for the post and bringing all the devs together in slack at one point!

Glad the issue got catched and will be gone from now on.

So everyone please flash a clean stock boot.img from whatever rom you´re currently on! Make sure to redownload( this is important) magisk 18.0.zip or latest canary from magisk manager( not another source!) after refreshing the view in the Magisk app.

Then proceed to flash TWRP zip (optional choice), flash magisk (fresh downloaded one) and my kernel.zip!

Thanks to everyone reporting here and trying to provide solutions!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
Ok, so you don’t use either Universal doze or sysconfig patcher right? Also, do you block any wakelocks in the ex kernel manager or leave everything as it is? Haven’t had a chance to leave my idle phone overnight as I’ve been needing my phone at full capacity the next day. When I do, I’ll report back.

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Don´t pay so much attention to the idle drain. The only thing I take like a benchmark for myself is the overnight drain when my device is sleeping for 7 hours straight. I typically lose between 2-4% on my Pixel 3 XL in these 7 hours which is totally fine for me. I didn´t try on my Pixel 3 XL yet but on my Pixel 2 XL I´d lose about 4-5%/h when streaming music via spotify. If I take that to the overnight drain you´re doing pretty good with your 1.5%/h in my opinion considering your usage :)

There are a few more drawbacks of idle drain calculation. They´re only accurate over a really long state of time. A few hours won´t get the exact average. What if in one day you multiple times use your phone for 10 minute intervals and losing 1% one minute after putting the phone to sleep?

If you find time let your phone stream/play music with screen off for 2 hours straight and see how much % was needed for this. Repeat the test a few times to have accurate number. Maybe do it one time on mobile data and one time WiFi. Pay attention the music isn´t locally availabe for the streaming service or buffered after the first testing round.

Then repeat the test over night for a few days. You´ll see that the values you´ll get with these tests are nowhere near "real" life usage when you actually use the phone. If a value of 1,5%/h is calculated with just 5 hours to compute with it cannot be very accurate. :good:

If your wakelocks stay the same and you get rid of the net_scheduler wakelock from play services you´ll have a device that sleeps really well!

No I don’t use any mods/apps/modules to block any sort of wakelock.

I also don’t block any kernel wakelock. The main reason why the wakelock Blocker is included is some wifi router may in very very rare cases have an incompatibility with the phone’s wifi driver. That can cause wakelocks. Blocking these, is one of the rare circumstances where blocking a wakelocks doesn’t cause more harm than good!

I use the kernel as it is flashed. Some things are tweaked in the kernel already to my liking at compile time ;)

The only thing I change in EXKM is enable s2w and s2s.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
I will definitely do the above tests that you have mentioned. Appreciate your time with this. Regarding the net_scheduler wakelock, even though I had the universal doze etc, I’m not sure why the net_scheduler is coming up. Nevermind, I can’t seem to find this wakelock in the wakelock blocker so how can i block it?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
Mine is low but my phone isn't doing anything while it's idle, no music, no navigation...etc.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
With the Wakelock blocker in EXKM you can only block kernel wakelocks no partial wakelocks. ;) I suggest you do a bit research regarding wakelocks in general and what’s the difference between those two.

There are ways of blocking partial wakelocks caused by google play services but it will just end up in another wakelock caused by google play services like it did when you used means of blocking wakelocks from play services via the magisk modules.

Yes that explains it. But it is great when there is more specific info in a post regarding the usage when stating idle drain of 0,5%\h. :svetius:

Because if one expects 0,5%/h idle when playing music after reading your post and is not an experienced user he may start doing things one really shouldn’t. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Love this kernel. Only one that removes verity for custom roms. Love it on stock too. Been following Dev since he started. Very impressed. Use too be obsessed with battery. (See 100 posts above) Now I use my phone as it's intended to be used. Ignore the 100 posts above. And plug it in and rapid charge. I never seen below 20% because Google phones have some of the best battery life available.

Not a gamer. Don't look at battery and plug it in or put it on the Pixel Stand.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
just reporting back, after using 1.8.3 - 1.8.5, over 7-8 hours i lose less than 5-6% in total, which isn't bad , could be better but i aint man.

SOT has been hovering around 5-6 hrs , that includes 1hr30min on average of daily spotify BT streaming during gym and about an hour of phone calls using whatsapp and regular phone calls.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Maty360414:
Link is dead
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
https://xdaforums.com/pixel-3-xl/de...ra-1-0-0-pixel-3-xl-aka-t3864563/post78391839
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
I'll do a bit of research on wakelocks. The only reason I'm raising the drain issue is that maybe there's something wrong with my phone? I'm having the same issues on other kernels as well where the drain starts good for a charge or two and then it goes up even though my usage pattern doesn't change. Maybe worth starting fresh, not installing any magisk modules or battery saving apps and see how it goes?

Thanks:o
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
The update to EXKM for improved AK2 autoflashing is up. Here's hoping the next kernel update goes smooth now that Magisk and the flashers have (hopefully) been fixed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes exactly! Playing with the wakelocks in the end results in worse drain. It´s not worth it.

Thanks for the kind words :) Hope you´re enjoying the kernel as much as on the other devices before!

Phone calls cost quite a bit of battery from my experience so I´d consider that actually good results with the additional music playback!

Yes that´s exactly what I would suggest. Start fresh, no mods or apps to control wakelocks. Just install Better Battery Stats to check if any app starts draining.

Flashing with EXKM is fixed, FKM still needs to be updated! Have a bit patience with [MENTION=3292224]franciscofranco[/MENTION] he´s a human too, like we all are :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spuri78:
Great. I'll flash the December factory image and go from there yeah? I won't even change the scheduler. Keep it as stock as possible. I feel that there's something wrong with my battery. Even on stock, Locked BL and unroot, I wasn't getting great battery life but let's start backwards and see how we go.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Sounds like a plan :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 1.8.6

Hey guys and girls,

So here is the new update! It includes backlight dimmer and an option to adjust speaker gain!

I have a few other changes in my experimental private kernel, which is still tested extensively!

The ramdisk error is now fixed. Please take a look at this post from [MENTION=4544860]osm0sis[/MENTION] for more information:

Big thanks to [MENTION=4544860]osm0sis[/MENTION] and [MENTION=4470081]topjohnwu[/MENTION] for everything at this point here! And everyone else that helped in the process!

Important:

What do you have to do to get finally rid of the ramdisk error?

1. Flash back a stock clean boot.img either for stock rom or the custom rom you´re on. (not a backup from some time ago, a clean stock boot.img)

Link to stock boot.img from Google´s december factory image for convenience

2. REDOWNLOAD(!) either magisk 18.0 or the latest canary directly from magisk manager and delete all old magisk zips on your device. (this is really important!)

3. Optional: Reinstall twrp.zip if you want to.

4. Flash the redownloaded magisk zip in TWRP

5. Flash my kernel either via TWRP or EXKM. (FKM is not yet updated! I will notify you guys when it is!)

6. Profit

Important Number 2:

The kernel works with custom roms :) I´ll also edit the OP accordingly!

So flash away :)

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

Why is linux-stable important?

I wish you all a nice day/evening!

Changelog:

- Include backlight dimmer ( thanks [MENTION=4684315]flar2[/MENTION] )

- Include option to adjust speaker gain (thanks [MENTION=4684315]flar2[/MENTION] )

For further details please take a look at my github!

Download is below :)

Download:

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

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post!

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: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
If I'm on Magisk 17.3, do I need to run the uninstaller before flashing 18?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
No, but it won't hurt. Even simpler is to just flash a stock boot image first. That way you won't lose any modules or settings.