Create an Android Permission Change Journal
Track permission changes for selected apps and explain how each change affects capability and risk.
Track permission changes for selected apps and explain how each change affects capability and risk.
Prepare 20m · Build 110m · Verify 30m · Document 20m
Work only inside the folder created by Smartphone-Academy.py prepare permission-change-journal. Use the supplied samples, your own phone, or systems you are explicitly authorized to administer.
Prepare the Termux workspace
Open Termux in the Academy root and prepare this lab with the local companion. It creates safe samples, notes and evidence files under your Termux account.
python Smartphone-Academy.py prepare permission-change-journalNo root. Keep the workspace under $HOME and avoid personal identifiers in evidence.Practical mission
- Select only apps installed on your own device for the exercise
- Record current dangerous and special-access permissions without personal data
- Change one low-risk permission at a time and observe app behavior
- Document whether the permission was necessary, optional or excessive
A before-and-after permission journal with rationale and verification steps.
Quality gate
Analyst reflection
Which result from “Document whether the permission was necessary, optional or excessive” needs stronger evidence before it can support a real decision?
After checking the evidence, run python Smartphone-Academy.py complete permission-change-journal. Progress is stored locally in the Termux home directory.