yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Avalun:
Actually I tried to switch to supersu too, my reason on that case is, if I start a terminal app and type su -i the terminal app just hangs.

I googled for that issue and the results told me I should switch to supersu.

Titanium Backup told me, too there might be issues with that app.

If i can resolve the issue with su acces in the terminal, and I can use Titanium Backup I would stay too.

Currently the ectool just told me a communication error.
[Pixel C Android Development] cheep5k8:
Did you run it as root? If so, and it still says communication error, that would be a bit curious.
[Pixel C Android Development] cheep5k8:
OK. I can give you instructions how to root it with SuperSU using my boot image *without* tripping the security measure (just don't ever flash the SuperSU ZIP!!). I had a bit of time to think what was actually missing from my boot image (it's essentially just the su.img which needs to be copied to /data, and Superuser.apk of course).

If you want to do it just send me a message or write another post, and thank you.

EDIT: For everyone, don't flash anything in TWRP that modifies the kernel. The kernel image is not a standard Android kernel image, it's a ChromiumOS depthcharge payload that CONTAINS an Android kernel. No standard Android tool will be able to handle this properly so DON'T!

In fact, I will probably modify TWRP in such a way that writing to the kernel is simply not possible/disabled. That should make this stuff much safer.
[Pixel C Android Development] Avalun:
I can't because if i do a su in the terminal it just hangs.
[Pixel C Android Development] brando56894:
Which app are you using? Mine would hang with one terminal app and not the other. Also you could give it a try by connecting it to your pc and running adb shell then su.
[Pixel C Android Development] dkryder:
the thing i do not get about superuser [phhusson] is su is in /sbin. that seems to be a non generic/standard location based on the other super user su binaries as well as many apps are hardcoded to expect su in one or two locations only and fail to recognize the device as "rooted" as a result. a workaround is to move su but that is very unadvised to do. the thing about superuser i do like is when it works it does very well. but, as it is now supersu is mostly what the apps are looking for or set up to expect su a certain way. this goes for root verify apps as well as apps that need root to run properly. so it stands to reason that one would probably have fewer issues with supersu. of course that all changes when it comes to pixel c because there has been no published development work specifically for the pixel c to date from chainfire. now, he did post to the issue by serial number thread so it seems he has access to a pixel c but i also read a few tweets of his which expressed frustration with the boot sequence which included the expression , "next device" which i take to mean he might be moving along, away from pixel c direct development. i hope i'm wrong, i really do cause this device needs all the help it can

get. and so far it looks like very little is coming from google. i hope this payload bull was just a hack late in the game after they accepted defeat on getting chrome os or chromium os to run but did not have time to put a traditional android os on it but it needed to ship.
[Pixel C Android Development] DaConcho:
I formatted data again, reflashed the boot image, reinstalled everything. Only thing I changed was I installed busybox to su/xbin instead of su/bin, and it worked!

Here is my output for the ./tpm_version:

WARNING: linker: ./tpm_version: unused DT entry: type 0xf arg 0x463
WARNING: linker: /vendor/lib64/libtspi.so.1: unused DT entry: type 0xf arg 0x138c3
TPM 1.2 Version Info:
Chip Version: 1.2.133.32
Spec Level: 2
Errata Revision: 3
TPM Vendor ID: IFX
Vendor Specific data: 85200050 0074706d 3439ffff ff
TPM Version: 01010000
Manufacturer Info: 49465800

Ready to go on the next part.
[Pixel C Android Development] phhusson:
Sounds like he hasn't got the signing part yet.

As for su "standard" location, SuperSU now puts it in /data/su/su. There is a centuries old(erm almost.) standard variable called PATH to know where to find commands. Both my SU and SuperSU overrides it to include /sbin for SU and /data/su for SuperSU.

I also handle the case where a ROM has /system/xbin/su, I mount --bind /sbin/su to /system/xbin/su, so that /system/xbin/su does work.

I had a release (r158 I'd say) where su was totally borked, possibly he got this one :/

Though your case is more interesting. Which terminal apps hangs?
[Pixel C Android Development] superchilpil:
Terminal Emulator by Jack Palevich is the one that hangs
[Pixel C Android Development] phhusson:
Thanks, works for me :/

Can you flash latest revision?
[Pixel C Android Development] Avalun:
I tried that one thich is included with Rom toolbox, then I tried that one from Jack Palevich and Termux. All the same.

The next thing I don't have a TWRP, it seems that I currently have no recovery at all.

adb says the device is offline
[Pixel C Android Development] superchilpil:
[ROOT] [UNTETHERED] [NO FORCED ENCRYPTION] Modified Flashable Stock Kernel (M...

Just tried the eng and now it reboots straight into recovery.

Tried to go back and download the the nocrypt version and I'm getting a 404 error for your site...
[Pixel C Android Development] phhusson:
Then please upgrade to latest boot-su-xxx (r160 ATM)

---------- Post added at 10:55 AM ---------- Previous post was at 10:50 AM ----------

Erf sorry, I meant latest release on http://superuser.phh.me/nexus/ryu/

ATM that would be http://superuser.phh.me/nexus/ryu/MXB48K/boot-ryu-MXB48K-su-eng-r160.img or http://superuser.phh.me/nexus/ryu/MXB48K/boot-ryu-MXB48K-su-nocrypt-r160.img
[Pixel C Android Development] cheep5k8:
It's a network file system. It's what you use when you browse Windows shares.
[Pixel C Android Development] cheep5k8:
9.10

Hey,

I've uploaded 9.10. It contains no experimental changes to the kernel base config, so everyone (including hopefully me) should be safe from spontaneous reboots.

It has CIFS fully enabled, and also has a few bugfixes for the Android subsystem back-ported from Linux 4.x kernel (specifically for the Android binder.)
[Pixel C Android Development] cheep5k8:
Does anyone else have massive wakelocks with the WIFI? I'm currently debugging the s**t out of my bcmdhd driver to eliminate the problem... let's see where I end up ;)
[Pixel C Android Development] YevOmega:
Thanks a lot for all that you do. The fact that you explained your absence to us was so sweet. Great to have you back! I'm down to start testing stuff after my exams on Tuesday! Will report back then!
[Pixel C Android Development] cheep5k8:
Thank you :)
[Pixel C Android Development] cheep5k8:
9.21

Hey everyone,

I've uploaded 9.21. Same as 9.10, but I've ported new code for the WiFi driver that makes it cooperate better with Android; it doesn't neccessarily mean that transfers will be faster etc., but it should work better overall. Also I tried to get hold of all the wakelocks, and ported some code from franco's OnePlus 2 kernel to get them into control (courtesy&thanks to [MENTION=3292224]franciscofranco[/MENTION]).
[Pixel C Android Development] cheep5k8:
9.22

Ok so it turns out I had cherry-picked a commit and forgot to make a minor change: if you have reboots (again... sorry..) in 9.21, just use 9.22.

Also, someone aeons ago asked for network traffic monitor support with the new Wifi driver; that works now that I've made the change in 9.21.
[Pixel C Android Development] flopponator:
[MENTION=4867279]cheep5k8[/MENTION] is it possible to disable forced encryption with your kernel? Sometimes I forget to flash SuperSU and end up with an encrypted tablet.
[Pixel C Android Development] cheep5k8:
Sure, I can arrange that. Other kernels often have multiple versions regarding verity and force encrypt anyway.

I'll set it up starting with the next version. Not really that complicated anyway ?
[Pixel C Android Development] followmsi:
Welcome back :)

You may think about lazyflasher for your kernel.

No need to take care about the ramdsik at all .. just replace the kernel binary only. (image.fit)

Have a look here ..

https://github.com/jcadduono/lazyflasher

https://xdaforums.com/pixel-c/orig-development/lazyflasher-make-install-custom-kernels-t3537487

Thanks as well for the fresh sources ..

https://github.com/md5555/android_kernel_google_dragon/tree/android_7.1.2_b

Tried to compile your kernel ... build errors :(

Pls upload your latest changes to GitHub.

It's much better to "see" what you are talking about ..

Thanks !
[Pixel C Android Development] cheep5k8:
9.30

Ok this is a big one:

I've fully managed to get the WiFi wakeups under control. My Pixel C now spends about 75-80% correction: about 90% in deep sleep, while still retaining connectivity, i.e. you will still receive notifications about new emails, etc. :highfive:

Download it as always from androidfilehost (see first post).

I've also made a stab at disabling forced encryption, but this seems more complicated than I thought, so in this build, forced encryption is still active (but dm-verity is disabled as already with 9.00).
[Pixel C Android Development] cheep5k8:
OK, so, I've uploaded another build, 9.31, since I noticed that constant high throughput didn't work with the expected performance (e.g. running Speedtest); thankfully I was able to remedy this rather quickly, so there's 9.31.

Everything else is unchanged from 9.30. You should now also be able to enjoy high data rates again.
[Pixel C Android Development] r_nation:
Is this only flashable on stock 7.1.2? I went ahead and attempted to flash on purenexus 7.1.1 but won't boot and left me encrypted:/ restored backup boot and reflashed su but still encryped:/ I cannot get a any custom boot.img to boot which includes dragon variant of nethunter kernel any ideas?
[Pixel C Android Development] cam30era:
[MENTION=7095878]r_nation[/MENTION],

Once you are encrypted, after flashing SuperSU you need to do a factory reset, or format user data (from fastboot), to get unencrypted. And yes, this will wipe your device.
[Pixel C Android Development] r_nation:
I appreciate it, now just gotta get it to boot.
[Pixel C Android Development] cheep5k8:
I really can't say anything about other ROMs than AOSP and stock. I'm simply using AOSP to build the kernel image (kernel+ramdisk). If it doesn't boot, well, it could really be a number of reasons why that happens :confused:
[Pixel C Android Development] r_nation:
Ok i flashed stock 7.1.2 and it boots, purenexus rom is about to update and I'll give it another shot then..thank you
[Pixel C Android Development] je55ter:
Thanks, however this appears to be the same build I already have installed. I was hoping there was a more stable one available, as this one freezes/crashes a lot.
[Pixel C Android Development] cheep5k8:
Sorry to hear that, however there isn't going to be any new Marshmallow builds as I don't find it feasible to backport all the fixes to the Marshmallow kernel, etc.

I understand that some people don't want to upgrade to Nougat, but it would be way too much work to make a new M build of the kernel now :(
[Pixel C Android Development] skawtnyc:
Unfortunately, right after I installed this version, when I go into Settings -> Apps -> (any app) the Settings app crashes. Guess I'm going back to stock for now. :(
[Pixel C Android Development] cheep5k8:
Strange, doesn't happen for me. Good call going to stock either way, but I'll have a hard time finding this if I can't reproduce it :cowboy: Are you on stock or some custom ROM?
[Pixel C Android Development] skawtnyc:
Stock, rooted, previously running Xceed 9.2.2.
[Pixel C Android Development] cheep5k8:
Frankly this doesn't sound like something that would be caused by the kernel, especially since nothing *major* from the perspective of Android changed between 9.22 and 9.30; all changes between 9.22 and 9.30/.31 are contained within the kernel and change nothing for Android. Really strange, that is.

Should I be able to reproduce this issue then I'll take a look.
[Pixel C Android Development] Alxoom33:
Your kernel installs and is working flawlessly for me. I'm on the latest stock 7.1.2 Android rooted with Xceed 9.31.
[Pixel C Android Development] 12paq:
+1 more for a non forced encryption version.

I found this out the hard way and lost all my data. My fault for not checking. I had full backups on my PC so it was a fun fix via ADB. :)

Way happy we have an up to date custom kernel, thanks!
[Pixel C Android Development] skawtnyc:
Going back to the stock kernel didn't fix it, neither did a non-wipe install of the OS. I'm going to do a Titanium Backup, wipe, restore. Something must have gotten corrupted recently, and it was coincidence that it happened around the same time as installing the new kernel.

I'll keep you updated.
[Pixel C Android Development] cheep5k8:
9.32 Security+Maintenance Release

I've uploaded 9.32. It is purely a security+maintenance release and contains security patches for bcmdhd ported from the official chromeos kernel tree, and various bugfixes for Tegra.
[Pixel C Android Development] skawtnyc:
Turns out it was definitely a data corruption issue. Factory wioe and a restore of user apps and data resolved the issue and the kernel works properly now.
[Pixel C Android Development] cheep5k8:
9.34

* Adjusted bcmdhd roaming configuration and patched up some roaming-related code; this prevents the STA (the WiFi client in the Pixel C) from sometimes disconnecting when the tablet is not being used
[Pixel C Android Development] cheep5k8:
I reeeeaaaalllly like this statistic:

Two things:

1) The tablet is not really charging; but sometimes it shows as charging in this overview. Anyone else has that? It has been like that since Marshmallow, IIRC

2) Obviously the Tablet has been off (I mean screen off) for the past 5 hours but 9 days? That's incredible. You could say I've (takes off glasses) exceeded in bringing good battery life :cool:

Now this is worthy of a tablet with a 9000mAh battery. Actually I think it could be still better.
[Pixel C Android Development] Bless1:
So just to make sure I can flash this to the boot partition in TWRP. And do I need to flash SuperSU after?
[Pixel C Android Development] cheep5k8:
1) Yes

And

2) Yes, if you want root access
[Pixel C Android Development] Alxoom33:
Wow! You have been very busy!
[Pixel C Android Development] cheep5k8:
Yep! And it paid off massively! Try it, the standby battery life is da bomb. :highfive:
[Pixel C Android Development] Alxoom33:
I am up to 9.34 working great, but have not tested the battery life. I am relying on you and others for that. Your results in the OP look terrific.

Also, the performance is excellent! Which is what I mostly care about! Thanks for all of your hard work. It's nice to tweak my Pixel C a little, every once in a while.
[Pixel C Android Development] cheep5k8:
Just for fun and to play around, I've created an overlay apk (goes into /vendor/overlay just like other overlays) that enables some options in Android.

For one, you can now enable gestures like lift tablet to wake, etc., but none of them work and most likely never will.

However, you can now enable Ambient Display, which works! Just like on other devices. Great.

Also this APK will enable proper DozeService on the device which means the Pixel C gets actual Doze Mode. Not sure how useful that is, though. Like I said, just something to play around ;)

EDIT: Ok, about Doze: it seems that when it's enabled, the average time spent in deep sleep goes a little bit down, BUT it is very stable. For me it's basically fixed at 74% for an hour or so. This seems very good. You might get slightly less overall battery life in standby, but it will be very consistent because Doze controls all that stuff that might run in the background.
[Pixel C Android Development] JerrellWong:
Hi guys , I'm on purenexus latest build - 7.1.2 , can someone guide me on how I can flash the img file ? Do I just boot into twrp and flash the image to boot ? I'm already rooted with SuperSU that I flashed after my rom
[Pixel C Android Development] flopponator:
Just go into TWRP, select the flash image option and flash it. but you need to flash supersu again after flashing the kernel to keep root access

edit: please let me know if it works since i love purenexus
[Pixel C Android Development] JerrellWong:
Yo ,I'm in a boot loop right now , could you guide me as to how to return to recovery because Everytime I boot there will be that 30 second wait thing and I don't know when I should be holding power up
[Pixel C Android Development] flopponator:
keep pressing and holding power and volume down until you're in the fastboot menu
[Pixel C Android Development] cheep5k8:
Y'all mfkers need to listen up!

OK so many people are having bootlops, doesn't boot, shows a dead Android with a orange triangle.

Since your systems are already broken I'll just assume that wiping your data won't be a big issue; fingers crossed.

We can't really take every single case apart, and to offer a single simple solution, please do this:

* Download the latest Pixel C factory image: https://dl.google.com/dl/android/aosp/ryu-n2g47d-factory-191d8ea6.zip

* Flash all of it, not just some images (use flash-all.sh/.bat) (You boot into fastboot/bootloader and then run flash-all.sh/.bat)

* Start the device up once so everything is configured and settled

* Then boot into the bootloader again and flash xceed

Because I think that everything else in between will be insufficient to properly make your Pixel C's work...

Cheers ;)
[Pixel C Android Development] JerrellWong:
So even if I wiped everything and flashed just the rom again, it won't boot ?
[Pixel C Android Development] cheep5k8:
OK, first of all, you really need to be more specific than that. I'm 100% sure that if you flashed the entire factory image and assuming your Pixel doesn't have a hardware fault, that it will boot.
[Pixel C Android Development] flopponator:
purenexus isn't compatible with this kernel. you have to use stock from google
[Pixel C Android Development] JerrellWong:
Yep , so if I were to , right now , wipe everything and flash just pure Nexus (no xceed kernel ) , would my pixel c still boot into purenexus normally ?
[Pixel C Android Development] flopponator:
yes it would. but you will not be able to experience this great kernel
[Pixel C Android Development] JerrellWong:
Lel , I want to but can't go back to stock haha
[Pixel C Android Development] cheep5k8:
I can look into making a PureNexus version. If it's not overly complicated I can make one.
[Pixel C Android Development] JerrellWong:
Awesome :)
[Pixel C Android Development] flopponator:
damn that's cool. thank you so much!
[Pixel C Android Development] tim.malone:
Thanks for the new version. Battery life is greatly improved. I left my Pixel C sitting around for about 9 hours yesterday, came back, and it was still at 100%. I used it pretty heavily for 2.5 hours and still had around 80% of the battery remaining. Wifi seems strong as well.
[Pixel C Android Development] cheep5k8:
Well that is awesome!! Thanks for the report, too.
[Pixel C Android Development] cheep5k8:
9.35 AOSP + PureNexus

OK guys,

Since you've all been very polite and well-behaved :cool: here's 9.35 for AOSP + PureNexus!

I've changed the layout on AndroidFileHost a bit.. There's now a folder "xceed-aosp-stock", which contains the kernel images for AOSP and stock ONLY. The folder "xceed-purenexus" contains images only for PureNexus. Should be clear.

I haven't actually tested the boot image on PureNexus, but building it was completely straightfoward so that I don't expect any issues with it actually working in the first place, but I'd be interested to know if battery life improvements, WiFi, etc. work just as well as on AOSP/stock. If someone could report back after installing it, that'd be great.

Cheers.
[Pixel C Android Development] 12paq:
A no force encrypted pure nexus version would be a dream. However I did read your post about non force encrypt kernel not being as simple as you thought, so I understand if it is asking too much.

Thanks!
[Pixel C Android Development] cheep5k8:
It just means It'll take more time, not that I'm not doing it. I first need to understand in detail how encryption is set up in Nougat; to my shame I realized that I'm not up to date in that regard. Just changing an option in fstab did not work, so that.
[Pixel C Android Development] cheep5k8:
Haha no wait.... :eek: I'm just an idiot. I removed forced encryption, though my tablet was already encrypted, but I didn't format /data again, so of course it wouldn't boot.

I'm going to integrate it starting with 9.36.
[Pixel C Android Development] 12paq:
Cool!

I thought is was just an fstab edit, but I had read your indepth posts about how the Pixel C is quite different as far as boot and chrome etc. You have really got that figured out. Thanks for those posts, very interesting.

Note: I will never ask for DTW! Haha.
[Pixel C Android Development] r_nation:
Thank you so much cheep5k8 for the purenexus variant of xceed!! I've missed it so much, i'll report back on battery life, etc.. omg this is awesome
[Pixel C Android Development] cheep5k8:
:D
[Pixel C Android Development] cheep5k8:
9.36 AOSP+PureNexus w/ Linaro6

Hey,

I've uploaded 9.36 for both AOSP and PureNexus. There are no changes to the kernel itself, but in addition to verity, forced encryption is now disabled as well. Also, I've compiled both kernels with Linaro gcc 6.x.

As usual in the AFH download area (see link in first post)

Cheers
[Pixel C Android Development] cheep5k8:
I'm rebasing xceed right now on the new released 3.18.49 kernel.. seriously, people just don't get paid enough to do git rebase. It's the most excruciating pain in the ass you can have when doing software development :eek:

Anyway :angel:
[Pixel C Android Development] 12paq:
Thank you very much!
[Pixel C Android Development] Alxoom33:
Tried 9.36 ASOP Linero on Stock 7.1.2, bootlooping.
[Pixel C Android Development] cheep5k8:
Hmm.. that's odd. I always test the builds before uploading (at least the AOSP ones for the moment). Didn't happen for me or I wouldn't have uploaded it! I swear!!!oneeleven :victory:

No but really, it worked for me. I'm here already on 9.38 which will be the next build, but I'll go back to 9.36. If I can make it bootloop I can try to find the issue, but otherwise it's really always very speculative :(
[Pixel C Android Development] Alxoom33:
I flashed 9.36 Linero and then 2.79 SR4 as always. Wiped caches and reebooted.
[Pixel C Android Development] cheep5k8:
Maybe it's the SR4? I didn't even know there's an SR4, I always downloaded the SR3 in the past few days. When I tested 9.36, I flashed 9.36 and either didn't flash SR3 at all, or I did, but not SR4. Just off my head this sounds like the most likely candidate for the problem to me right now. :rolleyes:

EDIT: OK, I've checked: there's a 2.78 SR4, and a 2.79 SR3. Are you sure you've used 2.79?
[Pixel C Android Development] Alxoom33:
I was able to recover by flashing the boot portion of my Nandroid.
[Pixel C Android Development] drewski_1:
i had similar . . .

9.36 flashed. no SuperSU flashed. hung on boot animation for 40 minutes.

re-flashing 9.32 fixed things.

i am encrypted from flashing 9.32 (didn't flash SuperSU and before you removed force encrypt). not sure if this is the issue and/or if [MENTION=4100646]Alxoom33[/MENTION] is also encrypted or not encrypted.
[Pixel C Android Development] cheep5k8:
Ok, now I get it. You guys are right.

In 9.36 I've removed the forced encryption, but forgot to add "encryptable" instead. Which means that if are already encrypted and upgrade to 9.36, it won't boot. Alright. Check.

I'm gonna release 9.38 in a couple of minutes then, with this issue fixed. Thanks for the patience with finding the issue :)
[Pixel C Android Development] cheep5k8:
9.38 (AOSP+PureNexus, Linaro6)

9.38 is up. Sorry for the encryption fauxpas with 9.36. It should be (is...) fixed now.

Other than that I've rebased on the very recently released 3.18.50 Linux kernel, so this build contains all the changes from that. Additionally I've re-enabled the different TCP algorithms again.