Pixel 8 / 8 Pro releases available

MrSmith
Ok I confirm this is a bug as according to the docs foreground services notifications shouldn't be dismissable, but currently are: https://developer.android.com/develop/ui/views/notifications#foreground-service
It can be reproduced by using Signal (downloaded from the website) without Play Services installed. The "Background connection enabled" notification can be dismissed.

I'm still unsure about the "Disconnected from always-on VPN" notification, as according to the same doc there was a change for some notification that can now be dismissed where it was impossible before: https://developer.android.com/develop/ui/views/notifications#android_140_api_level_34
But it seems weird to me that such important notification could be inadvertently cleared, so it may be a bug in this instance too.

Graphene1
From where did you download pixel 8 release ?
staging.grapheneos.org

As long as the link are stored in the staging URL, I bet we can't consider it as stable.
This is just "stable" experimental builds.

Edit : Actually my bad it moved out from staging.

https://grapheneos.org/releases#shiba-stable
But still tag as experimental in pixel 8 name.

So now the latest build from today is available, I have the same behavior I had with P6a A14 build.
I probably because hardened kernel is now active ?

I have a c**cked sideloaded app that does not work since A14 on P6a and since today on P8.

type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023102000:user/release-keys
package: com.coyotesystems.android:30041476
process: com.coyotesystems.android
processUptime: 3291 + 254 ms
installer: com.android.packageinstaller

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.coyotesystems.android/com.coyotesystems.android.mobile.activity.MobileMainActivity}: java.lang.RuntimeException: Cannot create map: Failed to read configuration file: /storage/emulated/0/Android/data/com.coyotesystems.android/files/coyote/here/customConfig/mwconfig_client
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3793)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3933)
	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:139)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:96)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2450)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:205)
	at android.os.Looper.loop(Looper.java:294)
	at android.app.ActivityThread.main(ActivityThread.java:8199)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
	at com.android.internal.os.ExecInit.main(ExecInit.java:49)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)
Caused by: java.lang.RuntimeException: Cannot create map: Failed to read configuration file: /storage/emulated/0/Android/data/com.coyotesystems.android/files/coyote/here/customConfig/mwconfig_client
	at com.nokia.maps.MapImpl.<init>(SourceFile:64)
	at com.here.android.mpa.mapping.Map.<init>(SourceFile:2)
	at com.coyotesystems.coyote.maps.here.services.HereMap.<init>(SourceFile:9)
	at com.coyotesystems.coyote.maps.here.views.HereMapView.onResume(SourceFile:2)
	at com.coyotesystems.coyote.maps.views.map.DefaultMapViewController.h(SourceFile:2)
	at com.coyotesystems.coyote.maps.views.map.DefaultMapViewController.resume(SourceFile:15)
	at com.coyotesystems.navigation.views.page.AbstractMapPage.resume(SourceFile:6)
	at com.coyotesystems.navigation.views.page.MapPagePortrait.resume(SourceFile:3)
	at com.coyotesystems.android.n3.view.component.DefaultPageDisplayer.setCurrentPage(SourceFile:20)
	at com.coyotesystems.android.view.main.PageContainerManager.a(SourceFile:3)
	at com.coyotesystems.android.mobile.activity.MobileMainActivity.a0(SourceFile:10)
	at com.coyotesystems.android.n3.app.MainActivity.onCreate(SourceFile:21)
	at com.coyotesystems.android.mobile.activity.MobileMainActivity.onCreate(SourceFile:1)
	at android.app.Activity.performCreate(Activity.java:8651)
	at android.app.Activity.performCreate(Activity.java:8629)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1461)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3775)
	... 14 more

If someone know how I can fix this...
The app worked fine before 20231020 build on P8... But never worked on A14 P6a (it was working on A13)
Thanks

PMUSR Typically, as I understand it, for a normal update, the GOS devs after working on the code (fixing bugs, updating security patches from Google, etc), release the code, first via the Alpha Channel, if there's no significant problems for those who set the phone update channel to Alpha, then a day later (?) its moved to Beta Update Channel, then a day later, moved to Stable Update Channel. This slow release lets the devs catch any missed problems BEFORE it hits every pixel on GOS :) I assume this process will also be followed for this major new phone model release...