SignalCheck Known Issues

SignalCheck  |  Help / FAQ  |  Change Log  |  To-Do List

Known Issues

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.

Android-Specific Issues

  • 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.
  • 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 has been filed.  Once it is added to the Android framework, it will be added to SignalCheck.
  • 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 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.  This is a documented bug in Android.  The icons will display properly in the status bar.
  • 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 Reset Mobile Connection feature will not work on non-rooted devices running Android 4.2 or newer.  This is because Google removed developer access to control the radio in Android 4.2.  A request to reverse this has been filed.

Device-Specific Issues

  • 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