this post was submitted on 18 Apr 2024
75 points (98.7% liked)

Android

17826 readers
67 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
you are viewing a single comment's thread
view the rest of the comments
[–] henfredemars@infosec.pub 35 points 8 months ago (1 children)

OK, this is really cool. We have practically zero insight into the longevity of these things. Even if you know what chips are being used, lack of information about the wear leveling algorithms means there isn’t much that we can say about the real world performance under different loads.

[–] ExtremeDullard@lemmy.sdf.org 21 points 8 months ago* (last edited 8 months ago) (5 children)

We have zero insight into the longevity of flash memory because it doesn't matter: whatever it is, it's a lot longer than the phone's planned obscolescence.

That's why you've never heard anybody complain about their saved data getting corrupted: their device has long since hit the landfill before that happens.

[–] henfredemars@infosec.pub 13 points 8 months ago

I must disagree. I’ve encountered a couple of phones from people in my family that could not be restored because the flash itself was bad. The flash memory specifically failed and required them to purchase a new phone.

We’re talking 5 to 7-year-old phones here. It does happen. There are plenty of people who will never replace their phone until it breaks.

For another example, consider that Google added forward error correction to their system images because they encountered issues with failing memory chips in the wild. This was an effort to keep devices booting and operable for longer.

[–] Daxtron2@startrek.website 9 points 8 months ago (1 children)

Can't agree with that, I've definitely had corrupted data events happen in the past.

[–] possiblylinux127@lemmy.zip 7 points 8 months ago (3 children)
[–] Liz@midwest.social 7 points 8 months ago (1 children)

It depends on the storage medium. SD cards will fail if you use them enough. Photographers and videographers will run into to problem every once in a while, especially if they're a professional. Why SD cards in particular have a tendency to fail, I can't exactly say. It might just be their form factor making internal physical damage more likely. I say internal, because the issue is that a normal looking SD card will one day turn up corrupted for no obvious reason.

I haven't heard of any other type of flash memory having lifespan issues for regular consumers.

[–] possiblylinux127@lemmy.zip 1 points 8 months ago (1 children)

I've used the same microsd for years. Granted it isn't heavily used.

[–] Liz@midwest.social 3 points 8 months ago (1 children)

Yeah it's at the level of frequency where an ordinary user with one SD card is unlikely to have a problem, but if photography is your hobby it's only a matter of time. In a rather informal poll conducted by Chelsea and Tony Northrup, they basically found that two thirds of the most active photographers had experienced at least one SD card failure. It basically was just a direct correlation with how many photographs you've taken.

[–] possiblylinux127@lemmy.zip 1 points 8 months ago (1 children)

Flash has a limited number of writes so that makes sense

[–] Liz@midwest.social 1 points 8 months ago (1 children)

Yeah but the practical write limit tests I've seen for SSDs (from ten years ago) put it well beyond what even a professional photographer would do. We're talking SSDs that sustained constant writing of random data 24/7 and didn't fail for more than a year. There's just something about SD cards. As further "proof," photographers don't complain about their SSDs failing on them, even though those should have more write cycles than their SD cards.

[–] mudeth@lemmy.ca 2 points 8 months ago (1 children)

SD cards don't perform wear leveling while ssds do. This is why there are specific SD cards meant for surveillance cameras. They have additional wear levelling circuitry at the expense of speed.

So photographers who fill up their sd cards end up writing over the same spots repeatedly and wear them out.

[–] Liz@midwest.social 1 points 8 months ago

No shit? Well today I learned. That's definitely going to reduce lifespan. I guess that means you should try to fill your card as much as possible before formatting it.

[–] Daxtron2@startrek.website 5 points 8 months ago

Not a whole lot to share. Phone was unstable for a bit and one day refused to boot past a blank screen. As far as I could tell from trying to pull data off it, something got corrupted and it could no longer boot but my data was all encrypted with no way to pull it off.

[–] stuner@lemmy.world 1 points 8 months ago (1 children)

I have seen multiple (quality) SSDs with unrecoverable read errors after a few years. All of them had plenty of spare area left. Maybe some kind of retention issue?

[–] possiblylinux127@lemmy.zip 1 points 8 months ago (1 children)

How does that apply to android?

[–] stuner@lemmy.world 1 points 8 months ago

The UFS storage inside an Android smartphone is basically an SSD. Both use flash memory, so it's reasonable to expect that they have similar failure modes. But I'm not sure if you could diagnose such a failure on Android.

[–] biscuit 7 points 8 months ago

I take it you weren't around for the Nexus 7 (first edition)?

[–] redcalcium@lemmy.institute 5 points 8 months ago

I wonder if it's still true now that most phone manufacturers enable Memory Extension by default. This feature will likely reduce storage lifespan especially on low end devices that don't have big RAM.

[–] Sylvartas@lemmy.world 3 points 8 months ago

I've had two phones die because of the storage chip, around 5-6 years after buying them.