Cell Info Plugin
🚧 Work in progress! 🚧
Lightweight Android library that is build over Telephony SDK. NetMonster core is extracted from NetMonster application and backports several Telephony features to older Android devices.
Why use NetMonster Core instead of legacy API?
Here's small comparison for each of voice / data network you can meet.
function | Min SDK Android | Min SDK NetMonster Core |
---|---|---|
CGI | - | I (14) |
NCC | - | N (24) |
BCC | - | N (24) |
Band | - | N (24) |
TA | O (26) | N (24) |
function | Min SDK Android | Min SDK NetMonster Core |
---|---|---|
CGI | - | I (14) |
CID (16b) | - | I (14) |
RNC | - | I (14) |
Ec/Io | - | M (23) |
Band | - | N (24) |
BER | - | Q (29) |
Ec/No | - | Q (29) |
RSCP | - | Q (29) |
function | Min SDK Android | Min SDK NetMonster Core |
---|---|---|
eCGI | - | I (14) |
CID (8b) | - | I (14) |
eNb | - | I (14) |
RSSI | Q (29) | I (14) |
RSRP | O (26) | I (14) |
CQI | O (26) | I (14) |
SNR | O (26) | I (14) |
TA | O (26) | I (14) |
Band | - | N (24) |
There are basically two ways you can use this library - as a validation library that will sanitize
data from AOSP cause lots of manufacturers modify source code and do not follow public documentation.
In that case you'll only need ITelephonyManagerCompat
to retrieve AOSP-like models that are properly
validated.
The second option is to use advantages of additional postprocessing of NetMonster Core. As a result you'll get more data but correctness is not 100 % guaranteed.
NetMonster Core focuses on mapping of two AOSP's ways to fetch current cell information:
Note that some of those methods are deprecated or even removed from AOSP - for more info see documentation of each method.
In this case you'll need to interact with INetMonster
class. Here's list of problems
that this library solves.
Issue:
Solution:
Issue:
Solution:
Using getNetworkType(vararg detectors: INetworkDetector)
you can specify which INetworkDetector
to use
when detecting current network type.
Credit to - eslamfaisal