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.
Inter-eNB carrier aggregation is possible and standardized (in the more recent releases) although it requires a unified backend core, so it won't be of much help until the transitional period has ended.
Does anyone have any pull to get a Magic Box Gold w/ voice amp? I have a gen 2 which works great for LTE but could really use the voice solution. The Airave doesn’t work for me as I don’t have a internet connection for it. I was promised by care like 5 times and then finally informed they are only for business accounts now.
Hey Brad, I just meant with any of those, but all together would be a great second step. I have a few embedded radios and available band combinations in generic firmware tend to be broad. Unfortunately Band 41 has limited FDD aggregation band support. Band 25/26 is available so Ideally 2 and 5 fall in there like dood mentions below.
Great solution! Super nice. My guess is development will gear more towards n41 but in the meantime this would be fantastic. I wonder if we will see a solution that allows us to aggregate channels from differing eNodeB or sectors. This would help in the transitional period of the merger.
I also wonder if this is possible with that fancy virtualized dual action but one end point core all the software magicians speak of. I believe the canadien carriers have an example of what I am referring to.