v0.1.14-alpha Bug Reports: Add your bugs here! about android-imsi-catcher-detector

[SecUpwN]

@xLaMbChOpSx, awesome work! Just a small comment on the initial About-Tab: Would you please transform the links (which are obviously not clickable yet) into buttons? Might be much better to navigate. I know the About-Tab is in its inital version, but please don't forget to integrate the rest of the stuff mentioned at Issue #17. THANKS! 👍 Edit: Just noticed your comment on completing it later. Nevermind!

Request for small UI enhancement: Please align the Details of "Device Information" with the "SIM Information" and "Network Information". In more clear words: Device Information "Type", "IMEI" and so on is set a little behind - please have a quick glance at the main menu to see what I mean. Just a nitpicky issue, feel free to think I'm crazy. ;-)

Also, can we switch the "Database Viewer"-Tab with the "Cell Information"-Tab? I think it's much more relevant to first see the neighbouring cells, than to analyze the database logs. Other than that, just a quick question into the room: Am I right to assume that the ciphering Indicator is just shown on Samsung-Devices yet? May I ask how it is shown or indicated to the users?

On AIMSICD-Persistancy: AIMSICD seems to just quit when clearing all opened Apps, even if the persistance-service is enabled. Would be cool if AIMSICD could really hook as deep as possible.

[E3V3A]

@SecUpwN He he! I was thinking the same thing (about the alignment), but was afraid to say anything, as I could come across as very ...you know. Anyway, I agree with all your comments.

Regarding the Ciphering indicator as shown on slide window. In all honesty, I have little frekkin clue to what it is actually telling us. I posted about it in the XDA thread, but never had any constructive response to my speculations. Thus that functionality is still purely speculation, but has something to do with the current enciphering status, which surely/probably depend on the current network you're connected to. (I started a new thread, to properly map out SM.)

What we would also need is the CI that is set in the SIM by your service provider.

This require us to use either:

(a) the AT command entry (my preferred way), as we had in the first versions or
(b) the internal SIM related API/IPC commands, for reading the SIM EF files.

@xLaMbChOpSx Would it be a problem to re-implement the AT command entry possibility as we had in the earlier versions? (Before I was able to test.) If so, we could use another slide page for this type of entry. I really promote the ATCoP entry, over the API stuff, because it give you complete and direct control without weirdness.

I know people probably think I'm a pain-in-the-.. for always talking obsessively about the AT access, but few people know that it allows for close-to full control of the Baseband, including completely reprogramming most RF-related main functions, as I have tried to document elsewhere.

@SecUpwN I forgot to mention that the persistence bug is an old one where the logic is reversed. Just check it and it will close down nicely.

[E3V3A]

@xLaMbChOpSx Just to clarify. When I said "promote" in the above comment, I really meant prioritize and not "replace". Obviously we need the API stuff, but the AT based results may be (but not always) both faster and more trustworthy.