I have a Sonim x320 (Xp3Plus 5G), - yes, I’m in middle of writing up a review, will post as soon as done - and I can’t enable accessibility on it for @wheredidmysleepgo’s C9 and @sh7411usa’s
Pointer apps.
When I go to accessibility settings to enable it, those two apps are grayed-out.
I haven’t either been able to enable developer options on it.
When I tap on build number, nothing happens.
Any suggestions?
Try *#*#2387#*#*
Tried that, didn’t work.
Do you have debugging?
No, that’s why I’m trying to enable developer options.
From past experience sometimes when its grayed out it will still work with a mouse to toggle on.
Oh it sounded like its just grayed.
What does that mean?
You can’t tap on a grayed-out switch, but you can click on it?
I meant through a bluetooth mouse. Worked for me once on a Kyocera.
I hear.
That’s pretty weird that that happened.
Sorry for suggesting
Turns out that it’s caused by Android 14’s tighter security.
Google AI overviews:
In Android 14, accessibility features, especially for apps, may be restricted due to new security measures. This can prevent apps from accessing certain accessibility features or data. To enable accessibility access, you may need to explicitly allow restricted settings for the specific app in the app’s settings or within the accessibility settings.
Here’s a more detailed explanation:
Reasons for Restrictions:
Increased Security:
Android 14 introduces stricter security measures to protect sensitive data and user privacy, including restrictions on accessibility services.
Restricted Settings:
Apps need to be explicitly allowed to access restricted settings to use certain accessibility features.
accessibilityDataSensitive Attribute:
Android 14 introduces this attribute, allowing apps to limit the visibility of specific views only to accessibility services that claim to help users with disabilities.
Google Play Protect:
This feature ensures that apps claiming to offer accessibility features are legitimate and trustworthy, further restricting access from non-Play Store apps.
How to Enable Accessibility Access:
Navigate to Settings: Open the Settings app on your Android 14 device.
Go to Apps: Find and tap on “Apps” or “App info”.
Select the App: Choose the specific app you want to grant accessibility access to.
Access More Options: Look for a three-dot menu (or “More” option) in the app’s settings.
Allow Restricted Settings: Select the option to “Allow restricted settings”.
Follow Prompts: You may need to confirm your choice with a PIN, fingerprint, or other security method.
Go Back to Accessibility: Navigate back to the Accessibility settings and enable the desired accessibility feature for the app.
Troubleshooting:
Trigger the Restricted Setting Dialog:
If the three-dot menu is missing, you might need to first trigger the “Restricted setting” dialog and click “OK” before going back to the app’s settings to allow access.
Check for Updates:
Ensure both your device and the app are updated to the latest versions.
You might need root. mtk?
Google should replace the Secret Service.
They seem to do a lot better of a job at security.
Qualcomm.
Apple is waaaay worse.
Whats with ai’s idea?
Sonim is supposedly releasing an update at some point to address this according to some comment on reddit, but not entirely sure how trustworthy this is.
I’ve spent the past day and a half trying to come up with a way to filter it without ADB, but kept hitting a brick wall.
eGate obviously wasn’t an option.
Sonim Safeguard can block apps, but can’t block app installation (the Sonim x320 can install apps without ADB).
@chatzie tried building an accessibility based solution, didn’t either work.
Not great.
I’m sure most of us can easily bypass that.
But it would have to work, because there was nothing better.
And then…
Drumroll, please.
