- Edited
DeletedUser69 Can somebody please kindly point me at recent source code for OSMAnd~ since it is supposed to be open source?
Is there a concern about what's on GitHub?
DeletedUser69 Can somebody please kindly point me at recent source code for OSMAnd~ since it is supposed to be open source?
Is there a concern about what's on GitHub?
Ghen It's not at all safe and you should not use an end-of-life device. It's highly insecure and filled with holes. It also has far fewer defenses against exploits than more recent devices, particularly with GrapheneOS. We'll be ending support for the legacy extended support devices soon especially because people keep wrongly believing it keeps them secure. Posts trying to convince people it's fine will result in an earlier end to legacy extended support.
Move to one of the supported devices and stop believing people telling you that not having important security patches is fine. You don't have anything close to current generation exploit protections to make up for it either.
Originalcahummer it seems that you don't value yourself enough to try GrapheneOS on officially recommended device. I did and succesfully and after two years I invested into future proofing my experience by purchasing currently second most expensive Pixel. So far I don't regret my decision.
While it might not fit your use case, here's a setup I enjoy using: GLiNet router (Mudi V2 in my case) with Mullvad set up right on the router.
Ghen so it is really serious or... Google is financing you ;-)
We're keeping it real over here, it's your choice at the end of the day but we won't downplay the risks associated with an out-of-date device.
Ghen once GrapheneOS stops supporting Pixel 5 as it did with previous Pixels, will we get annoying notifications or we can remain in grapheneOS?
It will be a bit like staying in a park after closing, you're not supposed to be there. Sandboxed google play for example relies on consistent updates, if the flow dries out, functionality will break down sooner or later.