These are elements within SignalCheck which are known to not work as well as they should, but the cause is out of our hands at the moment; Google or a device manufacturer will need to fix the issue. This list is broken down into general problems with the Android operating system and problems with specific devices.
- The 1X SID/NID/BID/BSL values do not update while on a telephone call. This is a documented bug in Android. SignalCheck will hide these values while a call is active to prevent inaccurate data from being displayed. SignalCheck will not adjust the Sprint 1X 800 status during a call, which, in certain circumstances, may cause this status to be inaccurate until the call is terminated.
- Pro version only: The BSL field may stop displaying addresses. If this occurs, and you have a working data connection, reboot your device to solve the problem. This is a documented bug in Android.
- Pro version only: The Reset Mobile Connection feature may reset the Bluetooth connection. If you experience this problem, rebooting your device once after attempting to use the Reset feature should permanently solve the problem. This is a documented bug in Android.
- Pro version only: The icons that display a combination of the network type and the signal strength will NOT display the signal strength part of the icon in the pulldown menu prior to Android 7 (when this bug was fixed). The icons will display properly in the status bar.
- Pro version only: The Reset Mobile Connection feature will not work on non-rooted devices running Android 4.2 or newer. This is because developer access to control the radio was removed in Android 4.2. A request to reverse this was been filed but closed by Android without action.
- DC-HSPA+ networks are not recognized by SignalCheck. This is because current versions of Android do not identify DC-HSPA+ networks. A request to add this feature was filed but essentially closed by Android without action. With the proliferation of LTE, it is unlikely that this will change.
T-Mobile has two vendors contracted to maintain their US wireless sites, and each vendor is responsible for two regions of the country. SignalCheck Pro is able to identify which region a site is in (it’s based on the TAC). BLC recently learned that each vendor configures its sites differently.
In the South and Central regions, the last two characters of the GCI indicate the LTE band. SignalCheck uses this information to indicate a band when connected to sites here. (This is how previous versions of the app worked).
On the East Coast and most of the West (Arizona, Oregon, and Washington are the exceptions), it is inconsistent. Instead of configuring the GCIs to indicate a specific band, they are issued in the order that a site is built out. So while many sites *might* share the same band/GCI correlation, it is just by chance, and there is no way to know which sites are configured in which manner. So, in the interest of accuracy, the app will not “guess” the band when connected to a site in one of those inconsistent regions.
From version 4.43 onward, if a device is reporting a valid LTE EARFCN (available on Android 7+), it will use that to calculate the band regardless of region (or provider, for that matter). Most devices are compatible; the glaring exception are most Samsung models. BLC has reached out to Samsung’s developer group but the company has not committed to a resolution yet.
Until version 4.43, thousands of SignalCheck users have been seeing T-Mobile band information that is incorrect but because of the app’s strong reputation, they trust it. That is very difficult for BLC to think about, and impossible to accept. SignalCheck’s reputation for accuracy must remain a priority.
- Most Samsung devices running Android 7+ (Nougat) do not report any LTE EARFCN information without root access. BLC has reached out to Samsung’s developer group but the company has not committed to a resolution yet.
- Most (all?) Huawei devices do not report signal information to the Android OS, therefore SignalCheck (and other similar apps) cannot obtain any useful data. Please feel free to submit diagnostic reports from within the app (About > Send Diagnostics) and include an e-mail address, perhaps some valid data may appear in future device updates.
- In addition to the information below, many Samsung devices display an invalid LTE PLMN (MCC-MNC) of 3100, 31000, or 310000. These values are incorrect, however this is what is being reported by the device to Android. UPDATE: Samsung has released an app that resolves this issue for some users. It is available on Google Play by clicking on this link or searching for “Samsung Refresh Customization” on Google Play.
|Device||Mobile Provider||Stock Android Version(s)||LTE GCI/PCI||LTE PLMN||Other Problems|
|HTC Droid DNA||Verizon||4.2.2||No||Invalid|
|HTC EVO LTE||Sprint||Up to 4.1.2||GCI Only||Ok|
|HTC EVO LTE||Sprint||4.3||Yes||Ok||No WiFi Channel|
|HTC One (M7)||Google Play Edition||4.4||No||Ok|
|HTC One (M7)||Sprint||Up to 4.3||Yes||Ok|
|HTC One (M7)||Sprint||4.4.2||Yes||Ok|
|HTC One (M8)||Sprint||4.4.2||Yes||Occasionally wrong|
|LG G2||Sprint||Up to 4.4.2||Yes||Occasionally wrong|
|LG/Google Nexus 5||All||Up to 4.4.4||Yes||Ok||No SNR or CQI|
|Samsung Galaxy Nexus||Sprint||Up to 4.3||No||Ok|
|Samsung Galaxy Note 2||Sprint||Up to 4.3||No||Ok|
|Samsung Galaxy Note 3||Verizon||Up to 4.3||No||Ok|
|Samsung Galaxy S3||Sprint||Up to 4.3||No||Ok|
|Samsung Galaxy S3||Sprint||4.4.2||GCI Only||Ok|
|Samsung Galaxy S3||Verizon||Up to 4.3||No||Ok|
|Samsung Galaxy S4||Verizon||Up to 4.3||No||Ok|
|Samsung Galaxy S4T||Sprint||Up to 4.3||No||Always reports 310120*See above for possible solution|
|Samsung Galaxy S4T||Sprint||4.4.2||Yes||Always reports 310120*See above for possible solution|
|Samsung Galaxy S5||Sprint||4.4.2||GCI Only||Always reports 310120*See above for possible solution|