For some reason captured .pcap files always empty. Is it so because of Android 10 instead of 9? I can drop my .qmdl log files if it will help to determine the issue.

Hello
Is it possible to modify the code to obtain possibility to install the application to older versions of Android? I have smartphones with Qualcomm and Android 5.0.1 or Android 7.0

Best regards
Michal

I can confirm that the app also works on OnePlus 8 Pro on Android 10.

https://github.com/RUB-SysSec/mobile_sentinel/blob/master/app/src/main/python/iodevices/fileio.py#L37

flake8 testing of https://github.com/RUB-SysSec/mobile_sentinel on Python 3.6.10

$ flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics

./app/src/main/python/iodevices/fileio.py:37:31: F821 undefined name 'write_buf'
            buf = util.unwrap(write_buf)
                              ^
./app/src/main/python/parsers/qualcomm/qualcommparser.py:281:5: F722 syntax error in forward annotation 'DIAG_LOG_F data without trailing CRC'
    def parse_diag_log(self, pkt: "DIAG_LOG_F data without trailing CRC", radio_id = 0):
    ^
./app/src/main/python/parsers/qualcomm/pycrate/pycrate_core/utils_py2.py:61:27: F821 undefined name 'long'
    integer_types = (int, long, _MPZ_T)
                          ^
./app/src/main/python/parsers/qualcomm/pycrate/pycrate_core/utils_py2.py:63:27: F821 undefined name 'long'
    integer_types = (int, long)
                          ^
./app/src/main/python/parsers/qualcomm/pycrate/pycrate_core/utils_py2.py:67:19: F821 undefined name 'unicode'
str_types = (str, unicode)
                  ^
1     F722 syntax error in forward annotation 'DIAG_LOG_F data without trailing CRC'
4     F821 undefined name 'write_buf'
5

https://flake8.pycqa.org/en/latest/user/error-codes.html

On the flake8 test selection, this PR does not focus on "style violations" (the majority of flake8 error codes that psf/black can autocorrect). Instead, these tests are focus on runtime safety and correctness:

• E9 tests are about Python syntax errors usually raised because flake8 can not build an Abstract Syntax Tree (AST). Often these issues are a sign of unused code or code that has not been ported to Python 3. These would be compile-time errors in a compiled language but in a dynamic language like Python, they result in the script halting/crashing on the user.
• F63 tests are usually about the confusion between identity and equality in Python. Use ==/!= to compare str, bytes, and int literals is the classic case. These are areas where a == b is True but a is b is False (or vice versa). Python >= 3.8 will raise SyntaxWarnings on these instances.
• F7 tests logic errors and syntax errors in type hints
• F82 tests are almost always undefined names which are usually a sign of a typo, missing imports, or code that has not been ported to Python 3. These also would be compile-time errors in a compiled language but in Python, a NameError is raised which will halt/crash the script on the user.

The app warned that there might be costs, but I didn't expect the call to Germany. It would be useful to state where the test number is so the user can make an informed decision about the costs before starting the test.

Hi,

When do you plan to release App for Android 10?

OnePlus 8 with Android 10 (rooted) does not detect device supports VoLTE.

Thanks

hi

i have a rooted galaxy s5 with android 9 which has (Qualcomm MSM8974AC Snapdragon 801 (28 nm) )but the app keeps crashing when sniffing and shuts-down after dialling 5 numbers when running detection.

https://www.gsmarena.com/compare.php3?idPhone1=6033&idPhone2=9769&idPhone3=9350

any ideas ?

Hello! I'm wondering about the determination of vulnerable eNodeB. Not quite sure that got that part right from the source code... So, the app makes short dials, records traffic, parses it... and what parameters point to the vulnerability? Is it if we recieve the same DRB ID twice?

https://github.com/RUB-SysSec/mobile_sentinel/blob/master/app/src/main/python/parsers/qualcomm/qualcommparser.py#L281

flake8 testing of https://github.com/RUB-SysSec/mobile_sentinel on Python 3.6.10

$ flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics

./app/src/main/python/iodevices/fileio.py:37:31: F821 undefined name 'write_buf'
            buf = util.unwrap(write_buf)
                              ^
./app/src/main/python/parsers/qualcomm/qualcommparser.py:281:5: F722 syntax error in forward annotation 'DIAG_LOG_F data without trailing CRC'
    def parse_diag_log(self, pkt: "DIAG_LOG_F data without trailing CRC", radio_id = 0):
    ^
./app/src/main/python/parsers/qualcomm/pycrate/pycrate_core/utils_py2.py:61:27: F821 undefined name 'long'
    integer_types = (int, long, _MPZ_T)
                          ^
./app/src/main/python/parsers/qualcomm/pycrate/pycrate_core/utils_py2.py:63:27: F821 undefined name 'long'
    integer_types = (int, long)
                          ^
./app/src/main/python/parsers/qualcomm/pycrate/pycrate_core/utils_py2.py:67:19: F821 undefined name 'unicode'
str_types = (str, unicode)
                  ^
1     F722 syntax error in forward annotation 'DIAG_LOG_F data without trailing CRC'
4     F821 undefined name 'write_buf'
5

https://flake8.pycqa.org/en/latest/user/error-codes.html

On the flake8 test selection, this PR does not focus on "style violations" (the majority of flake8 error codes that psf/black can autocorrect). Instead, these tests are focus on runtime safety and correctness:

• E9 tests are about Python syntax errors usually raised because flake8 can not build an Abstract Syntax Tree (AST). Often these issues are a sign of unused code or code that has not been ported to Python 3. These would be compile-time errors in a compiled language but in a dynamic language like Python, they result in the script halting/crashing on the user.
• F63 tests are usually about the confusion between identity and equality in Python. Use ==/!= to compare str, bytes, and int literals is the classic case. These are areas where a == b is True but a is b is False (or vice versa). Python >= 3.8 will raise SyntaxWarnings on these instances.
• F7 tests logic errors and syntax errors in type hints
• F82 tests are almost always undefined names which are usually a sign of a typo, missing imports, or code that has not been ported to Python 3. These also would be compile-time errors in a compiled language but in Python, a NameError is raised which will halt/crash the script on the user.

I have rooted the phone and installed the App. When I run the test, it gets 4 calls in to testing and the App crashes out. I have tried uninstalling and reinstalling again but same .

Pixel 3a XL (Qualcomm Snapdragon 670 chip)
Android 10 in developer mode
VoLTE network
SIM card: LTE voice and data
MobileSentinel 1.0

App doesn't detect IMSI (ICCID on this phone) and shows isVolteEnabled: False.
Changed Call Number to this phone.
Starting detection makes 4 calls and then gives up without logging anything.

The app crashes %10 thru the test

Android version 10