owasp-mstg VS android-udev-rules

I found a more detailed explanation of it: https://github.com/julepka/owasp-mstg/blob/master/Document/0...

> Generally, you should provide compiled code with as little explanation as possible. Some metadata, such as debugging information, line numbers, and descriptive function or method names, make the binary or bytecode easier for the reverse engineer to understand, but these aren't needed in a release build and can therefore be safely omitted without impacting the app's functionality.

I'm not a big fan of the reasoning, as it's security through obscurity. Which is not the worst tradeoff, but these days it just makes public bug bounties (and other public auditing) end up being less of an interesting prospect for improving security.

i had not many issues getting it to run on pop latest but pushing it to devices i had to fix permissions using this script https://github.com/M0Rf30/android-udev-rules

Only use the binaries from here, and check it periodically. You may have to follow the directions on setting up the udev rules and permissions here.

See a bunch more rules here: https://github.com/M0Rf30/android-udev-rules/blob/master/51-android.rules

>sudo git clone https://github.com/M0Rf30/android-udev-rules.git

That will work but I need permission for android-studio. Anyway my problem is solved now after following these steps https://github.com/M0Rf30/android-udev-rules

I used adb to flash a Pixel Experience onto my Android phone. While installing, I followed these instructions, and now my microphone doesn’t work in audacity, zoom, etc. unless I run with sudo. How do I go about reverting these changes? (If it helps, I flashed the ROM successfully so I don’t think I will need adb anymore.)

I installed android-tools and then the Android udev rules from here: https://github.com/M0Rf30/android-udev-rules