Jump to content

Network Vision/LTE - Cincinnati Market


ohioratrodder

Recommended Posts

What PRL are you on? The current stock PRL scans for 1900 before 800, so you won't get 800 until 1900 is unavailable.

 

 

I am on 25018.

 

On my Galaxy S5 the PRL version is 51100. When I update the PRL it still stays at 51100. Am I doing something wrong?

 

Thanks for any help!

Link to comment
Share on other sites

On my Galaxy S5 the PRL version is 51100. When I update the PRL it still stays at 51100. Am I doing something wrong?

 

Thanks for any help!

My S5 is on the same PRL 51100, I'm wondering if thats device related, now that you mentioned the PRL being the same as mine

 

Sent from my SM-G900P using Tapatalk

  • Like 1
Link to comment
Share on other sites

Some food for thought/testing....I snooped around the phone via ##3282# and found what looks like a LTE scan time field. It looks like you can decrease the time it takes the phone to search for LTE:

 

1.) Dialer app


2.) ##3282#

3.) edit

4.) enter MSL number (you get this from sprint) (just say you are running diagnostics)

5.) BSR

6.) Timer Menu

7.) nextLTEScan timer

8.) Mine was set to 5 (minutes?)

9.) Change to lower minute value for quicker scan.

10.) Restart the phone.


 

Can anyone confirm if this in fact helps? I may change mine to 2-3 minutes when more towers light up in my area and/or if I travel.

  • Like 1
Link to comment
Share on other sites

On my Galaxy S5 the PRL version is 51100. When I update the PRL it still stays at 51100. Am I doing something wrong?

 

Thanks for any help!

That is the current PRL for your device. It will scan for 1900 before 800.

 

 

Some food for thought/testing....I snooped around the phone via ##3282# and found what looks like a LTE scan time field. It looks like you can decrease the time it takes the phone to search for LTE:

 

1.) Dialer app

 

2.) ##3282#

 

3.) edit

 

4.) enter MSL number (you get this from sprint) (just say you are running diagnostics)

 

5.) BSR

 

6.) Timer Menu

 

7.) nextLTEScan timer

 

8.) Mine was set to 5 (minutes?)

 

9.) Change to lower minute value for quicker scan.

 

10.) Restart the phone.

 

 

Can anyone confirm if this in fact helps? I may change mine to 2-3 minutes when more towers light up in my area and/or if I travel.

I have my device set to 3. Every 3 minutes that you are not connected to LTE AND you don't have an active data session (IE: streaming music or downloading something), it will pause/disconnect your data connection to search for LTE. This does use more power, as every few minutes it is essentially relogging you into all of your services.

  • Like 1
Link to comment
Share on other sites

For my last Sensorly mapping trip in LTE only mode, I also set my timer to 1. Then I change it back when I'm done.

 

Sent from my SPH-L520 using Tapatalk

  • Like 1
Link to comment
Share on other sites

For my last Sensorly mapping trip in LTE only mode, I also set my timer to 1. Then I change it back when I'm done.

 

Sent from my SPH-L520 using Tapatalk

That's a good idea but doesn't always work. Sensorly is constantly uploading data, which is almost always a constant data session. Your best bet is using SCP's alert for loosing LTE, then either using the reset data connection button or putting your phone into airplane mode and out when you hear the alert. This will force it to scan.

 

Another option would be the LTE Discovery app.

  • Like 1
Link to comment
Share on other sites

Hey everyone. I've been following this thread for a long time and have received some amazing information from it. Just wanted to let everyone know that I work up in Blue Ash and am sitting at my desk using my Nexus 5 and getting a decent LTE signal. The best part about this is I'm not in LTE Only mode and can make and receive calls with LTE disconnecting and reconnecting as it should. It looks like they've turned on CSFB at the Tamarco Dr. tower which is the tower I usually connect to. I also ran a speed test at the intersection of Cornell and Kemper in Blue Ash and pulled 25 Mbps down and 9 Mbps up.

  • Like 4
Link to comment
Share on other sites

Can anyone tell me about the tower at 6141 campus ln? It seems that it would be on top of the water tower at that location but I cannot see any antennas on top, was that tower moved to the other tower they built in mt Washington a few years back and the address not updated? Or am I just blind? Which is entirely possible

Link to comment
Share on other sites

I'm on west side of Hamilton with my tri band phone connecting to band 41. Still able to receive phone calls and text also.yte3a2en.jpg And no I'm not forcing it either.

 

Sent from my HTC0P3P7 using Tapatalk 2

  • Like 2
Link to comment
Share on other sites

I'm on west side of Hamilton with my tri band phone connecting to band 41. Still able to receive phone calls and text also.yte3a2en.jpg And no I'm not forcing it either.

 

Sent from my HTC0P3P7 using Tapatalk 2

I know SCP is saying B41 but I'm not sure I trust that. The GCI & PCIs don't match the B41 pattern for the Cincy market. Can you check your debug/engineering screen? You may need to send a bug report to mikejeep if I'm right.

Link to comment
Share on other sites

I know SCP is saying B41 but I'm not sure I trust that. The GCI & PCIs don't match the B41 pattern for the Cincy market. Can you check your debug/engineering screen? You may need to send a bug report to mikejeep if I'm right.

I actually did a speed test and that seems to support your theory as well. The upload and download channels are not right also after further looking. I was driving so I couldn't get in the engineering screen, but I do agree that it was a bug and I really was not connected to B41.

 

Sent from my HTC0P3P7 using Tapatalk 2

  • Like 1
Link to comment
Share on other sites

I actually did a speed test and that seems to support your theory as well. The upload and download channels are not right also after further looking. I was driving so I couldn't get in the engineering screen, but I do agree that it was a bug and I really was not connected to B41.

 

Sent from my HTC0P3P7 using Tapatalk 2

Still good news that you got LTE without forcing it.

 

Sent from my SPH-L520 using Tapatalk

Link to comment
Share on other sites

Still good news that you got LTE without forcing it.

 

Sent from my SPH-L520 using Tapatalk

Never had a problem connecting to lte in Hamilton after they launched.

 

Sent from my HTC0P3P7 using Tapatalk 2

Link to comment
Share on other sites

Never had a problem connecting to lte in Hamilton after they launched.

Sent from my HTC0P3P7 using Tapatalk 2

Same here. West and East side of Hamilton including Lindenwald have been good for me so far.

Link to comment
Share on other sites

I was driving through Elmwood Place on Monday and picked up LTE (likely B25) on my tri-band S4 mini.  I even made a test call, [e]CSFB seemed to be working good.  LTE cut out to dial and talk (as it's supposed to), but after I ended the call my phone went right back to LTE.  Most places I go (home, work, Kroger, etc.) I can only get LTE if I am in LTE only mode.  It may not really be news to anyone, but it was nice to have LTE working properly with stock settings.

  • Like 3
Link to comment
Share on other sites

I was driving through Elmwood Place on Monday and picked up LTE (likely B25) on my tri-band S4 mini. I even made a test call, [e]CSFB seemed to be working good. LTE cut out to dial and talk (as it's supposed to), but after I ended the call my phone went right back to LTE. Most places I go (home, work, Kroger, etc.) I can only get LTE if I am in LTE only mode. It may not really be news to anyone, but it was nice to have LTE working properly with stock settings.

That's been up for awhile

 

Sent from my LG-LS980 using Tapatalk

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...