this post was submitted on 16 Jul 2024
29 points (75.4% liked)

Android

17395 readers
293 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 1 year ago
MODERATORS
 

Funny, the comment types here are the same as on Youtube:

  1. "I still run Android and it is totally fine, will never switch Android just got worse!"
  2. "Well, money"
  3. "Companies need to support phones longer"
  4. "I just use LineageOS on that device"
  5. Misinformation
you are viewing a single comment's thread
view the rest of the comments
[–] boredsquirrel@slrpnk.net 4 points 2 months ago (3 children)

Google doesnt do anything here. The OEMs need to port the Android kernel to older hardware.

They often just support one LTS kernel.

But Android even supports the LTS kernel for 6 years now.

[–] MonkderDritte@feddit.de 6 points 2 months ago* (last edited 2 months ago)

Google doesnt do anything here. The OEMs need to port the Android kernel to older hardware.

Wrong. Google had multiple projects like Treble to decouple the software from the hardware. What happened with it?

[–] MaggiWuerze 3 points 2 months ago* (last edited 2 months ago) (2 children)

Google develops Android and thus is responsible for it's update scheme. They already changed it quite a bit in the last years with GSIs and Project Treble but there's still no real seperation that would allow the same drivers and hardware blobs to be used independent of the Android Version or updating the Android version without these needing to be included every time.

That's what needs to change.

[–] boredsquirrel@slrpnk.net 4 points 2 months ago (1 children)

Their own phones have support for the mainline kernel. It is the vendors that dont want to upstream their drivers and produce half-proprietary garbage they dont publish, so nobody can update these devices.

[–] MaggiWuerze 1 points 2 months ago* (last edited 2 months ago) (1 children)

But Googles decides, that that is possible. I fthey changed the structure to enforce a seperation there's nothing that would keep Android updates from those devices. Put all hardware and device specific stuf in a seperate layer and have it accessible to the updatable system. And it's not like these vendors have an alternative to go to

[–] boredsquirrel@slrpnk.net 2 points 2 months ago (1 children)

Put all hardware and device specific stuf in a seperate layer

Could you elaborate?

Android uses Linux, a monolithic kernel. You cant just separate drivers.

I also heard that OEMs write horrible drivers, which wouldnt work on a microkernel without maaajor porting issues.

[–] MaggiWuerze 1 points 2 months ago (1 children)

And there are Linux distros with rolling releases, where the drivers stay where they are and the OS around them gets updated without issue. I'm sure the smart people at the Android team could do something similar

[–] boredsquirrel@slrpnk.net 4 points 2 months ago (1 children)

The drivers are in the kernel, kept updated with every release. As I said, pixels at least boot with mainline kernel support, but the Android kernel is modded.

And then manifacturer use out of tree drivers as core part of their kernel.

[–] MaggiWuerze 2 points 2 months ago (1 children)

Yes I know the manufacturers do, but there's no reason for the drivers to be replaced when the kernel is updated, you could hold them separately or reapply them after an update

[–] boredsquirrel@slrpnk.net 2 points 2 months ago

This doesnt always work as nonstable kernels (or even porting to a newer kernel) changes in their interface.

Like, backportig patches to a 6 year or more old kernel is crazy! My 6a runs on 5.14 and that is a currently supported phone.

[–] ReveredOxygen@sh.itjust.works 1 points 2 months ago (2 children)

You can run new android on an old kernel, see lineageos

[–] boredsquirrel@slrpnk.net 3 points 2 months ago

Yes and this is not secure. The kernel runs as root.