Yeah this particular behaviour is an AOSP issue and not GrapheneOS specific.
If it failed to come back at all it would be hardware related.
Yeah this particular behaviour is an AOSP issue and not GrapheneOS specific.
If it failed to come back at all it would be hardware related.
No replies yet.