[Galaxy S5 Mini Original Android Development] CurtisMJ:
OTG switching

Credit to tobigun for the original code (I actually attempted it at some point but failed miserably).

Execute the commands in a terminal:

Turn on OTG

su -c echo OTG > /sys/class/sec/switch/otg_cable_type

Turn off OTG

su -c echo USB > /sys/class/sec/switch/otg_cable_type

(Haven't touched Synapse in forever, cannot make sense of it anymore, so no Synapse switch soz)

Synapse Issues

I had some trouble with colour choosers crashing Synapse under specific conditions. If Synapse keeps crashing when picking colours for MDNIE, please try the custom build available in the downloads section of this project.

IF THE DEVICE IS CRASHING WHEN USING SYNAPSE, THEN YOU HAVE LIKELY SET UNSTABLE SETTINGS! SYNAPSE WILL NOT PREVENT THIS, SO PLEASE BE CAREFUL WHEN CHANGING SETTINGS!

There are two ways to recover:

- Use your recovery to delete Synapse's data folder

- Factory Reset your device (Only in extreme cases)

Using PIE netsched:(likely not working with Android at this point in time)

Run following in root terminal or as init.d script

tc qdisc replace dev wlan0 root pie
tc qdisc replace dev p2p0 root pie
tc qdisc replace dev rmnet0 root pie

ZZMoove and profiles:

The zzmoove governor is highly recommended. It can be set to various profiles to mimic the benefits of various other governors. It'll even ensure the device doesn't overheat!

The profile can be set by setting the "profile number" tunable in Synapse to one of the number values mentioned here. Setting it will change a bunch of other tunables. You'll need to restart Synapse after setting it and save the changes for future application.

Notes on DVFS

Samsung's DVFS feature in their TouchWiz ROMs seems to get a bit shouty when anything other than the "interactive" CPU governor is active. It could also be the cause of rare kernel panics relating to CPU frequency tables(frequency controller expects something from the governor, governor doesn't deliver, panic). Since it also seems to cause a couple other unrelated issues, I'd recommended simply disabling it altogether(the easiest way being via Xposed)

Double Tap 2 Wake

This feature allows you to wake the device by double tapping on the screen while it is off. NOTE:Deep sleep is near totally inhibited while this feature is active, this means extra battery may be consumed. On a tweaked ROM you'll get 2-3%/hr on full standby, on non tweaked you'll get about 4-5%/hr, please keep this in mind while using the feature! Android OS suspension should be unaffected. The feature disables itself when a Samsung branded flip cover is closed, including S-View covers(no double tapping on the window). The feature makes use of the light and proximity sensors in order to detect whether the device is in a dark enclosed place (eg. A pocket) and disables itself in these situations as well in order to prevent accidental wakes (though that may still happen...)

MDNIE Hijack Example

Profile based of iPhone 6+ screen:

R: FF 00 00 - G: 12 FC 12 - Bu: 00 00 FF - C: 12 FF FF

M: FF 00 FF - Y: FF FF 00 - W: FF FF FF - Bl: 00 00 00

Feel free to post any other nice looking profiles you find

Init.d in Lollipop

I did not add Init.d support when building the Lollipop variant's ramdisk. Instead, /su/su.d should be used to run boot scripts. The functionality is exactly the same as the old Init.d.

Haptic feedback on soft keys

In order to avoid conflict with ROM side solutions, haptic feedback is disabled by default. It can be enabled via the following command which can be run as a boot script (eg. in /su/su.d). Command must run as root.

echo 1 > /sys/class/misc/abov_touckey/vibrate

NOTE: Above "touchkey" was misspelled in code. It should be fixed in a future update. Sorry for any inconvenience

still not fixed lol

Extra Compatibility Notes:

[url]http://xdaforums.com/showpost.php?p=62226500&postcount=2[/URL]