yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
Let's integrate the few Google kernel changes for March as well ..

tegra-3.18_kernel_dragon_v180308_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for Mar 2018 -> android-8.1.0_r0.33

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2018-03-08

Enjoy :p
[Pixel C Android Development] Alxoom33:
OK, the Pixel C is not so EOL. Just not in Android P beta program.

I can rock O until Google stops providing monthly security patches. :)
[Pixel C Android Development] Alxoom33:
I can't get into TWRP, keeps asking me for password and dosn't recognize it. Even though I deleted my pin in security. Will play with this tonight, when I have time.
[Pixel C Android Development] skawtnyc:
Seems to be working fine. The current version of TWRP (3.2.1) seems to have issues with the latest encryption of Oreo 8.1. I usually just put the files I need onto a USB stick and flash them that way.
[Pixel C Android Development] Alxoom33:
I was able to get by the encryption issue by booting TWRP with fastboot. Then flashed the new kernel, Magisk.zip and the new kernel again. Everything now working properly. Thanks [MENTION=5480152]followmsi[/MENTION]!
[Pixel C Android Development] drewski_1:
are you rooted?

on March, after flashing Magisk 16.0, booting is stuck on Google logo. i tried Magisk 15.4 and got the same

edit: oh, i see you flashed kernel again after Magisk. will give that a go :good:
[Pixel C Android Development] Alxoom33:
Did it work for you?
[Pixel C Android Development] drewski_1:
Yes! :good:

Though I also deleted Substratum files so failed in only changing one thing to isolate the impacts :eek:
[Pixel C Android Development] Alxoom33:
I kept my substratum theming.
[Pixel C Android Development] Alxoom33:
April Google factory's images have dropped. :)
[Pixel C Android Development] followmsi:
Google was quick this month ..

tegra-3.18_kernel_dragon_v180402_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for April 2018 -> android-8.1.0_r0.43

- Based on 3.18.102 kernel sources (Thx to [MENTION=2489052]NYCHitman1[/MENTION] )

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2018-04-02

Enjoy :p
[Pixel C Android Development] Alxoom33:
My TWRP would not deycrypt data.
[Pixel C Android Development] Alxoom33:
I reflashed recovery kernel and Magisk,

Now it works. Not sure why, but I'll take it. Backing up now in TWRP.
[Pixel C Android Development] galearned:
Good Evening [MENTION=5480152]followmsi[/MENTION]:

I would like to try this kernel but, I would like to know what extra features it provides, how would my user experience be improved, etc.

I read the OP for the kernel but I did not see a feature list. Are there are a bunch of tweaks such as persistant USB debugging and MTP, or are those functions outside the kernel? The kernel must have been created to solve some deficiency in the stock kernel?

Where do I read about what the custom kernel does for me, and then if I wanted to go back to stock, is there a stock kernel that can be flashed versus re-installing the factory image?

Regards galearned
[Pixel C Android Development] followmsi:
https://xdaforums.com/showpost.php?p=76346491&postcount=569
[Pixel C Android Development] Alxoom33:
May updates are up!
[Pixel C Android Development] followmsi:
Yes .. very late this month !
[Pixel C Android Development] followmsi:
Google was late this month ..

tegra-3.18_kernel_dragon_v180508_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for May 2018 -> android-8.1.0_r0.57

- Based on 3.18.108 kernel sources (Thx to [MENTION=2489052]NYCHitman1[/MENTION] )

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2018-05-08

Enjoy :p
[Pixel C Android Development] Alxoom33:
June update is up. Flashed updated factory image, TWRP and Magisk.zip. Everything is working well!
[Pixel C Android Development] followmsi:
June 2018 ..

tegra-3.18_kernel_dragon_v180605_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for June 2018 -> android-8.1.0_r0.63

- Based on 3.18.112 kernel sources (Thx to [MENTION=2489052]NYCHitman1[/MENTION] )

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2018-06-05

Enjoy :p
[Pixel C Android Development] Alxoom33:
No issues on flashing the new kernel. Running well so far. Thanks [MENTION=5480152]followmsi[/MENTION]
[Pixel C Android Development] aoleg:
After updating to the latest build (factory image with June security patch + Xceed kernel), my Pixel C is awake about 30% of the time. The following wakelocks are top offenders:

alarmtimer

[timerfd]

NETLINK

wlan_rx_wake

Xceed allows blocking wlan_rx_wake, I believe (through EX Kernel Manager), but the other wakelocks keep my tablet awake. This is an ongoing issue during the last couple days. Don't know what to do, really; any word of advice?

Update: tested with stock kernel; same wakelocks minus the ability to block any with EX Kernel Manager. Back to Xceed now, and would still love an advice!
[Pixel C Android Development] followmsi:
Just did a quick google search ..Similar problems for oneplus

https://forums.oneplus.com/threads/wakelock-alarmtimer-in-4-1-0.510051/

As a first start .. try to clean cache/data of google search app and clock app.

As its not a kernel issue you might continue to google for a better solution .. Or just do a factory reset ;)

Good luck !
[Pixel C Android Development] aoleg:
I ended up doing just this, followed by the installation of Lineage ROM (official build). So far so good; no strange wakelocks and such.

Can you recommend using Xceed kernel with Lineage, or should I stick with what Lineage includes by default?
[Pixel C Android Development] followmsi:
Are you talking about the unified kernel from this thread ? Or the old original xceed kernel ?

I do recommend the stock lineage kernel or the unified kernel .. but no older kernels anymore.
[Pixel C Android Development] followmsi:
July 2018 ..

tegra-3.18_kernel_dragon_v180703_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for July 2018 -> android-8.1.0_r0.74

- Based on 3.18.113 kernel sources (Thx to [MENTION=2489052]NYCHitman1[/MENTION] )

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2018-07-03

Due to holiday season the August releases will be delayed !

Enjoy :p
[Pixel C Android Development] NYCHitman1:
114 just released, but haven't had time to test yet.
[Pixel C Android Development] Vartom:
On the 4.18 kernel the latest, it is possible to launch the recovery of the TWRP 3220. But there are problems in the form of incorrect display of fonts and colors.

Android 8.1 was not launched due to the lack of compatibility of graphics drivers.
[Pixel C Android Development] NYCHitman1:
[MENTION=5480152]followmsi[/MENTION] - .114 and .115 merged. All good on this end.
[Pixel C Android Development] followmsi:
Thanks a lot !

My holidays are coming soooooooon ... still time for a quick dragon kernel :)
[Pixel C Android Development] followmsi:
July 2018 - Part 2

tegra-3.18_kernel_dragon_v180716_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Based on 3.18.115 kernel sources (Thx to [MENTION=2489052]NYCHitman1[/MENTION] )

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2018-07-16

Due to holiday season the August releases will be delayed !

Enjoy :p
[Pixel C Android Development] followmsi:
August 2018

tegra-3.18_kernel_dragon_v180811_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for August 2018 -> android-8.1.0_r0.93

- Based on 3.18.117 kernel sources (Thx to [MENTION=2489052]NYCHitman1[/MENTION] )

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel_2018-08-11

Enjoy :p
[Pixel C Android Development] Panokiaran:
Hello, I found aosp9.0 in your google cloud disk, what is that? Is it exciting Android p?
[Pixel C Android Development] Monazite:
Yes but it's unbootable now.
[Pixel C Android Development] Panokiaran:
Can I improve processor performance by overclocking? Or how do I turn off the temperature limit? I found it should be a dvfs regulator.

I hope to get your answer.

Because the xceed kernel cannot be customized
[Pixel C Android Development] DaWeIII:
I'have tried this kernel. Well so far, but the split screen problem is still here. I have to activate the developer option: Disable HW Overlays (use always GPU to combine screens). That works for split screen, but netflix shows a black screen when using this options, so I have to come back here and disable it again to get netflix working.

is this issue kernel related? or ROM related bug? I know that bug was also in DU build and Official Oreo build...
[Pixel C Android Development] Monazite:
It's AOSP problem.
[Pixel C Android Development] MVP__911:
Thanks for your great jobs :)

Just 2 questions:

1) does this kernel support overclock CPU ?

2) do you change the max/min of cpu in this kernel? (Or still same as stock kernel?)

Thanks
[Pixel C Android Development] followmsi:
No it does not support overclocking.

Just the change current cpu values and all other changeable values via Kernel adiutor app.

The kernel contains a few more scheduler ..etc. .. a few special patches for DRM and other stuff.

And upstreamed to 3.18.117.

But that's it ..nothing more and no plans for more.

Cheers
[Pixel C Android Development] Panokiaran:
I want to adjust the temperature limit, can you give me some information?thanks
[Pixel C Android Development] Vartom:
If you really want to, you can increase this temperature(balanced_tskin_trip). It is responsible for controlling the heating of the case, after which the trotline will turn on.

https://github.com/followmsi/androi...arm64/boot/dts/tegra/tegra210-smaug.dtsi#L480

I advise you not to touch the remaining temperatures. Overheat chipset.
[Pixel C Android Development] Panokiaran:
Sorry, I am a fool, I don't know these things, but I have these ideas, but it is very far away. If I didn't solve this problem, then I should give up pixel c.
[Pixel C Android Development] MVP__911:
Does this kernel support 7.1.2 roms ?
[Pixel C Android Development] Panokiaran:
I have modified it according to your method. I have submitted the source code. I will compile it when I have time. Thank you for your help.

You can view the source code I submitted here:https://github.com/Jedenran/android...arch/arm64/boot/dts/tegra/tegra210-smaug.dtsi
[Pixel C Android Development] Vartom:
You should not be so. Chip burn it. Raise the temperature to 5-10 degrees and enough. But if the heat sink is really bad, you can get a chip blade.
[Pixel C Android Development] Panokiaran:
This is just a test, I am thinking of a better way to improve, such as disassembling it to increase the heat pipe, because its heat dissipation area is small, thank you for your help again.
[Pixel C Android Development] followmsi:
Unified Kernel for Android Pie

tegra-3.18_kernel_dragon_v180903_unicorn-xceed-followmsi-p.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for Magisk !

Changes:

- Ready for Pie

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-pie

Enjoy :p
[Pixel C Android Development] Alxoom33:
Will this kernel work on the latest Oreo patch anticipated to drop today from Google?
[Pixel C Android Development] Alxoom33:
I've, tried to flash Factory image from fastboot mode. Just says

< waiting for any device >

Any one else tried to flash the Factory images?
[Pixel C Android Development] followmsi:
It will boot but no wifi .. new Oreo kernel will come for Sept.
[Pixel C Android Development] NYCHitman1:
What OS?
[Pixel C Android Development] Alxoom33:
Windows 10. Adb and fastboot seem to be working. Just strange.
[Pixel C Android Development] NYCHitman1:
Wouldn't be something specific to the device, but the fastboot binary/drivers.
[Pixel C Android Development] Alxoom33:
So, instead of trying to trouble shoot, I downloaded the full OTA and flashed in TWRP. All is working well. Thanks,

Alan
[Pixel C Android Development] followmsi:
September 2018

tegra-3.18_kernel_dragon_v180907_unicorn-xceed-followmsi-p.zip

tegra-3.18_kernel_dragon_v180907_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for September 2018 -> android-8.1.0_r0.100

- Based on 3.18.121 kernel source

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-pie_2018-09-07

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-oreo_2018-09-07

Enjoy :p
[Pixel C Android Development] NYCHitman1:
No
[Pixel C Android Development] LONGXF:
It seems Tegra K1 supports Setting GPU Frequency.

I am confused Why Tegra X1 can't.
[Pixel C Android Development] NYCHitman1:
Assuming that it has the capability -- it just hasn't been exposed. I don't have any intention of doing it. I can't speak for [MENTION=5480152]followmsi[/MENTION] though.
[Pixel C Android Development] LONGXF:
Thanks for your Reply.

---------- Post added at 12:32 PM ---------- Previous post was at 12:29 PM ----------

Can you add the 'setting GPU Frequency'function into the Kernel?I think it's useful.:laugh:
[Pixel C Android Development] Alxoom33:
Why would anyone want to change stock GPU frequencies?
[Pixel C Android Development] LONGXF:
I Want to Test power dissipation

---------- Post added at 04:27 AM ---------- Previous post was at 03:56 AM ----------

I am a Phone Video Producer.And I want to introduce Pixel C and Tegra X1 to my fans.It contains power dissipation，So I need Set GPU Frequency to ensure different devices have same performance.

That' why:laugh:

Thanks.
[Pixel C Android Development] Alxoom33:
Ok, that actually makes sense.
[Pixel C Android Development] LONGXF:
Can you add this function into the kernel？:silly:

Thanks.:good:
[Pixel C Android Development] Alxoom33:
Not me. [MENTION=5480152]followmsi[/MENTION] is the developer. Have you tried EX Kernal Manager?
[Pixel C Android Development] LONGXF:
I have tried，It said My divice can't support.
[Pixel C Android Development] Alxoom33:
Really! It works for me. See.
[Pixel C Android Development] LONGXF:
It's CPU,not GPU
[Pixel C Android Development] Alxoom33:
Why don't you ask [MENTION=4684315]flar2[/MENTION], the Elemental X developer.
[Pixel C Android Development] Alxoom33:
EX KM works for GPU clock, as well
[Pixel C Android Development] followmsi:
The kernel needs to have code to make the GPU part working .. independent of the kernel manager.

As it looks like this code is missing in dragon kernel.

Sorry .. I don't have the time and the skills to implement stuff like this.

I would need to add code and adjust for tegra .. or grab it from other kernel sources.

It's not just activating an existing kernel feature/config .. like enable network file systems .. etc.

There are no plans to extend the kernel in any way .. just the google security updates and standard 3.18 kernel upstream changes.

Maybe a small additional fix .. if required.
[Pixel C Android Development] LONGXF:
I am confused Why Nexus 9 has much more developers than Pixel C.:crying:What a pity!:crying::crying:
[Pixel C Android Development] Monazite:
N9 is cheaper....but where are these developers? Nexus 9 hasn't got any Pie port yet. The Oreo development stopped for annoying HW acceleration.
[Pixel C Android Development] LONGXF:
Quantity isn't equal to quality.:D:victory:

Pixel C's developers are better.I just want to set GPU Frequency.:crying:
[Pixel C Android Development] Vartom:
In fact, you're not in the wrong topic, this setting does not depend on the kernel. More important is the knowledge of the program at which address it is necessary to set and block the change in the frequency of the GPU. Find this point is easy enough in the power library as part of the touch boot function.

https://github.com/followmsi/android_device_google_dragon/blob/aosp-oreo/power/power_dragon.cpp#L51

Please apply with your request to the developers of the EX manager app.
[Pixel C Android Development] LONGXF:
Thank you:svetius::laugh:.I think It's hard to contact EX manager's developers.Can you tell me how to use 'android terminal emulator' to set GPU Frequency？I think this way is simple.
[Pixel C Android Development] Vartom:
echo 0d > /sys/kernel/debug/dri/dri1/pstate \

chmod 0444 /sys/kernel/debug/dri/dri1/pstate

Approximately so, but I did not check it.
[Pixel C Android Development] followmsi:
October 2018

tegra-3.18_kernel_dragon_v181002_unicorn-xceed-followmsi-p.zip

tegra-3.18_kernel_dragon_v181002_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- Latest Google security fixes for October 2018 -> android-8.1.0_r0.113

- Based on 3.18.123 kernel source

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-pie_2018-10-02

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-oreo_2018-10-02

Enjoy :p
[Pixel C Android Development] JohnnyChim:
It boots with no wifi :(

I am using the latest stock android oreo
[Pixel C Android Development] followmsi:
Sounds like you did install the "p" version .. Pls install "o" version.
[Pixel C Android Development] locuturus:
Hello followmsi,

Can you please confirm for me that your kernel config does or doesn't include wacom tablet support? If not configured would you be willing to configure it so I can test it? My Nexus 10 and Pixel 2 are correctly configured to understand Wacom tablets but the Pixel C for some reason does not work (and never did). I thought I could find the kernel config file in your github but apparently I don't know what I'm looking for... the attached photo shows the config option recommended by Google.
[Pixel C Android Development] NYCHitman1:
https://github.com/followmsi/androi...kernel/arch/arm64/configs/followmsi_defconfig

Run a search here for whether or not wacom is enabled.
[Pixel C Android Development] followmsi:
As it looks like it's not configured.

I can activate for testing in next kernel.

Cheers
[Pixel C Android Development] locuturus:
Thank you for pointing me to it! Line # 3111 appears to be the likely culprit here.

Awesome, I've got my fingers crossed :)
[Pixel C Android Development] followmsi:
Are you still using Oreo ? .. or Pie ?
[Pixel C Android Development] locuturus:
I am running Pie (LineageOS more specifically). Very smooth, by the way. More so than I think the total wipe can account for itself.
[Pixel C Android Development] followmsi:
Pls have a test ..

tegra-3.18_kernel_dragon_v181103_unicorn-xceed-followmsi-p_wacom.zip

The relevant change .. you can see what I did activate - for testing just all 4 available wacom settings.

https://github.com/followmsi/android_kernel_tegra/commit/a4b88704df80e73c7dcd0e34d8b2f1ac8f1a9bcf

Let us know your results ..

Cheers
[Pixel C Android Development] locuturus:
It works! Thank you so much I am very happy now :D I will be testing this a lot and hopefully nothing else broke.

I wonder why those weren't enabled already from the factory—Google devices normally do. The only Google devices ones I've had which didn't accept Wacom input were the og Pixel and the Pixel C. Both share the 3.18–series kernel so I was worried there was a kernel incompatibility between Wacom and Android. Nexus 5 (3.4?), 10 (3.4 kernel), 6P (3.10 kernel), and Pixel 2 (4.4 kernel) all work out of the box. But my newer and more portable Wacom devices require at least 3.17–series kernels so my Nexus 10 has to use an older Wacom and it's a pain to bring it around with me. Now I can use the Pixel C!

Regards,

~Dave
[Pixel C Android Development] followmsi:
Good news !

For now we will keep the settings in unified "p" kernel only.

Later on we can enable in default lineage kernel too .. maybe "backport" to lineage-15.1 kernel too.

Cheers
[Pixel C Android Development] Alxoom33:
November factory images are up.
[Pixel C Android Development] followmsi:
November 2018

tegra-3.18_kernel_dragon_v181106_unicorn-xceed-followmsi-p.zip

tegra-3.18_kernel_dragon_v181106_unicorn-xceed-followmsi-o.zip

Installation:

1. Boot into TWRP

2. Install the Kernel Update.Zip file

3. Reboot into system .. no need for SuperSU / Magisk !

Changes:

- No Google kernel updates for dragon this month !

- Based on 3.18.124 kernel sources

- Activated WACOM support (Oreo and Pie)

Sources:

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-pie_2018-11-06

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-oreo_2018-11-06

Enjoy :p
[Pixel C Android Development] Alxoom33:
Working great on my pixel C, November update.
[Pixel C Android Development] xciteful71:
Been following the thread - root question

I've been following this thread and have read through all 77 pages of info. First off, the hard work and dedication to continuing support for the Pixel C is commendable - much appreciated.

Question: unless I have misunderstood the process, I'm still unaware of whether I need to have SU enabled to use this unified kernel. And regardless of whether that is true or not, do you have to flash the kernel after every flash of the LineageOS Nightlies?

Thanks in advance...
[Pixel C Android Development] Alxoom33:
Should we use this p kernel for the new lineage 16.0 build, or keep the one installed with the room?
[Pixel C Android Development] followmsi:
No, no need to have SU installed .. The kernel installer just takes care of existing SU installation - to prevent reinstall of SU/Magisk.

Yes, you need to flash the kernel after each Lineage update !
[Pixel C Android Development] followmsi:
Yes .. Like the "o" version for Oreo builds we have the "p" version for Pie builds.

Maybe later on we use unified kernel as standard Pie kernel .. Not sure yet.
[Pixel C Android Development] Alxoom33:
Thank you! Didn't know if I should use this Pie kernel since your lineage 16.0 is a few weeks newer. Just wanted to make sure this one is compatible and recommended to use with the newest Lineage build.
[Pixel C Android Development] xciteful71:
Thanks for the response. That provides much need guidance. I'm assuming if anything goes wrong with the kernel flash I'll just need to re-flash the boot.img to get the original kernel back.
[Pixel C Android Development] followmsi:
Yes, in case of problems just restore boot.img only.
[Pixel C Android Development] xciteful71:
Installed the kernel

Installed the latest kernel. Going to test through it today. So far no problems.

- 15.1 20181120-NIGHTLY-dragon

- tegra-3.18_kernel_dragon_v181106
[Pixel C Android Development] xciteful71:
Still no problems

Used it all last night. Nothing came up as problematic.

RAM usage was quite interesting. My device would sometimes go down to 97MB and then

all the way up to having 700MB of free RAM. I hadn't seen that sort of swing before in the RAM

management.

Question: what specifically does this kernel provide, over the stock LineageOS kernel besides

security updates, etc?
[Pixel C Android Development] xciteful71:
Still going strong

Haven't had one hiccup to speak of.

Good work.
[Pixel C Android Development] 夜霜行:
Love you, great work:svetius::svetius::svetius: