Map shows I'm connected to multiple BTSs at the same time

[agilob]

Some of them are very close to my location, others are >20km away

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

[E3V3A]

At first I thought this was a duplicate, but I must have read it in some comments to some other random issue. Yes, this is an issue and a side-effect of broken DB ( #470) and refusing to implement #215 and #250 (which require it).

And if your device support showing neighboring cells, they should be displayed with yet another color. A different color (or shape) should be used for the numbered (sum markers).

[E3V3A]

@agilob Basically what you see above are all the cells you've been connected to. So this behavior is fine until we fix 215.

[SecUpwN]

@agilob, since you mentioned in https://github.com/CellularPrivacy/Android-IMSI-Catcher-Detector/issues/852#issuecomment-205982941 that this Issue is indeed about a "misleading map legend" and not the same Issue, how would we need to change our map legend to fix the "mislead"?

[agilob]

.... If you read the legend, it says "[blue circle] currently connected BTS". If you now look at the map, you see that I'm connected to a BTS 40km away, which is technically not possible. I am also currently connected to 5 BTS at the same time... which is...

[arleslie]

I'm having a similar issue (connected to 5 BTS at the same time) except all of them are around my house. Am I fucked?

[agilob]

@arleslie yes, stop using AIMSICD for your own safety. Don't become paranoid because of bugs in the app.

[SecUpwN]

@arleslie yes, stop using AIMSICD for your own safety.

@agilob, we know of the rather heavy number of bugs in our project, but please refrain to recommend people to stop using it. I also know that you're pissed about the current development progress, but please do not discredit us in public if you'd like to stay member of our project. Thank you for understanding this.

[agilob]

I completely understand it. Your project got a lot of media coverage, but it doesn't detect anything what was proven many times in this repository and outside. Instead it claims to detect a lot of suspicious activity, but all of them are bugs.

[mimi89999]

Was AIMSICD tested against the latest/most advanced IMSI-C?

[mimi89999]

arleslie yes, stop using AIMSICD for your own safety. Don't become paranoid because of bugs in the app.

@agilob I would say stop using cellular/mobile networks...

[agilob]

phone and cellular networks don't tell me everyday that I SHOULD RUN because of false positives.

[Nordlenning]

Yesterday I took AIMSICD out for a 70km drive looking at this issue & 852. When I did this trip my Map-view was at ca 500mtr so I could see some bts & my car.

My finding is: I was connected to 9 bts at the same time, 2 bts was 35km away from my current location. I could not reproduce 852. My green "car" followed me quite accurate. Single arrow.

When I got home I uploaded my findings to OCID server OK, & downloaded it OK. No problem. Found 6 new bts & dusins of new measurements uploaded.(checked on my PC on OCID Map & they are uploaded.)

Then I noticed that if I changed from Street-Map to Terrain-Map I was returned to the main screen, not the map. I was expecting to be returned to map-view. I also noticed that this "Max integer Nr" keeps popping up on cells in Collected Measurements.

After "playing" in Map-View for a while at home, AIMSICD Crashed. Twice. (I took screenshot). I will try to reproduce & get log from this crash when I'm done with some other issues I.m currently working on.

I will do this trip again next week, but with the Map at Max zoom (close). Hope this info is of any value.

@SecUpwN, You may edit,copy,paste & delete in this post as you please.

[Nordlenning]

This happens when I did the same today, no double arrow on the way out, but when I stopped for a coffe & started moving again after 10 min, This LMF followed me all the way home 40 Km..( I could not see him/her) Well AIMSCID Crashed & Then My follower left after restart.

[SecUpwN]

@Nordlenning, thanks for extensively testing our app. Do you think you could be able to do another comprehensive test of this and add a link to an anonymized logcat to this Issue using PIEBIN?

[Nordlenning]

do another comprehensive test of this

Sure, What do you want me to do ? Provoke this crash again or hook my phone to my lap & take a drive while logging ?

[SecUpwN]

@Nordlenning, I'd be thankkful if you could trace down the crash and also possibly find the cause for the multiple BTS connections as mentioned in here. Please keep in mind to anonymize your logfiles.

Was AIMSICD tested against the latest/most advanced IMSI-C?

@mimi89999, likely not. @0x7678 and @evilsocket do have a self-built IMSI-Catcher, but tests need to be updated on our WIKI page Detection Tests. We encourage everyone to built your own and help us.

[Nordlenning]

I will hook my phone to my Lap & take a long drive this comming week & see what I can catch..

[SecUpwN]

I will hook my phone to my Lap & take a long drive this comming week & see what I can catch..

Thanks, @Nordlenning. Having you in our team means a lot to me.

[Nordlenning]

All these "Bluecells" "[blue circle] currently connected BTS". is actually new collected measurements or new discovered BTS, They should (could) be labeled "Orange" Then they would be correct.. All of them states O samples, See lower right corner of picture issue 852. I have 1700 of them after collecting for 2 hour drives & 160km. Some (few) have this Max Integer Nr, (2147483647) issue 817 or -1 . They all show where you're phone discover or measure this new BTS. NOT where the BTS is actually located.

[SecUpwN]

@ziem, would you please take a look at the above message? Sounds like some smaller part of our code to classify new collected cells is messed up..