Live data from Hacker News

Devices with GrapheneOS support should be available in 2027

grapheneos.social

271–280 of 444 posts

Re: Devices with GrapheneOS support should be available in 2027

#271

[flagged]

> Google, this small tech company (correct me if I'm wrong), is peddling source code via tarballs on google drive. What is the context for this? It's not clear from the linked social media post. The Android kernel source code is in git: https://android.googlesource.com/kernel/common/ Plus there's a lot of other Android source hosted on Google's git servers: https://android.googlesource.com/

It's mentioned in the same thread, just scroll up a few pages in the linked social post.

Re: Devices with GrapheneOS support should be available in 2027

#273
post #262

[flagged]

Google hasn't been able to properly do / fix Android gesture navigation for more than half a decade now. The amount that edge swipes in things like photo editing apps are detected as backswipes (sometimes destroying 10+ minutes of editing) is laughable. Technically this is because a lot of apps thumb their nose at the requirement to have safe areas around swipeable elements in their app, but as a user, that is not my…

The real fix would be to bring back physical control buttons and leave the touchscreen for the rest.

Also, I have 6GB of RAM in my phone - switching from a browser to youtube, or vice-versa, should not cause the other to clear and start back again from a freshly-loaded state.

350,000 a year and people can't even get basic things to operate properly. Google needs broken up and their engineers need to go back to the 90s and learn some real programming skill.

Re: Devices with GrapheneOS support should be available in 2027

#274

Earlier quoted context omitted.

My broker has a much more fully featured web app then it does on iOS or Android. You can do things in a browser that the phone apps will send you to a browser to do. BofA is just as good of a web app. Maybe people are just used to using their phones?

Can you deposit checks from the webapp? That is the feature most often missing in banking webapps. It isn't something I need often, fortunately.

The majority of the world don’t do this anymore.

Re: Devices with GrapheneOS support should be available in 2027

#275

I've never really understood why we chase Android-alikes on mobile platforms instead of trying to build on mainstream Linux. I know some folks in the nix community (nix-on-droid and other projects) have tried to bring us closer to this, but projects like Graphene seem to have a lot of traction.

Because without Android I can't run WhatsApp and my bank's app on my phone, which promptly reduces it to a paperweight. I wish it wasn't so, but reality refuses to cooperate, so let's just be happy that we've got GrapheneOS which is so good it has its own column in Cellebrite's support matrix.

[flagged]

Re: Devices with GrapheneOS support should be available in 2027

#276

[flagged]

And you have to fill out a Google Form to get that link in the first place. > I just want to get rid of forms. Like, I never want to fill out a form again. The opening line from this interview with Sameer Samat on the Google for Developers YouTube channel in June. https://www.youtube.com/watch?v=YvVsdZL2ogY

HE wants to get rid of forms, and make the rest of the world enjoy the burden of requesting access to open source code through a beloved form. Hope that's clear now.

Re: Devices with GrapheneOS support should be available in 2027

#277
post #262

[flagged]

Google hasn't been able to properly do / fix Android gesture navigation for more than half a decade now. The amount that edge swipes in things like photo editing apps are detected as backswipes (sometimes destroying 10+ minutes of editing) is laughable. Technically this is because a lot of apps thumb their nose at the requirement to have safe areas around swipeable elements in their app, but as a user, that is not my…

I think you are grossly minimizing the effects on your change on both users and developers. Neither are going to comply and then you have further fragmented the user base and removed a bunch of apps.

I use an Android tablet and I only backswipe at the upper left.

Re: Devices with GrapheneOS support should be available in 2027

#279

Specific devices: >At the time of writing, within ~12 months, in 2027, the 2027 Signature, Razr fold, and Razr flip will meet the hardware security requirements and should have official GrapheneOS support. Motorola is currently porting GrapheneOS to their devices. https://news.ycombinator.com/item?id=49038982

What I hope is that a compact and high-end device will have Graphene support.

We should be able to support the next generation of the Razr Ultra. It will take longer for the lower end devices to meet our requirements for updates and hardware-based security features.

Re: Devices with GrapheneOS support should be available in 2027

#280

Earlier quoted context omitted.

> AOSP is only more "secure" because, on some devices like Pixels, it exploits hardware features typically not found on general purpose computers. You don't think, say, isolating apps has anything to do with it?

Why are we acting like isolating software is impossible on Linux? It isnt even difficult, there are about a dozen different models to choose from.

It's not impossible, no, but it's not the default, and the different models tend to have various different issues.
Post reply on HN