Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში. აქ არავინ უნდა მოგთხოვოთ ტელეფონზე დარეკვა, შეტყობინების გაგზავნა ან პირადი მონაცემების გაზიარება. რამე საეჭვოს შემჩნევისას გთხოვთ გვაცნობოთ „დარღვევის მოხსენებით“.

ვრცლად

Firefox not using external download manager(1dm)on android 6

  • 2 პასუხი
  • 2 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 208 ნახვა
  • ბოლოს გამოეხმაურა Kiki
  • დაარქივებული

Hello Mozilla Support,

I am using Firefox on Android 6.0.1 (OPPO A57). I enabled the “external download manager” option in Firefox settings because I want to use 1DM (One Download Manager) to handle all file downloads.

However, when I tap on a download link in Firefox, it still uses the built-in downloader and does not give me the option to open 1DM or any external app.

Is there a way to force Firefox to launch 1DM (or any external download manager) when clicking on download links? Please guide me. If not possible, is there a version or workaround that supports this on Android 6?

Thank you!

Hello Mozilla Support, I am using Firefox on Android 6.0.1 (OPPO A57). I enabled the “external download manager” option in Firefox settings because I want to use 1DM (One Download Manager) to handle all file downloads. However, when I tap on a download link in Firefox, it still uses the built-in downloader and does not give me the option to open 1DM or any external app. Is there a way to force Firefox to launch 1DM (or any external download manager) when clicking on download links? Please guide me. If not possible, is there a version or workaround that supports this on Android 6? Thank you!

ყველა პასუხი (2)

It doesn't matter the device other people have this issue there is no way to activate the autofill for a separate password manager no matter what settings are tried for anyone no matter their phone type at least as far as Androids go

Hi Saeed,

I believe you're impacted by this bug. Could you please update your app to 140.0.3 and see if that fix this issue?