yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] r_nation:
Thanks everyone for your time and development. Ill be getting mine Monday(assuming 6.0.1) gonna attempt straight outta box. Have a few questions, on initial setup after entering gmail & password do you skip the set password? Because after unlocking bootloader ill be back to this point. So flash twrp, then flash vendor.img, then swipe bootloader fix,from twrp flash stock or rc3, then copy su.img, how do you copy su.img to data from twrp? Then apk..sorry for all the questions
[Pixel C Android Development] cheep5k8:
Hey. Unfortunately, you've got it essentially right, but all a bit mixed up. I'll try to answer the questions:

– Yes, if you plan to do additional stuff then yes, I would skip setting up the tablet completely, skip over GMail, the password, etc. (actually you shouldn't set any kind of security in that case)

- After unlocking the bootloader the first thing you should do is to install (flash) TWRP to the recovery partition

- You don't really need to flash any vendor image individually, unless you want to manually update to MXB48T

- RC3 (and all other versions of it) are just a kernel, so "RC3 or stock" doesn't really make much sense unless you mean the stock kernel, but your Pixel C will be already running the stock kernel, so there's not much point. But yes, of course you can flash the RC3 kernel, which is the next thing I'd do after flashing TWRP, but you do that from fastboot, not from TWRP

- [MENTION=2666750]oRAirwolf[/MENTION] made an excellent guide for all the steps involved: http://xdaforums.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
[Pixel C Android Development] r_nation:
Thanks for the reply, by stock I actually meant the unencrypted kernel. I've always rooted and flashed my devices but not having much luck since lollipop 5.1 just am unclear about the build numbers and compatibility, and copying su to data while in twrp.
[Pixel C Android Development] r_nation:
Thank you so much, you are the man that helped me out alot..hows battery life on RC3?
[Pixel C Android Development] cheep5k8:
At least not worse than on stock; should be potentially a bit better because of changes I merged that eliminate some wakelocks or at least their frequency.
[Pixel C Android Development] followmsi:
Bad news! While surfing on latest chrome version I got an unexpected reboot on RC3, the first one.

---------- Post added at 08:43 PM ---------- Previous post was at 08:31 PM ----------

For RC3 you have used another compiler, maybe related ?
[Pixel C Android Development] Boal:
Hmmmm... my camera is no longer working and will freeze the entire device. I'm not sure which change has caused this, manually flashing MXB48T's system.img/vendor.img or RC3. Anyone else experiencing something similar?
[Pixel C Android Development] #Baptiste:
Yes I have the same problem

EDIT: "Unable to communicate with the camera" / "Impossible d'établir une connexion avec la caméra"

EDIT 2: I just have a deadlock
[Pixel C Android Development] followmsi:
Confirmed, me too ! Will go back to RC1 and test the camera again.
[Pixel C Android Development] beardymcgee:
I'm on T and rc1 same camera issue, some times freezes tablet completely when camera app open.
[Pixel C Android Development] followmsi:
Yep, same experience on RC1.

Hmmmm ... Has RC4 to be build on T kernel sources ?
[Pixel C Android Development] cheep5k8:
Unfortunately Google hasn't tagged T yet, so it's not clearly possible to build a kernel from T stock.

BTW I've also got the camera issue, I think it's clear that my kernel base somehow breaks the camera, I'm going to investigate it.
[Pixel C Android Development] followmsi:
Thanks for the update and your hard work !
[Pixel C Android Development] cheep5k8:
Hey all,

I've uploaded v1-RC4.

It fixes the camera, and reverts back to Google's gcc 4.9.x compiler instead of Linaro (hopefully this fixes the single reboot instance that [MENTION=5480152]followmsi[/MENTION] had). We need to keep an eye out on that, it might very well be that Linaro's 5.x compiler somehow breaks something, so for now we're staying with Google's 4.9.

Everything else is unchanged from RC3, the TCP algorithms are still available.
[Pixel C Android Development] followmsi:
Yes! Camera is back to life. Perfect!

Will report back on reboots .. Hopefully not ;)

Thanks for the super fast RC4 fix release.
[Pixel C Android Development] beardymcgee:
RC4 all fixed and no issues so far, also thanks [MENTION=4867279]cheep5k8[/MENTION] for the tcp algorithms, appreciate the effort putting them in
[Pixel C Android Development] followmsi:
RC4 looks good, no reboots so far. ?
[Pixel C Android Development] cheep5k8:
Sadly, I am having reboots on RC4 (I have an RC5 internally but it's equally bad).

The most stable for me is RC3, but of course the camera is broken in RC3. I will attempt to start with RC3 again, fix the camera with as few changes as possible, and then test the stability again.
[Pixel C Android Development] followmsi:
Me too ?

One reboot, again while surfing with chrome browser.

Looking forward for public RC6 ?
[Pixel C Android Development] r_nation:
My C will be here today suprsingly, will follow the link. Will I need or should swipe the the fastboot fix from twrp at any point through process? thanks in advance
[Pixel C Android Development] cheep5k8:
You only need to do that in case fastboot stops working properly. Make sure the first thing you do after unlocking the bootloader is to flash TWRP, it can potentially save you from being locked out of the device.
[Pixel C Android Development] cheep5k8:
[MENTION=5480152]followmsi[/MENTION], [MENTION=1610074]beardymcgee[/MENTION] (and all others)

I won't be able to update the kernel for a couple of days (need to attend to work and family a bit); until then I recommend for those who don't really need the camera to flash RC3 (link below). It has been to most stable for me so far with 0 random reboots across a couple of days (including last night and all day today).

When I get a bit more time for the kernel next week again I'll dissect what changes exactly cause the reboots, and what makes the camera stop working and can then make a new RC build with both issues fixed.

(BTW if you have questions, I'll probably be able to respond, I just won't have the time to work on the build until then)

RC3: https://drive.google.com/file/d/0B9fx05P4rFbiaU9VQ0dTZW4xMDQ/view?usp=sharing
[Pixel C Android Development] followmsi:
Thanks for the update!

Take care ..
[Pixel C Android Development] bill3508:
I'm still on rc1 without a single reboot since you released it.
[Pixel C Android Development] beardymcgee:
Enjoy the break, Take your time [MENTION=4867279]cheep5k8[/MENTION], you're doing do great work
[Pixel C Android Development] r_nation:
Thank you sir..have a good night
[Pixel C Android Development] r_nation:
And I'm rooted:) went really really smooth, thanks for everyone's hard work and instructions! Was surprised to see Google February security patch download after process, is it ok to install this??
[Pixel C Android Development] acrickie:
I'm no expert - but I will say no as I suspect it will overwrite this kernel and the su.img.

I upgraded just by using fastboot to flash the vendor and system img files and root remained.

Of course I may be completely wrong - but I know that I did not lose root when doing the above.
[Pixel C Android Development] r_nation:
*appreciated* it was late by the time I rooted and was exhausted. I have a vendor image saved its 118.48 MB hopefully the right one..may I ask where to find system image..it would be really appreciated, thank you
[Pixel C Android Development] followmsi:
Please use the official images ..

https://dl.google.com/dl/android/aosp/ryu-mxb48t-factory-43820b34.tgz
[Pixel C Android Development] r_nation:
Ok I'm assuming MXB48K and MXB48T..any recommendations on which one, I know T is the latest and lastly does it matter if you flash vendor first or after system?

---------- Post added at 09:34 AM ---------- Previous post was at 09:21 AM ----------

You guys are amazing. I've been out of the loop I've been content with my one m8 rooted and rommed and s-off then bought a venue 10 7000(with no development) and was introduced to the world of forced encryption and dm-verity..turned my world upside down
[Pixel C Android Development] followmsi:
As you have custom recovery (TWRP) installed OTA updates will not work anyway.

You have to upgrade manually.

Flashing vendor, system, cache and bootloader will not hurt.

If you flash recovery you loose TWRP.

If you flash boot.img you overwrite the xceed kernel.

If you flash userdata you loose all your personal data and the su.img.

Hope that helps a bit ...

---------- Post added at 04:41 PM ---------- Previous post was at 04:35 PM ----------

Yes, go for T to include february release.

The order of flashing is not relevant in this case.

But start with vendor and then system.

fastboot flash vendor vendor.img

fastboot flash system system.img

Cheers
[Pixel C Android Development] r_nation:
I literally can't thank all of you enough. Bless you all
[Pixel C Android Development] r_nation:
I know this has been brought up I vaguely remember reading about it but after moving to T security setting crashes, I can't seem to uninstall apps either. Any fixes?
[Pixel C Android Development] acrickie:
The comments about this issue are at the beginning of this thread, so you may want to read through them, it seems to be about the vendor.img but I definitely do not have this problem after rooting as per the instructions in this thread and updating to the T firmware using fastboot to flash both system.img and vendor.img.

Not sure what to suggest other than trying to reflash the vendor.img from inside the official Google T "factory image" files.
[Pixel C Android Development] r_nation:
I flashed those exact files, will try again
[Pixel C Android Development] followmsi:
Bad news from Chainfire ...

[quote name="followmsi" post=65172629]

Is 2.67 ready for pixel c ?

The bootloader seems to be very special and people had somehow killed fastboot functionality.

Any experiences on pixel c here ?

[/Quote]

Chainfire:

Here is the link to this thread .. Supersu beta ..

http://xdaforums.com/showthread.php?p=65177799

Hmmmm .. No good news at all !

But xceed will manage it !!!
[Pixel C Android Development] Boal:
Anyone here know if the kernel supports OTG? I tried it but it didn't look like it does, but maybe I'm doing something wrong.
[Pixel C Android Development] beardymcgee:
what are you trying to connect?

ive had no issues connecting a hdd, ps4 controller, ethernet, sd card reader
[Pixel C Android Development] Boal:
I tried a keyboard and a USB thumb drive, but nothing came of it. Did you have to configure something? Maybe it's just my hardware. I have a micro-USB OTG cable that I attache using a micro-to-C adapter. What are you using? I read that some people can't make it work with some combinations of cable and adapter.
[Pixel C Android Development] beardymcgee:
im just using the usb c to usb a type that comes from google store for drive etc and an anker micro to USB a type joined together to plug in ps4 controller
[Pixel C Android Development] r_nation:
Does anyone know if its ok to flash phhusson's vendor.img on T, to try to resolve my issues?
[Pixel C Android Development] r_nation:
Nevermind, fixed:)
[Pixel C Android Development] cheep5k8:
v1-RC10

Camera works again

No more random reboots. BUT, I'm not sure we're dealing with only a single source of spontaneous reboots here, so IF they still occur, please do the following: after the device reboots from the random reboot, use "adb shell" or a terminal app and somehow save the contents of "/sys/fs/pstore/console-ramoops". It contains the kernel messages from before, and including, the crash, and then please make a post with the contents (or link to the contents). Thanks!

Enabled a few config options in dragon_defconfig (kernel config), e.g. iptables NAT, to avoid netd erroring out on some commands during boot when those options are disabled/features not present

Kernel version now contains the xceed kernel version, timestamp and the usual git hash

No other new features since the priority was to fix the random reboots; TCP algorithms are still enabled. I've looked into cpu schedulers, but most available need to be heavily modified to work in the 3.18 kernel and with this device, so this is still a bit ways off

I've updated the OP with the v1-RC10 kernel download.
[Pixel C Android Development] followmsi:
Welcome back !

I have used RC3 and had still some reboots, then I used your stock rooted K version.

No reboots with stock kernel .. But I am happy to test RC10.

Thanks

---------- Post added at 06:40 PM ---------- Previous post was at 06:19 PM ----------

Running on RC10 now ?

If I would like to test stock T boot.img ..

1. flash T boot.img via fastboot

2. boot directly into TWRP and flash supersu.zip

3. reboot into system for the first time with rooted stock kernel

4. reboot to TWRP and fix fastboot

5. boot into fastboot and validate that it's working.

6. boot into system and try using the rooted stock kernel.

What else will break except fastboot ? (Which can be fixed via TWRP)

Thanks for your input ..
[Pixel C Android Development] cheep5k8:
Nothing really. Also, you can now safely flash SuperSU starting with version 2.67, as Chainfire added provisions so that the ZIP doesn't try to modify the boot image. That means of course that you need a kernel that already has the neccessary ramdisk modifications, such as this one.

I'm still planning on adding TWRP support for flashing ARM64 FIT boot images (e.g. Pixel C) including signing before flashing, so that e.g. Chainfire could use that additional functionality and in future fully support the Pixel C without him needing to do all the legwork he probably doesn't have the time to (and it's really a bit messy).
[Pixel C Android Development] cheep5k8:
Hey guys,

Made a small mistake. I've used a ramdisk for this build that does not contain the SuperSU modifications, so you will (temporarily) loose root when you boot the RC10.

I'm preparing a new build, will post it in a while.
[Pixel C Android Development] cheep5k8:
[MENTION=5480152]followmsi[/MENTION]

I've uploaded RC10-3 which contains the correct ramdisk prepared for SuperSU again. Sorry for the troubles.
[Pixel C Android Development] followmsi:
Thanks for your answers!

Sorry, one more question .. :)

As I understood systemless supersu you need to patch the boot.img to make it running.

You mean starting from 2.67 there is a detection in the zip file for already patched boot.img.

Like your kernel .. but if not, if it´s fresh stock boot.img ?

Is supersu.zip not able to patch the pixel c boot.img correctly ?

Required ramdisk modifications are not done by supersu.zip in this case ?

Due the Chromium bootloader, which you want to fix by special TWRP version.

The result of installing supersu.zip via TWRP is not a stock rooted kernel ?

Of course, we still have the fastboot problem, which is fixed for now.

My plan was to test stock "rooted" T boot.img, as system and vendor are running on T already.

Sorry, for all my questions .. but I really would like to prevent a semi-bricked device :)

Thanks !

---------- Post added at 08:26 PM ---------- Previous post was at 08:23 PM ----------

ADB is still running .. few minutes later we run RC10-3. [emoji1]

Thanks!
[Pixel C Android Development] r_nation:
So flashing RC10-3 then flashing chainfire 2.67.zip through twrp would fix nvidia's tlk issue in future ota's?
[Pixel C Android Development] fiver5:
RC10-3 breaks adaptive brightness. Worked in RC4. Haven't experienced the reboot issue yet in RC4 so running that for now.

Thanks for the good work.
[Pixel C Android Development] cheep5k8:
There's quite a bit of issues really. I can also recommend to everyone to perhaps stay with an earlier RC* version for the time being.

I wish Google would tag MXB48T in git, so I would have a proper base to start from :(
[Pixel C Android Development] followmsi:
Just did test supersu.zip 2.67 on fresh T boot.img - Like you said the supersu.zip will not modify the ramdisk.

I did not even boot into T, just flashed back to RC10-3.

Looking forward for your next TWRP .. Maybe you are able to include OTG as well ? ?

Cheers
[Pixel C Android Development] cheep5k8:
Yeah, I'm keeping that in mind, though I'm rather sure that old-style OTG will not work on the Pixel C, but we rather need USB-C host mode. I would need to get an appropriate external device to test that.

I think I'm going to make one more stable RC release without any kind of experimental/testing features until Google tags MXB48T, and then work on the next version of (my fork of) TWRP.

So much to do, so little time. ;)
[Pixel C Android Development] followmsi:
I have a small usb-c to usb-a adapter.

Within Android it's working fine and detects my USB stick.

Yes, please go for stability first ?

Cheers
[Pixel C Android Development] cheep5k8:
It's the primary concern :cool:
[Pixel C Android Development] cheep5k8:
BTW, in case anyone is interested, there was one last random reboot issue: basically the SDHCI subsystem would cause the kernel to schedule while being in atomic state, that would then cause a reboot. The WiFi card is connected via SDIO (so via SDHCI).

It seems I was just able to fix this!

This does not fix the main WiFi issue with slow speeds, etc., however, but at least the reboots have stopped. I will monitor this through the day, and then can hopefully release a new stable version again so that I can start working on TWRP 3.0.0.0

PS: This is the one reboot reason why the stock kernel also sometimes reboots; I've already eliminated all reboot reasons caused by my modifications. So, kinda better than stock ;)
[Pixel C Android Development] sethyx:
There you go: MXB48T

Also: this tag, and a new stabilize branch might interest you.
[Pixel C Android Development] cheep5k8:
Awesome, thanks! :laugh:
[Pixel C Android Development] cheep5k8:
There are surprisngly little changes in the kernel for MXB48T. There are commits for the touchscreen which I had already included, and some fixes for WiFi, but those only peratain to vulnerabilities in the driver, nothing really to fix "the" WiFi issue yet.

I'll see what I can make of it....

EDIT:

Aside from that, my bugfixes for the random reboots look good. I'm going to let the tablet sit overnight and if everything works well, upload a new RC build. Technically they should be correct, but I want some kind of test in addition, just to make sure.
[Pixel C Android Development] followmsi:
Are you able to make a stock rooted T as well.

Like you did for K too.

Looking forward for your next release .. ?
[Pixel C Android Development] Boal:
That's great, thanks for all the work you are putting into our tablets! It wouldn't be half as great without your contribution.

May I also ask that you check whether the kernel still provides network bandwidth information? I'm using an xposed module to see the traffic and it doesn't seem to get values >0 any more. That wasn't the case before RC10.
[Pixel C Android Development] cheep5k8:
Yeah I'm just gonna make a stock rooted T for the moment, until I can get issues with the custom kernel resolved.

EDIT: OK, I've added the stock MXB48T without forced encryption+root to the OP.
[Pixel C Android Development] followmsi:
Thanks a lot !
[Pixel C Android Development] r_nation:
Thanks for rooted stock T!! Anyone running layers on their C?
[Pixel C Android Development] bill3508:
Haven't heard of anyone trying. This isn't really a 100% android device so no clue if you could.
[Pixel C Android Development] r_nation:
Ya, thought I'd ask a lil nervous to attempt.
[Pixel C Android Development] cheep5k8:
Actually, I did. At the moment I haven't installed any since I keep reinstalling the device often, but Layers works just allright (I tried a few different beta ones from the BitSyko community, as well as some that I bought).

Layers is OK to go.
[Pixel C Android Development] r_nation:
Awesome!! so it begins....
[Pixel C Android Development] bill3508:
Nice, I'll have to try it.
[Pixel C Android Development] sniperfox47:
I'm using a bunch of RRO layers, xposed v80, and the SuperSU from XCeeD and they all work great. Even with XCeeD RC10 I haven't had any issues yet.

Gonna try upgrading to SuperSU 2.67. At this point does it work unmodified or am I going to have to make any modifications to the su.img
[Pixel C Android Development] r_nation:
If you have latest version of twrp(1-19-2016-1) just flash su 2.67.zip...
[Pixel C Android Development] sniperfox47:
All working good. On 2.67 SuperSU now. Now just waiting for encryption support in TWRP so I can encrypt my data partition again and I'll have my device right where I want it!
[Pixel C Android Development] cheep5k8:
[MENTION=4794286]sniperfox47[/MENTION]

Thought I'll let you guys know that I've updated the TWRP post with TWRP 3.0.0-0. Encryption support should work, but feedback on whether it actually does for you would be welcome (I didn't test with my Pixel since it's currently unencrypted)
[Pixel C Android Development] followmsi:
Super cool !

Did you enable OTG as well ? ?

Will test now !

Thanks again !

---------- Post added at 11:12 PM ---------- Previous post was at 11:09 PM ----------

And RC15 too

... Cooooool !

---------- Post added at 11:44 PM ---------- Previous post was at 11:12 PM ----------

OTG is not working .. anyway thanks for the both releases today.

Cheers
[Pixel C Android Development] sniperfox47:
OTG with a type C to micro adapter will always have problems even if he can manage to hack it into the kernel. The Type-C legacy cables announce themselves, among other ways, by shorting the same pins that the old OTG cables did, just with different resistances. They way they announce themselves conflicts. Besides, the Pixel C has no support for OTG in it's USB controller chip.

One of the new Type-C to Legacy female-A adapters should work without issue, both USB 2.0 versions and USB 3.0 versions. I've had 0 problems with it on this kernel. Apple and Google both make them ("USB Type-C to USB Standard-A Adaptor") or you can get them from plenty of third parties now.

TL;DR: You're SOL on the idea of using a Microusb OTG adapter, but USB C to A adapters already work fine. And they have the benefit on supporting USB 3.0 if you get the right adapters (Both Google and Apples version supports USB 3.0).
[Pixel C Android Development] followmsi:
Yes, I am talking about usb-c to usb-a adapter which works fine within Android.

No micro usb adatper, this was discussed before here.

I would love to see it working in TWRP.

Cheers
[Pixel C Android Development] sniperfox47:
Oh my apologies. Got confused because you mentioned it in the kernel thread rather than the TWRP thread xD
[Pixel C Android Development] followmsi:
No worries .. Hopefully it's working in TWRP.
[Pixel C Android Development] bill3508:
Is the v1 release the newest still or is that old link?
[Pixel C Android Development] beardymcgee:
hey so since running v1 release, and kernel tweaks tweaks turned off, ive noticed benchmark scores across the board have dropped, not sure the real impact as ive only been watching media today but scores as follows:

geekbench: single 1200(normally 1400+) multi 3000(normal 4400+)

antutuv6: 70000(normal 100000+)

3dmark: es3.1 unlimited 2700 (normal 3700)

also no thermal throttling or and visible impact with cpu freq stepping
[Pixel C Android Development] cheep5k8:
I've released v1, so it's the most recent link! ;)
[Pixel C Android Development] cheep5k8:
Hey,

Actually I also thought I'm gonna run geekbench3 on v1-release and compare with Ars' reference test, and noticed a significant drop in benchmark scores as well.

I think the reason is that with the recent change to control the EMC clock from the cpufreq driver through the EMC driver, together with making the kernel tickless (I have configured it full tickless) resulted in the kernel being much quicker to adapt to reduced load, even on tiny scales. I think this has no actual impact when using the device but will show in benchmark scores.

I'll re-run geekbench with CPU gov set to performance, and post some results.