phone-company Did you install it in the normal profile or in private space ? It works well for me in Private Space, I installed it in the main profile for testing and the application launched well but I didn't go any further.

    At the moment, I'm using the build 2024101600 of the alpha version without any issues on my Pixel 8.

    Thanks to the GrapheneOS team ;)

    Oh, quick question: you mentioned that 2FA for unlocking the device would come with version 15. Do you have any idea when you'll release this highly anticipated feature?

    That way, we can finally have a real Diceware on our mobiles :)

    • de0u replied to this.

      Thank you for your work @GrapheneOS !
      Since I don't have a GitHub account, I will report the crash here :

      type: crash
osVersion: google/panther/panther:15/AP3A.241005.015/2024101600:user/release-keys
package: com.google.android.gms:244035029
process: com.google.android.gms.persistent
processUptime: 2582406 + 357 ms
installer: com.android.vending
GmsCompatConfig version: 141

java.lang.SecurityException: Need android.permission.BLUETOOTH_CONNECT permission for android.content.AttributionSource@a81b82d4: GattService registerServer
	at android.os.Parcel.createExceptionOrNull(Parcel.java:3251)
	at android.os.Parcel.createException(Parcel.java:3235)
	at android.os.Parcel.readException(Parcel.java:3211)
	at android.os.Parcel.readException(Parcel.java:3153)
	at android.bluetooth.IBluetoothGatt$Stub$Proxy.registerServer(IBluetoothGatt.java:2278)
	at android.bluetooth.BluetoothGattServer.registerCallback(BluetoothGattServer.java:638)
	at android.bluetooth.BluetoothManager.openGattServer(BluetoothManager.java:253)
	at android.bluetooth.BluetoothManager.openGattServer(BluetoothManager.java:215)
	at android.bluetooth.BluetoothManager.openGattServer(BluetoothManager.java:175)
	at byye.e(:com.google.android.gms@244035029@24.40.35 (190400-683445800):31)
	at cdbo.a(:com.google.android.gms@244035029@24.40.35 (190400-683445800):61)
	at cdel.i(:com.google.android.gms@244035029@24.40.35 (190400-683445800):58)
	at cdep.o(:com.google.android.gms@244035029@24.40.35 (190400-683445800):36)
	at cdep.l(:com.google.android.gms@244035029@24.40.35 (190400-683445800):102)
	at cdep.e(:com.google.android.gms@244035029@24.40.35 (190400-683445800):126)
	at com.google.android.gms.nearby.mediums.bluetooth.BluetoothRadio.n(:com.google.android.gms@244035029@24.40.35 (190400-683445800):27)
	at com.google.android.gms.nearby.mediums.bluetooth.BluetoothRadio.d(:com.google.android.gms@244035029@24.40.35 (190400-683445800):122)
	at cdbq.run(:com.google.android.gms@244035029@24.40.35 (190400-683445800):7)
	at byzy.run(:com.google.android.gms@244035029@24.40.35 (190400-683445800):20)
	at anmi.c(:com.google.android.gms@244035029@24.40.35 (190400-683445800):50)
	at anmi.run(:com.google.android.gms@244035029@24.40.35 (190400-683445800):76)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at anrt.run(:com.google.android.gms@244035029@24.40.35 (190400-683445800):8)
	at java.lang.Thread.run(Thread.java:1012)
	Suppressed: etin: 
		at tk_trace.nearby-ManualRadioStateReceiver_onReceive(Unknown Source:0)
Caused by: byzv
	at bzaa.a(:com.google.android.gms@244035029@24.40.35 (190400-683445800):3)
	at bzab.a(:com.google.android.gms@244035029@24.40.35 (190400-683445800):3)
	at bzbm.execute(:com.google.android.gms@244035029@24.40.35 (190400-683445800):5)
	at com.google.android.gms.nearby.mediums.bluetooth.BluetoothRadio.b(:com.google.android.gms@244035029@24.40.35 (190400-683445800):5)
	at com.google.android.gms.nearby.mediums.bluetooth.BluetoothRadio$1.ko(:com.google.android.gms@244035029@24.40.35 (190400-683445800):8)
	at com.google.android.gms.libs.punchclock.tracing.TracingBroadcastReceiver.onReceive(:com.google.android.gms@244035029@24.40.35 (190400-683445800):17)
	at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1814)
	at android.app.LoadedApk$ReceiverDispatcher$Args.$r8$lambda$mcNAAl1SQ4MyJPyDg8TJ2x2h0Rk(Unknown Source:0)
	at android.app.LoadedApk$ReceiverDispatcher$Args$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
	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 android.app.ActivityThread.main(ActivityThread.java:8736)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
	at com.android.internal.os.ExecInit.main(ExecInit.java:50)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:369)

      Do you want more information ?

        IamZorro Update to Gmscompatconfig version 142 and see if that fixes it.

          I've had success updating my cheetah after a few hours. Calls, regular notifications, all good.

          I was greeted with a new 'Wallet' quick setting that displaced mine, I have never used/installed Google Wallet.
          My 'one handed mode' was turned off.

          That's all I've noticed so far.

          Bug report

          Device: Pixel 6a
          Version: Android 15 Oct 16 alpha update
          Issue: default SMS application fails to work, sending a message gives an error saying its not the default SMS application, even when it is. Device can still receive messages

            Skyway Yes. As stated in my message, the message appears regardless of whether you're using Messaging or a different app as your default.

                [deleted] Just to confirm, is it out as an alpha/beta update, or a stable release? Sorry if it's a dumb question.

                It's not. It's asked every single time. Which is why I'm petitioning the team to include a statement in the releases about it being available in alpha and only coming to beta and stable "soon"

                    phone-company because it's the release text that gets people confused:

                    GrapheneOS version 2024101600 released:

                    People think "if it's released, why don't I have it?"

                    So my proposal is to simply change it to:

                    GrapheneOS version 2024101600 released in the alpha channel:

                        I have issues with Instagram stories with this release. If you watch a story and interact by e.g. sliding or trying to skip, it starts hanging. Already tried rebooting, exploit comp mode, the works. Thought I'd share it here to see if more are having the same thing.

                          Another update on my side : Fingerprint unlocking now works for apps installed in Private Space.

                            Hb1hf It's an announcement of the availability of the release and is not an indication of it being in specific channels yet. The releases are usually announced shortly before Alpha. This release wasn't in Alpha until hours after the announcement due to pre-Alpha testing via sideloading being the initial focus out of an abundance of caution which was warranted since we needed to fix a Bluetooth triggered sandboxed Google Play crash via GmsCompatConfig 142 before Alpha.