05-26-2020 21:27
05-26-2020 21:27
Whenever there is a firmware update these forums are inundated with messages from distraught users who have found that the update has bricked their device, or made it unusable in some other way, eg. vastly reduced battery life. On the other hand, presumably many users, most of whom do not post here, update without problems. Does Fitbit, or anyone else, have any idea on what causes the faulty updates? Is it maybe third party apps or clock faces that are not tested with the new firmware, or devices with low free memory due to music or other data filling the device, or does the update stress the hardware (eg. thermally - some Nexus phones had this problem) so that some fraction will fail, or maybe glitches in the communication (WiFi or Bluetooth).........? Fitbit must have a lot of information on the pre-update status of devices that fail: surely they can figure out this recurring issue. It would be interesting to know too what fraction of devices fail on updating.
05-27-2020 04:04
05-27-2020 04:04
Music memory is reserved for music, I dont think that would be it.
My thought would be a hardware issue with some piece of hardware that is not in spec.
Fortunately i dont notice these posts as much lately