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:
Allow me to go out on a limb and say that I don't like this trade off. This was one of the fundamental innovations of Android to conserve memory and accelerate application launch times. 200ms is a long time.
I respect this project and I've installed it on devices for friends, but even when I used it I did not take advantage of this feature.
It adds somewhere in the ballpark of 200ms to app spawning time on the flagship devices and is only very noticeable on lower-end devices with a weaker CPU and slower storage.
"Very noticeable on lower-end" devices is definitely true. Default GrapheneOS has really slow app start times on my Pixel 4a. It even made me switch to CalyxOS for a while, befiore I found out I could disable this security feature.
Pixel 4a? To be fair, you're not the current target audience of GrapheneOS since your device is "end-of-life, no longer receive firmware or driver security updates and receive extended support from GrapheneOS via a legacy branch based on Android 13 with only the Android Open Source Project security backports, certain other security patches and other minimal changes to keep them working." And it's been that way for 4ish months.
Yup, very sad. Awesome (but true, too weak for GrapheneOS) phone. I am still trying to find a damn usb-c DAC that works well and with analog headphones... as if that wasnt something EVERY phone supported before Google just removed it.
Also the selfie camera is worse!https://tux.social/@Rhababerbarbar/111755782091599768
Apple's 9 dollar dongle works pretty well for me. It's actually really good for the price.
Where do you get that?
I guess it makes sense to enable it by default (since it's meant to be the private OS it should be ready out of the box), but it might help to advertise the difference more is what I'm getting?
Agreed. It hits both startup time and memory usage. I'm not sure how significant the security gains are. Perhaps it makes sense in the scenario where you want to do everything you can to decrease the chance of exploits. However given how many other layers of security there are on Android, this might not be a worthy tradeoff for the common case.
The 200ms difference is virtually unoticeable on a Pixel 6 Pro.