Please wait...
Lua Player Plus (LPP) started as a homebrew application for the PlayStation Portable (PSP). It eventually evolved into an Android development environment where users could write and execute Lua code. LPP-SA is the System Actions fork of that project.
While the standalone LPP-SA app is robust, its true potential is unlocked when plugged into Tasker. By installing the LPP-SA plugin and referencing it within a Tasker action, you can trigger system-level Lua scripts directly from your Tasker profiles.
Never declare "secure": false for actions that modify system settings or inject input. A malicious app could repackage your plugin and trigger those actions via standard Locale API. If you must expose them, add a runtime user confirmation dialog.
The golden era of LPP-SA was around 2016-2018. Since then, Google has progressively locked down Android (Scoped Storage, restricted accessibility APIs). Many developers have migrated to alternatives like AutoInput (by joaomgcd) or Termux (for shell scripting).
However, tasker.lppsa persists for three reasons:
If you are on Android 12 or higher, expect some friction. Newer "Protected App" layers may block LPP-SA’s overlay capabilities.
Tasker’s built-in click simulation is limited. LPP-SA allows coordinate-based tapping with adjustable delays and swipe gestures. Imagine an automation where you receive a specific SMS, and Tasker triggers a Lua script that opens your banking app and automates a bill payment by "virtually" tapping the screen in the correct sequence.
As of Tasker 6.3 (Android 14+), the LPP framework is being extended with:
The .lppsa file will evolve to include ui_schema and data_policy sections, formalizing how plugins declare their data retention and network usage.
The power of tasker.lppsa comes with significant responsibility. You are effectively giving a scripting language the keys to your operating system.
By using LPP’s secure flag and INPUT_INJECT capability, you can simulate complex gestures (pinch, rotate, three-finger swipe) without the 500ms delay imposed by Android’s AccessibilityService.dispatchGesture(). This enables macro speeds approaching native touch input (~16ms).
Developing for tasker.lppsa requires a shift in mindset from standard Android development. You are no longer an isolated app; you are a co-processor to Tasker’s automation engine.
Lua Player Plus (LPP) started as a homebrew application for the PlayStation Portable (PSP). It eventually evolved into an Android development environment where users could write and execute Lua code. LPP-SA is the System Actions fork of that project.
While the standalone LPP-SA app is robust, its true potential is unlocked when plugged into Tasker. By installing the LPP-SA plugin and referencing it within a Tasker action, you can trigger system-level Lua scripts directly from your Tasker profiles.
Never declare "secure": false for actions that modify system settings or inject input. A malicious app could repackage your plugin and trigger those actions via standard Locale API. If you must expose them, add a runtime user confirmation dialog.
The golden era of LPP-SA was around 2016-2018. Since then, Google has progressively locked down Android (Scoped Storage, restricted accessibility APIs). Many developers have migrated to alternatives like AutoInput (by joaomgcd) or Termux (for shell scripting). tasker.lppsa
However, tasker.lppsa persists for three reasons:
If you are on Android 12 or higher, expect some friction. Newer "Protected App" layers may block LPP-SA’s overlay capabilities.
Tasker’s built-in click simulation is limited. LPP-SA allows coordinate-based tapping with adjustable delays and swipe gestures. Imagine an automation where you receive a specific SMS, and Tasker triggers a Lua script that opens your banking app and automates a bill payment by "virtually" tapping the screen in the correct sequence. Lua Player Plus (LPP) started as a homebrew
As of Tasker 6.3 (Android 14+), the LPP framework is being extended with:
The .lppsa file will evolve to include ui_schema and data_policy sections, formalizing how plugins declare their data retention and network usage.
The power of tasker.lppsa comes with significant responsibility. You are effectively giving a scripting language the keys to your operating system. If you are on Android 12 or higher, expect some friction
By using LPP’s secure flag and INPUT_INJECT capability, you can simulate complex gestures (pinch, rotate, three-finger swipe) without the 500ms delay imposed by Android’s AccessibilityService.dispatchGesture(). This enables macro speeds approaching native touch input (~16ms).
Developing for tasker.lppsa requires a shift in mindset from standard Android development. You are no longer an isolated app; you are a co-processor to Tasker’s automation engine.
