Jump to content

Where is 800mhz?

RAvirani
 Share

Recommended Posts

WiWavelength Member Level: LTE Advanced

WiWavelength

Posted
Posted

So like -90 3G would be -90 LTE?

 

Nope.  Subtract about 20.

 

http://s4gru.com/index.php?/blog/1/entry-308-rssi-vs-rsrp-a-brief-lte-signal-strength-primer/

 

AJ

  • Like 1
Link to comment
Share on other sites
creamy1973 Member Level: Morse Code

creamy1973

Posted
Posted

So I've been traveling around the US a lot lately and I have yet to pick up a B26 signal and I was wondering if anyone had a list of markets in which sprint has started to or finished deploying 800mhz LTE because I haven't seen any.

B26 is all over in South Carolina.  Its just ok.  I lose LTE quite a bit.  Hoping they beef it up more.  

Link to comment
Share on other sites
jeffcarp Member Level: 3G EVDO

jeffcarp

Posted
Posted

I've been traveling around various cities in Texas and getting 800 quite often but typically was poor results. Here is what SignalCheck shows. In this case I had no data to speak of. Google Maps couldn't even populate its traffic layer. I've also seen it say LTE 800 in SignalCheck also with mixed results as to whether I have data or not. uploadfromtaptalk1437277238428.png

 

Sent from my 0PJA2 using Tapatalk

Link to comment
Share on other sites
anthony.spina97 Member Level: 4G WiMax

anthony.spina97

Posted
Posted

I've been traveling around various cities in Texas and getting 800 quite often but typically was poor results. Here is what SignalCheck shows. In this case I had no data to speak of. Google Maps couldn't even populate its traffic layer. I've also seen it say LTE 800 in SignalCheck also with mixed results as to whether I have data or not. attachicon.gifScreenshot_2015-07-18-11-25-46.png

 

Sent from my 0PJA2 using Tapatalk

Well that screenshot is only showing 1x800, so it doesn't surprise me that you have "no data to speak of". 1x800 is only made for voice, text, and the smallest amounts of data. It's not a reliable internet connection. What device are you using?

 

-Anthony

Link to comment
Share on other sites
jeffcarp Member Level: 3G EVDO

jeffcarp

Posted
Posted

It's the HTC One M9. As strong as that signal was I guess I thought it would at least support the data for Google Maps traffic layer. This is not my area of expertise. Are you saying that I don't even have a 3G connection in that circumstance?

 

Sent from my 0PJA2 using Tapatalk

Link to comment
Share on other sites
anthony.spina97 Member Level: 4G WiMax

anthony.spina97

Posted
Posted

It's the HTC One M9. As strong as that signal was I guess I thought it would at least support the data for Google Maps traffic layer. This is not my area of expertise. Are you saying that I don't even have a 3G connection in that circumstance?

 

Sent from my 0PJA2 using Tapatalk

If we're talking technical terms, having a 1x800 connection is *technically* 3G. But as marketed by Sprint, 1x800 is what they call "2G". When you are connected to EV-DO or eHRPD, you have what they market as "3G". So to answer your question, in a technical sense, yes you do have 3G. But in the average-Joe sense, no, you don't.

 

-Anthony

Link to comment
Share on other sites
RAvirani Member Level: LTE Advanced

RAvirani

Posted
  • Author
Posted

Ok so no device issues it turns out and I have updated my PRL but still nothing. It's probably a faulty device. My contract is up in August/September so I'll upgrade to an iPhone 6S and hopefully that will be better because I don't really want to replace my current phone considering I will only have it for another 1-2 months. Thanks for all of ur help guys!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 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...