Q: CPU Stats has weird data, what’s wrong?
A: Check CPU Spy, if we have nearly the same results then it’s your ROM/kernel that’s borked. A user confirmed a reboot and dalvik-cache clearance fixed it for him.
Q: Does the app run in background and does it drain battery?
A: The app only runs momentary in the background at boot to apply Set-On-Boot if this feature is enabled. On Nexus 4, to keep color settings, it also runs momentary in background when screen is turned on. Because the time it takes to run in these circumstances is extremely short, it won’t affect your battery.
Q: TM asks me to update my donate key but I’m having the latest version?
A: Donate check was blocked by app like Greenify Deep Hibernation feature. This seems to be a bug as TM is not listed in the Greenified list. Please update to the latest version of the app and the donate key to work around the issue.
Q: The app can’t get root even though I have allowed it?
A: If you use SuperSU, please remove the app from allowed list, kill the app then run it again. You can also switch to ClockworkMod’s Superuser which seems not to have this bug.
Q: CPU/GPU frequency doesn’t stick?
A: If your frequency settings don’t stick, it’s because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues. Unfortunately, it can’t be fixed from app side
Q: Settings don’t stick?
A: You might have scripts, other apps, or ROM settings override Trickster MOD settings. In this case Set on boot delay might help if it’s for settings at boot otherwise you need to track down and disable the app/ROM settings
Set On Boot
Q: I use MIUI and Set On Boot doesn’t work?
A: Check this page.
Q: I also use other apps to config my ROM, how can I make Trickster MOD override their settings?
A: You can try Set On Boot Delay.
Q: Why is set on boot doesn’t stick even though I have set it?
A: First make sure you have set on boot and set on boot notification enabled. If after a reboot you see this notification
If settings do not stick then the 2 most likely problems are
A1: If you’re using chainsdd’s superuser switch to koush’s superuser or SuperSU.
A2: Make sure you are not using another tweaking app or your ROM has setting that overrides our boot configuration. In that case, “Set-On-Boot delay” feature might help.
Otherwise or if you still have problem, see below
A3: If your frequency settings don’t stick, it’s because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel service that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues. Unfortunately, it can’t be fixed from app side.
A4: DON’T use a reboot app, they effectively force reboot your phone like a system crashes. If you really have to use it, then do it after the apply grace period or disable grace period by setting it to 0.
A5: You might have scripts, other apps, or ROM settings override Trickster MOD settings. In this case Set on boot delay might help.
A6: Don’t force close the app (e.g. in Android Settings). It puts the app in a state that it can’t start at boot until user starts the app normally again.
A7: Don’t use app like Greenifier and/or xposed module like bootmanager to greenify/block Trickster MOD. Doing so will prevent it to run at boot to apply Set-On-Boot.
A8: The Android BOOT_COMPLETED broadcast might be borked because of theme, mods, or after a few dirty flash. In this case reinstall ROM with a data wipe is needed. This solution is confirmed by our users and as this issue is because of deteriorating ROM with ORD, nothing we can do about it on our side.
A9: If it still doesn’t work, please do in in app bug report using the option in the app menu right after Set on boot was run. You can enable Set on boot notification to know that.
Q: How to reset to default settings?
A: Disable the “Set-On-Boot” and restart the phone or use this recovery zip.
Here is the list of Trickster MOD’s used permissions:
|android.permission.ACCESS_NETWORK_STATE||ADBWireless and donate check when network becomes available|
|android.permission.INTERNET||APK integrity check|
|android.permission.VIBRATE||Notification will crash on some devices without this permission|
|android.permission.WAKE_LOCK||ADB-Over-Wifi Screen Lock|
|android.permission.WRITE_EXTERNAL_STORAGE||Backup/Restore Kernel feature & writing log when doing bug-report|
|com.android.vending.BILLING||Donate using Google Play In-App Purchase|
Q: Why is my device unsupported even though it is listed in compatible devices?
A1: Because the ROM you’re using changed the ro.product.device string in build.prop. Bring it up to your ROM developer.
A2: Manually revert it ro.product.device string in build.prop to original (tuna, grouper, vivo, endeavoru,… )
Boot loops or Recovery Reset
Apply Grace Period might might help users avoid bootloop. In any case, if you mess up and can’t boot, say aggressive OC/UV, use this recovery zip. You don’t need to flash this script every time you flash the new kernel though. Trickster MOD has mechanism to detect kernel changed, it will only apply the safe values for you.