Edit at 2017-01-21: see the comments about better ways, especially comment 6.
However, it has not been updated for quite a while (January 2015 at the time of this writing) and since then SuperSU has changed its way of installing the
su binary to your device, by preferring not to install this on the
As some older apps hardcode the complete path of this binary in their checks, and Secure Settings is one of these, it thinks it can not get root access.
On my quest of a fix for this problem, I found this post on XDA where a comment on Reddit was referenced, stating the following fix, running the commands from a command line (terminal) on your machine, having
adb shell su mount -o remount,rw /system touch /sbin/su /system/bin/su /system/xbin/su mount -o remount,ro /system exit reboot
This creates some empty files in locations that older (incorrect) apps check for the
su binary, so Secure Settings (and likely other applications) are made to believe they can get root (which they actually can, as you can not make those files without being root through
You can also do this on your device by just omitting the first line and starting with
su in a Terminal app (or for example JuiceSSH in a local session).
I hope this helps other people looking for a solution too.