[ROM][AOSP][dragon] -> [9.0.0_r31_PQ2A.190205.001] -> 02-2019 (DISCONTINUED)

[Alex93917]

Thank you VERY much for your hard work !!! My Pixel C stays updated, you're the best !

 

[followmsi]

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.

For icons only .. the rest is just P.

 

[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 @followmsi 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

 

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

 

[Vartom]

@followmsi
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

 

[followmsi]

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.

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 @followmsi 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

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/

 

[followmsi]

@followmsi
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

Thanks .. will check it.

 

[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 @Vartom
- 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 ..

 

[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 ?

 

[followmsi]

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 ?

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.

 

[Alex93917]

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 ?

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.

 

[Alex0703]

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.

Hoo realy thanks ! I looked for the solution until 2am yesterday!

 

[Monazite]

Can anyone test if the official keyboard can connect correctly?

 

[Alex0703]

Can anyone test if the official keyboard can connect correctly?

I use keyboard, it's work fine !

 

[Monazite]

No... Still cannot connect and tell me wrong PIN...
I think it will look better if set QS icons grid as 4*3

Sent from my Google Pixel 2 using XDA Labs

Edit:
One of split screen is quite laggy when scrolling, but I think it is AOSP-related and probably hard to fix.

 

[drewski_1]

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

was expecting fix for width of Quick Settings. was not expecting notifications to align in all positions!

great work, everyone who contributed @followmsi & @Vartom & anyone else! love it!! :good:

Sent from my dragon using XDA Labs

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

Can anyone test if the official keyboard can connect correctly?

+1 keyboard working fine here

Sent from my dragon using XDA Labs

 

[Monazite]

was expecting fix for width of Quick Settings. was not expecting notifications to align in all positions!

great work, everyone who contributed @followmsi & @Vartom & anyone else! love it!! :good:

Sent from my dragon using XDA Labs

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



+1 keyboard working fine here

Is your keyboard official?

Sent from my Google Pixel 2 using XDA Labs

 

[followmsi]

was expecting fix for width of Quick Settings. was not expecting notifications to align in all positions!

great work, everyone who contributed @followmsi & @Vartom & anyone else! love it!! :good:

Sent from my dragon using XDA Labs

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



+1 keyboard working fine here

Sent from my dragon using XDA Labs

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.

 

[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

 

[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