this post was submitted on 26 Feb 2026
38 points (95.2% liked)
Explain Like I'm Five
20323 readers
14 users here now
Simplifying Complexity, One Answer at a Time!
Rules
- Be respectful and inclusive.
- No harassment, hate speech, or trolling.
- Engage in constructive discussions.
- Share relevant content.
- Follow guidelines and moderators' instructions.
- Use appropriate language and tone.
- Report violations.
- Foster a continuous learning environment.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The simplest solution right now is to use a pin code instead (this would just be for your phone unlock, you can still use bio for app locks). It's inconvenient at first but you'll get used to it. After that, you can look into changing the OS if you want more privacy, if you can unlock the bootloader. Lineage is a good choice, and it looks like e/os is available for some Samsung phones. There's already been a recommendation for GrapheneOS but that's only available for Google Pixels for now.
I'd recommend starting slow if you're willing to wait. Switch to a pin lock, try out FOSS alternatives with fdroid, start looking into alternatives for major accounts like Google, etc. It's a lot and easy to get overwhelmed if you go all in at once. I spent 4 years switching everything over to FOSS and privacy focused options. The best time to start was yesterday, the second best time is today.
Unlocking the bootloader makes your phone more vulnerable if you do not lock the bootloader after you install a different OS.
https://community.e.foundation/t/locking-the-bootloader-after-installation/68474
https://xdaforums.com/t/guide-to-lock-bootloader-while-using-rooted-grapheneos-magisk-root.4510295/
Also root does increase your attack surface, however it enables some convenience for security profiles so make sure you have a usecase for it.
https://ssd.eff.org/ is a good collection of privacy best practices.