Status Query
STATUS
Section titled “STATUS”Query the current runtime state of GPS JoyStick. The app responds by broadcasting theappninjas.gpsjoystick.STATUS_RESPONSE with all state data as extras.
Action: theappninjas.gpsjoystick.STATUS
Tier: Pro
Extras: None
Works even when the joystick is idle (not actively mocking).
Response Broadcast
Section titled “Response Broadcast”Action: theappninjas.gpsjoystick.STATUS_RESPONSE
| Extra | Type | Description |
|---|---|---|
lat | double | Current latitude |
lng | double | Current longitude |
alt | double | Current altitude (meters) |
speed | double | Current speed (km/h) |
bearing | double | Current bearing (degrees) |
is_route_active | boolean | Whether a route is currently running |
is_route_paused | boolean | Whether the active route is paused |
route_remaining | int | Remaining waypoints in the active route |
route_total | int | Total waypoints in the active route |
route_mode | String | Route completion mode: "stop", "loop", or "reverse" |
is_reversed | boolean | Whether route is currently running in reverse |
is_running | boolean | Whether the joystick service is active |
is_hidden | boolean | Whether the joystick overlay is hidden |
is_recording | boolean | Whether route recording is active |
record_count | int | Number of waypoints recorded so far |
Note: The STATUS_RESPONSE extras use
doublefor location values (lat, lng, alt, speed, bearing), while the input extras for TELEPORT, WALK, and SPEED usefloat. This is intentional: the app casts internal values todoublewhen broadcasting status but reads incoming extras asfloat.
ADB Shell Example
Section titled “ADB Shell Example”adb shell am start-foreground-service -a theappninjas.gpsjoystick.STATUSThe response is broadcast - to capture it from ADB, you can use logcat or a broadcast receiver.
Tasker: Receiving STATUS_RESPONSE
Section titled “Tasker: Receiving STATUS_RESPONSE”- Create a new Profile → Select Event
- Choose System → Intent Received
- Set Action to
theappninjas.gpsjoystick.STATUS_RESPONSE - Link a Task - extras are available as Tasker variables:
| Tasker Variable | Corresponds To |
|---|---|
%lat | Current latitude |
%lng | Current longitude |
%alt | Current altitude |
%speed | Current speed |
%bearing | Current bearing |
%is_route_active | Route running state |
%is_route_paused | Route paused state |
%route_remaining | Remaining waypoints |
%route_total | Total waypoints |
%route_mode | Route mode (stop/loop/reverse) |
%is_reversed | Reverse direction state |
%is_running | Service running state |
%is_hidden | Joystick visibility state |
%is_recording | Recording active state |
%record_count | Recorded waypoints count |
Example: Conditional Automation
Section titled “Example: Conditional Automation”Use STATUS to build conditional workflows - check if a route is finished before starting the next one:
Tasker Workflow:
- Send
STATUSintent - Receive
STATUS_RESPONSEin a profile - Check
%is_route_active- iffalse, send the nextROUTEintent - Check
%route_remaining- display progress notification