yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] godard_6699:
Guys, weird issue, but one that's causing me a lot of grief. After a shutdown and restart I cannot log into the device. It accepts the password, screen goes black, and then I'm back at the login screen. The only way I've resolved this is to boot into recovery and do a wipe. But then I have to setup all over.

I've seen the same for both the initial and this latest release. Any one seen the same, or know what might be happening. I'm using Nova launcher of that's a possible cause.
[Pixel C Android Development] followmsi:
Lineage-16.0 ?

If you reboot just wait a few seconds longer before you enter password.

If you are too quick it will not work.

Similar issue with pattern.

If it's not working .. reboot via power menu and wait a bit longer ;)

Hope to find the root cause ..

As well you can always remove the password/pattern via twrp and reboot into system without lock screen.

Just one of 1000 examples..

https://xdaforums.com/android/software-hacking/remove-lockscreen-recovery-t3530008
[Pixel C Android Development] godard_6699:
Rebooting and waiting a bit before login worked. Thanks so much! :D

Edit: yes, Lineage-16.
[Pixel C Android Development] Ski-lleR:
Ive the same problem, and i'm not using nova launcher. The only solution i found for now is to disable password. Ive faced multiple screen goes black with the necessity to wipe data and have to reinstall everything.

Edit : and waiting before auth doesnt work for me
[Pixel C Android Development] bmbaker:
Great stuff :svetius:

Is ok to dirty flash this over the previous version?

Cheers
[Pixel C Android Development] followmsi:
Yes ..installer will take care of gapps and magisk.
[Pixel C Android Development] followmsi:
As said above .. wipe data is never required as you can deleted password/pattern only.

Pls check the link!

Sorry, no better help as waiting a bit longer after reboot.
[Pixel C Android Development] Burakki:
Hi,

at the moment I'm using the android 9 aosp rom. I wonder, which one works best between aosp 9 and lineageos 16?

What changes in terms of autonomy and performance? Beyond customizations, why prefer this or the other rom?

thank you all
[Pixel C Android Development] followmsi:
The unmapped gralloc is since Oreo and before .. no worries.

Pls use latest opengapps package ...

Or try the gapps from here.

https://xdaforums.com/showpost.php?p=77829052&postcount=340

No ideas about TB .. just keep your Oreo /data partition.
[Pixel C Android Development] keviiinn:
I'm not seeing the Oct vendor img in the downloads folder.
[Pixel C Android Development] followmsi:
Just open your eyes :p

It's inside the folder since a few days. ( vendor_OPM8.181005.003_Oct-2018.img )

You may need to switch to "desktop" view in your browser.

As mentioned several times .. all the monthly Nougat/Oreo stock vendor.img are coming from Google !

I just unzip and upload to have "complete" Oreo ROM at one place , as a "service".

Here is the original source for the vendor.img :

October build:

https://dl.google.com/dl/android/aosp/ryu-opm8.181005.003-factory-d5eea995.zip

All buillds:

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

Cheers
[Pixel C Android Development] mcole79:
Quick question

Anyone know if this will include Bluetooth Hands Free Profile? I don't know what Google was thinking, but they released the Pixel C without that capability. Kinda craps on the Fi "calls from all your devices" thing when the only way to do a call from the Pixel C is if you use it as a speakerphone.

Thanks! Glad we have awesome folks making awesome mods to play with!
[Pixel C Android Development] Reuben_skelz92:
Is there night light on this rom!?
[Pixel C Android Development] followmsi:
In LOS it's called "livedisplay".. here you can switch to "night".
[Pixel C Android Development] Reuben_skelz92:
Yeah I know about live display. Just like the toggle in quick settings. The pixel xl version had that too
[Pixel C Android Development] xda_jm:
Why did you remove it? Or in other words, what were the reasons???

Did not yet install the latest release, habe to go to Utrecht for work and don't do that kind of changes just before leaving ;)

Also - when you say:

"install ROM"you mean the "Lineage-14.1-...UNOFFICIAL-dragon-followmsi.zip" file?

"Install current stock vendor.img (flash via TWRP)": You mean the "vendor_N2G47...img" file?

I prefere to ask one time to many ;)

Cheers
[Pixel C Android Development] followmsi:
Like for all other devices too .. we need to exclude vendor blobs.

Also for legal reasons .. etc.

Yes, like you describe.

Choose image installation within TWRP to install vendor.img file.

If you have the current vendor.img already installed you don't need to install it again.
[Pixel C Android Development] Reuben_skelz92:
Latest ROM running awesome man:) buttery smooth and stable.

Worth it for livedisplay alone...always wanted to be able to adjust the screen calibration slightly on my pixel c:)

And as an added bonus night light is in quick settings now:)
[Pixel C Android Development] followmsi:
You are welcome ..
[Pixel C Android Development] xda_jm:
Just FYI - I just went through the entire process, an as someone already said here, it worked without an issue.

Only thing I needed to do, was to get the latest TWRP on it, as without it, I couldn't decrypt the system partition, hence no installation.

Thx again :)

Now - hopefully they will add it all to the official repository soon :D
[Pixel C Android Development] followmsi:
You are welcome ..

System partition is not encrypted - never.

Only /data partition.

Did you got a "no os" warning from TWRP ?

In latest 3.1.1 version is a fix included .. Fix reboot when no OS is present

https://github.com/omnirom/android_bootable_recovery/commit/0afc1fdc4846a3c36cea4488ef76b218101425a7

Hope this helps ..
[Pixel C Android Development] xda_jm:
You are right, it was the data partition.

Thing is, I copied the image/zip files to /sdcard using adb.

Under the old version (3.1.0) I could not access these files. With 3.1.1 I could as it asked for the decryption code.
[Pixel C Android Development] followmsi:
Encryption/Decryption has been tested on 3.1.0 version.

Several times .. and confirmed as working.

Also tested on 7.1.2 already.

Anyway ... now it's working for you.
[Pixel C Android Development] :
> 6. install SuperSU.zip and/or Magisk.zip

[MENTION=5480152]followmsi[/MENTION] I installed SuperSU and root access via ADB is working fine. But where are the options "Apps only" and "Apps and ADB"? Under "Developer options" --> "Root access", there are only 2 options:

[IMG="Root access"]http://i.imgur.com/6a7ML6j.png[/IMG]

[IMG="Tablet status"]http://i.imgur.com/RfCWLps.png[/IMG]
[Pixel C Android Development] followmsi:
Have seen this too .. not sure if it's a bug or if it's related to LOS su add-on.

For me it's Apps and ADB but I can't change it to apps either.

Supersu still grant root access for apps ?
[Pixel C Android Development] frauhottelmann:
The setting is for the su add-on not for SuperSU
[Pixel C Android Development] :
[MENTION=5480152]followmsi[/MENTION] Not permanently, only for a maximum of 15 minutes.

---------- Post added at 02:32 PM ---------- Previous post was at 02:26 PM ----------

[MENTION=592660]frauhottelmann[/MENTION] What su add-on are you referring to? I didn't find any su add-on files in the Google Drive folder?: https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg
[Pixel C Android Development] frauhottelmann:
https://download.lineageos.org/extras
[Pixel C Android Development] followmsi:
No, pls download su add-on from LOS website.

15 minutes sounds like config issue ;)
[Pixel C Android Development] :
1. What is the URL of this LOS website?

2. Did you use the LOS su add-on instead of the SuperSU solution? Or did you use both?
[Pixel C Android Development] LSS4181:
Nope still not working. Magisk won't show up (su from adb shell simply tells me Permission Denied).

Camera still FC, TB still won't install.

Oh... it seems something's odd: when I install Magisk 17.2, it sees the kernel as a ChromeOS boot image (rather than stock boot image, maybe I got it wrong), but still, Magisk Manager won't show up.

Also, a catch is that, if I install ROM then Magisk before the first boot, it'll first stuck on Google logo and restart, then on second boot it'll boot fine. If I only install ROM first, boot, then go to recovery and install Magisk and boot, it'll boot without any problem.
[Pixel C Android Development] frauhottelmann:
I installed it just with Open Gapps and it also rebooted at the first boot.

Also, I cannot encrypt it. It jumps to the encryption screen for a second, then reboots and stays in a boot loop forever. When I then go to twrp it seems that it isn't encrypted. Which kind of makes sense, because the encryption process was way to short ?
[Pixel C Android Development] LSS4181:
The exact reason why it would reboot on first boot is unknown... the ROM (or Android Pie) doesn't look like it's complete yet, as Camera isn't working.

But I'm curious about this...

It seems to suggest me to do a dirty flash, which I'm not quite certain as I'm on RR-O, not Lineage 15.1, something might break. Could it be the Pie isn't creating the data partition correctly for the time being? (Which might explain why apps aren't installing and why Magisk isn't showing up even after installation, since Magisk is systemless and takes up data partition instead).
[Pixel C Android Development] followmsi:
Thanks for testing encryption .. has not been tested yet.

I have updated the first page ..

Known issues:

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

- Screen Unlock: If you set Pattern or Password the Screen unlock does not work correctly.

- Workaround: On frresh 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.

The issues are related .. no idea about the root cause yet.
[Pixel C Android Development] followmsi:
Yes, Pixel C does have a chromeos signed boot.img.

Have seen this "double boot" issue once .. will see what can be done.

Don't see any negative impact either.

I do recommend clean install, like mentioned on first page.

But .. maybe it's more "dirty" to "play" with TB as keeping the existing Oreo data partition. :)

I did test lineage-16-0 clean install not on current version .. if there is a problem on clean install now - we will need to check.

The uppgrage from last month release went smooth.

Stock camera and OpenCamera are still working fine.

Maybe you wipe system too and start again from scratch ..

Just uploading a new version .. 20180812.

You may try this version ..
[Pixel C Android Development] followmsi:
Another ROM ..

lineage-16.0-20181012-UNOFFICIAL-dragon.zip

Changes:

- NotificationBar overlay -> thanks to [MENTION=6556709]Vartom[/MENTION]

- minor changes

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

Enjoy ..:p
[Pixel C Android Development] Monazite:
Official keyboard still can't connect, wrong PIN. ?
[Pixel C Android Development] frauhottelmann:
Works for me...
[Pixel C Android Development] LSS4181:
Did anyone get Magisk 17.2 working on Lineage 16.0?

Tried the latest version. No difference, Camera still crashes.

It seems TB didn't install was due to it unable to find anything that could provide root, as TB requires root. I tried sideloading F-Droid (doesn't require root) and it installed.

The core issue is that official Magisk 17.2 is not working (neither is 17.1). Did anyone here managed to get Magisk installed and usable on Lineage 16.0?

EDIT: It seems I need to sideload Magisk Manager myself. On Lineage 16.0 Magisk Manager couldn't be installed by the zip for some reasons. As for TB, it seems to be just simply incompatible with Pie at present.

After installing Magisk Manager it is able to recognize my Magisk installation.

EDIT 2: It seems for some reason Package Manager couldn't open TB's apk file, and I was finally able to install it by sideloading it through "adb install". Strange. So now the only problem is the stock camera.

EDIT 3: Now here's the issue with "Pixel Setup" having trouble with Google Play Services (using NYCHitman1's gapps package from that post), and I could not get my Pixel Keyboard detected for pairing.
[Pixel C Android Development] frauhottelmann:
Very nice. The quick settings are actually useful now ?

Is it a bug that the notifications are centred, but the quick settings open where ever you swipe down with your finger? Or is Google just going nuts? Or they don't care about android tablets any more ?*♀️
[Pixel C Android Development] Monazite:
They don't care about Android tablets any more. Chrome OS is main product now.

Google added expand animation when you click a notification. And to realize this animation, they centered notifications.?
[Pixel C Android Development] followmsi:
Yes .. not much love for Android tablets anymore.
[Pixel C Android Development] followmsi:
Hope you sorted out your issues now .. gapps for Android 9.0 are still considered as beta.

Next clean install testing I will check camera again.
[Pixel C Android Development] LSS4181:
After sorting out those issues, most of the things I'm using are working fine. The issues I'm having are as follows.

1. Stock camera is not working. This is on clean installs. (testing needed)

2. Magisk works, but requires manual installation of Magisk Manager after flashing the zip from recovery, which should be automatically installed by the zip (on Oreo devices this still works). It's possible that the issue may be on Magisk's side but I couldn't find any related reports on Magisk's issue tracker.

3. Occasional inability to sideload certain packages from Package Installer, but the "adb install" method still works and the apk installed this way functions correctly (possibly a filename/permission-related issue, as when I use "pm install" from a root shell it complained about unable to open the apk file in question).

4. Pixel Setup seems to have issues as system reports as "having trouble with Google Services". Pixel Keyboard couldn't be detected or paired for now as it might require a successful install/configuration of Pixel Setup in order to function (maybe it should get fixed once Gapps leaves beta).
[Pixel C Android Development] rroohh93:
once the pixel slate is out, do think is possible to port chrome os to pixel c?
[Pixel C Android Development] Monazite:
No. Pixel Slate is on x86_64 platform, while our Pixel C is on ARM64.
[Pixel C Android Development] NYCHitman1:
Good ol' Intel vs. Tegra lol
[Pixel C Android Development] Sam-X-:
Anyone else experience the problem that homescreen icons loose their caption when the tablet is rotated into landscape?

It is fine in portrait mode.

I am on latest LineageOS 15.1.
[Pixel C Android Development] mediawiz:
I just installed the latest build of LineageOS 16.0. As always, I really appreciate the great work being done developing ROMs for Pixel C!

With this particular ROM, most things seem to work well. The 2 issues that I continue to see are:

- LineageOS 16 (for Pixel C) does not detect hidden WIFI networks (ones that do not broadcast SSID). This is true even if I manually add the network. (I normally keep my wireless N network hidden. My Pixel C doesn't detect/connect to that network unless I un-hide it.)

- LineageOS has an option to move the navigation buttons (in the System -> Buttons -> Layout menu), either to the left or right side on the bottom of the screen. (I prefer the Nav buttons on the right side because I'm right handed.) The "normal" and "left-leaning" settings work properly, but the "right-leaaning" setting doesn't work. (The Nav buttons are on the left bottom of the screen.)

Those are the only issues I have detected with the 20181012 build thus far.
[Pixel C Android Development] followmsi:
When you add connection manually .. Advanced settings of wifi connection - select "hidden".

Maybe confirm security warning.

Navbar needs to checked .. will take longer.

Thanks
[Pixel C Android Development] followmsi:
When you test camera ..which gapps package did you install ?

Did you install stock gapps package ?
[Pixel C Android Development] LSS4181:
Actually when I tested camera I was on a freshly installed system without anything else, including Gapps, since I need some extra steps to be able to connect to Google, and without a proper connection I'd be stuck on Google's Setup Wizard.

I only installed Gapps after I made the tablet able to connect to Google to perform further setup. I'm now using NYCHitman1's package, although I haven't tested it afterwards as I did not have an immediate need to use it. Does camera somehow require Gapps components?
[Pixel C Android Development] followmsi:
I was asking if you may have installed stock gapps package and removed prebuilt camera with Google camera ?

Latest Google camera may not work due to missing HDR support on dragon .. .etc.
[Pixel C Android Development] frauhottelmann:
I am using OpenGapps nano. The stock camera doesn't get removed or replaced. It doesn't work...
[Pixel C Android Development] followmsi:
You did clean install ?

Other camera apps (opencamera) are working fine .. Just stock camera app is not working ?
[Pixel C Android Development] frauhottelmann:
Yes, clean install. Don't know if other apps are working, I'll try. Not that I care ? I have never used the camera anyway...

Edit: I can of course provide logs if you need and tell me what to do ?
[Pixel C Android Development] followmsi:
Yes, please test other camera apps (open camera) too and provide logcat.

Still wonder why my camera apps are still working fine .. clean install "should" make no difference in this case.

Thanks

EDIT:

Was able to replicate the issue .. indeed stock camera does not work.

But Google camera and open camera do work.

Will need to check in detail.
[Pixel C Android Development] LSS4181:
I don't use Google camera. The stock camera doesn't work on fresh installs.

Everything else's fine for the time being except Pixel Keyboard (which I suspect the Pixel Setup Wizard needs to be completed in order to function, but at present it's having trouble with Google Play Services and crashes after wifi selection screen).
[Pixel C Android Development] followmsi:
Made a fix for Camera2 .. the app somehow requires codec config files at "old" location in /system/etc.

If you copy the 3 files from /vendor/etc/ to /system/etc and reboot Camera2 should work again.

For next build ..

https://github.com/followmsi/androi...mmit/a6c9a34f23f66990f6b37716ff0e8fa5c75e8a6f

Cheers
[Pixel C Android Development] Alex93917:
Working great, thanks :)
[Pixel C Android Development] frauhottelmann:
Can you make a new build with this and the new security fixes?
[Pixel C Android Development] followmsi:
Yes, we can :)

But first we need to wait for lineage team .. they "promised" Sunday.

Pls have a look yourself ..

https://review.lineageos.org/#/c/LineageOS/android/+/231968/
[Pixel C Android Development] alphamode:
I think they finally worked out the issue and merged it
[Pixel C Android Development] followmsi:
Android Pie - November 2018

Lineage did play with Gallery app .. it's not part of this ROM.

Should be part of the next ROM again.

lineage-16.0-20181114-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> November 2018

- Fix for Camera2

- Other minor changes

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

Enjoy ..:p

EDIT:

Bluetooth has been broken due to this patch ..

https://review.lineageos.org/#/c/LineageOS/android_hardware_broadcom_libbt/+/226447/

This patch will be fix it again .. but not yet merged:

https://review.lineageos.org/#/c/LineageOS/android_hardware_broadcom_libbt/+/234177/

I took this patch and made a new vendor.img only.

vendor_lineage-16.0-20181114-UNOFFICIAL-dragon.img

Just flash via TWRP as vendor image and reboot into system.

Afterwards Bluetooth will work again.
[Pixel C Android Development] Rox598:
Any idea with this screen issue [MENTION=5480152]followmsi[/MENTION] ? I'm sure it's something to do with nightlight/livedisplay that the screen just goes all dark and I have to press and hold down the power button for a forced reboot to get the screen back on.
[Pixel C Android Development] Dethsesh:
This Pie ROM working great for me. I get no video for Netflix, but it's 100x better than stock that I was running.
[Pixel C Android Development] xda_jm:
Why would the Video/Netflix not work?

it works on LIneage 15.1 here...
[Pixel C Android Development] Dethsesh:
I get constant "Bluetooth keeps stopping" with this rom. Did a clean install a couple times, no luck.
[Pixel C Android Development] followmsi:
For me Netflix is working fine .. lineage-16.0 from today.

But Bluetooth has been killed by lineage. :(
[Pixel C Android Development] followmsi:
Not related to clean install.

Yes, Bluetooth has been killed.

Latest commit from libbt-vendor killed it.

Either we replace libs ... But better I will make new ROM.
[Pixel C Android Development] followmsi:
Don't know and don't have this problem you describe .. if my screen goes dark/sleep I can always wake by power button.

No need to force reboot.

I do not use NightDisplay nor livedisplay.

More details and logs please ..
[Pixel C Android Development] Rox598:
Problem with logs is since the screen is off I can't generate one through development options. I'm 100% sure it's a problem with the night light / live display though
[Pixel C Android Development] followmsi:
Pls install the vendor.img to fix Bluetooth ..

vendor_lineage-16.0-20181114-UNOFFICIAL-dragon.img

Just flash via TWRP as vendor image and reboot into system.

Afterwards Bluetooth will work again.
[Pixel C Android Development] followmsi:
Pls use usb debugging and cable to pull logs !

Any steps to replicate your issue ?

Are you talking about certain apps .. like here ?

https://xdaforums.com/showpost.php?p=76298705&postcount=550

As said before .. more details please.
[Pixel C Android Development] 4oo4:
For anyone else confused by the last few nightlies, it looks like they are switching back to actual Nightly builds for 15.1:

https://www.androidpolice.com/2018/...lds-14-1-nougat-will-switch-monthly-releases/

https://github.com/LineageOS/hudson/commit/19b2b7a3deb84d90b79868c2c2ea901143936463
[Pixel C Android Development] Dethsesh:
Awesome, ROM working great! Thanks man, this tablet feels revived all of a sudden.
[Pixel C Android Development] mediawiz:
Bluetooth app continually crashes on latest build (2018-11-14) of LiniageOS.
[Pixel C Android Development] WangAaron:
Here is the error I get after updating to the latest nightly build of 15.1

a vendor image mismatch has been detected. typically this means your vendor image is out of date xxxxxx

Everything else works with no issues, it pops up every reboot. What should I do? Reflash the factory vendor or wait for the next build? Thanks.
[Pixel C Android Development] followmsi:
Yes .. November vendor.img is required since beginning of this week.
[Pixel C Android Development] followmsi:
Yes, pls read above and install vendor.img from above .. or wait for the weekend - will make a new build.
[Pixel C Android Development] WangAaron:
Thanks you for the reply! I'll wait.LOL
[Pixel C Android Development] followmsi:
The vendor image is for lineage-16.0 but not for lineage-15.1. :)
[Pixel C Android Development] WangAaron:
I found a november vendor image from your google drive and flashed into my Pixel C ,and the problem turns out to be solved.Nothing pops up anymore.Is it universal? Since it runs perfect on LOS15.1...
[Pixel C Android Development] followmsi:
Like mentioned on first page ..

For lineage-15.1 you will need google stock vendor.img.

I put a copy into the gdrive folder too.

Changing monthly .. maybe November 2018 is the last one anyway :)

For lineage-16.0 there are no stock vendor.img existing and the ROM contains it's own vendor.img.

Nothing to do for lineage-16.0.

If you go back to lineage-15.1 you will need to re-install matching Oreo vendor.img too.
[Pixel C Android Development] WangAaron:
Got it! Thank you very much!