Jump to content

jefbal99

S4GRU Premier Sponsor
  • Posts

    3,619
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by jefbal99

  1. I can't believe Samsung screws up something so simple on its phones. I've got no PCI, no neighbors, and no B41 identification. :(

     

    But I'm very glad to have the update if only for the "strongest signal" fields in the log--that's a huge deal! I also see the "coming soon" option for a continuous log; also a huge deal. I can't wait for the next one now!

     

    Does anyone know if the Verizon 4.4.4 update fixed it for those customers? Trying to figure out if I should be looking forward to 4.4.4 as a fix or not. Otherwise, maybe 5.0 will help...

     

    - Trip

    I'm on an S4T and I get band 41 identification, but no PCI/neighboring cells. I'm still on the current 4.4.2 release, maybe a new radio with the next release will fix it. Previous radios didn't have TAC.

     

    Sent from my SPH-L720T using Tapatalk

  2. They're called jumpers by the way and there's 9.

     

    One for calibrated mini-dim and 8 for tx/rx mini-dim.

     

    Sent from my Nexus 5 using Tapatalk

    It was foggy this morning and dealing with sun/traffic, once I got past six and knew there were still two cables, i focused back on the road ;)

     

    I have my DSLR with me, so I might get some pics on the way home, just depends on timing because the boy has a soccer game.

    • Like 1
  3. This is why, if you are a serious network observer, these alternative, home brew ROMs are bad ideas. In my opinion, too many people are "flashaholics" obsessed over OSes.

     

    AJ

    AJ, I agree with you on the network observation thought. Stock would be the only acceptable data reporting method, however, we've even seen stock phones have issues.

     

    I'm not a flashaholic, but I can't stand touchwiz. I got my S4T knowing the devil was in it, but it has the best real world RF for low signal areas. I'm rural, so the better reception is noticeable even coming from my Note 2. My wife has a purple S4T sitting on the porch, just delivered today.

     

    Sent from my SPH-L720 using Tapatalk

  4. I know this post is a couple weeks old, but I just found this thread.. TACs are network identifiers, so it was either a glitch on your phone or something coincidental changed on Sprint's side. Could one value be decimal and one hex perhaps? Something could be hokey in CM11.

     

    -Mike

    No clue, but on CM, all my TACs are different

     

    Sent from my SPH-L720 using Tapatalk

  5. Some sort of a massive Mobile data issue that appears to be affecting the Lansing MSC.  At home in Portland, I was connected to the Kent St. site on the Grand Rapids MSC, everything was great.  Driving into work, the Grange Rd/Eagle site is the first on the Lansing MSC, and I've roamed or bounced crazy connections ever since.  No data, inconsistent texting/calls.  Only roaming works for sure.

     

    I've seen my 1X connection bounce anywhere from Fenwick and Caledonia via 1X800, Verizon romaing, a site in Dewitt, East Lansing, Holt, etc.

     

    With all the bouncing around, I assume that Network Ops is working on it.

     

    Calls to first level CSR have resulted in no assistance.  Lots of tweets to @sprintcare, but no good responses.

×
×
  • Create New...