|
|
|
Our `Android IMSI-Catcher Detector` has tons of cool features, but you might be confused or worry why we need so [many permissions](https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/blob/development/AIMSICD/src/main/AndroidManifest.xml). The reason is simple: We need to overcome the Android OS limitations as described in our [Development Roadmap](https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/wiki/Development-Status#development-roadmap). Since our App needs to digg down deep into the baseband and read values that are normally not readable, `AIMSICD` needs just about all variables, sometimes even ROOT access for extended functions like silent SMS detection. But don't worry, it is not mandatory and we're privacy enthusiasts - which means we're always trying to melt down the permissions to the bare necessities. Should you ever discover a permission you wonder about, feel invited to get in touch with us - either via E-Mail or a filed Issue. Thank you!
|
|
|
|
Our `Android IMSI-Catcher Detector` has tons of cool features, but you might be confused or worry why we need so [many permissions](https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/blob/development/AIMSICD/src/main/AndroidManifest.xml). The reason is simple: We need to overcome the Android OS limitations as described in our [Development Roadmap](https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/wiki/Development-Status#development-roadmap). Since our App needs to digg down deep into the baseband and read values that are normally not readable, `AIMSICD` needs just about all variables, sometimes even ROOT access for extended functions like silent SMS detection. But don't worry, we're privacy enthusiasts - which means we're always trying to melt down the permissions to the bare necessities. Should you ever discover a permission you wonder about, feel invited to get in touch with us - either via E-Mail or a filed Issue. Thank you!
|
|
|
|
|
|
|
|
---
|
|
|
|
|
| ... | ... | |
