I'd love to see a hybrid phone with an embedded stock android for banking, pay and government apps and a regular LinageOS or Linux OS that runs on a separate partition/hw/vm.
Like "gluing" two phones together - just better ;)
It would be great to run an open OS but having to carry a separate phone for banking/paying is not really a viable option.
This is on point and it's sickening what Google is allowed to get away with. Even with the recent crackdowns on Google by various governments, they are steadily locking down Android, so even if you paid for your phone, whatever apps that you want to put on it will need their seal of approval.
The excuse of "security" or "it's for the children" is complete BS, because it's about "them" having unwanted and total control.
They were both budget brands with niche offerings. For most people, the source of the OS is immaterial. There's very little competitive advantage to selling a forked OS, and a rather large downside in terms of support costs.
I'm mostly happy with my GrapheneOS device - but it is absolutely not suitable for mass market.
> I'm mostly happy with my GrapheneOS device - but it is absolutely not suitable for mass market.
What makes you say that? I run GrapheneOS on a Pixel and had to go through the relative simple flashing process, but if GOS came preinstalled on a device anybody familiar with Android (or even iOS) would be able to use it. Compatibility with Android apps is great too.
"Find My Device" means the location of your device is constantly sent to and stored on someone else's computer (the "cloud"), and it is something that shouldn't exist unless that someone else's computer happens to be yours.
I am not ordering anything. I was merely explaining that "Find My Phone" is not a feature -- it is an anti-feature that enables surveillance by a third party. The lack of such an anti-feature should be viewed as an advantage of Graphene, rather than a disadvantage.
Most banking apps work on GrapheneOS. Around 10% ban using any alternate OS, but a small subset of those specifically permit GrapheneOS now in addition to Google certified devices with the stock OS.
It's nearly the same permission model as Android 16 beyond having Storage Scopes and Contact Scopes as easy to use alternatives with fine-grained control along with Sensors and Network toggles. It's otherwise the same.
If you're talking about the exploit protection features with toggles, that's not part of the permission model and the defaults don't break any apps without serious bugs. Apps with memory corruption bugs can be broken by the defaults, which only requires turning on the compatibility toggle for the app. People don't need to understand the finer grained settings.
The default 4x5 icon grid has the same icon sizes as the stock Pixel OS, which can't be adjusted there either.
The vast majority of issues people have with GrapheneOS are issues with Android and Android apps which are not specific to GrapheneOS.
What is the issue with the permission model. It's basically the AOSP permission model. The changes made by GrapheneOS is the user-facing toggle for the INTERNET permission, and the sensors permission.
If people do not want to interface with those features, they can simply skip them, and the permission model will be the exact same as it is on Android.
GrapheneOS is partnered with a major Android OEM and working towards some of their future devices meeting our requirements and providing official GrapheneOS support. It won't be the main operating system, but it will be an officially supported option. Their current devices don't meet our requirements, but they're working towards meeting those for future devices.
Where are you from? I live in Germany. I use ING and DKB as my banks. Both of the banks require a Play Integrity-checked app as their default 2FA.In the past I used Sparkasse and Commerzbank. They too required a PI-approved app.
As an alternative you can order a code generator but for DKB that requires a paid debit-card. ING disables the phone app if you use a code generator. You cannot have multiple 2FA.
EU Nations who are familiar with computers like Sweden and Estonia did.
Germany likes to think that they belong to cabinets and powered with internal combustion engines. Internet was a new land in 2013. So every user-friendly feature has to be shoved into Germany's throat by EU (especially banks and insurance). The usual reaction from German companies is to wait until the last moment and then hire a law / consultancy firm to implement required changes as badly as possible.
All my banking apps works fine under lineage. The only app that does not work is McDonald. I have not investigated very far, maybe it is possible to make it work.
Like "gluing" two phones together - just better ;)
It would be great to run an open OS but having to carry a separate phone for banking/paying is not really a viable option.