Detect Connectivity Changes Without Scanning
Compare two local connectivity snapshots from your own Android device and explain changes in interfaces, routes, DNS configuration, and reachability without scanning other systems.
Compare two local connectivity snapshots from your own Android device and explain changes in interfaces, routes, DNS configuration, and reachability without scanning other systems.
Prepare 25m · Build 105m · Verify 25m · Document 25m
Work only inside the folder created by Smartphone-Academy.py prepare connectivity-change-detection. Use the supplied fictional samples or data you are explicitly authorized to handle.
Prepare the Termux workspace
Open Termux in the Academy folder and create the safe workspace. The companion generates samples, notes, and evidence files under your account.
python Smartphone-Academy.py prepare connectivity-change-detectionNo root. Work only with the supplied files under $HOME.Practical mission
- Capture or use supplied before-and-after interface, route, and DNS snapshots
- Normalize volatile values so harmless timestamp changes do not dominate the comparison
- Classify each difference as expected, unexplained, or evidence requiring a second check
- Write a minimal non-scanning verification plan using only your device and permitted endpoints
A connectivity-diff.md with normalized snapshots, a change table, and confidence notes for every conclusion.
Quality gate
Analyst reflection
Which result from “Write a minimal non-scanning verification plan using only your device and permitted endpoints” needs additional evidence before it could support a real operational decision?
After checking the deliverables, run python Smartphone-Academy.py complete connectivity-change-detection. Progress is stored locally in the Termux home directory.