Jump to content

chogardjr

S4GRU Member
  • Posts

    103
  • Joined

  • Last visited

Posts posted by chogardjr

  1. I live in Garland and work in Allen so my commute covers a lot of ground. In my 17 mile commute I'm on lte 90% of the time. Not exactly the fastest connection, between 4mbps-16mbps. In Allen where I work things have improved. During the first few weeks I was unable to get a signal anywhere but behind the building. Then a few weeks later the front of the building. Now I get lte indoors in most places, except the dead zone(still think my work is blocking signal somehow).

     

    So my experience is it has been improving, slowly but surely.

     

    Now I'm unlocked and rooted so I have changed my lte scan intervals, for both scan timers, to 1. This means it checks every minute instead of the default 30 minutes. This is a huge change that everyone should make. You don't have to be rooted although it makes it easier to get your msl code needed to have access to change these settings.

     

    I have had people tell me they have called Sprint and was given their msl code to change this. Your experience may vary. Just tell them exactly what you're trying to do and they should give it to you.

     

    Here is a screenshot of the timer menu so it's clear...

    http://db.tt/MZ0sqCKJ

     

     

    For a realistic look at coverage you should check out the maps on the Sensorly Web site, with an understanding that the crowd doesn't blanket the coverage area.

     

    My experience in the Plano/Allen/Frisco area suggests coverage remains spotty. I consider the growth of LTE sites since this market went live quite disappointing. During my 9 mile commute I see an LTE connection less than 50% of the time.

     

     

     

    Absolutely! At some locations between home and office the Speedtest app reports more than 20MB/sec, so when the phone, an HTC EVO LTE, finds a strong LTE signal the performance is amazing!

     

    Sent via LTE from my Evo LTE s-offed by an overweight panda.

    • Like 1
  2. I can confirm the 1.22 ota does improve lte connectivity.

     

    As far as the scan time, on my Evo4gLTE I went into the epst data lte record menu and changed the scan to 1 and it sticks. I also changed the bsr scan to 1. This makes my phone pop in and out of lte much much faster. The down side is if your on the edge of lte coverage it will keep switching back and forth making surfing sometimes a waiting game. Fortunate for me I am around a lot of lte and with the epst changes and the 1.22 ota I'm staying connected to lte much longer without all the switching.

     

    I believe the LTE scan is an issue based on things I've seen and heard. But the threshold issue is real, and the LTE scan is an unrelated issue.

     

    Thresholds were modified in the last round of OTA's. So threshold issues have been vastly improved. However, LTE scan could be affecting a lot of users now, and would explain a lot of the issues that EVO LTE customers are having. Cycling through CDMA only and CDMA/LTE mode forces the device to scan LTE, whereas it might take up to 30 minutes if you waited for it to scan on its own.

     

    On the GS3, it's called "nextLTEscan timer" and it is also set to 30. And there is a BSR timer set to 2. I went to modify the LTE timer down to 1, and it said "insert correct value" when I tried to save it. I changed it to 29, and it repeated the same error. It doesn't look like I am able to change the scan timer on my GS3. I will check my other LTE devices when I get a chance.

     

    Robert via CM9 Kindle Fire using Forum Runner

     

    Sent via LTE from my Evo LTE s-offed by an overweight panda.

×
×
  • Create New...