Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

How to troubleshoot when logins do not synchronise after transfering Firefox for Android v54.0 from S6 to new S7, while history and bookmarks do sync?

  • 1 odpoveď
  • 8 má tento problém
  • 20 zobrazení
  • Posledná odpoveď od chourmo51

more options

I am changing smartphone from s6 to s7. I use Firefox for Android v54.0 and use the sync functionality mainly for sync Login and Bookmarks with my PC Version (current 54.0) and other devices. After loging in with my sync account on new smartphone, the logins will not synchronize, even after i remove the option "use master password". History or Bookmarks did and still do sync with other devices. Would you please have any troubleshoot steps for me ?

I am changing smartphone from s6 to s7. I use Firefox for Android v54.0 and use the sync functionality mainly for sync Login and Bookmarks with my PC Version (current 54.0) and other devices. After loging in with my sync account on new smartphone, the logins will not synchronize, even after i remove the option "use master password". History or Bookmarks did and still do sync with other devices. Would you please have any troubleshoot steps for me ?

Vybrané riešenie

OK. Today I did de-install Firefox for Android and reinstall it, connect Sync and now...logins were synx. So i assume the issue root cause has to do with the initial direct app transfer from S6 to S7 (per USB). KR.

Čítať túto odpoveď v kontexte 👍 4

Všetky odpovede (1)

more options

Vybrané riešenie

OK. Today I did de-install Firefox for Android and reinstall it, connect Sync and now...logins were synx. So i assume the issue root cause has to do with the initial direct app transfer from S6 to S7 (per USB). KR.