PhotonCamera VS hardened_malloc

PhotonCamera: Android Camera that uses Enhanced image processing

Google Camera - most people suck it up and use GCam. The normal AOSP camera looks horrid. It sucks, but there's few other options available. Maybe try Photon if it annoys you?

If it's available (50mp RAW), you can look into Photon Camera. https://github.com/eszdman/PhotonCamera

It's refreshing that projects like https://grapheneos.org/ that let you take control of your device again at least to some degree.

Some days ago I decided to look at Zig a bit more in detail. So I skipped the usual marketing and I checked why it could be an alternative to C or Rust. Could it be?

It seems that allocators are a nice idea, however, it seems that they exist "somehow" already for C, so I wonder: why would you pick this language for your next low level program? They provide runtime checks, so you need thorough testing before you can spot use-after-free or so. It's very similar to the existing situation with c/c++ and the sanitizers, although they work a bit differently.

So the question I have for hardcore low level programmers: why don't they invest more on the memory allocators like hardened_malloc[0] instead of starting a new programming language? It would probably be less expensive in terms of time and would help fix existing software.

[0]: https://github.com/GrapheneOS/hardened_malloc

No matter how this turns out, I'm sure GrapheneOS will make a smart effort. https://grapheneos.org/

But long-term, Android is such a massive code base, and was designed more for surveillance and consumption, than for privacy and the user's interests.

I think getting mainline Linux on viable and sustainable on multiple hardware devices is warmer, fuzzier foundation. (Sort of a cross between Purism's work on the Librem 5, and PostmarketOS's work on trying to get mainline Linux viable on something else.)

>Give me a Pixel & all the Google stuff but without Google

https://grapheneos.org/

The number of combinations is irrelevant if you're not relying on randomness. Graphene sets the tag to a static value on deallocation[0] to prevent use-after-free, you don't even need to guess! The same is true for a lot of buffer overflows, as their allocator ensures two adjacent allocations have different tags, so unless the vuln allows you to skip ahead you'll always trigger a fault.

[0] https://github.com/GrapheneOS/hardened_malloc/blob/7481c8857...

I rather take my chances with googles hardware but good software (or even amazing with https://grapheneos.org) than guaranteed awful samsung software

Smartphone doesn't inherently mean telemetry and ads.

https://grapheneos.org/

https://f-droid.org/

Would grapheneos (https://grapheneos.org/) help with this? I am using a pixel 4a as a "house phone" so it is plugged in all the time but I wonder if I should upgrade.