Pixel 10a

AdorableWeasel

Just wanted to say that so far I've had a pretty flawless experience using the new experimental build of the Pixel 10a

The only issues I've encountered, were one's which online discussion and official guides were able to resolve. Things such as banking apps and Android Auto, all fixed with a couple setting and permission changes

It is sad that the Secure App Spawning needs to be disabled for apps to work and it is not possible to enable/disable per app. I completely understand that this is not currently possible and am not asking for the change, just expressing my only mild grievance so far :)

I'm sure you all have your heads very deep in issues and problems, I just wanted to show my gratitude and genuiene appreciation for your efforts

My props to the devs <3

MetropleX

AdorableWeasel It is sad that the Secure App Spawning needs to be disabled for apps to work

Isn't correct, ALL apps work with secure app spawning, turning it off is removing a fundamental security improvement over stock.

It can in some circumstances impact multitasking ONLY where RAM is the limiting factor based on the types and demands of individual apps.

As outlined in https://grapheneos.org/usage#exec-spawning

This feature can be disabled via Settings > Security & privacy > Exploit protection > Secure app spawning if you prefer to have faster cold start app spawning time and lower app process memory usage instead of the substantial security benefits and the removal of the only known remaining direct device identifiers across profiles (i.e. not depending on fingerprinting global configuration, available storage space, etc. or using side channels).

As for the rest appreciate your positive remarks. Thanks.

AdorableWeasel

If that is the case, these applications are completely broken unless this is disabled for myself:
Barclays
Tesco Clubcard and Banking

Oddly PayPal broke after I disabled the setting! But that might've been me just not realising it wasn't working in the first place. Honestly, I'll just use the website for that one. Barely touch it anyways

I found the fix in either GitHub or this forum so I am not sure if maybe I missed something there?

Thanks :)

AdorableWeasel

AdorableWeasel also to second this, I quickly ran through the steps outlined in that guide and can confirm the same problem happens with the following details:

Tesco:

type: crash
osVersion: google/stallion/stallion:16/BD6A.251031.001.A4/2026032001:user/release-keys
flags: dev options enabled
package: com.tescobank.mobile:40600000, targetSdk 35
process: com.tescobank.mobile
processUptime: 3609 + 261 ms
installer: com.android.vending

pw.qZl

This is fixed when you disable Secure App Spawning

Barclay's:

No crash, it just says "you're using a rooted device"
This is only fixed when Secure App Spawning is disabled and Barclay's is reinstalled

MetropleX

AdorableWeasel

flags: dev options enabled

Why?

Also the statement you made was requirimg Secure App Spawning for 'apps' to work not certain apps.

Can you provide the app store links? I will try investigate.

Which Tesco app?
Tesco Mobile, Teaco Clubcard etc

Same for Barclays multiple listings, this for Barclaycard or Bank?

With them doing something to detect it we could do with logs and an issue posting on the Issue Tracker to help see if we can do something about it.

https://github.com/GrapheneOS/os-issue-tracker/issues

MetropleX

Just checked the Tesco Bank one and I could get it to operate using only the Exploit Protection Compatibility Mode Toggle once I enabled it and cleared app data to get as far as the login screen post denying location permission.