yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] NYCHitman1:
Yeah, there should be zero issues conflicting with surfaceflinger if that revert is picked back.
[Pixel C Android Development] Vartom:
I collected from this repo from this moment.

https://github.com/ARM-software/drm-hwcomposer/tree/4f7dc9b6d7b31fdf94b96307a256c9bbee6cb0b7

Works no worse than Google repo. Plus there are no errors

09-18 20:34:28.154 238 303 W hwc-drm-display-compositor: Acquire fence 54 wait 0 failed (-1). Total time 100
[Pixel C Android Development] followmsi:
Did start a new lineage build just cherry picking this revert.

Hope it's enough to solve this issue .. ;)
[Pixel C Android Development] NYCHitman1:
That's just the drm_hwcomposer with commits from AOSP master and Chromium.
[Pixel C Android Development] Vartom:
Judging by the fact that there is a HWC2 in that repo, I conclude that the error is not in his presence, but in what is a shallow patch or an error with MERGE.
[Pixel C Android Development] Vartom:
[MENTION=5480152]followmsi[/MENTION] [MENTION=2489052]NYCHitman1[/MENTION]

I'm trying to make Treble support. But the system does not start. Judging by the logs there is a problem with the access from library vendors to libraries in the system partition.

Is there a way to configure the assembly to solve this problem?

09-23 20:05:07.145 253 253 E vndksupport: Could not load /vendor/lib64/egl/libEGL_tegra.so from sphal namespace: dlopen failed: library "libc++.so" not found.

..

09-23 20:05:07.461 275 275 E vndksupport: Could not load /vendor/lib/hw/android.hardware.camera.provider@2.4-impl.so from sphal namespace: dlopen failed: library "libhidlbase.so" not found.

...

09-23 20:05:07.542 281 281 E vndksupport: Could not load libutils.so from sphal namespace: dlopen failed: library "libutils.so" not found.
[Pixel C Android Development] NYCHitman1:
Hidlbase and utils are part of vndk. You'll need to create the vndk to call these libraries to build. See here: https://github.com/DirtyUnicorns/android_device_oneplus_msm8998-common/tree/p9x-caf/vndk
[Pixel C Android Development] Vartom:
Thanks, I'll try this.
[Pixel C Android Development] NYCHitman1:
I did say that it was not going to be an easy road, if possible at all. If you're just building vndk-sp instead of the full VNDK package -- it may be OK.
[Pixel C Android Development] followmsi:
Ocotber 2018

AOSP_9.0.0_r10_PPR2.181005.003_dragon-ota-eng.followmsi.zip

Changes

- Google security updates -> Ocotber 2018

- New kernel including the latest Google patches > Ocotber 2018

- Some graphics changes (drm_hwcomposer and libvulkan.so)

- Other fixes (sepolicy and health service ..etc.)

- Disbaled ZRAM

- etc ...

- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)

I have updated Oreo sources too .. but no build this time.

There will be one last AOSP Oreo build -> when Google releases the last official Oreo update.

Maybe October is the last official Oreo update .. we will know in November.

Enjoy ..:p
[Pixel C Android Development] Monazite:
We can receive Oreo updates until December this year, for Google started sold it in December, 2015.

If lucky enough, the updates to June, 2019 is possible as well. Google obtained Pixel C in December, 2017, and according to Nexus/Pixel devices support policy, ‘Pixel phones get security updates for at least 3 years from when the device first became available on the Google Store, or at least 18 months from when the Google Store last sold the device, whichever is longer. ’
[Pixel C Android Development] followmsi:
We will see .. for me personally they can stop Oreo updates now :)
[Pixel C Android Development] Monazite:
There is a strange problem...Pixel C keyboard can't connect and tell me PIN code is wrong...but there's no dialog pops up to let me ender PIN. Any suggestions?
[Pixel C Android Development] NYCHitman1:
Logcat? lol
[Pixel C Android Development] Monazite:
Sorry but i have go back to oreo...
[Pixel C Android Development] LifeAsADroid:
Formatted data in twrp, wiped everything, installed 9.0.0 rom then opengapps full, rebooted.

During initial setup, tablet hangs at "checking for updates" after connecting to home network... Any ideas?

If I skip the network step and try to complete setup without using network it stalls and says "couldn't sign in" as though it is attempting to use network anyway.

Anything I can try different?
[Pixel C Android Development] filjusz:
This is gapps fault. Try nano version or older relase
[Pixel C Android Development] calebcbump:
Ive tried all the current builds of Open Gapps and none of them work... Tve also tried a build from Sep25 an still does not work. Can anyone point me to a build of gapps that actually works?
[Pixel C Android Development] drewski_1:
does AOSP P have Night Light enabled?
[Pixel C Android Development] NYCHitman1:
Of course
[Pixel C Android Development] drewski_1:
cool :good:

It seems to come and go on stock (like current stock 8.1)
[Pixel C Android Development] followmsi:
Yes it's enabled in AOSP and Lineage-16.0

Cheers
[Pixel C Android Development] drewski_1:
same issue here with Oct 7 GApps

will try nano, but see followups that may not help either.
[Pixel C Android Development] redukt:
Have the same issue with all opengapps packages. Can´t setup / sync my device. On LineageOS the same. By deleting the setupwizard folder I´ve lost all syncs bye google services. I´ve tried also MindTheGapps & BiTGapps without results. The setup hangs on "checking for updates". Maybe something wrong with the vendor file?
[Pixel C Android Development] drewski_1:
i installed the ROM and then copied the /system/priv-app/provision/ folder and put that back after flashing GApps and deleting /setupwizard/

am getting some Play Services errors, but syncing seems to be working.
[Pixel C Android Development] redukt:
That sounds pretty interesting. Which gapps / package did you use for it? I didn´t know the method with the provision folder yet. I´ve tried only deleting the setupwizard stuff. So on this side did you try to wipe data / cache of play services?

I will try your "solution" on weekend :)
[Pixel C Android Development] followmsi:
Pls try gapps config file and include Chrome and webview in selection.

Pls try again setupwizard .. does it help ?
[Pixel C Android Development] drewski_1:
Provision is AOSP setup program. Not mine; It was mentioned in Delta GApps thread.

EDIT: and i used OpenGApps Stock package with this process
[Pixel C Android Development] NYCHitman1:
http://nychitman.com/josh/hidden/misc/SimpleGappsMini-arm64-9.x.x-official-Oct2018.zip
[Pixel C Android Development] drewski_1:
notifications always stay centered while the settings are aligned to where i pull down from on the top of the screen.

is this a known bug or something wonky with my setup (as noted previously, i did some workarounds to get past Setup Wizard).

doesn't bother me much, but thought i'd report it.

EDIT: you can also see that the QuickSettings shows 6 icons, but the space is not wide enough for all of them. again, doesn't bother me, but looks funky.
[Pixel C Android Development] Monazite:
It's a common bug related to AOSP Pie. Google never tested Pie on tablet devices. You can post this issue on Google Issue Tracker to let Google fix it.
[Pixel C Android Development] NYCHitman1:
Google isn't going to fix it because they killed off tablet support in AOSP lol
[Pixel C Android Development] Vartom:
fix for QuickSetting

https://github.com/vartom/android_d...mmit/a7701c7c28d63a32184bb590cfc1ec314cf30a2a
[Pixel C Android Development] followmsi:
Cool .. looks really good !
[Pixel C Android Development] LifeAsADroid:
Forgive my uneducated noobie-ness, but how do I implement this? Or is this something to add to the next updated flashable file by followmsi?
[Pixel C Android Development] Vartom:
This is what will be added to the next update from [MENTION=5480152]followmsi[/MENTION].
[Pixel C Android Development] followmsi:
Yes, part of next release ..

I can make SystemUI.apk only .. you need to replace to see the changes.

Will publish it later ..

EDIT:

Here you are ..

PixelC_Pie_AOSP_9.0.0-r10_SystemUI-NotificationBar_SystemUI.apk.zip

It's the SystemUI.apk and "oat/arm64" files only .. you need to manually replace the files.

Boot into TWRP to replace the files.

If you don't want to replace manually yourself .. just wait for next month release.
[Pixel C Android Development] Bleedos:
Did not flash for a long time and got tired of my Pixel C lagging a lot on Oreo so I wanted to try Pie.

Where did you copy "/system/priv-app/provision" from? After flashing the ROM there's no such folder? And there's no /setupwizard/ folder either.

I tried "adb shell find . -name system and got no "priv-app" result...
[Pixel C Android Development] drewski_1:
/provision was there for me after flashing ROM, but before flashing GApps.

did you mount /system partition?

/setup wizard would only be there after GApps flash and it should replace /provision. this is what happened during my installation sequence.

i then reversed it deleting the /setup wizard and copying back /provision
[Pixel C Android Development] Bleedos:
I'll check back today.

I got tired of trying different combinations and flashed back some Oreo ROM. There's something that annoys me with this particular ROM so I won't keep it.

Will try your "recipe" and if it doesn't work I'll put back another Oreo ROM.

Don't have much time. There's a big rush at work and I need to have fun with Concourse ?, Spring Boot and some Cloud environments...
[Pixel C Android Development] CharFalco:
I replaced the SystemUI files in TWRP but when I boot I'm missing.... the system ui, no navbar or status bar. I'm sure I deleted the original 3 files then moved the provided 3 into the right spot.
[Pixel C Android Development] drewski_1:
probably a permissions thing? iirc, the system files should be 0755 or -rwxr-xr-x

you can change that in TWRP file manager.
[Pixel C Android Development] CharFalco:
Mounted System in TWRP, navigated to each file that I moved from the posted zip, applied chmod-755 successfully, no change, no status bar, no nav-bar. I'm not sure what sorcery the person who got this to work did - but I'm jealous!
[Pixel C Android Development] drewski_1:
:(

no other ideas.

for me, i'd Nandroid back or dirty flash back to pre-change of those three. i'm personally just living with the graphic issues. everything else seems to be working pretty good
[Pixel C Android Development] followmsi:
No idea what's wrong .. and no time to check right now.

Sorry, pls wait for next month release.
[Pixel C Android Development] drewski_1:
MY BAD

i just looked at permissions in /system/priv-app/ and the FOLDERS should be 755 while the FILES (apk, oat) should be 644 (rw-r--r--)

HTH
[Pixel C Android Development] mattysiebs:
So how stable is the current release? I am very keen on installing this and running it on my Pixel C tablet (very annoyed google end-of-life-ed its software support).
[Pixel C Android Development] drewski_1:
very stable. Google Camera isn't working, but who takes pictures with a tablet, anyway? :silly:
[Pixel C Android Development] Mattycee:
I have applied the fix as listed and it shows all the icons across the top, but if I have notifications, they are still not lined up anywhere apart from the middle of the screen. Have I not applied the fix correctly or is that the usual behaviour? It is not a massive deal if it is the behaviour but if it isn't I will try again to apply the fix.
[Pixel C Android Development] Alex93917:
Thank you VERY much for your hard work !!! My Pixel C stays updated, you're the best !
[Pixel C Android Development] followmsi:
For icons only .. the rest is just P.
[Pixel C Android Development] j04nd03:
Possible launcher problem

Hi,

as I guess there won't be a new Pure Nexus release for the Pixel C any more, I finally switched to AOSP Pie. First of all I want to thank [MENTION=5480152]followmsi[/MENTION] for his great work, I really appreciate it to be able to use Android Pie on my favourite tablet.

Installation worked flawlessly except for the usual problem with the setup wizard (which I hadn't read up before, my bad), there seems to be a problem with the android launcher however:

First of all, Pixel Launcher isn't working for me at all, whenever I select it as starter app, after a few moments Android shows the message that it had repeatedly crashed and forces me to select another starter app. I therefore selected Quickstep, which appeared to work fine at first.

However, after initial setup including setting a screen lock gesture and a few reboots, the screen lock didn't seem to accept my gesture any more. As the appearance of the gesture input appeared to "behave differently" (difficult to explain, for example it didn't show the path of the gesture as a continuous line any more), I thought it might have something to do with the fact that the setup wizard hadn't been completed and still showed a notification in the status bar, so I wiped the tablet and installed the ROM anew, this time replacing the setup wizard with the provision folder, as suggested earlier in this thread. As I didn't want to risk being locked out of my tablet again however, this time I didn't use a gesture, but a simple pin code as screen lock. This seemed to work, and I have used the tablet without any other problems with this setting for about a week now.

However, today I was locked out of the tablet again: Although the screen lock seemed to accept the pin entry showing no error message (as ist usually does when the pin or the gesture is wrong), the screen blanked for about a second and immediately showed the pin entry screen again. Since the problem obviously can't be caused by the gesture input this time and due to the screen blanking, I guess that the launcher is crashing and immediately restarting, effectively resulting in a lock screen loop.

Luckily I was able to bypass the lock screen by deleting the lock keys via TWRP file manager and I'm not using a screen lock any more for the time being, but if the problem is not simply an error on my side but in fact a bug caused by the ROM itself, it's probably worth to be looked into for the next ROM release. If I can be of any assistance with that, just let me know how I can help.

Cheers, JD
[Pixel C Android Development] j04nd03:
Never mind, I just found this thread where the exact problem is described. It seems it's a known bug even on stock firmware, it just never happened to me on Pure Nexus before. According to the thread it never got fixed by Google and noone found another solution apart from deleting the key files either, but maybe it really has just been a crashing and restarting launcher right from the start, so it's probably worth to look into that anyway.

I've meanwhile updated the Pixel Launcher with the latest apk from apkmirror.com (build 9-4902955), but it still instantly crashes. The latest version of th Pixel C Launcher (build 8.1.0-4779173) does work however, even though it's obviosly built for Oreo.
[Pixel C Android Development] Vartom:
[MENTION=5480152]followmsi[/MENTION]

I found a patch by reverting which you can use the camera.dragon.so library without a shim.

https://github.com/LineageOS/androi...25c3121#diff-ad2c2c1d0b8883fff41d53394823de34
[Pixel C Android Development] followmsi:
Will update OP soon .. same text as for Lineage-16.0

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

Hopefully the "waiting time" before unlock will help on AOSP too.

Did not know that the problem happens on stock Oreo too .. we use the same blobs in Pie now.

Not sure if and by when this problem get fixed.

Cheers

Edit:

Pixel launcher is common problem on plenty devices.

Opengapps will not use modified apk and the unmodified does not work.

I do not search actively for any possible solution from device point of view.

Maybe there is a patch required. Just don't know.

Tested this one on another device.. does not crash.

https://www.xda-developers.com/download-pixel-launcher-google-assistant-search-bar-pixel-3/
[Pixel C Android Development] followmsi:
Thanks .. will check it.
[Pixel C Android Development] followmsi:
November 2018

AOSP_9.0.0_r16_PQ1A.181105.017.A1_dragon-ota-eng.followmsi.zip

Changes

- Google security updates -> November 2018

- No Google kernel updates this month !

- Fix for QuickSetting -> Thanks to [MENTION=6556709]Vartom[/MENTION]

- Fix for Camera2 app

- minor other changes

- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)

Again, I have updated Oreo sources too .. but no build this time.

There will be one last AOSP Oreo build -> when Google releases the last official Oreo update.

Enjoy ..:p
[Pixel C Android Development] Alex0703:
Hi !

Very thanks for update ! But i have problem when start this rom, i'm blocked in "Search update wait minutes"

Someone have solution for this problem please ? :(
[Pixel C Android Development] followmsi:
More details please ..

At which point do you see this message ?

Coming from system or from gapps ?

You did cleant install or upgrade from previoius version ?

If clean install, please do skip setupwizard updates and use minimal setup.
[Pixel C Android Development] Alex93917:
I have the same problem when I install Gapps in the same time of rom package. If I boot rom without Gapps and reboot with installing Gapps, the issue is passed.
[Pixel C Android Development] Alex0703:
Hoo realy thanks ! I looked for the solution until 2am yesterday! :o
[Pixel C Android Development] Monazite:
Can anyone test if the official keyboard can connect correctly?
[Pixel C Android Development] Alex0703:
I use keyboard, it's work fine ! ;)
[Pixel C Android Development] Monazite:
No...:( Still cannot connect and tell me wrong PIN...

I think it will look better if set QS icons grid as 4*3:p

Edit:

One of split screen is quite laggy when scrolling, but I think it is AOSP-related and probably hard to fix.
[Pixel C Android Development] drewski_1:
was expecting fix for width of Quick Settings. was not expecting notifications to align in all positions!

great work, everyone who contributed [MENTION=5480152]followmsi[/MENTION] & [MENTION=6556709]Vartom[/MENTION] & anyone else! love it!! :good:

---------- Post added at 04:34 AM ---------- Previous post was at 04:32 AM ----------

+1 keyboard working fine here
[Pixel C Android Development] Monazite:
Is your keyboard official?
[Pixel C Android Development] followmsi:
The alignment fix was part of latest AOSP for November .. provided by Google.

Not sure who did the code.

But this way the change will come to all other ROMs automatically.
[Pixel C Android Development] AlfreGarcia98:
Hi, i'm running lineage os 15.1 but split screen andtransitions are laggy. How are animations and performance in this rom and is it better than lineage os 16? I'v read that alignment has been solved for the quick settings. And how is battery life going?

Thanks
[Pixel C Android Development] minieod:
does the bootloader version matter at all?

im stuck on 7900.50.0 and can't update to the 126 version at all. i get unknown command issues when flashing it through bootloader

though, this will boot - but im stuck at "checking for updates" and it never gets through it.

i flashed the 1105 copy alongside 1111 gapps mini, off of twrp 3.2.3.0
[Pixel C Android Development] followmsi:
Did remove your USB stick ?

Change storage to internal.

Yes, then vendor , gapps and SuperSU and reboot ..
[Pixel C Android Development] Istvan_86:
Yes I remove usb :D but rom just doesn´t boot for me, when I reboot to system Pixel C just go back to TWRP but this time no OS installed warning is displayed. So extrange.....
[Pixel C Android Development] followmsi:
Did same steps like you ..

1. Wipe system

2. Unmount system manually

3. Install new downloaded OTA .. No error 7 message :)

4. Install new AOSP vendor.img for no warning message after first boot.

5. Install gapps arm64 - 7.1

6. Install SuperSU.zip

Reboot into system.

I will stay on AOSP :)
[Pixel C Android Development] Istvan_86:
I repeat all the process 3 times, still I can´t boot in your rom.
[Pixel C Android Development] followmsi:
After all the steps, what happens if you reboot into system ?

Still reboot into recovery ?

If so, please unzip the OTA and install the included boot.img via fastboot.

Reboot back into recovery and install SuperSU again.

Then boot into system again.

This is general approach for recovery bootloop .. install clean boot.img via fastboot.
[Pixel C Android Development] Istvan_86:
I have the boot.img extracted from the ZIP and I´m on my previous backup. So I must flash the boot.img using "fastboot flash boot boot.img" and then all the zips? Also I don´t like SuperSU I prefer Magisk
[Pixel C Android Development] followmsi:
Don't know magisk .. will have a look.

Does it support chromeos boot.img ?

No ? .. but that's why pure boot.img works for you .. which is modified already.

But better you use the correct tools ..

Pls try it again .. and use SuperSU .. thanks
[Pixel C Android Development] Istvan_86:
Now I can´t flash the img using fastboot I´m totally obfuscated and very tired also the laggy TWRP is a bit painful to use. I just go back to Pure Nexus because I need tablet for my daily work.

Also I just don´t want SuperSu so I don´t install it, and yes Magisk is 100% working in my Pixel C but I even can try it with your rom because I can´t boot it :D

I give it more trys next weekend.
[Pixel C Android Development] followmsi:
Just want to help you ..

Take care !
[Pixel C Android Development] Istvan_86:
hahaha really thanks, I just stop trying your rom because I need the tablet for my daily work, next weekend or maybe earlier I repeat all the process.
[Pixel C Android Development] followmsi:
You know the steps now :)

I will not be able to help you better..

Pls sort out your boot.img issue first.

You need to be able to fastboot - take current stock boot.img and flash.

Cheers
[Pixel C Android Development] followmsi:
The new monthly sources will arrive soon .. still made V2 version based on current release.

I use this version myself since a month .. works really fine.

AOSP_7.1.1_r24_N4F26T_dragon-ota-eng.followmsi-v2.zip

Installation:

1. Boot into TWRP

2. Wipe system, cache and dalvik

3. Install AOSP_7.1.1_r24_N4F26T_dragon-ota-eng.followmsi-v2.zip

4. Install open_gapps-arm64-7.1-xxxx-2017xxxx.zip (optional)

5. Install SuperSU-v2.79-201612051815.zip (optional)

6. Reboot into system

If you have installed gapps in previous build and did not wipe system you don't need to install gapps again.

Due to systemless rooting - if you have installed supersu before you need to install again !

Due to supersu installation it will boot twice - no panic, it's normal !

The required vendor.img is part of the ROM installer now.

If you face any strange issues, pls do a factory reset via TWRP first.

Changes:

- Added Night Mode to Display settings

- Added patches for different WebView versions - required for proper gapps installation.

- Added F2FS and NTFS support

- Using custom installer to add "addon.d" support - previous gapps installation will not get lost on ROM upgrade.

Enjoy :)