Law enforcement agencies are very often sending out so-called "silent SMS" (see this German article) which do not show up on a display of a target device, nor trigger any acoustical signal when received. But when they are delivered they generate a delivery receipt and, most importantly, are recorded in a data retention database together with the location of a mobile phone which received it. There's no need for an IMSI-Catcher then. Reliable detection of silent SMS will be crucial to the usefulness of AIMSICD.

A Silent SMS / Stealth SMS / Ping SMS is a Type0 SMS which is specified in GSM 03.40 as follows: "A short message type 0 indicates that the ME must acknowledge receipt of the short message but may discard its contents."

I have already contacted Michael (@SilentServices), the developer of the useful tool called HushSMS, which also enables its users to send out different types of SMS (including type Class 0, but without the location request). Check out his company Silent Services. I have bought his app a long time ago and am hoping he'll contribute some code snippets for detection of such SMS. Stay tuned.

The $115 bounty on this issue has been claimed at Bountysource.

Somewhat relevant to #479, but in the other direction: With the shift toward monochrome notifications icons, I would love to see an optional set of icons that could display all of the relevant states, but with a single colour to match. Currently, this is the one of only two persistent notification icon apps that use colour, and it doesn't match the rest of my notifications bar. Having this as a option UI enhancement for users would be a minor task but great improvement.

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

After a clean install of 0.1.32 alpha b00, the app crash when I try to download the cell informations from OpenCellID.

This from the download option in the menu or with the download icon in the map of the cells.

Samsung Galaxy S4 mini , stock firmware , rooted by towelroot.

As we have noticed in many recent issues and many past discussions, there is a terrible urgent need to restructure our original database (DB). This DB was originally made for our very first attempts in building this app. However, we've come to realize that the way it is used and structured and how its tables are internally labelled is really confusing at best. It was made according to very weak documentation and poor understanding of what we actually needed.

After several weeks of thinking about this, on and off, I've come to the point where it's time to get it done. Here is a brand new proposal that should cover most features in the near future and hopefully most of the beta stage life-time.

This is the way we will do it:

1. I finish the DB documents and table ER diagram, then
2. you guys make a critical re-view and feedback.
3. I make the required updates, if any, and go back to (1), else
4. we re-code the DB into app.

NOTE: I suggest keeping the old tables while adding the new ones, to maintain simple and progressive migration.

There will surely be loads of questions surrounding this, but I think I might have covered most of it in the (still to be finished) documents:

• [x] General DB functional overview
• [ ] Detailed DB tables Descriptions
• [ ] Default DB data

Then there will be new App help pages and an FAQ, to be implemented inside app. (Separate issue.)

• [x] General App functionality
• [x] Internal App help pages
• [ ] Internal App FAQ
• [ ] TBA

Here are the old currently used DB tables:

Here are the NEW DB tables:

UPDATED: 2015-07-31

Reference Issues: These are issues that directly depend on these tables. #13, #69,#71, #91, #93, #97, #100, #117, #176, #201, (#203 ?),

More descriptions will be added below.

There is a $10 open bounty on this issue. Add to the bounty at Bountysource.

Dear @xLaMbChOpSx, I know you have a rough time here. Another new Issue? Sigh - I'm sure you're not too happy about that. Furthermore, it appears that currently multiple Issues from previous WIP-Releases are cramped into one Issue, upgrading these to "Monster Issues" - that's NOT the fault of @E3V3A, but of the partially very fast development with new WIP-Releases in the middle. And that is a GOOD thing! But since you're currently pretty much alone on this journey (working to resolve that soon), I bet you're a little lost on what to work on.

Fret no more, here comes a cool new feature I'd like to take advantage of: Nested task lists!

So this is what I'll do with this new "Issue": I will review and ELIMINATE all "Monster Issues" (aka "v0.1.xx-alpha Bug Reports: Add your bugs here!") to comfortably list those Issues dragged from previous WIP-Releases up until now to be RESOLVED for WIP-Release 0.1.25 - this should allow for some time. And please, @xLaMbChOpSx, TAKE YOUR TIME! Really, I mean it. If you're upset about how things are being processed here, please talk to me on XDA. I'm a firm believer of the theory that god gave everyone a mouth to use it and to also voice constructive criticism. Please don't hesitate to tell me what you'd like to see changed.

@xLaMbChOpSx and @E3V3A, please help me on this to clear things up: Please TICK the things that are SOLVED! Thank you, folks. :sunflower:

Remember: When all these things are done, we're automatically at WIP-Release 0.1.25. Take it easy. We should also not forget to release the versions in the middle up until 0.1.25 fixing the other Issues.

Reported bugs from WIP-Release 0.1.8-alpha, Issue #44

• [x] "Tracking signal strength" icon still show red cross, when tracking
• [x] [Menu] --> "Show Map" starts map centered on the sea outside Togo (Africa)
• [x] [Menu] --> Preferences --> Icon Theme is not showing the current theme selection
• [x] All radio buttons are empty
• [x] Returning from "Show Map" using "top-left slider area" disables all tracking
• [x] Maps are not showing any cell towers (from OpenCellD)
• [x] OpenCellID CSV file is empty (even after download)
• [x] Exported CSV files contain many entries where only time stamp has changed
• [x] Signal strength CSV is empty.

Reported bugs from WIP-Release 0.1.10-alpha, Issue #49

• [x] Database Viewer: "Signal Strength Data" is empty, but warning is given
• [x] Database Viewer: When "Cell Data" is selected and doesn't contain any data, no warning is given
• [x] Show Map: Map starts at an "angle" where north is not up and map is not "flat"
• [x] Map settings are not saved between views
• [x] Updates of OpenCellID need to be downloaded again when going to the map
• [ ] OpenCellID data seem irregular: Sometimes showing some towers at other times not
• [ ] On main window, try to make some kind of indication of, when values have recently changed
• [x] Do we have any measure about the polling time? I mean, how fast do these variables update?

Reported bugs from WIP-Release 0.1.11-alpha, Issue #53

• [x] Database Viewer: "Cell Data" has entries with CellID = -1

Reported bugs from WIP-Release 0.1.13-alpha, Issue #58

• [ ] Menu: "Update OpenCellID Data", gives the error message "Unable to determine your last location!"
• [x] When disabling "tracking cell info", it should also disable "location tracking". But not vice versa.

Reported bugs from WIP-Release 0.1.14-alpha, Issue #62

• [x] Map View: Current "Map Type" selection is not shown. (perhaps add a radio button?)
• [ ] The "Update OpenCellID Data" function is not possible before enabling location tracking
• [x] Re-implement the manual AT command entry from older version. Perhaps in a new slide page?
• [x] Add automatic refresh of the "Cell Information" (ServiceMode data)
• [x] Add a "Preferences" settings item for the refresh rate above. Something like:
• Manual
• MAX (as fast as possible) Warning: Leaving this on may consume excessive battery power
• 1s, 2s, 5s, 10s, 30s, 1min, 5 min, etc.
• Automatic (when change is detected, should be default)

Bugs from WIP-Release 0.1.15-alpha, (not reported)

• [x] When there is no mobile network coverage, the app crashes and FC's upon start.

Bugs from WIP-Release 0.1.16-alpha, (not reported)

• [x] FC's when trying to view map on I9100 SlimKat 4.4.2. Just before FC, logcat shows several warnings from GooglePlayServicesUtil: "Google Play services out of date. Requires 4452000 but found 4325034."

Bugs from WIP-Release 0.1.17-alpha, (not reported)

• [x] Doesn't let you update OpenCellID without locked location.
• [x] Version number is still showing 0.1.16
• [x] Are you sure you uploaded the right version?
• [x] Refuses to close/quit no matter what the preferences settings

Bugs from WIP-Release 0.1.18-alpha, (not reported) On: S4-mini GT-I9195 stock 4.2.2 SELinux Enforcing

• [x] Crashes upon startup: "Unfortunately Android IMSI-Catcher Detector has stopped.", but then starts anyway! (WTF?)
• [x] Crashes upon "Quit" with same message as above, but then quits. (Those crashes seem random. Sometimes yes, sometimes no.)
• [x] Crashes after hitting and completing "Backup database"
• [x] Neighboring Cell Info broken
• [x] "AT-interface": still not enabled
• [x] "About AIMSICD": Background color of white text and blue text is different.
• [x] "About AIMSICD": Most info links should take you to another (popup?) window with text and not to Github website. (OK for now.)
• [x] Generates loads of Errors in Logcat from: LocSvc_afw, LocSvc_eng and LocSvc_adapter
• [x] "Settings:Refresh rate" item does not have an initial value shown. Should probably be Automatic. - [ ] "Settings:Refresh rate": Changing has no effect.
• [x] Very "laggy"... need further investigation.

Summary: This version is harder to test on this device. Possibly because of the Enforcing mode, which prevent access to many file locations and other operations. More tests needed with SELinux settings in Enforcing versus Permissive modes, including setting full access to (via EFS files) to the ServiceMenu items.

On: GT-I9100, SlimKat 4.4.2b4

• [x] Crashes on "Backup database"
• [x] "Settings:Refresh rate": Changing has no effect.
• [x] Attemting to download OCI DB crashes if no GPSlock has been found.

Summary: Most things that was causing crashes for the I9195 above, is working on this device, apart what is mentioned above. Neighboring cells look better and more clear. More testing needed. (I have a very bad battery and no gps-lock near outlet.)

Bugs from WIP-Release 0.1.19-alpha, (not reported) On: S4-mini GT-I9195 stock 4.2.2 SELinux Enforcing

• [x] "Settings:Refresh rate": Changing has no effect.
• [ ] "Neighboring Cells": Hitting refresh, doesn't update list, but only adds previous list (not being able to scroll down), but increments the cell count by one, every time.
• [x] Crashes after "Quit" with the message: "Unfortunately Android IMSI-Catcher Detector has stopped.", and then closes. Relevant Logcat HERE.
• [ ] "Neighboring Cells": Showing "funny code" for all cells. look like perhapsits the PSC ? Need further investigation, also a warning in logcat about length of something.

On: GT-I9100, SlimKat 4.4.2b4

• [x] "Settings:Refresh rate": Changing has no effect.

Summary: Most things that was causing crashes for the I9195 before have been fixed, apart what is mentioned above.

Bugs from WIP-Release 0.1.20-alpha, (not reported)

General UI/UX improvements (all devices):

• [x] UI: remove "line number" item from Device Information
• [x] UI: Change "Network CellID" name to "Network CID" (or is there a another reason for using that?) and move it under "LAC" item. (These usually go together.)
• [x] "About": Change the text background color to be the same as for the rest of the screen.
• [ ] Install Buttons: Can we change them from "next to each other" to stacked? So that we can fit the text above next to the buttons?

On: GT-I9100, SlimKat 4.4.2b4

• [ ] Funny behavior when using "Persistence" OFF and "Tracking" ON, and then trying to Quit, or stopping GPS. With the result that the app refuses to close.

On: S4-mini GT-I9195 stock 4.2.2 SELinux Enforcing

• [ ] SU/Busybox checks should be done when opening Application and not later. (Unless necessary.)
• [ ] "AT" works but output goes to the shell where cat /dev/smd0 & was issued... Need more test.
• [x] There is this item called "Line Number" under Device Information. What is that? Do we need it? (On my phone it just shows the IMSI, which is already shown under SIM info.)
• [ ] After "Quit" the App now refuses to shutdown, even though Persistence is OFF. Service issue. (?)

Bugs from WIP-Release 0.1.21-alpha, (not reported) GT-I9195:

• [ ] Crashes when entering Map Viewer without initial GPS-lock/location
• [x] Need roller/spinner for informing on the status of OCI download
• [ ] DB:LocationData has 0x7FFFFFFF values (shown in dec) for CID and LAC
• [ ] Cell Inforamtion:NeighboringCells has 0x7FFFFFFF values (shown in dec) for all fields
• [ ] Cell Inforamtion:NeighboringCells show no indication of refresh

:exclamation: BUG ADD FREEZE - LET'S FOCUS ON FIXING ALL OF THESE. THANKS. ~~This list is subject to changes and / or deletions as we test them on our latest WIP-Release.~~

I am browsing the source code. I do not have a rooted phone but I am wondering the AT Command injection output. Can you provide application screenshots ?

Hello, on my Nexus 7 (see TD) is Network Information empty. Using apps like NetMonster I can see Network Information. Unfortunately there is nothing in the logcat.

We need better logging in the app to find the bug.

09-30 23:40:12.573    6681-6681/com.SecUpwN.AIMSICD E/MultiRil﹕ Samsung Multiclient RIL not available: gsm.version.ril-impl = android xgold-ril 1.18
09-30 23:40:12.743    6681-6681/com.SecUpwN.AIMSICD D/dalvikvm﹕ GC_FOR_ALLOC freed 202K, 4% free 7969K/8216K, paused 21ms, total 21ms
09-30 23:40:13.303    6681-6681/com.SecUpwN.AIMSICD I/AIMSICD_Service﹕ Service launched successfully.
09-30 23:40:13.313    6681-6681/com.SecUpwN.AIMSICD I/Choreographer﹕ Skipped 61 frames!  The application may be doing too much work on its main thread.
09-30 23:40:13.403    6681-6681/com.SecUpwN.AIMSICD D/libEGL﹕ loaded /system/lib/egl/libEGL_tegra.so
09-30 23:40:13.413    6681-6681/com.SecUpwN.AIMSICD D/libEGL﹕ loaded /system/lib/egl/libGLESv1_CM_tegra.so
09-30 23:40:13.423    6681-6681/com.SecUpwN.AIMSICD D/libEGL﹕ loaded /system/lib/egl/libGLESv2_tegra.so
09-30 23:40:13.443    6681-6681/com.SecUpwN.AIMSICD D/OpenGLRenderer﹕ Enabling debug mode 0
09-30 23:40:13.813    6681-6681/com.SecUpwN.AIMSICD D/dalvikvm﹕ GC_FOR_ALLOC freed 400K, 6% free 8075K/8516K, paused 17ms, total 17ms
09-30 23:40:14.013    6681-6681/com.SecUpwN.AIMSICD I/Choreographer﹕ Skipped 41 frames!  The application may be doing too much work on its main thread.

Debug version of App doesn't quit. Need to force close it.

This is an old bug we used to have (issue #246) and painfully managed to solve, but now it seem all this bloody "refactoring" has re-introduced it again. Or it is a side-effect of using leakcanary?

@d-mariano You managed to solve this in the past. Any ideas?

Request to http://opencellid.org/cell/getInArea?key=XXXXXXXXXXXXXXXXXXX&BBOX=... returns

<?xml version="1.0" encoding="UTF-8"?>
<rsp stat="fail">
<err info="Your API key must be whitelisted to run this operation. 
This service is free of charge as long as your application contributes to the OpenCellID project. 
Should your application meet this requirement, please contact [email protected] for the authorization of your API key." code="4"/>
</rsp>

EDIT by @SecUpwN: Removed sensitive API key information.

Thank you for your feedback! Please add below details so that we can help you a bit faster.

Agreements

Please check these boxes to ensure you've actually read and understood these important rules!

• [x] I have reviewed and accepted the guidelines for contributing to this project.
• [x] I have searched the open Issues and made sure I am not filing a duplicate.
• [x] I have read the notes on debugging and will properly maintain this Issue.

Overview

Please add a short and easy to understand description of the Issue you've experienced here.

There are 2 unexspected forcecloses that is discovered in 0.1.41 alfa (01.04.16 18:00) Rooted Sony Experia lt25i CM Tsybasa (lollipop)

1. When you try to download OCID data in Aiplaine Mode W or WO wifi connected, AIMSCID Crash. Log of the inncident https://defuse.ca/b/PxOPvb8L1OeR9Q1aCRZpMD
2. When you are in map view & try to watch logging while you download OCID data, AIMSCID Crash.

Log of the inncident https://defuse.ca/b/NngQqTs5reAJo3pY3Elo7n

Reproduction

Please tell us the detailed steps on how to reproduce your Issue here.

--- Same as above

References

If your Issue is related to any other existing Issues or pull requests, please link them here.

--- Comments in 816 including screenshot

Screenshots

If you experienced visual glitches, please add a screenshot without metadata here.

@xLaMbChOpSx, after having installed version 0.1.2-alpha with the correct permissions in system/priv-app, I seem to not be able to install any other Apps. I will try to remedy this situation by removing the app and re-flashing my ROM, but wouldn't it be useful to implement some method of internal error log collection for AIMSICD? We might have a chance of better debugging through doing so..

EDIT: Ok, so I have serious trouble right now - even after removing AIMSICD v0.1.2-alpha and re-flashing my ROM atop the old data, I still cannot install any new Apps. Will have to do a fresh install. To find out what's causing this behavior, I'd like you to take a look at the following logcat: http://d-h.st/bqC. Please tell me if AIMSICD is the cause or if another App like Xprivacy is causing me headaches. Thanks!

The only commits for the last few years seem to be automated commits from the Weblate translation service. Is this project still active, or is it dead like #982 claim?

Agreements

• [x] I have reviewed and accepted the guidelines for contributing to this project.
• [x] I have searched the open Issues and made sure I am not filing a duplicate.
• [x] I have read the notes on debugging and will properly maintain this Issue.

Overview

• AIMSICD version (see the About screen):
• Phone and ROM running current release:
• Link to logfile without identifyable data:

Reproduction

References

Screenshots

I have a long story but the sheriff dept has been intercepting mine and others calls in my area for at least the last year. They've watched and tracked my location. Followed me around...all that fun stuff.

Their system shuts off a call at 4 hours on the dot. Have to reconnect the call after that. When they are not intercepting calls have lasted 6.5 hours.

They disconnect my phone from the normal cellular network and then drive off but my phone does not reconnect to the network and will sit "dead" all day until I reset it.

When their device is within about 150 - 200 yards it overheats my phone - too hot to touch inside the crappy rubber case. This has happened on my friend's phone as well. We've gone through 6+ phones trying to figure out what's going on. I sent him a Nokia 7.1 and it got super hot but burned out their interception device before it died. The device could only disconnect our calls - wouldn't let calls go through.

While they are listening I can hear " tsst.......tsst.......tsst......tsst.......tsst.......tsst....." in the background during the call. kind of like when your phone is ringing and going through different switches and stuff but it will last the entire length of the call - or 4 hours whichever comes first. I don't hear it as much recently. I've been complaining to them during calls that I can tell they are listening so IDK if they have gotten better or if they got tired of me talking shit to them.

Everybody thinks I'm paranoid - which I am - but I didn't believe it either until it happened to me. I was talking shit to one of them one night and walked out side. My phone overheated in my pocket to such a degree it would literally burn me. I held my phone off my skin inside my pocket moving my fingers around and at that time a sheriff patrol SUV came around the corner. My phone cooled off when he got 2 - 3 blocks away. Probably about 200 yards.

I have other reasons to believe this is happening also but the phone over heating is the one that really clued me in.

I"m not real good with ADB nor am I very versed in github. I"m gonna try and get this loaded up and see what happens.

Sorry I couldn't figure out how to contact you guys another way.

Hello. I apologize for writing here, but I have not found any contacts. Can you please tell me what this "Spy call" function is? - https://github.com/CellularPrivacy/Android-IMSI-Catcher-Detector/wiki/glossary-of-terms#spy-call What devices support it? Is it possible and where to read about "Spy call" in the RFC GSM specification? If there is type 0 for "quiet sms" or "ping sms", then what type of call is for "Spy call"? I searched the internet but did not find a mention anywhere. Thanks.