yashsingh1/xdaforums huggingface dataset:
[Pixel C Original Android Development] DaConcho:
Awesome I will give that a try.

Thanks!

Edit: so I downloaded a smaller open Gapps and basically any google app installed with the gapps package as a system app works, but anything downloaded from the play store doesn't. So FYI for anyone else who runs into this, you are better off downloading the full stock Open gapps and uninstalling any you don't want.

Sorry [MENTION=2489052]NYCHitman1[/MENTION], hope I am not detracting from the thread. Happy flashing and Stay Dirty!
[Pixel C Original Android Development] NYCHitman1:
It's fine. I'm just not sure why the two of you are having gapps issues.
[Pixel C Original Android Development] Deltalfa:
Sorry for my insistance but after flashing wifi won't turn on! even if i flash vendor!
[Pixel C Original Android Development] NYCHitman1:
WiFi is fine here. You're doing something wrong.
[Pixel C Original Android Development] Deltalfa:
Stucl on a serious problem. Look what i did:

1 wipe all

2 flash official 10v5

3Flashed vendor dragon_mxc89k.img

3 no wifi, 02:00:00:00 Mac address and stuck on searching.

4 Wipe all.

5 Flashed Stock Android Marsh.

6 After booting and starting wizard setup, same thing. Stack on searching.

What can i do for fixing? I do all at the letter!
[Pixel C Original Android Development] NYCHitman1:
Again, for the 1000th time -- K is not the latest vendor. L is. We've said this a few times to you.

Please learn what you're doing to your device prior to modifying it.

This is a development thread, not a place for you to come for tech support.
[Pixel C Original Android Development] NYCHitman1:
I've never had one random reboot. Likely one of your rogue apps causing it.
[Pixel C Original Android Development] setmaster:
There are no rogue apps installed. Here is a more recent Kernel Log:

[ 3563.679882] sdhci: Tuning procedure failed, falling back to fixed sampling clock
[ 3563.679946] mmc1: tuning execution failed
[ 3563.680025] mmc1: cmd error, mask 000a0001
[ 3563.680150] mmcblk0: error -84 sending status command, retrying
[ 3563.688469] mmcblk0: unknown error -5 sending read/write command, card status 0x900
[ 3563.688521] blk_update_request: 39 callbacks suppressed
[ 3563.688552] blk_update_request: I/O error, dev mmcblk0, sector 9739920
[ 3563.688605] blk_update_request: I/O error, dev mmcblk0, sector 9739928
[ 3563.688645] blk_update_request: I/O error, dev mmcblk0, sector 9739936
[ 3563.688682] blk_update_request: I/O error, dev mmcblk0, sector 9739944
[ 3563.688714] blk_update_request: I/O error, dev mmcblk0, sector 9739952
[ 3563.688753] blk_update_request: I/O error, dev mmcblk0, sector 9739960
[ 3563.688791] blk_update_request: I/O error, dev mmcblk0, sector 9739968
[ 3563.688825] blk_update_request: I/O error, dev mmcblk0, sector 9739976
[ 3563.688855] blk_update_request: I/O error, dev mmcblk0, sector 9739984
[ 3563.688952] Aborting journal on device mmcblk0p7-8.

Is my newly device broken?
[Pixel C Original Android Development] NYCHitman1:
Uncertain. What I/O scheduler are you using?
[Pixel C Original Android Development] setmaster:
I did not change anything kernel related, nor have any kernel tuning app installed, so i would guess, the default io scheduler. Im now trying xceed kernel and will have a 24 hour try and look for reboots.
[Pixel C Original Android Development] NYCHitman1:
I'll look into it, but like I said -- I've never had not even one RR.
[Pixel C Original Android Development] redukt:
Can confirm - never had some random reboots.
[Pixel C Original Android Development] DaConcho:
I have had random reboots on stock and on Dirty Unicorns. Found this a while ago: http://www.androidpolice.com/2016/0...reboots-on-the-pixel-c-is-an-rma-replacement/

It hasn't been such an issue that I am prepared to swap out my perfect condition one for a refurb, but I might have to do that before the one year warranty is up. Dirty Unicorns has never caused a random reboot on any other device I have owned, so inclined to think its my device.
[Pixel C Original Android Development] NYCHitman1:
That sucks. I had no idea this was an issue on some units.
[Pixel C Original Android Development] DaConcho:
Ya... I think thats what I get for ordering one of the first ones and not waiting for any issues to get ironed out.
[Pixel C Original Android Development] Mazda:
As many of you guys know Android N is rolling out. It probably won't be long til we get a hold of source and we begin the new cycle again.

We've gone ahead and given our users some insight on what we're planning to do moving forward.

If you guys care to read it, check it out here

https://plus.google.com/+AlexCruz/posts/cbsB4LJxPxM

#StayDirty
[Pixel C Original Android Development] Istvan_86:
Hello!!,

I updated to latest stable version (2016-08-05) and when I boot the ROM says that I must update system image. As you said in the above post I must reboot to recovery and flash vendor L image and reboot? Or after flash L image I should flash ROM again.

Another question that I have is about GAPPS, can I flash TR-GAPPS over Banks-GAPPS and viceversa?

Thanks in advance.
[Pixel C Original Android Development] NYCHitman1:
I had indicated previously that I forgot to update the build fingerprint to match the vendor.img fingerprint, so the warning will appear -- however, you can disregard it. If you use the latest weekly build -- you'll have no issues with that.

And no, I do not recommend flashing different gapps packages over one another.
[Pixel C Original Android Development] Istvan_86:
As usual really thanks for your fast answer, I update to WEEKLY build when I arrive at home to avoid the vendor.img message.

Cheers. :D
[Pixel C Original Android Development] Istvan_86:
Hi again.

I updated to the lastest weekly build (20160819) and the "vendor image maybe out of date" still appears. I´m doing something wrong?

Thanks in advance.
[Pixel C Original Android Development] NYCHitman1:
If you updated and you're still getting the message -- you aren't on the correct vendor.img. You want to be on MXC89L. To avoid issues, download the file from the OP and flash it in recovery.
[Pixel C Original Android Development] Istvan_86:
Ok. I always download all the OP files, so I have it. I just need to reboot to recovery and flash MXC89L and boot to the weekly build as usual right?

Thanks again mate.
[Pixel C Original Android Development] NYCHitman1:
Yup.
[Pixel C Original Android Development] Istvan_86:
I go to follow your steps now and I see that the OP file is a img file, if I´m not wrong I msut use fastboot to flash a img file right?
[Pixel C Original Android Development] NYCHitman1:
No. Vendor images can be flashed in recovery. Download the file > reboot to recovery > click Install > change type to Image > select the image you downloaded > select Vendor Image (as for the partition you're flashing to) > swipe to flash > reboot system.

Make sure you're using the 3.0.2-21 version by [MENTION=5480152]followmsi[/MENTION]
[Pixel C Original Android Development] Istvan_86:
Really thanks!!!! Works like a charm.

---------- Post added at 01:52 AM ---------- Previous post was at 01:34 AM ----------

I forgot to say that I decide to perform a clean flash after see that all goes ok and I install Banks GAPPS, I can´t log in to gmail app, it says that this account already exists but I Have full acces to play store. What can be the problem now?
[Pixel C Original Android Development] NYCHitman1:
Uncertain. Clear data of the gmail app and try again. I use my TR gapps w/o issue.
[Pixel C Original Android Development] setmaster:
I just want to inform, that i had no random reboots anymore since i use xceed kernel.

Gesendet von meinem Nexus 5 mit Tapatalk
[Pixel C Original Android Development] Istvan_86:
I always use your TR, but after this clean install (few days ago I was doind some tests with Xposed and because of that I decide to do a clean flash) I use Banks instead of TR and the problem with gmail appears.

I´ll try to clear data and post here the results.

Thanks again for all your time.
[Pixel C Original Android Development] Istvan_86:
Ok, I did a clean flash again in order to install TR gapps the issue is gone but now my PC doesn´t detect the Pixel for MTP. What can be the problem now?

Thanks in advance.
[Pixel C Original Android Development] NYCHitman1:
Just go to developer settings and flip the option to MTP manually.
[Pixel C Original Android Development] Istvan_86:
I can´t enable it.... When I click on MTP option the menu closes and charge remains selected. Strange....

EDIT: Also google keep FC when i open it.
[Pixel C Original Android Development] NYCHitman1:
This was a clean flash? Never had this happen to me.
[Pixel C Original Android Development] Istvan_86:
Yeah.. Now I restore a backup and tomorrow try to do all the process again.

My backup is from the build of 10th of june and MTP doesn´t work..... I´m totally disturbed and can´t udnerstand why this is happening to MTP. USB OTG works fine.
[Pixel C Original Android Development] NYCHitman1:
Might be your USB-C cable.

As I said, I don't have this problem.
[Pixel C Original Android Development] Istvan_86:
I use this cable since I buy the Pixel it´s an Orzly usb 3.0 type-C, MTP doesn´t work but the Pixel start to charge.
[Pixel C Original Android Development] NYCHitman1:
Is this a Windows unit or?
[Pixel C Original Android Development] DaConcho:
Go into developer settings and flip the option for ADB debugging, then turn it back on again. This happens to me after a clean flash for whatever reason, but that should fix it and you will get mtp and file transfer again.
[Pixel C Original Android Development] Istvan_86:
Sorry for the delay answering you a very busy weekend.

I use Windows 10 x64, I made about 4 or 5 clean flash with different versions (the last time that I use MTP was in Win 7 x64, I need some special driver), now my wifi also doesn´t work, it turns on but can´t detect any wifi network.... This combined with the MTP made my Pixel nearly a brick for me. I don´t know what can be happen, can I provide some kind of log or similar?

Thanks in advance.

---------- Post added at 10:16 AM ---------- Previous post was at 10:16 AM ----------

Hello,

I´m at the office right now I try it when I come to my home and told you if it works for me.

Really thanks.
[Pixel C Original Android Development] Istvan_86:
Hello guys sorry for the delay in my response, I have an intense weekend and a very hard start of the week in the office before holidays,

I did an insane amount of tests with Pixel C and different kind of GAPPS, stables and weeklies. I try to resume it:

1-The fix that DaConcho offer to me work flawlessly for my MTP problems.

2-I try to clean flash the 2 latest weeklies (20160819 and 20160826) doing all the possible combinations between them and latest Banks GAPPS or DU ThemeReady GAPPS.

3-After step 2, Google keep crashes in every combination of ROM + GAPPS (Google Keep is a essential part of my work, no chances of not have a perfectly functional Google Keep app on my tablet)

4-I restore an older backup from the build 20160610 (in that backup my google keep works without any kind of problems) and update it to latest weekly and nearly all problems seems to be gone.

5-I detect some minor but annoying issues:

*YouTube Force Closes sometimes. After that it opens normally.

*When I try to add new shortcuts to Quick Settings, System UI Force Closes. (This is a very important feature for me, but I can survive without it)

*Can´t use a custom image for Profile Info under Users option.

I start my holidays tomorrow and at least I have all that I need working fine in my Pixel, but I can´t understand how I have this insane amount of problems.

Again really really thanks to all the people that help with my problems :D

EDIT.: If I find more extrange problems or FC I post it here.
[Pixel C Original Android Development] NYCHitman1:
Gotta be honest.. work here is done and I can't duplicate your issues. Thus, nothing will be done.
[Pixel C Original Android Development] DaConcho:
Ivstan,

As we mentioned in this forum a few users have issues with the gapps package. Really weird, but can't be reproduced by NYC hitman so not much can be done, he can't fix a problem if he can't find a problem.

You will need to flash Open Gapps to fix the issue. Make sure you do either the full or the stock package as any google app downloaded from the play store won't work, has to be included in the gapps package.

Remember, google is your friend. Read and search this thread if you have any other issues 99% of the time the answers are out there, the 1% of the time its user error haha.

Also - changing the quick settings force closes... go to the page to edit the quick settings, select the 3 dots at the top and hit reset. After that it will work. Just needs to be cleared first.
[Pixel C Original Android Development] NYCHitman1:
Final Marshmallow build is now available in the OP. Enjoy!

This thread will now be closed until we're ready for the eventual DU11 release. See ya!
[Pixel C Original Android Development] Clark Joseph Kent:
Thread Opened as per OP's request, thank you.
[Pixel C Original Android Development] NYCHitman1:
New build in the OP. Enjoy everyone!!
[Pixel C Original Android Development] Alxoom33:
Build has been running great for a few days.
[Pixel C Original Android Development] golf60:
Great news....

Do you have a changelog?

Thanks a lot
[Pixel C Original Android Development] NYCHitman1:
Changelog:

- First Q build lol

There you go!
[Pixel C Original Android Development] Alxoom33:
Have you updated it to A11? Lol!
[Pixel C Original Android Development] NYCHitman1:
Nah, I think next build will probably be the end of the line for the ol' Dragon.
[Pixel C Original Android Development] Alxoom33:
EOL! It has to come sometime. But I have been enjoying this DU build.

BTW, can you provide me a zip with your kernal? I wanted to try [MENTION=5480152]followmsi[/MENTION] 's new kernel, but I don't want to try it without a safety net in case it makes the tablet bootloop. Thanks,

Alan
[Pixel C Original Android Development] NYCHitman1:
I'll post it in here this weekend once I post the final build
[Pixel C Original Android Development] Alxoom33:
Thank you!
[Pixel C Original Android Development] NYCHitman1:
Final Dragon build is in the OP.

Kernel [MENTION=4100646]Alxoom33[/MENTION]: https://bit.ly/3hrAQ9o
[Pixel C Original Android Development] Alxoom33:
Thanks [MENTION=2489052]NYCHitman1[/MENTION]
[Pixel C Original Android Development] heyChristo:
[MENTION=2489052]NYCHitman1[/MENTION] Awesome Job! Thanks, One of these bad boyz just arrived to my door fresh off ebay and seemingly in mint condition. First damned thing I did was unlock, twrp, and flash this before I even got it on wifi. First boot and customizing and super excited about getting this bad boy online in a quick minute!

(I misss G+) :(
[Pixel C Original Android Development] heyChristo:
Is there a trick to get Magisk working with this one? I keep getting an error saying:

! Unsupported Image format

! Installation failed

10-7-20 Update: Tried flashing and pushing boot.img per instructions on John Wu's magisk page and although boot.img flashes still no root.

10-9-20 Update: Sometimes I am my own worst enemy. After tinkering for hours I realized that its the latest update of magisk that breaks the system. It probably worked for a few minutes before I did the update and broke root. Magisk 20.4 works just fine as does Magisk Manager 8.02. Updating Magisk to 21 however will break the root and you will have a hell of a time trying to get it back. I had to wipe data and start over again. Only reason I am posting this here is because I couldn't find what I did wrong in any posts. Obviously because the new magisk was just pushed out over the past 48 hours. There is no need however to flash the boot image injected with magisk. A simple twrp flash will work.
[Pixel C Original Android Development] Alxoom33:
.

Hey man! Still like to flash your build once in a while to see how it's running. But I see it's offline. Would you consider keeping it up a little longer or available to dl from another repository. Thanks,
[Pixel C Original Android Development] heyChristo:
I hope there not an issue. This Rom is awesome. Haven't experienced any issues. Everything I have tried works. I can host a link of necessary.
[Pixel C Original Android Development] NYCHitman1:
Oh, damn. I must've done that accidentally.
[Pixel C Original Android Development] NYCHitman1:
Yeah, throw up a link so I can DL it. I must've accidentally deleted it while I was doing some maintenance on my server.
[Pixel C Original Android Development] heyChristo:
[MENTION=2489052]NYCHitman1[/MENTION] Here ya go! Let me know and I can take down the link afterwards or leave it up, whichever you prefer.

File link in OP.
[Pixel C Original Android Development] Alxoom33:
Thanks [emoji106]
[Pixel C Original Android Development] NYCHitman1:
You can take it down now. Thank you for sharing it again. I have put the build back on my server and the same link from the OP targets it again.
[Pixel C Original Android Development] heyChristo:
Done.
[Pixel C Original Android Development] jin878404951:
About "UC Browser" crash

Is there a way to make "UC Browser" run normally.I really like this rom. But "UC Browser" it's very important to me. I like to use "UC Browser" to watch TV,double speed function is very good. I'm talking about “China version UC Browser”. “UC 浏览器”

PixelExperience_dragon-10.0-20200814-1616-UNOFFICIAL，this rom have the same problem. Can you solve this problem？

My English is very poor ，Sorry. I just use google translate.

Thank you very much for your "rom"：笑：
[Pixel C Original Android Development] NYCHitman1:
I am no longer putting out releases for this device. It is now EOL for me.
[Pixel C Original Android Development] NYCHitman1:
You don't need to wipe Internal, so you can just load everything up via MTP while in system. As stated previously, flashing instructions are in the OP.

To answer your #6 -- we don't install recovery, so that's not going to be an issue -- and yes, the build is rooted.
[Pixel C Original Android Development] Digitalpants:
I currently have a issue and no idea how to continue. I followed the instructions like you posted and flashed rom-gpapps, but whenever i try to boot into system it just sends me to recovery. I then proceeded to just extract the boot.img from the the install zip and flash it. It boots just fine after that. The part where i am stuck at is that it does not install supersu, i tried to manually flash/install it and then we are right back at square 1 where it only boots into recovery.

I am currently running the 3.0.2.0 TWRP you posted, and i am pretty sure i followed all the instructions correctly from your post.
[Pixel C Original Android Development] oRAirwolf:
I am having a hell of a time with this.

Here is what I am doing:

Restore tablet to MXC89F factory image using flash-all command for totally fresh install.

Put ROM files in /sdcard/ROMs using Windows

Boot into bootloader

Flash TWRP 3.0.2_0 from the link you provided in the unlock guide

Boot into Recovery

Go to Install - Does not show any folders in /sdcard

Go to Wipe > Advanced > Check all

Go to Advanced > ADB Sideload > Enable

Sideload ROM and GAPPs via ADB

Reboot

Boots back into Recovery

What am I doing wrong?
[Pixel C Original Android Development] ilpolpi65:
Don't wipe internal storage
[Pixel C Original Android Development] Digitalpants:
I was having the same issue as you are. What i ended up doing what just installing TWRP 3.0.0-0 cheep posted then proceeding to install the rom, and gapps. This should get you booted up and for the most part working. I still had the issue where SU was not installed so i manually pushed su to /data and manually installed superuser.apk which seems to have fixed everything. So far everything is running just fine, but still doing more testing to see if there are any issues i have not caught.

Still worth prob waiting for a reply from NYChitman1 since he will have a more direct solution.
[Pixel C Original Android Development] oRAirwolf:
Were you able to flash the files from the local storage or did you have to sideload? If local, what folder did you put them in?
[Pixel C Original Android Development] Digitalpants:
I was able to flash from local storage, default directory /sdcard. Like the poster above you said, you might have deleted internal and deleted both rom/gapps.
[Pixel C Original Android Development] dkryder:
used to be the first trip into twrp you had to format data so twrp could get rid of encryption and be able to read /data partition. is that still necessary? if so does that get rid of internal storage?
[Pixel C Original Android Development] redukt:
For recovery bootloops please try to reboot in bootloader and type "fastboot reboot".
[Pixel C Original Android Development] SonySteve:
Here are some recaps after finally flashed the DU successfully. (Coming from rooted XCeeD kernel)

1. Boot into TWRP recovery 3.0.2.0?

3. Using TWRP wipe -> advanced wipe -> system/data/cache/dalvik (internal storage can be left unchecked)

4. After wipe finish, return to TWRP main menu without reboot.

5. Enter install feature of TWRP, and I installed fellow downloaded zip files in sequence without reboot.

DU_dragon_6.0.1_20160505-0106.v10.2-OFFICIAL.zip

DU_ThemeReady_4-28-16.zip

6. After all zip have been installed successfully, return to TWRP main menu

7. Reboot->System

then everything come to live (regular new system start up and all).

System running as rooted with SuperSU enabled already.

(My only previous 3rd party ROM experience was CM)

So far everything runs smoothly without all the pre-installed junks (use up less internal space for system)

But I do encounter with the asking for updated vendor.img message everytime I reboot the system.

Upon trying to flash (under fastboot mode via fastboot commands) the provided vendor.img file I did encounter the fallowing error.

target reported max download size of 268435456 bytes

erasing 'vendor'...

FAILED (remote: unsupported command)

finished. total time: 0.004s

Would be greatly appreciated if can point me in the right direction to resolve that error.

(and I read that few of the guys lost all the internal data (the ROM zip files) during wipe, thus unable to run installation later in TWRP.)

(upon my minglings that happened to me once, I had to run adb "push" commands to copy files back into the device)

Hope my experience above can help others to get DU up and running smoothly there!!

and great job with DU there!! looking forward to enjoy the benefits of all the tweaks and so on!! thanks!!
[Pixel C Original Android Development] redukt:
Pls try to reinstall right drivers or another USB port. It's a typical error message for wrong setup.

Btw - why did you flash two several gapps packages?

Alternative you can try to fix fastboot in TWRP options
[Pixel C Original Android Development] SonySteve:
All rightie, will attempt few more times then.

I wasn't quite sure wether to install both or choose one. Guess I only need one. (will modify my notes then)
[Pixel C Original Android Development] redukt:
Hope for maximum success ;)

It´s not really tricky ;)
[Pixel C Original Android Development] streilu:
Got it up and running, but no way to get MTP to work. It's just charging when I plug it to my PC. Tried MTP Enabler App, but no luck... Is there any hidden setting for USB connection?
[Pixel C Original Android Development] NYCHitman1:
In TWRP, run the fix fastboot cap action.
[Pixel C Original Android Development] NYCHitman1:
I've used MTP countless times to transfer movies w/o issue.
[Pixel C Original Android Development] regime2008:
Love the Rom! I have been running DU since the Samsung note 2, up until my nexus 6, and have been more than happy with it. Out of curiosity, is there any way to reposition the navigation buttons, like how it is for stock Rom? (Back and home button on the left, and recent button on the far right). Thanks for the awesome development!