yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] nigelhealy:
If you root then automatic OTA won't work usually as it detects the change, so you have to download the full ROM from Google and use a PC with fastboot to flash. That means you need a PC basically to keep current.

What followmsi has done has put the images from the source full ROM into recovery flashable zips format so you download on the Pixel and boot into recovery and install. You'd have the kernel zip, the system vendor zip, the SuperSU zip, install all 3 and reboot, no PC required. It is a good idea to keep your current working and the next to install saved so if the install fails you flash the prior working.

You have choice of 3 kernels and there hasn't been really a discussion of the benefits of each, so try each and form your own conclusions. I tried them and I couldn't spot anything but the tetra one seems a bit better wifi but I could just be random benefit with varying congestion with neighbor routers.

Prerequisites are unlock bootloader and flash recovery which needs a PC. To upgrade recovery then use flashing app or in recovery install image.
[Pixel C Android Development] followmsi:
For the chromeos kernel .. like on the first page described.

The last change (commit) inside this kernel is :

https://chromium.googlesource.com/c...el/+/1e924326fc71f9eccf81cccf155ba1316b49ba94

The complete change log:

https://chromium.googlesource.com/c...nel/+log/stabilize-smaug-7897.B-chromeos-3.18

As it looks like, since Android N there are some more "tegra" kernel activities inside the google aosp sources too ..

The following "tag" has been used for the "tegra" kernel ..

https://android.googlesource.com/kernel/tegra/+/android-7.0.0_r0.16

And the latest commit ...

https://android.googlesource.com/kernel/tegra/+log/c66b63ef6aff27146c34c9d7c720151119213202

Again .. not much new google sources for the Pixel C kernel in the moment.
[Pixel C Android Development] followmsi:
Thanks for the explanation.

Just to clarify ... the 3 different kernel versions.

1. The stock kernel from google - the boot.img used by the current factory firmware - just packed into TWRP flashable .zip format.

Update.ZIP_PixelC_Ryu_NRD91D-kernel-dragon.zip

2. Chromeos kernel sources from chromium.googlesource.com. (not released for NRD91D)

3. Tegra kernel sources from from android.googlesource.com.

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD91D_v161004_followmsi.zip

kernel-tegra-3.18_v161004_NRD91D_boot.img

All kernels are using the stock ramdisk from the current build version (NRD91D) - to be compatible with the rest of your system.

And they are built on default kernel config. (dragon_defconfig)

https://android.googlesource.com/ke...0.0_r0.16/arch/arm64/configs/dragon_defconfig

Not sure if I will continue on tegra and chromeos .. will monitor both sources for a while.

Again, the purpose of these kernels is just to use "newer" sources as the stock kernel is using.

All the same company anyway :)
[Pixel C Android Development] m0ritz:
[MENTION=5480152]followmsi[/MENTION], [MENTION=4775959]nigelhealy[/MENTION],

Thank you for your insight. I will give it a go as soon as I have my computer with me to unlock the bootloader. (so far I did not see the need for it)
[Pixel C Android Development] followmsi:
There were some changes yesterday ... a few new commits for the Pixel C kernel.

Moving from android-7.0.0_r0.16 to android-7.0.0_r0.18.

7cb4bfe ANDROID: binder: Clear binder and cookie when setting handle in flat binder struct by Arve Hjønnevåg · 8 weeks ago android-tegra-dragon-3.18-nougat android-7.0.0_r0.18

807f6f4 ANDROID: binder: Add strong ref checks by Arve Hjønnevåg · 9 weeks ago

8272776 UPSTREAM: arm64: perf: reject groups spanning multiple HW PMUs by Suzuki K. Poulose · 1 year, 7 months ago

74a2fe6 UPSTREAM: net: Fix use after free in the recvmmsg exit path by Arnaldo Carvalho de Melo · 7 months ago

d76cb12 BACKPORT: tcp: make challenge acks less predictable by Eric Dumazet · 3 months ago

596a9a5 binder: prevent kptr leak by using %pK format specifier by Nick Desaulniers · 7 weeks ago

4a74783 Revert "HACK: memory: tegra: Do not go to 40.8 MHz EMC" by Danny Huang · 3 months ago

f6e6f00 CHROMIUM: clk: tegra: set sbus rate to minimum when no user enabled by Danny Huang · 3 months ago

046bb05 CHROMIUM: clk: tegra: keep sbus clock always on by Danny Huang · 3 months ago

f3b81d7 CHROMIUM: clk: tegra: set SCLK source to PLL_P by Danny Huang · 3 months ago

12b8859 drm/panel: lpm102a188a: Avoid backlight updates when panel is disabled by Adrian Salido · 10 weeks ago

9ed6fc6 FROMLIST: usb: xhci: Fix panic if disconnect by Jim Lin · 3 months ago

Here we go ...

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD91D_v161005_followmsi.zip

kernel-tegra-3.18_v161005_NRD91D_boot.img

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-23.img

2. Install Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD91D_v161005_followmsi.zip

3. Install SR1-SuperSU-v2.78-SR1-20160915123031.zip

4. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy !
[Pixel C Android Development] nigelhealy:
TBH given this kernel is just patches, if you don't need root I'd stay locked. I am using root for AdAway (I miss Xposed sob sob).

What followmsi work helps with is the PC-less benefits of current ROM and root.
[Pixel C Android Development] m0ritz:
PC-less until you installed TWRP via ADB with a computer... Or am I missing something?
[Pixel C Android Development] Alxoom33:
Thanks for all of your help. Updated flawlessly. By the way, I no longer get the "No OS detected" warning when reebooting in TWRP.
[Pixel C Android Development] nigelhealy:
I think you meant fastboot?

Yeah it's fastboot oem unlock (wipes), then fastboot flash recovery two.img, then use the key sequence to get to bootloader and select recovery, then you don't need PC.

Or oem unlock, then fastboot boot twrp (so not install) then sidpad install SuperSU, then you got root then flashing twrp image then into recovery.
[Pixel C Android Development] nigelhealy:
Views of getting your built kernels for 7.1 Preview?
[Pixel C Android Development] followmsi:
Here you are ...

Android 7.1 Developer Preview (NPF10C):

Update.ZIP_PixelC_Ryu_NPF10C-system-vendor.zip

Update.ZIP_PixelC_Ryu_NPF10C-kernel-dragon.zip

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPF10C_v161020_followmsi.zip

kernel-tegra-3.18_v161020_NPF10C_boot.img

Still need to install it myself :)
[Pixel C Android Development] En Kee:
Tried with dirty flash : Bootloop to recovery

Tried full wipe : Bootloop to recovery

I had to install image factory. Rooted with 2.78 SR1 and it works.
[Pixel C Android Development] followmsi:
Sorry, I can not replicate this problem.

It seems there are some more Pixel C owners with the same issue.

All my installations are "dirty" .. running the same data partition since verison MXB48K.

And I always use the Update.zip files.

Just did the dirty upgrade to Android 7.1 Developer Preview - the installation was smooth as always.

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-23.img

2. Install Update.ZIP_PixelC_Ryu_NPF10C-system-vendor.zip

3. Install Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPF10C_v161020_followmsi.zip

4. Install SR1-SuperSU-v2.78-SR1-20160915123031.zip

5. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Cheers
[Pixel C Android Development] En Kee:
I never had this problem with your packages before, so it's weird. Thank you anyway for your answer ! :)
[Pixel C Android Development] Alxoom33:
Just wanted to let you know that this update/kernel combination has been running extremely fast and smooth. Just an eye test...I really seems to have unlocked the potential of the Pixel C.
[Pixel C Android Development] Reuben_skelz92:
Sorry for noob question. So is this kernel different or better than stock?
[Pixel C Android Development] Alxoom33:
You will probably need to wait from an answer from [MENTION=5480152]followmsi[/MENTION]. I think that it is a bit better, but definitely different from stock.
[Pixel C Android Development] Reuben_skelz92:
Thats cool. So can I just flash the kernel over stock? I'm on 7.1.1
[Pixel C Android Development] nigelhealy:
Add me to the list who has tested the 7.1, I'm on the system-vendor and the followmsi tegra kernel, also fyi using supersu, the systemless-adaway and then the adaway app.

I can't prove it, more a feeling, might be wrong, but Wifi seems best on Tegra kernel.
[Pixel C Android Development] nigelhealy:
If you're on stock, then yes you can just flash the kernel zip in recovery. Of 2 followmsi kernel choices, I prefer the tegra one it seems better on Wifi for me.

The system-vendor zip is so you can bypass using a PC to fastboot flash and just update via recovery without a PC.

Make a backup is always recommended.

What I do now is keep the new latest kernel zip and system-vendor zip and the version before kept stored so if an update fails I can go back.
[Pixel C Android Development] Reuben_skelz92:
OK will try the tegra one:) is performance or battery any different?
[Pixel C Android Development] nigelhealy:
I can't tell, the battery life is so good on Pixel C it would take a huge effort where you ran for days consistently usage before a conclusion could form with any chance of being valid.

Performance is good, so good I can't tell if its any different speed.

The only weakness for me was Wifi and BT and they are better, but my Wifi performance in a corner of the house where it often drops is worse in evening when the neighbor is home and using their Wifi more, so I can't really prove anything it could be coincident.

So its a conditional opinion, not a firm opinion on preference. I encourage you to try the 3 kernels and form your own conclusions.
[Pixel C Android Development] Reuben_skelz92:
I know what you mean. It's so quick with amazing battery life anyway. But the tegra one to me doesn't seem as snappy
[Pixel C Android Development] nigelhealy:
If that is true it should be measurable, define "snappy" what exactly is slower, if it is say loading an app then get a stopwatch and time loading apps., if an app is slower doing something then time it.
[Pixel C Android Development] Reuben_skelz92:
To be honest like you its just feeling opinion lol
[Pixel C Android Development] nigelhealy:
So I update to the 7.1 and my wifi got unusable when I moved my unit further from the Wifi router, so then I downgraded back which led to heaps of problems. Wished I'd taken a backup. Ended up having to go into fastboot flash factory then move forwards from there.

The best wifi for me is the 91D Tegra, but this may be unit and router specific YMMV.
[Pixel C Android Development] Alxoom33:
Seems pretty fast to me. Maybe you have something else going on.
[Pixel C Android Development] nigelhealy:
I also don't have a strong view on this and didn't measure in a meaningful way, but the 7.1 preview also for me seemed a little laggy, but could be imagination.

I'm back on the last 7.0 as Wifi better (I have no idea why).

---------- Post added at 11:26 PM ---------- Previous post was at 11:04 PM ----------

I was on the 7.1 and Tegra kernel. Wifi bug on 7.1 preview is it shows a Wifi signal (good) but never gets an IP address, I was thinking might be just the foilables of my unit/router combination, I tried setting static IP but won't fix. Going back to the last 7.0 fixed it.

Might be unit/router specific issue, but recommend nandroid backup and keep the past/next both system-vendor and kernel zips to go back.
[Pixel C Android Development] Yostie:
Can someone please explain to me the difference between these two kernels.

Update.ZIP_PixelC_Ryu_NPF10C-kernel-dragon

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPF10C_v161020_followmsi

Cheers
[Pixel C Android Development] followmsi:
Pls have a look here ..

http://xdaforums.com/showthread.php?p=68982504
[Pixel C Android Development] Alxoom33:
I have not had any wifi issues with 7.0 or the 7.1.1 preview. All good here, running very fast and smooth with the [MENTION=5480152]followmsi[/MENTION] modified kernel.
[Pixel C Android Development] GonzoKSV:
Flashed dirty without problems.

Since 7.0 I have an Bluetooth issue (force close Bluetooth). Well, the update to 7.0 was regular before I had opened the bootloader.
[Pixel C Android Development] 530farm:
has anyone had any success with PHH supersu instead of chainfires? trying to avoid that company who bought chainfire. Looking to try the 7.1 preview
[Pixel C Android Development] drewski_1:
haven't tried PHH for awhile, but Chainfire has his own releases in the SuperSU beta thread (v2.78 SR2) which works to root the 7.1.1 preview

. . . not sure how long that will continue (his own releases)
[Pixel C Android Development] followmsi:
Another month .. another release -> NRD91N

system-vendor:

Update.ZIP_PixelC_Ryu_NRD91N-system-vendor.zip

stock kernel:

Update.ZIP_PixelC_Ryu_NRD91N-kernel-dragon.zip

Seems to be the same bootloader as used for the final version .. bootloader-dragon-google_smaug.7900.27.0.img

A fresh compiled tegra-3.18 kernel will follow within the next days ..

Cheers
[Pixel C Android Development] Alxoom33:
Wow! I didn't even get the ota notification yet. Anything exciting here! ;)
[Pixel C Android Development] Alxoom33:
Having a problem here. Getting android.process.acore fail messages. Gmail fc. No Camera or Settings icon. No recents.

---------- Post added at 06:17 PM ---------- Previous post was at 06:15 PM ----------

Help :0)

---------- Post added at 06:23 PM ---------- Previous post was at 06:17 PM ----------

I'm going to dl again and see if it was a bad dl. I flashed System-Vendor Zip. Dragon-Kernel.Zip and Super su 2.78 SR3

---------- Post added at 06:56 PM ---------- Previous post was at 06:23 PM ----------

Still having an issue.

---------- Post added at 06:56 PM ---------- Previous post was at 06:56 PM ----------

Any ideas?
[Pixel C Android Development] Alxoom33:
Feeling pretty foolish mistakenly flashing back to 7.0 from 7.1.1. No wonder I was getting fc's.

---------- Post added at 02:12 AM ---------- Previous post was at 02:09 AM ----------

Impatiently waiting for the next beta update.
[Pixel C Android Development] followmsi:
Yes , it's the monthly 7.0 update. :)

The new November 7.1.1 preview we follow once published.

Cheers
[Pixel C Android Development] Alxoom33:
Thank you, I found out I jumped the gun when I wiped my data and got a beta update notification back to 7.1.1 relase 1 (C).
[Pixel C Android Development] followmsi:
Time for a new kernel .. and some strange issues too :)

Yesterday Google released some new tegra kernel sources .. there are 2 new relelvant tags this time ..

https://android.googlesource.com/kernel/tegra/+/android-n-mr1-preview-1_r0.1

AND

https://android.googlesource.com/kernel/tegra/+/android-7.0.0_r0.36

There are a lot of commits ..

https://android.googlesource.com/kernel/tegra/+log/5369ac86bb1fec13ae7e1fc979e8f1f16b1e192b

I did compile both versions .. but on both versions SuperSU installation is failing - at least for me. :(

( Tested 2.78 SR1 + SR3 on NPF10C)

The new kernels are booting fine ... but proper SuperSU installation seems to be impossible.

Have seen similar problems on November release for other devices.

Let´s wait for more information on this topic.

As we don´t want to produce more problems .. I did compile a fresh version based on the previous "stable" android-7.0.0_r0.18

tag.

The kernel below is running fine on NFP10C and SuperSU 2.78 SR3 ..

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPF10C_v161108_followmsi.zip

kernel-tegra-3.18_v161108_NPF10C_boot.img

And for the new November 7.0 release as well ..

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD91N_v161108_followmsi.zip

kernel-tegra-3.18_v161108_NRD91N_boot.img

My Pixel C is just restoring from backup - the second restore today. :)
[Pixel C Android Development] followmsi:
Anyone who did install NFP10C stock kernel .. e.g. stock boot.img ?

Similar problems to upgrade/install SuperSU ?
[Pixel C Android Development] Alxoom33:
I had all kinds of problems, SuperSU was the least of them. But I was accidently flashing over the 7.1.1 beta release. I erased my user data, discovered that I had gone backwards to 7.0 and restored my 7.1.1 C backup. I'm sorry that I cannot be more helpful.
[Pixel C Android Development] Shadowzerosix:
followmsi,

You seriously rock!

I as you can see don't post much in forums, but had to login just now to tell you that your images worked flawlessly and beautifully

*(For anyone in a similar predicament) from having nothing flashed or a bootable ryu....

Downloaded (don't as why) stock NPF10C.zip from Google dev:

fastboot flashed: boot, vendor, cache, (system.img didn't flash)

fastboot flashed your TWRP recovery image conveniently provided.

....Then

Downloaded your most recent NPF10C update.zips:

Update.ZIP_PixelC_Ryu_NPF10C-kernel-dragon

Update.ZIP_PixelC_Ryu_NPF10C-system-vendor

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPF10C_v161116_followmsi

and then lastly your SR4 SuperSU

Using your conveniently provided MTP driver was able to drop all the update.zips onto /sdcard

flashed one by one

Upon reboot was greeted with Google logo (reboot during process as per SU boot) and then..... lastly..... the Google boot animation

As beautiful as nougat is, about 7-10 seconds later was prompted for the setup.

again followmsi, you friggin rock!

ESPECIALLY a thanks for having all zips in one easy to access location

Thank you for your hard work and contribution here I was pretty frustrated earlier.

Second note: For those who are having Wifi issues with ryu... if it's any constellation, my device has had ZERO connectivity issues EVER, even now being on this build for 2 hours now updating and accessing personal repository for job specific stuff.

I don't mean to be a brag, but if I can help with something (device info, etc.), let's talk (in relevant forum).
[Pixel C Android Development] Alxoom33:
The new kernel and SuperSu 2.78 SR 4 worked great on 7.1.1 beta. Thanks [MENTION=5480152]followmsi[/MENTION]
[Pixel C Android Development] revengers:
NPF10C_v161116

Same thing here, flawless install and awesome performance; many thanks [MENTION=5480152]followmsi[/MENTION] :cool:
[Pixel C Android Development] Deltalfa:
Could anyone explain me what are this files and what Can i do with? ( Searching somethings to improve stock 7.1 n previews and rooting)
[Pixel C Android Development] Alxoom33:
These files help your Pixel C run better, smoother, faster. Read the OP (opening post) on the first page and some of the linked threads. That should help.
[Pixel C Android Development] Deltalfa:
After wiping all, and flashed stock 7.1, trying to flash kernel tegra but nothing.
[Pixel C Android Development] followmsi:
Do you flash via fastboot or TWRP ?

What is the detailed problem ?
[Pixel C Android Development] Alxoom33:
Did you check to see if you had a bad download? I sometimes dl twice just in case.
[Pixel C Android Development] Deltalfa:
Yes I do. But check my procedure:

Stock 7.1

Flash tegra kernel 1616ecc with tarp

Should I do something else?

Edit: I m performing twrp bootloop also after fastboot reboot
[Pixel C Android Development] followmsi:
Install full 7.1.1 Preview 1 again.

Reboot into system once - data will be encrypted.

Reboot into fastboot and install the 161116 kernel boot.img via fastboot.

Reboot into system again and check the new kernel.

Does it work ?

If you want unencrypted data partition and root you need install TWRP via fastboot and boot directly into TWRP.

Format data and install SuperSU.zip and then reboot into system.

Always when you install a new kernel you need to install SuperSU.zip afterwards !

This is independent of the kernel version .. tegra or stock.

Look a few threads above for kernel installation on unencrypted and rooted devices via TWRP.

Good luck.
[Pixel C Android Development] Deltalfa:
Stock ,7.1 with ,(flash-all) so via fastboot. Then reboot, complete wizard, reboot to fastboot, flash twrp and then stock in bootloop! So what can I do, and also, before I make all this things, is was on 7.1 with twrp that working, so I simply flash the update.zip with tegra kernel but then bootloop in twrp
[Pixel C Android Development] followmsi:
Don't know what did go wrong in your case .. as it was working before.

As you have the bootloop now ..

Try to install stock kernel again - via TWRP (dragon-kernel.zip) or use fastboot.

Does it boot into system now ?

Don't forget SuperSu in between .. if you had it before.
[Pixel C Android Development] Deltalfa:
When I have to flash SuperSU?
[Pixel C Android Development] followmsi:
Always AFTER you flashed a new boot.img.
[Pixel C Android Development] Deltalfa:
All done:) performing some random reboot it's normal? Or I have to RMA.....again
[Pixel C Android Development] followmsi:
My last random reboot is long time ago.

Also no unexpected reboots on 7.1.1
[Pixel C Android Development] followmsi:
Android 7.1 Developer Preview 2

Date: November 2016

Build: NPF26F (Nexus 5X, Nexus 6P, Nexus 9), NPF26H (Pixel C)

Emulator support: x86 & ARM (32/64-bit)

Google Play services: 9.6

Update.ZIP_PixelC_Ryu_NPF26H-system-vendor.zip

Update.ZIP_PixelC_Ryu_NPF26H-kernel-dragon.zip

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPF26H_v161122_followmsi.zip

kernel-tegra-3.18_v161122_NPF26H_boot.img

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-23.img

2. Install Update.ZIP_PixelC_Ryu_NPF26H-system-vendor.zip

3. Install Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPF26H_v161122_followmsi.zip

4. Install SR4-SuperSU-v2.78-SR4-20161115184928.zip

5. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy DP2 !
[Pixel C Android Development] Deltalfa:
Theres some new feature?
[Pixel C Android Development] Alxoom33:
Thank you! Had to flash twice to get out of recovery root. All good now. Substratum and layers still mot working... however.
[Pixel C Android Development] followmsi:
Had no problems .. It seems the battery last longer on DP2.
[Pixel C Android Development] Alxoom33:
Got a few apps fc'ing. Gmail, Chrome beta and... Twitter. Maybe apps not completely updated for this ui. Runs smoothly[emoji4]
[Pixel C Android Development] revengers:
DP2 has been performing fine for me as well, I could not duplicate an FC problem with GM or Chrome Dev; not sure about Twitter (I don't have it)

I was able to push the system to freeze up on me by forcing kodi to run in a free-form window along with an online webcast stream and mightytext. This happened only once and I had to cold boot, could not duplicate though. Overall very happy with battery life

Thanks
[Pixel C Android Development] followmsi:
My Pixel C is broken :(

The right side of the screen goes crazy .. seems to be a known Pixel C issue.

RMA process has started .. google will send me a new tablet.
[Pixel C Android Development] Alxoom33:
So sorry about your tablet! But look at the bright side, you will soon have a brand new Pixel C [emoji2]
[Pixel C Android Development] revengers:
Do we know if that is a hardware flaw? Pretty disappointing, if so...:(
[Pixel C Android Development] followmsi:
I strongly believe it´s a hardware issue.

Running the same software level without any problems for one week - suddenly the screen issue started.

If you get strange screen artifacts in recovery mode (twrp) it´s not related to the current system version you are running on.

The bootloader has not changed too.

Here you can have a look .. very similar to my problem: https://www.youtube.com/watch?v=u6PWmJrKfFc

The replacement unit has been sent via DHL Express - will be here soon :)
[Pixel C Android Development] revengers:
Thanks; I bet the issue is old enough to have been assessed (and addressed) at production/QA stage already. Let us see:cool:
[Pixel C Android Development] Alxoom33:
Very strange. Hope it won't happen again. Good luck with your new Pixel.
[Pixel C Android Development] followmsi:
Back in Town :) .. the first xda message written on my "new" Pixel C.
[Pixel C Android Development] Alxoom33:
That's great! Hope you have better luck with this one. I'm glad you are back on board.

---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------

Is it exactly the same, or are there updates?