15
submitted 10 hours ago by sabreW4K3@lazysoci.al to c/android@lemdro.id
top 6 comments
sorted by: hot top controversial new old
[-] Fizz@lemmy.nz 10 points 10 hours ago

What you need 64bits for on a watch

[-] merci3@lemmy.world 5 points 9 hours ago

from my understading, a smartwatch is the exact case scenario of a device that needs to be converted to 64 bit only as soon as possible, the reason being the Y2K38 bug.

[-] limerod@reddthat.com 4 points 8 hours ago

That same page says those systems can use 64-bit signed integer to store date time even on 32bit systems.

[-] Toes@ani.social 4 points 7 hours ago

Its harder to make that change (reliably) to your app than it is to publish a arm64 package.

Its also expensive in terms of cpu cycle waste.

[-] ByteMe@lemmy.world 3 points 10 hours ago
[-] Zedstrian@sopuli.xyz 2 points 5 hours ago* (last edited 5 hours ago)

It seems like 2026 is the year that Google’s other platforms will embrace the 64-bit era. Android TV and Google TV will require 64-bit app versions from August, and the company has now announced similar plans for Wear OS.

this post was submitted on 02 Apr 2026
15 points (89.5% liked)

Android

21677 readers
46 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.

🔗Universal Link: !android@lemdro.id


💡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: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 2 years ago
MODERATORS