Hello,
I’m experiencing an issue with Brave on Android on my Samsung Galaxy S25 Ultra regarding autofill for passwords, addresses, and payment cards.
I use Proton Pass as my external autofill service. In Brave’s settings, I selected “Autofill using another service”, and I also disabled Brave’s built-in password, address, and payment saving.
However, when I open a login page, the Proton Pass autofill suggestion does not appear above the keyboard. To make it show up, I have to tap repeatedly and switch between the “username” and “password” fields many times before the autofill suggestion finally appears.
The problem does not seem to come from Proton Pass or the keyboard. I tested with Microsoft SwiftKey and also with the default Samsung keyboard, and the issue occurs with both.
I also tried the same test with Google Chrome, using exactly the same autofill settings (“Autofill using another service”), and everything works correctly. The autofill bar appears immediately above the keyboard without needing to tap multiple times.
So my questions are:
-
Is this a known issue with Brave on Android?
-
Has anyone else experienced the same behavior?
-
Is there a fix or a setting that could resolve this?
Thanks in advance for your help.
I’ve been trying out Proton Pass for the last couple of days and it’s going out the window before not too long but that’s another story.
So you’ve set PP as your PW manager then switch back to ‘Autofill with Brave’.
I am also a Proton Pass (PP) user.
Yes, I experienced similar issue before, on my android device. It was a couple of months back. Now I can’t say if it was specific to Brave.
I went away from using PP for about a week or two. But ended up reinstalling it again.
As of now, I have been using PP on the same device without any issues for more than a month.
I’m having the same issue. Did the disable+reenable with autofill service on both Android and then Brave settings. Still having issues with it.
On Chrome, I realized I never enabled Autofill With Other Services, but after that, it just works. I’ve tried with Bitwarden as well, it also doesn’t work on Brave. Even when it appears, it’d often just say there’s no content to autofill.
I’ve just updated Brave as well, it is Brave 1.88.133, Chromium 146.0.7680.119, on Samsung A55 Android 14; Build/UP1A.231005.007. I use FUTO Keyboard if that matters, but I don’t think it should.
Edit:
Wait, it works now, after I enabled Autofill With Brave? That seems… Weird, and the reverse of the expected result from the setting description.
It does require me to deselect + reselect the user/password field first, but at least it seems to work now?
@bbhalim I don’t know whether this is a Chromium thing or a Brave thing but it was the only method I could find for either Bitwarden to work and now Proton Pass.
I never use Chrome and it always remains disabled but I’m not totally sure what you mean by:
“It does require me to deselect + reselect the user/password field first, but at least it seems to work now?”
Ah, to clarify, I meant:
- The behavior in Chrome and Brave, with Proton Pass and Android 14 (OneUI 6.1), was weirdly opposite for me. Most of my searches shows that I should DISABLE Autofill with Chrome and ENABLE Autofill using another service on Chrome… but per the screenshot, the OPPOSITE works for me on Brave, enabling with Brave fixed it for me.
- “It does require me to deselect + reselect the user/password field first, but at least it seems to work now?” What I mean is that, sometimes, the autofill doesn’t appear on my keyboard. When I open a login page, tap on the username/password field, it won’t appear. What I need to is tap on the field, tap somewhere else, and then tap again on the username/password field. NOW it appears. Very weird behavior, but as I said, it works and I can autofill now.
Overall, it’s just a weird janky behavior, but that’s how I solved it on my device.
Its a known issue/nice security feature of Android. 
You should of seen it before external autofill was being supported in Android, Ive broken a few keyboards lol.
If proton pass is not running, keep in mind that its a secure application, rolling in with system calls that also need to pass sig checks in cHromium and its also needing you the user to hit go the first time in Brave, if it was not active.. Like bombs over bagdad active, Android’s "app optimization will shelve your autofill client, so make sure proton pass os not optimized.
This actually was a bit of an issue in windows too, but the built in autofill can be run as a web app there, and it can pass right on over to your prefered autofill now, without some phantom battery nazi causing undiagnosed issies..
But in Android, you the user, do not actually have permission to be making device management decisions, and its probably for the best, because all those password services have an active/unpatched vulnerability when running as an extension on desktop machines.
Thank you for the explanation, but it doesn’t quite match my experience.
If the issue were caused by Android itself, it should occur consistently regardless of the external password manager or the browser being used. However, as I mentioned in my original post, I tested this with Google Chrome and encountered no issues at all.
When I select “Autofill with another service,” the Proton Pass autofill bar (which appears just above the keyboard) shows up instantly as soon as I tap on the username or password field on a login page.
With Brave, however, this behavior is different. The Proton Pass bar does not appear immediately. I have to tap somewhere outside the input field (any blank area on the page), then tap back into the field, sometimes repeating this 5 or 6 times, before the Proton Pass bar finally appears.
So if this were truly an Android-related issue, why does it work perfectly in Chrome but not in Brave?
I had two example videos of the login page on this site, one with Google Chrome and one with Brave, but I’m unable to post them because I’m a new user, sorry about that.
I’m not an expert, but since both browsers are based on Chromium, could this be caused by a specific setting difference between them ? For example, something in the chrome://flags configuration ?
\\\**edit**
Check your Android settings to see if ProtonPass can be added in to handle passwords & (*or) autofil. On my phone, an S24, Android 16, UI 8, these are combines into one setting and allows adding (in my case NordPass),
whereas,
on my dev device, running Android 13, One UI 5.1, where Debo(google) is doing his usual Debo’ing, the settings are seperate. Anyway, they’e located here on my newer device:
Settings>Security & Privacy>More Security Settings>Passwords Passkeys & Autofil>
\\\**EditComplete
**
i see.. Well I have proton pass too but it took me years to get Nordpass to respond the way I want it too, and every time I think I should try it, that um, ptsd kicks in lol. The only thing I can offer is that chrome has those workflows built into, and tested in Android before it’s released. And yeah, I mean I realize brave is built on chromium but you know how google likes to lock stuff down “for your security.” 
I have a ticket in with NordPass to get some help from a real dev about a similar issue as what I used to experience in Brave. Telegram now lets you use passkeys, and i set one up while this was beta. Now, when Im trying to set up a passkey for my alt account, google comes bossing in like Debo, and Nordpaas never sees the request. Now this further solidifies my thinking, that with this type of access to those request built into the OS, etc etc, google etc.. Also, telegram is a great place to upload some videos, and Im sure they will help with this thread. Thats it for now Jimbo, I’ll let ya know if I get any good info from NordPass.
