this post was submitted on 16 Jun 2023
590 points (100.0% liked)

Technology

37630 readers
274 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] catacomb@beehaw.org 1 points 1 year ago

Thanks for the info. From the perspective of GrapheneOS, verified boot for custom firmware is going to be one of the most important aspects and that wasn't something I expected from the device. It would be a nice-to-have for longevity as running an unlocked bootloader is an awful idea. The lack of a secure element also won't help the case. I was aware that "support" might mean "only security patches past two years" which is acceptable to me.

However, I can see your point about fixes from SoC manufacturers as that is a crucial part of these updates. I was aware that the SoC was older but only really thought about performance impacts. In that case, the device will only receive Android platform and kernel fixes?

Maybe I'll have to think about switching to something else after that point, then. I spent about as much as I wanted to on a phone and it will only be unfortunate that I didn't get more years out of it. I've already been slightly concerned that they're steering away from their "mission" and selling ordinary earbuds which are unsustainable by their own standards.