Given the fact that Virgin has access to Extended Coverage ever since it's Inner Circle plan still now with it's current one at least according to customer service. Shouldn't Virgin be using PRL 55070 like it was with Inner Circle or is 7080 correct? I feel like there's an issue that isn't being paid attention too. Does PRL 7080 have the necessary stuff to make the device roam on Sprints extended partners.
iPhone 5 running iOS 7.1.2. Carrier "Sprint 16" and PRL 51101.
In the past I have been able to use the method of replacing carrier.prl in the sprint_lte_us carrier bundle folder, use the PRL push flag in carrier.plist, and with a few reboots I could get full time verizon 3g roaming with "prl 00001."
I am now visiting Alaska and am stuck on PRL 51101 with "extended" coverage and 1x data. I have tried every PRL I can find (11114, 11119, 53135, 00001) and I seem not to make any difference. After making the prl changes and after the last reboot I am stuck at no service. When checking phone info it will still say 51101.
I have to restore a backup of the sprint_lte_us carrier bundle folder and then things will work again after a reboot.
Any ideas? WIll the PRL update only work if there is native Sprint service around to start with?
When things are working with 51101 @ 1x speeds on "extended" I can do the ##update# and it say success.
Any help appreciated, would just like 3g data while traveling.
CA is disabled when HPUE is active.
HPUE devices should be able to use L2500 at signal levels down to -128. If the you often wind up in scenarios where the uplink is too congested, then the Qqualmin value is likely set too low.
Mine sure can not. I have an S9 with HPUE and it absolutely can not use -128. Also, I suspect that when we use carrier aggregation on 2500, HPUE is disabled. I doubt if the cell phone can transmit at the high levels of HPUE on two channels.
Somebody please verify that I am right or wrong on using HPUE on 2 aggregated channels.
I don't recall if I mentioned it here but major updates like those above features are usually sent out each quarter so it's not ready as I last checked a few weeks and they don't expect it til at least fall at the earliest. They've been doing field tests on the alternative backhaul mode but it requires network configurations and hw deployments out of the hands of the MB team. Sent from my Pixel 3 using Tapatalk
Red_Dog, Your posts are usually good ... you've tought me a lot, so thanks... but I have to say this...
1. Merger has not gone through. So no worries.
2. T Mobile 600 being deployed at a record pace as many on here have admitted to. Give it time. (Sprint would take years... just got Sprint 800 MHz in my area and how long has it been??) It works for crap anyway.
3. Sprint doesn't give up 800 for 3 years as it was written. They can also lease back, so I don't understand what the worries / issues are? None of it can be deployed instantly.
4. T Mobile owns very little 700 MHz, (5 or 10 MHz? and I don't think it's nation-wide) I think less than Sprint has 800 MHz... but they too are installing it as much as they can. Sadly, at the rate of all the states suing them, blocking and so forth on purely political reasons... not even sure this will actually happen. Now they're all crying that the FCC should/must open it up to public comment before their final vote . With a year and a half into the review, and the millions of pages of material submitted, there is no need or more review and re-review.
Until then, .. your Sprint service should remain the same.