yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
Same here .. settings menu works fine.

More info pls.
[Pixel C Android Development] Alxoom33:
I did a dirty install from last week's build. Used Gapps Mini. 8.29 same as last build.
[Pixel C Android Development] EnginEAR:
Installed over previous LOS17.

Used GApps (full stock, October 6th beta). Same used with previous LOS17 build.

Your custom kernel and Magisk canary.
[Pixel C Android Development] followmsi:
No idea .. for me it's working fine.

No time to replicate your issue.

If you take TWRP backup before and start clean install .. all ok ?

Rom only .. no gapps, no magisk .. all ok ?

Sorry .. can't help you better now.
[Pixel C Android Development] EnginEAR:
It's fine. I wasn't actually expecting help.

These builds are expected to have some glitches.

I was merely trying to report back (for your sake and the others following this thread).

If I manage to fix it (I'm also somewhat limited in time ATM) - I'll report back.

Thanks again for all your hard work.

It is greatly appreciated.
[Pixel C Android Development] muerte33:
I failed installing the new 10/10 version. I had to revert back to the 9/29. I tried different GAPPS, clean installs, dirty installs, etc. I would get it installed, but after the first reboot (after doing all the google setup), I could type in my PIN# and the main menu would flash, then go back to the lock screen.

It kept going to the lock screen, then would reboot. The 17.0-20190929-unofficial-dragon works great though.

I'll try the next round.

Thanks
[Pixel C Android Development] followmsi:
Yeah .. the "keymaster issue" is back - still not sure about the root cause.

From first page ..

- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.

Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.

The waiting time is required on fresh boot only, the following unlocks are working normally.

In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.z ip to remove pattern/pin or password.
[Pixel C Android Development] muerte33:
Thanks Followmsi!!

I'll definitely follow those instructions on the next release, glad that was all it was.
[Pixel C Android Development] Alxoom33:
Reflashed with new open gapps 10/6 Stock beta. Now working fine. Thanks.

Been trying to get Camera to work. Google Camera 7.0 and 7.1 are a no-go. 6.3 did not work either
[Pixel C Android Development] followmsi:
Camera will take longer .. still buggy !
[Pixel C Android Development] Alxoom33:
I did a factory wipe. A lot of issues that I was considering bringing up, like Gmail and playstore issues were fixed [emoji16]
[Pixel C Android Development] KrX38:
update 15.1 to 17 , no Gapps

Hello ,

I was on 15.1 and everything was OK with Gapps .

But when i flashed the 17 lineage OS and PICO Gapps 7.1 , no Gapps are present even if TWRP said it's OK .

Can you help me ? I really want to go to Android 10 but at least with some Gapps ( i tried the AOSP 10 ROM , same problem , no Gapps even flashed with twrp)

Now my tablet say that the system maybe corrupted and need to be repaired after the loading bootlogo of lineage ...

Reflash lineage 15 gave me a solid google logo at the boot ....

I try to reflash the stock FW but i have also a solid GOOGLE at the boot ... ( edit : i'm just dumb . I've flash the entire ZIP instead of extract it and just run the " Flash-all " command )

Now i think i just need to go back all over ....

Can someone confirm me the steps to go to line17 with gapps ?

What i've done : install TWRP ( bootloader unlocked ) , install lineage 15.1 ( site web installation instructions followed ) via twrp + adb ( after that and again in TWRP i've installed the Gapps 8.1FULL then magisk 20 ) . Reboot . My google account working on the tablet with YOUTUBE and GMAIL . Reboot to TWRP and install the zip lineage17 , again reboot to system and no Gapps ( magisk was still here ) .
[Pixel C Android Development] Mother_Teresa:
Have you tried flashing the gapps for the newer Android version?
[Pixel C Android Development] followmsi:
Android Pie - October 2019 - LAST LINEAGE-16.0 ROM -> DISCONTINUED

This is the end .. :)

It's the last Android Pie (lineage-16.0) build .. I will continue on lineage-17.0 only.

If you want to make your own Pie builds .. pls have a look here:

https://github.com/followmsi/manifests/tree/dragon-lineage-16.0

All my "final" ROM will be uploaded to androidfilehost.com ..

lineage-16.0-20191017-UNOFFICIAL-dragon.zip

Changes:

- Google (base/general) AOSP security updates -> October 2019

- Latest LineageOS changes for Pie

The ROM does contain it's own vendor.img !

Enjoy :p
[Pixel C Android Development] pierrebe:
Thanks for your work
[Pixel C Android Development] NYCHitman1:
Yeah, I've been looking into this more recently. However, I haven't found any resolution to getting the service to play nice and connect to Ashmem yet.
[Pixel C Android Development] Vartom:
In my AOSP 10, I observe that the MAC address of the Wi-Fi is taken from the kernel "00:90:4c:11:22:33" and not normal as it was previously in the AOSP 9.

Is Lineage 17.0 the same?

Some changes in Wi-Fi seem to have influenced this, but how to return it?
[Pixel C Android Development] xciteful71:
Hey folks, I have a basic question: The last system image for 15.1 is from Aug. Are the current Lineage OS builds still utilizing this image and is the last 15.1 tegra-3.18_kernel_oreo_dragon_v190906_unicorn-xceed-followmsi.zip also built against this system image?

Thanks.
[Pixel C Android Development] followmsi:
Yes .. seems so.
[Pixel C Android Development] followmsi:
Yes .. for lineage 15.1 you still need to use last Google (August) vendor.img.

And yes .. kernel should work too.
[Pixel C Android Development] Markeee:
Wanted to give 17.0 a try considering 10.0 Gapps is not out yet on opengapps.org wheres the best place to grab opengapps for 10.0 ?
[Pixel C Android Development] xciteful71:
Everything updated without issue. :good:
[Pixel C Android Development] 12paq:
10A Gapps are out as a test or canary build. Look harder on their site or read back a few pages on this thread for a link that was posted.
[Pixel C Android Development] Markeee:
Got a link I'm not seeing it ?
[Pixel C Android Development] ipdev:
The official OpenGApps builds have been moved to SourceForge.

OpenGApps Summary SourceForge - Link

Android 10 is in Beta.

OpenGApps arm64 Beta SourceForge - Link

Cheers. :cowboy:
[Pixel C Android Development] Markeee:
Thanks
[Pixel C Android Development] Alxoom33:
Yep! That's what I have been using!
[Pixel C Android Development] Tayl:
Hello, semi-noob here.

I would greatly appreciate if anyone could point me in a direction to a good guide to follow to get the latest Android 10 LineageOS on my Pixel C. I've dabbled with flashing my Moto X years ago, but without a good guide I'm pretty confident that I'll brick it.

Thank y'all for any help you can provide.

~Taylor
[Pixel C Android Development] Alxoom33:
Take a look at the OP in this thread and search for [MENTION=5480152]followmsi[/MENTION]'s Lineage 17 posts n this thread. Also, after reading and searching, everyone in this thread is available to answer educated questions. Enjoy!
[Pixel C Android Development] kalinskym:
Are you going to be porting over gestures working on third party app launchers since it's available on Pixel 4 series.
[Pixel C Android Development] Matt Carter:
Boot loop.

After installing the last ROM (

lineage-17.0-20191010-UNOFFICIAL-dragon.zip), the device gets stuck in the lineage opening scree animation.
[Pixel C Android Development] Zed Smith:
Hey, I'd like to build my own android 10 lineage build, may you upload this manifest as well? Thank you :)
[Pixel C Android Development] followmsi:
No plans for the moment .. actually we still have device problems like Camera .. etc.
[Pixel C Android Development] followmsi:
No idea whats happening for you .. installed all published builds myself.

No problems, except for knnown issues on first page.

Are you able to reproduce your problem ? .. If yes, I will need logs.
[Pixel C Android Development] followmsi:
Here you are ..

https://github.com/followmsi/manifests/tree/dragon-lineage-17.0

Happy ROM building :p
[Pixel C Android Development] Zed Smith:
Thank you for the quick response! However, the kernel fails to build. I think the interesting line is "aarch64-linux-android-gcc is not allowed to be used.". Tried it with the modified aosp build tools from your GitHub but no luck there. Unfortunately I am not allowed to post links here and I don't want to spam the forum with the huge error chunk it throws, I hope the short report is sufficient :/
[Pixel C Android Development] followmsi:
https://github.com/followmsi/manifests/commit/6bc1f848233ba38c16ffc54cbb4119a8925f803d
[Pixel C Android Development] Zed Smith:
Blazing throu' the kernel section, great! :)
[Pixel C Android Development] followmsi:
Android 10

Vukan API is fixed now .. had to take prebuilt libs from Nivida shield firmware. :)

Lineage has shipped trebuchet launcher .. and some more (minor) changes.

lineage-17.0-20191025-UNOFFICIAL-dragon.zip

Changes:

- Fixed Vulkan API

- Added new health HAL and more changes .. thanks to [MENTION=2489052]NYCHitman1[/MENTION]

- Latest LineageOS changes for Android 10 -> still a lot of lineage stuff is missing.

The ROM does contain it's own vendor.img !

Enjoy :p
[Pixel C Android Development] doumer:
Sorry for the noob-question, but never had this with any other rom: what das "The ROM does contain it's own vendor.img !" mean exactly? I would guess I would have to flash the stock vendor-image via fastboot before flashing this rom from recovery but since there is no v10 vendor-image, this can't be true - so how to install this rom (coming from stock)? Thanks in advance!
[Pixel C Android Development] tschmid:
No dont Flash Stock vendor image, just rom, gapps and magisk

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] MrTim68:
Just installed this rom and it's crashing back to the recovery. The previous lineage 17 rom installed no problems. Has anyone else had this issue?
[Pixel C Android Development] schoerb:
I had the same problem with the new version. I had to flash Gapps and Magisk after LineageOS 17.0 and it started :)
[Pixel C Android Development] Alxoom33:
New update, smoother and working better than ever. Definitely a DD!

---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------

See below.

Just install the Rom and Gapps and reboot. Then after everything settles go back to TWRP and flash kernel and latest Magisk Canary build. This version is awsome.

If you are still having problems, go to TWRP, Wipe data Factory Update and start clean.
[Pixel C Android Development] Markeee:
For me Dirt Flashing over previous build kept boot looping back to recovery doing a full format in TWRP clean flashing Rom Gapps and Magisk worked perfectly. This build is a definite improvement over previous builds

Thanks
[Pixel C Android Development] michaelsage:
OpenGApps

Just as a heads up, I had to use the 20190928 version of the OpenGapps BETA, the latest 20191006 detected the wrong ROM and wouldn't install. Hope that helps someone! :)
[Pixel C Android Development] Markeee:
Open_gapps-arm64-10.0-nano-20191006-BETA worked fine for me on a clean install
[Pixel C Android Development] tommy1994:
i cant connect to my home mesh wifi

but i can connect to the wifi hotspot that i share via my iphone

using 1025 build with clean install
[Pixel C Android Development] Alxoom33:
I used the 10/26 open Gapps full version. Working w/o a hitch[emoji41]
[Pixel C Android Development] michaelsage:
That's weird, it detected my version of android incorrectly. I tried the nano install.... very strange. Glad it's working for you :cool:
[Pixel C Android Development] tschmid:
Same on my device

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] Vartom:
I'm not surprised, because in the properties it has 8 android

PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=dragon \
PRIVATE_BUILD_DESC="ryu-user 8.1.0 OPM1.171019.016 4503492 release-keys"

BUILD_FINGERPRINT := google/ryu/dragon:8.1.0/OPM1.171019.016/4503492:user/release-keys

PRODUCT_PROPERTY_OVERRIDES += \
ro.build.fingerprint=google/ryu/dragon:8.1.0/OPM1.171019.016/4503492:user/release-keys
[Pixel C Android Development] ipdev:
To those having issue installing OpenGapps.

It's been noted before, opengapps is having a problem mounting system properly.

To work around it, you have to mount system before installing OpenGapps.

Install rom.

Mount system.

Install opengapps.

Install magisk if you want.

Reboot.

Cheers. :cowboy:

PS.

OpenGapps installer looks for SDK level not the build fingerprint.

Not at home to check the exact line. If anyone wants to check, it in the opengapps inc.installer.sh file.
[Pixel C Android Development] tschmid:
For me Android Setup is force closing. Any Tipps?

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] Alxoom33:
That makes sense!I always make sure System, Vendor and data are mounted before flashing. Good advice [emoji106]
[Pixel C Android Development] followmsi:
You should set as well .. this is fixing Saftey.Net check in Magisk .. not related to gapps installation at all.

Cheers
[Pixel C Android Development] followmsi:
Edit "default.prop" and change ..

ro.control_privapp_permissions=enforce

to

ro.control_privapp_permissions=log

or

ro.control_privapp_permissions=disable

Test Setupwizard again .. Not sure if this will help !

Cheers
[Pixel C Android Development] followmsi:
system-as-root (SAR)

Some (newer) devices were using it before .. but beginning with Android 10 it's mandatory for all devices.

Also for "legacy" devices like dragon - yes - we are legacy now !

We use "2SI" - 2 stage init - thru fstab in ramdisk !

Magisk team explains the different ways on how SAR got implemented into Android devices.

Pls check magisk xda thread and twitter account for more details on SAR.

Various apps and tools do have problems with "system-as-root (SAR)" and all it's implementations.

It will take some time until all the tools have been updated.

Magisk 20 is ready for "most" of the SAR implementations.

If you install Magisk 20 on dragon Android 10 ROM you will see "Detecting .. system-as-root" on your screen.

Until all the apps and tools have been modified for SAR there are some workarounds in place ..

Dont' make installation queue in TWRP !

Install each zip file manually.

For gapps installation it helps if you mount system partition manually in TWRP mount menu - before gapps installation.

if mounted already in mount menu - unmount and remount again.

For other tools it helps to just copy "/system/system/build.prop" (SAR location) to "/system/build.prop" (OLD location before Android 10)

build.prop is just an example .. maybe your tools requires other files to be copied.

The logic to detect if "/system" is now located in "/system/system" is missing in most of the tools/apps today.

Actually I have made TWRP version for dragon to use the flag "system_root" in config - to let TWRP know about SAR.

Maybe next TWRP version will include also some additional "checks" for Androdid 10 SAR devices - and it's various implementations.

https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html

To summarize .. :)

Pls be patient until all the tools/apps have been updated for SAR on Android 10 !

Or use some workarounds to make it working today.

Cheers
[Pixel C Android Development] tschmid:
Strange its runing fine now [emoji41]. I made a complet format and installed without twrp queue now all works

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] JohnnyChim:
may I ask why I am not able to install gapp for android 10 after I have flashed Lineage os 17.0

TWRP said my version is 7.1.2

then I flashed gapp 7.1.2 successfully but there are no gapp in the system
[Pixel C Android Development] tschmid:
Did you formated data?

Did you installed every zip separate?

Did you remounted system after los-17?

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] JohnnyChim:
I have solved the problem after remounting system

But the setup.exe keep crashing after booted into the system
[Pixel C Android Development] tschmid:
Had the same, format data

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] JohnnyChim:
What about some random reboot, did you guys experience it?

I got it from time to time
[Pixel C Android Development] tschmid:
No, nothing atm

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] Iggy82:
Thank you Followmsi

Installed latest version of TWRP from your Google Drive directory (3.3.1-1)

Wiped everything as per your instructions

Installed Lineage 17

Unmount/Remount System

Installed Gapps (20191006 BETA Stock)

Unmount/Remount System

Installed Magisk v20

Done!

I previously came from Lineage 16. Hope the above steps help others who've had install issues.

2 issues I've found which I can't seem to fix:

Random Reboots (Happened twice in last 15 minutes) - EDIT: No more reboots since I disabled Chrome and used Chrome Beta instead

Chrome browser won't let me type a URL/search into the address bar without crashing. It just suddenly closes every time I try.

Tried Reboot, uninstall all updates, wipe cache, wipe storage of Chrome app. Only success I've had is to disable it and install Chrome Beta, which works fine.

I did notice Chrome was in some kind of forced dark mode (I have dark theme enabled from Display settings), it doesn't look right. Whereas Chrome Beta is working in standard colours (i.e. white). Not sure if this has something to do with the error.
[Pixel C Android Development] 12paq:
I had a random reboot while my tablet was starting for the first time after flashing the latest 17. I have not had a other reboot since.
[Pixel C Android Development] Thug Life of the France:
Two questions regarding the Pixel C stuff

Hi everyone,

I just would like to know if there's a way to get rid of that stupid 30s delay at startup saying "os verification is off, device will continue booting after 30s"

Also, is there an effective way to disable the LED bar on the back, mainly to preserve battery life as it shines for no reasons sometimes, and because one LED died off, so that looks stupid now

Cheers everyone,

Looking forward to a more stable Android 10 ROM
[Pixel C Android Development] followmsi:
This is another strange issue .. happens on several devices.

Maybe another gapps problem.. no idea.

If you remove location permissions for chrome is works again.

Cheers
[Pixel C Android Development] Dhalsim43:
Sadly, I believe it's not possible to avoid BL unlocked warning... ?
[Pixel C Android Development] 12paq:
No. There seems to always be some sort of notification on every device when the bootloader is unlocked. Yes this one's a bit more annoying because it has the 30 second delay. But you get used to it. The dev support on this device is very small, so we don't expect much and are gracious for what we get. Just getting two or three devs working on Android 10 was unexpected and very appreciated.

I think there's a thread around here in the Pixel C XDA forums about someone turning the rear LEDs into some sort of notification. Maybe there was a way to turn them off. If it's still around it's very old and likely not maintained. See previous paragraph.
[Pixel C Android Development] Vartom:
In AOSP 9/10, I turned off the notification bar.

The delay of 30 seconds can not be removed at all, but it is possible (but this is not accurate) can be reduced to 2 as it is on chrome OS laptops.
[Pixel C Android Development] followmsi:
How to reduce to 2 seconds ?
[Pixel C Android Development] Vartom:
There is such a flag dev-screen-short-delay. Question how to change it. Perhaps it can be changed by adding code to the fwtool utility.
[Pixel C Android Development] Dhalsim43:
I've read somewhere that there's a physical switch inside
[Pixel C Android Development] Vartom:
There are no physical switches inside. Look at the site with the disassembly of the tablet.
[Pixel C Android Development] Dhalsim43:
No more official 15.1 build ?
[Pixel C Android Development] Iggy82:
Could be a solder joint, some Chromebooks have a screw to remove which effectively breaks a circuit. It would take a genius to figure out if it was included. Certainly possible as this tablet was originally designed with ChromeOS in mind, but they changed to Android later on for release
[Pixel C Android Development] Dhalsim43:
That was this message
[Pixel C Android Development] Vartom:
Chromebooks have such a thing as a virtual developer switch. It is registered in the bootloader configuration (coreboot / v-boot) of the tablet.
[Pixel C Android Development] Thug Life of the France:
Well, I'm not seeing that option on followmsi's build of LOS 16
[Pixel C Android Development] followmsi:
Android 10 - November 2019

Still no go for Camera .. will take longer.

Tested with opengapps beta (11/05) and Magisk 20.1 ..

lineage-17.0-20191107-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> November 2019 (10.0.0_r11)

- Latest LineageOS changes for Android 10 -> still a lot of lineage stuff is missing.

system-as-root (SAR)

For gapps installation issues and more information ..

Pls read first .. https://xdaforums.com/showpost.php?p=80693701&postcount=1350

The ROM does contain it's own vendor.img !

Enjoy :p
[Pixel C Android Development] muerte33:
Thanks FollowMSI, running it now
[Pixel C Android Development] Markeee:
Can this be dirt flashed over previous build ?
[Pixel C Android Development] Alxoom33:
Dirty flash works for me!
[Pixel C Android Development] Markeee:
Got it thanks