Jump to content

Everything 800mhz (1xA, LTE, coverage, timeline, etc)


Recommended Posts

 No actual acceptances (For the entire upstate ny market!) but it's definitely connecting, in the same way you described off of LTE. I hope we see something on the maps soon. 

This is not surprising at all.  We know 800 acceptance reports come in less frequently than other reports, it's been stated many times. 

  • Like 2
Link to comment
Share on other sites

My N5 is acting the same way down in Binghamton. No actual acceptances (For the entire upstate ny market!) but it's definitely connecting, in the same way you described off of LTE. I hope we see something on the maps soon. 

 

I have found some in Albany as well. Looking at the map you can see 800 acceptances coming in from the east and south... I suppose they could be coming this way :)

Link to comment
Share on other sites

Hope so! The 800 has been spotty for weeks, and eCSFB is definitely not functioning. So I really hope a full swath of 800 gets switched on this week with the necessary CSFB upgrades.

 

My guess is they've just been testing in our markets, hence nothing showing up on the maps in recent 800 acceptance reports. The 800 probably isn't ready to go public. I missed 3 calls today because my phone wouldn't switch off of LTE to answer them - getting peeved but waiting patiently. :-)

Link to comment
Share on other sites

Well i will just say that just because you have acceptances doesnt necessarily mean live and useable or connectable. Cause my market has some 800 cdma acceptances but ive never been able to pick it up at all and its my home site. Ive tried everything to try to be able to grab it but nothing so far. Just wanted to let you know this so that there is no dissapointment.

Link to comment
Share on other sites

Well i will just say that just because you have acceptances doesnt necessarily mean live and useable or connectable. Cause my market has some 800 cdma acceptances but ive never been able to pick it up at all and its my home site. Ive tried everything to try to be able to grab it but nothing so far. Just wanted to let you know this so that there is no dissapointment.

 

Guess I'll repeat this again. If you have a reliable 1X connection on 1900 MHz, your phone has no reason to switch to 800. It could be live in your area, but you just don't need it. It's not like EV-DO vs. LTE; 800 is not "better" than 1900. It will not switch when it discovers 800. In fact, the latest stock PRLs won't even look for 1X 800 if it connects to 1900. If you're losing a 1X 1900 signal when walking into a building, with no sign of any transition to 1X 800, then perhaps it's not live in your area.

 

You shouldn't necessarily be "disappointed" unless you're having trouble holding a 1X connection. The speed is the same and the voice quality is the same. The difference is 800 has increased signal coverage over 1900, which comes in most handy in buildings and previous dead spots. If you're maintaining a reliable PCS signal, you don't need it.

 

-Mike

Link to comment
Share on other sites

Guess I'll repeat this again. If you have a reliable 1X connection on 1900 MHz, your phone has no reason to switch to 800. It could be live in your area, but you just don't need it. It's not like EV-DO vs. LTE; 800 is not "better" than 1900. It will not switch when it discovers 800. In fact, the latest stock PRLs won't even look for 1X 800 if it connects to 1900. If you're losing a 1X 1900 signal when walking into a building, with no sign of any transition to 1X 800, then perhaps it's not live in your area.

 

You shouldn't necessarily be "disappointed" unless you're having trouble holding a 1X connection. The speed is the same and the voice quality is the same. The difference is 800 has increased signal coverage over 1900, which comes in most handy in buildings and previous dead spots. If you're maintaining a reliable PCS signal, you don't need it.

 

-Mike

You're absolutely right, EXCEPT in 1x1900 coverage areas which are somewhat fringy and where there is good 1x800 coverage. Whatever algorithm(s) Sprint is using to determine when to handoff are holding onto 1x1900 way too long. I live in one of the few parts of Chicagoland with an incomplete Sprint site (no 1x800, no LTE). With the previous PRL, I could force my GS3 to seek 1x800; with the latest one, I am basically stuck on 1900. I find myself in areas where I used to be able to call reliably and could always get and receive texts, but in which I no longer can do so. It is frustrating. Hopefully, Sprint and/or the phone vendors will correct his.

  • Like 1
Link to comment
Share on other sites

I'm not convinced that there is any hand off to 1X 800 from 1X 1900 or vice versa occurring yet anywhere during an active phone call.

 

Robert

  • Like 1
Link to comment
Share on other sites

I'm not convinced that there is any hand off to 1X 800 from 1X 1900 or vice versa occurring yet anywhere during an active phone call.

 

Robert

I have seen it occur in the middle of a call, switch from 1900 to 800 without an issue. I don't know why the network sees it fit to connect me to 1x800 even with a PCS signal in the -70's
Link to comment
Share on other sites

I have seen it occur in the middle of a call, switch from 1900 to 800 without an issue. I don't know why the network sees it fit to connect me to 1x800 even with a PCS signal in the -70's

 

If you are ever able to take video of it, I'd love to see it.  Thanks.

 

Robert

  • Like 1
Link to comment
Share on other sites

I'm not convinced that there is any hand off to 1X 800 from 1X 1900 or vice versa occurring yet anywhere during an active phone call.

 

I have always dropped the call when handed off between 1X 800 and 1X 1900 and assumed it was not possible, but others (I know nexgencpu already replied) pointed out they had no issues with it. Perhaps it's a market/vendor thing for now. It hasn't happened to me as often with my Nexus 5, but that's because it practically laughs at the notion of losing 1X 1900 anywhere.

 

It was more prevalent with my EVO LTE that was often hopping between PCS and SMR. I was usually using a sponsor PRL that prioritized 800 and camped on it; I would lose any call that moved out of range of live 800 sites, despite the fact that I would watch the phone immediately connect to 1900.

 

-Mike

  • Like 2
Link to comment
Share on other sites

You're absolutely right, EXCEPT in 1x1900 coverage areas which are somewhat fringy and where there is good 1x800 coverage. Whatever algorithm(s) Sprint is using to determine when to handoff are holding onto 1x1900 way too long. I live in one of the few parts of Chicagoland with an incomplete Sprint site (no 1x800, no LTE). With the previous PRL, I could force my GS3 to seek 1x800; with the latest one, I am basically stuck on 1900. I find myself in areas where I used to be able to call reliably and could always get and receive texts, but in which I no longer can do so. It is frustrating. Hopefully, Sprint and/or the phone vendors will correct his.

 

Agreed.. that's the one scenario I was trying to indicate would be a valid reason to generate "disappointment". I didn't mean to infer that a fringe 1900 signal should be considered reliable.

 

I'm not often in an area where my N5 has a weak 1X 1900 signal, other than going deep into some buildings. It does seem to switch when the PCS signal is lost, but you're absolutely right, it should transition to SMR before it gets to that point. It's like they need to adjust the threshold to connect to 800 a bit sooner.. if there is such an adjustment. I can't imagine the 1900 signal needs to be completely dropped before this could happen.

 

-Mike

  • Like 2
Link to comment
Share on other sites

Man the Nexus RF performance is ridiculously good!!! I just rode my elevator up and down (while holding it in a death-grip) and could not for the life of me get the PCS signal to go below -95dBm (whereas my HTC One would be in the 100's without the death-grip)... ill keep trying and get back to you guys.

 

 Looking forward to B26 stability like this! Would do wonders in pre-war buildings in NYC.

  • Like 1
Link to comment
Share on other sites

I'm not convinced that there is any hand off to 1X 800 from 1X 1900 or vice versa occurring yet anywhere during an active phone call.

 

Robert

Unfortunate choice of terms on my part. I didn't mean active hand off of calls, but rather changing frequencies while parked. The problem is that when a phone is idle, the Sprint network will tend to leave it parked on whichever frequency it is on (e.g., 1900) even when the alternate frequency is much stronger. And even when sending (or trying to receive) texts or initiating or receiving a call, Sprint loyally stays on the frequency. In "fringe" PCS coverage areas, this causes poor call quality, and failed and delayed texts. My point was that the method currently used by Sprint to change the parking frequency seems to hang on to 1900 even when signal quality falls below acceptable levels, when the phone should be "handed off" to 800. With current PRL 25018, for example, I can do nothing about this. With previous PRL 25017, I would force a PRL rescan, which would find 800 where available, and *poof* the connection problem was gone!

 

I'm sure there is a better term than handoff, but can't remember it.

Link to comment
Share on other sites

I have always dropped the call when handed off between 1X 800 and 1X 1900 and assumed it was not possible, but others (I know nexgencpu already replied) pointed out they had no issues with it. Perhaps it's a market/vendor thing for now. It hasn't happened to me as often with my Nexus 5, but that's because it practically laughs at the notion of losing 1X 1900 anywhere.

 

It was more prevalent with my EVO LTE that was often hopping between PCS and SMR. I was usually using a sponsor PRL that prioritized 800 and camped on it; I would lose any call that moved out of range of live 800 sites, despite the fact that I would watch the phone immediately connect to 1900.

 

-Mike

 

 

I'm using the sponsor PRL as well and I always seem to drop in areas where I might switch between 1x800 and 1x1900.  In particular, one tower near the kids' school shows as 3G/4G accepted for several months but I've never received LTE from that Site and the 3G speeds in the area are terrible.  Every other site in the area has LTE and most have 1x800 (although on the testing SID).  When I'm on a call and head to that area, when the farther away 1x800 sites drop out I lose the call every time.  And I have a hard time holding calls in a few spots on 1x1900 in that area too. 

 

Here's a thought, could it be that areas still on the testing SID are unable to handoff between the two bands, but ones that are officially accepted and on the right SID for the market are handling handoffs correctly?  No evidence one way or the other, just an idea.

Link to comment
Share on other sites

Here's a thought, could it be that areas still on the testing SID are unable to handoff between the two bands, but ones that are officially accepted and on the right SID for the market are handling handoffs correctly?  No evidence one way or the other, just an idea.

 

Plausible.

 

Robert

Link to comment
Share on other sites

I'm not convinced that there is any hand off to 1X 800 from 1X 1900 or vice versa occurring yet anywhere during an active phone call.

 

Robert

 

I've been able to handoff just fine between 1x 1900 and testing 1x 800 once the towers in my area started broadcasting correct neighbor sets.

 

EDIT: It's a normal hard handoff going between frequency bands just like it is when going between frequencies in the same band.

  • Like 1
Link to comment
Share on other sites

New FCC document posted regarding 800 and rebanding. 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2014/db0306/DA-14-306A1.pdf

 

 

Here's the companies/governments dragging their feet on their 800 rebanding efforts out west:

 

Region 3 (Arizona)
Arizona Public Service Company (Mar. 21, 2014)
City of Tucson (Apr. 21, 2014)
City of Mesa (Mar. 21, 2014)
City of Phoenix (Mar. 21, 2014)
City of Yuma (Apr. 11, 2014)
Gila River Indian Community (May 5, 2014)
Henry Zappia (May 30, 2014)

 

Region 5 (Southern California)
City of Los Angeles (Apr. 7, 2014)
Coachella Valley Water District (Mar. 31, 2014)
Eastern Riverside County Interoperable Communications Authority (ERICA) (May 16, 2014)
San Diego Gas and Electric Company (May 9, 2014)
San Diego Metropolitan Transit System (March 14, 2014)

 

Region 50 (Texas - El Paso Area)
City of El Paso (Mar. 31, 2014)

Region 53 (Southern Texas - San Antonio Area)
American Electric Power Service Company (Mar. 29, 2014)
City of Brownsville (May 11, 2014)
City of Harlingen (May 2, 2014)
City of Laredo (Apr. 21, 2014)
City of McAllen (May 26, 2104)
City of Rio Grande City (Mar. 14, 2014)
County of Cameron (May. 31, 2014)
County of Hidalgo (May 19, 2014)
Lower Rio Grande Valley Development Council (Apr. 7, 2014)

  • Like 9
Link to comment
Share on other sites

New FCC document posted regarding 800 and rebanding.

http://transition.fcc.gov/Daily_Releases/Daily_Business/2014/db0306/DA-14-306A1.pdf

 

 

Here's the companies/governments dragging their feet on their 800 rebanding efforts out west:

 

Region 3 (Arizona)

Arizona Public Service Company (Mar. 21, 2014)

City of Tucson (Apr. 21, 2014)

City of Mesa (Mar. 21, 2014)

City of Phoenix (Mar. 21, 2014)

City of Yuma (Apr. 11, 2014)

Gila River Indian Community (May 5, 2014)

Henry Zappia (May 30, 2014)

 

Region 5 (Southern California)

City of Los Angeles (Apr. 7, 2014)

Coachella Valley Water District (Mar. 31, 2014)

Eastern Riverside County Interoperable Communications Authority (ERICA) (May 16, 2014)

San Diego Gas and Electric Company (May 9, 2014)

San Diego Metropolitan Transit System (March 14, 2014)

 

Region 50 (Texas - El Paso Area)

City of El Paso (Mar. 31, 2014)

Region 53 (Southern Texas - San Antonio Area)

American Electric Power Service Company (Mar. 29, 2014)

City of Brownsville (May 11, 2014)

City of Harlingen (May 2, 2014)

City of Laredo (Apr. 21, 2014)

City of McAllen (May 26, 2104)

City of Rio Grande City (Mar. 14, 2014)

County of Cameron (May. 31, 2014)

County of Hidalgo (May 19, 2014)

Lower Rio Grande Valley Development Council (Apr. 7, 2014)

Sprint probably won't push too hard on the ones in the IBEZ since they can't use it right away anyway. But they won't let it drag on for too long.

 

Thanks for the update!

 

Robert via Samsung Note 8.0 using Tapatalk Pro

 

 

  • Like 4
Link to comment
Share on other sites

New FCC document posted regarding 800 and rebanding. 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2014/db0306/DA-14-306A1.pdf

 

 

Here's the companies/governments dragging their feet on their 800 rebanding efforts out west:

 

Region 3 (Arizona)

Arizona Public Service Company (Mar. 21, 2014)

City of Tucson (Apr. 21, 2014)

City of Mesa (Mar. 21, 2014)

City of Phoenix (Mar. 21, 2014)

City of Yuma (Apr. 11, 2014)

Gila River Indian Community (May 5, 2014)

Henry Zappia (May 30, 2014)

 

Region 5 (Southern California)

City of Los Angeles (Apr. 7, 2014)

Coachella Valley Water District (Mar. 31, 2014)

Eastern Riverside County Interoperable Communications Authority (ERICA) (May 16, 2014)

San Diego Gas and Electric Company (May 9, 2014)

San Diego Metropolitan Transit System (March 14, 2014)

 

Region 50 (Texas - El Paso Area)

City of El Paso (Mar. 31, 2014)

Region 53 (Southern Texas - San Antonio Area)

American Electric Power Service Company (Mar. 29, 2014)

City of Brownsville (May 11, 2014)

City of Harlingen (May 2, 2014)

City of Laredo (Apr. 21, 2014)

City of McAllen (May 26, 2104)

City of Rio Grande City (Mar. 14, 2014)

County of Cameron (May. 31, 2014)

County of Hidalgo (May 19, 2014)

Lower Rio Grande Valley Development Council (Apr. 7, 2014)

Both MTS and SDG&E in San Diego? aargh....   looks like it's time for me to start moonlighting at the public utilities commission and transit authority

Link to comment
Share on other sites

Ive tried to read up/keep up on this thread as best I can, but I cant seem to find any info about something that I recently noticed that had happened to me. On two separate occasions now my phone has fallen back to an "X" with no bars and reported "Searching for service" as opposed to having switched to 800, or even roaming. First time I was in a warehouse in Chatsworth CA at the corner of Nordhoff and De Soto. I noticed the signal drop to nothing, show an "X" and then after a minute it picked up 800 and signal check jingled me as such to let me know. It showed 3 bars in signal check on my notification bar, stayed for about 30 seconds, and then went back to the "X", with 800 never again to return until I left the area and normal 1900 had returned. The second time was yesterday at Universal Studios Hollywood inside of the Jurassic Café next to the Jurassic Park Ride. Same thing as last time, it fell back to no signal, 800 popped up for a minute, I sent a few texts out and receieved them also with it showing this time 5/6 bars in signal check before jumping back to the "X". I also now have a different GS4 than I did when I had noticed this the first time. Does my PRL just prioritize 1900 that much that it wont even accept 800 and stay with it?

Link to comment
Share on other sites

New FCC document posted regarding 800 and rebanding. 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2014/db0306/DA-14-306A1.pdf

 

 

Here's the companies/governments dragging their feet on their 800 rebanding efforts out west:

 

Region 3 (Arizona)

Arizona Public Service Company (Mar. 21, 2014)

City of Tucson (Apr. 21, 2014)

City of Mesa (Mar. 21, 2014)

City of Phoenix (Mar. 21, 2014)

City of Yuma (Apr. 11, 2014)

Gila River Indian Community (May 5, 2014)

Henry Zappia (May 30, 2014)

 

Region 5 (Southern California)

City of Los Angeles (Apr. 7, 2014)

Coachella Valley Water District (Mar. 31, 2014)

Eastern Riverside County Interoperable Communications Authority (ERICA) (May 16, 2014)

San Diego Gas and Electric Company (May 9, 2014)

San Diego Metropolitan Transit System (March 14, 2014)

 

Region 50 (Texas - El Paso Area)

City of El Paso (Mar. 31, 2014)

Region 53 (Southern Texas - San Antonio Area)

American Electric Power Service Company (Mar. 29, 2014)

City of Brownsville (May 11, 2014)

City of Harlingen (May 2, 2014)

City of Laredo (Apr. 21, 2014)

City of McAllen (May 26, 2104)

City of Rio Grande City (Mar. 14, 2014)

County of Cameron (May. 31, 2014)

County of Hidalgo (May 19, 2014)

Lower Rio Grande Valley Development Council (Apr. 7, 2014)

 

Appendix C – Joint Requests for Additional Time to Negotiate Costs with Sprint Corp.

 
Relief Granted: Extension to Complete Negotiations on or Before the Date Requested (indicated in 
parentheses).
 
Region 5 (Southern California) 
City of Irvine (Mar. 14, 2014)
 

Damn you, City of Irvine!!

 

Well... at least that date has passed. Let's hope the negotiations were fruitful.

Link to comment
Share on other sites

I'm using the sponsor PRL as well and I always seem to drop in areas where I might switch between 1x800 and 1x1900.  In particular, one tower near the kids' school shows as 3G/4G accepted for several months but I've never received LTE from that Site and the 3G speeds in the area are terrible.  Every other site in the area has LTE and most have 1x800 (although on the testing SID).  When I'm on a call and head to that area, when the farther away 1x800 sites drop out I lose the call every time.  And I have a hard time holding calls in a few spots on 1x1900 in that area too. 

 

Here's a thought, could it be that areas still on the testing SID are unable to handoff between the two bands, but ones that are officially accepted and on the right SID for the market are handling handoffs correctly?  No evidence one way or the other, just an idea.

I am in an accepted area and have yet to have an accepted handoff :/ always drops, but I know where it drops off usually so I avoid calls in those areas. Might just be the 513 prl causing issues because it wants to stick to 1x800 more
  • Like 1
Link to comment
Share on other sites

New FCC document posted regarding 800 and rebanding. 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2014/db0306/DA-14-306A1.pdf

 

 

Here's the companies/governments dragging their feet on their 800 rebanding efforts out west:

 

Region 3 (Arizona)

Arizona Public Service Company (Mar. 21, 2014)

City of Tucson (Apr. 21, 2014)

City of Mesa (Mar. 21, 2014)

City of Phoenix (Mar. 21, 2014)

City of Yuma (Apr. 11, 2014)

Gila River Indian Community (May 5, 2014)

Henry Zappia (May 30, 2014)

 

Region 5 (Southern California)

City of Los Angeles (Apr. 7, 2014)

Coachella Valley Water District (Mar. 31, 2014)

Eastern Riverside County Interoperable Communications Authority (ERICA) (May 16, 2014)

San Diego Gas and Electric Company (May 9, 2014)

San Diego Metropolitan Transit System (March 14, 2014)

 

Region 50 (Texas - El Paso Area)

City of El Paso (Mar. 31, 2014)

Region 53 (Southern Texas - San Antonio Area)

American Electric Power Service Company (Mar. 29, 2014)

City of Brownsville (May 11, 2014)

City of Harlingen (May 2, 2014)

City of Laredo (Apr. 21, 2014)

City of McAllen (May 26, 2104)

City of Rio Grande City (Mar. 14, 2014)

County of Cameron (May. 31, 2014)

County of Hidalgo (May 19, 2014)

Lower Rio Grande Valley Development Council (Apr. 7, 2014)

 

Wow I feel bad for the City of McAllen.  Will have to wait another century to finally get 800 MHz  :P .  So are these dates negotiated dates of when they will submit their 800 rebanding bids?  OMG this means that the US/Mexico IBEZ markets won't be getting 800 MHz for at least another 2-3 years.

  • Like 2
Link to comment
Share on other sites

New FCC document posted regarding 800 and rebanding. 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2014/db0306/DA-14-306A1.pdf

 

 

Here's the companies/governments dragging their feet on their 800 rebanding efforts out west:

 

Region 3 (Arizona)

Arizona Public Service Company (Mar. 21, 2014)

City of Tucson (Apr. 21, 2014)

City of Mesa (Mar. 21, 2014)

City of Phoenix (Mar. 21, 2014)

City of Yuma (Apr. 11, 2014)

Gila River Indian Community (May 5, 2014)

Henry Zappia (May 30, 2014)

 

Region 5 (Southern California)

City of Los Angeles (Apr. 7, 2014)

Coachella Valley Water District (Mar. 31, 2014)

Eastern Riverside County Interoperable Communications Authority (ERICA) (May 16, 2014)

San Diego Gas and Electric Company (May 9, 2014)

San Diego Metropolitan Transit System (March 14, 2014)

 

Region 50 (Texas - El Paso Area)

City of El Paso (Mar. 31, 2014)

Region 53 (Southern Texas - San Antonio Area)

American Electric Power Service Company (Mar. 29, 2014)

City of Brownsville (May 11, 2014)

City of Harlingen (May 2, 2014)

City of Laredo (Apr. 21, 2014)

City of McAllen (May 26, 2104)

City of Rio Grande City (Mar. 14, 2014)

County of Cameron (May. 31, 2014)

County of Hidalgo (May 19, 2014)

Lower Rio Grande Valley Development Council (Apr. 7, 2014)

So does that mean the issues in south Florida have been resolved? Or do we not have word on that just yet?

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.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Was at the Yankees vs Tigers game today and besides being a terrible day to have good seats, T-Mobile had great speeds via the stadium's DAS. I consistently saw 500-600Mbps on 5G and on LTE I got upwards of 200Mbps. I noticed that the stadiums DAS is broadcasting 140MHz n41 while macros that surround the stadium are at 80MHz. 
    • Throwed Roll Lambert's Cafe 
    • I've now seen how things work in Kobe, Hiroshima, and Osaka, as well as some areas south of Osaka (e.g. Wakayama, Kinokawa), and tried three more SIMs. The two physical SIMs (different branding for each) both use IIJ, which provides a Japanese IP address/routing on NTT, aleit LTE-only, so latency is ~45ms to Tokyo. The catch with NTT is that it uses two frequency bands (B42/3500 MHz LTE, n79/4900 MHz NR) that you're not going to get on an Android sold in the US, and I'm guessing that B42 would be helpful speed-wise on that network, as it doesn't have B41. I also found one place that doesn't have cell service: a vending machine in the back of the Osaka Castle tower. Or, rather, the B8/18/19 signal is weak enough there to be unusable. Going back to 5G for a moment, I saw a fair amount of Softbank n257 in Hiroshima, as well as in some train stations between Osaka and Kobe. 4x100 MHz bandwidth, anchored by B1/3/8, with speeds sometimes exceeding 400 Mbps on the US Mobile roaming eSIM. Not quite the speeds I've seen on mmW in the States, but I've probably been on mmW for more time over the past few days than I have in the US over the past year, so I'll take it. My fastest speed test was actually on SoftBank n77 though, with 100 MHz of that plus 10x10 B8 hitting ~700 Mbps down and ~80 Mbps up with ~100ms latency...on the roaming eSIM...on the 4th floor of the hotel near Shin-Kobe station. Guessing B8 was a DAS or small cell based on signal levels, and the n77 might have been (or was just a less-used sector of the site serving the train station). I'm now 99% sure that all three providers are running DSS on band 28, and I've seen 10x10 on similar frequencies from both NTT and SoftBank IIRC, on both LTE and 5G. I also picked up one more eSIM: my1010, which is different from 1010/csl used by US Mobile's eSIM unfortunately, as it's LTE-only. On the bright side, it's cheap (10GB/7 days is like $11, and 20GB for the same period would be around $15), and can use both KDDI and SoftBank LTE. It also egresses from Taiwan (Chunghwa Telecom), though latency isn't really any better than the Singapore based eSIMs. Tomorrow will include the most rural part of our journey, so we'll see how networks hold up there, and from tomorrow night on we'll be in Tokyo, so any further reports after that will be Tokyo-centric.
    • I think the push for them is adding US Mobile as a MVNO with a priority data plan.  Ultimately, making people more aware of priority would allow them (and other carriers) to differentiate themselves from MVNOs like Consumer Cellular that advertise the same coverage. n77 has dramatically reduced the need for priority service at Verizon where the mere functioning of your phone was in jeopardy a couple of years ago if you had a low priority plan like Red Pocket. Only have heard of problems with T-Mobile in parts of Los Angeles. AT&T fell in between. All had issues at large concerts and festivals, or sporting events if your carrier has no on-site rights. Edit: Dishes native 5g network has different issues: not enough sites, limited bandwidth. Higher priority would help a few. Truth is they can push phones to AT&T or T-Mobile.
  • Recently Browsing

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