Jump to content

Any news for Tucson?


Recommended Posts

Since my last post was locked without answering my question, I know there's a Tucson thread but it hasn't been updated in a while and no new info, is Tucson on track to receive LTE, and if so when can we expect them to start working on it? I don't understand why it takes sprint years and Verizon has done much much better and FASTER. I'll be happy with sprint once we get 4G

Link to comment
Share on other sites

Since my last post was locked without answering my question, I know there's a Tucson thread but it hasn't been updated in a while and no new info, is Tucson on track to receive LTE, and if so when can we expect them to start working on it? I don't understand why it takes sprint years and Verizon has done much much better and FASTER. I'll be happy with sprint once we get 4G

 

Work was not supposed to even begin until the end of Winter in your market. There will be nothing new until then. And since most markets have started late, this one may not be any different. Please use the market thread for future discussion: http://s4gru.com/index.php?/topic/2509-network-visionlte-tucsonyuma-market/

 

Thread closed.

 

Robert via Nexus 7 with Tapatalk HD

Link to comment
Share on other sites

azmattaz06, you need to do better research. S4GRU is loaded with information why the VZW LTE deployment has gone so fast: no LTE-Advanced compatibility, no RRUs, no dual band panels, no AWS capable devices.

 

I like to reference it to the Jason Hanky episode on "Seinfeld." It goes a little something like this, "When you don't actually do the steps, you can go through them pretty quick." Watch the whole thing, or jump to 3:30...

 

http://www.youtube.com/watch?v=c654iTRuxic&feature=player_detailpage#t=209s

 

AJ

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • What devices should do, and what they actually do, are two very different things! As you've probably heard me mention countless times, many of those screens get information in a proprietary manner directly from the modem; apps like SignalCheck can only get what the OS is reporting. I did find your earlier reports, and as I guessed, the OS was reporting valid signal strength. I will try to figure out a solution.
    • Service mode shows the SIM as having no service, so I would think the device should report that. I believe I sent a diagnostic report a little while back—can you check to see if you have it?
    • Interesting, that doesn't happen on my P7. Can you send me a diagnostic report the next time you see that please? Hopefully the phone isn't actually reporting the -115, that will be tricky.
    • Hey Mike—another dual SIM bug. If one SIM loses service, it doesn’t disappear from the app.  I’ve seen this a couple times—my Dish SIM will lose service (confirmed in service mode), but SCP won’t stop displaying -115 or so. And it logs a data point at that signal every time the location updates.  Along the same lines, I have a custom trigger set up for 313340 (Dish), and the custom trigger keeps firing when this is happening. 
    • TLDR: not really 😂 With dual SIM, initially I was struggling to keep the info from each SIM separate but updating properly. I figured out how to get each to update without negatively impacting the other SIM's process.. which caused those processes to run on separate threads. On some devices (notably your e5 Play), the OS doesn't like the separate threads updating the UI. But it was only a very small subset of devices. And at first, the crash reports gave the correct crash reason but it was pointing to unrelated parts of the code. Once I cleaned up some other bugs, the crash reports pointed me directly to what I needed.
  • Recently Browsing

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