search

CellularPrivacy / Android-IMSI-Catcher-Detector

AIMSICD • Fight IMSI-Catcher, StingRay and silent SMS!
https://cellularprivacy.github.io/Android-IMSI-Catcher-Detector/
GNU General Public License v3.0
4.68k stars 941 forks source link

Too few BTS measurements #472

Open E3V3A opened 9 years ago

E3V3A commented 9 years ago

Renamed from: Too many redundant BTS measurements

The database viewer show too many equivalent measures. In one minute I get about 60 measurements all with the same exact data.

screenshot_2015-06-16-16-27-55

This means that the mechanism for updating measurements is broken somehow.

Correct behavior: Maximum rate possible using listener for new (mobile) network connection updates. If no changes has occurred, only log first seen and last seen, none of the measurements in between.

EDIT:

Since the isue now has changed to the opposite, in respect that there might not be enough measurements, we need to discuss further.

Developer Question: To what extent should add Signal Strength changes to this table?

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

E3V3A commented 9 years ago

After the new DB overhaul # 215 this issue has reversed. Now there is not enough measurements taken or shown in DB Viewer. (Hard to tell which.)

ghost commented 9 years ago

Atm I only update what cell already logged so not to fill up view with duplicates but easy fix and I was aware of this just didnt know what exactly you where going for with bts measurements

E3V3A commented 9 years ago

Ok, good to know. Yes, I see what you're saying. The EventLog show only events that have informational value to the user. Whereas, the BTS Measurements table should have all events found by phone from network. It's the basis of the EventLog and all the detection mechanisms. Therefore the BTS Measurements has to be shown sorted by timestamp (latest first) in the DB Viewer.

The original issue above was that every measurements would be shown, even is the same in all aspects.