11-23-2022
11:06
- last edited on
12-14-2022
15:00
by
YojanaFitbit
11-23-2022
11:06
- last edited on
12-14-2022
15:00
by
YojanaFitbit
I updated to Android 13 today.
From then on, no sync possible anymore.
I already:
Now I'm stuck with a watch that can't be connected anymore and is stuck in install mode.
Edit: To clarify. The Charge 5 is being seen via bluetooth, i get's found by the app, but it doesn't complete the connection.
Answered! Go to the Best Answer.
12-09-2022 07:29
12-09-2022 07:29
I mean if it comes down to it are people going to tell their friends to not buy android or fitbit for christmas?
Sounds like google/android effectively just killed fitbit for the holiday season.
12-09-2022 07:31
12-09-2022 07:31
100% agree
12-09-2022 07:40
12-09-2022 07:40
12-09-2022 07:56 - edited 12-09-2022 08:04
12-09-2022 07:56 - edited 12-09-2022 08:04
@AbleZombie Most phones affected are Samsung Galaxy Z devices with Android 13. These will be a small fraction of all the phones used with Fitbits. Hence Google / Fitbit and Samsung don't consider this a priority.
Everyone, If you want to raise the profile of this problem you could also subscribe to my two subreddit posts here and here.
12-09-2022 08:01
12-09-2022 08:01
12-09-2022 09:37 - edited 12-09-2022 09:38
12-09-2022 09:37 - edited 12-09-2022 09:38
I tried again, this time by changing various Bluetooth settings in the Android development options menu. (Hidden menu in the Settings)
Deleted the Charge 5 from my account and tried to pair it dozens of times while changing some Bluetooth options.... still without success... I guess it isn't as surprise as I can't change Bluetooth MTU size (packet size) on a unrooted phone...
Anyway... Is it really up to me to do and test this?
I had a false hope when I felt a slight vibration of the Charge 5 while trying to pair it... it was in fact an invitation to move more, 10 minutes before the full time.😅
Fitbit Developers... If your problem is really about the size of the Bluetooth packets as mentioned earlier in this thread... maybe this will help...
Ok.... jk 😜
I reset everything to default and paired again with my Android 13 S7+ tablet.
I give up trying to troubleshoot... I'll sync it with my tablet in the evening from time to time, hoping for a fix someday.
Happy Friday, and good weekend to all !
12-09-2022 09:39 - edited 12-11-2022 13:30
12-09-2022 09:39 - edited 12-11-2022 13:30
Me, too! Mine stopped working on Monday. 12/05. Tried everything to no avail--- restarting phone, restarting Charge 5, restarting Bluetooth after waiting 15 sec, force stopping app, uninstalling and reinstalling Fitbit app, checking permissions Repeated several times. Fixing to cancel
premium services.
Android 13 update no longer allows Bluetooth system app cache to be cleared.
12-09-2022 09:40
12-09-2022 09:40
Good effort
Have a great weekend
12-09-2022 10:37
12-09-2022 10:37
Hello, I've been having the same issue and it has been frustrating trying to get it to connect. I believe it is because of the upgrade on my new phone as it still works on my old one. It can find the fitbit, but can't connect to it. Also, I don't know if it's connected, but my battery on my fitbit has been acting oddly by not always displaying the correct percentage left. Any updates on correcting the main issue would be appreciated. Thanks
12-09-2022 10:46
12-09-2022 10:46
Thanks for the heads up
I now use old phone with Charge 5 once a day to update.
Until they find a fix
12-09-2022
11:11
- last edited on
02-14-2024
12:40
by
MarreFitbit
12-09-2022
11:11
- last edited on
02-14-2024
12:40
by
MarreFitbit
Hello everybody.
I appreciate you taking the time to share your latest experience after the Android 13 update. It seems to have affected Samsung devices.
This situation has been reported and Fitbit is working on a solution already. In the meantime you can try to use a different mobile device to sync your Fitbit. Thanks for your patience.
Have a nice day!
12-09-2022 11:24
12-09-2022 11:24
12-09-2022 14:00
12-09-2022 14:00
Safer to find old phone and sync daily with that
Could be months
12-09-2022 15:47
12-09-2022 15:47
Any updates on this?
12-09-2022 18:24 - edited 12-12-2022 05:56
12-09-2022 18:24 - edited 12-12-2022 05:56
Ok, I have been having the same issue after updating my Samsung Z fold 4 to Android 13. After 3 days of not being able to sync on the Z Fold 4 and reading about other people using other devices and having it work. I tried that with my tablet, and it is working fine! Now for the strange part. My Samsung Fold 4 is now working, not smoothly but my steps are back as long as I sync my tablet and then log out and log back into the Z Fold 4 my steps sync. The sync will not work if I try to sync without syncing the tablet first and I must log out and back in to have the phone have the correct steps, it's as if the phone is working off the blue tooth on the tablet to complete the syncing. This is rather inconvenient to say the least and I hope I don't have to continually do this in order to use my Phone and my Fitbit!
Edit: As of 10 pm on 12/9/2022 although slow the FitBit app on My Z Fold 4 starting syncing again and showing all my steps and other data. However, I still have to log out and log back in to have the steps updated, so there is progress. I just want it back the way it was with the entire syncing issue resolved so that when I open the app the sync takes place quickly without me having to log out and back in!
Edit: Today is 12/12/22- My Z Fold 4 is syncing but still not like it was before the Android 13 update. I still have both my FitBit and the FitBit app on my tablet because I am starting a new challenge today and the steps Must Sync and if not on my phone, then somewhere! The progress that I saw was that I did not have to log out and log back in to get it to sync but it is 1) not registering the steps automatically like it was before the update 2) slow to record it, the sync is several minutes behind the current time even when refreshing the screen and refreshing the screen sometimes brings up an error message that things are taking longer than expected.
I still don't trust the phone to work by itself because, I do not feel the phone is properly paired with the FitBit, I am dealing with a new Fitbit Device( my old one was just fine and as I thought was not the issue) which paired properly on my tablet (received 4-digit code) but did not receive a code when trying to pair it with my phone! So, the phone is getting the data but not directly as far as I can see! An earlier poster said my tablet was uploading to the cloud and my account was being updated and then the phone looks like it's syncing when in fact, the tablet is direct and the phone is indirect, that makes sense! Just wanted to keep you all updated as we all go through this process!
12-09-2022 19:08
12-09-2022 19:08
I'm having the same problem. Just started after update on my zflip4 phone.....
Did all the things suggested above...😞
Fitbit update as well???
Contact us. Please
12-09-2022 19:15
12-09-2022 19:15
Thanks for posting this, glad it's being looked into.
12-09-2022 19:52
12-09-2022 19:52
12-09-2022 20:42
12-09-2022 20:42
Is there any plan to communicate a timeline on when this will be fixed? The advice to just use another phone isn't practical, neither is the advice to keep checking the app for updates. I'm having to contact your customer service everyday, and your twitter folks don't even respond to me anymore. Very very poor customer service. Atrocious.
12-10-2022 02:18
12-10-2022 02:18