Vendetta Crash on App Start-up [Exynos Chips]
ReLyf47 opened this issue · comments
Using a Samsung Galaxy A13 4G, everytime i open vendetta it crashes
Most possibly a bug with Exynos Chips being a dumbass and not liking how vendetta is structured or something like that, since discord crashed for 1 week on like lastest version
I have exact same device and am having same issue. it used to work idk what happened
i have samsung galaxy a03s and i have same issue
idk what happend
Pixel 8 on GrapheneOS having the same problem. Not happening if I enable exploit compatibility mode.
exploit compatibility mode
- Switch from hardened_malloc to Android's standard allocator (Scudo)
- Reduce address space size from 48 bit to Android's standard 39 bit
- Disable memory tagging, unless the app has opted-in to it (only on compatible devices)
- Allow native debugging (ptrace) access
makes sense
btw the name for this issue is still really confusing, i'd suggest something like "vendetta crashes on exynos", because:
boot = when your phone turns on
home menu = ???
exploit compatibility mode
- Switch from hardened_malloc to Android's standard allocator (Scudo)
- Reduce address space size from 48 bit to Android's standard 39 bit
- Disable memory tagging, unless the app has opted-in to it (only on compatible devices)
- Allow native debugging (ptrace) access
makes sense
Well yesterday this was not a problem so I don't know what has caused it
for me crashes have disappeared for now after removing the NoTrack plugin
Same issue for me on Samsung Z Flip 5
Crashes have disappeared for me after disabling the NoTrack plugin. I can enable both hardened malloc and memory tagging and it works fine.
It seems it is related
I can't even open the app, this is my first time using vendetta and its manager
Can any of you get a logcat output of just the Discord crash?
Here's the error and full log which is happening for me when enabling hardened malloc in GrapheneOS.
There's probably no way around that for GrapheneOS without disabling exploit protection. It's probably a known general incompatibility with LSPatch.
A log from someone on the affected Samsung devices would be appreciated since that is the original issue at hand.
I see. So how is it only having effect when the NoTrack plugin is enabled?
Can any of you get a logcat output of just the Discord crash?
how would i do that
az_recorder_20240128_173905.mp4
Here's footage of whats actually happening, its a hard crash, idk how to do the logcat or discord crash log