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
  • Issues
  • #269
Closed
Open
Issue created Jan 08, 2015 by Administrator@rootContributor

Initial Startup: Verify Detection & Protection

Created by: SecUpwN

Androids

Folks, I know we're currently piling up on Issues, sorry about that. But trust me, this is good since this conveys we're having very clear ideas about how our App shall work and what needs to be addressed.

Since our project has set a high goal to provide broad support for current consumer smartphones out there, it is important to verify to the user if our App is really working as supposed to on their specific phone. Of course, we currently have our Requirements, but I do want to avoid people thinking that our App works on their new smartphone while in fact it does nothing else than showing a green Status Icon.

Proposal:

  • On initial startup of the App, run a set of tests to verify that the phone supports detection/protection
  • Show a prompt that gives exact detection information (maybe automatically create a logcat on SD)
  • If a users phone is not supported, tell user to join our GitHub and upload the logged information
  • Users shall be re-run it again by pressing Verify Detection/Protection from Preferences

Should this Issue be in fact a duplicate of #173 (which was declined here), let me know.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Assignee
Assign to
Time tracking