yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] johnbravado:
I see there is the additional file 7.1.2 AOSP where or what is that in the install? everything i have is formatted to ext4. Maybe there is something in that thing i need to have also installed but idont quite know what it is or what i am installing with it.

Also is there a way to only install the pico variant of GApps. i know the file you have is full stock with newspaper and stuff i dont want. it doesnt bother me that much as i got plenty of system app space i cant change anyways and i can disable them. but if i could do something as imple as comment out a line somewhere and it will only install pico that would be awesome
[Pixel C Android Development] followmsi:
Nothing to install except the ROM, vendor.img, opengapps and magisk/supersu at the end.

In my example config file I have activated a few apps only ..

Just uncomment the PICO section only.

Pls read this article to understand opengapps config file.

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

Good luck !
[Pixel C Android Development] johnbravado:
Just in case someone else has issue. When I updated the TWRP to the Android Only version it reset settings to default. 1 of the settings is something about use -r RM instead of format or something. Anyways it has always been checked in all my TWRP and it wasn't this time. Don't know if that was issue but booted right up no problems after clean install and checking that setting
[Pixel C Android Development] 12paq:
Android 8.0.0 rooted with Magisk is running great here. Passed all checks and even got Substratum to half work.

Thanks for your continued time and efforts deving for the Pixel C!
[Pixel C Android Development] Reuben_skelz92:
Does Netflix work?
[Pixel C Android Development] 12paq:
Yes, tested with FollowMsi's O kernel and Magisk installed and SafteyChecks passed, Netflix works.
[Pixel C Android Development] Reuben_skelz92:
Tbats cool. Didnt work for me on the lineage O build so gonna try this:)
[Pixel C Android Development] followmsi:
Not expected anymore .. but the September release has been arrived ..

AOSP_8.0.0_r7_OPR1.170623.026_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.0.0_r7 - Sep 2017

- tegra-3.18_kernel_dragon_v170914_unicorn-xceed-followmsi-o

You will find fresh open gapps Oreo packages inside the download folder too.

Enjoy .. :p
[Pixel C Android Development] GonzoKSV:
Having force closes of gplay services everytime (Oreo). Format data wasnt the solution. Came from Lineage 14 and made everything as suggested. Hmm...

Gesendet von meinem HTC U11 mit Tapatalk
[Pixel C Android Development] bbubelis:
Has anyone gotten V4A to install? If so, which version? Rooted with Majisk 14.0.

Thanks in advance
[Pixel C Android Development] Dressiel:
[MENTION=5480152]followmsi[/MENTION]

Bad news Buddy. Was tryin to update from r12 to r28 (AOSP 7.1.2) on twrp 3.1.1.0

In recovery i flashed the new update...."install complete"...after that i couldnt return via UI to flash vendor>superSU. so i powered off and could Boot normally. Going back in recovery and flashed the vendor_N2G48C_2017-08.img ...again stucked at ui after flash completed...powered off and tryed to boot into recovery, i See the 30sec Bootloader and after that i hear the beep and for just a split second maybe a android bot picture..

Now i cant Boot the device nor into recovery

Any hints ?
[Pixel C Android Development] followmsi:
Try to install gapps again .. on top of your current installation.

Wipe cache/dalvik and reboot.
[Pixel C Android Development] followmsi:
Just start from scratch .. recovery is gone - just flash twrp via fastboot again.

Boot into TWRP

Wipe system only

Install ROM of your choice.

EDIT: install vendor.img

Install gapps

Install supersu

Wipe cache/dalvik only

Reboot into system

Cheers
[Pixel C Android Development] Dressiel:
Jepp could wake up the device and Boot into Android ....quickly turned developer Option on and USB debugging ...Problem is. My win10 machine recognised the device (sound bleep) but i could not communicate via fastboot ...no response -.- driver check?

---------- Post added at 06:49 PM ---------- Previous post was at 06:00 PM ----------

@followmsi

Im stuck and out of ideas.

Fastboot is working again (need to set driver manually). I can flash twrp . but if i reboot into recovery via Hardware buttons or via fastboot ...black screen after Google Logo

Tryed twrp from official source (3.1.1.1) and your files from Google Drive ...my last attempt was with the exact file i had installed (3.1.1.0)

So, what happened here ?
[Pixel C Android Development] followmsi:
As you are still on Nougat go with 3.1.1.0 first .. to prevent any unknown issues.

For Oreo use 3.1.1.1.

It's not possible to boot into recovery via fastboot.

You have to use hardware keys and enter boot menu and choose recovery from there.

You may start to flash recovery again ..

If this is not working ..

Revert to stock ROM and start from scratch ..

Cheers
[Pixel C Android Development] 12paq:
If you have not already, you also have to use the latest 8.0 gapps in followmsi's Drive folder.
[Pixel C Android Development] Dressiel:
Jepp, i flashed again twrp 3.1.1.0 (exact file like previously installed)...via fastboot reboot back in Android...shut the pixel c off...turned it on with volume down + Power and choosed reboot into Android recovery....again black screen -.-

So again what happened , that the twrp suddenly didnt work anymore ? And how can i Start from Scratch and revert to Stock ROM without twrp ?
[Pixel C Android Development] bbubelis:
Latest 8.0 version gone from Drive folder
[Pixel C Android Development] JerrellWong:
hi bro, I flashed this, booted up fine, when I launched the camera though, it hangs there and when I go ahead to reboot, it boot loops.

---------- Post added at 08:35 AM ---------- Previous post was at 08:33 AM ----------

flash the stock images, https://dl.google.com/dl/android/aosp/ryu-opr1.170623.026-factory-e27ff2c8.zip
[Pixel C Android Development] Dressiel:
How can i flash without twrp ?
[Pixel C Android Development] GonzoKSV:
Thanks a lot for your help. I think I'm going to check it in the afternoon. Tried 7.12 now because I wasn't satisfied with Lineage. But I still like to get Oreo working :)

There only was no selection except Pico or stock. I have tried both from middle September (9.14 I think).

Gesendet von meinem HTC U11 mit Tapatalk
[Pixel C Android Development] JerrellWong:
run it via cmd/ terminal. run the flashall.sh bat file inside
[Pixel C Android Development] followmsi:
Pls use "fastboot" to flash stock images .. via usb cable connection.

Since September release there are "strange" issues .. try to exlcude "unified" kernel as root cause.

Pls have a look here ..

https://xdaforums.com/showpost.php?p=73836325&postcount=588

Cheers
[Pixel C Android Development] GonzoKSV:
Are there any experiences with dirty flashing 8 over 7.12?

Gesendet von meinem HTC U11 mit Tapatalk
[Pixel C Android Development] 12paq:
No. And it is never recommended for major os versions.
[Pixel C Android Development] GonzoKSV:
Didn't worked :(

I try to download gapps and Oreo once again to make sure there was no Download Problem.

Gesendet von meinem HTC U11 mit Tapatalk
[Pixel C Android Development] followmsi:
If you come from official lineageos and you want to keep your data partition you need to convert keys.

You may try with factory reset first and may restore backup later on.

Did you format system for the upgrade from lineage 14 to AOSP Oreo ?

Normally no issues with gapps on Oreo ..
[Pixel C Android Development] Dressiel:
Sry for the late reply !

So yeah i started from scratch , flashed the Stock ROM via fastboot . flashall.bat ! After that i tryed to flash twrp as always. BUT whenever i want to boot into twrp (hardware button) i see a robot with the text "no command".

Here is the trick-->flash twrp via "fastboot flash recovery twrp.img" ! After that, as always "fastboot reboot"...in this 30sec Bootloader timeframe you need to force into twrp via hardware buttons! (dont let it boot into Android!)

thats it, i saw the twrp splash screen and thought: "thanks god its finally working -.-". Anyway i decided to go with the LineageOS 14.1 and im happy af (LineageOS 15 seems buggy for me, couldnt install frdoid ;( ) [MENTION=5480152]followmsi[/MENTION] , [MENTION=7069651]JerrellWong[/MENTION] Thank you guys [MENTION=4845115]GonzoKSV[/MENTION] Willkommen Landsmann
[Pixel C Android Development] JerrellWong:
Good that you got it working , but btw the reason u didn't boot into TWRP is because that's the wrong command . You should've typed fastboot boot "recovery name ".img
[Pixel C Android Development] Dressiel:
Interesting, every Guide said "fastboot reboot"....lesson learned, thx for the hint
[Pixel C Android Development] GonzoKSV:
Ein gepflegtes Moin vom nordhessischen Frühstückstisch :D

I decided to format data partition before flashing AOSP because a had had some trouble in the past after I didn't do - no matter what device. So Data was completely clean.

Well, 7.12 runs well - that's strange. I did a factory reset and wipe system, too. No problems, all goes well. TWRP is 3.1.1-1. When I restore I have an issue according the password. I have seen it on another thread but forgot where it was.

Well, today I'm going to try once more Oreo with a fresh download. I'm excited ;)

Btw Software Keyboard has got force closes, too when I'm trying to get to the Numbers screen. Need the Hardware Keyboard for signs.

UPDATE: Installed r1 + vendor from scratch, copied configuration from phone. Well, logged in into Google but still force closes. Then updated to r7 + vendor, google and magisk 14 on top, wiped cache and dalvik. No success. I'm going to begin to hate Oreo. But it's only the Google app now and not the services. I hope the rest is working now.

Gesendet von meinem HTC U11 mit Tapatalk
[Pixel C Android Development] followmsi:
The upgrade from r1 to r7 is not required at all.

If you have problems on r1 then you have them in r7 too.

What gapps package are you installing ? Try to use the same setup you used on Nougat.

You do "format" system before installation of r7 and new gapps ?

You can even keep your old 7.1.2 data partition to keep all your settings.

Just wipe cache and davlik.

Pls have another try .. as well I recommend to use "android-o" kernel from September 14th.

Also in download folder .. install as very last step .. after magisk.

Cheers
[Pixel C Android Development] GonzoKSV:
Made everything like I had done before but didn't wiped data. I think installing the kernel after magisk was the solution for the problem. Now everything seems to be alright, no force closes in the beginning. I'm excited :) Thanks a lot, man!

Gesendet von meinem HTC U11 mit Tapatalk
[Pixel C Android Development] followmsi:
Another month ..

AOSP_8.0.0_r13_OPR1.170623.027_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.0.0_r13 - Oct 2017

- tegra-3.18_kernel_dragon_v171003_android-o_followmsi

You will find fresh open gapps Oreo packages inside the download folder too.

Enjoy .. :p
[Pixel C Android Development] revengers:
r13 working fine here, thanks for the good work :o

---------- Post added at 06:18 PM ---------- Previous post was at 06:15 PM ----------

I was wondering if we still have complaints about wifi connectivity/performance issues

:cool:
[Pixel C Android Development] followmsi:
Thanks .. running r13 too .. smooth.

No infos about wifi complains anymore.

For me it works ok.
[Pixel C Android Development] raz123:
Couldn't find it :(
[Pixel C Android Development] followmsi:
All unofficial versions have been removed from gdrive .. it's official now ;)

http://opengapps.org

Cheers
[Pixel C Android Development] Peterpaulmarie:
Android 8.1.0 (OPP5.170921.005) is out.

I'm actually on official 8.1.0 and it works fine, but I plan to flash your ROM?
[Pixel C Android Development] followmsi:
Yes, it's Android 8.1 Developer Preview.

The sources should arrive beginning of December.

Cheers
[Pixel C Android Development] followmsi:
Thanks for the update .. for next monthly release we will use webview BETA 62 .. seems to solve the issue.

For now you have to install chrome .. like you did.

Or you install webview beta 62 only.

Cheers
[Pixel C Android Development] LSS4181:
It seems AOSP or Oreo is having issues with the power delivery capable USB hub with RJ45 port. Sometimes it defaults to Charging rather than RNDIS, and I need to manually switch it to RNDIS under the Developer's Options, and it takes effect preferrably after reboot.

Additionally, though I haven't paired a bluetooth headset yet, I could not change the default codec. It's always SBC. I intend to pair my aptX-capable headset in order to remove the dreaded ~500ms audible latency when playing games and such with bluetooth headsets.
[Pixel C Android Development] followmsi:
You have this RNDIS issue since Oreo ?

Nougat was working fine ?

Did you test stock Oreo images too ?

Will be a tricky one .. no test device, no logs .. etc.

Aptx libs are not part of the system .. licensing stuff.

https://www.xda-developers.com/goog...upport-for-aptx-on-the-nexus-5x-and-nexus-6p/

As I know Pixel C does not have the libs either ..

There are some zip package on XDA including the missing libs .. seems to work.

https://xdaforums.com/showpost.php?p=72693862&postcount=42
[Pixel C Android Development] LSS4181:
Apparently I was on RR 5.8.4 (Nougat) when I got the hub and before I flashed AOSP Oreo, and the hub worked without issues there including ethernet (RNDIS).

It doesn't appear to be the Developer Options thing... so it's possible something is blocking the ethernet functionality as I was able to briefly see the Ethernet icon when I rebooted. But if the ethernet is detected and enabled the moment the tablet booted it'll be fine... so I might need to look into it more. It's not a major issue, though.

As for aptX... well, it's possible that we'll have to add those libs externally before using for licensing concerns... and this holds true for many devices.
[Pixel C Android Development] revengers:
If I may chime in, I am on r13 with working LAN through a USB-C/OTG adapter and a generic (cheapo) USB Gigabit hub with RJ45 port; zero problem here:cool:
[Pixel C Android Development] followmsi:
You may try another kernel for testing ...

https://xdaforums.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
[Pixel C Android Development] LSS4181:
I was already on that kernel...

Guess it's also a UI bug... I tried plugging it after boot... the ethernet icon did not show up, but this time the ethernet functioned properly... From what I could remember, at times the IP was indeed not available, but in any case, the moment I pressed Restart in the Power Menu, the ethernet icon can be briefly seen before actual reboot. If I keep it plugged while booting, the ethernet icon will be visible.

Not anything major at present as I'm more looking forward to an official LOS 15 or similar ROMs. After all, there indeed are some good improvements in Oreo compared to Nougat.
[Pixel C Android Development] followmsi:
November 2017 ..

AOSP_8.0.0_r28_OPR1.170623.032_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.0.0_r28 - Nov 2017

- Latest kernel changes -> tegra-3.18_kernel_dragon_v171107_android-o_followmsi

- Added Webview 62 to fix OpenGapps installations without webview or chrome.

Pls download official OpenGapps package for Oreo ..

Tested with Magisk 14.0 and fresh gapps from today.

Enjoy .. :p
[Pixel C Android Development] jimzenn:
This is an awesome room. I have used for about 2 weeks now and it's completely bug free and butter smooth.
[Pixel C Android Development] theborkz:
Encrypted

Tried a clean flash of this ROM following the directions with opengapps and magisk on latest TWRP and now im stuck not being able to boot and TWRP tells me i need to decrypt my files so I cant even access my backups on the /sdcard.

I've tried any info I can find so far including TWRP decrypt with default_password and the code for my pattern from my previous rom.

Im at a loss here for whats going on, any suggestions? Thanks
[Pixel C Android Development] followmsi:
You was encrypted before ?

You said clean flash ? .. wiped data via TWRP or via factory reset on previous ROM ?

Twrp were able to access encrypted data partition before ?

This ROM has no forced encryption anyway.

Default FDE encryption is working in latest TWRP.

If you flash back stock ROM are you able to access internal storage ?

You may screwed up your encryption .. worst case you need to "format" data.

Once formatted install magisk 14.3 directly after ROM installation, gapps afterwards.

Clean cache and dalvik and reboot.
[Pixel C Android Development] MrPhilo:
Any reason to use this over Google Stock ROM? I just got myself a Pixel C (again, after 2 years) for an amazing price!
[Pixel C Android Development] 12paq:
This ROM has no forced encryption, the boot image is ready for root and magisk and the dev updates it frequently and reliably. The dev is also nice and answers most of our dumb questions.
[Pixel C Android Development] MrPhilo:
I'm getting Google Service force close at setup, I have done a full wipe and flashed 4 different open gapps (nano, pico) on each clean install with same error

I am using R28 Oreo. I have tried all the suggested fix in search but no avail

Anyone got a solution?
[Pixel C Android Development] followmsi:
You need to install chrome via opengapps.. either install a package with chrome included or use config file for opengapps.

The included webview from last release seems not to solve this issue entirely .. some reports of "good" and "bad" installations.

Same problem on other AOSP ROMs too.

I guess there will be a fix soon .. but the "chrome workaround" is working.
[Pixel C Android Development] brackenhill_mob:
Thanks for this - I had the exact same problem.

Rather than re-install the stock or full version of opengapps, I just downloaded Chrome from the Play Store having originally installed nano - worked perfectly.
[Pixel C Android Development] theborkz:
I was looking at the fstab in the root and it seems to mount the partitions f2s with some weird encryption thing pointing to something on one of the mounts. Maybe I have to mess around with the bootloader or boot.img and custom kernel

It mounts the partitions with soimething like this "wait,check,forceencrypt=/dev/block/platform/700b0600.sdhci/by-name/MD1". I'll try and post the fstab tomorrow.
[Pixel C Android Development] followmsi:
Are you using Nougat ROM ?

You can use "mount" command to see actual used filesystem for your partitions.

https://github.com/followmsi/android_device_google_dragon/blob/aosp-oreo/fstab.dragon

F2FS has been removed for Oreo.

In case you still have F2FS partitions you need to switch back to ext4 for Oreo .. just use TWRP to switch.

You will need to format the partition to change filesystem.

If you flash boot.img you overwrite all old settings. (Ramdisk and kernel binary)

Format system, cache and data as ext4, reflash ROM , install root, install gapps and reboot.

Normally F2FS backups which are restored onto ext4 are working fine.

Good luck !
[Pixel C Android Development] EvansJD:
I saw one post saying Substratum was half working for them.

Should it work?

I've installed it and applied themes but nothing seems to change
[Pixel C Android Development] ladehunter:
HI, followmsi.

Thanks a lot for your work.

I pull your local_manifest folder and put it into .repo like your guide. When i sideload my otapackage in TWRP, I got an error 7. I try to use the update-binary in your zip instead, it worked. I just want to ask you how can I build a correct otapackage so i don't need to change the update-binary every time.

look forward to your kind advice.
[Pixel C Android Development] followmsi:
This one is removing the OTA checks from OTA file.

github.com/followmsi/platform_build/commit/9937b92420e8ce4ad8ffef84ae7c0f60098a5825

The device check is currently not working on Oreo .. either this related to Nougat based TWRP or needs to be fixed in update-binary sources.

Made already an Oreo based TWRP for testing .. TWRP itself works fine but BusyBox has still problems on Oreo.

This "device check" problem exists on several devices .e.g. TWRP versions.

To bypass this check while building you need to remove this line manually ..

https://github.com/followmsi/platfo...ls/releasetools/ota_from_target_files.py#L201

Cheers
[Pixel C Android Development] Smala777:
4. Install current stock vendor.img (flash via TWRP) .... Where I can find it?
[Pixel C Android Development] followmsi:
It's coming from stock factory image of the current month .. you can find a copy inside the gdrive folder too.

Flash via TWRP.

Cheers
[Pixel C Android Development] Smala777:
hi, install your ROM

AOSP_8.0.0_r28_OPR1.170623.032_dragon-ota-eng.followmsi

vendor_ryu-opr1.170623.032_Nov-2017

Magisk-v13.3-pixel-c

But Google play services dont work.

When launching the market mark, the inscription "Verification" and the load slider load continuously. What I did not do?
[Pixel C Android Development] followmsi:
Pls use latest Magisk .. 13.3 was a special version at this time.

Just use 14.5 beta.

Opengapps somehow not recognize the installed webview version.

In this case you need to install chrome via opengapps.

You can use gapps config file and stock package for this purpose.

Will check if we can improve this issue for next release ..
[Pixel C Android Development] Smala777:
What do I need to do to make Google services work?

I need to download the stock version, install it and all?

Do you need to do something extra?
[Pixel C Android Development] followmsi:
Yes .. or a package where chrome is part of.

Or read this .. to use a config file and select the software you need.

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[Pixel C Android Development] followmsi:
Android 8.1 arrived ..

AOSP_8.1.0_r1_OPM1.171019.011_dragon-ota-eng.followmsi-v2.zip

Changes:

- Based on android-8.1.0_r1 - Dec 2017

- tegra-3.18_kernel_dragon_v171205_android-o_followmsi

- Opengapps (8.1) are not ready yet .. will try to hack the code to get unofficial API 27 version.

- This ROM is using "my" installer which has included the "backup" functionality from Lineage.

- This way you should keep your current Oreo 8.0 gapps alive .. needs to be tested.

- The update-binary has been changed too .. Oreo 8.1 is using system.new.dat.br

- The ".br" seems do do more compression as before .. the ROM is about 50MB smaller now.

Enjoy .. :p

EDIT:

Opengapps packages for Oreo 8.1 .. I hope they work fine.

open_gapps-arm64-8.1-pico-20171207-UNOFFICIAL.zip

open_gapps-arm64-8.1-stock-20171207-UNOFFICIAL.zip
[Pixel C Android Development] sabrdawg:
My Pixel C will be arriving later today and I will be looking at flashing this! :D
[Pixel C Android Development] 12paq:
[MENTION=5480152]followmsi[/MENTION] I'm getting a TWRP "error 6" when I try to flash 8.1.0_r1

Do I have the wrong vendor image or is there an error in the zip's updater script?
[Pixel C Android Development] followmsi:
Please use AOSP_8.1.0_r1_OPM1.171019.011_dragon-ota-eng.followmsi-v2.zip

The update-binary from aosp has still some more issues. :(

Pls report if all is working fine with v2.
[Pixel C Android Development] 12paq:
AOSP_8.1.0_r1_OPM1.171019.011_dragon-ota-eng.followmsi-v2.zip works perfectly. Along with your stock GAPPS.

Thank you! :good::cool:

Edit: Also working is Magisk and passes all checks with 14.3 beta
[Pixel C Android Development] EvansJD:
Flashed 8.1 and all OK

Was a dirty flash from 8.0

Only thing I have is very small nav bar buttons. Are the configurable?
[Pixel C Android Development] EvansJD:
ignore me.. Just installed custom nav bar app and all ok
[Pixel C Android Development] 12paq:
Yeah, the miniature nav buttons are wacked. What app did you use?
[Pixel C Android Development] Evans_jd:
This one

https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner&hl=en_GB

Works really well.
[Pixel C Android Development] LifeAsADroid:
Substratum supported?
[Pixel C Android Development] minieod:
i dont see anything in there for size options. what did you do to make them larger