fitbit

google-reshapes-fitbit-in-its-image-as-users-allege-“planned-obsolescence”

Google reshapes Fitbit in its image as users allege “planned obsolescence”

Google Fitbit, emphasis on Google —

Generative AI may not be enough to appease frustrated customers.

Product render of Fitbit Charge 5 in Lunar White and Soft Gold.

Enlarge / Google Fitbit’s Charge 5.

Fitbit

Google closed its Fitbit acquisition in 2021. Since then, the tech behemoth has pushed numerous changes to the wearable brand, including upcoming updates announced this week. While Google reshapes its fitness tracker business, though, some long-time users are regretting their Fitbit purchases and questioning if Google’s practices will force them to purchase their next fitness tracker elsewhere.

Generative AI coming to Fitbit (of course)

As is becoming common practice with consumer tech announcements, Google’s latest announcements about Fitbit seemed to be trying to convince users of the wonders of generative AI and how that will change their gadgets for the better. In a blog post yesterday, Dr. Karen DeSalvo, Google’s chief health officer, announced that Fitbit Premium subscribers would be able to test experimental AI features later this year (Google hasn’t specified when).

“You will be able to ask questions in a natural way and create charts just for you to help you understand your own data better. For example, you could dig deeper into how many active zone minutes… you get and the correlation with how restorative your sleep is,” she wrote.

DeSalvo’s post included an example of a user asking a chatbot if there was a connection between their sleep and activity and said that the experimental AI features will only be available to “a limited number of Android users who are enrolled in the Fitbit Labs program in the Fitbit mobile app.”

Google shared this image as an example of what future Fitbit generative AI features could look like.

Google shared this image as an example of what future Fitbit generative AI features could look like.

Fitbit is also working with the Google Research team and “health and wellness experts, doctors, and certified coaches” to develop a large language model (LLM) for upcoming Fitbit mobile app features that pull data from Fitbit and Pixel devices, DeSalvo said. The announcement follows Google’s decision to stop selling Fitbits in places where it doesn’t sell Pixels, taking the trackers off shelves in a reported 29 countries.

In a blog post yesterday, Yossi Matias, VP of engineering and research at Google, said the company wants to use the LLM to add personalized coaching features, such as the ability to look for sleep irregularities and suggest actions “on how you might change the intensity of your workout.”

Google’s Fitbit is building the LLM on Gemini models that are tweaked on de-identified data from unspecified “research case studies,” Matias said, adding: “For example, we’re testing performance using sleep medicine certification exam-like practice tests.”

Gemini, which Google released in December, has been criticized for generating historically inaccurate images. After users complained about different races and ethnicities being inaccurately portrayed in prompts for things like Nazi members and medieval British kings, Google pulled the feature last month and said it would release a fix “soon.”In a press briefing, Florence Thng, director and product lead at Fitbit, suggested that such problems wouldn’t befall Fitbit’s LLM since it’s being tested by users before an official rollout, CNET reported.

Other recent changes to Fitbit include a name tweak from Fitbit by Google, to Google Fitbit, as spotted by 9to5Google this week.

A screenshot from Fitbit's homepage.

Enlarge / A screenshot from Fitbit’s homepage.

Combined with other changes that Google has brought to Fitbit over the past two years—including axing most social features, the ability to sync with computers, its browser-based SDK for developing apps, and pushing users to log in with Google accounts ahead of Google shuttering all Fitbit accounts in 2025—Fitbit, like many acquired firms, is giving long-time customers a different experience than it did before it was bought.

Disheartened customers

Meanwhile, customers, especially Charge 5 users, are questioning whether their next fitness tracker will come from Fitbit Google Fitbit.

For example, in January, we reported that users were claiming that their Charge 5 suddenly started draining battery rapidly after installing a firmware update that Fitbit released in December. As of this writing, one thread discussing the problem on Fitbit’s support forum has 33 pages of comments. Google told BBC in January that it didn’t know what the problem was but knew that it wasn’t tied to firmware. Google hasn’t followed up with further explanation since. The company hasn’t responded to multiple requests from Ars Technica for comment. In the meantime, users continue experiencing problems and have reported so on Fitbit’s forum. Per user comments, the most Google has done is offer discounts or, if the device was within its warranty period, a replacement.

“This is called planned obsolescence. I’ll be upgrading to a watch style tracker from a different company. I wish Fitbit hadn’t sold out to Google,” a forum user going by Sean77024 wrote on Fitbit’s support forum yesterday.

Others, like 2MeFamilyFlyer, have also accused Fitbit of planning Charge 5 obsolescence. 2MeFamilyFlyer said they’re seeking a Fitbit alternative.

The ongoing problems with the Charge 5, which was succeeded by the Charge 6 on October 12, has some, like reneeshawgo on Fitbit’s forum and PC World Senior Editor Alaina Yee saying that Fitbit devices aren’t meant to last long. In January, Yee wrote: “You should see Fitbits as a 1-year purchase in the US and two years in regions with better warranty protections.”

For many, a year or two wouldn’t be sufficient, even if the Fitbit came with trendy AI features.

Google reshapes Fitbit in its image as users allege “planned obsolescence” Read More »

“time-to-move-on”:-fitbit-owners-fed-up-with-battery-problems,-google-response

“Time to move on”: Fitbit owners fed up with battery problems, Google response

Fitbit Charge 5

Enlarge / The Fitbit Charge 5 came out in September 2021.

Google

Fitbit owners are getting frustrated with Charge 5 fitness trackers quickly losing their charge and, in some cases, exhibiting additional problems. Google has denied that the problems are tied to firmware updates. But users remain skeptical, and some are fed up with Google’s limited response to a recurring problem.

Charge 5 battery complaints

On December 21, Fitbit announced Charge 5 firmware update 194.91 on its support forum. On paper, the update seemed typical, promising things like new clock faces, support for right-to-left text, and “bug fixes and improvements,” per the release notes.

But by early January, there were complaints on the forum from people who said they updated their Charge 5 and then saw their device’s battery suddenly drain much faster. Examples include one user claiming their battery life drains from 100 percent to 0 percent in 25 minutes and others saying their Charge 5 lasts about 12 hours. Most say their Charge 5 no longer lasts for a full day despite staying powered for days between charges before the update. The problems led a user going by Ge0ffh to call his device “completely unusable.”

A user named Disappointed01 said:

My Charge 5 (2yrs [sic] old) was working fine until I ran this update. Now I have to recharge it as least twice a day. Fully charged last night wore it for sleeping & flat when I awoke this morning. Have tried resetting … as per the advice on here. Has made no difference. Really disappointed as I love my Charge 5. I see a direct correlation between this battery issue and the update even though Fitbit reckon that’s not the case.

There are similar recollections and accusations against the firmware update on the support thread, which is 21 pages long as of this writing.

One user on the thread reported that they live in a household with three Charge 5s and that theirs is the only one with the latest firmware update and the only one experiencing problems.

Google denies firmware problem

The BBC was the first to report on concerns about the Charge 5’s latest firmware. Today, it reported that Google denied problems with the update.

“We’re still investigating this issue but can confirm it is not due to the recent firmware update,” a Google spokesperson told the BBC, which noted that Google’s rep “did not offer any alternative explanation.”

The Google spokesperson also advised users to keep updating their devices and to contact customer service if they have problems.

On the thread announcing the update, a Fitbit moderator has also advised users to contact Fitbit and conduct basic troubleshooting.

When I looked through the 21 pages of mostly complaints on the support thread, I saw a few people who reported that the firmware update did not result in Charge 5 problems.

But there are also numerous threads online (examples here, here, here, and here) demonstrating newfound frustration with the Charge 5.

“Time to move on”: Fitbit owners fed up with battery problems, Google response Read More »

don’t-miss-this-fitbit-sense-2-deal,-back-at-its-best-black-friday-price

Don’t miss this Fitbit Sense 2 deal, back at its best Black Friday price

internal/modules/cjs/loader.js: 905 throw err; ^ Error: Cannot find module ‘puppeteer’ Require stack: – /home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js: 902: 15) at Function.Module._load (internal/modules/cjs/loader.js: 746: 27) at Module.require (internal/modules/cjs/loader.js: 974: 19) at require (internal/modules/cjs/helpers.js: 101: 18) at Object. (/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js:2: 19) at Module._compile (internal/modules/cjs/loader.js: 1085: 14) at Object.Module._extensions..js (internal/modules/cjs/loader.js: 1114: 10) at Module.load (internal/modules/cjs/loader.js: 950: 32) at Function.Module._load (internal/modules/cjs/loader.js: 790: 12) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js: 75: 12) code: ‘MODULE_NOT_FOUND’, requireStack: [ ‘/home/760439.cloudwaysapps.com/jxzdkzvxkw/public_html/wp-content/plugins/rss-feed-post-generator-echo/res/puppeteer/puppeteer.js’ ]

Don’t miss this Fitbit Sense 2 deal, back at its best Black Friday price Read More »