yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] brando56894:
Over the past few weeks the wifi on my pixel was getting pretty crappy, first time since I've had it, I didn't think anything of it, until it was a constant thing. SSH would lag horribly when I was just connecting to a pc in LAN, I switched over to mosh and that would tell me it couldn't contact the server every few minutes and then reconnect about 10-30 seconds later. I just ran a few simple tests between my nexus 6 and my pixel c and the C is definitely the issue since there were none with my 6, both are using 2.4 GHz in a dense residential area with a lot of WAPs (I'm not colliding with anyone, I made sure). I've always been using your newest kernels (currently on v6.10-TEST3) so I don't know what the issue is.

Here's 3700 pings between my pixel and my router (which is separate from my WAP, a Verizon FIOS router, which I'm replacing with a 5 GHz AC WAP), notice the 7% packet loss and the high max response time of 3400 ms! Average of 70 ms (I'm sitting literally 10 feet or less from my WAP and there is nothing blocking the signal).

Here's my Nexus 6 at the same distance, right after the Pixel completed it's run, 0% packet loss and a low average time of 13 ms and a max of 630 ms

Here's an iperf3 run between the Pixel and my NAS, the connection always drops out in under 60 seconds (usually around 10-30 seconds) on the pixel, but will continue like normal on the Nexus 6. It's usually a random dropout for the Pixel (sometimes after 10 seconds, sometimes after 15 seconds, etc...). I looked at my WAP and it's operating at about a measly 9 MB/sec ( ~76 Mbps), the Nexus 6 sometimes reaches that, and the Pixel does rarely also. but it it also is the one the drops below a MB/sec! Also once the Pixel drops the connection it never re-connects, until I start the test over again.

Pixel

Nexus 6
[Pixel C Android Development] cheep5k8:
Could you give 6.10 a try?
[Pixel C Android Development] brando56894:
False alarm, sorry. An Xposed module I had installed for blocking ads on Tumblr was the culprit. Once I removed that, my speeds in iperf3 rocketed up to 10 MB/sec :) That still sucks, but it's my WAP's fault.
[Pixel C Android Development] Onraad:
[MENTION=4867279]cheep5k8[/MENTION] Thanks a lot for providing root access for this tablet!

I am still on the MXB48J build with an older version of this kernel. To update, should I flash the T build and go through the unlocking/recovery/root process again? Or are not all these steps necessary? Thanks
[Pixel C Android Development] UK_Wildcats_Fans:
I would like to thank you for your efforts and hard work. The performance difference from stock is very apparent and significant. Everything is working much better and I have access to all the great apps that require root.
[Pixel C Android Development] beardymcgee:
[MENTION=4867279]cheep5k8[/MENTION]

Just advising mxc14g release nice and stable, great job on quick release.

So as everything seems smooth now, and if you're willing to share what's next?

Could we have CPU/GPU OC and GPU governor access from kernel managers?
[Pixel C Android Development] teshxx:
is the 6.10 mxc14g stock or the one with changes?

Also, cheep5k8, would you be kind enough to post a stock rooted mxc14g boot img like you did for MXB48T?

Thanks
[Pixel C Android Development] beardymcgee:
with changes
[Pixel C Android Development] jeston:
First off, thanks to [MENTION=4867279]cheep5k8[/MENTION] for making this tablet rock.

I just upgraded to mxc14g and am having one problem now. When Android starts up I get the following error:

Everything still seems to work ok though. My upgrade procedure was as follows:

fastboot flash bootloader

reboot bootloader

fastboot flash cache

fastboot flash system

reboot into recovery

flash xceed kernel

What did I do wrong?
[Pixel C Android Development] cheep5k8:
Not sure what's different for some users, but I think this warning has no consequences (I had it for a while as well, but it disappeared now). But, again, not sure what causes it in the first place.
[Pixel C Android Development] cheep5k8:
Sure. This evening or so when I get the time.
[Pixel C Android Development] cheep5k8:
Ooof. Not sure yet what's next... ;)

Also for people who have issues after the upgrade (both kernel and factory images): Try wiping cache (not Dalvik, just plain cache) in TWRP. I had major issues with Chrome after the upgrade but a cache wipe fixed it.
[Pixel C Android Development] brando56894:
Do you have a modified /vendor partition? About a month or two ago, rooting required flashing a modded /vendor partition so the security menu in settings wouldn't crash. Flashing the partition fixed the crash but would give you that error. After upgrading a few weeks ago I started from scratch (reflashing system and wiping data, cache, dalvik and flashing the stock vendor) and after booting up and rooting I no longer received that error upon boot up.
[Pixel C Android Development] jeston:
Nope, just got my tablet about 2 weeks ago, although the first time I went through the rooting process I did have a crash when trying to open Security settings. So I reflashed the entire stock image and started over. But I never downloaded or flashed a modified vendor image.
[Pixel C Android Development] brando56894:
Pretty much it means "Something isn't stock". It's not anything to worry about, it's just annoying.
[Pixel C Android Development] jeston:
Alright, that's pretty much what I figured. Just weird that it didn't happen with the previous build.

Also, probably unrelated, is it normal that under About tablet -> Kernel version it's listed as 3.18.0-xceed-MXB48J? I assume this is just text somewhere that hasn't been updated in a couple builds, but thought I'd mention it as well. Made me think I flashed the wrong build at first, but the build date is correct, so I know it's all good.
[Pixel C Android Development] cheep5k8:
It's fine, I just forgot to tag the git tree with MXC14G after rebasing.
[Pixel C Android Development] jeston:
Cool thanks again! Keep up the good work :good:
[Pixel C Android Development] UK_Wildcats_Fans:
There are many different version of Viper4Android (lolliviper) out there that seem to be tailored for specific devices. Would someone please post a link a version that is work on the Pixel C.? Thank you.
[Pixel C Android Development] JoeDat:
Anyone else experiencing location service issues on the 6.10 kernel? Looks like my device is unable to provide it to various apps. If I downgrade to the 6.8 kernel, I still had the same problem until I wiped cache and Dalvik. The same cache/Dalvik wipe didn't fix on 6.10. Logcat output shows the following when I attempt to lookup location.

3308 3308 E LocationReceiver: Received bad location: null

Edit: This was via Google Maps.
[Pixel C Android Development] bill3508:
So for whatever reason I erased cache in fastboot, who knows, i was thinking of something else. And now the C won't boot and it whenever I try to fastboot flash cache it says image is corrupt and fails. Ive downloaded the image twice now and same. Any way to go here or should I just try to flash back to stock?

Weird, so leaving it alone for 10 minutes pondering my options the same cache image that said was corrupt before just flashed. So now its booting again.

Thanks for the updated kernel.
[Pixel C Android Development] Boal:
I'm tempted to try the N preview. What do you think, [MENTION=4867279]cheep5k8[/MENTION], is there a chance we can use your kernel with it without potentially dire consequences?
[Pixel C Android Development] cheep5k8:
I haven't tried it myself and am really not planning on doing so, and would definitely not recommend trying it. I personally don't think something terrible will happen but really, I don't know what might, so as developer of xceed, I'm fully advising not to try it.

EDIT: In case anyone is wondering, TWRP might be OK, but so far, I'm already having massive issues with TWRP and Android N Preview on my Nexus 6P, and not sure what the specific issues are yet.
[Pixel C Android Development] bill3508:
Same they'll get it worked out but until then I'll just run stock on the 6p. Shouldn't take long. N on the Pixel C is running very nice though. Actually feels pretty snappy.
[Pixel C Android Development] spybyscript:
I've tried it on my pixel C and already rolled back to M with your kernel.

Pixel C right now with N is a horrible, janky mess that performs about 1/2 of what it can do in M right now (most benchmarks are about half as good as they are under M), many apps break outright (and part of this I identified as sqlcipher making use of NDK calls that aren't allowed/changed in N) and really... unless you're doing dev work that needs to test compatibility with N there is no reason to have a pixel running N.
[Pixel C Android Development] xennos:
Hello,

Little question. Your kernel totally fix WiFi bug or make WiFi little better than before (bug) ?

2 issue for me : flash kernel or RMA ..

My pixel sleep in my drawer 2 month now.

Sorry for my English . thanks you ☺
[Pixel C Android Development] JoeDat:
Bumping, as I think this might be a bug in the new kernel
[Pixel C Android Development] cheep5k8:
I'll look into it, however a little busy at the moment.
[Pixel C Android Development] cheep5k8:
I don't think it fixes *all* issues with the WiFi. For some cases, it's substantially better, and it also fixes some invisible underlying technical issues with the WiFi, but (I think?) some users are still experiencing poor WiFi even with this kernel.

Maybe others can say a little more about this? I'm just one other user (when I don't develop the kernel or TWRP ;) )
[Pixel C Android Development] teshxx:
I guess I am in the lucky few who has no issues with WiFi (fingers crossed).

Hey cheek5k8 ... any update on the MXC14G stock rooted boot img?

Thanks bud.
[Pixel C Android Development] JoeDat:
Thanks. Wasn't an intention to rush. Just felt that it might have gotten buried, and a bug report isn't something I'd imagine you want to miss.
[Pixel C Android Development] wangsiyu:
It seems that the maximum CPU frequency is locked at 1720MHz although you set the frequency higher.
[Pixel C Android Development] xennos:
OK Cheep , I see.

Thanks you for your hard work ?
[Pixel C Android Development] cheep5k8:
I'm at it right now. Going to prepare an MXC14G stock rooted image, as well as an N Preview kernel.

Soon(TM) ;) (In an hour or 2)
[Pixel C Android Development] Boal:
I don't wanna be annoying and sound like a broken record but if it's possible it would be really great if you could also have a look at why the bandwidth monitoring isn't working any more.
[Pixel C Android Development] DanRyb:
Hmmm, am I doing anything wrong? I flashed your N Preview kernel and installed phh's Superuser from the Play Store, however I do not have root?
[Pixel C Android Development] tw1tch175:
Same, I restarted and it prompted me to update the SU binary but it didn't do anything when selected.
[Pixel C Android Development] cheep5k8:
Yeah, a slight detail went wrong when building the image. I'm trying to fix the problem this instant.
[Pixel C Android Development] DanRyb:
Wow, very cool! Thanks for your hard work!
[Pixel C Android Development] beardymcgee:
I've noticed this too,

Maybe it was changed in stock march release, have you noticed this [MENTION=4867279]cheep5k8[/MENTION]?
[Pixel C Android Development] tw1tch175:
Has the N image been updated with the root fix?
[Pixel C Android Development] cheep5k8:
Current status of everything is:

I can't properly make a rooted stock image for N Preview since Google hasn't posted the kernel image yet

I'm having troubles with building an xceed N kernel; I can build it and it basically works, but there are reboots again

Additionally, I'm having issues with both phhusson's Superuser and SuperSU with N Preview. Those issues are known, and Chainfire has released a version of SuperSU that works with N, but unfortunately so far, on N Preview, no one (?) has been able to decrypt data within TWRP (I also tried it on my 6P but no luck)

Safest bet for the moment is if you run N Preview complete stock, or Marshmallow stock/rooted or with xceed.

EDIT: Guess I will do it dirty and extract the plain kernel image from the N Preview factory image, and then use SuperSU 2.69 for root. Fingers crossed.
[Pixel C Android Development] Scarfacez2007:
6.0.1 (MXC14G) with root??
[Pixel C Android Development] cheep5k8:
Ow. I forgot about that one. That one is no problem, gonna prepare it today after work.
[Pixel C Android Development] Scarfacez2007:
Alright no problem, and I can wait for you:) let me know when you all done for this keep it up
[Pixel C Android Development] CrazyPeter:
Thanks, also keen to try a totally stock (except root) MXC14G
[Pixel C Android Development] markshep:
I followed the guide to unlock my bootloader, install TWRP & flash an xceed kernel (v6-RELEASE) with the MXB48T release. Then today I was offered an OTA update to MXC14G. After checking there was an xceed kernel available for it I started the install. However it rebooted into TWRP rather than the Google updater thing. From there I did a normal system boot and it's showing me as still on MXB48T (which I'd expect), but checking for a system update tells me that my system is up to date :(. I have two questions about this:

1. How should I install an OTA update so that I don't break things next time? Do I need to first install the standard recovery rather than TWRP?

2. To get to MXC14G from my current state do I have to reinstall the whole thing from stock (and therefore lose my data), or is there a way to just apply an update without a total reinstall?

Thanks,

Mark
[Pixel C Android Development] cheep5k8:
You most likely don't need to delete data either way.

I recommend you download the factory image for MXC14G: https://dl.google.com/dl/android/aosp/ryu-mxc14g-factory-3bc18b89.tgz

Then from that image (you need to unpack this archive, and then inside again the ZIP archive), in fastboot, flash *only* vendor.img and system.img:

tar xfz ryu-mxc14g-factory-3bc18b89.tgz
cd ryu-mxc14g
unzip image-ryu-mxc14g.zip
(reboot the Pixel into fastboot)
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot xceed-kernel-google-dragon-v6.10-RELEASE-mxc14g.img
fastboot flash recovery twrp-3.0.0-0-dragon-ryu-02-11-2016-1.img
(reboot)

That should basically do it. You might still need to copy su.img to /data/ from TWRP as per instructions. I'm looking for a way to simplify that but for now it's unfortunately still a small annoying neccessary step. :)

EDIT: To answer question 1) directly, yes that would be the way to go: flash the stock recovery, apply OTA, then re-flash TWRP again.
[Pixel C Android Development] markshep:
Thanks, that got it working while keeping my data intact! I didn't need to copy su.img as the /su directory was still there (and still working) after flashing the upgrade.
[Pixel C Android Development] UK_Wildcats_Fans:
For MXC14G, I did the same. I flashed system, vendor and xceed kernel via fastboot. That was all that was needed.
[Pixel C Android Development] 530farm:
Can anyone explain why you have to format user data when flashing this/rooting? Also, do you have to do the extra steps like pushing su.img etc. or can you just do the following :

Fastboot flash xcdeed.img > flash supersu 2.68 in twrp?

Thanks,
[Pixel C Android Development] cheep5k8:
My TWRP is not able to decrypt /data, I haven't yet had the time nor the hint as to why, so everything will only work when /data is unencrypted.

You can theoretically flash SuperSU 2.68 but the way Chainfire built is is that it will abort when it detects the Pixel C, leading to an incomplete installation (that is just a safety measure as not to softbrick the device).

The Pixel C is a bit harder to deal with than other Android devices because it is basically a Chromebook that runs Android. It's a bit more challenging on the hardware and firmware side, which is why many things don't work exactly like on a typical Android device.
[Pixel C Android Development] 530farm:
I appreciate your response. I ended up deciding to take a risk last night, and here's what i did.

Did not format data.

Flashed xceed kernel.

flashed supersu 2.68 via twrp > Towards the end of the script it did mention and error about mounting a partition, can't remmeber which now, but seemed to complete.

Rebooted

Everything seems to work fine. I have supersu installed and root working. Device is till encrypted. Do you recommend i go back and start the process over gain w/ formating data to unencrypt? I figure that would remove the mounting partition error I got. However you said Supersu would abort on a pixel c, which it didn't do and seemed to work. Thoughts?
[Pixel C Android Development] cheep5k8:
Then Chainfire might have changed something in 2.68.

What systemless SuperSU does is it extracts the device's boot image, unpacks it, modifies the ramdisk, and flashes the boot image back, then installs su.img on the /data partition.

So from this perspective, a few things are curious about what you're describing:

- First, the changes to the ramdisk are, basically, not neccessary with xceed as I have incorporated the changes into the kernel image already, but I'm not sure why 2.68 didn't abort on recognizing a ChromeOS boot image, which 2.67 used to do. Still, using xceed and then installing the su.img is enough for SuperSU to work, so if 2.68 managed to install the su.img file, then everything should be good to go.

- Secondly, I don't see a need to unencrypt data if everything works for you. Did you place the su.img file yourself, probably from Android and not TWRP? Couldn't have been done from TWRP as it is currently unable to decrypt /data and write to it
[Pixel C Android Development] 530farm:
I didn't place any su.img myself. The only thing root related I did, was flash xceed via fastboot, then boot into twrp and flash supersu 2.68 and rebooted. didnt' manually push su.img like the tutorial.

You seem like the resident pixel super dev, maybe you want to give just flashing supersu 2.68 or newer without any of the manually pushing su.img, and see if thast the way to go now? Thanks again for the response
[Pixel C Android Development] cheep5k8:
Yes I think I should do that, or at least inspect the SuperSU ZIP for what changes Chainfire has made so we're in the clear what's going on.

Eventually I'm planning to extend TWRP for the Pixel C in such a way that it is safely possible to flash kernel images and transparently have TWRP sign them with dev keys as is required with a ChromeOS boot image, all the while the ZIPs that do that don't need to care about this process, like e.g. the SuperSU ZIP.
[Pixel C Android Development] 530farm:
Please let me know what you see. I may try unencrypting and flashing supersu like I did again. Any real danger of doing so?
[Pixel C Android Development] scoobydu:
[MENTION=4867279]cheep5k8[/MENTION] I'd also appreciate your views on any likely issues installing your TWRP and flashing chainfires 2.68 supersu to directly modify boot.img.

Thanks in advance
[Pixel C Android Development] 530farm:
Also, I see you added tap to wake at one point but didn't see it in any kernel app and didn't see any posts saying you removed it. Thanks
[Pixel C Android Development] DaConcho:
http://xdaforums.com/pixel-c/general/pixel-c-rant-developer-perspective-t3301632

Read what he said there..
[Pixel C Android Development] drewski_1:
I also installed your Kernel & flashed Supersu 2.68 and am rooted AOK. It looks like it installed su ok, but borked on kernel / ramdisk mods.

It's Systemless

Sent from my Moto X

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

I think it's the other way. The boot.img modification is last so the superuser image is installed before the Flash errors out.

I did decrypt data first so that might be why it worked?

In your OP you say flashing SuperSU 2.67+ is OK, but if it's dependent on decrypting stuff, that probably needs to be made clear.

Either way, I appreciate your Dev efforts on the Pixel C and am enjoying my Rooted / Decrypted tab so far (just one day) :good:
[Pixel C Android Development] dkryder:
drewski_1, what build/kernel combination do you have? I am thinking of setting up my pixel c with cheep5k8's work . mine arrived today and has MXC14G. This one actually works rather well.
[Pixel C Android Development] natezire71:
How did you flash SuperSU in TWRP? I'm trying to replicate what you did and I'm not able to mount /data or perform adb sideload. I'm not sure how you flashed it then...
[Pixel C Android Development] charesa39:
First, just wanna say THANKS for all your hard work and time you've dedicated to making this device as tinker friendly as possible. I do have a quick question:

How are you modifying the ramdisk on the stock kernel to allow root? Are you using Android Image Kitchen? What changes do you make? I used to use AIK to disable forced encryption in the stock boot image for my Nexus 6. It was as simple as unpacking the image, replacing forceencrypt with encryptable in the fstab file inside the ramdisk, and repacking. However, I assume making the appropriate changes to allow root in the ramdisk for the Pixel C isn't as simple? I can't even get Android Kitchen to unpack the Pixel boot image... I assume because of the whole ChromeOS thing?

Just trying to see if this is something I can do myself so I can be one less person bothering you for mods. :D
[Pixel C Android Development] drewski_1:
I upgraded to MCX14G first and then unlocked, decrypted (re-format) + the Xceed Kernel, and finally SuperSU 2.68

---------- Post added at 11:15 PM ---------- Previous post was at 11:15 PM ----------

I updated to MCX14G first and then unlocked, decrypted (re-format) + the Xceed Kernel, and finally SuperSU 2.68

---------- Post added at 11:19 PM ---------- Previous post was at 11:15 PM ----------

Not sure, but sounds like you're not decrypted?

Follow the steps in the Rooting guide. This will decrypt the tablet.

Just a guess. Good luck!
[Pixel C Android Development] cheep5k8:
If you use Linux:

dd if=originalkernel.img of=out.img ibs=65536 skip=1

That will give you an image you can unpack with Image Kitchen. However if you repack it, you can't simply flash it again, you will have to sign it for vboot. But that's a topic for another post :P
[Pixel C Android Development] cheep5k8:
Due to how the Pixel C is constructed hardware- and firmware-wise, it was not doable.

In fact I had two separate implementations working: one that uses the screen like on other devices, and the other used the same mechanism that is used for tapping the light bar.

But due to specifics of the Pixel C, none of them would work permanently under all circumstances. Maybe the screen one would if I had more access to firmware source code, but at this point... nope. (I read a ton of documentation about the related hardware already, but it didn't help much)
[Pixel C Android Development] natezire71:
Yes, I'm not decrypted. You're missing the point. The guy I replied to was able to do everytging without decryption
[Pixel C Android Development] JoeDat:
Wanted to post that I'm no longer experiencing this issue. Was pretty convinced that it was related, but things are fine now on 6.10, so dunno what the deal was. Just wanted to make sure you weren't spinning your wheels looking into what appears to be a non-issue.
[Pixel C Android Development] charesa39:
Whoa... May be way over my head as I simply use Windows. I guess I'll have to leave this to the pros. :o

Thanks for the info!