halcyoncmdr

I can't view the changes in the Note II PRLs as they don't follow the standard numbering scheme. That being said, it should be identical to the 21xxx series, just with 800SMR taken out due to the incompatibility they're still working on.

4GV apparently is EVRC, according to Wikipedia. NB means narrowband, which is what EVRC-B is. The 4GV suite also consists EVRC-WB, whish is the wideband codec. EVRC_NW stands for Narrow/Wideband, so it is capable of both the narrowband and wideband spectrum with the same codec, the wideband capability is what allows HD Voice.

The only thing that makes sense is something network-side converting it over. Perhaps due to landline calls not supporting either the EVRC-B or EVRC-NW codec and thus needing conversion anyway so it lets the phone transmit what it wants? I am only semi-educated in regards to codecs and know very little about telecom codec specifically so I don't know what is used beyond these two specifically.

Well, the EVRC-NW codec is the one used for HD Voice. EVRC-B is used for standard calls. Another older codec may be forced by the network if a tower is extremely overloaded and can't handle even that bandwidth for all of the calls. http://www.anandtech.com/show/5726/sprint-hd-voice-on-htc-evo-4g-lte-is-evrcnw-1x-advanced The only thing I can think is that the phone may still use the EVRC-NW codec on its end if the tower says the bandwidth is available, and then it is converted network-side for transmission to the other end. The EVRC-NW codec can handle everything the EVRC-B one can, plus additional, so it can be encapsulated entirely within the EVRC-NW transmission to the HD-capable handset. I've never seen an EVRC-NW codec listed on a call when it isn't an HD Voice call happening. The call I made the other day was with two HD Voice capable devices on a 3G Network Vision enabled tower, so it should have been HD.

You can check the debug screen while on a call. DEBUG can be accessed by dialing ##DEBUG# (##33284#) in the dialer, then going to 1X Engineering. If you are on an HD Voice call it will say "EVRC_NW" under "S0". This shows which audio codeo the phone is using for the call. I just made a test call on my G2 to look right now and happened to get an HD Voice call started, I've never gotten an HD Voice call that I know of before (I don't call much). Both phones have to be using a 3G Network Vision-enabled tower (as this has the equipment to support the codec), and both phones have to support HD Voice (as they have to support the wider-band codec). If either of these conditions are not met, the phones will fallback to an older codec instead.

At the moment, Tucson is sitting at 41/102 towers completed, with 40.2% completed. In addition, many of these sites seem to be clumped near each other (probably because of backhaul availability) so in some areas speeds will be great as these clusters can handoff with each other, whereas the one off towers are going to be more heavily used until nearby towers are upgraded still.

This is where the confusion with the redundant Sprint PRLs comes into play. Some Tri-Band devices are getting "SV-LTE" PRLs, others aren't. My LG G2 is currently on 55018, after updating PRL right now it gave me 51100. I don't have the expertise to actually tell what the difference between the two series are, we need Digiblur!

Yes, unfortunately in IBEZ markets LTE will likely be much more lackluster until the 800MHz stuff is sorted out. Unfortunately, these markets also aren't likely the highest priority for Spark either to help compensate. You also have to keep in mind that the few LTE sites active around Tucson are covering much more area than intended once they are all upgraded.

Changed first post to embed the spreadsheet itself into the post. I can't get it squished together enough to fit into the site's fixed width, but I've gotten it as close as I can.

Okay, I think I got it squished down so it will fit within the frame no matter your screen resolution. I noticed that IE8 has issues with the cell merging, so if you are running IE8, you will have issues viewing it in the frame, the actual Google Doc may still work however, if not then I'm sorry.

Edited to add the actual embedded spreadsheet into first post, it updates every time a change is made to the spreadsheet so it will always be up to date. I'll still be working on it throughout the day to try and optimize it better to fit the fixed-width of the forum, so if it's looking screwy just give me a bit.

Nothing, 51100 and 55018 are functionally identical. Read the stickied Current PRLs thread in the General forum. I update the data each time there is an official PRL update and accompanying information released by Sprint. The only difference officially is that the 55xxx series are supposed to be for SV-LTE (Simultaneous Voice and LTE) devices. Since the G2 is tri-band it cannot do SV-LTE and thus was using an incorrect PRL. In reality, I don't know what minor differences there are between the two PRLs, Digiblur may be able to give more specific information, the actual GEOS/SIDs/NIDs, etc. in the two PRLs are the same. Same frequencies, same roaming partners, etc. It has been discussed in depth in other threads that Sprint's PRL listings are much more complicated than they need to be, preferring to have separate PRLs for different device types even though a device will ignore entries it can't use anyway (this is why the "incorrect" PRL type worked just fine).

It isn't highlighted by default on IP.Board software unless it includes the http:// as well. Either your browser is hyperlinking it for you, or you have an extension installed that is changing the page. The main device.sprintpcs.com page is not a web-accessible standard domain, it is a domain used by Sprint to host files for hyperlinking from elsewhere.

Well, eHRPD is fairly new to the network, so it's quite likely you've never seen that error before. Error 67 on the other hand is fairly common, but if you've never had issues like most customers, then you would never see it.

I'm hoping that Sprint has a massive nationwide marketing campaign after Network Vision completion that has a simple video like this, or series of videos to explain the massive scale of the upgrades to the average Joe. I'm not sure how to cut it down to a proper 30-60 second TV spot though.

eHRPD:11 is the equivalent of an Error 67 on EVDO. Most new phones now show both eHRPD:11 MIP:67 on the error screen that comes up now. It is a data authentication failure. There are numerous reasons for this to occur, most having to do with your phone's data provisioning being out of sync with the network values. It will also occur when your phone is hotlined, suspended or disconnected; since your NAI is then suspended as well in those instances. It gives no information to actually determine what the cause is, it's the runny nose of the mobile world, a symptom with no real evidence of the cause but a huge number of potential causes.

RDFs have been updated for unreleased software before, fairly often actually. It just means it got through a certain point of testing.

Updated to new Google Sheets system, old link may not work anymore, and will no longer be updated. New link updated in original post, please update bookmarks if you have them set.

I have updated the Google Spreadsheet to their new Sheets system, the published link has changed for those of you with it bookmarked, the old link will no longer work.

Thank you, that's the information I needed. I just needed to know what one phone went to, we were too busy at work today so I didn't have a chance to look out at the demos.

That one sentence explains the "changes" made in the PRL update officially. The switchover from xxx99 to xxx00 however hasn't happened before, so I'm not sure whether they just rolled over all the numbers and kept the first 3 intact, or if the first 3 rolled over as well... For example, I don't know if PRL 21099 went to 21000 or 21100... and I haven't seen anyone post an updated PRL on their device other than an xxx18 series or a Note II with its own series. I don't expect it to take more than a couple days until the listing is updated officially so I can ensure the spreadsheet is right.

Many people forget about that time, The management post-Nextel merger made all of the wrong decisions. Every one of those decisions dug Sprint into a deeper hole come the era of smartphones and ubiquitous data usage.

Updated the spreadsheet again. I have the reasoning of the changes, but not the actual PRL numbers associated with it. The xxx17 to xxx18 series wasn't hard to figure out... but the xxx99 series being updated to xxx00 I am unsure of. The main page I get my listing of PRLs from hasn't been updated yet and still shows xxx17 and xxx99, it will likely be updated in the next couple of days after the weekend. So the actual PRL numbers are temporary unless my guesses were correct.

Officially it is still under investigation. Unofficially it is rumored and specualted it is an 800MHz issue, more common in Samsung Network Vision markets. Kind of ironic given it's a Samsung device, you'd think they would have tested it on their own equipment.

Yes, there is a natiowide issue currently.