GrapheneOS version 2023111500 released:
https://grapheneos.org/releases#2023111500
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2023111500 released:
https://grapheneos.org/releases#2023111500
See the linked release notes for a summary of the improvements over the previous release.
Thanks for the update! Any news about the missing Mali GPU kernel patch for 6th & 7th gen Pixels?
This release fixed the fingerprint issue for me. Yay!
Con: now I'm considering turning off auto update for a while.
It worked for me too - unlocking with the fingerprint when changing the profile now works. Thanks for fixing!
I am still having an issue on the P6P, with the fingerprint sensor failing when AOD is turned on and in low power mode
Do this - lock the phone, let it sit for about 5 seconds, the screen will quickly flash when it enters low power mode. When attempting a fingerprint unlock in this state, it will say "press firmly on the sensor", followed by "fingerprint not recognized". Since this action "wakes up" the screen, the following fingerprint will unlock.
This is repeatedly reproducible and is not the actual fingerprint failing, but something to do with the screen being in low power AOD mode kicking back any fingerprint attempt. I can "wake" the screen or bring it to the normal lock screen and the fingerprint works 100% of the time. This is some bug introduced a few months ago (it used to work normally).
Also there is a completely unrelated issue that started in Android 14 where when you swipe up to go into multitask view, sometimes another quick swipe up (as if you were trying to close/swipe away the app you were in) will make the app actually scroll down as if you were still in the app, instead of swipe it away.
Not sure if this is AOSP or GOS related. Never happened in 13.
Murcielago oh lucky you, i dont see any improvment regarding that :(
My Pixel 5 grabbed it yesterday, and there has been a flurry of Signal updates.
Currently 6.40.4.
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.
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.
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....
archvile77 I'm also having the same problem. Hopefully they will release a fix soon.
This is getting worrisome to me.
I have never seen this, nor do I want to.
Is it something we can just wave aside?
Hb1hf
Oh no, unfortunately you seem to be right - after a few restarts the error occurs again for me too :-/
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.
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.
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.
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 msjava.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