this post was submitted on 16 Dec 2024
55 points (96.6% liked)

Android

17813 readers
334 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
 
top 11 comments
sorted by: hot top controversial new old
[–] passepartout 30 points 6 days ago* (last edited 6 days ago) (3 children)

I wonder what this will mean for custom roms. Mediatek are among the only chipsets with available microcode and therefor e.g. supported by OpenWRT, which gives me hope.

[–] Turret3857@infosec.pub 9 points 5 days ago (1 children)

OpenWrt mentioned!!!

also I feel like google knows they'll lose like 25% of their phone market share if they dont allow custom ROMs on pixels. No one's buying a pixel for the "status" and it is not a budget device by any means.

[–] Robust_Mirror@aussie.zone 2 points 5 days ago* (last edited 5 days ago)

I buy it for the camera, best Android camera imo.

[–] UnityDevice@startrek.website 6 points 5 days ago (1 children)

Mediatek has been making phone SoCs since forever now, they have two lines - Helios and Dimensity. They're used in many phones, usually on the lower end. Even Samsung uses them. Both lines have abysmal custom rom support compared to Snapdragon phones, so I don't think you can hope for much there.

[–] Robust_Mirror@aussie.zone 3 points 5 days ago (1 children)

But is that because it's difficult or because it's in phones people don't care about.

[–] rakeshmondal@lemmy.zip 3 points 4 days ago (1 children)

The latter, almost everyone wants to use a phone with a qualcomm chipset, because most app and game developers almost never bother to optimise their software for mediatek processors.

I think it could be because about 10 years ago, mediatek didn't really have any SOCs that could compete with the qualcomm flagships, therefore confining themselves to the budget phone category. Which is what earned mediatek SOCs the reputation of being slow.

That started to change with the release of their dimensity line of SOCs which matched or in some cases even surpassed the performance of Qualcomm flagships but the public perception of mediatek has only recently started changing. Hopefully we see more people buying mediatek SOC based phones so developers have some incentive to optimise their apps for it.

[–] sheogorath@lemmy.world 2 points 4 days ago

I'd argue it's little bit of column A little bit of column B, MediaTek are notoriously slow in releasing their kernel sources, hampering custom ROM development for devices that are using their SoCs.

[–] pirat@lemmy.world 1 points 5 days ago (1 children)

Would you want to run OpenWRT on the phone? If yes, why? I'm genuinely interested in examples of actual use cases.

Or are you hoping something new will emerge that takes advantage of the MediaTek chipset, similar to what OpenWRT already does for routers etc. but with a slightly different, smartphone-focused approach?

[–] passepartout 4 points 5 days ago (2 children)

I was just trying to say that i hope that the creators of custom roms will still be able to do their work, which i don't take for granted. Google doesn't make their money with the phones themselves but with the data they get from the os thats running on them.

[–] Markaos@discuss.tchncs.de 4 points 5 days ago

The CPU is still Google's Tensor, and the modem on current Pixels is already a blackbox that custom ROMs interact with using binary blobs ripped from the official ROM. There isn't much that could get worse with this change.

[–] Auli@lemmy.ca 2 points 5 days ago

Oh bullshit. Google is charging as much as Apple. They are making money off of the phone sales.