Episode 107 - How apps can secretly collect your information even if you deny their permissions
Added 2023-03-31 11:07:42 +0000 UTCGrapheneOS is tracking this issue here: https://github.com/GrapheneOS/os-issue-tracker/issues/156
Comments
Unfortunately, Google doesnt trust GrapheneOS because of safety net, but if you do decide to keep using Graphene heres a list of alternative nfc banking apps: https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/ Or maybe try a different phone, use a smartwatch with NFC capabilities, or use nfc chip/card to pay. Could put the nfc chip on the back of the phone A similar issue here: https://lr.odyssey346.dev/r/GrapheneOS/comments/100a5pk/grapheneos_nfc_payment_options_google_pay_etc/j2gmgfr/?context=3
hope
2023-04-16 00:10:54 +0000 UTCI mean this: https://discuss.grapheneos.org/d/475-wallet-google-pay. It's regarding the Wallet and NFC payments in general (Pay, not Play :). There are two things that I expect from this kind of functionality: 1. Virtual cards you can physically pay with. Implemented via NFC and a virtual card proxy service. This helps you avoid disclosing payment details to peers like shops at a cost of disclosing your receipts to the service. Lowers risks of loosing physical access to the card (one phone is harder to loose; if lost you still have your cards + can restore access to your cards with another phone using remote banking). 2. Integration with payment services. If you're trying to pay for something remotely, either from an app or on internet site, you MAY be presented with an option to pay via Google Pay or Apple Pay. This cuts a lot of effort required to fill in your card details and have the same benefits/risks as #1 above. #1 Could be replaced with something like SwatchPay! although at additional cost, but #2 can not, and requires filling in the details even if you chose to use a virtual card service. One other option would be to still use a normie phone for specific needs like travelling.
wurdfcon
2023-04-15 09:48:32 +0000 UTCWhat do you mean? You can install the entire Google Play Services suite and run everything sandboxed. Did you install Google Play on your GrapheneOS phone? What didn't work properly? You might want to reach out to GrapheneOS forums for help, if you have troubles but for my usage, I've found no major issues.
The Hated One
2023-04-14 12:21:31 +0000 UTCA major blocker from running GrapheneOS device as my daily driver is the lack of Google Pay support. Basically if you're travelling and need to install and use an app for transporting, ordering food, tickets etc. adding physical card / paying in cash could put you in an unnecessary stress. Any recommendations with that?
wurdfcon
2023-04-09 21:28:14 +0000 UTCNot sure if side of burritos video is up to date. But he makes some mistakes in the video. First, you can get notifications from different profiles. Second, it seems like work profiles (which is what shelter creates) aren’t as privacy focused and does not prevent IPC from happenings. See the link below: “By design, work profiles are also made to allow communication between apps on the user profile and the nested work profile.” https://discuss.grapheneos.org/d/115-work-profile-vs-user-profile/4
No Name
2023-04-04 15:44:22 +0000 UTCJust curious what people think of using Shelter, instead of/in addition to separate profiles, please. Side of Burritos brought Shelter on grapheneOS to my attention.
2023-04-02 20:57:53 +0000 UTCInteresting discussion here about it https://discuss.grapheneos.org/d/1549-more-questions-about-ipc
No Name
2023-03-31 16:03:24 +0000 UTCThis is very helpful. And I’ve started fully utilizing profiles. My main profile has nothing other than stock grapheneOS apps. No google play store or services because I have a SIM card installed and not esim. I will then isolate apps from “untrusted” developers in their own profile. I’m thinking as an example isolating gcam to its own profile and only launch it when I want to take a picture. When I’m done, I will then end the session.
No Name
2023-03-31 15:56:26 +0000 UTC