Tasker.lppsa

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. tasker.lppsa

Combine accelerometer, gyroscope, and magnetometer data from Tasker’s %SENSOR variables, process them via a native C library (loaded via System.loadLibrary), and inject filtered orientation data back into Tasker as new user variables. Latency: <5ms over LPP. Lua Player Plus (LPP) started as a homebrew

Unlike traditional Tasker plugins that rely on com.twofortyfouram.locale.intent.action.FIRE_SETTING, the LPP method uses local sockets (AF_UNIX on /data/local/tmp/tasker_plugin.sock). This bypasses the Intent dispatch overhead (often 50–150ms) and allows for sustained bidirectional streaming—critical for real-time sensor fusion or accessibility event injection. While the standalone LPP-SA app is robust, its

Tasker writes to the socket:
QUERY_CAPS com.example.secureplugin
The plugin responds with a binary blob of its declared actions.

Tasker updates frequently. Your tasker.lppsa should include a min_tasker_version field. If omitted, Tasker assumes version 5.0 (released 2019). Newer features like async_timeout and input_private require Tasker 6.1+.