yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Dagazz:
Thank you. That is a nice easter present :)

Different to the last update, this time the update worked as it should. (GApps and Magisk are working fine; no need to delete system partition again.)

Have some nice days and stay healthy, too.
[Pixel C Android Development] Elektron60:
When i made a twrp backup i see a red line that say: "Cannot decrypt FBE device".

This is only on one device and the backup is running normal.

What does this mean? Can i fix it?
[Pixel C Android Development] tschmid:
Do you have a pin/pattern whatever?

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] Elektron60:
My device is unencrypted but has a pin set.
[Pixel C Android Development] shadow_empire1:
Any idea...?

Thx
[Pixel C Android Development] followmsi:
https://www.the***********.com/install-viper4android-android-10-guide/

Actually XDA is "killing" the link .. Google will be your friend.
[Pixel C Android Development] followmsi:
It's already included :)

Settings -> System -> Mulituser

We are A-Only system-as-root using first-stage-init .. I prefer the Magisk naming "2SI" (2 stage init)

Anyway .. your root explorer must support this stuff.

Just boot into TWRP to replace files -> "/system" is now in "/system/system/"

system-as-root (SAR)

For gapps installation issues and more information ..

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

Cheers
[Pixel C Android Development] followmsi:
https://xdaforums.com/showpost.php?p=81461951&postcount=703
[Pixel C Android Development] shadow_empire1:
Thank you! Missed it...
[Pixel C Android Development] dev-da:
I have TWRP 3.3.1-2 installed.

I did WIPE >

- Format D

- Advanced Wipe > Dalvik + System + Data + Internal Storage + Cache

I installed lineage-17.1-20200410-UNOFFICIAL-dragon.zip

Unmounted System + Data + Cache

Mounted System + Data + Cache (again)

Installed open_gapps-arm64-10.0-pico-20200412.zip

Installed Magisk-v20.4.zip

Reboot

BUT I stuck at the lineage boot screen... after a long time the system reboots into recovery (twrp) again.

Some ideas?
[Pixel C Android Development] zmw:
disable the TWRP app.
[Pixel C Android Development] locuturus:
For what it's worth, my Chargie has actually worked all day today (for the first time). I am on version 1.20.18, not sure if that's a beta or not, and I reset the app data today before trying again. They have been updating almost every other day and it seems to maybe be good now. I have not tried auto connecting or anything and honestly I'm afraid it'll stop working if I disconnect lol.

Chargie has always been good on my Pixel 3a and a mixed bag on my work phone (Samsung S9). Pixel C just flat out failed to work at all (before). So I think they are starting to figure out how to play nice with more Android implementations.
[Pixel C Android Development] dev-da:
Thank you, thank you, thank you!

I have TWRP 3.3.1-2 installed.

I did WIPE >

- Format D

- Advanced Wipe > Dalvik + System + Data + Internal Storage + Cache

I installed lineage-17.1-20200410-UNOFFICIAL-dragon.zip

Unmounted System + Data + Cache

Mounted System + Data + Cache (again)

Installed open_gapps-arm64-10.0-pico-20200412.zip

Installed Magisk-v20.4.zip

Reboot (without Installation of TWRP App)

System starts :)
[Pixel C Android Development] Elektron60:
My Chargie is now running fine. I use a Pixel C as a permanent running Info panel and Chargie swipes brave between 70 and 71 percent.
[Pixel C Android Development] mediawiz:
For the most part, this ROM seems to work well, but Instagram keeps crashing!
[Pixel C Android Development] Elektron60:
I have a randomly toggeling mac on one device. How can i fix it?

The wrong mac is 00.90.4C.11.22.33
[Pixel C Android Development] hernil_:
Thanks!

I flashed the zip with TWRP and it seemed to have worked just fine. However the Wireguard application still reports using the Go userspace backend. Can anyone confirm getting the kernel module working with that kernel? Any obvious things I might have missed? :)
[Pixel C Android Development] EddieK23:
Loving this ROM over the other ones I've tried like stock and Pixel Experience, feels way more stable and battery life is already better on LineageOS 17.1

Only hoping that the camera issue gets fixed at some point and then this would be perfect.
[Pixel C Android Development] nnirvana:
Thanks. I've read that post before and tried the instructions step by step, but unfortunately it won't work. Thanks, anyway. I think I can live without V4X, since this ROM works perfectly in all other respects.:)
[Pixel C Android Development] muerte33:
I agree, if the camera ever gets fixed, this ROM with the Pixel "C" are about the best $200 android tablet solution!
[Pixel C Android Development] xda_jm:
FYI - just experience, for the first time, the keymaster issue (latest ROM_20200410 release).

While trying to put the pin_remover zip onto the tablet, I plugged the USB-Cable in, and as my computer was not allowed, the adb devices listed an "unauthorized" device.

Selecting the USB configuration on the locked screen asked me to enter my PIN. I tried, and I could enter the system fine.

So - kind of workaround without having to go into TWRP.

All that a part, this is the best ROM for this Pixel C. Especially the battery charge level unlinked from Kernel speed configuration is amazing!

Thx again to all who make this ROM happen!
[Pixel C Android Development] followmsi:
Just download the pin_remover zip file directly onto your device .. no need for USB cable.

Below are the relevant lines of the pin remover ..

delete("/data/system/password.key");
delete("/data/system/pattern.key");
delete("/data/system/gatekeeper.password.key");
delete("/data/system/gatekeeper.pattern.key");
delete("/data/system/locksettings.db-wal");
delete("/data/system/locksettings.db-shm");
delete("/data/system/locksettings.db");

Cheers
[Pixel C Android Development] sharukins:
Hey guys,

I was wondering if anyone else has issues installing Netflix? I did a clean install of twrp and LineageOS 17.1 including OGapp nano.

Now Play store says that my device is not compatible with Netflix...

I also tried using magisk & magisk manager, but that didn't do the trick.

Any help would be greatly appreciated.

Thanks and kind regards
[Pixel C Android Development] tschmid:
Download it from apkmirror

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] sharukins:
well i downloaded the app from netflix directly and it says "device not supported". I guess that happens for the one hosted on apkmirror as well?
[Pixel C Android Development] tschmid:
Tryed this:

https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-7-55-0-build-23-34841-release/

PS. No, had the same problem, this from apkmirror worked

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] xda_jm:
Running netflix over here. But had it installed a long time ago and always upgraded the app over time.

Currently running:

open_gapps-arm64-10.0-pico-20200303

lineage-17.10-20200410 image

Magisk-v20.1

In Magisk advanced settings, I have "Preserve AVB 2.0/dm-verify" active. All the rest disabled.
[Pixel C Android Development] followmsi:
Android 10 - May 2020

Just the regluar Android security updates ..

lineage-17.1-20200506-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> May 2020 (android-10.0.0_r35)

- Patched framework/base to support microG

- Latest LineageOS changes for Android 10

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

Enjoy :p
[Pixel C Android Development] golvellius:
Ok Thanks for all the work ...

I have some issues , when i am using youtube and watching videos .. then suddenly it blocks the pixel-c and sound also it is blocked ... Sometimes it will restart automatically ..

I am going to try this new realease for checking ..

But i have this issue with old both releases .. Could it be a problem of the rom or maybe my tablet?

Thanks for all
[Pixel C Android Development] golf60:
Try a complete fresh install.
[Pixel C Android Development] golvellius:
hi..

i have remove lineage and install original android 8 rom..

i will made some stress test .. i thnik i have my pixel on faulty state ...

Later i will check lineage .. thanks

good work
[Pixel C Android Development] QuantumSingularity:
Installed the 20200506 version.

Formatted /system /cache /dalvik

Installed rom + opengapps pico

rebooted and running.

No problems found. [MENTION=5480152]followmsi[/MENTION] Thank you for the update
[Pixel C Android Development] Burdus:
Hi, tried a fresh install (comming from stock).

- TWRP 3.3.1-2

- Lineage-17.1.-20200506-UNOFFICIAL-dragon.zip

But after installation (delete data, cache, dalvik) the Lineage OS boot animation shows up for 30-60 minutes, and that the tablet reboots into TWRP.

Any advice?
[Pixel C Android Development] m+a+r+k:
Yes, follow the instructions on page 1 :)

Did you format the data partition (don't just delete it) and install gapps after ROM?
[Pixel C Android Development] Burdus:
Yes, did it in the order on the first page, so:

1. Boot into TWRP

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

3. Install ROM.zip

4. install gapps (arm64)

5. install Magisk.zip (20.x+)

6. Wipe CACHE and DAVLIK

7. Reboot into system

Maybe I missed some, let me try again. (Used open_gapps_arm64-10.0-stock-20200509.zip)
[Pixel C Android Development] Alxoom33:
Try a smaller Gapps package. I use full. But Mini is good also
[Pixel C Android Development] Burdus:
Tried the micro gapps, and formatted the data portions also. Still no luck.

Rebooting to recovery after the Linage boot animation is there for a few minutes.

Any other suggestions?
[Pixel C Android Development] Burdus:
Thanks! Tried Mini and it look like that did the trick. Also I didn't install the TWRP Manager at the end of the installation of the zip files.

So 1 of those 2 did it! :)
[Pixel C Android Development] Alxoom33:
Did you check your MD5's for the LOS App and Gapps? you may have a bad dl.
[Pixel C Android Development] schoerb:
How can I fix the stopping videos in Chrome, Vivaldi and Brave?

With Firefox Eversthing ist eine.
[Pixel C Android Development] Alxoom33:
That's great, I think Mini gapps did it. Not installing TWRP Manager at the end, dosn't do much at all. I have it installled, but it's just an app.

---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------

Do't watch videos. Loll

I like using Firefox beta for videos. Works best, imo.
[Pixel C Android Development] ipdev:
Hi. :)

Actually installing the TWRP app can cause a boot failure on some devices and seems to be mentioned more recently in some threads.

Seemed to originally affect a few devices, not sure if I have seen it mentioned in the PixelC threads.

Not exactly sure why (Never looked to much into it) but, allowing the TWRP app to install results in booting into recovery instead of system.

Maybe it's found it's way over to PixelC now?

My backlight is borked again and I haven't had time to try and get it to turn on.

When I have the time (and if it actually turns back on) I'll clean flash and see if it follows the pattern of other devices.

Then again, mine developed an odd issue with flashing boot images in TWRP so, not the best test device to try on though.

Side note:

I'm not sure about OpenGapps at the moment, I haven't been following it lately.

Mini should share most of the install as micro and above though, might be another overlay added though.

Good to hear OpenGapps Full works. :)

Cheers. :cowboy:
[Pixel C Android Development] Alxoom33:
Good to know about TWRP app. I personally have not had any problems with it, at least so far. I've been using the full version of gapps without any problems. Stock version seems to be a little too large and causes random reboots. Thanks!
[Pixel C Android Development] sxg75:
Question - when anyone say camera wouldn't work... does this mean any video app / conferencing app would also not work with this rom?

Apart from camera.... what other issues compared to stock are missing or not working properly? I'd be thankful if someone write a few lines, thanks in advance!
[Pixel C Android Development] Alxoom33:
I was able to get camera to work using [MENTION=5480152]followmsi[/MENTION]'s guidence. Search this thread. However, it's not dependable, the camera will fc in the middle of use and will require a reboot to work again.
[Pixel C Android Development] brackenhill_mob:
Missing gps.conf?

Running the May 2020 release, I can't get a GPS lock.

Poking around, I discovered that there is no /system/etc/gps.conf file (there is a debug file in that folder) and I cannot create one because it is a read only system

[MENTION=5480152]followmsi[/MENTION] please can add this to the next release or tell me/us how I can add this to the system myself (which I really need as my gps.conf file is specific to my country and very fast to lock)

Thanks
[Pixel C Android Development] Elektron60:
No GPS HW?
[Pixel C Android Development] apascual89:
lol it seems like you really want me to take over lol
[Pixel C Android Development] followmsi:
Very nice .. you just did take over !

Welcome to the new maintainer of RR. [emoji1]
[Pixel C Android Development] jeffyca:
i've notived that when using the builtin browser with lineageos and the pixel c keyboard, when using the address bar to perform a search and hitting enter, the browser moves the "selection/mouse" to the search bar in the middle of the page and it doesn't perform a search on the entry in the address bar. this only seems to occur when using the pixel c keyboard(physical keyboard), as the virutal keyboard and hitting enter when searching from address bar works fine
[Pixel C Android Development] ToldYouSo:
Kernels I've tried and did not crash:

xceed-9.38_kernel-flasher-5.1-20170426.zip

xceed-9.40-linaro6-lazyflash.zip

tegra-3.18_kernel_dragon_v170526_lineageos-followmsi.zip (older versions also work)

All other xceed, test etc. kernels crash.

Kernels included in latest OMS and RR roms, crash also.

And yes only in LOS. When on stock with these kernels there is no problem at all. I've tried again today with factory image and several kernels. No crash.

It seems to crash on L2TP/IPSec PSK security. Tried PPTP security too and crashes also.

Also just to be clear. I am not using any third party app to make the VPN connection. I only use the VPN settings in Android and make the connection without the use of any app. OpenVPN is always through a third party app I think? I've tried that today using the OpenVPN app and that works fine.
[Pixel C Android Development] ToldYouSo:
Found the setting in the RR version btw. But couldn't find it in LOS, it's not there or I need eye laser surgery again :p
[Pixel C Android Development] YevOmega:
Lol. I was gonna say the same thing. Thank you guys so much!
[Pixel C Android Development] followmsi:
Finally .. :)

https://download.lineageos.org/dragon

https://mirrorbits.lineageos.org/fu...neage-14.1-20170612-nightly-dragon-signed.zip
[Pixel C Android Development] Reuben_skelz92:
Will the official builds differ much to your unofficial ones?
[Pixel C Android Development] apascual89:
Great news! How was the signature thing finally resolved?
[Pixel C Android Development] frauhottelmann:
I am running into error 7 "Can't install this package on top of incompatible data"
[Pixel C Android Development] followmsi:
https://wiki.lineageos.org/faq.html

Installing LineageOS zips in TWRP results in “Error 7”

The most common reasons for this error are:

You are trying to install a build for a different device.*You need to make sure you download the zip for the correct device *and* variant

You are attempting to migrate from an unofficial build to official LineageOS.*A full data wipe is needed if you are coming from something other than an official build of LineageOS.

Your vendor/modem/bootloader is too old (or maybe too new).*Flash the correct stock image for your device, before wiping data and attempting to install LineageOS again. This information should be listed on the device’s wiki page.

You can backup data, wipe it , install official version and restore data again. ;)
[Pixel C Android Development] frauhottelmann:
Yeah I already tried backing up data and restoring it after the installation of LOS, but that resulted in a constantly crashing system ui. ?

Vendor.img should be up to date...
[Pixel C Android Development] followmsi:
Like mentioned above ..

2 changes for chromeos vboot are merged into android_build.

https://review.lineageos.org/#/c/176470/

https://review.lineageos.org/#/c/176468/

This fixes signing on production, as all the required tools are in otatools.zip.
[Pixel C Android Development] followmsi:
Full wipe without restore works fine ?
[Pixel C Android Development] frauhottelmann:
I didn't have the time to check this morning. I'll try it later.
[Pixel C Android Development] followmsi:
It was not the plan to continue unofficial builds.

For OMS version there will be 1-2 monthly releases.
[Pixel C Android Development] followmsi:
Just tested the official one .. confirmed.

Get the same error using my unofficial data partition.

Wiped data and rebooted .. all fine now.

But I still want to find a way to keep my data partition .. even it's dirty ;)
[Pixel C Android Development] frauhottelmann:
There used to be migration builds for CM -> LOS. Can you trigger one on the build server? I migrated my Nexus 5 from CM to LOS that way...
[Pixel C Android Development] followmsi:
https://lineageos.org/Update-and-Build-Prep/

( Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time. )

Not sure if we will get a migration build, I doubt, but I will ask for more details.

After you did the restore of your old data and boot into system again ..

Once you see the "system ui stopped" error message enter following command .. via adb:

adb shell pm grant com.android.systemui android.permission.READ_CONTACTS

This way you can enter system and play a bit more .. still a few permission errors left.

For various applications ..

Will have a look if we can do more here .. most probably not.

The clean and recommended way is still to do a factory reset. :)
[Pixel C Android Development] frauhottelmann:
Thanks, I'll probably restore the whole backup to get it working again. But I can do that if you need a log...
[Pixel C Android Development] m+a+r+k:
The Pixel C doesn't have GPS.
[Pixel C Android Development] brackenhill_mob:
[MENTION=7153555]Elektron60[/MENTION] & [MENTION=5416206]m+a+r+k[/MENTION] that explains it ;)
[Pixel C Android Development] Eurgain:
All very nice -many thanks for your efforts!

I am using lineage-17.1-20200506-UNOFFICIAL-dragon.zip with no patches.

I found one small problem. I always have rotation locked in portrait, but every time I wake it up it is locked in landscape. I don't use any form of lock, but it is the same if I enable swipe. The only way I can get back to portrait is to switch to autorotate, then back to lock once it back in portrait.

Any ideas if this can be fixed?
[Pixel C Android Development] schoerb:
Since yesterday my Pixel C shows rounded corners. I don't know, which app could cause this.

Does anybody have an idea?
[Pixel C Android Development] michie:
Reflash the rom. You probably flashed the gesture navbar height fix V1 which also included some pixel stuff. I updated the fix for just the navbar height in the pixel 10 thread.
[Pixel C Android Development] JLowe:
Dear followmsi,

thank you for your excellent LineageOS transfer for Android10. I am using the latest build Lineage-17.1-20200506-UNOFFICIAL-dragon.zip and it works very well for me!

Is there any possibilty to get the reading mode permanent that it stays after a reboot?
[Pixel C Android Development] schoerb:
Thx, this was the solution!
[Pixel C Android Development] echoIII:
Some of my Bluetooth devices cannot be used, some cannot be found in "Available devices" (eg Logitech R500), some can be recognized but always in the "Pairing ..." state (eg Dualshock4 controller). My Thinkpad bluetooth keyboard is successfully paired.
[Pixel C Android Development] sxg75:
Some DRMbased Apps wouldn't work for me. Sadly... the Rom itself works mostly great... but need restock.
[Pixel C Android Development] narse:
I've been playing around with the new roms, but wanting to use duo in lockdown. What is the newest rom that has a working camera?

Thanks
[Pixel C Android Development] tschmid:
Atm no 10 rom has working camera, were looking for a solution

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] narse:
Do any of the 15.1 & 16 roms have a working camera? I did try the most recent 16 and the camera still stopped working. I have also tried the newest 15.1 and couldn't get it to boot. I was just wondering if any were working reliably before I spend time downloading and installing again.

Thanks.
[Pixel C Android Development] tschmid:
I received the answer that in mokee its working, but its a ten build. Ill do a compare of all codec relevant xml files maybee theres the solution

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] :
Hello there, can anyone confirm if the original magnetic google pixel c keyboard works flawlessly with this rom? Thanks in advance
[Pixel C Android Development] tschmid:
Keyboard not type cover?

Keyboard works fine

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] :
I've meant the original keyboard not the type cover which is nearly nowhere available. Thanks for the replay. Thinking about getting one because my Logitech K380 bluetooth keyboard sometimes doesn't automatically pair properly with my Pixel c which is really annoying. I had this problem also on stock rom
[Pixel C Android Development] OmaeKumiko:
still met keymaster problem on lastest android 10 release
[Pixel C Android Development] dictionary:
For some reason, every 10 rom I flash has weird battery drain and charge issues. Flash back to final stock, then custom 9, no problem. Anything beyond that, and it'll say 100, then take it off charge. It'll drop really fast to 0. Like within an hour. Reboot it reads 0. Plug it in, charge jumps to like 80. It's screwed lol. It's got juice, but it isn't reading it on anything beyond 9.
[Pixel C Android Development] Vartom:
No need to speak for everyone about all the firmware. On my AOSP, I did not see the problems you described with the battery.
[Pixel C Android Development] dictionary:
Pardon? I'm not speaking for anyone but myself. Simply stating, that every 10 ROM I've tried, including yours, has this weird battery glitch. It was fine at first, but then one day the battery ran down to zero. Plugged in to charge, and that's when the wonkiness all started. It's just strange because it only happens on a Q ROM. I thought initially the internal battery monitor was screwed because I let it drain, but it works on 9 ROMs. This isn't a post meant to insult any dev, it was me mentioning my experience, hoping someone had experienced something similar, and found a solution.
[Pixel C Android Development] Vartom:
What kind of charger do you use? I use the charger that comes with the tablet, as soon as it has proved to be the best option of all that I have. Try to use it.
[Pixel C Android Development] dictionary:
That's what I'm using. During the initial time it started to mess up, I was bouncing between two different chargers. I read something about the chargers, and since then I've just been using the stock one. Same issue. I'll deal with it at this point, just strange that this is only an issue with Q ROMs, but stock (laggy) or P ROMs it is okay with. I thought maybe vendor? I dunno
[Pixel C Android Development] Vartom:
Can you make the kernel and system logs immediately after the tablet is rebooted and after the moment the glitch appears? Use the syslog program from Market. Perhaps you have some kind of rare modification of the tablet that requires changes in the system.
[Pixel C Android Development] followmsi:
Confirmed .. need to check this when time is left.