[SuperSU] DodoGTA:
[MENTION=631273]Chainfire[/MENTION] So, I tried SuperSU v2.82 SR3 in LineageOS 11 (based on Android 4.4.4) on my Samsung Galaxy Trend Plus and here's what I got:

I used your AROMA-based SuperSU config ZIP to generate this config that you see here:

SYSTEMLESS=true

BINDSBIN=true

FRP=false

BINDSYSTEMXBIN=false

PERMISSIVE=true

Firstly, I tried to directly flash the SuperSU ZIP, but I couldn't get systemless mode to work, even after using that config (So, I did a mod to the update-binary of that ZIP (which is shown in the first attached screenshot) and install went well without any issues, but after my device has booted, I noticed some issues):

The SuperSU app wasn't being installed, so I installed it manually from SuperSU v2.82 SR3 ZIP and noticed some other issues:

- All root requests would be kind of stuck (For example, when I opened a terminal emulator and typed "su", the root prompt would appear, but after clicking "Grant", the toast message appeared saying that SuperSU granted root permission to that app from time to time, but thall

erminal emulator never dropped me into the root shell (The same thing happened with other apps, like FX by NextApp (nextapp.fx), so this isn't the app's fault)

- SuperSU app always said that "SU binary needs to be updated" (This is obviously fake in this case)

- SuperSU app never logged root grants (only denials for some reason)

- SuperSU would allow me to install it as system app in its settings, despite that option being grayed out if systemless root is detected

And, here are some notes that I found while I was messing around:

- If I uninstalled the SuperSU app, then root worked fine (But if I reinstalled it and set it up, existing root sessions worked fine, but new ones didn't as described above)

- I also noticed that the launch_daemonsu.sh script placed the SuperSU app without any issues, but it placed that app wrongly

Here's an another bug that I found:

- su.d scripts would not execute at all (I don't know why)

And, here are the reasons for most of the bugs that I mentioned:

- SuperSU not installed: Different user app structure (the raw .apk files directly go in /data/app folder)

- SuperSU app's weird things: That app's code isn't able to work well with a weird setup like this

- Root requests being kind of stuck: Sort of unknown, but it might be SuperSU app-related

/sbin/.launch_daemonsu.log contents are shown in the second attached screenshot

"ps | grep su" output is shown in the third attached screenshot

Note: SuperSU needs a lot of other adjustments to work well in systemless mode on KitKat

Note 2: I did have suhide-lite v1.08 installed with some adjustments (which I will cover in the suhide-lite thread later on), but I don't think it affected this test

Note 3: Is it OK if "getprop init.svc.daemonsu" returns "stopped" (but root works fine and daemonsu processes are running, according to "ps | grep su" output)?

So, this is the end of this long post, but before you go, I wanted to give you some questions:

- Is there any more info that I can provide that would be helpful?

- What should I have done differently during this procedure?

- And, would you fix these issues under any circumstances?