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.
Like I said, anecdotal. All of those speeds tests where done in the span of 10 minutes past midnight, in (which is safe to assume) the same location and with extremely great signal strength/LOS.
The problem with upload speeds in the 2.5 Ghz band is that the UL speeds dramatically fall off whenever you move away from the tower. Good speeds are possible, but on a few select areas near towers.
Do you have the TA correction option enabled under Preferences?
What I really need to do is get a decent sample size of B41 TA reports without the correction factor enabled, and record what the app shows and what the correct distance is. That would allow me to calculate what the proper correction value would be. TA is a funny beast on TD-LTE, I have always had a correction factor applied to the raw value.. so with the option enabled it's applying a correction to the correction.. 🤯