Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GrapheneOS – Break Free from Google and Apple

blog.tomaszdunia.pl

Post reply on HN
Print view View original

541–550 of 967 posts

Re: GrapheneOS – Break Free from Google and Apple

#541

Post by goda90 »

dlcarrier wrote: post #527
goda90 wrote: post #395

Earlier quoted context omitted.

What would sandboxing an app like Google Maps look like? There are definitely situations where a sub-par map app would be detrimental. Obviously it's going to send data to Google, but do I have to sign into an account or will it have some other way of identifying my phone if I used a one-off account just for it?

It doesn't need to be logged on to a Google account, and it supports locally storing map data and generating routes, so you could turn on network access, download local maps, block network access, then use it for navigation without it calling home.

There's also value in live traffic and road closure information.

Re: GrapheneOS – Break Free from Google and Apple

#542

Post by korhojoa »

InitialLastName wrote: post #385
empyrrhicist wrote: post #374

Earlier quoted context omitted.

Your password must be between 8 and 12 characters, and must have lowercase, uppercase, numbers, and punctuation. Pick up the can!

My favorite is when it must have punctuation, but certain punctuation is silently banned, so I have to keep refreshing my password generator until it gives me an acceptable combination.

I came across a "special character" requirement while creating an account. The client validation was not the same as the server validation. The client proceeded as if my account was created, but it never was. The client functioned without an account until it was closed. I asked the creator what their app's problem was, why did I need to keep resetting my password, then be told that I don't have an account, and have to create it anew.

They would not believe I was creating an account and using the device, because their own logging was so terrible.

I had to send them a screen recording from me using this abomination, and only then was I told "you're using the wrong special characters". They helpfully gave me some examples of allowed special characters, which then would pass the server validation.

I wish they would have gotten rid of the account requirement, as the device and client software seemed to work fine without them.

Re: GrapheneOS – Break Free from Google and Apple

#543

Post by aniviacat »

mnmatin wrote: post #86

Wallet Apps and Tap-to-pay do not work. Even got banned from PayPal. Android needs an architectural change from the ground up.

I use the PayPal app with Tap-to-pay on GrapheneOS and I haven't been banned.

But of course that's entirely up to how their algorithm happens to feel about you.

Re: GrapheneOS – Break Free from Google and Apple

#544

Post by gwillem »

drnick1 wrote: post #537
rahkiin wrote: post #526

Earlier quoted context omitted.

That’s why for most transactions I do with a credit card in my country, you need an extra validation with the mobile app. It is mostly American websites that do not enable this functionality.

Yes, because we don't want these stupid locked down apps. Credit cards give buyers many protections, it's very easy to dispute an illegitimate transaction.

However, you pay 2.7% for that convenience

Re: GrapheneOS – Break Free from Google and Apple

#545

Post by seba_dos1 »

palata wrote: post #218
hengistbury wrote: post #162

Earlier quoted context omitted.

What is the difference here between "Android" and "AOSP" (Android Open Source Project)?

AOSP is Android without the Google proprietary stuff (and without the manufacturer proprietary stuff, e.g. Samsung's). If you install bare AOSP, it will look like the Android on a Pixel phone, but the biggest difference you will see is that it won't have the Play Services or some Google apps. If you want to be a certified Android system (like all Android manufacturers do), you have to port AOSP to your hardware, inst…

You're confused.

To quote Google's documentation:

> To build an Android-compatible mobile device, follow this three-step process: > 1. Using AOSP, implement Android on your device. > 2. Ensure your device complies with the Android Compatibility Definition Document. The CDD enumerates the software and hardware requirements for an Android-compatible device. > 3. Pass the Compatibility Test Suite (CTS). Use the CTS as an ongoing aid to evaluate compatibility during the development process.

AOSP is how Android is being distributed. Being "Android-compatible" (implementing Android and passing CTS) does not automatically give you access to Google Play, it just unlocks the possibility of licensing it:

> After achieving compatibility, your device is considered Android compatible and you can consider Licensing Google Mobile Services (GMS) and prepare to use the Android trademark.

Google restricts the use of "Android" trademark on hardware, packaging or marketing materials of devices and requires prior approval of any use, but that doesn't make AOSP "not Android". If you insist otherwise, you're going against common use of these terms.

In fact, not just "common use", but even Google's use - AOSP's homepage has this as its headline:

> Android is an open source software stack created for a wide array of devices with different form factors.

It also tells you how to "get the Android source" or "build the Android OS".

Sure, many apps that are being called "Android apps" are in fact apps for the Google Play platform (perhaps that's where you got your confusion from), but that doesn't make Android-based systems non-Android.

Re: GrapheneOS – Break Free from Google and Apple

#546

Post by askonomm »

GoblinSlayer wrote: post #525
notpushkin wrote: post #398

Earlier quoted context omitted.

> Can the PIN change? You can change it in the app, yes. > How to issue new key if needed? I think you’ll have to reissue your ID. There’s also digi-ID (similar e-signature certificate on a card, but without any ID features), Mobiil-ID (e-signature on a SIM-card, no idea how it works), Smart-ID (in app, tied to secure storage in Android/iOS, cross-signed by the server which is supposed to check the device somehow) an…

How much the certificate costs and lasts?

It costs as much as your ID card costs by the government, and lasts as long as well. They are one and the same. Applying for a new ID card / national ID document in Estonia costs 35€ and the document is valid for 5 years. If you forget your PIN code, you can reset it with your PUK codes, but if you also lose your PUK codes you need to apply for a new ID card. The process for getting a new ID card from the moment you applied for it takes no more than 30 days. You can also have it fast tracked for 250€ and get it in 2 days.

But, like the parent said, you have many other options other than the physical ID-card as well. Most people these days use Mobiil-ID or SmartID, which works on your phone and even smart watch. SmartID is completely free and Mobiil-ID is tied to your phones carrier, so the cost varies, but it's a one-time set-up fee of around 5€. Mobiil-ID certificate also lasts 5 years.

Re: GrapheneOS – Break Free from Google and Apple

#547

Post by Gud »

aniviacat wrote: post #451
Gud wrote: post #353

Is there a great phone with high end specs this runs on? Currently have an iPhone 16 pro, and probably my next phone will be something like this. I need to be able to share photos easily with my wife, typically I’ve been using airdrop.

You can use GrapheneOS with the Google Pixel lineup, or in particular the Pixel 10 Pro XL [1]. GrapheneOS supports Android's Quick Share, which (on the Pixel 10 family) is compatible with AirDrop [2]. [1] https://grapheneos.org/faq#supported-devices [2] https://blog.google/products-and-platforms/platforms/android...

What if I don't want to give money to Google at all?

Re: GrapheneOS – Break Free from Google and Apple

#548

Post by fsflover »

no-reply wrote: post #531
Aachen wrote: post #493

Earlier quoted context omitted.

> The whole reason why GrapheneOS is superior to its alternative is because they do all that. What is "its alternative"? > I also wish they could support non-Google phones, but that's a problem coming from the manufacturers, not from GrapheneOS. The manufacturers aren't blocking the installing of GrapheneOS...

GOS has minimum hardware requirements and most of the available smartphones don't meet them

This is a contradiction. There is nothing "minimal" about a requirement that excludes every device but one. Also some people (me) value independence from Google more than the highest degree of security (which relies on Google hardware).

Re: GrapheneOS – Break Free from Google and Apple

#549

Post by aniviacat »

Gud wrote: post #547
aniviacat wrote: post #451

Earlier quoted context omitted.

You can use GrapheneOS with the Google Pixel lineup, or in particular the Pixel 10 Pro XL [1]. GrapheneOS supports Android's Quick Share, which (on the Pixel 10 family) is compatible with AirDrop [2]. [1] https://grapheneos.org/faq#supported-devices [2] https://blog.google/products-and-platforms/platforms/android...

What if I don't want to give money to Google at all?

Then GrapheneOS is currently not an option, however they are working with another OEM to have non-Google phones available with GrapheneOS by next year [1].

[1] https://grapheneos.social/@GrapheneOS/115987006592879172

Re: GrapheneOS – Break Free from Google and Apple

#550

Post by tonyedgecombe »

abustamam wrote: post #450
empyrrhicist wrote: post #440

Earlier quoted context omitted.

One time I had to reset my password with the power company - they had such a system, and the lady had to read me something like: Uh4zB4DP55WD! Apparently I was a bit salty with the system when I set it. The fact that she shouldn't have even been able to look up the password in the first place due to hashing was lost on her.

That's pretty funny on a few levels, not in the least that they required a "secure" password like that but stored them in plain text.

My bank’s password field is case insensitive. Of course they could have lowercased it before hashing but I doubt it.
Post reply on HN