yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
New kernel arrived .. compiled today .:)

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89H_v160611_followmsi.zip

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD35K_v160611_followmsi.zip

I am running the kernel on Android N without problems ... very smooth !

Installation:

1. Reboot into TWRP

2. Install the kernel.zip

3. install SuperSu.Zip (2.72+)

4. reboot into system

Due to supersu installation it will boot twice - no panic, it´s normal :)

Have fun !
[Pixel C Android Development] jeffyca:
any way to add some type of color calibration to the kernel? would be awesome to change the RGB values of the screen
[Pixel C Android Development] followmsi:
Sorry .. in my little branch I use official Google commits only.

Some of them I revert .. but just official chromeos-3.18 sources.

Maybe xceed or NYChitman is able to implement special "stuff" ;)

Cheers
[Pixel C Android Development] jeffyca:
Appreciate the reply and thought I would ask. Love the fact you update the kernel for us to use. Love running the newest and disappointed Google is still using a kernel from April even on the newest release
[Pixel C Android Development] followmsi:
Thanks for the feedback ...

This is actual the reason for this kernel.

To have newer sources as the stock kernel.

Love latest versions too ;)
[Pixel C Android Development] followmsi:
Developer Preview 4

Date: June 2016

Build: NPD56N

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

Google Play services: 8.4

https://developer.android.com/preview/support.html#dp4

Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip

Update.ZIP_PixelC_Ryu_NPD56N-kernel-dragon.zip

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD56N_v160611_followmsi.zip

Have fun on N !
[Pixel C Android Development] followmsi:
Installation of N Preview 4:

We have a new bootloader again .. "bootloader-dragon-google_smaug.7900.20.0.img"

To be safe .. I did the bootloader installation via fastboot before the following steps.

- Reboot into TWRP (v15)

- Install Update.ZIP_PixelC_Ryu_NPD56N-system-vendor.zip

- Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD56N_v160611_followmsi.zip

. Install BETA-SuperSU-v2.74-2-20160519174328.zip

- Reboo into System

Done :)

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

N4 seems to be even quicker as N3 .. I like it :)
[Pixel C Android Development] twirtle2:
Is there any way of checking the bootloader version? I upgraded from DP3 to DP4 using the OTA flash zip file from the factory image site would that have upgraded the bootloader?
[Pixel C Android Development] followmsi:
adb shell getprop ro.bootloader

Google_Smaug.7900.20.0

Works in recovery (v16) and system too ...

Cheers
[Pixel C Android Development] followmsi:
New kernels arrived :)

last commit in this kernel: https://chromium.googlesource.com/c...el/+/dabe7f6f83c51a217310974665c1e899110b5dd3

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD56N_v160617_followmsi.zip

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89H_v160617_followmsi.zip

Have fun !
[Pixel C Android Development] twirtle2:
Fantastic thanks! Looks like OTA updated the bootloader too
[Pixel C Android Development] followmsi:
Actually it was not planned to make a new kernel so quickly again :)

But there are so many fixes right now ... all relevant for Pixel C. :)

22f7042 CHROMIUM: spidev: fix heap overflow vulnerability by Stephen Barber · 12 hours ago chromeos-3.18

535aa2f CHROMIUM: arm64: dragon: disable CONFIG_ION_TEST by Stephen Barber · 16 hours ago

d466ba7 FROMLIST: net: Allow xt_owner in any user namespace by Eric W. Biederman · 16 hours ago

8e64b27 CHROMIUM: drm/nouveau: Use vmalloc instead of kmalloc by David Ung · 19 hours ago

e2bb02c CHROMIUM: arm64: dragon: enable CONFIG_SECURITY_PERF_EVENTS_RESTRICT by Stephen Barber · 22 hours ago

53584b0 ANDROID: FROMLIST: security,perf: Allow further restriction of perf_event_open by Jeff Vander Stoep · 22 hours ago

f4cc8d5 ANDROID: BACKPORT: perf tools: Document the perf sysctls by Ben Hutchings · 22 hours ago

36ce88b CHROMIUM: drm/bridge: ps8640: Add a 3 ms delay before unmuting output by Daniel Kurtz · 24 hours ago

c267140 CHROMIUM: arm64: dts: mt8173-elm: Add ps8640_fixed_1v2 ramp delay by Daniel Kurtz · 24 hours ago

c8dc07f CHROMIUM: config: enable memconsole and VPD on i386, x86_64 and arm64 by Wei-Ning Huang · 24 hours ago

a1203aa CHROMIUM: firmware: google: refactor coreboot table and memconsole by Wei-Ning Huang · 24 hours ago

036a474 CHROMIUM: Add the kasanconfig make target. by Alexander Potapenko · 30 hours ago

Kasan seems to be quite intersting -> kasan - KernelAddressSanitizer, a fast memory error detector for the Linux kernel !

Anyway .. its all included now ... here we go .. the first kasan enabled kernel for Pixel C :)

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD56N_v160618_followmsi.zip

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89H_v160618_followmsi.zip

Same installation like always, via TWRP .. or unzip and use fastboot.

And don´t forget to install SuperSU, if you were rooted before. :)

The next kernel will take a bit longer !

Have fun !
[Pixel C Android Development] Alxoom33:
I had the Recovery Bootloop problem mentioned in the OP. Tried going to terminal and type "fastboot reeboot" did nothing. Tried manually booting into fastboot and used adb on my computer, typed "fastboot reeboot" and nothing happened. Is that the correct adb command?

reebooted system using Nexus Root Toolkit (WUG FRESH). But it still reebooted to recovory. I restored the old 3.18 boot image and it reebooted ok. Not sure why I had so much trouble with loading the new 3.f18 kernel and Boot image.
[Pixel C Android Development] whoamigriffiths:
Check your spelling.

Should be "fastboot reboot"

All the best Rich
[Pixel C Android Development] NYCHitman1:
Not all of that is relevant to Dragon. Maybe 3 of the new 10+ commits.
[Pixel C Android Development] Alxoom33:
Thanks Rich, the correction of the spelling did work and Fastboot rebooted, but right back to TWRP 3.0.2v18. So once I added the updated 3.18 kernel I was in the infamous Recovery bootloop. Fastboot flashing "fastboot reboot" apparantly didn't help. Restored my old Boot partition with the older vesion of the 3.18 kernel and booted up normally. There is something missing in the kernel zip that is causing the bootloop. Perhaps Supersu 2.74 needs to be flashed before flashing the new kernel? Please let me know what you think?
[Pixel C Android Development] whoamigriffiths:
I'm not rooted atm to check, but didn't cheap5k8 add a function to twrp that fixes this issue?

I'll have a bit of of a browse for the info and update if I find it, though in fairness I could very well be just talking out of my arse ;)! (I have rooted this once, but havn't bothered to do it after I switched to the N preview, as it was such a pain to do it)

All the best Rich
[Pixel C Android Development] Alxoom33:
Rich, thank you, as my idea failed. Same results. BTW, I'm on the N4 preview. love the functionality and layers allows for lots of customization. If you can fix this issue with TWRP that would be wonderful, as it is a reoccurring problem with the Pixel C.
[Pixel C Android Development] NYCHitman1:
He added a function into TWRP that fixes the fastboot: unsupported command failure due to the coreboot failsafe getting tripped.
[Pixel C Android Development] whoamigriffiths:
Go to advanced settings in TWRP, there's a setting to fix fastboot, swipe to confirm and you should be done.

That's the fix I was thinking about, I'm not sure if it's the right one for you though.

I'm so out of the loop atm.

All the best Rich

---------- Post added at 07:36 PM ---------- Previous post was at 06:42 PM ----------

Gah, thanks for the clarification, I knew I was clutching at straws.
[Pixel C Android Development] followmsi:
Did it fix your problem ? . . I did test all the kernels before uploading them .. no problems so far.

I do install them via TWRP and install SuperSU directly afterwards .. it has one "normal" bootloop due to SuperSu installation.

It just works fine .. at least for me ..

Sorry, would like to help you better !
[Pixel C Android Development] Alxoom33:
Advanced has fix Contexts, is what you are referring to?

---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------

I had been flashing SuperSu first, then Kernel. Just tried the reverse, as you suggested.

---------- Post added at 05:23 PM ---------- Previous post was at 05:21 PM ----------

It worked! Thanks, the old User error?
[Pixel C Android Development] followmsi:
Fix fastboot.. should be there as well.

You need this if you get "unknown command" while doing fastboot commands .. like "fastboot reboot'".

If you don't get "unknow command" and you are able to flash via fastboot .. etc., You don't need it.
[Pixel C Android Development] followmsi:
Thanks for the update...

Yes, the order is important ;)

Cheers
[Pixel C Android Development] Alxoom33:
Do you mean fastboot linked to my pc; or a terminal command on TWRP Terminal emulator?
[Pixel C Android Development] followmsi:
Yes .. the link to your computer .. there are you using the fastboot command to flash .. etc.

But with TWRP you can fix it, if it's broken.

(Unknown command)

This was made by xceed ... Some time ago.

Cheers
[Pixel C Android Development] Alxoom33:
Thank you. but I checked in TWRP 3.0.2-19/ADVANCED, no fix fastboot, only Fix Contexts.

---------- Post added at 06:42 PM ---------- Previous post was at 06:38 PM ----------

It's not on TWRP 3.0.2.0 on my Nexus 6 either.

---------- Post added at 06:43 PM ---------- Previous post was at 06:42 PM ----------

BTW, what is Fla**** script for image flashing?

---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------

Fla**** script..

---------- Post added at 06:45 PM ---------- Previous post was at 06:44 PM ----------

its not a curse "Fla****"

---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------

Flash-IT LOL!
[Pixel C Android Development] followmsi:
Pls Look on your Pixel C again.. down .. right corner in Advanced Settings - fix fastboot.

No, its not in your Nexus 6 ..

Cheers
[Pixel C Android Development] followmsi:
Pls check again in pixel C .. bottom right corner ..Fix fastboot.

Thanks
[Pixel C Android Development] followmsi:
No, mit on Nexus 6 ... On Pixel C only.

Pls check again ... Right bottom corner.

Thanks
[Pixel C Android Development] Alxoom33:
Ha ha, it wasn't there because I flashed a TWRP Dark Theme zip file that I was using on my Nexus 6. See,https://r.tapatalk.com/shareLink?ur...share_tid=2915584&share_fid=3793&share_type=t

[THEME][TWRP] TWRP Materialised - Dark / Light / Play [01/05/16]

It worked fine with your Pixel C version, but it masked the one button that we were talking about. Reflashed the theme ui.zip and I found it, right were you said it was :)
[Pixel C Android Development] followmsi:
Time for a new kernel ....

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD56N_v160624_followmsi.zip

kernel-chrome-3.18_v160624_NPD56N_boot.img

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89H_v160624_followmsi.zip

kernel-chrome-3.18_v160624_MXC89H_boot.img

Removed the kasan stuff again :)

Changed to another branch: stabilize-smaug-7897.B-chromeos-3.18

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

Fresh sources for the smaug version too ...

4e85de4 Revert "Revert "HACK: CHROMIUM: security: tlk_driver: fix sys_munlock issue"" by Stephen Barber · 7 hours ago stabilize-smaug-7897.B-chromeos-3.18

a0b370f Revert "Revert "HACK: security: tlk_driver: lock/fault userspace pages"" by Stephen Barber · 7 hours ago

1c24ada Revert "security: tlk_driver: add support for PHYS_LIST handling." by Stephen Barber · 7 hours ago

c76aa98 HACK: drm/nouveau: use trylock for cli->mutex during system suspend by Vince Hsu · 2 days ago

c1e33ea UPSTREAM: USB: fix invalid memory access in hub_activate() by Alan Stern · 2 days ago

21c62ad UPSTREAM: AIO: properly check iovec sizes by Greg Kroah-Hartman · 2 days ago

c84d773 CHROMIUM: arm64: dragon: disable yama by Stephen Barber · 2 days ago

....

Installation:

1. Reboot into TWRP

2. Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_VERSION_vDATE_followmsi.zip

3. Install SuperSu.zip (2.72+)

4. Reboot into system

Or just use fastboot :)

Due to supersu installation it will boot twice - no panic, it´s normal !

Have fun ... the summer is magic :)
[Pixel C Android Development] followmsi:
The Google July Update has been released yesterday.

But as it looks like no Update for the Pixel C this time ...

Maybe in August will be the next regular Android M Update ?

Personally I hope Nougat No. 5 will be released soon ;)

Cheers
[Pixel C Android Development] NYCHitman1:
Yeah, it seems that way. I guess they don't think Dragon has any issues lol..

As for N -- I think we'll see a source release in September.
[Pixel C Android Development] dkryder:
the pixel c has been later than the others a few times so i hope it comes in the next week. the security bulletin for july mentions enough that should get a patch.
[Pixel C Android Development] NYCHitman1:
The majority of fixes are in actual AOSP source -- not really many that were device specific.
[Pixel C Android Development] dkryder:
well, the 7/05/16 patch lists around 30 device specific fixes. does not mention which device, but more device specific fixes than there have been in a long time.
[Pixel C Android Development] NYCHitman1:
Those are kernel changes for Bullhead and Angler.
[Pixel C Android Development] EddieK23:
Got into the recovery bootloop, tried to do "fastboot "reboot" through fastboot, but no luck. Anything else I should try?

EDIT: Got it working, re-did the process of flashing TWRP -> Xceed Kernel -> SuperSU and everything works fine now.
[Pixel C Android Development] dkryder:
it appears at least,

cve-2015-8816 / usb, critical

cve-2016-3775 /kernel, critical

" " -0723 / kernel, moderate

" " -3808 / serial interface, high

were marked for pixel c in july device specific. so it would seem that the pixel c is due sometime..
[Pixel C Android Development] NYCHitman1:
Google doesn't operate like that. They release everything at once.
[Pixel C Android Development] Alxoom33:
When I flash TWRP image, SuperSU 2.76.zip and EXceed 8.02 image I still get 3.18.0-00110-g 13482c2 build@srvr.tech #16 Fri June 24 23:07:40 CEST 2016 showing as the kernel version in Settings/About tablet.

I am presuming that this is the latest Chroma 3.18 kernel, not EXceed.

Does EXceed 8.02 show in your's?
[Pixel C Android Development] rsa 329:
Thanks for your work. I'm new to the Pixel as of yesterday. Just flashed your system and vendor images. Do you happen to have the bootloader image as well?
[Pixel C Android Development] followmsi:
Sorry, the bootloader still needs to be done via fastboot.
[Pixel C Android Development] Alxoom33:
You can us WUG's Nexus Root Toolkit to unlock and flash the bootlloader, if you are unfamiliar with fastboot.
[Pixel C Android Development] followmsi:
As it looks like .. released today :)

6.0.1 (MXC89K)

Update.ZIP_PixelC_Ryu_MXC89K-system-vendor.zip

Update.ZIP_PixelC_Ryu_MXC89K-kernel_dragon.zip

Just compiling a new stable smaug kernel .. released soon as well :)

Enjoy !
[Pixel C Android Development] NYCHitman1:
GTFO. GOOGLE!!!!!! I hate you, but I love you at the same time for your deception. Lol
[Pixel C Android Development] followmsi:
And here is the new kernel (boot.img) .. still on the same branch .. stabilize-smaug-7897.B-chromeos-3.18

Not much changes this time ..

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD56N_v160711_followmsi.zip

kernel-chrome-3.18_v160711_NPD56N_boot.img

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89K_v160711_followmsi.zip

kernel-chrome-3.18_v160711_MXC89K_boot.img

Installation:

1. Reboot into TWRP

2. Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_VERSION_vDATE_followmsi.zip

3. Install UPDATE-SuperSU-v2.76-20160630161323.zip

4. Reboot into system

Or just use fastboot

Due to supersu installation it will boot twice - no panic, it´s normal !

Have fun !
[Pixel C Android Development] Alxoom33:
HHmm... now looking at your new Android N kernel in Settings/About tablet that I just flashed which says 3.18 and today's date with followmsi@..., I guess I must have been previously running the EXceed kernel all along. I expected to see 8.12 somewhere.

Oh well, I think that the Chroma kernel that I just flashed is probably better. Although I am not aware of how the various features compare. It sure flashes easier. Thank you for all of your work.
[Pixel C Android Development] followmsi:
The kernel will show version (3.18) and builduser@buildmachine .. and date.

Maybe you can adjust the output, but I keep it default unchanged.

Can't comment on all the kernel features .. just using latest google sources.

For me the kernel is very stable .. No unexpected reboots anymore which I had on some stock kernels before.

Cheers
[Pixel C Android Development] dkryder:
ok.
[Pixel C Android Development] NYCHitman1:
I was wrong. They deceived us all! :highfive: :laugh: :crying:
[Pixel C Android Development] dkryder:
they were not going to let you skate on ROM work this month. :)
[Pixel C Android Development] Alxoom33:
Thank you for your response. I am used to development on my old Samsung S4 and my old Moto Xoom and current Nexus 6, where there has been a lot of Rom development and development of a myriad of custom kernels, like Franco and Elemental X. So my thinking about development on the Pixel C needs to be adjusted. Please correct me if I'm wrong, but it appears that Pixel C development is at a much earlier stage due to the Pixel's hardware limitations and the much lower number of users and developers on this platform. Is this correct.

So the available 3.18 kernels, for Android N are not highly customized as in the other devices. They are mostly stock. My understanding is the 2 Pixel C Android N kernels are the Chromeos 3.18 kernels that you have been compiling and developing, and the XCeed 8.12kernel that is being developed by [MENTION=4867279]cheep5k8[/MENTION]. However, at this stage, both seem to be primarily stock kernels that are relatively stable for controlling the rooted Pixel C devices presently running Android N DP4. Please let me know if I have any misunderstanding of the present state of development, or if you would like to, please provide additional details. Thank you very much for all of your efforts and excellent work.
[Pixel C Android Development] followmsi:
I can not speak for the xceed kernel, just for my little work.

Yes, like written before. My kernel is based on google sources only.

I just use newer sources as the stock kernel, which is using approx. 1-2 month older sources.

Some of the commits will not been used for next stock kernel, some of them are part of the next stock kernel.

But you are right it's all stock and no own code and modifications like in Franco kernel .. or other kernels on other devices. Have used Elemental X on flo myself, nice work.

My knowledge and my time is limited, I will not be able to make own modifications like this.

Yes, the community is not as big as for other "nexus" devices.

Maybe that's the point .. Its not a 'real' nexus device as well.

But the community is growing ... day by day ;)

And even the Pixel C is a little bit special .. I still like it ;)
[Pixel C Android Development] Alxoom33:
Thank you [MENTION=5480152]followmsi[/MENTION] I appreciate your work and contribution to the Pixel C community... I have been enjoying my Pixel C much more since I found this little community. :)

By the way, this new kernel is smooth!.
[Pixel C Android Development] sxg75:
Is it somehow possible to extract and flash bootloader from latest MXC89K factory image?

Edit found it in the .bat files

fastboot flash bootloader bootloader-dragon-google_smaug.7132.295.0.img
[Pixel C Android Development] followmsi:
Yes, it's inside the .tgz file.

Flash it via fastboot.

As I remember, there was no change to MXC89H, pls check.
[Pixel C Android Development] sxg75:
Will have a look. Will flashing BL erase internal memory (data/media)?

Edit had a look - 89h also has bl 7132.295.0.img included.

Edit2 - flashing bootloader didn't wipe anything.
[Pixel C Android Development] sxg75:
Just for info here also: flashed two zips from over there to have sustainable permissive mode which stays alive even after reboot 8-] those logd and sh-skripts worked for me on NPD56N, also on Kernel used from this thread here.
[Pixel C Android Development] followmsi:
It´s time for a new Android Nougat Preview ....

Developer Preview 5

Build: NPD90G

system-vendor ...

Update.ZIP_PixelC_Ryu_NPD90G-system-vendor.zip

The new stock kernel ...

Update.ZIP_PixelC_Ryu_NPD90G-kernel-dragon.zip

And a fresh new stabilize-smaug-7897.B-chromeos-3.18 kernel .. for both versions ..

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD90G_v160718_followmsi.zip

kernel-chrome-3.18_v160718_NPD90G_boot.img

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89K_v160718_followmsi.zip

kernel-chrome-3.18_v160718_MXC89K_boot.img

Installation:

1. Reboot into TWRP

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

3. Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD90G_v160718_followmsi.zip

4. Install UPDATE-SuperSU-v2.76-20160630161323.zip

5. Reboot into system

Due to supersu installation it will boot twice - no panic, it´s normal !

Pls flash the new bootloader-dragon-google_smaug.7900.27.0.img via fastboot.

Running fine on Android Developer Preview 5 now :)

Enjoy !
[Pixel C Android Development] zezayer:
DP5 with the new kernel working fine. Lets see if google have fixed the crashing when the RAM gets full issue.
[Pixel C Android Development] Alxoom33:
Thank you, [MENTION=5480152]followmsi[/MENTION], the update to NPD90G went great. I extracted the bootloader from the Google supplied zip file. I hope that is what your instructions meant and flashed the various zip files. I hope I flashed everything I needed, usually I just flash the tar file, root and custom kernel.

All looks good as far as the system UI. Smooth and stable.

One issue that puzzles me is I was able to debloat the System and inset some custom apk's and I was abl to flash the custom Navbarz that I use. However, when I tried to restore my layers, it didn't take. I even tried to reflash from scratch. But nothing happened. Anybody have a similar experience with layers and any insights?

Thanks,
[Pixel C Android Development] followmsi:
Yes, the bootloader still needs to be taken out from the Google firmware .tgz file.

On other devices you can flash the bootloader via update.zip as well. To be honest the "unknown" chromeos bootloader scares me to work on this one ;)

The real advantage of Update.zip you have when there is no bootloader update at all.

No fastboot, no cables just TWRP ;)
[Pixel C Android Development] Alxoom33:
Yes, that is very convenient! Any idea what this new bootloader does differently than the prior one?

Any thoughts on Layers not working on this update?

Also, strange thing happened overnight I charged my pixel on my laptop, in the morning it did not recognize my password. I had to wipe data and re-flash my data from the Nandroid backup I made last night. Now I'm back on the Pixel, but don't understand how my password could have changed or been corrupted.
[Pixel C Android Development] followmsi:
Don't know more details as stated here ... Not much regarding bootloader changes.

https://developer.android.com/preview/support.html

Sorry, can't help you on Layers .. maybe you ask inside their forum(s) too.

Also the battery one .. don't see any relationship to password reset either.

For me No. 5 works quite well .. charging and usage - no problems so far.

Have seen that DP5 System.img uses approx. 200MB more disk space as DP4 System.img.

It's the "near" final system .. wait for September .. there will be more fixes coming ;)