yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Alxoom33:
Well it's not Open Gapps. I use the Open Gapps ARM 64-Super package with no problems. I also have used the smaller packages, as well.

This Rom comes with Trebochet Launcher. Not the Google Now Launcher, which is not compatible with this build.

I like to use my purchased version of Nova Launcher Prime, which works well on this rom. If you want to use the Google Now launcher, you will need to download a similar "Pixel Launcher" from the Google Play Store or other source that is compatible with this tablet and the Lineage 16.0 ROM.

I don't think that you did a complete Data Reformat of your internal memory, which is probably contributing to your problem. Otherwise, you may be restoring data, somehow, that is incompatible. Have you been restoring data or apps with Titanium BU or a similar program?
[Pixel C Android Development] Monazite:
The lockscreen file exists in /data/system/locksettings.db and other nearby xxx.db or xxx.key

If you modified system partition (or other partitions related to system) and you still set a password, system will crash after you reboot and enter the password.

This problem exists even in stock ROM. Probably related to Pixel C's original Chrome OS kernel.
[Pixel C Android Development] followmsi:
The TWRP flashable zip below will remove all your patterns and passwords .. etc.

Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip

Just run via TWRP and reboot into system.

Not sure if and when the keymaster/encryption issues will be solved.

We have nvidia and not snapdragon .. not all is working the same on all platforms.

We may rely on Oreo blobs which are not working correctly on Pie.

Have updated the known issues too.

- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.

- 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.

Cheers
[Pixel C Android Development] followmsi:
The TWRP flashable zip below will remove all your patterns and passwords .. etc.

Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip

Just run via TWRP and reboot into system.
[Pixel C Android Development] cmit37:
It just happened to me again. It must be a bug.

I was watching this video with the Youtube app when the tablet crashed and I wasn't able to log back into it:

https://youtu.be/mXnCJr7PtY4

The fworkaround was Boot Recovery, Advanced, File Manager and I renamed the following files.

/data/system/locksettings.db

/data/system/locksettings.db-shm.bkup

On next restart the lockscreen was removed so I could login again. thanks

Is anyone else getting these crashes while watching Youtube?
[Pixel C Android Development] barbara-luise:
After flashing the 30/01 los 15.1 nightly update I get a "vendor image mismatch" error at startup. How can I fix this error?

Any help is appreciated.
[Pixel C Android Development] mightywhites29111971:
You need to update to the lastest vendor img. It should be in the download section of the OP for 15.1.
[Pixel C Android Development] barbara-luise:
Thank you.

You mean downloading and flashing the vendor.IMG that I found here:

https://drive.google.com/file/d/1RjZXtndjSHK1GCgttcXl1Y11Suib_mLj/view?usp=drivesdk

If I flash vendor.img via twrp, will this erase all personal data on my device?

Sorry for the questions, but I've never done this before.
[Pixel C Android Development] mightywhites29111971:
Just flash it through TWRP making sure you change the file type from zip and then flash to the vendor section. It will not wipe anything.
[Pixel C Android Development] barbara-luise:
Thanks. It worked! :good:

Just for the sake of interest: why is the required (stock) vendor.img not part of the ROM installer?

Further, is it recommended or even required to manually update the bootloader, radio or anything else from time to time? If so, where can I find the required files / images?
[Pixel C Android Development] followmsi:
Vendor.img is not part of the ROM installer due to legal reasons.

For dragon there is no radio ... etc.

But bootloader should be updated !

Fastboot commands will do this.

All the files are in last stock ROM ..

https://developers.google.com/android/images#ryu

If you had latest stock google ROM installed before you should have latest bootloader too.

Cheers
[Pixel C Android Development] barbara-luise:
Will face unlock work out of the box in official lineages 16 for pixel c? Or will I have to install a certain gapps package to get it work? If so, which one?
[Pixel C Android Development] Alxoom33:
The stock Google Bootloader for the Pixel C has not been updated for a while. Even with the February 2019 update, the Bootloader version is still 7900.126.0 the same as in the October 2018 factory update.
[Pixel C Android Development] followmsi:
February 2019 - lineage-15.1

The Google February 2019 changes for dragon device and kernel have been pushed to Lineage github today.

The next official build will require February vendor.img !

Right now it's not clear by when Lineage will merge the general February security updates.

I have just uploaded the February 2019 vendor.img to gdrive folder too. (Oreo only)

Enjoy :p
[Pixel C Android Development] barbara-luise:
What is the recommended order for flashing the vendor.img: Before or after flashing the ota update?
[Pixel C Android Development] followmsi:
Installation order is not important.

If you boot with old vendor.img you get vendor missmatch warning.
[Pixel C Android Development] followmsi:
Android Pie - February 2019

lineage-16.0-20190206-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> February 2019

- Google kernel updates -> February 2019

- Latest LineageOS changes for Pie

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

Enjoy ..:p
[Pixel C Android Development] Alxoom33:
Working great so far. New Lineage 16 and new kernel. Thank you!
[Pixel C Android Development] d3l1:
Lineage OS 16 is working great so far. I have come across two things that concern me ATM. Maybe you can help me here.

- pixel launcher won't start, it's constantly crashing when I select it as the launcher (installed through opengapps)

- copy text from the task switcher doesn't seem to work. I can't seem to select any text. Is there some restriction regarding this feature?
[Pixel C Android Development] Alxoom33:
I use Nova Prime launched. Perhaps if you flash the Pixelfy.zip it may fix things. However, I would first ask for confirmation from [MENTION=5480152]followmsi[/MENTION]. The file is in the drive with the Lineage 16.0 zip.
[Pixel C Android Development] zennoux:
Does this include the kernel found here: https://xdaforums.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591, or do I have to install this separately?
[Pixel C Android Development] followmsi:
No idea when pixel launcher will be fixed.

There is no "pixelfy.zip" on gdrive folder .. never been.

You can test Pixel Experience ROM .. they did include pixel launcher into ROM.
[Pixel C Android Development] followmsi:
No .. to be installed separately.
[Pixel C Android Development] Alxoom33:
Yes, I think that is what I meant to refer to. I had saved a Pix3lfy.zip magisk module next to a of the Pixel Experience rom and confused the two.

I take it from your comments that Pixel Experience is a separate rom, not a mod to be flashed on top of Lineage 16.0.
[Pixel C Android Development] CoreyMck:
Correct. That ROM is here https://xdaforums.com/pixel-c/development/rom-20190116-t3890641. It works great and is the ROM I have been using but it has been discontinued.
[Pixel C Android Development] d3l1:
No problem, I don't want to use Pixel Launcher, I was just wondering why it crashed all the time. I use Nova on my phone but on the tablet I prefer Niagara.

What I do want to use is the new Pie feature to copy&paste text from within the Task Switcher. This doesn't seem to work, although the pill-guestures work just fine.

This is also the main reason why I asked for Pixel Launcher, because it seems that you can enable/disable this c&p feature in the Pixel Launcher settings: https://www.androidcentral.com/how-turn-suggestions-pixel-launcher-android-p
[Pixel C Android Development] feiwolf2008:
installed smoothly. one problems that i set a pattern key. and settings kept shuting down. now i can't turn off the screen lock anymore. any advices besides restore? its just so annoying. or will the bug fixed in next release?
[Pixel C Android Development] followmsi:
Updated OP ..

Known issues:

- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.

- 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.zip to remove pattern/pin or password.

Not sure by when this issue can be fixed .. if possible at all.

Cheers
[Pixel C Android Development] NYCHitman1:
You can only use copy/paste from Recents with Pixel Launcher because it contains the back end code callbacks for the feature.
[Pixel C Android Development] Alxoom33:
Thank you! This pin/pattern remover has saved me a lot of work, several times.

Any idea if it would work on my Pixel 2 XL?
[Pixel C Android Development] b8842dc0:
I've just upgraded to lineage-15.1-20190213-nightly-dragon-signed.zip. After rebooting, I got the vendor mismatch error. Then I remembered [MENTION=5480152]followmsi[/MENTION] mentioning, back on the 5th about there being a new vendor image. So, I downloaded the required vendor image and flashed it. However, I still get the same error, upon reboot. I ran the following command that, I believe, shows that I have it correctly imaged:

dragon:/ $ getprop | grep fingerprint

[ro.bootimage.build.fingerprint]: [google/ryu/dragon:8.1.0/OPM8.190205.001/5175807:user/release-keys]

[ro.build.fingerprint]: [google/ryu/dragon:8.1.0/OPM8.190205.001/5175807:user/release-keys]

[ro.vendor.build.fingerprint]: [Android/aosp_dragon/dragon:8.1.0/OPM8.190205.001/5175807:userdebug/test-keys]

Any ideas?

---------- Post added at 03:02 PM ---------- Previous post was at 02:11 PM ----------

I've fixed my vendor mismatch issue. I downloaded the vendor image that [MENTION=5480152]followmsi[/MENTION] had uploaded to google drive. The md5sum from that image, was not the same as the md5sum of the image that I downloaded and extracted from here: https://dl.google.com/dl/android/aosp/google_devices-dragon-opm8.190205.001-bbaaa660.tgz:

md5sum of the one I downloaded from Google: e6e7060cfa2e3a66830d3967499f526a

md5sum of the one downloaded from [MENTION=5480152]followmsi[/MENTION]'s google drive: c973e63a5e717b2e313738c91fa1a052

I fixed the vendor mismatch by flashing [MENTION=5480152]followmsi[/MENTION]'s version. But, any ideas why those two images wouldn't match?
[Pixel C Android Development] followmsi:
You are welcome ..

Yes, should work on all devices.
[Pixel C Android Development] followmsi:
You posted you own answer ..

[ro.build.fingerprint]: [google/ryu/dragon:8.1.0/OPM8.190205.001/5175807:user/release-keys]

[ro.vendor.build.fingerprint]: [Android/aosp_dragon/dragon:8.1.0/OPM8.190205.001/5175807:userdebug/test-keys

The complete string has to match .. not just the numbers.

Cheers
[Pixel C Android Development] zjcjgjj:
The kernel wakelock is too many.what can i do？
[Pixel C Android Development] ardevd:
Has anyone figured out a way to run a custom ROM on the Pixel C with a locked bootloader? It doesn't seem like Google has implemented their own bootloader standard. It seems like only the Green and Red state is supported. No Orange (locked bootloader, dm-verity success, but with non-stock OS).
[Pixel C Android Development] followmsi:
Chromeos bootloader is a bit special .. e.g. boot.img has to be signed .. etc.
[Pixel C Android Development] ardevd:
Yeah, I know. Hence my question if there's any way to boot a custom ROM with a locked bootloader on the Pixel C at all. If anyone knows a way I'd really appreciate some tips.
[Pixel C Android Development] followmsi:
Never tried this .. just have a try yourself. :)

Sign and flash own build system.img, recovery.img and vendor.img and relock bootloader.

May adjust fstab to do "verify" again.

Cheers
[Pixel C Android Development] ardevd:
Yeah I already tried. Not sure how I can sign the vendor image though since it's prebuilt. (I'm running aosp though)

Not sure what fstab modifications would be necessary but if you have any pointers, that would be awesome.

Also, if you're so inclined, please feel free to try this too :) perhaps you'll have better luck than me.
[Pixel C Android Development] followmsi:
If you build on pure AOSP the verify is already included.

https://android.googlesource.com/device/google/dragon/+/refs/tags/android-8.1.0_r61/fstab.dragon#6

Sorry, no time to play with this stuff .. actually I don't see any benefits - just problems only.

Yes .. this way you could skip 30 seconds waiting time from bootloader.

You still have the risk of bricking your devices .. especially with our "famous" Chromeos bootloader.

Cheers
[Pixel C Android Development] ardevd:
There are plenty of benefits. With an unlocked bootloader you're saying goodbye to pretty much all the boot related security mechanisms, including the entire verified boot chain. The standardized support for verified boot has green, yellow, orange and red states. See https://source.android.com/security/verifiedboot/boot-flow. The Pixel C doesn't implement the standard verified boot. It has a custom implementation and may not have support for verifying an alternate operating system like the Nexus 5X, 6P and Pixel phones. Locking the bootloader with an alternate OS generally doesn't work anymore with the exception of Pixel phones and the last generation of Nexus phones since it does more than simply disabling flashing and formatting via fastboot. However, I'm still hoping there might be a way to get it working on the Pixel C.
[Pixel C Android Development] followmsi:
Yes - with unlocked bootloader you loose security but you may get more freedom at the same time.

Even it would work on dragon device .. I guess there will be still some limitations left.

As I never tried to run custom ROM on locked bootloader I do see a lot of potential problems ..

- root of trust .. which keys ?

- "freezing" and signing all images (including gapps ?)

- if you alter system (gapps installation) you break dm-verity, as we change hash values.

- if you change config file on vendor partition you will change hash values too.

- what about custom recovery .. still working on locked bootloader ?

etc.

Maybe there are simple solutions for my open questions/points .. but I have not the time to study/test them.

Actually I still buy new devices only - if bootloader is unlockable - in some official way.

Google, xiaomi, Nokia and some more vendor do still have open bootloader philosophy - which I do like !

Cheers
[Pixel C Android Development] Alxoom33:
I am on Lineage 16.0. Sometimes, when I put in my pin the tablet reboots and goes back to the lock screen. I usually flash the zip that you provided to be able to open my Pixel C. Any idea why that happends, it appear that the code is recognized.

Any other potential solution that you have come accross, besides flashing the pin/pattern remover?

Thanks,

Alan
[Pixel C Android Development] followmsi:
As you know - the Pin/pattern issues are known since a while .. updated OP accordingly.

Dragon device seems to use some custom libs/config for keymaster and encryption.

There is no new Nvidia device or similar devices to pull (working) libs for Android Pie.

Maybe we find another solution to make it working on Pie.

For the moment - No other solution than skipping pin/pattern completely.
[Pixel C Android Development] frauhottelmann:
I am using pattern for a while now and I had no issues at all ?

I have a 4x4 pattern, but I also only restart the tablet after I've installed an update.
[Pixel C Android Development] Alxoom33:
These issues come and go...
[Pixel C Android Development] keviiinn:
Just noticed, when using Skype, my front facing camera stops working after a few minutes. I think it's got something to do with the stock camera app. Latest LineageOS 16. Anyone else?
[Pixel C Android Development] locuturus:
I haven't tried Skype but I have noticed this with Duo. The camera seems to run longer than it did a few versions back but it does still lock up after a minute or so while using Duo.
[Pixel C Android Development] Alxoom33:
New March Android updates are out.
[Pixel C Android Development] followmsi:
March 2019 - lineage-15.1

The Google March 2019 changes for dragon device and kernel have been pushed to Lineage github today.

The next official build will require March vendor.img !

Right now it's not clear by when Lineage will merge the general March security updates for Oreo.

I have just uploaded the March 2019 vendor.img to gdrive folder too. (Oreo only)

Enjoy :p
[Pixel C Android Development] followmsi:
Android Pie - March 2019

lineage-16.0-20190308-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> March 2019

- Google kernel updates -> March 2019

- Latest LineageOS changes for Pie

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

Enjoy :p
[Pixel C Android Development] Alxoom33:
Flash with gapps, and the new kernel. Easy peasy! Thanks!
[Pixel C Android Development] Monazite:
[MENTION=5480152]followmsi[/MENTION] will you push dragon to official channel?:o
[Pixel C Android Development] locuturus:
Happy to report that the network traffic monitor option works now :)

Also I find the tablet to be smoother when using noop or sioplus instead of the default cfq but that might just be me (shoutout to Kernel Audiator).
[Pixel C Android Development] followmsi:
Dragon is official Lineage device since Nougat.

Due to the known issues on Pie it's not sure if and when dragon will switch to lineage-16.0 officially.

As well we use custom drm_hwcomposer repo .. needs to be freshly synced by lineage - for all devices.

Not sure if we break other devices with our reverts/changes .. needs testing and approval.

Actually I doubt as not much devices using it at all .. but all this kind of "adminstrative" issues/tasks are still open too.

As I have less and less time left for Android I don't want to promise anything.

Hope you have a better understanding ..

Cheers
[Pixel C Android Development] :
Great work Follow... It's all in the details. Lineage 16 may need a little more polish in some places but... It looks like it has the potential to be a great release! It's great to see someone recognising and realising the potential in the Pixel C. You'd think someone in Google would see things the same way? Keep up the good work Follow!
[Pixel C Android Development] Vartom:
All this stuff, all these parts can be added to the proprietary drivers in the vendor section. The remaining fixes are already in LOS-16.0.
[Pixel C Android Development] followmsi:
Yes .. we can use prebuilt drm_hwcomposer and move into vendor blobs.

The repo does not change a lot.

What about data encryption/decryption .. does it work now ?

As well the "unstable" Pin/Pattern/Password unlock.

I still have Pattern problems after boot, if I try to unlock too early.

And no time to look into the problems ..
[Pixel C Android Development] Vartom:
I have not tested it so carefully.
[Pixel C Android Development] francoscala:
Nice room!

Thanks for your work! I think that there is a bug, when I activate the old type of navigation bar the squared button disappear! If I use the setting with it at right and the other buttons at left!
[Pixel C Android Development] unfnknblvbl:
are we able to disable gesture control yet?
[Pixel C Android Development] frauhottelmann:
Gesture control?
[Pixel C Android Development] unfnknblvbl:
Yes, gesture control.
[Pixel C Android Development] frauhottelmann:
Sorry I meant: which gesture control are you talking about?
[Pixel C Android Development] unfnknblvbl:
You know, with having a "pill" in the bottom bar that you perform magic, arcane gestures on, instead of actual buttons that do the same thing only much faster and easier.

You can disable the gestures and bring back the buttons with a couple of ADB commands on a Pixel phone, but they don't work here for some reason.
[Pixel C Android Development] frauhottelmann:
You can disable it in the settings: settings -> system -> gestures -> swipe up on home button

BTW: I think the "pill" was one of the most stupid decisions Google could make. Litteraly every action you perform takes longer with the pill than a simple tap of a button...
[Pixel C Android Development] unfnknblvbl:
Oooo thank you. I agree wholeheartedly too, but I doubt Google will back down on it anytime soon. They really like sticking to their stupid decisions, like removing TabletUI..
[Pixel C Android Development] emureddu43:
Hi, I need someone to help me. This is the issue: I was going to connect a usb flash drive with the otg as usual but I noticed the pixel c doesn't read the flash memory anymore, it just recognise the drive connected and shows me the partition even in all the other file manager apps but when I go to open it, it says like Impossible to read (or show me 0 bytes ) I even tried to mount it with stickmount but same result, even with other flash drives and other otg adapter same result. If I try to read it through TWRP it works just fine so it's all working fine not hardware related, since it was working before lineage os 16 (I was on stock 8.1 with follow msi kernel) l. I will be so grateful to anyone who will be able to solve the problem. Thanks
[Pixel C Android Development] gettinwicked:
Sooo, I need up to update my C to the latest image, but, I haven't since the September 6th, 2018 release. I can dirty flash this, right? Then I assume flash kernel, magisk, then GAPPS again? There are a TON of pages since I was last here, so, I apologize since this question has likely already been answered. I just don't have time to go through them all. Please and thanks!
[Pixel C Android Development] frauhottelmann:
Don't know about magisk, but you only need to flash Lineage. Gapps are not necessary. It wouldn't hurt either if you flash all of them ?
[Pixel C Android Development] Alxoom33:
Read the OP! If you are updating to 16.0 you are probably going to need to format your memory and flash clean. You might want to take the time read the forum, since you don't want to brick your C.
[Pixel C Android Development] gettinwicked:
I read the OP. See where I said I haven't updated since last September? I'm on 16, just needed to update to the March version. I got it done, all good.
[Pixel C Android Development] Alxoom33:
Excellent [emoji106] Did you flash updated gapps?
[Pixel C Android Development] gettinwicked:
I did! ROM, GAPPS, Kernel, Magisk. Working good! Smoother than the September build for sure.
[Pixel C Android Development] emureddu43:
Do you know something concerning my issue?
[Pixel C Android Development] frauhottelmann:
How are your flash drives formated? Lineage is a bit picky at the moment.

Get rid of stick mount or other helpers that interfere with USB. They are definitely not needed.
[Pixel C Android Development] emureddu43:
Flash drives are fat32, I don't have any other mount helper program. I tried paragon exFAT/NTFS which I use to read an external HDD in exFAT format and that one is working well so I assume it is not working just with fat32.
[Pixel C Android Development] derAndroidler:
If I use the 16.0 unofficial, can I dirty flash to official LOS 16.0 later, when it will be released?
[Pixel C Android Development] keviiinn:
I did this, but the multitasking button doesn't come back. It just moved the back and home buttons to the left...