Jump to content

SlowSprintInSD

S4GRU Member
  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • Phones/Devices
    HTC Evo 4G LTE
  • Gender
    Not Telling
  • Location
    San Diego
  • Here for...
    4G Information

SlowSprintInSD's Achievements

Member Level:  Smoke Signals

Member Level: Smoke Signals (1/12)

3

Reputation

  1. I noticed my LTE on at Catalina and Voltaire as well. In Bird Rock, I looked at my phone at La Jolla Blvd and Turquoise and saw the 4G indicator, but couldn't test it to confirm coverage. Sensorly shows it's not supposed to be active in that area.
  2. Not sure if this is coincidence (i.e. Sprint suddenly lit up LTE towers on Wednesday night) or if installing and using LTE Discovery (thanks for the tip djmatty!) on Wednesday helped my phone find its LTE powers, but yesterday and today I've been noticing that the 4G indicator now lights up periodically as I roam my neighborhood/drive to the office. Again, before yesterday, I've never gotten LTE on my phone even when I travel to LTE live cities.
  3. Wrote the previous message then proceeded to drive to the office. Sitting at the light at Catalina/Talbot, using "phone 1" (weaker of the two), I toggled airplane mode on then off... There it was: 4G! Had to rub the sleep out of my eyes to make sure I wasn't seeing things. As this was the first time I experienced Sprint LTE, I had to pull over and play with it. It was glorious. But to put it into numbers, ran a speedtest. 18.67MB down, 7.63MB up, 50ms ping. Drove two blocks north and it was gone. Now, on to trying to make sure I have the best settings/software for optimal connectivity.
  4. Tried the LTE Discovery on both phones (in a lighter signal strength area). First phone, got nothing. Second phone, had recordings of LTE signal, saw the 4G indicator light up once, but was never able to connect long enough to try out LTE. Then I tried the first phone that was unsuccessful at the Catalina/Talbot hotspot, again with no luck. So it seems like the first phone has issues and the second phone may work when NV is done. Is it worth the time and energy it would take to call Sprint to get to a "level 3" tech that might be able to trouble shoot phone 1 or should I wait until LTE is "officially on" in San Diego?
  5. Installed. Thanks! Seems like a pretty cool app. 'Signals' Looks like the data I get from ##debug# but using a nice overlay, then adds the 'Discover' tab which will be useful while driving (all SDiegans know how 'great' our fellow motorists are - no need to add to the problem), and the 'Map' is useful, but wish it showed all known towers, not just the one you're pinging off of. Maybe add sensorly-like historical data.
  6. Newb learns something new. Go figure. Thanks, I'll try the airplane mode toggle tonight in the "dark purple" spot at Catalina and Talbot. I tried it a little on the drive to work up Catalina (lighter purple on the map) when stopped at lights with no luck. That could also be part of the problem. Thanks, will check it out.
  7. Old post, but worth checking. I just checked out sensorly yesterday and it said we had coverage in Point Loma. I installed the app and used the map tracker driving up and down Catalina and got no LTE hits (300 or so pings - all 3G). So I went LTE signal hunting on foot. I was walking at Catalina and Talbot and got nothing. I have two HTC Evo 4g LTEs, both set to accept CDMA/LTE. Am I doing something wrong? What elese can I try? Thanks in advance for not skewering a noob. BTW, not LTE-related, but for anyone else that drives south on Catalina from Nimitz, do you have a guaranteed call drop at Catalina and Narragansett? They've been "working" on that for me for three years. The call log has gone on so long, that a new ticket has been started 4 times to accommodate the notes. Been escalated to OKC call center twice where they had me pull over and do that ##debug# thing and supposedly sent techs out 6x. No luck. Just checking to see if it's just me (have had three different phones as well do the same thing) - they tell me everything should be working fine, but no bueno.
×
×
  • Create New...