Google Pixel

5906 readers

81 users here now

The World's Google Pixel community!

This community is for lemmings to gather and discuss all things related to the Google Pixel phone and other related hardware. Feel free to ask questions, seek advice, and engage in discussions around the Pixel and its ecosystem.

We ask you to be polite when addressing others and respect Lemmy.world's rules.

NSFW content is not allowed and will immediately get you banned.

It also goes without saying that self-promotion of any nature and referral links are not allowed. When in doubt, contact the mod team first.

Also, please, no politics.

For more general Android discussions, see [email protected].

This community is not in any way affiliated with Google. If you are looking for customer support regarding your Pixel phone, look here instead: https://support.google.com/pixelphone/

founded 1 year ago

MODERATORS

AlmightySnoo

mandlar

hackitfast

104

Pixel 4a (not 5G) owners, what do you plan to do with your phone now that it reached its final Android update? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by AlmightySnoo to c/googlepixel

66 comments fedilink hide all child comments

This month is the final month of guaranteed major and security updates, and we already know Android 14 won't land in the Pixel 4a (though it will in the Pixel 4a 5G as it has guaranteed updates until November).

So for those of you who own that phone, what do you plan to do with it? Are you going to keep using it for a couple more years without the updates? Install a custom ROM (which one?)? Or are you maybe planning to get a new phone (a Pixel?)?

If you still own an older Pixel phone, how are you keeping it alive?

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

[–] [email protected] 10 points 1 year ago

But even then, I still don't get why that has to be the case. Linux still supports drivers for very ancient hardware.

Linux is kinda infamous for not having any stable driver interface - it doesn't really have a concept of drivers in the way Windows does, Linux drivers are just indistinguishable parts of the kernel and their only way to interact with the rest of the kernel is to use the internal kernel functions that have no stability guarantee.

The idea is that if someone wants to change any of the internal functions, they will also be expected to go and find all parts of the kernel that would be affected and update them to work with the change. That works great for "drivers" that are part of Linux, but it makes maintaining out-of-tree drivers a nightmare.

This isn't going to get any better until either Linux gets a stable driver API (fat chance) or SoC manufacturers decide to release their drivers under GPLv2 and go through the effort of mainlining them into the kernel (also a fat chance - current situation works great for them and guarantees more sales of new SoCs).