Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
Use GrapheneOS. It never has this bug to begin with, as the team found and fixed it while porting the OS to Android 14. https://grapheneos.social/@GrapheneOS/111309676504712576
GrapheneOS also has many other significant privacy and security improvements compared to the stock OS, it's definitely worth checking out.
They said that, but I couldn't find the fix in their github repository. Does anyone know the commit that fixes this bug? It would help shed light on the technical details of the issue.
GrapheneOS is spread across many many repos. They are listed on the website: https://grapheneos.org/source#grapheneos. It's impossible to put an entire operating system stack into one single repository.
I used GitHub's search across the entire Graphene org, but couldn't find any references to the issue. Doesn't mean its not there, I just couldn't find it. If the technical details of the issue were public, it would help people know whether or not their data is recoverable if they are already stuck with a "pixel is starting..." phone that doesn't boot.
I think I know why they don't publish details about bugs. It might have something to do with this https://grapheneos.social/@GrapheneOS/111234090393336322
Do banking apps work there?
There's a list of apps that work and those that don't work. Most banking apps should work though as the GrapheneOS passes Google SafetyNet checks.
NFC payments still seem to be an issue though as most banking apps rely on Google Pay for that?
I have no idea. For your privacy and your freedom it's best not to use these corporate surveillance systems anyway. Use cash whenever you can or if necessary a credit card with contactless payment that you keep in an RFID-blocking case when you don't use it. There might also be prepaid credit cards that support this, I don't know as these are only common in North America and I don't live there.
The repos issue tracker is slightly more up to date.
There are some banking apps and apps in general that may be problematic. For such cases, here are the possible work around solutions.
The website just links to the repo
Yeah yeah, GOS is cool and all but the only way to use it is to buy an expensive Pixel phone.
It's not that expensive, my Pixel 6a was 300 bucks.
I looked at Graphene OS and I am interested, but how can I find out if it will run on my old Samsung Galaxy S7?
how can I find out if it will run on my old Samsung Galaxy S7?
It won't. GrapheneOS only supports recent Pixel phones.
By looking at this page on their website. But I can also just tell you the answer: No, unfortunately it's not supported. There are quite a few reasons for this. The Galaxy S7 is old and abandoned by Samsung, meaning it doesn't receive kernel and firmware updates anymore. Even if it ran the newest release of Android, it would still lack important patches and potentially be insecure. There's another reason why the GrapheneOS team decided to only support modern Google Pixel phones: Hardware security. Google pixel phones are equipped with what is known as a 'secure element' with their Titan M chips. These are tamper-resistant and can thus safely be used to store cryptographic keys and other secrets that are e.g. used for full-device encryption.
Thank you for this information! 🙏
Any idea if Japanese Felica can still be used when running Graphene?
~~Could you briefly explain what that is?~~
Edit: I did some research and apparently it's a japanese mobile payment system that utilizes NFC. I found this on the GrapheneOS issue tracker, it seems to have been broken, but apparently it's fixed now. Unfortunately I can't try it out as I'm not from Japan. I also found this in the patch notes of a GrapheneOS version that was released in March of this year:
include PixelNfc app on all supported Pixels to enable support for FeliCa on Japanese Pixel models
So this is what it looks like when Google prioritizes a fix. Neat!
Google from the article:
Thanks for sticking with us. Our team is looking into this storage issue affecting some Pixel devices running Android 14 and we're working hard on a fix. We'll update this thread with more details soon.