Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Поиск в поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 2 ответа
  • 2 имеют эту проблему
  • 84 просмотра
  • Последний ответ от 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?