Jump to content

PRL 61092


prophead
 Share

Recommended Posts

Just downloaded PRL #61092 this morning. Can anybody tell me what changed between this and 61091?

 

I'm hoping this opens up 800mhz SMR for voice (which Shentel told me should start working around new year)

 

Thanks for any info!

 

PS.... this is on a DuraXT

Link to comment
Share on other sites

Sprint has national PRLs they don't deal with the madness of regional ones. They already have enough madness with the crazy number per device and account types and some aren't needed.

 

Google will help you find out how to use qpst with the evo lte

 

Sent from a little old Note 2

 

 

Link to comment
Share on other sites

Hmm.... let's see how well you guys are at reading:

 

Geo:11 SID/NID 22435/65535 Sprint Nextel - Baltimore MD; Cumberland MD; Hagerstown MD Added with:

Pref RoamInd:None EVDO-Enabled:Yes

1X: S/476 S/526

EV-Scan: Sprint(0084:0AC0) P/125 P/150 P/325 P/650 P/50 P/550 P/225 P/675

  • Like 3
Link to comment
Share on other sites

Hmm.... let's see how well you guys are at reading:

 

Geo:11 SID/NID 22435/65535 Sprint Nextel - Baltimore MD; Cumberland MD; Hagerstown MD Added with:

Pref RoamInd:None EVDO-Enabled:Yes

1X: S/476 S/526

EV-Scan: Sprint(0084:0AC0) P/125 P/150 P/325 P/650 P/50 P/550 P/225 P/675

this enables smr in the Maryland area!

 

Edit: and evdo roaming?

Link to comment
Share on other sites

Leave off the roaming of EVDO. It just means your phone will scan for EVDO while attached to 800SMR on that SID.

 

24010 and 25010 both have this add. Looks like the 55xxx series for the Note2, iPhone5, Photon LTE(or whatever it is called), etc hasn't come out yet. Maybe they will get some SMR loving for the first time.

 

You could have say an S3, EVO LTE, and a iPhone5 all with the latest PRLs and updates. Go in a fringe covered building and the iPhone5 would be roaming or have no signal while the other two would have 800SMR.

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

    • What devices should do, and what they actually do, are two very different things! As you've probably heard me mention countless times, many of those screens get information in a proprietary manner directly from the modem; apps like SignalCheck can only get what the OS is reporting. I did find your earlier reports, and as I guessed, the OS was reporting valid signal strength. I will try to figure out a solution.
    • Service mode shows the SIM as having no service, so I would think the device should report that. I believe I sent a diagnostic report a little while back—can you check to see if you have it?
    • Interesting, that doesn't happen on my P7. Can you send me a diagnostic report the next time you see that please? Hopefully the phone isn't actually reporting the -115, that will be tricky.
    • Hey Mike—another dual SIM bug. If one SIM loses service, it doesn’t disappear from the app.  I’ve seen this a couple times—my Dish SIM will lose service (confirmed in service mode), but SCP won’t stop displaying -115 or so. And it logs a data point at that signal every time the location updates.  Along the same lines, I have a custom trigger set up for 313340 (Dish), and the custom trigger keeps firing when this is happening. 
    • TLDR: not really 😂 With dual SIM, initially I was struggling to keep the info from each SIM separate but updating properly. I figured out how to get each to update without negatively impacting the other SIM's process.. which caused those processes to run on separate threads. On some devices (notably your e5 Play), the OS doesn't like the separate threads updating the UI. But it was only a very small subset of devices. And at first, the crash reports gave the correct crash reason but it was pointing to unrelated parts of the code. Once I cleaned up some other bugs, the crash reports pointed me directly to what I needed.
  • Recently Browsing

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