Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Firefox crashes whenever I connect my Sync account to my phone

  • 6 wótegrona
  • 3 maju toś ten problem
  • 2 naglěda
  • Slědne wótegrono wót philipp

more options

Over the past week or so, I have been struggling with using Firefox paired with my Sync account, for it has crashed randomly whenever I am connected to the Internet (my phone's connectivity is only part-time.)

Specs: Starmobile KNIGHT X, KitKat

Over the past week or so, I have been struggling with using Firefox paired with my Sync account, for it has crashed randomly whenever I am connected to the Internet (my phone's connectivity is only part-time.) Specs: Starmobile KNIGHT X, KitKat

Wšykne wótegrona (6)

more options

hi bonarae, can you type about:crashes into the address bar of your firefox on android and paste the latest few crash ids into a reply here in the forum? thank you!

more options
more options

thank you. this appears to be a crash on some less common devices triggered by sync that is being investigated by mozilla's developers at the moment.

could you try to replicate the issue by using a current firefox 38 aurora build which is available as .apk from https://wiki.mozilla.org/Mobile/Platforms/Android#Download_Aurora if so can you get the id of the crash signature again and report it here as well?

many thanks and sorry about the issue...

more options
more options

Still having the issue as of the latest Aurora build.

more options

hi bonarae, yes unfortunately it's an ongoing issue still (you could also follow along in bug #1138943). maybe the developers working on fixing this would want to get in contact with you to gather some more information on the issue...