This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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 பதிலளி
  • 8 இந்த பிரச்னைகள் உள்ளது
  • 20 views
  • Last reply by chourmo51

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 ?

தீர்வு தேர்ந்தெடுக்கப்பட்டது

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.

Read this answer in context 👍 4

All Replies (1)

தீர்வு தேர்ந்தெடுக்கப்பட்டது

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.