LAC changing detected

[MatejKovacic]

I have installed AIMSICD (WIP TEST RELEASE v0.1.28-alpha-b00) to a mobile phone with Android 4.4.2. I am customer of slovenian mobile operator Si.mobil (operator's code is 29340).

Today I was at some location, where AIMSICD noted me, that I am in hostile service area - changing LAC is detected:

So I checked out Antenna Map Viewer and it seems I am connected to two different cells:

However, detail view has shown, that two cells are in fact different:

My question is: what does it means, how to explain this behavior. Because the area where this happened is quite isolated (there are some hills around) and there is only one base station of Si.mobil service provider.

Any idea?

[SecUpwN]

@E3V3A, would you please chime in? Thank you.

[scento]

I experienced something similar while testing AIMSICD 0.1.28-alpha-b00 on hammerhead with Android 5.1 - it seems as if all base stations around my location in Germany are using different LAC's (40326, 5827, 31506, 40326). My map view shows even more "active" BTS, which are far away from my current location.

[SecUpwN]

@MatejKovacic and @scento have you made sure that you've downloaded the current OCID data?

[E3V3A]

Actually, I just noticed you're using 4G (LTE ) which we currently don't have support for...

[E3V3A]

This is also a side effect of having as broken DB. Fix the DB so that we can properly filter bad BTS. The PC is also wrong since it should be 5 digits and not 6.

[SecUpwN]

Actually, I just noticed you're using 4G (LTE ) which we currently don't have support for...

Is this an (invalid) bug on our side now, or how to classify this? Let it stay open?

[MatejKovacic]

OK, any hint how to fix broken database?

[SecUpwN]

OK, any hint how to fix broken database?

The right thing to do would be to craft a pull request for the complete overhaul described in #215.

[E3V3A]

@SecUpwN

Is this an (invalid) bug on our side now, or how to classify this? Let it stay open?

I don't have a working LTE device right now, so I can't test this at all. We need to file a separate issue for LTE support.

@MatejKovacic

OK, any hint how to fix broken database?

All the hints required can be found in that #215 issue thread.

[E3V3A]

Many of the programming details and required LTE info can be found in AIMSICDDbAdapter.java.

[E3V3A]

This may also be related to #525...

[SecUpwN]

@MatejKovacic, please accept that I am closing this as INVALID since our app does not yet support LTE until #442 has been solved. Furthermore, you did not respond via E-Mail since more than a month. You may test the latest version of our app without using an LTE connection and re-open this if it reappears.

[SecUpwN]

@smarek, this Issue is INVALID since we do not support LTE yet (see #442) and it will likely not happen until the v0.1.37-alpha release. Hence no need to assign you, me, or a specific milestone. ;-)