Jump to content

Two Sites supposedly live with CDMA 800 in Rural Chicago Market


Recommended Posts

Posted

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
Posted

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?

Posted
This is so exciting. The first 2 of the 800 1xA sites are live!

 

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

Posted

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

 

Now that you mention it, I do remember that.

Posted

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

Posted

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
Posted

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

Posted

 

 

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?

Posted

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

Posted

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

Posted

I forgot how to get to my debug screen. I think we should post a stickie so it's easy to access.

Posted

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

 

Robert

Posted

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

Posted

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
Posted

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

Posted

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
Posted

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

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

    • It took a couple of months but this site is finally back online.  I was certain that a decommission permit would come through one day since it was offline for over 3 months but I passed by it today and it was working again. — — — — — This site is also finally live. This was probably the longest I had ever seen a site take to go live once all hardware was installed, about 3 months. Hopefully the site in Long Island City doesn't take as long.
    • So while we wait for @RAvirani to fix the website, I was able to connect one of my phones to Verizon n77 on a site with an NCI that appears to be adjacent to an NCI that was already in my database. Specifically, the site I call Taylor Run has been observed with these NCIs on n77: 44EEE469A 44EEE46AA 44EEE46AB 44EEE46BA 44EEE46BB I separately connected to the site I call Fairlington on its beta sector on n77: 44EEE46DA 44EEE46DB I'm assuming alpha sector is 44EE46CA/B.  With this data, I learned two things: 1) They're clearly not tracking the LTE GCIs with the NR NCIs.  Taylor Run is 1B61Fxx, while Fairlington is 1B680xx, not sequential. 2) It's clear that they're not using three byte sectors.  They're not even using two byte sectors like LTE does.  It looks to be done in an oddball fashion like how Dish is doing things.  Best I can come up with is a site ID that's something like: (NCI-0x20)/(0x30) It's possible it's actually (NCI+0x10)/(0x30) but I'm not really sure.  I also haven't connected to anything outside my immediate area here to know if this is consistent with other regions.  Not entirely sure how to persuade a device to do so, my Dish phone just connects to n77 at random in lieu of going to no signal.  (No data passes.) My take is to "break" the site notes for Verizon NR the way it was done with Dish NR, so at least the notes don't get copied to inconsistent sites, as has happened when I connected to Fairlington (came up as "Taylor Run").  It seems that Verizon, AT&T, and Dish all need work on the NR side to make sure site notes work properly.  Frustrating that they didn't standardize that for NR the way they did for LTE.  T-Mobile and US Cellular (while it lasts) seem to have done it the way I would have done it.  The others, not so much. - Trip
    • I tried to access that forum but it says I need a password. Is it limit to certain contributors?    I was going to report that the website is broken. For days it's been saying unable to retrieve signal data then going to a 404 error.
    • Sorry, I forgot about it when I posted previously.  And then I was talking to chamb by e-mail and away from my computer and suggested posting here.  Moved the posts to the proper spot. - Trip
    • It is probably better to post topics related to the map in the dedicated thread to help keep things organized and secure. This thread is big enough as it is, just want to try help keep things on track!
  • Recently Browsing

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