Technology

74731 readers

2791 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related news or articles.
Be excellent to each other!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
Check for duplicates before posting, duplicates may be removed
Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago

MODERATORS

L3s@lemmy.world

enu@lemmy.world

technopagan@lemmy.world

L4s@lemmy.world

L3s@hackingne.ws

L4s@hackingne.ws

1510

Google: 'Your $1000 phone needs our permission to install apps now'". Android users are screwed - Louis Rossmann (youtube.com)

submitted 2 days ago by rustyredox@lemmy.world to c/technology@lemmy.world

503 comments fedilink hide all child comments

https://consumerrights.wiki/index.php?title=Android_Developer_Verification

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

[–] Saik0Shinigami@lemmy.saik0.com 144 points 2 days ago (2 children)

Well the assumption is that the Graphene team will be able to maintain non-store app installs. There's recent news that Google is no longer providing update packages the way they used to which will make it harder on Graphene to update stuff too.

We can't assume that Google's next update will not functionally block the ability for GrapheneOS as well.

[–] rhymepurple@lemmy.ml 27 points 2 days ago

I believe Google plans to use Google Play Services to block side loaded apps. By default, GrapheneOS does not come with Google Play Services installed. I am not sure how things would work if the sandboxes version of Google Play Services that GrapheneOS provides is installed.

The issue about maintaining/updating GrapheneOS is a separate issue from side loading apps. That was due to Google shifting the development of Android to a closed source model and only open sourcing the final code. This limits the Grapheme team's ability to anticipate changes and make any required adjustments until after the release of Android.

[–] atrielienz@lemmy.world 22 points 2 days ago (1 children)

The Graphene OS team have said that they are going to continue, have received the pixel 10 phones they ordered and have put out a statement regarding this issue.

[–] Saik0Shinigami@lemmy.saik0.com 61 points 2 days ago* (last edited 2 days ago)

No they didn't..

https://discuss.grapheneos.org/d/25099-pixel-10-still-too-early-to-ask-us-when-it-will-be-supported

Our Pixel 10 support will likely only be possible to complete after we finish porting to Android 16 QPR1 which is being released in September.

They don't know IF they can even support it until they figure out the new releases that are jacking up their dev cycle.

It will be significantly more work than usual to support the new Pixel 10 phones since Android 16 removed the Pixel device trees from the Android Open Source Project. However, that was already only part of what we need for device support and we worked around it by expanding our automated tooling.

This is exactly the issue I'm referencing. Google can completely sabotage this route. We don't know yet.

Edit: I should clarify that they did say they're trying to continue, but should they not be able to crack the device tree issues they will be stuck. Nothing they released said that they've figured this issue out yet.