Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Android-IMSI-Catcher-Detector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CellularPrivacy
  • Android-IMSI-Catcher-Detector
  • Wiki
  • AT Command Interface

AT Command Interface · Changes

Page history
Changed image link to SpiderOak authored Apr 07, 2015 by Security: Pwned.'s avatar Security: Pwned.
Hide whitespace changes
Inline Side-by-side
AT-Command-Interface.md 0 → 100644
View page @ 726d7c3f
:exclamation: **CAUTION: VERY ALPHA! ROOT IS REQUIRED!**
The AT Command Interface is now enabled thanks to the great work of [E3V3A](https://github.com/E3V3A) and [xLaMbChOpSx](https://github.com/xLaMbChOpSx). The current version of the AT Command Interface is accessible through the navigation drawer, but it will vanish into a special debugging menu in the future.
Root terminal methods are used to execute the AT Command. Therefore, this fragment will check for both ROOT (su binary) and BUSYBOX to confirm both are available on your device. If they are not available, the execution section of the fragment will NOT display.
If the initial setup works correctly the next step is trying to determine your RIL Serial Device through the system property `ril.libargs`. If this is successful then you are in business and the AT Command Interface system is available for you to test. This will probably NOT WORK on many devices (such as i9100) but it will provide details of the failure if available and display them to the screen but also write them to the file `error.txt` in the AIMSICD directory of your external storage (we are happy to receive these error reports to improve our App). Use the Timeout drop-down field to set a certain time for an AT Command response.
![AT Command Interface](https://spideroak.com/share/IFEU2U2JINCA/GitHub/home/SecUpwN/SpiderOak/SCREENSHOTS/AT-Command-Interface.png)
\ No newline at end of file
Clone repository

Project Information

  • Glossary of Terms
  • Requirements
  • General Overview
  • Technical Overview

Getting started

  • Building
  • Installation
  • Permissions
  • Status Icons

Navigation Menus

  • Disclaimer
  • Main Screen
  • Navigation Drawer
  • Preferences
  • About AIMSICD

Important Functions

  • Cell Monitoring
  • Cell Information
  • AT Command Interface
  • Database Viewer
  • Antenna Map Viewer
  • Silent/Stealth SMS

Developers

  • Development Status
  • Testing Devices
  • Contributing
  • Style Guide
  • Resources
  • Privacy

Support

  • FAQ
  • Contact
  • Problems
  • Donations

Gimme moar!

  • Unmasked Spies
  • Media Material
  • Press Releases
  • Recommendations
  • Similar Projects