GrapheneOS version 2023062300 released

GrapheneOS

GrapheneOS version 2023062300 released: https://grapheneos.org/releases#2023062300.

See the linked release notes for a summary of the improvements over the previous release.

SoulKeeper

Is the issue with unlocking the device with fingerprint after switching from user profile to owner profile fixed?

VAULT

SoulKeeper I usually check the link above so I know whats been updated. e.g.

Changes since the 2023061402 release:

Sandboxed Google Play compatibility layer: fix compatibility with Nearby Share with current Play services versions
add production ready Pixel Tablet support (we published our initial release for it on June 21st, but this is the first production release with tags)
ignore non-system packages for location indicator exemptions, getLocationBypassPackages(), Qualified Network Services, telephony data services, device provisioning and wlan/wwan wireless network services to resolve an upstream vulnerability in the approach to exemptions impacting the Pixel Tablet
Settings: hide eSIM activation app toggle when the app isn't included in the OS such as the Pixel Tablet
prevent adding guest user on lockscreen via adding new users on lockscreen is disabled (UI only appears on large screens such as the Pixel Tablet)
improve compatibility with apps trying to use a network location provider when none is available
fix work profile screenshot crash caused by missing configuration in AOSP
use unified tags based on our build number rather than the standard BUILD_ID.BUILD_NUMBER
Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a: set BUILD_ID to match stock OS again
Settings: improve our infrastructure for user management toggles
Settings: add toggle for preventing a user from running in the background
kernel (Generic 5.15): update to latest GKI LTS branch revision including update to 5.15.110
adevtool: add support for devices without a cellular baseband
adevtool: make adding vendor_kernel_boot partition-exists generic
adevtool: disable broken support for file reference overlays
simplify Pixel prototype check by comparing brand instead of device model
GmsCompatConfig: update to version 58
GmsCompatConfig: update to version 59
GmsCompatConfig: update to version 60

Skyway

SoulKeeper
Just updated and still the same .

Themble

VAULT Settings: add toggle for preventing a user from running in the background

This sounds interesting. Does this mean you can put another profile to rest from main profile?

treequell

Themble Yes. As I understand, it means that if enabled, the secondary user profile will only be active when you are using it. Switching to another profile, will end the session of that first user profile. This has a few advantages:

The secondary profile will never run in the background
This means you can directly switch from one secondary user profile to another, and put the first secondary user profile at rest at the same time. Previously, the only way to put the profile at rest was to press end session, but this always brought you back to the owner profile.

Themble

I understand. But then there can't be noifications across profiles, right?

treequell

Themble I understand. But then there can't be noifications across profiles, right?

Correct. The user profile needs to be running in the background for notifications to arrive there, and then be forwarded to your current user profile.

Skyway

Themble
Just played with the settings , this is a per user setting not a global one .

brambler

treequell Thanks for this! Was wondering where this new toggle was.

Blastoidea

Wow!

Everyone is really on the stick. I just got it.

Thank you to everyone involved.

gosrox

is the launcher crashing for secondary users all the time fixed? this was error

java.lang.NullPointerException: Attempt to read from field 'com.android.internal.util.LatencyTracker com.android.systemui.shade.NotificationPanelViewController.mLatencyTracker' on a null object reference in method 'void com.android.systemui.recents.OverviewProxyService$1$$ExternalSyntheticLambda9.accept(java.lang.Object)'
	at android.os.Parcel.createExceptionOrNull(Parcel.java:3027)
	at android.os.Parcel.createException(Parcel.java:3005)
	at android.os.Parcel.readException(Parcel.java:2981)
	at android.os.Parcel.readException(Parcel.java:2923)
	at com.android.systemui.shared.recents.ISystemUiProxy$Stub$Proxy.onStatusBarMotionEvent(ISystemUiProxy.java:360)
	at com.android.quickstep.SystemUiProxy.onStatusBarMotionEvent(SystemUiProxy.java:287)
	at com.android.launcher3.uioverrides.touchcontrollers.StatusBarTouchController.dispatchTouchEvent(StatusBarTouchController.java:79)
	at com.android.launcher3.uioverrides.touchcontrollers.StatusBarTouchController.onControllerInterceptTouchEvent(StatusBarTouchController.java:109)
	at com.android.launcher3.views.BaseDragLayer.findControllerToHandleTouch(BaseDragLayer.java:183)
	at com.android.launcher3.views.BaseDragLayer.findActiveController(BaseDragLayer.java:193)
	at com.android.launcher3.views.BaseDragLayer.onInterceptTouchEvent(BaseDragLayer.java:163)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2653)
	at com.android.launcher3.views.BaseDragLayer.dispatchTouchEvent(BaseDragLayer.java:303)
	at com.android.launcher3.dragndrop.DragLayer.dispatchTouchEvent(DragLayer.java:225)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:500)
	at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1912)
	at android.app.Activity.dispatchTouchEvent(Activity.java:4307)
	at com.android.launcher3.Launcher.dispatchTouchEvent(Launcher.java:2111)
	at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:458)
	at android.view.View.dispatchPointerEvent(View.java:15309)
	at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:6774)
	at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:6574)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:6030)
	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:6087)
	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:6053)
	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:6218)
	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:6061)
	at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:6275)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:6034)
	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:6087)
	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:6053)
	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:6061)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:6034)
	at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:9202)
	at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:9153)
	at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:9122)
	at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:9325)
	at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:267)
	at android.view.InputEventReceiver.nativeConsumeBatchedInputEvents(Native Method)
	at android.view.InputEventReceiver.consumeBatchedInputEvents(InputEventReceiver.java:247)
	at android.view.ViewRootImpl.doConsumeBatchedInput(ViewRootImpl.java:9282)
	at android.view.ViewRootImpl$ConsumeBatchedInputRunnable.run(ViewRootImpl.java:9416)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1231)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1239)
	at android.view.Choreographer.doCallbacks(Choreographer.java:899)
	at android.view.Choreographer.doFrame(Choreographer.java:824)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1214)
	at android.os.Handler.handleCallback(Handler.java:942)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.app.ActivityThread.main(ActivityThread.java:7937)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
	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:355)

gosrox

Skyway there really needs to be downgrade option for botched updates. My phone has almost unusable for 2 weeks now (jun 14 update) with launcher crashing all day and no one seems to care or experience it. If gos team cannot fix issues introduced by quarterly patches then those should be optional or downgradable to a different version with just kernel or quarterly rolled back. If i needed my phone in an emergency now i would be screwed becausd the launcher is crashing and i wouldnot be able to bring up app quickly tryibg to work around it while panick emergency. This should have never gone to production. Fingerprint issue too but mainly launcher for me. Launcher crashing all the time broke app switching completely.

No one even acknowledged my log here and in previous update thread no one had idea lol gosrox

siabadaba

My fingerprint unlock disappeared completely after the update 😮 Not even an option in the Security settings. What's up? Pixel 6a

treequell

siabadaba I have not seen any other reports of this issue.

Where are you looking exactly? In Settings > Security, Fingerprint Unlock should be the second option from the top, after Screen lock and before Auto reboot.

Is this in the system user or a secondary user?

https://source.android.com/docs/devices/admin/multi-user#categories_of_users

TrustExecutor

siabadaba
I had the same issue with a Pixel 6 Pro. I rebooted and then the fingerprint unlock was there again.

pdagenius

Strange. Just updated my 6a and it is functioning correctly.

siabadaba

treequell It's the system user (I don't have multiple users toggled). That's exactly where I'm looking and the option is not there. Screen lock and then immediately Auto reboot. When I go into Screen lock settings the only available options are None, Swipe, PIN and Password.

Another issue I just discovered is that my phone started dropping calls after _30s. Had it with multiple callers, both when I called and received. Network coverage is good.

SoulKeeper

Do third party clock apps work nicely with GrapheneOS? Let say, I set an alarm on a third party click app (downloaded from Fdroid) and the device somehow restarts, will the alarm trigger on time or do I need to unlock the device once?

matchboxbananasynergy

SoulKeeper It's up to the clock app in that case, which would need to support direct boot to be able to use part of its functionality while the phone is in BFU state. It's not up to GrapheneOS, but rather the app itself.

As an example of this, GrapheneOS actually contributed direct boot support to Florisboard, which means it can be used to unlock the phone while in BFU state where it otherwise wouldn't.

treequell

siabadaba That's strange! Could you do something for me to help investigate this further?

Enable multiple users, create a secondary user, and then switch to that secondary user. Then have a look in Settings > Security, and tell me if you have the same issue with Fingerprint Unlock being hidden. That will help to establish if it's a device-wide issue or a strange configuration in your system user. You can always delete the secondary user after.

siabadaba

treequell Same thing in the new user. Screen lock and then immediately Scramble PIN input. No fingerprint. Also in the initial setup that option was not present

[deleted]

siabadaba Just checking, do you have a pin or pw set? If not, you need to create one before adding your fingerprints. These are a prerequisite to decrypt the profile/device from rest and as a fallback to fingerprints for when they fail.