Android

17673 readers

70 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.

Support, technical, or app related questions belong in: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

See thread

Chat and More

founded 1 year ago

MODERATORS

[email protected]

Fitbit Charge 5 units dying, Google says it's not because of updates (9to5google.com)

submitted 9 months ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 9 months ago (2 children)

I've had several Google products just die after an update. I don't really trust them anymore.

[–] [email protected] 3 points 9 months ago (1 children)

The charge five isn't really a Google product. Google were still in the process of buying Fitbit when it was released. And as someone who's owned the charge HR (bad band), the charge 2 (great device, miss it), the charge 3 (died randomly - screen was backlit, device was charged but it would not wake up after an update), the charge 4 (still going strong, use it for work), and the charge 5 (too fragile in my opinion but a nice device), I can't say I'm too surprised. The software update I will admit is google, but Fitbit had problems with device QC and quality long before Google bought them.

[–] [email protected] 2 points 9 months ago

You know it's just sad. Fitbit buying Pebble and not using any of that in their watches. Then Google buying Fitbit and not using any of that tech either. Just so much potential being wasted.