yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] jeffyca:
I manually wiped everything. Did not have a system installed. TWRP even yelled at me when i wanted to reboot to try again saying no OS was installed. I was coming from February image and an older TWRP before updating to the newest TWRP and trying this AOSP package before going to March image.
[Pixel C Android Development] followmsi:
Strange indeed ...

Here is the relevant part ..

(!less_than_int(1488913849, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Tue Mar 7 20:10:49 CET 2017) over newer build (" + getprop("ro.build.date") + ").");

getprop("ro.product.device") == "dragon" || abort("E3004: This package is for "dragon" devices; this is a "" + getprop("ro.product.device") + "".");

ui_print("Target: Android/aosp_dragon/dragon:7.1.1/N4F26T/follow03072010:userdebug/test-keys");

Need to remove this and save the file and zip again ..

The script is the checking the date of the Recovery ;)))

Will remove this .. and make a new Upload ..
[Pixel C Android Development] followmsi:
This is really funny .. :)

You are using already 3.1.0-1 from the download folder ... which is newer as the ROM ..

Look at the build date :

ro.bootimage.build.date=Thu Mar 9 17:08:49 CET 2017

Anyway ...

I already uploaded a new version .. same name !

Pls download again .. and install .. Thanks for your understanding !

The new update script looks like ..

getprop("ro.product.device") == "dragon" || abort("E3004: This package is for \"dragon\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Android/aosp_dragon/dragon:7.1.1/N4F26T/follow03072010:userdebug/test-keys");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/700b0600.sdhci/by-name/APP", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/700b0600.sdhci/by-name/KERN-A");
show_progress(0.200000, 10);
set_progress(1.000000);

Sorry for this one :)

Will be fixed for the next month AOSP package ..

Cheers
[Pixel C Android Development] Istvan_86:
Sorry a hard day in the office and I go directly to bed.

I wipe everything and system is in ext4 but error 7 stiill stops the flashing process. Also my usb otg stop working in 3.1.0-1 and I must go back to 3.1.0-0 to restore my backup that iis stored iin a usb.
[Pixel C Android Development] followmsi:
Pls re-download new OTA version .. same name - from the one drive folder again.

Removed the error 7 check now .. The OTA is older as the recovery you are using :)

Pls stay with TWRP 3.1.0-0 for now.
[Pixel C Android Development] Istvan_86:
Ok I´m back on TWRP 3.1.0-0 and downloading the new AOSP ZIP. I reinstall Pure Nexus just for testing and it installs and boots without problems with TWRP 3.1.0-0. So now with a booting rom installed what must I wipe before install the new zip?

Thanks for all your help.
[Pixel C Android Development] followmsi:
Pls format system first .. to remove the pure nexus stuff ...

Have made dedicated version of the vendor.img too.

AOSP_Update.ZIP_PixelC_Ryu_vendor_N4F26T.zip

Oherwise you will get warning message at system start ..

All the small issues ... but now it's looking good.

I have moved as well ... I will stay on AOSP now .. no BETAs anymore !

Once they release the 7.1.2 code we will make a new AOSP :)

No problems on 3.1.0-1 in terms of USB.OTG ..

Just doing USB-OTG restore of my old data partition and will merge it "dirty" into AOSP now ..

All the google apps will cry :)

Takes 1-2 hours fixing stuff ... but not installing 150 apps and tons of other settings from scratch .. etc. :)

AOSP is coming :)

Cheers
[Pixel C Android Development] Istvan_86:
I repeat all the steps includiing downloading again all the files but when I end the process and try to reboot to boot in the rom TWRP says that OS isn´t installed.... We are missing something?
[Pixel C Android Development] followmsi:
Just reboot .. ignore the message.

Sometimes TWRP has an issues if system is mounted before you install the zips.

After you have formatted system, just manually unmount system in mount menu.

I am running AOSP myself .. works like a charm !
[Pixel C Android Development] followmsi:
Using Tapatalk from the old backup .. all was working directly.

But not all apps .. maybe 15 of 140 apps have to be reinstalled .. if you want to keep the settings, just install apk version over the existing installation .. works fine too ;)

Fully burning AOSP ;)
[Pixel C Android Development] Istvan_86:
Ok, I install again pure nexus and boot it. After that I reboot in TWRP and wipe dallvik + cache + system and when this finish TWRP says "Unable to mount storage" Is this normal and I can now unmount system in order to flash the AOSP zip and the vendor zip + gapps and reboot?

Thanks.
[Pixel C Android Development] GonzoKSV:
Moin!

Is it still nessecary to install Gapps after dirty flashing?

Gesendet von meinem AOSP on dragon mit Tapatalk
[Pixel C Android Development] followmsi:
Nein .. the ROM installer should make backup and restore of gapps when you install the new ROM.

In case of changing API level .. eg. From 8.0 (API 26) to 8.1 (API 27) I recommend to install fresh gapps again.
[Pixel C Android Development] tim.malone:
I just wanted to say thanks for making this! I installed it last week and it's working great. Seems smoother than stock and my battery life has been great.
[Pixel C Android Development] followmsi:
Feb 2018 ..

AOSP_8.1.0_r10_OPM1.171019.016_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.1.0_r10 - Feb 2018

- Latest kernel changes -> tegra-3.18_kernel_dragon_v180206

Pls use opengapps from here ..

https://drive.google.com/drive/folders/1IY1JrNDlkk7OjXutlX3zGeASfWpSsRdl

Enjoy .. :p
[Pixel C Android Development] Alex93917:
Thank you for your hard work especially for Pixel C guy !!
[Pixel C Android Development] followmsi:
March 2018 ..

AOSP_8.1.0_r16_OPM1.171019.022.A1_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.1.0_r16 - March 2018

- Latest kernel changes -> tegra-3.18_kernel_dragon_v180308

Offical opengapps packages are ready now ..

Enjoy .. :p
[Pixel C Android Development] brackenhill_mob:
Weird thing. Opening the link in Drive on the tablet shows me old files and not the new ones no matter how many times I hit refresh, but opening in a browser does everything as expected.

Anyone else seeing this?
[Pixel C Android Development] tim.malone:
Ethernet adapter

Hello,

I've been running AOSP for a while now and really like it. I just bought a WeMe USB hub and ethernet adapter. It works fine on my Huawei Mate 9 (after I turn wifi off). I cannot get it work on the Pixel C. I am running the March 2018 build with the stock kernel (from the build). I've tried the combined kernel (with xceed changes), but that doesn't work for me either. I have this adapter: https://www.amazon.com/WEme-Etherne...00WHLJIQM/ref=cm_cr_arp_d_product_top?ie=UTF8

I see in this thread that others are using ethernet on Oreo builds. Does anyone have this adapter working? Can anyone point me to an adapter that is known to work? Is there anyway to fix this? I'm not even sure how to debug it. If I go into the terminal and use dmesg, I see an event register when I plug or unplug the adapter (a generic usb event), but nothing else. Trying to bring up eth0 using ifconfig doesn't work. Not sure what the issue is.

Thanks.
[Pixel C Android Development] followmsi:
We have general usbnet support activated in kernel .. and some device specific drivers.

CONFIG_USB_USBNET=y

CONFIG_USB_NET_AX8817X=yCONFIG_USB_NET_AX88179_178A=yCONFIG_USB_NET_CDCETHER=y# CONFIG_USB_NET_CDC_EEM is not setCONFIG_USB_NET_CDC_NCM=y# CONFIG_USB_NET_HUAWEI_CDC_NCM is not set# CONFIG_USB_NET_CDC_MBIM is not setCONFIG_USB_NET_DM9601=y# CONFIG_USB_NET_SR9700 is not set# CONFIG_USB_NET_SR9800 is not setCONFIG_USB_NET_SMSC75XX=yCONFIG_USB_NET_SMSC95XX=y# CONFIG_USB_NET_GL620A is not setCONFIG_USB_NET_NET1080=y# CONFIG_USB_NET_PLUSB is not setCONFIG_USB_NET_MCS7830=yCONFIG_USB_NET_RNDIS_HOST=y# CONFIG_USB_NET_CDC_SUBSET is not set# CONFIG_USB_NET_ZAURUS is not set# CONFIG_USB_NET_CX82310_ETH is not set# CONFIG_USB_NET_KALMIA is not set# CONFIG_USB_NET_QMI_WWAN is not set# CONFIG_USB_HSO is not set# CONFIG_USB_NET_INT51X1 is not set

Most probably we need to add device specific usbnet driver too.

Which one ? ;)

Maybe you need to port the driver from other kernel sources ..mate 9 ?
[Pixel C Android Development] tim.malone:
Thanks! Your suggestion helped, but I haven't solved it.

I looked into it more and the driver is enabled (realtek 8153). I played around a bit more and discovered that the pixel c doesn't even see the hub. It doesn't register at all according to USB device info (from the play store). When I plug just the hub into my mate 9 it shows up under that app. No entry appears on the pixel c. Also, on the mate 9, the little power light on the hub is completely steady. On the pixel c it seems to be slightly unsteady. Not fully turning off and on, but wavering a little. Maybe it's trying to draw more power than the pixel c will provide? That seems odd since it will power an external hard drive. It seems like it may be a hardware issue.

I think I'll start a new thread asking for recommendations for hubs with Ethernet.

Thanks again! Great ROM BTW.
[Pixel C Android Development] followmsi:
April 2018 ..

AOSP_8.1.0_r19_OPM1.171019.026_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.1.0_r19 - April 2018

- Latest kernel changes -> tegra-3.18_kernel_dragon_v180402

- Fix for small NavBar icons

Enjoy .. :p
[Pixel C Android Development] darren1:
Stock Android for the Pixel C doesn't allow you to add trusted devices for Smart Lock, is this option available on this Rom?
[Pixel C Android Development] LifeAsADroid:
Using TWRP 3.1.1-0...

Wiped system, cache, and dalvik.

Installed ROM zip, then vendor image to vendor image partition, then open gapps, then supersu.

Rebooted device. It booted to the Google screen, then the Android screen. Then rebooted on its own back to TWRP recovery. I attempted to reboot system again, same thing happens.

Edit: in TWRP the internal storage is reading 0MB... No files on sdcard to even attempt to flash again...

Second edit: when tablet boots into TWRP it warns the system is unmodified... Attempting to factory reset wiping data, cache, dalvic fails due to unable to mount storage...

Any ideas?

Thanks
[Pixel C Android Development] followmsi:
Pls use 3.2.1 TWRP .. always latest version.

Did not test SuperSu for a while .. using magisk 16.3.

No idea what's going wrong for you .. pls start over from scratch.

You may need to format data .. and copy install files via adb in recovery.

Sorry .. can't help you better.
[Pixel C Android Development] LifeAsADroid:
Thanks for getting me started and offering to help out.

I'm having issues with adb in fastboot mode... was thinking I could fastboot flash the twrp 3.2.1 to the pixel c using adb. I'm using "minimal adb and fastboot". Typing the command "adb devices" does not list anything. I was able to get to "adb sideload" within twrp itself and now the tablet is recognized by adb on the computer. Am I able to flash a new twrp while in twrp adb sideload? Do you happen to know the exact command in adb command window to type? Something like "adb flash recovery twrpfilename.img"? I've done it from fastboot, but never from within TWRP itself.

Thanks again.

EDIT: along the same line, am I able to just flash the ROM.zip file, followed by the vendor.img file from adb sideload in TWRP (after updating TWRP to 3.2.1)? I can then reboot and install open gapps and supersu later after the tablet is up and running.
[Pixel C Android Development] followmsi:
All needs to be installed at the same time .. no reboot into system in between.

You can use "install image" in TWRP to update TWRP itself.

Reboot into recovery afterwards to use the new version.

asb push source/filename target/filename

Normal installation inside TWRP.

Once you have TWRP installed .. flash all stuff in one shot, you may try Magisk 16.3 as well - as last installation step !

Good luck !
[Pixel C Android Development] LifeAsADroid:
I can't use the install img in TWRP because I can't mount the internal storage. I would need to adb sideload the img within TWRP but don't know the command to do so.

I also can't adb push files to the tablet for the same reason... No mounted internal storage.

Using fastboot isn't an option because the tablet isn't recognized by the computer in fastboot, only in adb sideload within TWRP.

I know there's a way to adb sideload zip files like the rom file, but is there also a way to adb sideload img files?

I attempted to mount the storage from inside TWRP with their mount function but the data or internal storage won't mount.
[Pixel C Android Development] followmsi:
You can push to /tmp .. anyway.

You may format data as first step, reboot back into TWRP and start to copy the files via ADB onto /data.

You don't own an USB stick ? ;)

General documents on how to use ADB will help you with the commands .. quite easy.
[Pixel C Android Development] LifeAsADroid:
Thanks for all the help and advice. I'll see what I can do later tonight with either pushing to /tmp or reformatting /data or the usb flash drive. Thanks for the idea about a micro-usb stick for getting the files to the tablet, never thought of that ;)
[Pixel C Android Development] LifeAsADroid:
Another couple of quick questions (I'm new to this whole "flash vendor img file after ROM zip thing...").

- Which partition do I flash the vendor img to? I vaguely remember there were two "vendor" choices in TWRP. EDIT: I was mistaken, there is only one vendor partition available.

- Do I have to reflash the vendor img file every time I update a nightly build for a current ROM? Is the vendor img file the same regardless of ROM that I flash? Like, if I flash this ROM with the vendor img file, then decide to flash LineageOS ROM, do I use the same vendor img file or is the vendor img file written specific for each ROM?

Thanks.
[Pixel C Android Development] LifeAsADroid:
A lot here, please bear with me.

Using a flash drive and mounting in TWRP worked. Was able to flash the TWRP 3.2.1 img file, reboot into recovery, all is good there.

I am however noticing that TWRP is EXTREMELY slow to respond to commands (it was also very slow when 3.1.1 was installed, this isn't new to me). Is it supposed to be this slow??

After installing any zip or img file successfully, TWRP becomes unresponsive. After each install, I have to reboot directly to bootloader then to recovery again. I am guessing this is my issue with installation of the ROM, even if I am not booting the system? Has anyone else noticed this slow behavior in TWRP? Is this supposed to happen? Is TWRP supposed to be ridiculously slow? Does TWRP eventually respond after installing a zip or img file to allow the installation of another file and I just have to be extremely patient?

I was able to restore a backup in TWRP, however when the tablet gets to the "Google" screen on boot it hangs/stalls. Maybe I need to let it work longer than I am leaving it? It was sitting a good 5 minutes with no change at this screen.

Side note:

From what I am gathering online in other device forums that had a similar issue with the internal storage reading 0MB and being inaccessible is that during that first system boot up when the device would reboot to recovery is that the internal storage was somehow encrypted and unable to be accessed by TWRP. Using the flash drive as a work around was an excellent idea, thanks again for that suggestion.
[Pixel C Android Development] followmsi:
There is one vendor.img for all ROMs only - coming from monthly Google stock ROM updates.

Like for Nougat the last vendor.img will come with the last Google update for Oreo .. whenever P arrives.

You can download factory image and unpack to grab the vendor.img from it's original source.

Like me too ..

Cheers
[Pixel C Android Development] followmsi:
The TWRP speed on dragon has been discussed 1000 times already...

It's related to the Nvidia DRM stuff .. etc.. graphics issue.

Quite complicated either !

Official lineage and google stock ROM are doing force encryption on first boot.

For this reason you need to install magisk (or other tools) before first boot, but after ROM installation.

If you forget once - you are encrypted again .. Magisk has some auto reinstaller add-on script.

On XDA you will find more detailed information..

Cheers
[Pixel C Android Development] LifeAsADroid:
Thanks for all the help. I now have a working tablet again. Used the latest Lineage ROM file. The procedure that worked was:

-Install ROM, reboot device DIRECTLY to bootloader (power button + volume down), then DIRECTLY to recovery via recovery option.

-Install vendor img. Reboot system and let device do its thing.

-Once set up completes, reboot to recovery, install Gapps package. Reboot system, let device do its thing.

-Boot to recovery, install supersu (sorry, I'm stubborn about not using magisk, I've tried using it on my last two phones and could never get the phone to boot after installing magisk, always had to wipe everything in recovery and reinstall from scratch). Reboot device, let it do its thing, and done.

... Hopefully this process has all been worth it.
[Pixel C Android Development] followmsi:
You may not reboot in between of your installation steps.

Anyway .. enjoy lineage 15.1

Cheers
[Pixel C Android Development] laurentbon:
Hello All - great ROM, first time I root my pixel c!

Disappointed to notice that the split screen lag is in this ROM too. When having 2 apps side by side on split screen, the app on the left stutters when scrolling. Must be an AOSP bug since the factory ROM also has it.

Does anyone know of a ROM that does NOT have this issue?

Thank you,

L
[Pixel C Android Development] Monazite:
Go to developer options and enable 'disable hw overlays'
[Pixel C Android Development] laurentbon:
Thanks a lot. It works as intended now! Happy
[Pixel C Android Development] gtaadicto92:
I have this rom and the xceed kernel on my Pixel C and I'm happy with the battery life and smoothness. But when the battery percentage drops below 40% it starts to lag like crazy, lots of stutters in the animations, chrome is slow...

Why does this happen? I recently installed Xposed and Amplify to limit location, icing, sync and Twitter app wakelocks. Is it related to this?
[Pixel C Android Development] followmsi:
If you disable the Xposed stuff it's back to normal ?

Same problems if you keep the kernel from ROM ?

On stock ROM too ?

Sorry . No idea what's going wrong for you.
[Pixel C Android Development] followmsi:
May 2018 ..

AOSP_8.1.0_r29_OPM4.171019.016.C1_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.1.0_r29 - May 2018

- Latest kernel changes -> tegra-3.18_kernel_dragon_v180508

Enjoy .. :p
[Pixel C Android Development] followmsi:
June 2018 ..

AOSP_8.1.0_r31_OPM4.171019.021.D1_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.1.0_r31 - June 2018

- Latest kernel changes -> tegra-3.18_kernel_dragon_v180605 (android-8.1.0_r0.63)

- Google added new Bluetooth firmware this month.

Just as a reminder ..

June 2018 factory image does include another new bootloader: bootloader-dragon-google_smaug.7900.126.0.img

Enjoy .. :p
[Pixel C Android Development] wizzardsk:
Sorry, but what is the difference between stock and this ROM? Both are pure Android, or I misunderstand someting?
[Pixel C Android Development] Monazite:
Both are pure Android.
[Pixel C Android Development] wizzardsk:
So why would anyone install this when we have stock?
[Pixel C Android Development] followmsi:
You install AOSP if you ..

- want to decide which gapps you install without playing in system ;)

- want slight modifications like NavBar size .. etc.

- want not to be force encrypted without any root tools ..

- want to use the minimal setup and adjust yourself.

etc..

And because its just cooler as running stock ROM ;)

Have a nice weekend ..
[Pixel C Android Development] followmsi:
Normally the fully working sources are published at go-live date and not before.

Made a quick search .. DP3 is not too hard to build ..

https://groups.google.com/forum/#!topic/android-building/JfgzeR_S9N4

Actually I did start a DP3 test build last night .. It's building .. but not sure if and how it's running. :p

Needs to be tested ..

AOSP_Android-P-DP3_dragon-ota-eng.followmsi.zip

Made new gapps package too .. same here - needs testing.

open_gapps-arm64-9.0-pico-20180625-UNOFFICIAL.zip

open_gapps-arm64-9.0-stock-20180625-UNOFFICIAL.zip

I will have no time for more tests this week .. pls let me know your results.
[Pixel C Android Development] Displayer:
Hey [MENTION=5480152]followmsi[/MENTION],

I just tried installing your DP3 build with the provided GAPPS,

I can't flash GAPPS even after a reboot it says it needs to be on android 9.0,

Also i tried only with and without magisk and the DP3 build,

Did not even booted up in any of these cases,

Cordially,

Maxence
[Pixel C Android Development] followmsi:
Thanks for testing ..

Made a quick check .. Api level is still 27.

We want api level 28 now.

If you use 8.1 gapps it will not complain, but the ROM is clearly not P !

As we can see the tag "android-p-preview-3" gets compiled but the outcome is something different.

https://android.googlesource.com/platform/build/+/android-p-preview-3

Most probably I will not spent more time at this early stage using incomplete sources.

Thanks again for testing ..
[Pixel C Android Development] Displayer:
Yes that's what I tried,

It succeed with GAPPS 8.1 but still can't boot,

No problems, my pleasure,

Available for more testing whenever you want ! :)
[Pixel C Android Development] followmsi:
July 2018 ..

AOSP_8.1.0_r37_OPM4.171019.021.N1_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.1.0_r37 - July 2018

- Latest kernel changes -> tegra-3.18_kernel_dragon_v180703 (android-8.1.0_r0.74)

- media volume steps from 15 to 25

- disable bionic warnings

Due to holiday season the August releases will be delayed !

Enjoy .. :p
[Pixel C Android Development] followmsi:
Just back from holidays and some more P testing for dragon .. :p

AOSP_9.0.0_r1_PPR1.180610.009_dragon-ota-eng.followmsi.zip

Still the same gapps packages .. will make some new packages in the next time.

open_gapps-arm64-9.0-pico-20180625-UNOFFICIAL.zip

open_gapps-arm64-9.0-stock-20180625-UNOFFICIAL.zip

This is a test version !

This build has not yet been tested by me - Not sure whats working and if its booting at all !

If it boots the system should have permissive selinux.

The August Oreo AOSP build will be published later on ..

Cheers
[Pixel C Android Development] Monazite:
Ohhhhhh! Pie! followmsi you are genius! ???
[Pixel C Android Development] yankeefan:
Thanks for great work! I tried to install Pie but could not get it past Google splash screen. Look forward to it as I am using it on an Essential PH1 now and it is great
[Pixel C Android Development] followmsi:
Thanks for testing .. will have a look in the next time.
[Pixel C Android Development] followmsi:
August 2018 ..

AOSP_8.1.0_r42_OPM4.171019.021.Y1_dragon-ota-eng.followmsi.zip

Changes:

- Based on android-8.1.0_r42 - August 2018

- Latest kernel changes -> tegra-3.18_kernel_dragon_v180811 (android-8.1.0_r0.93)

Enjoy .. :p