Jump to content

iPhone and lte


Turboxsloth

Recommended Posts

In the "Current Sprint PRLs" thread in General topics, digiblur says that it sounds like it may be a legacy non-LTE prl, and I think it's safe to assume that it may be a mix-up on Sprints end. I doubt they would purposely force us off of LTE, because I see no benefit to Sprint in that.

Thanks for the clarification. I'll head over to that thread and see what's the fuss.

  • Like 1
Link to comment
Share on other sites

In the "Current Sprint PRLs" thread in General topics, digiblur says that it sounds like it may be a legacy non-LTE prl, and I think it's safe to assume that it may be a mix-up on Sprints end. I doubt they would purposely force us off of LTE, because I see no benefit to Sprint in that.

Talk about incompetence. Whoever was responsible should be fired.

  • Like 1
Link to comment
Share on other sites

Not just iPhone forced off LTE with this PRL, my G2 has it and wife said her PRL updated at work, but I dunno what number HTC one is. Haven't done PRL on my iPhone 4S or my gs3 yet. May not until this gets sorted.

 

Sent from my LG-LS980 (G2) using Tapatalk

 

 

Link to comment
Share on other sites

Talk about incompetence. Whoever was responsible should be fired.

On the bright side, maybe we'll be able to confirm the theory that the flood of upgraded iPhones this fall was largely responsible for the reduction in LTE speed & SNR there ;-)

  • Like 1
Link to comment
Share on other sites

On the bright side, maybe we'll be able to confirm the theory that the flood of upgraded iPhones this fall was largely responsible for the reduction in LTE speed & SNR there ;-)

That could work, except, I don't think many iPhones will get this prl as (to my knowledge) it wasn't pushed. I manually did a ##update# to get it. I usually check for updates once a week. Just so happens I pulled one that disabled the biggest feature of my phone. Hopefully, Sprint has a plan with this mistake.

Link to comment
Share on other sites

Did the update PRL again, and it updated to 55017 this morning...apparently they caught their mistake rather quickly. Still won't be out until later today in definite LTE territory to see what this does for my G2, but hopefully LTE is restored.

 

*edit*

 

My GS3 updated to 25017...so, **017 is apparently the one they meant to push...and **017 should be what phones are going to. going to check the HTC One right now and update PRL on it. I'm sure it'll roll to 55017 too.

Link to comment
Share on other sites

I could be wrong, but I believe that for iPhone users you can restore your phone as new and go through the activation screens. This should reset the factory PRL to 31000 (or whatever it is) which I believe is LTE without roaming. You can then restore your phone from a backup. I'm not worried about it b/c I have neither LTE or SMR near me, but I think that should work.

Link to comment
Share on other sites

If it was a mistake, it's one that shouldn't have lasted longer than an hour.

Except for the fact that the only people who manually update their PRL are us here...which in the scheme of things is minuscule to Sprint. I bet the issue won't bubble up to them for a few days at best more from new activations than people updating their PRL.
Link to comment
Share on other sites

Except for the fact that the only people who manually update their PRL are us here...which in the scheme of things is minuscule to Sprint. I bet the issue won't bubble up to them for a few days at best more from new activations than people updating their PRL.

That could be a good possibility. Could a customer service rep push a prl to your phone if I tell them this problem?

Link to comment
Share on other sites

Except for the fact that the only people who manually update their PRL are us here...which in the scheme of things is minuscule to Sprint. I bet the issue won't bubble up to them for a few days at best more from new activations than people updating their PRL.

That's not entirely true. Don't forget: Sprint's #1 customer care quick-fix is always a PRL update.

  • Like 1
Link to comment
Share on other sites

That could be a good possibility. Could a customer service rep push a prl to your phone if I tell them this problem?

You can try, but I just called in to try and make them aware of the issue and the guy had no idea what I was even talking about, "a PRL simply tells your phone what towers are around you and selects the best one..." Then I dropped the call because, well that's what happens in my market when I go from a NV to legacy tower. I'm cool with it though....
Link to comment
Share on other sites

That's not entirely true. Don't forget: Sprint's #1 customer care quick-fix is always a PRL update.

Well yes, it is, however there has to be an updated PRL to be pushed to your phone...their first go to move is to tell you to update your PRL, however the running humor in that is that does absolutely nothing for you if you're already on the most up to date PRL - which in this case is 60657. The fix need to come from wherever the PRLs are updated and pushed out to the devices, then "updating the PRL" will in fact fix the problem. Again, I go back to the fact that the quantity of Sprint users that has updated their PRL in the past 24 hours is probably in the single digits (us on this forum), and the only way that I know of to bring awareness to them is by customers calling in. Bottom line - this is yet another self-imposed debacle....WTF.

Link to comment
Share on other sites

I have tried to update today also, because it seems that 60657 also doesn't allow roaming, considering I'm at school where I always get 5 bars of Extended 1x/3G on my iPhone 5 but right now I am currently getting "No Service" and "Searching" constantly :td::wall:

Link to comment
Share on other sites

If you're still on 60657 update your PRL again (##UPDATE#) and you should get 51099. Worked for myself as well as others here. I'm not in an LTE area so I can't say you'll connect back, but logic would say 51099 is the next progression after 51098 and therefore your LTE scan should once again be active.

  • Like 1
Link to comment
Share on other sites

51099 was fixed in the system. You can update now.

Putting aside this whole 60657 debacle (thanks for taking the lead and getting it fixed BTW) you have any way of seeing what changes 51099 brings to 51098?
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.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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