You'd think I'd know by now. *Never* update your Fitbit when everything is working, but I had to go ahead and take the latest update (4.2?) like an idiot...
Since then, the music control function only works once, until I reboot both my phone (Motorola X4, Android 9) and my Versa to use music controls again. Until I reboot everything, the watch connects but just says "Start playing music on your phone..." and I have no music controls (back, play, fwd, etc.) available.
This isn't the first time a Versa update broke the music controls, but at least last time you had a fix update issued within a week. Other than that one week from the bad update, music controls worked more or less consistently with my X4. (Very occasionally I had to reboot the watch and phone to get them to work together again, but now it's constantly!)
How hard is it to get this right? My old Pebble watches never failed to work as music controllers, and they were compatible with a lot more music apps than the Versa ever was. The Versa seems to trying too hard- Pebble just functioned as a generic bluetooth AVRCP device, but the Fitbit seems to overcomplicate things.
I love having my Fitbit built into a smartwatch, but I'm this close to going back to my old separate Fitbit Zip and Pebble watch until the next Versa firmware update. Consistent music control is far more important to me than having my step counter built into my watch! (Plus the Pebble can reply to texts with more than 5 canned replies!)
