Blaze doesn't display correct time or accept clock face settings

[fsBlaze]

So this is my first fitbit device and i walked through all the setup steps, followed all instructions and it seemed to be working fine at first with an occasional exclamation point when it tries to sync.  But on subsequenet syncs it works (most of the time).  Less that a day after it's now displaying rather random times, it's not a time zone difference.  It's off by random hours and minutes.  I also changed the clock face a few times and it shows the same clock face it had when I started.  It charges fully and even when is says sync error, I seem to see the current step count in the app.  But the blaze says I don't have any alarms set and I did set them.

It also doesn't give me any of the reminders that it's time to move (my coworker claimed he was getting a light buzz to tell him every hour to get up and hit the hourly 250 step target).  I've set that up and nothing.

I followed steps in several topics in the forum, resetting the phone, resetting the blaze, deleting and repairing the blaze to my phone by deleting the app.  I've changed the timezone around.  Nothing seems to matter.  I'm pretty much ready to return this things since it seems from my experience and what's in the forums that this device is prone to losing its pairings and not syncing properly. 
Any tips before I return it?

[AlejandraFitbit]

A warm welcome to the Community @fsBlaze. Regarding to the clock, I recommend changing your timezone to a complete different one, sync your tracker, put the correct time and sync your tracker one more time. To change the timezone, do the following from a computer:

1. Log into your fitbit.com dashboard and click the gear icon in the top right corner. 
2. Select “Settings” from the drop-down menu. 
3. Scroll down to the Time section and choose the time zone that best reflects your current location. You can also select 12-hour or 24-hour time display format here. 
4. Sync your tracker to update your time zone. 

If you experience any inconvenience syncing, feel free to follow the instructions provided in the Having trouble syncing? post. Now about the reminders to move, please check that this feature is on by doing the following from a computer:

1. Click the gear icon

2. Click Blaze Tracker

3. Check the Reminder to Move information

4. Verify that it is on 

5. Edit the information if needed

6. Sync

I hope this helps, let me know the outcome. 

[fsBlaze]

@AlejandraFitbit

I wasn't super detailed in my original post but I did mention that I had tried changing the time zone.  I did so several times using the steps you mentioned.  I had also gone through those steps to sync up the reminder to move. From chatting with a few people at work it sounds like only 1 out of 5 workers have working reminders to move (it's a mixture of blaze and charge2).

I left my blaze home yesterday all day and didn't have it anywhere near my phone since I posted my question.  And when I just checked it this morning to see if there were any additional steps in your response I could follow I noticed it was happy and synced.  I'm not sure what it synced to since my phone was well over 40 feet away. 

When I try syncing now I get a little red exclamation point that says tracker not found.  I was able to pair up the device when i removed it from my fitbit app and readded it but it won't sync. From the supported device list I noticed it includes Samsung Galaxy Core but not Core Prime.  Could that be the problem?

[Tryinghard1]

Same problem

Is it again an issue with some faulty update?

Why are you doing this fitbit?

[fsBlaze · Accepted solution]

I intentionally waited a bit to see how things worked out and if they broke again but things appear to be working now.  Notifications, reminders, pairing all looking good.  The steps I took to get it working:

1. Removed the blaze from the fit bit app
2. Double checked that it didn't show up as a paired device in my mobile's bluetooth after removing from the fitbit mobile app (don't recall if it was there or not, if it was I would have removed it)
3. Removed all paired devices from the mobile's device list.
4. Re-added blaze to the fit bit app
5. Let it pair up
6. Waited close to a day for pairings and everything to work properly
7. Re-added bluetooth speakers pairings for my cel phone

I don't know if those steps really made the difference or if it was the combination preceded by the large number of steps that I took before this (going through many variations of all the steps in this post, the original post, the replies to this post, and other threads that in the forum where people ran into issues with pairing.

I'm anonymous here so you can take this with a grain of salt, but I am an experienced software engineer who spent a lot of time writing and debugging code, including time writing device drivers, thought not for mobile devices.  Based on the number of random permutations I went through to eventually get this working and all the issues in this forum people have with pairing the device, I'd say there is something fundamentally unstable in how the fitbit android app pairs with the blaze.  I don't know if it's limitations in bluetooth technology, how android exposes that, how the fitbit app uses it, how the blaze uses it, etc...  Once it's working this thing is pretty awesome and I'm glad I stuck with it.  But if these sorts of issues persist I wouldn't hesitate to switch brands or devices if I come across one with comparable (or even reduced) feature set that is seemingly more stable.