So, somehow this happened, I don't know because I've been on a flashing/modding/nandroiding/restoring binge. Maybe it happened when I installed SuperSU from chainfire while still having SuperUser form ChainsDD still installed. However, I don't remember telling SuperSU to install it's binary ever...
I have SuperSU su binary v1.02 installed in my xbin folder, however, I use the SuperUser.apk from ChainsDD.
All my apps have root without asking for permission! I found a thread on xda where someone had this problem due to an outdated binary, and my binary is somewhat out of date (SuperSU v1.25 seems the most current), but it is only a few weeks old at most, I think. Maybe it is due to some incompatibility of the su binary with the su app automatically causing permission to be granted since it can't find its native app to ask for permission...
I haven't flashed back to ChainsDD su binary yet, so I won't know that fixes it for certain... but I'll update this thread when I do.
Hope someone finds this helpful or interesting.
I have SuperSU su binary v1.02 installed in my xbin folder, however, I use the SuperUser.apk from ChainsDD.
All my apps have root without asking for permission! I found a thread on xda where someone had this problem due to an outdated binary, and my binary is somewhat out of date (SuperSU v1.25 seems the most current), but it is only a few weeks old at most, I think. Maybe it is due to some incompatibility of the su binary with the su app automatically causing permission to be granted since it can't find its native app to ask for permission...
I haven't flashed back to ChainsDD su binary yet, so I won't know that fixes it for certain... but I'll update this thread when I do.
Hope someone finds this helpful or interesting.