Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

When downloading a file, firefox causes com.android.phone to stop

  • 1 отговор
  • 2 имат този проблем
  • 29 изгледи
  • Последен отговор от Paul

more options

as the title says when downloading a file, firefox causes com.android.phone to crash. enough crashes causes my tablet to panic and auto restart itself.

the only app that can cause this is is firefox, downloading files via something like discord, doesn't trigger it, only firefox. i tried with other apps to no avail.

it started happening after an update (update TB-X606F_S301018_230810_BMP ) (the last update was a year ago so lenovo isn't gonna fix it on their end anytime soon) and it's quite annoying when i need to use firefox to download files to view/use.

Details:

 Device: Lenovo Tab M10 FHD Plus (TB-X606F)
 Android Version: 10
 Firefox version: 117.1.0
 security update: 2023 Aug
 Google play system update: 2023 May
 Lenovo system version: TB-X606F_S301018_230810_BMP
as the title says when downloading a file, firefox causes com.android.phone to crash. enough crashes causes my tablet to panic and auto restart itself. the only app that can cause this is is firefox, downloading files via something like discord, doesn't trigger it, only firefox. i tried with other apps to no avail. it started happening after an update (update TB-X606F_S301018_230810_BMP ) (the last update was a year ago so lenovo isn't gonna fix it on their end anytime soon) and it's quite annoying when i need to use firefox to download files to view/use. Details: Device: Lenovo Tab M10 FHD Plus (TB-X606F) Android Version: 10 Firefox version: 117.1.0 security update: 2023 Aug Google play system update: 2023 May Lenovo system version: TB-X606F_S301018_230810_BMP

Всички отговори (1)

more options

Hi

This is something that our developers are looking into and hope to have resolved very soon. You can follow progress on this at:

https://bugzilla.mozilla.org/show_bug.cgi?id=1847141