Skip to main content
MikeC
New Member
May 22, 2026
Question

How to disable Android Autofill across the device?

  • May 22, 2026
  • 4 replies
  • 209 views

We’re currently using a mix of Android 13 and 14 devices (specifically Zebra mobile computers). With some recent update, across all applications users see popups to perform autofill on form inputs. We’re currently using SOTI’s Mobicontrol EMM along with SOTI’s Surf browser. So this isn’t limited to Chrome.

This also occurs on the Search Apps input field.

Is there any way to completely disable this? It’s causing significant impact.

4 replies

MikeC
MikeCAuthor
New Member
May 22, 2026

I have ongoing tickets with Zebra and SOTI as well on this issue, I’m just trying to tackle it from multiple angles.

mattdermody
Level 3.0: Honeycomb
May 25, 2026

Yes I have been dealing with the same. Another frustrating auto-update Google has forced out without any clear management controls. 

It appears to be a subactivity of GMS.

com.google.android.gms/.autofill.ui.AutofillActivity

The only method I’ve found to suppress it is to force uninstall recent GMS updates to downgrade the device to the version build into the BSP. Its a less than ideal temporary stopgap but it ultimately removes the auto fill prompting.

Google should be aware that my customers would rather downgrade all GMS features back to a v23.x version than to otherwise deal with these pain points introduced by a v26.x version.

Moombas
Level 4.4: KitKat
May 26, 2026

But wouldn’t be a switch to Zebra EKB helpfull in such cases?
Would also provide full version control then and getting rid of GMS in same go.

Even we don’t work with Zerba devices anymore in my part of the company, i remember we used it very likely and (if doesn’t changed) is withut any additional costs.

mattdermody
Level 3.0: Honeycomb
May 26, 2026

If you install EKB and apply the appropriate MX to disable other input types then you can suppress this. The issue however is that this new AutoFill appears as a new input type separate from Gboard so even if you had Gboard previously disabled it could appear as a new keyboard input type for the end users. Once multiple are enabled the users can typically see a globe icon on their screen enabling them to toggle between input types, which we don’t want them to have access to. Ultimately just one of those leaky boat issues with Android. It is constantly springing leaks thanks to unwanted and unmanageable forced updates from Google and we’re left trying to plug those holes. I can’t imagine why Google would think AutoFill on a shared dedicated device would be a good idea but it’s more so likely that Google isn’t thinking about that use case at all when forcing these things out. 

 

 

Lizzie
Community Manager
May 27, 2026

Hey ​@MikeC, ​@mattdermody, ​@Moombas,

 

Thanks for highlighting this. I can understand your frustration on this. I’m just asking about this internally and will search out the ticket. I’ll come back when I have more information. 

 

Please do continue to share your experience on it. 

 

Thanks,

Lizzie

Welcome to the Community everyone!
Lizzie
Community Manager
May 27, 2026

Hey ​@MikeC, ​@mattdermody, ​@Moombas,

 

Me again, speaking with our team, I wanted to check have you tried enabling the ‘Disallow Autofill’ policy? As this control block this feature.

 

If you have this set and it’s not working, either way can you let me know please?

 

Thanks so much, speak soon.

Lizzie

Welcome to the Community everyone!
Moombas
Level 4.4: KitKat
May 27, 2026

At least from my side and neither in Soti nor oemconfig, haven’t seen such setting available anywhere yet.
@mattdermody, how about you?


And a side question ​@Lizzie : Does this functionality have an own bundleid we could block instead until the functionality is available in the MDM (if i haven’t overseen it)?

Lizzie
Community Manager
May 27, 2026

It would be good to hear whether you can find it ​@mattdermody

 

Unfortunately, I don’t think it’s possible to get a bundleID for this type of policy, even if it would be possible I would be wary initiating a block as it could possible impact other things. 

If it looks like the policy isn’t available via SOTI, I would recommend contacting SOTI directly to see what they would suggest here. 

 

 

Welcome to the Community everyone!