Android

17681 readers

455 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.

💡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: [email protected]

For fresh communities, lemmy apps, and instance updates: [email protected]

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below

Rules

Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
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.
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.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

See thread

Chat and More

founded 1 year ago

MODERATORS

[email protected]

Device makers hiding the SoC they are using is a terrible recent trend (lemmy.sdf.org)

submitted 1 month ago by [email protected] to c/[email protected]

8 comments fedilink hide all child comments

Rant incoming:

This was spurred by having just read https://www.androidpolice.com/google-tv-streamer-questions-answered/ , particularly this bit:

When I asked directly, a Google representative told me they couldn't confirm which chipset powers the Google TV Streamer — essentially, Google declined to answer.

I've been noticing an increasing trend by device makers to not disclose the SoC their devices run on. I've been seeing it with e-readers, network routers, media streamers, etc.

It's incredibly frustrating to have devices actively exclude important information from their spec sheet and even dodge direct questions from tech news reporters. Reporters shouldn't have to theorize about what chip is in a released device. It's nuts.

If you're wondering why this infomation is important, it can be for several reasons. SoC vendor can have significant impact on the real world performance and security of a device. It also carries major implications for how open a device is as SoC vendors can have dramatically different open source support and firmware practices.

I've had to resort to inspecting the circuit board photos of FCC filings way too much lately to identify the processors being used in devices. And that's not a great workaroud in the first place as those photos are generally kept confidential by the FCC until months after the device releases (case in point the Google Streamer).

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

[–] [email protected] 8 points 1 month ago

They want your data. If you start trying to modify the device you become less lucrative