GrapheneOS version 2024111800 released

Accent18 AOSP beta isn't the same as GrapheneOS beta. If you look at the previous GrapheneOS releases, the one based Android 14 QPR2 was not released until after AOSP, in March. This is because the source code is not released until after the official release, or something like that.

So yes, the delay will likely be that long. Also, if you want to be the first to try it, choose the Alpha channel instead.

I recognized a Bug with instant system reboot when I try to record my screen and choose only one App. It was the Google Wallet App I tried to open. Maybe the log helps the devs :)
`

type: crash

SystemUptimeMs: 63702420
Process: system_server
Timestamp: 2024-11-20 18:19:35.021+0100
Build: google/husky/husky:15/AP3A.241105.007/2024111800:user/release-keys
Crash-Handler: com.android.internal.os.RuntimeInit$KillApplicationHandler
Loading-Progress: 1.0
Dropped-Count: 0

java.lang.NullPointerException: Attempt to invoke virtual method 'com.android.server.wm.Task com.android.server.wm.ActivityRecord.getTask()' on a null object reference
	at com.android.server.wm.ScreenRecordingCallbackController.setRecordedWindowContainer(ScreenRecordingCallbackController.java:99)
	at com.android.server.wm.ScreenRecordingCallbackController.onScreenRecordingStart(ScreenRecordingCallbackController.java:179)
	at com.android.server.wm.ScreenRecordingCallbackController.-$$Nest$monScreenRecordingStart(ScreenRecordingCallbackController.java:0)
	at com.android.server.wm.ScreenRecordingCallbackController$MediaProjectionWatcherCallback.onStart(ScreenRecordingCallbackController.java:75)
	at com.android.server.media.projection.MediaProjectionManagerService$WatcherStartCallback.run(MediaProjectionManagerService.java:1463)
	at android.os.Handler.handleCallback(Handler.java:959)
	at android.os.Handler.dispatchMessage(Handler.java:100)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at com.android.server.SystemServer.run(SystemServer.java:983)
	at com.android.server.SystemServer.main(SystemServer.java:661)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:880)

I was really excited to see the release note mentioning improved voice commands for Android Auto, but unfortunately voice commands still won't work for me.

I did some additional testing, and it seems when Google Maps is the main app open in Android Auto, Google Assistant will not work at all. As soon as you switch to a different app, in my case Spotify, tapping the Assistant icon works. I have microphone permissions enabled for every Google app including Maps, so it should be working. I recorded some video of this behavior, and can send it in a DM to someone on the team, just let me know.

I also took logs for Google, Google Maps, Google Play Services, and Android Auto to hopefully help fix this issue.

I'm putting the logs in a separate notes page because they're too long to send here:
Google Logs: https://monogr.ph/673e5bebf3126cdba5570c3e
Google Maps Logs: https://monogr.ph/673e5c45f3126cdba5590c3e
Google Play Services Logs: https://monogr.ph/673e5c66f3126cdba55b0c3e
Android Auto Logs: https://monogr.ph/673e5c93f3126cdba55d0c3e

Please let me know if I can help troubleshoot this issue in anyway, it's the one thing that's really been bothering me. Thanks!

EDIT: It also seems the Microphone doesn't work in the Google Maps even when not connected to Android Auto.

Homerstar I can't reproduce this issue. Did it only happen once, or does it happen every time?

There has probably been a minor regression on one of the last few builds. When closing Spotify, the media player widget on the lock screen no longer disappears, but instead still shows the cover art and song name for the last played song, just, no buttons work anymore. The widget used to disappear in this case, which is more expected behavior, as one probably do not want it anymore if one has shut down Spotify completely. There are some widget related changelogs in GrapheneOS recently, but the upgrade to AOSP 15 is also recently. I don't know if it is an upstream issue or not. Could of course also be Spotify's fault. I am just mentioning it, because I feel like I need to mention I have observed this regression. But it does not seem near serious enough to even be worthwhile to make a ticket about, just a minor inconvenience.