yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] NYCHitman1:
BioShock CPU gov is REAL nice. I think that people just need to remember that while it was originally designed to be used on Tegra chipsets -- it is a conservative-based governor, so there is a chance that performance can take a hit while performing resource intensive tasks.
[Pixel C Android Development] hagbardceline23:
Did you manage to get access to the mounted share as normal user ? I can only get access to the share as superuser - i think it might be an SElinux issue. I tried to "setenforce Permissive", but this immediately is forcing a reboot :(
[Pixel C Android Development] cheep5k8:
Worked for me as user...
[Pixel C Android Development] hagbardceline23:
.. strange ... how did you mount the share ?
[Pixel C Android Development] cheep5k8:
I didn't mount it, I accessed it through an app.
[Pixel C Android Development] hagbardceline23:
.... now it works perfekt - the problem was simply the wrong mount point ;)
[Pixel C Android Development] wardy277:
It's been a long while since I had a device with a cifs supported kernel. I used mount manager back I the day but it doesn't seem to be avaliable. How are you all mounting your cifs shares? I found an old patched version of cifs manager but that is very unusable and mounted an empty folder...
[Pixel C Android Development] hagbardceline23:
I am also using the old patched version of cifs manager (v1.5a). Try to install StickMount, start it once, and reboot your pixel ... now it should work. I use "/data/media/0/cifs/" as MountPoint.
[Pixel C Android Development] cheep5k8:
v8.01

Released v8.01. Only major change is fixes in the MMC driver to fix a sometimes occuring, very rare kernel panic in the ext4 VFS caused by nonresponsive MMC driver.

Downloads will be available from now on on srvr.tech (our build-and-everything-else-host):

https://dl.srvr.tech/ryu/xceed/
[Pixel C Android Development] NYCHitman1:
Did you get the source up for that commit yet? I noticed this happen the other day, but I was too lazy to track it down since it literally has only happened once in over a month of total time.
[Pixel C Android Development] cheep5k8:
Not sure if I actually pushed. But it's not just one change, I've basically used the device/mmc/ tree from xceed v6.10. I need to double check a few things in my working tree and then I'll push the changes.
[Pixel C Android Development] ilpolpi65:
I flashed v8.01 on N3 : can I encryot Pixel C again ? Thanks
[Pixel C Android Development] cheep5k8:
That should work without issues. Only the v6.xx versions have verity and encryption disabled by default; for v8.xx and N Preview you would need to flash the kernel, then SuperSU which modifies the ramdisk to disable both, and then format data and go from there.

If you're currently in an unencrypted state you can simple re-encrypt it. Since followmsi's TWRP now supports decryption in recovery everything should be good to go.
[Pixel C Android Development] ilpolpi65:
[MENTION=4867279]cheep5k8[/MENTION] : all OK thanks !!
[Pixel C Android Development] followmsi:
Not yet .. Still not working .. Maybe in the future :)

EDIT:

Fresh compilation from today ... TWRP_dragon_3.0.2-0_v7.img

The relevant build flags from today ... built on AOSP r43 .. not r32.

TW_INCLUDE_CRYPTO := true
TW_CRYPTO_REAL_BLKDEV := "/dev/block/platform/700b0600.sdhci/by-name/UDA"
TW_CRYPTO_MNT_POINT := "/data"
TW_CRYPTO_FS_OPTIONS := "noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,discard,errors=panic"

Pls test .. Thanks !
[Pixel C Android Development] manaka3161:
I'm running my Pixel C (Android N Preview 3) rooted with xceed-v8.01-NPD35K.img + SuperSU 2.74.

And there are some problems.

First, movie's audio is not playable when video playback is SW decode mode. Even if I change playback app, I get the same result.

Second, specific apps can't gain root access. For example, I can't use root explorer mode with ES file explorer. (Notification popup window of root access doesn't appear when launching app, in the first place.)

Adaway isn't usable, too. Most of apps can gain root access. (e.g. TitaniumBack, RootBrowser, BusyBox, etc)

Is there anyone who has the same problems?
[Pixel C Android Development] pkelly517:
Maybe you should look through the SuperSU beta thread.
[Pixel C Android Development] drewski_1:
Contact ES dev. Their app has hard coded SU location that does not work with Systemless root. There's a workaround in the SuperSU thread.

Also, you should ditch ES. It has Spyware.

AdAway also has a workaround. Check the thread for it.
[Pixel C Android Development] manaka3161:
Thanks. I should have posted to another thread.

They have a workaround! OK, thank you. I'll try them.

And sorry to have posted to the wrong thread.
[Pixel C Android Development] YevOmega:
N DP4 is out!
[Pixel C Android Development] ilpolpi65:
Your kernel is the only one that saved me from random reboots..are you going to update to N4 ?
[Pixel C Android Development] Alxoom33:
Does XCeeD v. 8.01 work with N DP4?

---------- Post added at 09:33 PM ---------- Previous post was at 09:28 PM ----------

Are there sufficient changes in N DP4 that requires an XCeed v.8.02?
[Pixel C Android Development] cheep5k8:
I haven't looked yet.. I'm just (as usual :) ) way busy, but I'm planning on releasing 8.02 for DP 4 if there's enough relevant changes (probably this weekend or so). Stay tuned :highfive:
[Pixel C Android Development] Alxoom33:
Thank you. I knowthat@flar2 has not yet made any changes to his Elemental X 4.0.5 kernel for the Nexus 6 N DP4. But he may be tied up, as well.
[Pixel C Android Development] cheep5k8:
I've uploaded a v8.02 but I don't think it's working right (the device keeps reverting to the stock DP 4 kernel); I'll check what's wrong.

Okay, so you need to modify /system/bin/install-recovery.sh, and delete all but the first line (I thought that SuperSU modifies that script, but apparently it doesn't, or doesn't any more).

Then DP4 will stop reinstalling the stock DP4 kernel, and you can flash xceed (and supersu).
[Pixel C Android Development] Alxoom33:
I'm not sure I understand. We need to modify the System in order to install the Kernel? Is there a way of doing it in the other direction? Modify the Kernel so it is compatible with the new system?
[Pixel C Android Development] cheep5k8:
I'm not 100% sure what is happening, but flashing xceed on DP4, and then SuperSU leads to the system restoring the stock kernel. If I just flash xceed there is no problem. Looking into it.
[Pixel C Android Development] Alxoom33:
Are you still rooted after flashing ECeed?

---------- Post added at 08:28 PM ---------- Previous post was at 08:28 PM ----------

XCeed
[Pixel C Android Development] Alxoom33:
You may want to ask [MENTION=631273]Chainfire[/MENTION].
[Pixel C Android Development] jeston:
I'm pretty sure when you install SuperSU 2.74 it restores a backed up version of the stock kernel for whatever reason. I don't know how to stop it from happening, but at least with my Nexus 6 we were told by the kernel dev to just install SuperSU then the kernel afterwards, which I know is backwards from what we're all used to but it works.
[Pixel C Android Development] Alxoom33:
Yeah, when I first rooted the Pixel C that is what I did, Since I too have a N6, but with the Pixel it Recovery Looped.
[Pixel C Android Development] Alxoom33:
flashing of 8.02 kernel image did not work. About phone still shows Chromeos 3.18 6/24/16 version. No matter how many times I tried to flash in TWRP
[Pixel C Android Development] ilpolpi65:
DP4 stock + twrp

I successfully flashed 8.02
[Pixel C Android Development] Alxoom33:
What did you start with, what did you flash exactly... did you use TWRP or fastboot? Thanks,
[Pixel C Android Development] ilpolpi65:
I flashed DP4 >twrp (fastboot)>8.02(fastboot)
[Pixel C Android Development] Alxoom33:
SuperSu 2.74?
[Pixel C Android Development] ilpolpi65:
No...

---------- Post added at 06:23 PM ---------- Previous post was at 05:26 PM ----------

@cheep5k8

thanks!!
[Pixel C Android Development] Alxoom33:
That's the catch. I'm flashing and have SuperSu installed. So there are other background considerations... Thank you for responding.

---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------

Thank you!

Are you flashing the XCeed.img file using TWRP or fast boot? Also, what's the 65B XCeed.8.02.image.sha1 file?
[Pixel C Android Development] cheep5k8:
I flashed the kernel in fastboot, but it seems correct: flashing SuperSU afterwards restores the stock kernel.

The sha1 file contains the checksum of the kernel so you can make sure your download is not corrupted.
[Pixel C Android Development] Alxoom33:
Ok, I just fast boot flashed 8.02 IMG so flashing SuperSu. But About Tablet still shows I have Chromos 3.18 June 24 build.

---------- Post added at 03:06 PM ---------- Previous post was at 02:36 PM ----------

I don't think that my SuperSu can access the stock kernel.
[Pixel C Android Development] drewski_1:
What exactly does that mean?

I'm on DP4 Pixel Stock Kernel and rooted with SuperSU 2.74-2
[Pixel C Android Development] cheep5k8:
Just flash the kernel and reboot, don't flash SuperSU. The ramdisk is already modified for SuperSU functionality.
[Pixel C Android Development] Alxoom33:
That's what I did, above. Did not change.

---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------

Will try again later.
[Pixel C Android Development] cheep5k8:
I didn't have much time since just building 8.02 to test further, but simply flashing xceed, then booting straight into Android worked, though I've also modified the /system/bin/install-recovery.sh script, which also contains code to revert to the stock kernel.
[Pixel C Android Development] Alxoom33:
Unfortunately, that doesn't seem to work for me. When I flash 8.02 image file via Fastboot, Flashify or TWRP, the Chromos 3.18 June 24th version Kernel persists. Interestingly, Flashify will not flash the image saying that it is for an undefined partition. Not sure why. Can you upload a Boot zip file for 8.02 to try. Thanks, [MENTION=4867279]cheep5k8[/MENTION]
[Pixel C Android Development] drewski_1:
Have you tried going back to stock kernel?
[Pixel C Android Development] Alxoom33:
Yes, I did and could then only boot into TWRP (Recovery Boot Loop), so I flashed SuperSU 2.74 and 8.02 kernel and reebooted System. Checked my kernel and it was 3.18 June 24th version, again. I tried reflashing 8.02 and still the kernel is 3.18.
[Pixel C Android Development] penguinyaro:
Can anybody link me to the superSU img and apk? I can't seem to find it. Or is it okay to just flash the zip from chainfire as long as it's above 2.72? I'm not running NDP4, still on 6.0.1.
[Pixel C Android Development] Alxoom33:
Use the [MENTION=631273]Chainfire[/MENTION].eu SuperSu 2.74 zip file
[Pixel C Android Development] penguinyaro:
:highfive: worked great
[Pixel C Android Development] aldawoudy:
I flashed both "xceed-v8.02-NPD56N.img" and "xceed-v8.01-NPD35K.img" but I always get stuck at google logo directly after flashing the img!

Any idea why?
[Pixel C Android Development] Alxoom33:
Flash Super Su 2.74 after kernel and it should. Reboot.
[Pixel C Android Development] EddieK23:
So I've been having some really bad luck lately. Previously, my Pixel C worked great with the OP's guide to rooting and all was well. I got tired of the beeping sound and waiting when I would reboot my Pixel C, so I attempted to re-lock the bootloader once I flashed TWRP and got root working. This is where everything went downhill.

Booting to system would leave the Pixel C in a bootloop that when connected to my PC said that it was "an unrecognizable device". I tried repeatedly unlocking & locking the bootloader, then flashing the proper bootloader through TWRP. After doing the latter, I can no longer enter recovery, and fastboot does not allow me to flash to any partition by giving me the "FAILED (remote: unsupported command)" error.

What I've tried so far includes:

-Entering recovery, gets stuck in bootloop and "unrecognizable device" USB error.

-Booting to system, same issue as above.

-Flashing the custom kernel, get "FAILED (remote: unsupported command)" error.

-Flashing official Android N beta image, same error as above.

-Using SkipSoft Toolkit to try to find a sort of "fix" command that was included in TWRP, can't seem to find one that works through fastboot.

I also tried talking to a Google rep who said he'd get back to me within one to two days, but I'm really hoping I can fix the issue myself. Can anyone offer some help or advice?
[Pixel C Android Development] cheep5k8:
If you don't have TWRP and are not rooted I'm afraid you're SOL.
[Pixel C Android Development] Alxoom33:
Try downloading Wug's Nexus toolkit and follow instructions. It is very intuitive and supports Pixel C through N4. Read the op and thread for Wug's Nexus toolkit. Good luck!

---------- Post added at 11:33 AM ---------- Previous post was at 10:56 AM ----------

[MENTION=4867279]cheep5k8[/MENTION], would it be possible to post a flashable zip boot file of your 8.02 kernel. I have been looking forward to trying it since you had released this Android N4 kernel and I have tried just about everything I know to TWRP and Fastboot flash your 8.02 image, without success. Thank your tireless efforts in developing your kernel for the dragon :) Your work is very much appreciated!
[Pixel C Android Development] followmsi:
[MENTION=4100646]Alxoom33[/MENTION] .. If you want a flashable zip - just unzip an existing .zip file and replace the boot.img and zip it again.

If you still have questions, pls let me know.

[MENTION=4867279]cheep5k8[/MENTION], why dou you still use pre-rooted ramdisk in your latest kernel ?

Why not let SuperSu.zip do the work for you ? :)

This way the user is able to decide if he/she wants root access or not .. maybe some "flashing issues" are solved as well :)

Cheers
[Pixel C Android Development] cheep5k8:
That was just incidental. I'll make a new IMG with a new ramdisk soon.
[Pixel C Android Development] Alxoom33:
Thank you! Made the zip and it flashed ok. However, The 8.02 kernel did not work in my setup. Not sure why. But I'm now waiting for the next iteration for Android N DP5.
[Pixel C Android Development] aoleg:
xceed-v8.02-NPD56N on Android N DP4 (NPD56N). I flashed this kernel specifically to address the Wi-Fi issue that has recently developed on my Pixel C. After using the tablet for nearly 3 months, I started seeing random Wi-Fi disconnects every 3 to 15 minutes. (I tried multiple channels in the 5GHz and 2.4GHz range, factory reset my router, yet the drop offs are still there). Xceed offers significantly better Wi-Fi performance compared to the stock N kernel (Xceed gets me stable 230 Mbit/s down, while stock kernel fluctuates between 40-170 Mbit/s in the same conditions). However, random disconnects are still there, and occur about as often as on the stock kernel. I'm looking for an advice. Do you guys think there's any chance this will be fixed in software, or do I have defective hardware (->RMA)?
[Pixel C Android Development] EddieK23:
So I RMA'd my original bricked Pixel C, got the replacement one, and flashed the NPD56N kernel again (because it's honestly the best kernel). I was wondering, since you've worked on the Pixel C for so long, but is there a way to skip the "Unlocked Bootloader" warning screen during startup, or how to relock the bootloader without going through what I did and having to RMA the tablet?
[Pixel C Android Development] NYCHitman1:
No, it cannot be skipped.
[Pixel C Android Development] Alxoom33:
Looking forward to the next iteration. I was running your kernel, all along. It was labled 3.18....So I thought it was the Chromeos 3.18 version, instead of XCeed 8.2. Please consider labeling your kernel as "XCeed 8.xx 3.18..." so all will know. ;)
[Pixel C Android Development] a.f.x.:
I just installed system.img and vendor.img from MXC89K and then the 3.18 xceed kernel via fastboot.

Now I get a message on each reboot that my system has an internal problem and I should contact my vendor.

But so far the system seems to work fine.

Any ideas? Or shoud I just ignore it?

thx

afx
[Pixel C Android Development] sxg75:
Where is download to latest version for 6.10.X?
[Pixel C Android Development] Alxoom33:
Usually that would be in the OP.
[Pixel C Android Development] sxg75:
Not seeing any MXC89K based?
[Pixel C Android Development] Alxoom33:
V 6.10?
[Pixel C Android Development] sxg75:
-mxc14g.img? no newer one available (-MXC89K)?
[Pixel C Android Development] Alxoom33:
Don't think so on XCeed.

I'm on N DP4. So I don't follow MM kernel development.

However that kernel may work for you. Try it, if it dosn't flash back to stock. Or you can try DU or Chromeos kernels. They are both built for MM.
[Pixel C Android Development] sxg75:
Changing selinux mode via su command forces reboot immediately - though - would it be possible to have permissive mode, even staying alive after reboot - referring to http://xdaforums.com/nexus-6p/general/permissive-mode-android-n-npc56w-build-t3343573 - for the n6p? Or even use logd from that thread?

Edit - I used those two zips from over there and it worked. So its possible to restore apps from Titanium on Android N preview also.
[Pixel C Android Development] Eason85:
Hi guys,

Using this kernel to try and root my pixel C after unlocking bootloader. I was on the latest N preview.

After I flashed recovery and xceed-v8.02-NPD56N, I can't get it to boot. It just stays on the google animation screen. I've waiting 20 minutes- should I be waiting longer?

I figured that it was the wrong kernel for the current OS, thus the animation loop, but I tried xceed-v8.01-NPD35K with the same results. Any ideas?

I'm going to recovery, wiping,

going to fastboot, flashing the boot.img

>>> logo animation forever
[Pixel C Android Development] pkelly517:
Look in [MENTION=5480152]followmsi[/MENTION] thread. He has the latest kernel compiled with necessary ramdisk (?) changes.
[Pixel C Android Development] Eason85:
Thanks for the reply. I restored back to m and then flashed with the latest update.zip, and manually flashed bootloader. Works now.
[Pixel C Android Development] cheep5k8:
[MENTION=987550]sgx75[/MENTION] In a shell, run:

> stop logd

> setenforce 0

No need for a custom (broken) logd, but you will temporarily lose logcat either way.
[Pixel C Android Development] cheep5k8:
Hey everyone,

I'm on vacation right now so no Preview 5 xceed kernel for the moment :(

Though I managed to flash Preview 5 onto my Nexus 6P only using a Nexus 5X and no computer thanks to USB-C... I installed adb and fastboot for Android on the 5X, downloaded the firmware image and flashed it from the 5X. Probably could have used FlashFire.. :D

Either way, just a little story from me until the next build!
[Pixel C Android Development] cheep5k8:
Oh yeah, one more thing, good news: Google asked me to upstream the modified Wi-Fi driver, which means they at least want to take a look at it. Would be great if improved Wi-Fi finally came to all Pixel C users!
[Pixel C Android Development] sxg75:
What makes you think that that compiled logd from "over there" might be broken? Using Catlog/Logcat unter OSMonitor seems to work fine for me.

Well would there otherwise be possible to compile a hacked pixelC "native" logd that allows setenforce 0 without restarting?
[Pixel C Android Development] cheep5k8:
In my opinion it's broken, since the changed behavior is fixed. I'm pretty sure you can hack up logd so no other functionality is impaired or changed except for the selinux detection. But alas, I'm on vacation right now so can't give it a try at the moment.
[Pixel C Android Development] Alxoom33:
Enjoy your vacation[emoji569]
[Pixel C Android Development] RoFrie:
One question: where can I find and download adb and fastboot for Android? Thx
[Pixel C Android Development] cheep5k8:
Oof...I didn't really save the links. I think the simplest way right now would be that I make a ZIP (not a flashable, just a zip) with both, upload it, and see that I credit the original creators even if anonymously.

The stuff is on my girlfriend's phone, I need to wait until she sleeps to upload it ;)
[Pixel C Android Development] RoFrie:
THX that would be helpful.
[Pixel C Android Development] drewski_1:
Search for "minimal adb & fastboot" on XDA to get a thread with the basics you can install.

"Official" can be gotten from Google's Android SDK, but it's s big total package and can be confusing how to set up.
[Pixel C Android Development] cheep5k8:
I think he means adb&fastboot that you can run ON Android, which I used to flash N Preview 5 on a 6P using a Nexus 5X
[Pixel C Android Development] RoFrie:
That is true. Especially when there is no PC around it would be very helpful to use them from one Android via USB to the other Android.
[Pixel C Android Development] cheep5k8:
Server Meltdown

Hi everyone,

Our build&development server had a harddisk meltdown. It's not tragic, everything is up on my GitHub, but I will have to restore the development environment before I can make a new build for DP 5. Originally I planned making a new build today but it seems it will take a bit more time.

Just a heads up ;)
[Pixel C Android Development] Alxoom33:
Sorry to hear about your harddisk meltdown. Good luck with the restore, we can wait. Thank you!
[Pixel C Android Development] cheep5k8:
OK so the reason xceed v8.02 will not boot on NPD90G is because of changes in the ramdisk. Without recompiling I've made an image using xceed v8.02 and the stock ramdisk from NPD90G, and it does boot for me, but your mileage may vary. Just booting it didn't work at all, you'll have to flash it, in fastboot.

You can find the image on our build server's download section (https://dl.srvr.tech/ryu/xceed/NPD90G/)
[Pixel C Android Development] Alxoom33:
Did not boot for me when I flashed the image in TWRP. Worked fine when I flashed image via fastboot and flashed Super SU 2.76 with TWRP. Any suggested settings. I am using EX Kernel Manager which I am using with My EX Kernel on the Nexus 6.
[Pixel C Android Development] cheep5k8:
Hmm, for starters set the TCP algorithm to HTCP, it seems to perform best on the Pixel C (unless of course you already have a different preference). As IO scheduler I tend to use FIOPS with 512KB read ahead. Other than that you could try the Bioshock CPU governor and see if it improves anything for your use case.

My kernel doesn't have too many options, my priority is to stabilize the device and fix bugs like with the broken WiFi driver in the stock kernel, but at least there's a little bit to play around d with ;)
[Pixel C Android Development] Alxoom33:
Thank you, I'll give it a shot :)
[Pixel C Android Development] r_nation:
Has anyone got kali linux or nethunter on their pixel?
[Pixel C Android Development] natezire71:
Anyone tried this with official Android N via factory images? (i.e. flash factory images, flash TWRP, boot into TWRP and flash xceed)
[Pixel C Android Development] a.f.x.:
Would it be sane to flash the individual N factory images (nrd90m) and xceed-v8.02-NPD90G.img over the latest M release with the xceed kernel?

I really don't want to do a full factory reset...

And is xceed-v8.02-NPD90G ok for nrd90m or should we wait for a new xceed kernel?

thx

afx
[Pixel C Android Development] cheep5k8:
I can't guarantee that it will work. It won't break anything, so much I'm sure (but as always, disclaimer!), but it might just not work correctly.

I didn't get around to building for NRD90M yet, actually I'm not yet sure if the right kernel sources are already up on chromeos git. Probably this weekend :)
[Pixel C Android Development] NYCHitman1:
They actually didn't upload source to ChromeOS git. It's on Google's normal Android git.

https://android.googlesource.com/kernel/tegra/+/android-tegra-dragon-3.18-nougat
[Pixel C Android Development] cheep5k8:
Interesting. Thanks for the link.
[Pixel C Android Development] a.f.x.:
Ok, waiting then ;)

thx

afx
[Pixel C Android Development] NYCHitman1:
Yup. They even included allowance for alternative compression algs, so it's not a requirement to use lzma like we have been previously.