yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] cheep5k8:
I've also noticed that I have better reception now, but I've made no further changes to the driver in the time inbetween... Maybe they fixed something in the firmware or Android in the latest update (?)

EDIT: As for the reboots, I only noticed that it had rebooted when I came back to use it a few hours after I've flashed the 7-PREVIEW kernel, so far I have no conclusive leads regarding the reboot reason...
[Pixel C Android Development] beardymcgee:
Ooo does that mean we can make feature requests? :D

If so please let me request

CPU/GPU overclock and GPU Governor support :laugh:
[Pixel C Android Development] cheep5k8:
You guys can really make feature requests whenever you want and I will TRY to honor them, but my time for xceed and TWRP is a bit limited so it might take a while. The boards are primarily there so I don't forget stuff ;)

But if you want something in the kernel just say it... As for overclock and GPU governors, I already tried to OC the chipset, it's very difficult to do in code, I will attempt it again but wasn't successful so far (even when looking at e.g. Tegra 3 OC code).
[Pixel C Android Development] Boal:
Well, in that case I would kindly ask for the bandwidth monitoring to be re-enabled :)

I think you mentioned somewhere that it's probably just necessary to turn on some kernel flags, nothing else.
[Pixel C Android Development] CrazyPeter:
Can I request that it stays as close to stock as possible, with just ROOT, and nothing else. Thanks.

The further a kernel deviates from Google's code, generally the more unreliable it becomes.
[Pixel C Android Development] cheep5k8:
I usually also publish a stock rooted boot image which is the stock kernel for each update release, just root-enabled. You're free to use that, but the xceed kernel is really meant for modding stock and adding new features, improvements, etc.
[Pixel C Android Development] beardymcgee:
There is a stock version released as well on first page, I think the point of this kernel is to add extra things that are above the stock experience
[Pixel C Android Development] Boal:
Unfortunately, the stock kernel on the first page is not up to date.
[Pixel C Android Development] sniperfox47:
GPU over clocking for the Tegra X1 isnt really a kernel thing is it? I thought nouveau was handling the clock rate, by passing instructions to the proprietary firmware?

Correct me if I'm wrong but wouldn't over-clocking the GPU on the X1 in this setup require you to make a whole custom GPU firmware blob?
[Pixel C Android Development] Freak07:
I didn’t check if, but maybe something proprietery in the vendor.img changed.

Okay I still didn’t get a reboot.
[Pixel C Android Development] JoeDat:
Has anyone gotten xceed working on N-preview v2? I've tried both the 6.10 kernel in the OP, as well as V7. 6.10 reboots immediately after the Google logo (next boot goes into recovery), while v7 gets stuck during boot-up (animation is normal, but never boots in to Android). I was sure to wipe data before booting.
[Pixel C Android Development] cheep5k8:
Then it probably won't work. I didn't really have time this weekend to prepare something, also not entirely sure how to get SuperSU with xceed working on NPv2.

Hope to make some updated builds this week.
[Pixel C Android Development] JoeDat:
I'm surprised that v2 could be that much different to break compatibility. I would like someone else to try to rule out me just being stupid, which is a very real possibility :)
[Pixel C Android Development] YevOmega:
Any plans to try enabling the disabled A53 cores? Thanks!
[Pixel C Android Development] Magnus579:
Also would like to have encryption added. Thanks for all the work cheep5k8!
[Pixel C Android Development] raedur:
You aren't being stupid :) I'm getting exactly the same thing. Looks like something in preview 2 broke. I even tried flashing the stock boot.img back onto it, wiping and it still wouldn't boot. The only way I could get it to boot again is to flash the factory images back onto it again.
[Pixel C Android Development] a.f.x.:
Now that the new rom is out (ryu-m5c14j-factory-b714e9bd), how do I install it?

I assume I can not perform an OTA install but need flash it via TWRP right?

Flash it like the one in the first post and then do the kernel (xceed-kernel-google-dragon-v6.10-RELEASE-mxc14g) and su again on top?

Or do I need to wait until the new kernel is ready?

thx

afx
[Pixel C Android Development] dkryder:
i installed with fastboot from a pc. not sure if cheepsk8 has done a new boot image for that build.
[Pixel C Android Development] followmsi:
Fastboot flash system.img and vendor.img and reboot.

Wait for the new xceed Kernel. ;)

You still have supersu installed .. on data.

Cheers
[Pixel C Android Development] a.f.x.:
Thanks, sounds like a plan ;)

cheers

afx
[Pixel C Android Development] Freak07:
You may do as is already written above me. Or you can flash the 7.0 preview kernel which was released on top of the updates. I did one week ago and it was stable until now. No reboots or chrashes and the wlan performance is significantly better. at least in daily usage.
[Pixel C Android Development] YevOmega:
[MENTION=4867279]cheep5k8[/MENTION] Is it OK to take the April security update, or will the OTA not work?
[Pixel C Android Development] Avencore:
I tried the Second N-Preview and I'm getting constant 100mbit over wifi instead of 30mbit with stock april update. What a great improvement :D Only problem ist, that on N I'm getting a reboot almost every 5 minutes if the display is off. When the screen is on everything works just great.
[Pixel C Android Development] NYCHitman1:
Thanks for this kernel [MENTION=4867279]cheep5k8[/MENTION]. Just so you know -- I decided to go balls to the wall and manually flashed SU 2.71 in TWRP, which did indeed give me root.

Just fooling around a little while I get a DU build ready for Dragon, which I'm sure everyone will enjoy.

Side note:

is Dragon's kernel source using third_party/chromeos-3.18 or another branch?
[Pixel C Android Development] redukt:
Dirty Unicorns on Pixel C? Great news! :)

Is your build stable enough to use it as dd? If you need some testers - <------ :)
[Pixel C Android Development] NYCHitman1:
It's going to be a while before anything is released. I want to make sure that it runs 100%.
[Pixel C Android Development] redukt:
Well that sounds great :) Keep me in mind as potentially tester. And sorry for OT! :)
[Pixel C Android Development] En Kee:
I tried that once and indeed I had root and everything was fine... Until I tried to flash via adb the new factory image from Google. It was not possible to flash anything in fastboot ("remote: unsupported command")
[Pixel C Android Development] NYCHitman1:
That has nothing to do with the kernel. You were probably using incorrect fastboot commands.
[Pixel C Android Development] En Kee:
You were talking about flashing SU 2.71 via TWRP, that's what I did. After that I couldn't flash anymore via fastboot. My commands were correct. I had to push again su.img from that LINK to have back the possibility to flash.
[Pixel C Android Development] NYCHitman1:
I just used fastboot to try and flash my own kernel, which was successful.
[Pixel C Android Development] redukt:
Man... own kernel... hope for some sharings of your stuff :) And again, sorry for OT ;)
[Pixel C Android Development] YevOmega:
LMK if you need a tester. Happy to help!

---------- Post added at 03:14 PM ---------- Previous post was at 03:13 PM ----------

Have you looked into enabling the A53 cores at all? Also, thanks for your work!

[MENTION=4867279]cheep5k8[/MENTION] sorry for OT!
[Pixel C Android Development] NYCHitman1:
In retrospect, I discovered that our lovely device has a funky fastboot issue in relation to a flag that's set, which prevents you from using fastboot. However, you can fix it by using fwtool.
[Pixel C Android Development] manaka3161:
So, let me ask a question.

Currently can we root the new N ROM(M5C14J)?

Has anyone tried?
[Pixel C Android Development] NYCHitman1:
M5C14J isn't "N"

That's still Marshmallow. However, to answer your question -- yes, it is rootable. I'm currently running a stock build with root.
[Pixel C Android Development] manaka3161:
I'm so sorry...

What I really meant was Developer Preview 2 (NPC91K).

I want to know whether Developer Preview 2 is rootable or not.

I'm already running rooted Developer Preview 1 (NPC56P).

Sorry to confuse you.
[Pixel C Android Development] drewski_1:
The fastboot fix is incorporated into TWRP under Advanced->Fix Fastboot option

---------- Post added at 03:41 PM ---------- Previous post was at 03:38 PM ----------

I haven't seen a successful root method for DP2 yet.

Regardless of root, I've found DP2 to be very unstable on the Pixel with frequent random reboots. Some have reported it's working OK unrooted so YMMV
[Pixel C Android Development] NYCHitman1:
I know it is, but it's good to know how to do it the "more difficult" way if necessary.
[Pixel C Android Development] phhusson:
Mmm, with your own key, or the one by default in Android build system?

I used the one in Android build system, I don't know if it might change something...

Edit: Ok i've checked with futility verify, and everything seems ok :s
[Pixel C Android Development] cheep5k8:
Yes, it is properly signed, or the Pixel wouldn't boot it when flashed.

My kernel is not the issue of the current problems. I even flashed many unsigned kernels before I found out a flashed kernel must be signed and contained within a depthcharge payload, and the Pixel C didn't lock down. I still have no idea what caused this to happen, but clearly it happened after flashing SuperSU (for me, and others).

FYI, I read the depthcharge fastboot code and the code for board smaug: the fastboot_full_cap flag is not set in nvram is the most likely explanation (it must have been reset)

References:

Fastboot checking for capabilities:

https://chromium.googlesource.com/c...hcharge/+/master/src/fastboot/fastboot.c#1441

https://chromium.googlesource.com/c...harge/+/master/src/fastboot/capabilities.c#98

Fastboot Capabilities checking nvram for fastboot_full_cap:

https://chromium.googlesource.com/c...harge/+/master/src/fastboot/capabilities.c#86

"secure" var is set to "yes" if FLASH capability is not set:

https://chromium.googlesource.com/c...thcharge/+/master/src/fastboot/fastboot.c#302

(and yes, before you ask, that IS the code that is running inside the Pixel C... if you don't believe it, check the same source tree for board "smaug")
[Pixel C Android Development] phhusson:
I know it is, I'm the first one to mention it on XDA...

If you're still stuck on the building part, might I suggest to install a debian chroot?
[Pixel C Android Development] cheep5k8:
Stuck on the building part? Of what?

I'm rather looking into accessing the device's NVRAM... I've ported tpm-tools to run on the Pixel C, and they basically work but can not communicate with the TPM properly, I'm looking into that.

EDIT: ChromiumOS uses TrouSerS to connect to the TPM. I've ported that and tpm-tools on top of it but while they run on the device they can't or don't access the TPM module properly, so this is the next step.
[Pixel C Android Development] cheep5k8:
It seems that the tcsd daemon must be running to communicate with the TPM. I didn't really catch that. I have the Pixel C with me, but am at work now, so this needs to be done when I get back home (for everyone waiting for this issue to be fixed).

EDIT: [MENTION=1915408]phhusson[/MENTION] If you meant building the tpm-tools, I'm running Ubuntu on my home laptop anyway but thanks :)
[Pixel C Android Development] phhusson:
No, I really meant to compile the tools in the chroot itself. No cross-compilation, no ndk-thingy, you just have to build it the same way you would compile any program for your own computer

If you get a wider look at how those elements work together, I'd be interested in some description of how those work
[Pixel C Android Development] cheep5k8:
I'm sort of getting the picture, but it's not fully cohesive yet as I am not sure how much of ChromeOS is in the Pixel C (but to be sure, there is a lot). At least everything up until where Android boots is ChromeOS (including booting the Android kernel via depthcharge payload).

Even the Android kernel has some interesting CROS stuff accessible via sysfs (I poked around yesterday but didn't make any notes).

I have actually been planning on making a writeup on the Pixel C once this issue is resolved and I understand the stuff a bit more.
[Pixel C Android Development] cheep5k8:
I've built ectool for the Pixel C and since /dev/cros_ec is available, it does work!

Download ectool: ectool

(Best is if you put it into /vendor/bin, do not put it anywhere in /system!!)

Could someone with a Pixel C with root access that is *not* bricked (i.e. fastboot works) please run it and post the output of:

./ectool --interface=dev --name=cros_ec switches

For me, it outputs:

Current switches: 0x00
Lid switch: CLOSED
Power button: UP
Write protect: ENABLED
Dedicated recovery: DISABLED

So I'm curious whether "Write protect" is also ENABLED for those whose device is not softbricked.

Also the output of:

./ectool --interface=dev --name=cros_ec flashprotect

It will only display info about the flash protection.

For me, it shows:

Flash protect flags: 0x0000000f wp_gpio_asserted ro_at_boot ro_now all_now
Valid flags: 0x0000003f wp_gpio_asserted ro_at_boot ro_now all_now STUCK INCONSISTENT
Writable flags: 0x00000000

Thanks.
[Pixel C Android Development] streilu:
I can't download the file, otherwise I'd check the output for you.

Gesendet von meinem Pixel C mit Tapatalk
[Pixel C Android Development] brando56894:
Fastboot doesn't work for me but I get the same output....
[Pixel C Android Development] cheep5k8:
Yeah, well.. it's a shame there's no easy way to undo the write protection.

I'm at work still, but this evening I should be able to access the TPM, and from there the NVRAM and hopefully set the fastboot_full_cap flag, so fastboot works again.

Once I have that confirmed working I'll post the neccessary tools and instructions on how to undo this, and then a way to install SuperSU without flashing the full ZIP (we basically just need my kernel, which by itself is no problem, it's signed and doesn't trip any security, and then all we need is the su.img copied to /data, not the full SuperSU ZIP).

I'll report back once I've got more information.
[Pixel C Android Development] phhusson:
I understand you prefer SuperSU, and what you do is interesting anyway, but is there any reason specific you don't use my SuperUser?
[Pixel C Android Development] cheep5k8:
No real reason, I was just interested in different things. I wondered if TWRP can work, and it does, and I wondered if we can have systemless SuperSU, and we can (I didn't expect the fastboot lock problem).
[Pixel C Android Development] cheep5k8:
devhost is really not so good... I'll upload it somewhere else when I get home
[Pixel C Android Development] dkryder:
i think that server gets confused as to what file type it is. it was delivered to me as ectool.htm for some reason, might be browser,

but when i renamed to just ectool then it was "file corrupt" then i gave up. maybe if you zip it might help.
[Pixel C Android Development] cheep5k8:
GUYS!! I am able to access the Pixel C's TPM!! Now gimme a moment so I can peek around there.
[Pixel C Android Development] cheep5k8:
OK, so, someone whose fastboot is NOT broken will need (well... it would be nice) to run the tpm tools and give us a dump of their NVRAM. Then we can find out which flag is different, and fix it for our bricked Pixel C's.

Any volunteers? (This is safe as you only perform read operations. You basically just read an area of RAM)
[Pixel C Android Development] DaConcho:
I would be happy to do it as soon as I get off of work. What exactly do I need to do to get it?
[Pixel C Android Development] oRAirwolf:
Does it need to be rooted or have TWRP? Mine is unmodified but I am ready and willing.
[Pixel C Android Development] cheep5k8:
You need to be rooted since /dev/tpm0 is not accessible as normal (shell) user.... but thanks a lot anyway for volunteering!
[Pixel C Android Development] manaka3161:
Thanks.

I'm satisfied with current DP1, so I keep using this.
[Pixel C Android Development] Legendaria:
How is the battery life on this kernel compared to stock?
[Pixel C Android Development] cheep5k8:
Hey guys, it's been a while :)

Great to see other devs coming to this device, and great to see an actual full custom ROM ported (thanks goes to [MENTION=2489052]NYCHitman1[/MENTION]).

I've been way busy with a lot of stuff, of course mainly work but also Android sideprojects. I've developed a pretty awesome unzipping app for Android.

You might think how can an unzipping app be "cool"... well let's just say that I think that most ZIP apps for Android suck and that a good app should assist you a little during the process and not just show you a screen that looks like WinZip on Windows 95 with a zillion options and then leave it to you to handle it. I plan on putting it on the Play Store somewhen-ish next week.

But, to the Pixel C. I think I'll be focusing on Android N from here on out, as the N Preview 3 is really pretty good as far as a beta goes and sooner than we realize we'll be leaving Marshmallow-land on the Pixel C for good anyway.

So the next builds of xceed will be, also because of my rather limited time (of which I'd dearly like to have more), for Android N only.

First I need to get this new app into the playstore, then the week after I'll dedicate my development to the xceed kernel and the Pixel C again.

I hope you're all having a great time!

Over & Out (for now)
[Pixel C Android Development] cheep5k8:
N Preview 3 v8.00 alpha

OK guys, so in a frenzy I did it, and whipped up v8.00 alpha, which is built from NPD35K kernel sources. Works perfectly for me so far.

It includes:

* The nvidia bcmdhd WiFi driver which fixes many WiFi issues since Google Still. Has. Not. Fixed. The Wifi... :eek:

* ROW, BFQ and FIOPS I/O schedulers

* Enabled all TCP algorithms

* Various kernel config improvements

This is just the first alpha, more stuff will be included in the final v8.00 (I'm thinking CIFS and support for USB 4G modems).

Have fun testing it out!

PS: Had random reboots on the stock NPD35K kernel; the reason is their broken tegra210 cpufreq driver which is also fixed in xceed: no more spontaneous reboots on N Preview 3.
[Pixel C Android Development] NYCHitman1:
Feel free to take a peek at my kernel source -- I was able to successfully port over some things which are behaving quite nicely thus far.
[Pixel C Android Development] wardy277:
Am I doing somwthing wrong or is the alpha 8.0 version link pointing to the 6.10 version? Looking forward to testing this out
[Pixel C Android Development] cheep5k8:
Somehow I messed up the links; just fixed it. :)
[Pixel C Android Development] Boal:
Does bandwidth monitoring work again, e.g. with an app like System Monitor (Lite)?
[Pixel C Android Development] dkryder:
cheep5k8,

i've read the latest supersu only works with stock kernel at install but do you have an idea about after install of supersu if i flash stock then your kernel, if your kernel would work on currently rooted install ? or is getting phhusson's su and put it in /data like prior installs is the proper way to go now.? thanks
[Pixel C Android Development] BewareAlbatross:
Wandered in, thought, well, I'll see what the nice dev is planning with the new N beta... And there ya go. You. You're good. :good:

As usual the only reason I don't entirely regret buying this Pixel C is because of your kernel. :D
[Pixel C Android Development] drewski_1:
I was rooted via SuperSU 2.74 and installed XCeeD v8 and have retained root so it looks like XCeeD had the needed SE policy changes :good:

SuperSU install might barf during the kernel modification step, but I believe you should still be rooted.
[Pixel C Android Development] dkryder:
ok, thanks drewski_1 is it correct that if i want to go from supersu modified to Xceed that i need to flash stock kernel then Xceed immediately after? i read on elementalx google + page that any changes in which modified kernel should have the stock flashed first then the new modified. is that proper way?
[Pixel C Android Development] drewski_1:
You can just flash this over stock modified.

E-x installer is sort of a "hybrid" using parts of the currently installed boot.img. this is why Flar says to go to stock first.

This kernel is the complete Image so doesn't have the same issue.
[Pixel C Android Development] followmsi:
If you have latest N bootloader installed .. are you able to run Android M too ?

Or is it required to downgrade bootloader if you go back to M ?

Just in case you want to go back to M ;)

Any experiences ?

Thanks
[Pixel C Android Development] brando56894:
I started fresh with the N image and flashed this kernel, booted into Android, downloaded the SuperSU beta and flashed it. It did complain about created the InitRD but when I booted back into Android SuperSU was there and everything worked perfectly.
[Pixel C Android Development] cheep5k8:
Hey guys,

I've uploaded another build for N Preview, 8.00-alpha2. It fixes another issue with the cpufreq driver, and I've enabled the full CIFS stack. Going to test that myself now with some app that I can find, I hope, maybe.. ;)

EDIT: Yep, CIFS is working! Albeit a bit slow. But isn't CIFS always slow? Anyhow :)
[Pixel C Android Development] hagbardceline23:
Thanks, this is great news, finally we get CIFS on the pixel :)
[Pixel C Android Development] r_nation:
Will 8.0alpha 2 work on mxc89f build?
[Pixel C Android Development] PandaVoyageur:
Bootloops with v8.00

I wanted to try your NPD35K kernel, but my pixel C only gets to the Google logo for a short while before rebooting again and again. And adb does not have time to see the device, so no logcat :/

I tried installing it by rebooting to fastboot and flashing it with "fastboot flash boot xceed-v8.00alpha2-NPD35K.img". On another try, I rebooted to recovery to try to flash supersu (it complained "normally" on the image being already modified), but same result.

I had the tablet running unencrypted and rooted with oRAirwolf's guide, then updated to current Marshmallow releases, then current NPD35K (bootloader, vendor.img and system.img). Android N works fine with chromeos-3.18-kernel_Android-N_v160519_followmsi + supersu flashed over it.

Current setup is working, but I wanted to test your wifi fixes (N preview kernel indeed has bad performance compared to M). File sha1sum is correct too.
[Pixel C Android Development] followmsi:
Just a comment .. my M kernel and the N kernel are identical !

The only difference is the ramdisk, taken from stock npd35k for the N version.

Because of the stock ramdisk you still need to root the "kernel" .. eg. the ramdisk included.

I "feel" not much performance differences compared M to N.

N is working quite good for a "preview" ..

Cheers
[Pixel C Android Development] cheep5k8:
Well, the way I tested it is you can merrily go flashing between stock and xceed, and then just flash SuperSU 2.72+ after each time, nothing breaks. Chainfire is the man.
[Pixel C Android Development] dkryder:
thank you for confirming that it works. i read a report awhile back the supersu did not flash on non-stock kernels but that might have been an earlier release of supersu. and i agree, Chainfire has made pixel c easier to control. remarkable talent.
[Pixel C Android Development] cheep5k8:
v8.00

I've released v8.00!

Features:

- improved nvidia bcmdhd driver (less WiFi issues than Google stock; part is probably hardware)

- FIOPS, ROW and BFQ schedulers

- BioShock CPU scheduler (Thanks to [MENTION=2489052]NYCHitman1[/MENTION] + DragonBlood kernel!)

- various arm64 optimizations (ditto)

- enabled CIFS

- enabled drivers for various USB 4G dongles (hopefully this works for someone)

- cpufreq fixes (no more spontaneous reboots)

- enabled all TCP algorithms

- bugfixes over Google stock

- and more
[Pixel C Android Development] brando56894:
This was happening to me also, I think what finally fixed it was booting the kernel via fast boot after it was flashed: fastboot boot xceed.img