You must log in or register to comment.
Here’s the scope of it
A National Institute of Standards and Technology (NIST) advisory on the bug describes it as “an issue [that] was discovered in the m2m scaler driver in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850, and W920.” A use-after-free bug in the mobile processor ultimately leads to privilege escalation, the agency added.
Its a good thing people already knew Exynos sucks. Made me steer well clear of those chips.
Looks like they’re mainly used in Galaxy S phones and tables…
The bootloader is locked for your own good, boy!
Urrg! I have one of those CPUs. (Exynos 9820) I don’t want to upgrade with an expensive new phone. I get no longer security updates.
Ugh, I’m in the same boat. s10e, I have zero complaint other than the EOL security update. Bought it 2nd hand two years ago.
There’s nothing in the market with similar price with the spec and size of my current phone.
Lineage might extend that life a little bit
I’d try it, but this is essentially an emergency signalling device and not something I’d like to render inoperable.
Certainly understandable. Wouldnt risk it on my current main device either. Only on a future new or old backup phone
Pixel and grapheneos…
About as good as normie can get currently
Buy used to dent google direct profit and it is cheaper
Pixel phones can have hardware quality issues. Samsung arguably makes the best hardware. Their cameras and screens have always been way ahead of every other phone.
I have heard about that. Samsung prolly does have better quality but their US models got locked bootloaders and theu dont really get any support from calyx and graphene, so i cant recommend them.
As idiotic as it is, googles phone is the besy choice if you are privacy/security first type
My banking app sadly doesn’t work on a rooted phone.
Grapheneos isn’t rooted by default, and they recommend re-locking the bootloader after installing it, so most banking apps work.
Custom roms dont require rooting. It is a bad security practice and not necessary.
GrapheneOS uses sandboxed google play store and most banking apps work fine with exception like CashApp and other bankspy type shops.
Is there a confirmed list of apps that will not function in Graphene? I searched around, and all I get is “some bank apps dont work” but your the first I see mention cashapp specifically. I could probably work around Cashapp, but I’d at least need zelle/venmo etc. Due to my credit union app more than likely not being compatible.
I really want to move to the platform, but I don’t currently have a Pixel, so I can’t just try it out. Before going out, buying a Pixel, loading Graphene and finding out I can’t use my banking app or the very least the other money apps I’d just like a heads up.
In the end if I need a backup phone then so be it.
I think this might apply to your request: https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos
Linked by this article: https://grapheneos.org/usage#banking-appsAlmost. It doesn’t list cashapp, venmo, zelle. I use a local credit union, so my bank app would likely never be listed.
Maybe I just keep an eye out for a cheap Pixel and just try it.
I think there lists out there but i never seen them, maybe somebody can post.
My friend tried the switch and cashapp was deal breaker for him so thats how i know.
It is trial and error and my understanding, some banks are actively working to brick custom roms
Cash app used to work according to reddit posts i saw.
I am abit more hardcore about it. If bank fucks around, i will fucking move. I know we cant exepct most people to do this.
But with privacy/security first mentality it is doable.
I am abit more hardcore about it. If bank fucks around, i will fucking move.
Thank you. That’s someone willing to make a change.
