yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
.

I do not want to assume you understand the process ( um, you do not turn the phone off and then run the batch ! ) . . . . The pre-setup before running the "flash-all" batch is : (0) have an unlocked boot loader . . . . (1) download the latest developer tools subset to get you the s/w tool "fastboot.exe". . . It'll come with the "adb.exe" along with it . . . . (2) place those tools in the sub-dir where the batch update is located . . . . Do not assume the usb device driver for adb usage will load and run happy ! . . . (3) from "off", press the volume down and then also the power button to get the phone to come up into the 'fast boot" mode . . . (4) at a pc cmd prompt window in that sub-dir, run "fastboot devices" and get a string back to verify the pc is happy and talking to the phone . . . . (5) then finally run the "flash-all" batch.

.

And then very important . . . ( like [MENTION=7037416]joetheshmo[/MENTION] just stated ), must wait for our leader [MENTION=3428502]Freak07[/MENTION] to announce that he has a "new" custom kernel with the Google January changes folder in.

.

( is worded okay by you guys ? )
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
In the bootloader you want to run fastboot devices, not adb devices. adb only works in system or recovery.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] odontastic:
Awesome kernel working smoothly for me as well.

And "Hey, Google" works for me again! :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I'd also add that you may have trouble using a USB C to USB C cable. I can only get it to work properly using an OG USB port on my laptop
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hello everyone,

There are no google side kernel changes pushed until now.

It should be okay to flash the old kernel on January looking at the posts from those who did successfully. If sources drop I’ll try to get out a build of course :)

I’m not at home for a few days but I set up a VM so you guys get the security update :svetius: at least that was my plan.

Have a nice day everyone!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] scloutkst:
I've had this issue with all 3 of my pixels. For some reason they Don lik c to c cables when doing adb or fastboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sunnyschlecht:
I actually had no other way then using my MacBook pro to flash the new January update since I was at work. After probably 30min it did actually work even with the USB c to USB c cable that came with the phone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
1.90 works fine with the Jan update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mac208x:
As of late I've been only pull roughly 4h screen on time. It used to be almost 7h before. I know I didn't change anything as far as I can remember.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
Did you install any different apps since then?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mac208x:
No same ones I've used always
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sunnyschlecht:
TWRP backup failing

So I don't know what else to try. For some reason my twrp doesn't backup my data part. Every time it gets to the data it gives me a weird error message 255 that I have never seen before. Tried reflashing stock as well as TWRP without success. Anyone else have seen this? Thanks in advance!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
When you get that error go to advanced in twrp and use copy log. Look at the end of the text file and you should see what file is causing the error. There's probably one that is corrupted.

Edit, also, why are you backing up all those partitions? In my experience only the data partition is going to you any good.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Deleted.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
He's using TWRP. He's on a Pixel 3 XL (or at least a 3, kernel is common to both). That means 2 things - any busybox that he installed doesn't come into play.

Also he's not running busybox tar. He's running toybox tar. TWRP switched to using toybox (and, incidentally, the mksh shell, same as the default Android shell), at least in the Pixel 3 builds. (If I had to guess they're probably doing it for all new devices, but that is a guess)

The previous post about getting the log is the correct approach
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sunnyschlecht:
recovery log

Thanks for all your help guys. Very much appreciated. So I went ahead and got the log file but I can't seem to identify the issue. If someone could take a look that would be great. Thank you so much.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
At this stage this should probably go in the TWRP thread. It's really veering way off topic for this thread, but anyway:

I:addFile '/data/vendor_ce/11' including root: 1

==> set selinux context: u:object_r:vendor_data_file:s0

failed to lookup tar policy for '/data/vendor_ce/11' - 'b5244f2e9a2a129e'

I:Error adding file '/data/vendor_ce/11' to '/data/media/0/TWRP/BACKUPS/89DY0672H/Data/data.f2fs.win000'

Is /data/vendor_ce/11 a file or a directory? I have no corresponding entry. Only thing directly in /data/vendor_ce/ is /data/vendor_ce/0/

Did you add additional users to the phone? Is there a corresponding entry in any of /data/[vendor_de system_ce system_de user_de]?

I'm tempted to just say delete that item and try again, but it depends on the answers.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sunnyschlecht:
Thank you so much. After deleting a bunch of /11/ folders that were all over it finally worked again. It must have been some leftover folders from when I had another account on my phone. Sorry again to have taken this off topic but greatly appreciate your help!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
Just wanted to report that the January update took just fine for me while still using Kirisakura 1.9.0.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
New update with latest Linux stable, which got released a few hours ago, will probably drop tomorrow :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
Me too
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 1.9.1

Hey guys and girls,

Here´s the update with latest linux-stable as already announced.

Important :)

All flashing errors are now fixed. The ramdisk error is fixed if you did the procedure I put in hide tags below.

Kernel is flashable via TWRP or directly in the EXKM App as well as the FKM App. The presence of a custom rom will be detected and the kernel will get patched so it boots the custom rom too!

Root will always be preserved! So happy flashing everyone :)

By now most people will have their ramdisk fixed. But keep this here just in case.

Procedure to fix the ramdisk issue:

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, EXKM App or FKM App

6. Profit

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:

- Upstream to 4.9.149

For further details please take a look at my github!

Download is below :)

Download:

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

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: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Installed 1.9.1 on to the January update. Everything seems solid and smooth.

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] peikojose:
Can someone explain what happened with the kernel sources Jan security patch for the Pixel 3? Is it really safe flash a kernel without that January patch?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Seems as though there wasn't anything updated kernel side.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
What [MENTION=7037416]joetheshmo[/MENTION] said.

There are no kernel changes from google uploaded as of now. So either they ran into some issues this month and want to give it more time or there are simply no kernel changes this month for bluecross.

There don’t have to be kernel changes for any security update. It’s safe to flash away at this point now. :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jiexi:
Dec Update

Kirisakura 1.9.0, default settings

Always on Display disabled

Double Touch to Wake (Stock, Not kernel) enabled

Universal GMS Doze

SysConfig Patcher

Device admin apps: Find my device deactivated

Naptime, default settings

Strong Wifi all day

Mostly sitting on table

Adaptive Battery Off: 100% -> 63%

2h6m 10.44% screen on

19h28m 0.72% idle

18h34m deep sleep

21h34m total

Estimated 100% -> 0%: 58h17m

Adaptive Battery On: 100% -> 67%

1h52m 11.18% screen on

19h47m 0.61% idle

19h6m deep sleep

21h40m total

Estimated 100% -> 0%: 65h39m

In a post on the ElementalX thread, I mentioned Naptime being detrimental to battery life. After deactivating Find My Device under Device Admin Apps , this was no longer true. In that same post i had results of getting 0.6% - 0.8% idles, which unfortunately went away as I setup my device completely. However, with the setup posted above, I'm back at these numbers once again.

Now if someone could actually post some damn numbers about how much Blackenedmod actually improves their active/idle...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Donric13:
Hi Freak. Nice to see your kernel also on the 3 line (just changed device from taimen). Just a little question: in op you state that usb-debugging should be turned on in dev-options. Is this also necessary to keep it on after flashing your kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] loonix:
After enabling "Randomize Mac Address" in EKM, I found that the MAC wasn't changing. Turns out in addition need to enable "Connected MAC Randomization" in Developer options.

.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
That developer settings option is completely different to the kernel method. If you turn the kernel way off in exkm and have the dev options one on it'll work. I couldn't get the kernel way to work at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yes. I forgot to reply previously if you were the one bringing it up. It seems mac randomization that’s built into android is overwriting the kernel mac randomization.

I’ll probably remove it in the next build. Sorry about that. It’s working on my phones which still run Oreo. I just tested it. But not on devices running pie.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
New update with latest linux-stable 4.9.150, which got released a few hours ago is going to drop tomorrow :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] AjaySp:
booting to twrp

hi i flashed the ltest kirisakura using ex kernel manager and now the phone is only booting into twrp

is there anything to do after the kernel flash

please help me out

thank you.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
Works fine for me every time I flash through ex manager. Try fastboot flashingJan boot img, and start over from there. This has happened to me in the past and this fixes it, has to do with magisk, and modules I think, but I'm speculating. Or just try reflashing magisk in twrp, I've read somewhere this works sometimes too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Additionally flashing the latest magisk uninstaller zip before restoring magisk might help too! :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Device admins, do you have Google pay enabled and find my device disabled? Or both disabled
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jiexi:
both disabled
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
I have nothing disabled on my phone running this kernel on dec patch. I gotta say my p3xl has Superior battery life. Everyday
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 1.9.2

Hey guys and girls,

Hey guys, as promised here is the update with latest linux-stable merged in.

We´re nearing the 2.0.0 release which will be again a bigger one :)

On a side note I forgot to remove the mac randomization for the wlan driver. It´s not working currently. Please fall back to the in built mac randomization build into the OS, accessible under developer options since Android Pie.

Important :)

All flashing errors are now fixed. The ramdisk error is fixed if you did the procedure I put in hide tags below.

Kernel is flashable via TWRP or directly in the EXKM App as well as the FKM App. The presence of a custom rom will be detected and the kernel will get patched so it boots the custom rom too!

Root will always be preserved! So happy flashing everyone :)

By now most people will have their ramdisk fixed. But keep this here just in case.

Procedure to fix the ramdisk issue:

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, EXKM App or FKM App

6. Profit

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:

- Upstream to 4.9.150

For further details please take a look at my github!

Download is below :)

Download:

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

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: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] AjaySp:
So flashing jan boot image seemed to work thank you really appreciate it

---------- Post added at 09:24 PM ---------- Previous post was at 09:23 PM ----------

So flashing jan boot image worked thanks for the help appreciate it
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
Update to 1.9.2 working great. Thanks!

I've noticed that the best battery life I've gotten are with Kirisakura + Greenify + Sysconfig Patcher compared to other kernels or configs I've tried.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
( sorry for going off topic ! )

.

The Greenify module for Magisk is complaining, 'your api of 28 isn't lower than the maximum' . . . and I thought this was happy before. Must have been dreaming of retirement . . .
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
I should say I'm using the app not the Magisk module.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
I just donated. Hope others feel like showing some appreciation...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Short Update on the Roadmap

Google has released what seemed to be the January Security changes for the Pixel 3/XL.

I already had all of these changes minus one in my experimental tree for quite a while now. Plus my experimental tree has hundreds of changes to various subsystems like f2fs, camera driver etc.

I release this as the stable 2.0.0 plus the January Security Update soon. Either late this evening (in my timezone) or tomorrow morning before work starts!

These changes were now for over 2 month tested by me and my trusty testers over at hangouts! A big thanks to them at this place!

So stay tuned!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] keaheng:
Clean install with the latest kernel 2.0, scrolling in chorme choppy and laggy so much. Any kernel tweak that can improve the performanc?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] old_fart:
I have this strange conspiracy theory that the "Titan M chip" is not allowing us to change that horribly bright white boot up screen. . It's google's way of showing us they have the upper hand.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
bastards!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
next release will be one hell of a release :)

Tests are looking very good.

I guess tomorrow will be the great day :fingers-crossed:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] airmaxx23:
This fixed the saturation level not sticking, thank you.

Do you have plans to add High Brightness Mode?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] elreydenj:
Sounds great! Why push off to tomorrow what you can accomplish today?!?!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Dude, really digging Kirisakura-Kernel 1.5!!!!!!!! Quick but smooth and best battery life yet. So, once it's released to the public (I'm testing it, thank you sir) I hope you agree this ain't your mama's kernel... Cool thing too, no need to flash magisk cause it detects it as it should.

[MENTION=3428502]Freak07[/MENTION] good work my man!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Roll3r:
Thanks man!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
my suspicions are right

EXT4 is faster than F2FS

look at this
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
sorry I cannot load that screenshot...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
fixed
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
So did you manage to convert it on your pixel 3 after all?

Is that with fsync disabled or enabled?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
stock kernel, fsync enabled.

i was able to format as ext4 with issues im trying to address.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Interesting!

Are you encrypted?

do you have a comparison to your device on stock with f2fs?

That’s what I get with my kernel on f2fs.

Everything is faster or basically the same except sequential write. Could that be maybe to the things that aren’t working properly yet on ext 4?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
ext4 wont boot encrypted had to boot decrypted

its possible seq write is low because EXT4 isnt working properly.

my limited knowledge of android fs stops here - i am stumpted and out of ideas on how to get this working.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
no you got that confused. your seq write speed was faster, due to no encryption.

that was the last part of the puzzle and explains your result. If you would get ext4 with encryption fully working, sequential write speeds would drop to the speed my screenshot (with f2fs) shows.

So all in all we can conclude that f2fs is faster or at least as fast as ext4 on this device.

I don´t think ext4 yields any benefits over f2fs on this device.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
i agree

now i just need to find a way how to decrypt and allow fingerprint and pin registration

edit:

got data and wifi working on EXT4.

also using this kernel so not sure if its kernel related.

the only annoying thing is not being able to use a fingerprint because decrypt.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
[MENTION=3428502]Freak07[/MENTION]

look at this

ext4 with data working

EXT4 is MUCH faster now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
What did you get working?

are you still decrypted?

we cannot really compare decrypted results to encrypted ones.

random read/write performance is still nearly about the same. That´s the most important one for Android OS.

do the test with /data formatted to f2fs and decrypted as well as /data formatted to ext4 also decrypted. and post the results please.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
results are similar with f2fs decrypted.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _LLJY:
That isn't surprising in the slightest. F2FS was never meant to be "faster". However you do get a few advantages running F2FS over EXT4 that is

F2FS is a Copy on Write filesystem, which can potentially save space and write endurance

F2FS has lower overhead and hence will have less latency.

However it is worth mentioning that filesystems make less of a difference as compared to changing I/o schedulers, CPU throughput and storage speed. overall, EXT4 is more stable and less prone to failure than F2FS, however F2FS is in a really decent state right now, so I'd say it's still pretty comparable *during normal use*
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ridobe:
Smooth as always for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DIXZ06:
Absolutely no issues here!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] :
Same here, smooth as butter on a clean install.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dukat0s:
Hey fella.. no lag at all here it's even "smoothest " than last update. .

Please next time consider to take a log , so developer.or any other person with knowledge can help you solve your problem , for a better experience... [MENTION=3428502]Freak07[/MENTION] is always helping users get the best out of their devices ;) have fun around ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] keaheng:
Okay maybe its only me. Thank you all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] tysj:
Hopefully not too off-topic but has anyone had any issues with 2.0.0 and installing Blackenedmod 1.0? Did a fresh install of both and each time resulted in a virtually non-functional device a few minutes after boot. Removing Blackenedmod real quick after startup and restarting seems to fix everything.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BlacquePhalcon:
Same here, 2.0.0 isn't playing well with Blackenedmod. Everything works until it seems the script takes hold. Apps don't launch, turning off the display doesn't lock and eventually total system lockup. Blackendmod works fine on 1.9.2 though. Going to leave the mod off for the time being
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Even with 1.9.1 my scrolling got choppy with that mod, I had to remove it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] simonwil:
Same for me. I went back to 1.9.2 but will try 2.0.0 again without Blackenedmod.