Android-IMSI-Catcher-Detector
Android-IMSI-Catcher-Detector copied to clipboard
CellularPrivacy
No "Neighbouring Cells" displayed
No "Neighbouring Cells" displayed under "Current Threat Level"
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Yeah, I noticed the same recently, what device and ROM (version) do you have? It worked on my S3 with stack android, but when I switched to CM AIMSICD became unusable, patch should be easy to make, but want to make sure it's not device or version dependent.
Running latest nightly of cyanogenmod on Galaxy S4.
Yeah, I noticed the same recently, what device and ROM (version) do you have? It worked on my S3 with stack android, but when I switched to CM AIMSICD became unusable, patch should be easy to make, but want to make sure it's not device or version dependent.
— Reply to this email directly or view it on GitHub https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/issues/630#issuecomment-150116780 .
I think CM team removed one class in 10.2 release that provided required data. No proof, just speculations.
??? On Oct 22, 2015 6:19 AM, "agilob" [email protected] wrote:
I think CM team removed one class in 10.2 release that provided required data. No proof, just speculations.
— Reply to this email directly or view it on GitHub https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/issues/630#issuecomment-150170679 .
@agilob could you please look up what class should have been removed? Curious what this speculation is based on.
@larsgrefer, is https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/issues/630#issuecomment-150170679 really the case? How can we get back hands on that important data?
I am running stock Android and have the same issue. It's a bug in the app, not because of CM. I have a Galaxy Core LTE with Android version 4.x. 1-2 AIMSICD version ago, it worked perfectly, but now same issue as OP.
I am using CyanogenMod 12.1 (Android 5.1.1) on OnePlus Two. Telefon/SIM-Details showing fine, but no neighboring Cells at Current Threat Level. OpenCellID API Key is good and data downloaded.
If a developer needs a OnePlus Two to investigate on the issue - it's lying around here, so i can lend it or hand it over...
Good morning @fabifri, welcome to our project and thanks for offering your device for testing! Please keep it and continue testing, a fresh version of our app will be released by the end of this week.
To everyone reading this Issue: Which network type do you use? Keep in mind that our app currently works best when locked on 3G. If you use LTE, our app will not throw an error, but will get no data (yet).
Telefon/SIM-Details showing fine, but no neighboring Cells at Current Threat Level
That's device-dependent. On some you will get neighbouring cells, on some you won't.
I am only using 3G (and sometimes 2G Networks). Thanks for your Answers. Yeah, i'll continue testing - of course. ;-)
So, the Detection / Thread-Level-Display does still work, even if i can't see any Neighboring Cell Data?
Same Problem on a Fairphone 2 with Fairphone OS 1.2.8 (Android 5.1), also locked to 3G.
Folks, what we need is LOGFILES. Otherwise our developers will not be able to trace down the Issue. So to everyone wanting to help solving this: Please be so kind and record a full logcat with working neighboring cells, then do another one without neighboring cells. Instructions can be found here. Please anonymize your logs by removing CID, LAC and other things and use PASTEBIN. Thank you.
@SecUpwN List of neighbouring cells is implemented correctly (still there is place for improvements), if there is no NC it means:
- device doesn't support it, eg. most Samsung, some LGs doesn't support it at all
- ROM doesn't support it, some ROMs removed that feature
- You're using connection that doesn't provide neighbouring cells like CDMA
It's normal, stop confusing people.
- device doesn't support it, eg. most Samsung, some LGs doesn't support it at all
- ROM doesn't support it, some ROMs removed that feature
That is why I think we need #181 during which #269 should be executed to make that clear to our users.
On an older version of the app, I could see neighbouring cells. Not sure exactly what version changed that, but I can check if it would help fix this issue for some of the users.