HOW TO: Start/Stop Scan/Pause WiGLE WiFi Android when a battery, location, network, or other event happens

Suggestions for WiGLE/JiGLE/DiGLE

6 posts • Page 1 of 1
Guide to using intents in WiGLE:

Some of the most common WiGLE WiFi feature requests include numerous permutations of "start/stop scanning," upload, or quit when certain external conditions are satisfied (1, 2). While we may eventually implement the most popular of these in WiGLE WiFi Wardriving, you need not wait to get this functionality!

WiGLE uses a feature of the Android operating system named "broadcast intents" - these are an operating system-supported mechanism for passing simple messages between Android applications. In order to do simple automation based on system events, people have built a whole suite of cool tools where you can set up broadcast intents to fire when any of a large number of system events take place.

Currently, the app supports four primary intents:
1. Start Scanning: net.wigle.wigleandroid.SCAN
2. Pause Scanning: net.wigle.wigleandroid.PAUSE
3. Upload current networks: net.wigle.wigleandroid.UPLOAD
4. Stop WiGLE WiFi: net.wigle.wigleandroid.END

There are plenty of different apps that can fire broadcast intents for android, but we've tested with Tasker and Automate

Tutorials for settings up broadcast intents with the app of your choice are available online, but the tasker guide serves as a good staring point.

Implementation notes:
- you *must* specify the whole name in the "Action" (e.g. net.wigle.wigleandroid.UPLOAD )
- you *must also* include the "Package" ( net.wigle.wigleandroid ) even though it's redundant.
For Tasker users, user DNC composed some helpful screenshots demonstrating how to configure an "Action" to trigger a WiGLE intent:
dnc-tasker-action-1.png
dnc-tasker-action-1.png (51.93 KiB) Viewed 15566 times
dnc-tasker-action-2.png
dnc-tasker-action-2.png (54.61 KiB) Viewed 15566 times
[code] :D [/code]
Guide to using intents in WiGLE:

Some of the most common WiGLE WiFi feature requests include numerous permutations of "start/stop scanning," upload, or quit when certain external conditions are satisfied (1, 2). While we may eventually implement the most popular of these in WiGLE WiFi Wardriving, you need not wait to get this functionality!

WiGLE uses a feature of the Android operating system named "broadcast intents" - these are an operating system-supported mechanism for passing simple messages between Android applications. In order to do simple automation based on system events, people have built a whole suite of cool tools where you can set up broadcast intents to fire when any of a large number of system events take place.

Currently, the app supports four primary intents:
1. Start Scanning: net.wigle.wigleandroid.SCAN
2. Pause Scanning: net.wigle.wigleandroid.PAUSE
3. Upload current networks: net.wigle.wigleandroid.UPLOAD
4. Stop WiGLE WiFi: net.wigle.wigleandroid.END

There are plenty of different apps that can fire broadcast intents for android, but we've tested with Tasker and Automate

Tutorials for settings up broadcast intents with the app of your choice are available online, but the tasker guide serves as a good staring point.

Implementation notes:
- you *must* specify the whole name in the "Action" (e.g. net.wigle.wigleandroid.UPLOAD )
- you *must also* include the "Package" ( net.wigle.wigleandroid ) even though it's redundant.
Does anyone know how to do the app intents in Automate?
It appears automate has some pre-discovered package activities on the app start event but none match the intents above.
hehe, spent my money on Tasker so haven't invested in Automate yet, but if you get it figured out, please post; happy to pin/add to the guide post!

If you need a "receiving class" (it should auto-resolve from the package/intent), they may be:
net.wigle.wigleandroid.listener.TerminationReceiver
for net.wigle.wigleandroid.END

net.wigle.wigleandroid.listener.UploadReceiver
for net.wigle.wigleandroid.UPLOAD

net.wigle.wigleandroid.listener.ScanControlReceiver
for net.wigle.wigleandroid.SCAN and PAUSE
the intents above are definitely the correct ones, but it looks like Automate
Automate App instructions
Use the fx button at the end of each field to enter manual mode

1) Turn on wifi using a Wi-Fi Set State block

2) Start the app using an App Start block
Package
="net.wigle.wigleandroid"
Activity Class
="net.wigle.wigleandroid.MainActivity"

2) Control the app by Broadcast Send blocks
Package
="net.wigle.wigleandroid"

Then in the next fields
a. Start scanning
Receiver Class
="net.wigle.wigleandroid.listender.ScanControlReceiver"
Action
="net.wigle.wigleandroid.SCAN"

b. Upload
Receiver Class
="net.wigle.wigleandroid.listender.UploadReceiver"
Action
="net.wigle.wigleandroid.UPLOAD"

c. Exit the app
Receiver Class
="net.wigle.wigleandroid.listender.TerminationReceiver"
Action
="net.wigle.wigleandroid.END"

Idea:
I am trialing a function where if i plug in to mains power during 9am-5pm, it will wait 30 seconds before checking if the GPS speed is above 10km/h - if so then it will launch wigle and start scanning, then terminate when I unplug.

6 posts • Page 1 of 1

Return to “WiGLE Project Suggestions”

Who is online

Users browsing this forum: No registered users and 4 guests