Jump to content

PRLs and LTE


Recommended Posts

Apparently I am wrong and I will admit it. From everything I saw and read it looked like the PRL did not have anything to do with LTE or the PCS G block.

 

Driving through Houston or should I say riding through Houston, with an EVO LTE and Galaxy 3. The Sammy is fully stock. EVO LTE is not of course. It has the latest firmware and base with a 12124 based prl. I couldn't get a 4G connection on the evo. I tried everything until the last thing I tried, PRL update to 25xxx. Boom.. 4g.

 

It makes total sense now. It's based on the MCC MNC records in these prls. Although it has nothing to do with the acquisition records themselves. Maybe it is just hard coded to g block. And later if another carrier is added it would get pushed or hashed to the other carrier like evdo does.

 

I want to confirm.. Has anyone been able to pickup LTE with a non 24xxx or 25xxx prl?

 

On another note.. The scanning is fixed on the EVO. I found I had a 4G indicator more on the evo than the galaxy 3. Shocker there. Would have thought it was the other way around.

 

Sent from my C64 w/Epyx FastLoad cartridge

  • Like 2
Link to comment
Share on other sites

Apparently I am wrong and I will admit it. From everything I saw and read it looked like the PRL did not have anything to do with LTE or the PCS G block.

 

Driving through Houston or should I say riding through Houston, with an EVO LTE and Galaxy 3. The Sammy is fully stock. EVO LTE is not of course. It has the latest firmware and base with a 12124 based prl. I couldn't get a 4G connection on the evo. I tried everything until the last thing I tried, PRL update to 25xxx. Boom.. 4g.

 

It makes total sense now. It's based on the MCC MNC records in these prls. Although it has nothing to do with the acquisition records themselves. Maybe it is just hard coded to g block. And later if another carrier is added it would get pushed or hashed to the other carrier like evdo does.

 

I want to confirm.. Has anyone been able to pickup LTE with a non 24xxx or 25xxx prl?

 

On another note.. The scanning is fixed on the EVO. I found I had a 4G indicator more on the evo than the galaxy 3. Shocker there. Would have thought it was the other way around.

 

Sent from my C64 w/Epyx FastLoad cartridge

 

I've connected to lte while on a vow prl. Galaxy nexus

Link to comment
Share on other sites

Each record has a sid with it too and a subnet FF'd. Which I assume is a wildcard like the 65535 full word value in most NIDs and the subnets on EVDO so you pick up every tower and panel.

 

The sid is the adjoining sid record for the cdma side of things.

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

Now I am curious which MCC records are in the prl. I never had the chance to add that comparison part into my PRL app yet.

 

So who has qpst and the 25xxx prl and wants to look it up? :)

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

Now I am curious which MCC records are in the prl. I never had the chance to add that comparison part into my PRL app yet.

 

So who has qpst and the 25xxx prl and wants to look it up? :)

 

Sent from my C64 w/Epyx FastLoad cartridge

 

I used to have the qualcomm PRL editor extension to Excel. I wanted to make the one PRL to rule them all but I got bored and lost interest (I'm a lazy mofo).

Link to comment
Share on other sites

Sooo... Add this to your list in Waco, Robert. Once you find LTE, load the 12124 prl and see if you can connect. Patiently awaiting confirmation... Tick tock tick tock... Tap tap tap... Jeopardy song starts playing.

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

 

I used to have the qualcomm PRL editor extension to Excel. I wanted to make the one PRL to rule them all but I got bored and lost interest (I'm a lazy mofo).

 

You just need the prl editor that comes with qpst.. And of course the file.

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

So if understand this correctly, you cannot modify your PRL to get EvDo roaming if you have an LTE phone at this time?

 

Not necessarily. You can modify the 25xxx prl to add evdo roaming.

 

I am not 100% sure on this either, but about 95%. I am waiting on further confirmation from people in a LTE area that know how to load PRL files.

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

There is another piece to this puzzle that I have never understood, which might be relevant. Those with EVO 4G LTEs report that there is a screen under the hidden LTE menu labeled CDMA List, which is a dynamic table of CDMA SIDs and BSIDs . (This screen is absent on the GS3.)

 

The relationship of these CDMA records to LTE, I think, has been a mystery. It is not as if anyone has shown that LTE node base stations broadcast the CDMA IDs of the towers where they are colocated. I have surmised that this "CDMA list" is a list of the CDMA sites the phone detects while it has an LTE connection. But of course I really don't know.

Link to comment
Share on other sites

So Robert confirmed it with the S3 as well. Sounds like it does depend on the MCC/MNC records. If there are any other S3 or EVO LTE owners in an LTE area, I'd like a confirmation from you as well with 12124 if you can. Just to make sure this is 100%...I'm about 98% now ;)

 

I'm thinking this has to do with the no SIM card on the Sprint phones. So they snuck it into the PRLs to control the LTE. The record doesn't control the band/channels at all as it has nothing to do with G block from what I can tell.

 

So... what MCC MNC records are in 25006? Let's take a look:

 

4162 - New York

4170 - Phoenix

4121 - Denver

4120 - Dallas

4181 - San Antonio

4812 - Memphis TN

4103 - Birmingham AL

4124 - Des Moines IA

4654 - Jacksonville FL

4982 - Richmond VA

4384 - Chicago IL

4148 - Louisville KY

4274 - Atlanta GA

 

Sooo... weird ones in the list right? Where's Houston? Where's Baltimore? How are they working right now? Are those towers assigned wrong SIDs right now on the LTE side? Nope. It looks like they only need to assign one MCC/MNC record to each Geographic section of the PRL, just like how EVDO Assn records are done. They FFF the record and it covers all the SIDs in the geo record. That takes care of the weird list. So I looked at things a bit further. Which geo areas don't have a "LTE" record? AK, NE, HI, & VI/PR

 

Hmm...the plot thickens. I need a guniea pig that knows how to load PRLs on their phone in an LTE area as I'd like to test a few ideas.

Link to comment
Share on other sites

So... what MCC MNC records are in 25006? Let's take a look: 4162 - New York 4170 - Phoenix 4121 - Denver 4120 - Dallas 4181 - San Antonio 4812 - Memphis TN 4103 - Birmingham AL 4124 - Des Moines IA 4654 - Jacksonville FL 4982 - Richmond VA 4384 - Chicago IL 4148 - Louisville KY 4274 - Atlanta GA

 

My question is: how are those MCC-MNC records? Those are SIDs, which are an IS-41 (AMPS, TDMA, CDMA) construct. MCC-MNC should be 310-120 (310 for the US, 120 for Sprint).

 

AJ

Link to comment
Share on other sites

There is one sid associated with each MCC record. And actually Sprint has their code FF'd.

 

Still doing my research on this whole MCC MNC thing and what they are really supposed to be used for.

 

Sent from my C64 w/Epyx FastLoad cartridge

Link to comment
Share on other sites

Indeed I was correct, each GEO requires a MCC record.

 

I did some digging and found a 683-E PRL in the NV on the phone. Actually has the proper LTE records and full MCC MNC for Sprint. I wasn't able to find the MSPL and MLPL files though.

 

The MLPL defines systems in terms of MCC only. Although existing PRLs can encode MCC information (see CDG Reference Document #86), in many cases the MCC broadcast by 1X / DO networks is not reliable. Instead, MMSS makes use of a new PRL record structure added to revision E of IS-683 to “tag” a 1X or DO system with an MCC (and possibly MNC).

This IS-683-E PRL creates an alias MCC for a 1X / DO system that is internally defined in the MS/UE, and is not dependent on the broadcast MCC value from the system. This MCC value is then used to find a match in the MLPL, so the correct technology priorities can be applied.

The new system record may be provisioned as follows:

 Only a single “tagged” record is required in each GEO. All untagged systems will be assumed to have the same MCC value. It is recommended to apply the tag to the first record in the GEO for clarity.

 Use of a wildcard MNC is recommended, to match the MCC-level granularity in the MLPL.

 The tagged record can be either a 1X or DO system record (both use the same new System Record Type value).

 Rather than adding a tag to an existing record, it is recommended to duplicate the record and then tag it. This can assist non-IS-683-E capable devices to skip the new record and access the remaining PRL records without missing a high-priority system.

In initial LTE deployments, there may be regions (represented by GEOs in the PRL) where no LTE service is available. There may or may not be home 1X / DO coverage in these regions (refer Figure 2-1 above). To avoid unnecessarily scanning for Home LTE service in these regions, implementations may support an optimization such that a device that acquires a 3GPP2 system in a PRL GEO where no system is tagged with an MCC will not attempt to start MMSS. Operators can leave their non-LTE GEOs unmodified from the standard IS-683-C format to prevent scanning for LTE in these regions.

Link to comment
Share on other sites

I can confirm on the galaxy nexus, I am able to use a hacked Verizon-only prl (00001) to be on Verizon Evdo and Sprint LTE simultaneously. I can also be a dummy and try any other prl if needed.

Thanks, saved me some time.

 

When I first found Sprint LTE, I was on 00001, so I was confused. I stopped roaming anyways, but now I'm gonna start again.

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

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Update just showed up for both of my phones. So far I don't notice any difference, LTE TA is still reporting as 0, I was hoping the new routine might fix that. I sent a diag report from both phones in case you need any of that info. I'll let you know in a day or so if its crashing as frequently or not. 
    • A new SignalCheck Pro beta release is rolling out now, and should become available on Google Play shortly! Some notable changes: New "swipe to refresh" -- flick down on the main screen, and the data will "refresh" -- I put this in quotes because it will *not* force the modem to be polled (that's unfortunately not possible), but it will 'wake up' the app and display the latest information if for some reason your screen did not automatically update. I am still working on improving this. New cell identification methods for Android 12+ devices -- new routines are available in Android 12 and this is my first attempt at implementing them. I have not seen any changes positive or negative on my Pixel 6, but hopefully someone sees improvements. I will continue exploring these methods and adding new features as I get them working. Location service auto-restart -- if your location has not changed in 10 minutes, the background location service should restart itself. This is a work in progress that I intend to optimize during beta testing. Missing/invalid TAC values included in web uploads -- this will need some testing, because I can't replicate it myself. The option to log cells with missing TAC must be enabled for this to have an impact. Feedback welcome as always!
    • Another converted keep site: Sprint eNB 9436 -> T-Mobile eNB 895067 (40.60777246698788,-74.16199692361377) Looks like they're using the FFVV-65A-R2-V1 here, as well!   Edit: Also, I know this technically isn't NYC, but here's a Jersey City conversion. Not 100% sure on either eNB. Sprint eNB 105863 -> T-Mobile eNB 876452 (40.72265196811989,-74.08804945021805)
    • More confirmations incoming! T-Mobile eNB 880561 (40.74176835140717, -73.88364207139453)   Sprint eNB 6191 / T-Mobile eNB 880065 (40.71339007010928, -73.85695387371624) Confirmed this site but was unable to get a photo because the antennas are set back from the edge of the building. I could see them from super far away but there wasn't a good area for me to pull over and snap a pic.   Sprint eNB 6189 / T-Mobile eNB 877995 (40.71183894845567, -73.83529788316665)   Sprint eNB 253741 / T-Mobile eNB 875537/875538 (40.70170960850086,-73.83302208208359)   Sprint eNB 79912 / T-Mobile eNB 875989 (40.86349197342981, -73.923456682535) — — — — — T-Mobile eNB 880536 in the Bronx isn't a Sprint conversion but rather, T-Mobile changed the eNB when they upgraded the site. The nearest Sprint site at 40.8150405321864, -73.93010756429787 still has all of its antennas up and is literally within spitting distance of two other T-Mobile sites in an area that's very industrial as opposed to residential or commercial so a keep site isn't particularly necessary. You can see on Cellmapper that the old eNB stopped broadcasting about two days after the new eNB went live.  — — — — — Also wanted to add that I spotted AT&T C-band antennas quite a bit in both Queens and the Bronx. I would expect a summer C-band launch announcement from them because they're moving FAST. At least in my area, it seem like they're upgrading at a faster pace than Verizon is. Some more pics: AT&T eNB 116408 / T-Mobile eNB 42887 in Woodhaven. This one is interesting because T-Mobile upgraded this site but in the process didn't put any Ericsson n41 antennas. There are just two of the RFS antennas that we normally get.   AT&T eNB 112047, bad pic but the arrows on the billboard are pointing right at the C-band antenna lol   — — — — — Last edit I promise: I noticed T-Mobile submit a permit to convert the keep site I found in Staten Island (Sprint eNB 75141). I 100% guessed it's location since I connected to it literally 4.5 miles across the water while inside a building. Glad to see I was right!
    • Support for the -1 TAC is good to go now, so I'm ready whenever you are!
  • Recently Browsing

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