Jump to content

Two Sites supposedly live with CDMA 800 in Rural Chicago Market


S4GRU

Recommended Posts

ATTENTION S4GRU MEMBERS! WE HAVE A LIVE ONE...err, two!

 

I was going through my latest list of live NV sites, and I came across two sites labeled with CDMA 800. All the NV completed sites to date have been labeled CDMA 1900 or LTE 1900. Does this mean that the 1xAdvanced carrier is active on Channel 476 on these two sites? It looks like it!

 

If you are in the Chicago area, have a 800 SMR capable device and have the skills to install our 800 CDMA PRL, then please drive out to the Rochelle/De Kalb area and try to connect to these 800MHz CDMA sites on Channel 476. This is some crazy exciting stuff for the wireless nerd!

 

If you are going to give it a try, let me know before you head out there. The suspense is killing me. See the map of the site locations in question below.

 

Robert

 

 

gallery_1_1_83728.jpgClick Map to Enlarge

  • Like 7
Link to comment
Share on other sites

I live in Yorkville and my dad lives in Waterman. I can test but Im not sure what device is required. I have a Epic Touch and OG Epic. I have installed custom prl's on the touch a few times, but Im unsure It either of these devices are able to get on 800. Let me know If I can and I will post my results when I can get out by Waterman. Also in Yorkville we have been having many dropped calls, duplicate/late text, time changing to a hour ahead. Do you know what is going on in my area this last month? I know they have lost quite a few costumers because of this. Is you list of live NV sites public? If so where can I view this at?

Link to comment
Share on other sites

Thought someone in LA already connected his EVO3d to an 800 1xa carrier?

 

We did get a report. Was likely testing, since these two sites are the first ones to show live in the Sprint system.

 

Interesting, i thought they couldn't deploy 800 if iDEN was active, and that is definitely in iDEN area.

 

Sort of. They cannot deploy 800 CDMA on Channel 476 until enough iDEN channels have been cleared out of the way for it to be used. It appears that Sprint is removing some iDEN carriers this year, just enough to deploy 800 CDMA on Channel 476 in most markets. This will substantially improve voice coverage in advance of full iDEN decommissioning.

 

Im in Maryland and I connected to a nv site and using the test prl I was on channel 476. is this 800 mhz?

 

Please post a screen shot of your Debug screen the next time you connect. Would love to see some verification of 800 CDMA live in your area. Thanks!

 

Robert

  • Like 1
Link to comment
Share on other sites

Will the Galaxy Nexus be able to use 800 CDMA?

 

Yes. Once the PRL is updated in the future to run on it. Or you download ours.

 

Robert

Link to comment
Share on other sites

 

 

Sort of. They cannot deploy 800 CDMA on Channel 476 until enough iDEN channels have been cleared out of the way for it to be used. It appears that Sprint is removing some iDEN carriers this year, just enough to deploy 800 CDMA on Channel 476 in most markets. This will substantially improve voice coverage in advance of full iDEN decommissioning.

 

 

Robert

 

If there any plan that lists where this will be done, or do we just have to wait for them to complete the sites?

Link to comment
Share on other sites

If there any plan that lists where this will be done, or do we just have to wait for them to complete the sites?

 

I'm in waiting mode. I have not seen any plans of this occurring, only evidence of it.

 

Robert

Link to comment
Share on other sites

So it should be available in the next 12 months, or so?

 

Sooner. I believe they will push a PRL that will run on 800 CDMA in the near future.

 

Robert

Link to comment
Share on other sites

##DEBUG# in your phone dialer. Does not work with some custom ROMs, like anything from Cyanogen. Most devices, you will need your MSL #.

 

Robert

Link to comment
Share on other sites

##DEBUG# in your phone dialer. Does not work with some custom ROMs, like anything from Cyanogen. Most devices, you will need your MSL #.

 

Robert

 

Thanks.

Link to comment
Share on other sites

We did get a report. Was likely testing, since these two sites are the first ones to show live in the Sprint system.

 

Sort of. They cannot deploy 800 CDMA on Channel 476 until enough iDEN channels have been cleared out of the way for it to be used. It appears that Sprint is removing some iDEN carriers this year, just enough to deploy 800 CDMA on Channel 476 in most markets. This will substantially improve voice coverage in advance of full iDEN decommissioning.

 

Please post a screen shot of your Debug screen the next time you connect. Would love to see some verification of 800 CDMA live in your area. Thanks!

 

Robert

I have a screen shot.

 

gallery_1_1_17694.jpg

  • Like 1
Link to comment
Share on other sites

I have a screen shot.

 

 

Thanks for the screenshot. Of note, it is coming up SID 22429, which is allocated to Idaho/Utah/Western Wyoming. It should be 22435, according to this. It looks like Sprint has made some modifications to the SID list. Or maybe there is an error in the programming of the carrier? Cool stuff.

 

Robert

Link to comment
Share on other sites

I have a screen shot.

 

gallery_1_1_17694.jpg

 

 

SO 33 is 1xRTT-- your phone must not support RC11/RC8 (1xAdvanced). At least it should work fine. I'm a little disappointed with the -84 dBm signal... you're either a good 2 miles from that tower or there's alot of downtilt (as I would expect in a dense urban environment). In Maryland, your SID should be 22435. Locking onto the SID you have, I would expect your 3G (EVDO) to be lost since I'm sure the ACQ records don't match! I can remod the PRL to use the 22429 SID in your area with its native EV carriers. 22429 should be Salt Lake City market.

  • Like 2
Link to comment
Share on other sites

SO 33 is 1xRTT-- your phone must not support RC11/RC8 (1xAdvanced). At least it should work fine. I'm a little disappointed with the -84 dBm signal... you're either a good 2 miles from that tower or there's alot of downtilt (as I would expect in a dense urban environment).

 

I would not worry about that -84 dBm RSSI. But look at that -3.0 dB Ec/Io. That is stellar -- no doubt, a completely unloaded carrier. Even with a strong signal, typical Ec/Io in a moderately loaded cell is roughly -7 dB.

 

AJ

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

  • Posts

    • The S21U was very spotty with connecting to 6E. It would only see it on a router reboot. I thought it was more the router than the S21U, however my laptop would solidly connect to the 6E network, so it must have been the S21U. Since I'm on WiFi7 with the S24U, I haven't kept track of it. I will flip over and check it out later. 
    • Wi-fi 6e missing (6 GHz on one of two ultras). Perhaps coming from an app?  Wifi analyzer can see the 6ghz, just can't see them to connect.  May try wifi reset, although communications reset could have been the source of this problem.  Others have reported it, so not an isolated issue. Edit: Fixed: Rebooted into safe mode. Wifi 6e worked. Normal boot back. No wifi 6e in available nerworks.  Unistalled Asus Router app. Checked for Wifi 6e being visible in wifi available networks. Nothing. Deleted Netgear Genie app. Then saw networks. of mine I had not connected to in wifi available networks. Forgot the desired 2.4&5&6 SSID that did not show 6E. Connected to it again. 6e now works.
    • I noticed today while I was out and about in Louisville that b30 has been widened back to 10x10. They reduced it to 5x5 back in Sept 2018 presumably due to satellite radio interference. Not sure how long ago the change happened but it couldn't have been too terribly long ago. I noticed the different earfcn in the neighbor list, I don't usually see b30 as pcc much but I wonder if that will change now. I locked my phone to b30 only on my drive home from work and noticed the new(old?) earfcn on every site, so it wasn't just a 1 or 2 site fluke. It also looks like they've been doing some fiber or other cabling work around the b2/b46 small cell nodes, I wonder if they are about to start adding c-band radios to those. 
    • Should trade it for some low-band there or elsewhere. AT&T dominates lowband.    
    • I checked existing spectrum holdings and selling 5x5 PCS to each of VZW and AT&T in Kauai would get them to 20x20 apiece there, which should make them happy. In Maui it makes more sense to sell 5x5 each of PCS and AWS to get VZW 20x20 AWS and AT&T 15x15 PCS. I figure it would be a sale rather than a swap, as neither of the other two have spectrum T-Mobile would want that's high-frequency enough to avoid the spectrum screen. Honestly, T-Mobile is strong enough in Hawaii from a capacity perspective that cutting down PCS/AWS holdings won't hurt, particularly in exchange for finally unlocking 2.5 (though in Maui I saw 140 MHz n41 regularly in September if I remember correctly).
  • Recently Browsing

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