yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tribecca:
I'm thinking of trying this. Will it stop google from spying on me?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
What? No, a kernel doesnt do that.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mustbevick:
Appreciative.

Could you share your kcal settings.

Thank you
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tribecca:
Sorry, stupid question
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] 12paq:
Happy to help.

For the P4a I only adjusted RGB and Saturation values. Out of the box the screen was a bit too warm for me. This is not a perfect Pantone color calibration, which is often quite flat. This is just what I like for average viewing accuracy. Ymmv, as it seems Pixel phones are not all the same.

I wasn't sure what kernel app you use, since my adjustments were simple, I'll just share a screenshot.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mustbevick:
Thank you! - i am using EXKM / is that franco kernel manager ?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] 12paq:
Yes.

And of course since I went and checked my settings I started manipulating and playing around with it again! Haha

I like these better:
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Watanabe_You:
Welcome to the SD730 family, coming from the Mi 9T group.

We got some good sh!t to get you started if you need it in the kernel department

https://docs.google.com/spreadsheet...EeHh8awi9gxI0Cc_pNMV6QgqxI/edit#gid=786387371

https://github.com/vantoman/kernel_xiaomi_davinci

https://github.com/ArbitraryFox/kernel_xiaomi_davinci/tree/Orokin-AOSP

https://github.com/ArianK16a/android_kernel_xiaomi_sm6150
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
11 Kernel updated to match current 10 kernel, currently in testing.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Alright, went ahead and posted the 11 kernel, Development Version 1.0. This matches the 10 kernel in features and everything appears to be working fine here but need some more reports before I make and post the Release Version.

Let me know, thanks!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Cj719:
DV1 running well so far and I pass magisk check without the hide module.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Alright, Release Version for Android 11 is posted!

Couple things with this kernel:

It is inline with all the changes from the 10 kernel, same features, setup, and toolchains. Just as stable and no issues, runs great!

That being said,

I am currently building with the android-r-beta3 FTS Touch driver as the android-11 branch driver does not allow touch to function. That being said, the r-beta3 branch driver is newer than the android-11 branch..

On a similar note if you tried to build the sunfish kernel yourself, the rmnet shs driver is broken and does not compile without fixing the last mismerge in the commit tree.

On top of those two, the stock defconfig from google in this kernel source does not line up with the modules that google is shipping with the official images/otas nor the android-11 source code (platform/device/google/sunfish-kernel). They are shipping a WIL6210.ko (kernel driver/module that our device does not use) but the defconfig in the kernel/msm android-msm-sunfish-4.14-android11 says they disabled building that driver in one of the last commits so... either they're giving out kernel source that's newer than what they have in the rom source, or vice versa, either way something is off there even if it is something that does not matter for our device.

Outside of those 3 things, the kernel is solid as far as I and any testers can tell. If you find anything, please let me know here, and I'll continue work on it for as long as we continue to get sources from Google.

Now, back to working on rom stuff, enjoy!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mustbevick:
Thank you for your hard work. Any recs to kernel settings that could give a little bit more speed aside from running it in performance mode. Thanks in advance.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] shrapner:
After upgrading to 11 and rooting. I downloaded the stable 11 kernel zip from here and flashed in fkm. The phone restarted but it did not flash.

So I went back into fkm but this time choosing only flash and to not reboot right away. The flash dialog only ever said getting ready to flash and nothing else. But flash successful reboot notification showed up in the notification shade. Upon reboot, the kernel was still not flashed.

Any ideas?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Which mirror did you download the kernel zip from? try downloading from other one and try again and see how it goes.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] shrapner:
I tried both mirrors and same result. Flashing with magisk canary instead of stable wouldn't be my issue would it?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tweaked:
I am having this same issue. So I also grabbed exkm and flashed, this one worked but stuck at google logo after boot.. I reflashed 11 with the -w and booted back into my phone. I haven't figured out what is going on. I'm going to download the file on my pc and transfer it to the phone and try again since reflashing 11 with the -w is easy enough to keep troubleshooting.

Edit:

Downloaded with PC, transferred file and Same thing so far. FKM never finishing set up if I tell it to just flash. just says setting up env and then hangs. If I tell it to flash and reboot, it reboots. No change.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] mustbevick:
Same thing here with FK.. flash reset nothing. I used exkm instead and it worked. Good luck.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Weird, I only flash with EXKM or FKM and have zero issues. Just redownloaded and flashed myself no problem.

Can you get me your build.prop? Maybe device name is slightly different or something.. Or try this new build.

Release Version 1.1

I noticed touch was slightly finicky with this 11 kernel so I've enabled Touch Offload in the driver which seems to help with that. Also building with Thin LTO currently.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Cj719:
I flashed through Ex and never had any issues.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] shrapner:
1.1 was a no go also. I think its because i'm still in canary channel for magisk. If i try to switch to stable i just bootloop until I reflash the rooted boot.img
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
you HAVE to have canary for root to work and you should be flashing the kernel zip from inside the EXKM or FKM app.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] shrapner:
ok. then it just doesn't work then in FK. right now my phone says e66b0bf3 (20425) and MM version 2eb00187(299)

which yes, does give me root on android 11. I only mentioned going back to stable because it was an answer to a question I had in another thread. I was under the impression that after you are up and running, you switch back to the stable channel and only update the manager part but when I do that i don't get root permission prompts.

what I have installed, is what I'm trying to flash this kernel with through franco's manager. I'll buy exkm and try it.

EDIT. exkm works fine. I guess fkm needs an update. I was being cheap by not just buying exkm the whole time.

Thank you for your patience :)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] tweaked:
This build flashed with no issues in Exkm. Thank you.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] danbrown162:
Working great in android 11 for me.

Just a little off topic, in theory, would it be possible to OC the pixel 4a screen like many xiamoi devices now?

I'd switch the 4a to my primary device if this were the case

:)
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] alvintimothyjr:
-Unlocked bootloader

--Flashed factory image

--Magisk debug installed (rooted)

Unfortunately, my device hangs on the google boot screen.

Anything else I should check for?

Thanks,

link to build prop : https://drive.google.com/file/d/11Vdq7hpOVSQZBI_zPUsxxIPw9r0bkXW3/view?usp=sharing
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bobbarker2:
HI [MENTION=1211160]HolyAngel[/MENTION], thank you for your work and contribution. I'm not asking these questions as a "challenge" to you or your capabilities, but rather for opening a dialogue. I understand the reason for enabling ThinLTO, but isn't it still experimental? And also not used for linux-stable. I like NathanChance's write-up about the importance of linux-stable - https://github.com/android-linux-stable/notes/blob/master/info/what-is-linux-stable.md

Also why did you decided to use Maple IO w/ 128kb read-ahead as the default IO Scheduler? Using AndroBench - I know benchmarks don't equal real world performance but they are still a relevant tool - other schedulers produces better results in the areas that matter for daily use.

Maple

Random Read: 33977 IOPS

Random Write: 35928 IOPS

SQLite Insert: 4507 QPS

SQLite Update: 3447 QPS

SQLite Delete: 4928 QPS

Zen

Random Read: 37168 IOPS

Random Write: 39103 IOPS

SQLite Insert: 4457 QPS

SQLite Update: 3645 QPS

SQLite Delete: 4897 QPS

CFQ

Random Read: 36572 IOPS

Random Write: 38607 IOPS

SQLite Insert: 4315 QPS

SQLite Update: 3526 QPS

SQLite Delete: 4686 QPS

Random Read/Write and DB performance do effect everyday usage. And I ran all these at 128KB read-ahead, when we would see different results with a larger read-ahead as our emmc is 128GB.

BBR all the way!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
[MENTION=5417405]bobbarker2[/MENTION]

Thanks for the in-depth reply!

I actually should have re-enabled FullLTO for this release build, I'll have it fixed for the next one!

Thin LTO just allows for much faster development cycles as currently I've seen Full-LTO take anywhere from 10-50 minutes to finish compiling the kernel as it only uses a single cpu core to process and optimize all the bitcode from the entire kernel. With ThinLTO, while not indexing the entire kernel all together at once, can use multiple cores and allow compilation to finish in ~30 seconds. It may be experimental on some, but is default on others, and I've not had any issues with it in my testing other than minor regressions in certain particular benchmark scores.

I use Maple IO due to to my own personal experience over the last almost decade or so of using all the schedulers. For me it just seems to give the best balance of a snappy UI and still being good on battery. It does heavily depend on your usage though, so that's why I include all the other schedulers, so you can choose what you want. Again though, this is still in development. It usually takes me a couple months to find what the SOC/UFS Storage/Battery tend to like best to strike the best balance. Each phone, soc, and even kernel version is a little different.

Edit: Looks like I am using 512kb read-ahead by default with Maple IO. Stock is the one using 128kb by default with CFQ.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] imna357:
You don't need to reflash everything, just flash the factory boot image and you'll be back on
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bobbarker2:
Yep I get the reason for using thinLTO, the compilation time saved is massive and the regression in performance and code size/overhead is negligible.

When I read about LTO/thinLTO on the kernel, it always catches my eye because I know about the complications associated with lto. It can only be enabled in Android kernels 4.14 and 4.8... And there's lots of bugs, prerequisites and conditions needed to enable it. E.g. vdso won't build if LTO and CC_OPTIMIZE_FOR_SIZE were both enabled. And that's just LTO, thinLTO is even more problematic. See Google talk about potential issues with thinLTO vs LTO here: https://chromium.googlesource.com/c...b632/docs/clang_sheriffing.md#ThinLTO-Trouble

You're right default is 512 not 128, some app must have changed that when I was looking at it. I've always read and seen in testing, if emmc is >32Gb then 2048kb is optimum.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] GoldElocks:
Are results similar for read-ahead values greater than 128kb? ie is Zen still scoring considerably higher r/w followed by CFQ and then Maple? I remember with my older Nexus devices different schedulers seemed to make a slightly noticeable difference with day-to-day usage but I wonder how noticeable the difference is with these newer faster devices and this device's USF 2.1 storage.

Do you think there are any battery savings for different schedulers or would they be negligible? I figured I would ask here first rather than doing any in-depth testing of my own :)

So far this phone is running super smooth with all settings I have tried on this kernel and battery life has been very good. Definitely looking forward to seeing how much further we can stretch performance and see just how capable this budget phone can be.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bobbarker2:
IO scheduler's are never going to have much of an effect on battery life.

I realized the program I use before the test performance was old and not clearing caches between different tests, attached as a screenshot of maple at 512 kb for #1 and 2048kb at #2.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rignfool:
Not that I have any real idea but...

CFQ is the I/O scheduler ACTIVELY being developed/worked on by Google ..

And while your benchmark is designed to show how the scheduler related to read and write... There is a good chance that CFQ might do something else... EG: error correction, batched jobs, etc
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bobbarker2:
What do you mean CFQ is being developed by Google? It hasn't been changed since 2005 af the latest.

You should read up on what IO schedulers do.

And that's entirely too much time talking about scheduling when it really doesn't have that big of a difference for a cell phone.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] the.emilio:
Just got this device a few days ago. Noticed some screen flicker when watching videos in different apps like FB, IG and YT. Would flashing this kernel help resolve that issue. A Google search indicates this seems to be a wide spread problem with this device with no known fix. Some say to disable adaptive brightness others say that doesn't work.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] ngollop:
Would it be possible to sideload this rather than flash zip? A case of simply taking the boot.img and sideloading it? I dont have root/twrp and dont wish to install it...
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
There is but you would need to repack the stock boot.img with my kernel.

osm0sis makes the Android Image Kitchen you can use to unpack the stock boot.img. Then replace the split_img/boot.img-lz4 with my kernel (image.lz4-dtb) from my kernel zip. You'll have to rename my Image.lz4-dtb file so it's the same name as the file you're replacing. Then repack the kernel and you can sideload that through fastboot.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Alright, HDK Release Version 2.0 is posted!

Added ability to disable vibration, thanks to Flar2 <3

Increased Read-Ahead values to 1024kb - I experimented with these values greatly over the last week and a half or so and have come to the conclusion that this is best value I can reasonably put in the kernel. Higher values than this DO make things seem faster, but when you get a miss-cache event there can be a significant lag in the system while it flushes and re-fetches. Enough that you'd see the lag in the UI anytime it happens.

Doubled the MAX_RQ value to 256 - This value is the amount of requests that can be written to the disk at a time. This value hasn't been changed since at least emmc storage from years ago. We have UFS flash storage now so having a higher value here increases the overall performance of the system while still not maxing out the iops. Can likely go a bit higher too but leaving it here for now.

Merged in latest October updates

Some minor backend changes, removed 843419 erratum from LTO to match the 10 kernel, plus this erratum shouldn't affect our current soc anyways, might already be taken care of by the compiler, and so having it disabled will either not hurt at all or will increase our performance. I also increased the ksym_name_len in order to quiet a couple compiler messages..

That's pretty much it, Enjoy!
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] misterbusy:
If I understand correctly, the 4a should theoretically be able to support DisplayPort Alt Mode if enabled in the kernel. Is this true and can you give an indication of the difficulty of implementation?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] gvsukids:
Any option of having louder volume?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bobbarker2:
I don't see disable vibration option in EXKM (flar2a kernel manager). Not that I'd want to disable vibration but could you expose the settings for vibration strength?

By the way elementalx is available for this device. Flar2 just doesn't have time to post a thread for every device he supports. I'm not suggesting it's better than this kernel, I haven't even tried the other, I just thought people should be aware. The more comparative experiences the better
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] crackerjack1957:
Not if you are still on Android 10
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
*deleted*

My bad, posted in the wrong thread.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bobbarker2:
I'm on 11. Your phrasing of your sentence makes me unsure of what you mean.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] crackerjack1957:
Was implying there was no ElementalX kernel for Pixel 4a on A10 according to EXKM
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheUndertaker21:
how do we remove this kernel? my chrome is crashing and swift backup is rebooting the phone
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Those aren't kernel related issues but one would hope you made a backup of your stock rooted boot image to return to. If you didn't then you just reflash the stock boot.img from google's factory image page or my other thread that host's them here, and reroot your phone.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] TheUndertaker21:
correct my issue was with an edxposed module.

fixed and thanks
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] daemonspudguy:
I'm on Android 11 and don't currently have the cash for FKM or EXKM. Anyone know an alternative that works?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Lada333:
Is Kernel Adiutor outdated by today's standards?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] daemonspudguy:
Yes.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Meth0d:
How does this kernel compare to ElementalX ? Tbh I am a big fan of flar2 kernels ever since the nexus 5 but on my pixel 4a it does not seem to do a lot of its magic when I comes to battery life, at least not compared to stock.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Alaadragonfire:
I don't think the 4a needs battery life adjustment through kernel, battery life is awesome on this device, I'm getting 5 hours SOT with 50% battery left.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] francescod:
Yep, but you can use its very good foss evolution, Smartpack Kernel manager https://github.com/SmartPack/SmartPack-Kernel-Manager/releases

Btw, it would be nice to see some underclock by about 300MHz on both Cpu and Gpu, to see what can be achieved by this compact monster.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] daemonspudguy:
No. You can't. It needs r/w access, which is unavailable. I've already tried it.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Flar2 is awesome! Great guy and one of the few to ever help me out over the last..12 years here.

Anyways,

Elementalx:

+ Wake Gestures

+KLapse Support

+FSync toggle-able

- No scheduler tweaks

- No IO tweaks

- Full logging enabled

- Tainted Kernel - Does not include all kernel drivers/allows any module named "wlan" to load (This is technically really common here at xda)

- LTO Disabled

Up to you. I build for myself and what I personally like to run.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Meth0d:
Flar2 will always stay in my memory for beening the guy who made my nexus5 run for 2 days on battery and be a lot faster then before.

Anyhow... I will give your kernel a shot too just to compare battery, I'm not rly looking for anything more since the phone is snappy as it is.

I would like to reach 2days on battery though with 80% charge curve ... But I don't know if that's going to be possible.

If i come from ElementalX, I guess I should flash the stock boot.img again?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Yeah cleanest install would be to reflash the stock boot image and then my kernel, and root if you need it.

I will say I easily get two days of standby, usually a little over 2days, and 5-6hr sot with that same standby. Haven't been using my phone much lately so unsure of single day stats.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] rignfool:
No...

This is a bad idea...

Load calculation will get all wonky... And in return... Will cause schedutil to basically act like ondemand....

You'll get amazing standby... Because deep sleep doesn't happen... But your screen on time will go way down
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] xT29c:
How are people able to install this on Android 11? I just recently learned that the flashing app is broken on Android 11. And the only way that I've seen custom kernals installed onto the pixel devices at this point is using a. Jsom file to import into the app itself. And not using a zip file.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Yeah working on the json, was not aware franco made that mandatory with the new version. It just worked before.

Anyways you can flash with exkm app currently.. I'm also looking into offering premade boot images you can flash in fastboot but you won't get root out of the box that way, would have to manually root the image on your phone and reflash it if you need root.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] xT29c:
Okay. Thanks for the quick reply. One last question if I flash stock boot. IMG back onto my phone for a clean install of your custom kernel does that erase any user data or media files?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
It will not touch your userdata or media files.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] bobbarker2:
You're talking as if he's dead lol. He's still a very active developer.
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] Meth0d:
I dont know if you didnt read the rest of what i wrote or if you just dont want to quote it right but i said:

"Flar2 will always stay in my memory for beening the guy who made my nexus5 run for 2 days on battery and be a lot faster then before."

As that is what instantly comes to my mind when i read the name. I know that hes very active obviously as i am running his kernel on my pixel 4a .....
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] francescod:
Might there been a misunderstanding: I meant to underclock the highest (not the lowest) freqs on Cpu/Gpu, as, on my SD712 I set them to 2GHz instead of 2.3GHz and 355MHz instead of 610MHz on Gpu.

Wouldn't be good for SD730 too, if you're not using high demanding tasks?
[Google Pixel 4a ROMs, Kernels, Recoveries, & Other] HolyAngel:
Alright,

Kernel updated with November patches, some LZ4 updates thanks to eng.stk's base, enabled lzma and lz4 ramdisk support in order to work with twrp or anything else that may require it.

I also uploaded the latest November Stock Boot Image repacked with my kernel, in case you have an unlocked bootloader but do not want to be rooted but want to try it, just download it and flash with fastboot.

Enjoy!