GrapheneOS version 2023111500 released

Hb1hf

Murcielago Thanks for fixing

They didn't. It's an upstream AOSP bug that goes away and back with every GOS update even though they're not actually touching it.

Murcielago

Hb1hf
Oh no, unfortunately you seem to be right - after a few restarts the error occurs again for me too :-/

RoyValentine

archvile77 I'm also getting this! I was also wondering if it's a Graphene issue or AOSP.

Hopefully someone is aware of this issue.

ve3jlg

RoyValentine I was also wondering if it's a Graphene issue or AOSP.

In the end it does not matter. A broken user experience is problematic no matter who points the finger at who.

In any case, one cannot rationally separate AOSP and GrapheneOS. Using AOSP is the the most fundamental and core design decision of GrapheneOS of all. GrapheneOS does not exists without AOSP. To say that serious AOSP defects are not a GrapheneOS issue is nonsensical.

RoyValentine

Also to note, after my phone updated and finished optimizing apps in the background I restarted the phone. I then received the "Your phone has no operating system" message. I got the same message when Graphene released the first A14 build.

Luckily this time it only took one hard reset to get it to boot properly but this is getting a bit annoying / concerning when it happens. Maybe I'll turn off auto update for a while....

yore

archvile77 I'm also having the same problem. Hopefully they will release a fix soon.

Blastoidea

This is getting worrisome to me.

I have never seen this, nor do I want to.

Is it something we can just wave aside?

ve3jlg

Blastoidea I have never seen this, nor do I want to.

You can disable updates as I did and wait until the new defects are corrected.

Of course anyone who didn't disable updates before the major A14 release (which like most major software releases was likely to have many defects) is out of luck for now. But it's never to late to disable the updater, watch for and read about (fixed) defects in new releases, then update when the software is more usable.

Hb1hf

Hb1hf This release fixed the fingerprint issue for me. Yay!

Ohhh never mind. Restarted the phone and it's back again

de0u

ve3jlg To say that serious AOSP defects are not a GrapheneOS issue is nonsensical.

If an issue arises in code specific to GrapheneOS, it seems pretty unlikely that Google will submit a fix to the GrapheneOS team. If an issue arises in the AOSP code base, it is plausible, albeit far from certain, that Google will submit a fix to the GrapheneOS team (and everybody else, via AOSP). That seems like a potentially sensical distinction.

[deleted]

I can't manually install apps from a File Explorer (I've tried Root Explorer -without root permissions, of course- and also the Files app included with GOS, with same result):

type: crash
osVersion: google/cheetah/cheetah:14/UP1A.231105.003/2023111500:user/release-keys
package: com.android.packageinstaller:34
process: com.android.packageinstaller
processUptime: 3213 + 204 ms

java.lang.RuntimeException: Unable to start receiver com.android.packageinstaller.InstallEventReceiver: android.util.AndroidRuntimeException: Calling startActivity() from outside of an Activity context requires the FLAG_ACTIVITY_NEW_TASK flag. Is this really what you want?
at android.app.ActivityThread.handleReceiver(ActivityThread.java:4469)
at android.app.ActivityThread.-$$Nest$mhandleReceiver(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2263)
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: android.util.AndroidRuntimeException: Calling startActivity() from outside of an Activity context requires the FLAG_ACTIVITY_NEW_TASK flag. Is this really what you want?
at android.app.ContextImpl.startActivity(ContextImpl.java:1132)
at android.app.ContextImpl.startActivity(ContextImpl.java:1108)
at android.content.ContextWrapper.startActivity(ContextWrapper.java:436)
at android.content.ContextWrapper.startActivity(ContextWrapper.java:436)
at com.android.packageinstaller.EventResultPersister.onEventReceived(EventResultPersister.java:189)
at com.android.packageinstaller.InstallEventReceiver.onReceive(InstallEventReceiver.java:50)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:4460)
... 11 more

[deleted]

[deleted] Its an issue with the app, This Stack Overflow question might be helpful for the developer

yore

[deleted] You should open a separate post if this issue still persists. You're more likely to get useful answers.

[deleted]

[deleted] I think isn't an issue with the app.
When I click into the APK a system confirmation dialog (not an app confirmation dialog) is displayed and askingif I want to install the app update and then the crash is received

[deleted]

[deleted] Sorry, you're right. I didn't read the package: com.android.packageinstaller:34 line.

[deleted]

I don't kwon if it occurs at previous versions, but in this version, if I enable BT at main profile, then switch to another profile, the BT remains enabled at the other profile but it becomes disabled when I finish session at the other profile then return to the main profile.
Is there a workaround for that?