username11, Yes, I understand what you want to say, but you are mistaken. The author has made binary binary not earlier than starting with version 3.0.7 and writes about
here -(
original ). By the way he himself confesses that he went wrong in version 3.0.1 -
here .
Next, I simply quote:
"The application was originally written zinx- (author) and I took him, and make it more useful. The application consists of two parts, Superuser.apk and SU binary"
And now I will try to explain what it means. Or rather, what is different from the Superuser SuperSU.
Binary is that other applications requesting when they require superuser. SU checks the database that defines Superuser.apk and if you have already submitted an application rule, then Superuser.apk're not asking permission. This is the binary system. I already wrote to you, that the example of this - there is Startup Manager program. So its earlier versions (Startup Manager) and earlier versions Superuser did not work in the binary system. When I tried to remove from startup element is encountered every time the request root, despite the fact that an application has been granted rights as others. (The others behaved properly) As a result, each such request, I log had every Startup Manager program element, and it was not convenient, as on past the list of allowed applications, 40-I in the log has the same number of logs from the Startup Manager program. And flipping such a list was extremely uncomfortable, that would get me to the desired program, as I leafed through 40 elements alone Startup Manager. Who previously used it, I will not lie.
Conventional programs usually are not looking for binary and directly interrogate the application itself, which is not true. And looking for exactly Superuser.apk. It is for this reason Chaynfayr was forced to write the name of your update is not SuperSU, and Superuser, which gave a lot of trouble to himself, since it is not his fault that the bend is interviewed APC - Superuser. Well, as a result, we sometimes see in the log inquiry com.noshufou.android.su.
Chaynfayr freed the root access in the binary system. That is, it has moved in this direction much earlier than ChainsDD and made binary binary. After that, the program ceased to question the right of the root, allowing authorized applications to run much faster and without any extra requests as a binary file. Moreover, he went the other way, than ChainsDD ... It is in your APK has added not only binary but also the very command to replace su file that requires busybox. ChainsDD also made it so that does not require, but did Chaynfayr chattr command detection function and if this team does not, then it throws the program itself, making it easier to update binaries. At what this team is not only a symbolic link, but as I understand it performs other functions as symlink can not weigh 10 kb for one busybox. That is why all normal developers choose SuperSU, since it does not bind the application to their needs. It allows programs to work fast, because there is no request, but there is just the root log. Next, I'm not going to argue that any debate. Both authors are well done, but at the moment I chose
SuperSUas well as other good developers.
And you
username11, special thanks! Because it is thanks to you, I started to get involved in this more closely. This happened after we last spoke with you, when we were about update.zip discussion. With people like you, truly interesting. Thank.
Post has been editedGrizzly-bear - 26.12.12, 08:45