yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] narse:
Dirty flashing from 20dec to 26dec caused my tablet to reboot to recovery. Clean installing working well though.
[Pixel C Android Development] QU3U3:
I was having the same issue so I started at the rear of this thread and found your post. I also went back another couple of pages and saw people having trouble with mounting. So, I decided to look a bit further at that and found that System and Vendor are not mounted when I booted into TWRP. I'm new to this mobile stuff but I have 2 decades of experience with Linux and it seemed odd to me that we would try to write to a file system that was not mounted. I gave it a shot and got myself up and running.

Here are my steps, then ...

1. Boot into TWRP

2. Check and, if necessary, mount System and Vendor (Data and Cache are already mounted for me)

3. Wipe SYSTEM and DATA partitions! (If you are encrypted, pls format DATA partition !)

4. Install ROM.zip (I use adb sideload from my Linux laptop)

5. WORKAROUND for Android 10 system-as-root: unmount / remount SYSTEM in TWRP mount menu (System was not mounted when I got there so, I mounted, unmounted and remounted)

6. install gapps (arm64) (pico, for me)

7. install Magisk.zip (20.0+)

8. Wipe CACHE and DAVLIK

9. Reboot into system

The unit then proceeded to reboot twice and then get me past the Google splash screen and into LineageOS 17.

The install gapps is crossed out as it produced a "Setup Wizard Keeps Stopping" error that would not go away. I guess that will be my next challenge to overcome.

Like I indicated, while I have computer skills, this mobile stuff is still a bit of a mystery to me. I can't tell you why this works or even if it should matter. Maybe someone with more skills in the mobile space can chime in and explain it to us.

Give it a shot and let us know if it worked for you, too.
[Pixel C Android Development] followmsi:
I switched from stock gapps to pico gapps package .. as stock was not included before we don't include pico either.

For dragon .. only Pixel Experience ROM does include gapps into ROM.

And Yes .. opengapps for Android 10 are still not considered as "stable".

But with pico package I get less "strange" issues.

Happy New year !
[Pixel C Android Development] followmsi:
Right now I am connected to hidden 5 Ghz WiFi network .. works the same like on Pie before.

DHCP server is your router .. no idea what's wrong for you.

Mac address gets partly randomized .. should not prevent you from connecting to 5ghz network.

Happy new year !
[Pixel C Android Development] followmsi:
Tested clean install and dirty install (but from older backup) .. no issues.

You may remove pin/pattern before update and set afterwards again.

Sorry for your problems .. december patches are still not merged - also strange issues with dirty upgrade.

Happy new year !
[Pixel C Android Development] followmsi:
Twrp FBE message is due to updated twrp sources .. just ignore the message.

We do not support encryption on dragon for the moment.

You may try bitgapps for arm64. .. does not include setupwizard ..

Again .. I am not able to make opengapps stable .. we all need to wait for proper working packages.

Happy new year to you as well ..
[Pixel C Android Development] brackenhill_mob:
Happy New Year to you too, and thank you for keeping our Cs alive!

I hear what you say re DHCP but the router is clearly registering an address and it is being received by the C otherwise I would not be able to use a non-Mesh SSID (which is coming from the same router). Something weird is going on but I can live with it ;) I'll monitor this as your newer versions appear and report back. Also the router will get a new OpenWRT update soon...

---------- Post added at 12:26 PM ---------- Previous post was at 12:22 PM ----------

I'm using this on all my devices. I've had no problems with this unlike OpenGAPPS which is flakey at best. Recommended
[Pixel C Android Development] narse:
Happy new year to you. Thanks for continuing to support the Pixel C - problems are to be expected, just happy to be able to run newest software on my tab.

I mainly use my Pixel C for emails, web browsing, shopping, video's and casting and I am sure it is running better now than it ever did with the official firmware.

Thanks again.
[Pixel C Android Development] xda_jm:
So - is there a place where we could have links to the gapps that can be used? Currently, one can't download (At least I can't) gapps for arm64 and Android 10 or does

"Switched to opengapps pico version (BETA 12/09) as I have too many "strange" issues with opengapps stock version."

mean it is alrady inside the ROM?
[Pixel C Android Development] Alxoom33:
No, No, No! Gapps must be flashed separately! They are not part of the Rom.

Most, including myself have been flashing the stock Gapps until December. Apparently, the stock version includes a Pixel launcher overlay component that causes fc's of the Turbochet launcher. The pico gapps do not include that component.

Use google search engine to find the latest Open Gapps beta version for Android 10 I believe they are hosted by sourcefourge.
[Pixel C Android Development] xda_jm:
Got it. Retried it, and this time it worked with the beta gapps. Cheers :)

Even did a dirty-flash (Not formatting data) when going over form PixelExperience. Smooth experience :)

Cheers
[Pixel C Android Development] Alxoom33:
I'm glad it worked out for you. However, if you experience any issues, I suggest a nice clean factory data wipe.
[Pixel C Android Development] xda_jm:
I'm one of these very old Linux users (from when the kernel was 0.07p11 times). I actually never wiped my data-directoy on my linux machines.

Eventually I delete a configuration directory for a specific application, and this is the reason I prefere keeping the data directory if I can.

But thx for the advice. In case that happens (which it does not so far), I'll keep that in mind.
[Pixel C Android Development] netherhigal:
On either of the December update versions, I cannot get the battery icon on the status bar to change shape or show percentage. This has been the 26th clean install, then 20th clean install, and back to 26th for a clean install. On all 3 installs the relevant settings could be changed but were not reflected on the status bar. It is very minor but useful to have.
[Pixel C Android Development] Thug Life of the France:
The ROM isn't sideloading correctly.

It says "pre-kitkat sideload" and then says " failed to read command, fails on the tablet as well...

Oh man, I hate TWRP so much, it's buggy as hell and doesn't do the trick for me, never did, prefer Philz and CWM days

So for now this tablet will become a paperweight (again) oof
[Pixel C Android Development] Alxoom33:
Have you been updating TWRP? [MENTION=5480152]followmsi[/MENTION] uploaded at least 3 unofficial updates.

---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------

I have been experiencing screen tearing issues occasionally. What happened is my browser freezes and half the screen reboots and shows the Lineage boot animation.

I need to maually reboot to recover. Just fyi.
[Pixel C Android Development] netherhigal:
I had the half-screen reboot issue, though only while trying to set up the google account features initially. When loading with only AOSP features I did not encounter that one. I could brute force my way through reboots by letting it finish rebooting, continuing the process partially on the left screen, then putting the screen to sleep, and turning back on from there would have the whole screen back in sync. It did take about 4 tries to brute force through the whole setup, but I have not had the half-screen freeze since then. Just adding more details to this as well.
[Pixel C Android Development] Everio9000:
I tried several times install Gapps but it's impossible. I flashed LOS17 and it works perfectly. The problem is with Gapps. I tried with Pico-Gapps, Nano Gapps, etc but problems comes. I mounted and remonted System all the time with every Gapps, but nothing. Same problems flashing last version of Magisk.

I don't know what I'm doing wrong but I follow carefuly each step always....I guess : )

---------- Post added at 10:21 PM ---------- Previous post was at 10:15 PM ----------

Did you "Swipe to Start Sideload" before type sideload commands? The message you said appears when you try flash any sideload zip without swipe blue bar to really enter to Sideload.
[Pixel C Android Development] followmsi:
Strange gapps issues .. also for me.

You may try other gapps packages .. like BitGapps .. etc.

Like mentioned before I do use (not integrate) pico opengapps for the moment .. and have still some issues.

But less as with stock version before.

For me the problems appear espically after new install due to ROM upgrade .. like today.

Sorry .. can't help you better here .. maybe lineage-17.1 is running smoother :)

Cheers
[Pixel C Android Development] followmsi:
Android 10 - January 2020

Beginning with December updates Lineage has started new branch .. lineage-17.1

lineage-17.1-20200108-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> January 2020 (10.0.0_r23)

- 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] Markeee:
Can someone please confirm issue free dirt flashing with this latest build and maybe post how they did it ?
[Pixel C Android Development] followmsi:
From first page .. :p

Upgrade from previous lineage-17.0 builds:

1. Boot into TWRP

2. Wipe SYSTEM only !

3. Install ROM.zip

4. WORKAROUND for Android 10 system-as-root: unmount / remount SYSTEM in TWRP mount menu

5. install gapps (arm64)

6. install Magisk.zip (20.0+)

7. Wipe CACHE and DAVLIK

8. Reboot into system

Lineage is working on related changes for ROM installer .. next build should have "automatic" re-installation of gapps and magisk .. if installed before.

The same way like it was in Pie before.

Cheers
[Pixel C Android Development] muerte33:
The dirty flash seemed to work fine for me, but I got an initial screen I have not seen before on my Pixel "C" with this latest ROM and the 12/9/2019 pico beta gapps.

What does the "Choose what to allow exchange services to access" mean after I reboot the new ROM?

I denied access to them all, and everything seems to work OK for now?

Thanks!
[Pixel C Android Development] ipdev:
It is a communication error, adb will fallback to older (pre-KitKat) method when sideload connection is not found.

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

The device has to be in sideload mode to use adb sideload.

Few things to try.

Enable sideload on the device and wait a few seconds, then run the adb sideload command on your computer.

Disconnect and reconnect the usb cable and try again.

- Using adb you can start TWRP sideload from you computer using adb shell.

adb shell twrp sideload will start TWRP sideload on the device. You can run this command as soon as TWRP is booted, you do not need to touch or swipe anything on the device.

Great option if you are running a device that has TWRP touch issues. ;)

adb shell twrp sideload
adb sideload NameOfFile.zip

You can try a different version of TWRP. (Older or Newer)

Check your adb/fastboot version and try an older/newer version.

You can grab the newest from developer.android - Link

Cheers. :cowboy:
[Pixel C Android Development] Markeee:
Ok followed your above instruction been running this rom for a couple of months

Dirty install and clean install both not working for me on this 01/08 build getting a Pixel and Trebuchet launcher would load keeps stopping error lucky I made a backup of 12/26 had to restore it
[Pixel C Android Development] Alxoom33:
Thanks, everything flashed great. I'm up and running on 17.1. And pico gapps and your 12/20 dragon kernel.

Thanks,
[Pixel C Android Development] jamesthedisciple:
Followed instructions above, working great.

Thank you.

Magisk manager is saying an update of magisk is available. Will this install properly through the manager or should download and install using the "system unmount/remount procedure" in TWRP?

---------- Post added at 03:26 PM ---------- Previous post was at 03:22 PM ----------

I seem to remember a bug with Trebuchet and Pixel launcher clashing over a file or 2 a couple of pages back.
[Pixel C Android Development] EnginEAR:
Gesture Navigation

Finally! I was waiting for full gesture nav support... Thanks much!!!
[Pixel C Android Development] Alxoom33:
Thank you [MENTION=5480152]followmsi[/MENTION]! This LOS 17.1 version flashed w/o issue with pico gapps and is working well!

Is there a camera app that will work with 17.1? I notice there was none in the app drawr.

Thank you!
[Pixel C Android Development] gumarn:
Hi thank you for providing this rom for pixel c tablet.

Overall I really like this rom.

I Just noticed following (tested with lineage-17.1-20200108 and lineage-17.0-20191226):

1. Settings for Status Bar: Battery Indicator

Battery status style->changes have no effect

Battery percentage->changes have no effect

2. Turn On Display from standby->strange changing animation if Ambient Display is enabled in Status Bar. At first black block on the left side, than on the right and than it's gone; tested with screen lock none and screen lock Swipe. Though ambient display is unavailable within Display Settings.

3. No proper WebView Support. Only Android System WebView/AOSP WebView is supported even if Chrome is installed. See url: opengapps.org/blog/post/2016/10/06/nougat-webview/: Check following links for WebView Provider Patches url: github.com/opengapps/opengapps/wiki/Notes-for-Android-7.x (Sorry I'm not allowed to post Links as I'm new to XDA)

4. Black Screen/only sound without video on Netflix (while Amazon Prime does work) if Night Light is turned on; tested with both lineage kernel and unicorn-xceed kernel. I don't know if it has something to do with Widevine L1 DRM because on my android Smarthphone with Widevine L3 DRM Night Light works.

5. SELinux->Deactivated ->It would be nice if it would be Permissive mode or Enforcing mode

6. System Updater does not work, Only manual update through twrp

Translation:

1. Display Settings->Tap to sleep and Wake on plug->German translations are missing.

2. Location Settings in Status Bar->German Translations are missing

3. Reading Mode, ADB over network, Ambient Display, Caffeine, Heads up in Status Bar->German translations are missing

Additional:

-With open_gapps-arm64-10.0-nano-20191209-BETA.zip Digital Wellbeing App force-closes very often with Trebuchet configured as launcher.
[Pixel C Android Development] QuantumSingularity:
Yesterday I've dirty flashed the latest version over the early-december version. (Only System formatted).

Everything works well. No problems so far.

Only one app doesn't start: De Volkskrant App ( https://play.google.com/store/apps/details?id=be.persgroep.android.news.mobilevk ).

Also on earlier versions of this ROM it didn't work.

On my Android 10 OnePlus6 it works well.

Is there a way to debug what is causing the crash of the app?

Version: 2010-01-08

Gapps: 2019-12-09 Opengapps Beta ARM64 Nano-Version

No Magisk/root.

Language: us_english

Region: nl

Cleaned: Dalvik/Cache and cache of the app.
[Pixel C Android Development] pierrebe:
Hi. Disable ambient display and Netflix will work. Known bug.
[Pixel C Android Development] followmsi:
Thanks for reporting ..

Except for the Netflix black screen issue you describe (general) open issues from lineage-17.0/17.1.

Yes, they are still not ready with Android 10.

Sorry, I will have not the time to forward your findings, You may contact core team directly.

Also there are a lot of issues with opengapps BETA packages .. still not stable.

If I find the time for Android I will work on device related problems only.

Cheers
[Pixel C Android Development] followmsi:
I have OpenCamera and Footej Camera installed.

Need to check on clean install .. when time is left.

"stock" camera2 is located in /produc/priv-app now .. not /system/priv-app anymore.

Cheers
[Pixel C Android Development] followmsi:
No time to check this now .. just going thru XDA only.

Did this app work on lineage-16.0 ?

Did you test smaller pico gapps .. or BitGapps too ?

We will need "logcat" of the app crash.

Cheers
[Pixel C Android Development] Alxoom33:
Yes, I found the camera2.apk I installed the Open Camera and Footej Camera apps. Worked initially and when reopened had issues. Something's not compatible.

Thanks,

Edit: In Open Camera Settings, I changed the Api to from stock Camera to Camera2 api, rebooted and Open Camera now works. See photo below.

I uninstalled Footej Camera, as I am satisfied with one working Camera app. Please let me know if there is a way to get the Pixel Camera app to work with LOS 17.1. I tried installing the Google Camera 7.2...for Arm 64 devices from APK mirror, it fc as soon as I open the app.

Picture taken with Open Camera on my Pixel C, running LOS 17.1. The reflections are due to my living room window. View attachment 4925105
[Pixel C Android Development] rauhut:
Installed new ROM leaving OpenGApps / Magisk / Nova Launcher on same versions that I used before and dirty flash installation worked successfully this time. However, on first boot (only) I saw blinking icons and controls (but not when apps or settings were launched) followed by split-screen reboot reported by [MENTION=4100646]Alxoom33[/MENTION] on #1497. Noticed this also on the 1226 version now and then but was not able to reproduce, likely it happens more often when the device boots for the first time after power on (it's always the left side of the screen showing half of the LOS boot animation while the right side is frozen, turning screen off and on again with power button after boot is finished solves the issue).
[Pixel C Android Development] Markeee:
Same issues after several attempts finally got it installed
[Pixel C Android Development] followmsi:
Tested clean install .. camera2 appears and is working.

No .. Google Camera is not working .. maybe old versions work.
[Pixel C Android Development] followmsi:
Pls test new build from today .. just dirty install over current installation.

opengapps and magisk will be automatiicaly re-installed.

Just wipe cache and reboot to system ..
[Pixel C Android Development] followmsi:
Android 10 - January 2020 - Part 2

Lineage has merged battery icon .. finally :)

As well they have adjusted ROM installer .. opengapps and magisk will be automatically reinstalled .. like in Pie before.

For this build I have used hwcomposer from Team Mokee .. may improve strange issues after boot.

Needs more testing.

Tested with Magisk 20.3 and opengapps BETA pico package (2020-01-12) ..

lineage-17.1-20200113-UNOFFICIAL-dragon.zip

Changes:

- New HWComposer -> Thanks to Team Mokee

- 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] EnginEAR:
Butter

Smooth!

Thank you so much!!!
[Pixel C Android Development] Alxoom33:
Dirty installed with System wipe. Gapps and Magisk were not retained and did not boot-up. Perhaps I was not supposed to wipe System??

Once installed pico gapps 1.12.20 booted fine, and installed Magisk seperately.

Havn't used much, but keep getting GMail fc's. Curious what would happen if I flash Stock version of these open gapps?
[Pixel C Android Development] followmsi:
No... Do not wipe system !

The addon scripts are on /system partition.

ROM installer will use scripts to reinstall current version of opengapps and Magisk.

Wipe system to update opengapps version.

To update Magisk just flash boot.img before Magisk installation.

Cheers
[Pixel C Android Development] gumarn:
Thank you for your reply, I didn't know that these are general open issues from lineage 17/17.1.

I would forward them upstream but I don't know where and I don't know how to connect to core team.

According to wiki.lineageos.org/bugreport-howto.html only bug reports for official builds should be reported though this is an unoffical port and I also don't know how to report bugs for development tree of not released lineage versions like 17.0/17.1.

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

->fixed, wellbeing could be used now without force-closes
[Pixel C Android Development] Alxoom33:
Thank you! Fixed my Gmail issues.

The Open Gapps "Stock" package did not work. Both Terbuchet and Pixel launches fc'd. Re-flashed with thePico gapps package and working nicely![emoji38]
[Pixel C Android Development] Alxoom33:
I just found out that 17.1 is SEL permissive. Did you know that? Was 17 SEL permissive, as well?View attachment 4926049
[Pixel C Android Development] gumarn:
I'm unsure about this point. Lineage Trust still says SELinux deactivated(that's the information I checked with older builds and the newest one), Root Checker Pro says SELinux Permissive (tested with the newest build)
[Pixel C Android Development] muerte33:
That was easy!

Thanks FollowMSI!

Must have worked because after I rebooted the system, Google Playstore told me Netflix wanted to update, and it installed the current version 7.39.0 build 23 34648
[Pixel C Android Development] Alxoom33:
Tablet has been working great on LOS 17.1. Thank you!
[Pixel C Android Development] nnirvana:
Oops, I did wipe system and was stuck on the startup (I was using the 010820 version). What remedial measures can I take? Do a completely clean installation? Thanks for any suggestions in advance!
[Pixel C Android Development] nnirvana:
Could you please share a link to the OpenGAPPS Pico that is compatible with the latest 0113 ROM? I tried many versions (including the latest one) but it won't work. Thanks!
[Pixel C Android Development] gumarn:
This build

URL:sourceforge.net/projects/opengapps/files/arm64/beta/20200115/open_gapps-arm64-10.0-pico-20200115-BETA.zip/download

and the December beta build worked for me
[Pixel C Android Development] nnirvana:
Thanks for the info. But I tried this (but failed as it says "No ro.build.id") and the December beta and several earlier ones, it just won't work. I did a clean install, wiped system and data, installed the ROM. Everything went well until I install the opengapps, and I was stuck every time at startup (lineage logo loop). Any hints?
[Pixel C Android Development] shadow_empire1:
I get the same error...

Any idea, to make this upgrade process consistent... getting really annoying to have this situation.

Anyway, thx to all the developers to make this rom possible!!!

Edit: Flashing with open_gapps-arm64-10.0-nano-20191209-BETA.zip gives no error, but Lineage boot logo is looping....
[Pixel C Android Development] followmsi:
Just let them finish their work :)
[Pixel C Android Development] followmsi:
Both .. Lineage-17.0 and Lineage-17.1 are permissive.

On Android shell you can run "getenforce" (as root) to get current status.

You can switch "setenforce 1" to make "enforcing mode" .. "setenforce 0" ot make "permissive mode".

Like german translations .. some code needs to be changed from Lineage team .. shoud show permissive not just deactivated.

Just be more be patient !

Cheers
[Pixel C Android Development] followmsi:
https://xdaforums.com/android/software/pa-gapps-continuation-t3098071
[Pixel C Android Development] Alxoom33:
Thanks, that works. Although I have noticed that the rom reverts to SEL permissive upon rebooting. Is there a way of keeping it SEL enforcing?
[Pixel C Android Development] Ulunyth:
Hi,

Got the same pbm. Then I saw that there is that : https://sourceforge.net/projects/op...ps-arm64-10.0-pico-20200116-BETA.zip/download :)

Enjoy !