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

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

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

  • 2 réponses
  • 2 ont ce problème
  • 131 vues
  • Dernière réponse par 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!

Toutes les réponses (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?