[Magisk] topjohnwu:
I had planned to release the new update in a few days, but postponed because something caught up .

This is a public apology to [MENTION=631273]Chainfire[/MENTION]:

I apologize for redistributing your tools without your permission while you're in vacation

I apologize to release a workaround without notifying you in the first place

I apologize to use your hard work, and seems to benefit "the other project"

I had to emphasize my position again:

Magisk is NOT for Android Pay, NOT for Xposed, and especially NOT to compare which root method is better.

I regret myself to even considering fixing Android Pay, I can say this is the dumbest decision I've ever made on XDA.

It gives me more work to do, requires more time for me to investigate, not only upsets developers but also makes me look like a bad guy, and most importantly, I CANNOT EVEN USE ANDROID PAY IN MY COUNTRY!

Why should I bother?

I'm the first person to discover the way to make Xposed work systemless-ly: "post-fs-data" is the key. After repelling a lot of issues, I finally get a mostly-working build after 7 releases.

Not long later, [MENTION=631273]Chainfire[/MENTION] updated his SuperSU (2.76) with the change of the initializing root in post-fs-data. At that time I'm really happy that my ideas are adapted by the greatest mind in the Android Community. I consider this as a "trick" that people might just have missed, not an "original" work from myself, so even no credits are given to me, I didn't feel bad about it, and actually I'm a bit proud of myself.

As a rom dev myself, I've spend time to make custom roms to work with Android Pay. Soon as I found out that Google updated the detection, I continued to explore what I can play with the current situation as it seems that neither the original author of SuperSU nor Xposed care about this issue. During the same time, a developer asked me about the possibility of porting his mod to work systemless-ly. That's why I also started to create this whole Magisk project. I soon found out that both Xposed and root can benefit from the systemless interface I created.

I should've focus on the systemless interface instead of finding solutions of existing projects to work with Android Pay. Overall, all my effort spent on this topic is considered "unofficial", as they are other people's work, not mine. I bet [MENTION=4419114]rovo89[/MENTION] will still use SuperSU as a dependency, since [MENTION=631273]Chainfire[/MENTION] is a better developer than me in every aspect, even if it has issues in some rare conditions.

Maybe he would just take the new "trick" I used in Magisk (that runs reliably and works even on older Android version), and include them into the next SuperSU to fix current issues, and soon nobody will care about this project because what most people care is about Android Pay on root and Xposed.

Please don't get me wrong, I'm not here to say anything bad of [MENTION=631273]Chainfire[/MENTION]. In fact the opposite: I fully respect and grateful what he has done to the Android community. Without his hard work, there shall be no "systemless" concept (at least for me), and all my work is based on his great foresight. I learned a lot from his scripts and how the way systemless SU works, and that inspired me to start working on first the systemless Xposed, then this Magisk project.

Guess what's the "good" news here: I quit attempting to fix Android Pay on root and Xposed. I'll remove all root specific projects, root management functionality, as I fed up dealing with it.
[MENTION=631273]Chainfire[/MENTION] released a better solution for AP recently. His few days of work is worth the weeks of crap I've wasted and done even better; apparently he is a much better developer than me in this field

I apologize again for not aware that I crossed the line and messed up the situation for using other people's hard work in unwelcome purposes. Everything is 100% my fault.

Things I have learned while developing Magisk:

Samsung is the ****ing cancer of Android. If I wouldn't need to support them, I will not need to use supolicy to patch the sepolicy

Development is difficult. I am only a university student and cannot afford dozens and dozens of flagships like the greatest developers do, there are always things that is broken, especially cancerous devices.

Don't play with things that I'm not good at, as I can be roasted easily in anytime, exposing the huge gap between skills

Now let me throw away all the work I've wasted in my whole summer vacation. I should enjoy my break, and not fixing features that I cannot even enjoy.