How To Call It
System is a global table: call its functions with a dot (System.<method>(...)), not a colon.
Turns a device feature on or off: "torch", "volume_up", "volume_down", "volume_mute", "ringer_normal", "ringer_vibrate", "ringer_silent", "dnd", "auto_brightness", "rotation_lock", "screen_cache" and similar.
Documented for app version 1.0.51Updated:
System is a global table: call its functions with a dot (System.<method>(...)), not a colon.
In system flow, design steps as observe first and act second when the API can affect device state.
Required: feature. Optional: enabled (omit to pass nil and use the runtime default). Returns a boolean (true or false).
Using this API with logging, error handling, and next-step control produces much more professional results than calling it in isolation.
The snippet below is a starter pattern that can be applied directly in runtime flow.
local ok = System.toggleFeature("torch", true)From foundation to combined usage, each level is provided as a separate code block so you can copy the level you need and adapt it directly.
local ok = System.toggleFeature("torch", true)local stepOk = true
local ok = System.toggleFeature("torch", true)
if stepOk then
wait(200)
endlocal ok, err = pcall(function()
local ok = System.toggleFeature("torch", true)
end)
if not ok then
print("API step failed: System.toggleFeature: " .. tostring(err))
requestStop()
end-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_togglefeature_step()
local ok = System.toggleFeature("torch", true)
end
local ok, err = pcall(run_togglefeature_step)
if not ok then
toast("Step failed")
print(err)
endlocal ok = System.toggleFeature("torch", true)
wait(200)
print("Combined with logging and flow control")