Jump to content

Hello from Aberdeen MD!

sjkramer29

By sjkramer29
in Welcome

 Share

Recommended Posts

sjkramer29 Member Level: Smoke Signals

sjkramer29

Posted
Posted

Hello,

As a customer who recently came back to Sprint, and excited for Network Vision I found this site in a google search while trying to figure out why my iPhone 5 was dropping signal. When I started reading these forums.. I was blown away with the amount of Information and technical knowledge that is on this site.. it's good to interact with people who KNOW what their talking about.. 

 

This site is actually why I am still a Sprint customer (who didn't re-port back to Verizon), since I see firsthand what will be coming with the continued NV and LTE rollouts.

 

With that being said, I will be donating to this site ASAP.

 

Thanks again for your hard work.. and see you in the forums! .

 

-Scott

 

 

  • Like 2
Link to comment
Share on other sites
S4GRU Member Level: LTE Advanced

S4GRU

Posted
Posted

Welcome to S4GRU! Hope to see you around.

 

:welc:

 

Robert via Nexus 7 using Tapatalk 4 Beta

 

 

Link to comment
Share on other sites
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
    • CalebM
      SignalCheck Beta Crew Forum

      By CalebM · Posted

      Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • mikejeep
      SignalCheck Beta Crew Forum

      By mikejeep · Posted

      Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • mdob07
      SignalCheck Beta Crew Forum

      By mdob07 · Posted

      I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 

  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...