Jump to content
mikejeep

SignalCheck - Android app to monitor your 2G/3G/4G LTE signal strengths

Recommended Posts

Mike, tried sending diagnostic, but said failed

 

Sent from my SM-G955U using Tapatalk

  • Like 2

Share this post


Link to post
Share on other sites

Mike, tried sending diagnostic, but said failed

 

I just tried as well and ran into the same issue.. I don't know what keeps happening. The app sends the data to a very simple script on my website, a script that I never touch. I have no idea why it keeps giving that odd "Temporary Redirect" error. I'm on it...

 

-Mike

  • Like 1

Share this post


Link to post
Share on other sites

I just tried as well and ran into the same issue.. I don't know what keeps happening. The app sends the data to a very simple script on my website, a script that I never touch. I have no idea why it keeps giving that odd "Temporary Redirect" error. I'm on it...

 

-Mike

Tried sending the CA diagnostic for you

 

Sent from my SM-G955U using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

Tried sending the CA diagnostic for you

 

Thanks. Keep trying; I just tried about a dozen times, and most of them went through. I am looking into it and intend to change the app itself to be more robust. Unfortunately the way it's configured now, the server doesn't give any technical details about why the report is failing like this.

 

EDIT: Should be resolved for now; I think the hosting server is just getting overloaded. Unfortunately I'm paid up for another 18 months and don't want to throw that away.. I will keep working on the app side to handle these issues better.

 

-Mike

Edited by mikejeep
  • Like 3

Share this post


Link to post
Share on other sites

Not yet by earfcn just by GCI and ALU 10x10 should end with 11/12/13. That is why ingenium first image shows 10x10. I also thought earfcn 8640 was 10x10.

 

Sprint does not always show 10x10 in GCI format depending on the market like Pittsburgh is not shown by GCI.

8640 is a 10x10 carrier

 

Sent from my SM-G950U using Tapatalk

Share this post


Link to post
Share on other sites

Mike,
I got excited when I thought they upgraded this small cell site to B41, but when I checked the engineering screen, it's still B25. I don't know if anyone had showed you this yet, but it's misidentifying it as B41. I took two screen shots because it's two different small cells at the same site. I haven't checked the two other small cell sites near me yet. da0e3a2038eeee29247f7af38c11fff5.jpg31804b1e6fb91ab7372e5fab8df59ff8.jpg

Sent from my SM-G935P using Tapatalk

  • Like 2

Share this post


Link to post
Share on other sites

hmmm, a 1900Mhz small cell. Photos would be great (place in another Shentel thread). 800Mhz was a known possibility. Overall B41 still the right way to go given the odds. Might need an override list option. Good find!

Share this post


Link to post
Share on other sites

hmmm, a 1900Mhz small cell. Photos would be great (place in another Shentel thread). 800Mhz was a known possibility. Overall B41 still the right way to go given the odds. Might need an override list option. Good find!

 

I think they've been around for some time. Before B41 small cells were considered for deployment.

Share this post


Link to post
Share on other sites

I think they've been around for some time. Before B41 small cells were considered for deployment.

You are correct. Before Softbank. Useful, but evolutionary dead ends.

 

Sent from my LG-LS980 using Tapatalk

Share this post


Link to post
Share on other sites

I posted this in the Nexus 5X thread but was told it might be bad data. Have you ever seen ATT band 25 reported? I'm no longer in that area (Somerset KY area if it's not in the screenshot), so I can't attempt to recreate it.

4ebdcfd06b7ac83e3aaf26cb16837f18.jpg

 

Sent from my Nexus 5X using Tapatalk

Share this post


Link to post
Share on other sites

I posted this in the Nexus 5X thread but was told it might be bad data. Have you ever seen ATT band 25 reported? I'm no longer in that area (Somerset KY area if it's not in the screenshot), so I can't attempt to recreate it.

4ebdcfd06b7ac83e3aaf26cb16837f18.jpg

 

Sent from my Nexus 5X using Tapatalk

We have seen AT&T implementing MFBI and broadcasting in the PCS G Block in select areas, the first more often that the latter, although this very well could be stale data. Did you have a chance to grab engineering screenshots?

Share this post


Link to post
Share on other sites

We have seen AT&T implementing MFBI and broadcasting in the PCS G Block in select areas, the first more often that the latter, although this very well could be stale data. Did you have a chance to grab engineering screenshots?

Unfortunately I didn't think to do that

 

Sent from my Nexus 5X using Tapatalk

Share this post


Link to post
Share on other sites

Unfortunately I didn't think to do that

 

Sent from my Nexus 5X using Tapatalk

Too bad...if you see this again then be sure to do so.

Share this post


Link to post
Share on other sites

Looking for a hand from my faithful followers.. Android has an online bug tracker that helps sort out issues with the OS. Users can "vote" for issues by giving them a 'star' which helps bring them to the attention of the important powers that be. If you haven't already, could you take a moment and 'star' the following Android bug reports to help work some of the glitches out that will make SignalCheck a better app? It only takes a moment.

 

Bug report for LTE neighbors not displaying in Android 7: https://issuetracker.google.com/issues/63848701

Bug report for invalid LTE EARFCN data with newer bands: https://issuetracker.google.com/issues/37136986

Request to add a method to obtain LTE bandwidth: https://issuetracker.google.com/issues/37132691

 

And for reading this far down, I will reward you with the good news that another SCP update is on the horizon.. testing should be done soon.

 

Thanks!

-Mike

 

  • Like 13

Share this post


Link to post
Share on other sites

Done.

 

Thanks again for your hard work!

 

Sent from my HTC U11 using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites

Starred

  • Like 1

Share this post


Link to post
Share on other sites

Done

  • Like 1

Share this post


Link to post
Share on other sites

Three stars from me, Thanks for your hard work Mike.

  • Like 1

Share this post


Link to post
Share on other sites

I starred the issues. Just wondering if you saw the bug I posted about a few days ago.

 

http://s4gru.com/index.php?/topic/3060-signalcheck-android-app-to-monitor-your-2g3g4g-lte-signal-strengths/?p=512380

 

Thanks! I did see that.. I've been thinking about it a lot, and hadn't come up with a great approach on how to address it so I hadn't replied yet. The problem is it's perfectly fitting the GCI pattern for B41 SC (even third character; characters 4-6 exceed 900; sector 01). This is the first B25 report I've seen, but I worry that it won't will be the last. So do I just display them all as small cells and eliminate the band designation? Or is this going to be a rare find?

 

-Mike

Share this post


Link to post
Share on other sites

Thanks! I did see that.. I've been thinking about it a lot, and hadn't come up with a great approach on how to address it so I hadn't replied yet. The problem is it's perfectly fitting the GCI pattern for B41 SC (even third character; characters 4-6 exceed 900; sector 01). This is the first B25 report I've seen, but I worry that it won't will be the last. So do I just display them all as small cells and eliminate the band designation? Or is this going to be a rare find?

 

-Mike

It's probably a rare find according to a conversation I had with another member. Apparent Shentel used some B25 small cells before B41 small cells became available. Maybe some others with knowledge can comment.

 

Sent from my SM-G935P using Tapatalk

  • Like 1

Share this post


Link to post
Share on other sites

Just pushed out an update to SignalCheck Pro, version 4.44.. everyone can grab it on Google Play here! It was more significant than I originally intended, but that's good for you guys.. here are the highlights:
 
NEW OPTIONS:

Display mobile connection IP address
When the app is in the foreground and the mobile data connection (not Wi-Fi) is active, you will see your external IP address displayed. PLEASE NOTE: This feature uses data. It pings my server which simply responds with your external IP -- nothing is captured, logged, or saved at all. It is only a small amount of data (literally, the response is just your IP in plain text), but it will happen every time your mobile signal changes. I do not expect it to be a significant amount of data, but for an app that really doesn't use data, this is something worth pointing out. When the app is not in the foreground, you are on Wi-Fi, or this option is disabled (as it is by default), nothing is displayed and no data is used.
 
Display Reset Mobile Connection button on the action bar
You can now show the button on the main screen, action bar, both, or neither.
 
Hide CDMA 1X display when connected to LTE
If you're a big fan of neighbor cells, this should give you more screen real estate. This only changes the main screen display; logs will still record GCI and any notification icons will still reflect a 1X connection if present.

Display LTE ECI (decimal) instead of GCI (hex)
Somebody asked for it a long time ago. This only changes the main screen display; logs will still record GCI.

 
NOTABLE NEW FEATURES:

Added feature to add current location to a site note
When editing a site note, you will see a new button "HERE" that will fill the prompt with your current location if you have the app's Location Service enabled. If "HERE" is grayed out, the app didn't have your location coordinates at the time you opened the prompt. If you decide you don't want to use the address that pops up, simply cancel the prompt and your previous note will remain in place.
 
Improved diagnostic reports; failed reports will now be saved and can be manually resubmitted from the Send Diagnostics screen
If you try to send diagnostics but your connection (or my server) is unavailable, the report will be saved on your device. It will be attempted again when you send another report, or if you select the "Send Saved" option from the diagnostic report screen. Should be very helpful to those of you who do testing with deactivated devices.

Changed provider to indicate if CDMA 1X connection is a Sprint Airave or 800 SMR
This helps make CDMA logs a bit more useful, and brings CDMA logging more in line with how LTE providers are logged.
 
Added donation link to About screen
Those of you who have asked for it, you can now throw me a few extra bucks if you're feeling generous. You will get nothing in return other than knowing you made my day and motivated further development! Thank you!
 

 
BUG FIXES AND LESS-EXCITING STUFF:

  • Added indicators for some Sprint LTE band 25 oDAS cells.
  • Added notification icons for LTE bands outside of North America.
  • Resolved force closes at startup in certain situations.
  • Resolved force closes when requested permissions are not immediately granted on Android 6+.
  • Resolved issue with connection titles overlapping signal meters.
  • Resolved issue with geocoder features not working.
  • Resolved issue with LTE 1900 notification icons missing.
  • Resolved issue with LTE band conflicts between native EARFCN and GCI-calculated band.
  • Resolved issue with LTE frequency title not updating properly in certain situations.
  • Resolved issue with misidentified Sprint LTE band 25 10×10 sites in certain areas.
  • Resolved issue with unreliable CDMA 1X BSL and Site Note displayed in the notification pulldown when a call is in progress.

 

A *long* overdue update to SignalCheck Lite is finally on the horizon as well, it will bring the free version up to speed with all relevant features and fixes to date.

 

As always, feedback is welcomed and my sincerest thanks to everyone for their support. And to my Beta Crew for being a huge help!
 
-Mike

  • Like 10

Share this post


Link to post
Share on other sites

Just pushed out an update to SignalCheck Pro, version 4.44.. everyone can grab it on Google Play here! It was more significant than I originally intended, but that's good for you guys.. here are the highlights:

 

NEW OPTIONS:

 

Display mobile connection IP address

When the app is in the foreground and the mobile data connection (not Wi-Fi) is active, you will see your external IP address displayed. PLEASE NOTE: This feature uses data. It pings my server which simply responds with your external IP -- nothing is captured, logged, or saved at all. It is only a small amount of data (literally, the response is just your IP in plain text), but it will happen every time your mobile signal changes. I do not expect it to be a significant amount of data, but for an app that really doesn't use data, this is something worth pointing out. When the app is not in the foreground, you are on Wi-Fi, or this option is disabled (as it is by default), nothing is displayed and no data is used.

 

Display Reset Mobile Connection button on the action bar

You can now show the button on the main screen, action bar, both, or neither.

 

Hide CDMA 1X display when connected to LTE

If you're a big fan of neighbor cells, this should give you more screen real estate. This only changes the main screen display; logs will still record GCI and any notification icons will still reflect a 1X connection if present.

 

Display LTE ECI (decimal) instead of GCI (hex)

Somebody asked for it a long time ago. This only changes the main screen display; logs will still record GCI.

 

 

NOTABLE NEW FEATURES:

 

Added feature to add current location to a site note

When editing a site note, you will see a new button "HERE" that will fill the prompt with your current location if you have the app's Location Service enabled. If "HERE" is grayed out, the app didn't have your location coordinates at the time you opened the prompt. If you decide you don't want to use the address that pops up, simply cancel the prompt and your previous note will remain in place.

 

Improved diagnostic reports; failed reports will now be saved and can be manually resubmitted from the Send Diagnostics screen

If you try to send diagnostics but your connection (or my server) is unavailable, the report will be saved on your device. It will be attempted again when you send another report, or if you select the "Send Saved" option from the diagnostic report screen. Should be very helpful to those of you who do testing with deactivated devices.

 

Changed provider to indicate if CDMA 1X connection is a Sprint Airave or 800 SMR

This helps make CDMA logs a bit more useful, and brings CDMA logging more in line with how LTE providers are logged.

 

Added donation link to About screen

Those of you who have asked for it, you can now throw me a few extra bucks if you're feeling generous. You will get nothing in return other than knowing you made my day and motivated further development! Thank you!

 

 

BUG FIXES AND LESS-EXCITING STUFF:

  • Added indicators for some Sprint LTE band 25 oDAS cells.
  • Added notification icons for LTE bands outside of North America.
  • Resolved force closes at startup in certain situations.
  • Resolved force closes when requested permissions are not immediately granted on Android 6+.
  • Resolved issue with connection titles overlapping signal meters.
  • Resolved issue with geocoder features not working.
  • Resolved issue with LTE 1900 notification icons missing.
  • Resolved issue with LTE band conflicts between native EARFCN and GCI-calculated band.
  • Resolved issue with LTE frequency title not updating properly in certain situations.
  • Resolved issue with misidentified Sprint LTE band 25 10×10 sites in certain areas.
  • Resolved issue with unreliable CDMA 1X BSL and Site Note displayed in the notification pulldown when a call is in progress.

A *long* overdue update to SignalCheck Lite is finally on the horizon as well, it will bring the free version up to speed with all relevant features and fixes to date.

 

As always, feedback is welcomed and my sincerest thanks to everyone for their support. And to my Beta Crew for being a huge help!

 

-Mike

Mike, found a bug, I'm on the main network but my 1x says I'm on my Airave 3. Would you like a diagnostic? b4ce392af2afd023ad98bf9ca341bfe3.jpg

 

Sent from my SM-G955U using Tapatalk

Share this post


Link to post
Share on other sites

ive enabled mobile IP address display but it will not show on the nexus 5X.  weird.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • TAPATALK VERSION
    BACK ONLINE

  • PROGRESSIVE RAFFLE
    FOR AN iPHONE 8

    iphonexiphone8.jpg

    WHICH CAN PROGRESS TO AN iPHONE 8+ OR AN iPHONE X
    **or an Android device of equal or lesser value**

    CLICK HERE FOR MORE DETAILS

  • gallery_1_23_9202.png

  • Similar Content

    • By danlodish345
      hey guys i am due for a upgrade today....i am curious on the opinions of others of what phone is a great phone... any opinions are welcome !
    • By jakeuten
      Just a bit of insight. I live near UMD in Duluth, MN. Sprint's signal is clearly much 'dirtier' with a 1.0 SNR compared to T-Mobile's 20.4 SNR. I don't have a screenshot from the same time, but I get about a 22 to 29 SNR with T. I know that AT&T uses RRU's but I'm not too sure about Sprint or T-Mobile. Also, I didn't even know they had L2500 where I live, but I force checked it on my Samsung S7 (AT&T). 


    • By danlodish345
      hey guys i m curious what you guys think about rooting phones and the positives and negatives about it.... let the discussion begin!
    • By MarshieZballer
      Karma Go Hotspot Discussion & User Thread

      Since we don't have an official spot for this little hotspot, I'd like to make one... meet the Karma Go hotspot. Running off the Sprint LTE network, the Go is a Spark/LTE Enhanced enabled, tri-band hotspot.
       
      Currently it runs for $149. Down below in post #2 you'll find all the information that I've compiled about Go.
       
      For anyone who has never heard of Karma, check out the Karma Go. 
          If you'd like to purchase the Karma, PM me and I can give you my referral code for an extra $10 off your purchase!
      Be sure to watch for sales to get the Go at $99 and if you add my code in, $89! 
       
       
      Current Sale(s):
       
      Not at this time... Check back soon!
    • By S4GRU
      Did you know that with many Sprint (Uniband) LTE Android devices, the signal strength indicator at the top does not show your LTE signal strength? Even if 4G or LTE is displayed next to it?
       
      That's right!  This signal displayed here is your 1x (voice signal), and it is not your 3G EVDO signal strength, nor your LTE signal strength.  Regardless of whether it says 3G or 4G next to it. This is the cause of a lot of confusion.  Also, third party apps like NetMonitor do not show accurate LTE signal strengths. They also only show the 1x signal strength, even though they may reference being connected to LTE.
      The purpose of this thread is to help educate the masses, because many people think they have a strong LTE signal, when in fact they do not. And then they are unhappy, thinking that Sprint LTE is really slow, even with a strong signal. LTE performance is very signal strength dependent. So, when you have a weak signal, you can expect much slower than peak results.
       
      There is only one accurate way to get your LTE signal strength, and that is from your LTE Engineering screen in your Debug menu. And we will discuss the different ways to get that below.
       
      ...In HTC, Motorola & LG Sprint LTE devices:
      Go in to your phone app, and dial ##DEBUG# Select LTE Engineering Go down to RSRP. The number under RSRP shown in dBm is your LTE signal strength. ...In Samsung Sprint LTE devices:
      Go in to your phone app, and dial ##DEBUG# Enter 777468 for your lock code Select LTE Engineering Go down to RSRP. The number next to RSRP shown in dBm is your LTE signal strength. ...In the Galaxy Nexus, Nexus 5:
      Go in to your phone app, and dial *#*#DEBUG#*#* Enter 777468 for your lock code Select LTE Engineering Go down to RSRP. The number next to RSRP shown in dBm is your LTE signal strength. The LTE Signal Strength Scale:
       
      Now you have determined your actual LTE signal strength in dBms your device is receiving, you can use the following scale below to determine its strength:
      Better than -88dBm RSRP is a strong signal Between -89dBm and -96dBm is a very good signal Between -97dBm and -105dBm is good Between -106dBm and -112dBm is fair Worse than -113dBm RSRP is poor Feel free to link people to this thread for explanation. Hopefully, this will clear up some confusion out there!
       
       
  • Posts

  • Recently Browsing

    No registered users viewing this page.

×