Jump to content

EvanA

S4GRU Premier Sponsor
  • Posts

    1,775
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by EvanA

  1. Yes without band 26 connecting to fringe 25 may be better. The radio is really built with the completed network in mind in that it drops 25 early so that it can move to 26. Sent from my Nexus 5 using Tapatalk
  2. Where are you located? Sent from my Nexus 5 using Tapatalk
  3. .15 inflates dBm readings. In reality .15 and 2.13 probably have very similar performance and 2.13 gives a small boost on 3G/1x. Sent from my Nexus 5 using Tapatalk
  4. Not gonna change anything... How long are you talking? Sent from my Nexus 7 using Tapatalk
  5. Yep that's right, you have to wait for eCSFB on B26 to be fixed, or use the .15 radio and miss calls and texts. Sent from my Nexus 5 using Tapatalk
  6. It's not the radio, it's a bug within the sprint network. My post on the previous page explains what is happening. Also a few pages back someone posted that sprint confirmed this was the case and that network engineers are looking for a solution. I'll reiterate here. This is not the fault of the radio. This is the fault of poor deployment of b26/41 alongside existing b25 with working eCSFB. Here is what I believe happens. The phone scans for LTE and connects to LTE on band 26/41 with broken eCSFB. Since eCSFB is broken/not added, the device falls back to 3G because the network tells it to. The radio is built with completed network upgrades in mind, where all bands have eCSFB. The phone behaves correctly for a properly deployed network. Because of the half-upgraded state of the network, Sprint has to tweak the network side to tell the phone to connect to the band with working eCSFB in the case that it finds a band without it. It also looks like the G2 users are experiencing this http://www.reddit.com/r/Sprint/comments/27kejy/what_is_going_on/ More G2 evidence: http://s4gru.com/index.php?/topic/4886-lg-g2-users-thread/page-245&do=findComment&comment=317751 Sprint forum thread where the issue is confirmed: https://community.sprint.com/baw/mobile/mobile-access.jspa#jive-discussion?content=https%3A%2F%2Fcommunity.sprint.com%2Fbaw%2Fapi%2Fcore%2Fv2%2Fdiscussions%2F162466 Now can we please stop the b****ing about this radio until the network is fixed? I have found that this radio is on par with .15 when the incorrect reporting of signal levels on .15 is taken into account. Throughput on the new radio also seems to be improved across all bands. Once the network side is fixed up I think people will be making a 180 on their thoughts about this radio. Sent from my Nexus 7 using Tapatalk
  7. He's wrong at the end when he says sprint can "flip a switch" and turn on VoLTE. There's still a lot of work to do before that can happen. He's also wrong about the top 5% stuff being removed... It's still there http://www.sprint.com/legal/open_internet_information.html Sent from my Nexus 5 using Tapatalk
  8. PRL update forces a rescan of all channels. Sent from my Nexus 5 using Tapatalk
  9. It probably hasn't been updated yet and thus doesn't have eCSFB. In Ericson markets like Austin it takes up to 14 days after the tower is accepted for the update to be pushed and eCSFB to start working. Sent from my Nexus 5 using Tapatalk
  10. Experienced the LTE scan issue today. The phone connected to B25 fine with working eCSFB, then it found B26 and almost immediately dropped to 3G due to lack of eCSFB on 26. Sent from my Nexus 5 using Tapatalk
  11. Wait was that band 41 then? Sent from my Nexus 5 using Tapatalk
  12. That's odd I can't find that site on the map. Sent from my Nexus 7 using Tapatalk
  13. The band 26 issues are eCSFB related from what I see. I have a sizeable amount of 26 around me and the new radio doesn't have any problems with it. Sent from my Nexus 5 using Tapatalk
  14. It could have just been the scan times not lining up. When on 3G the phone only scans for LTE every so often, so when it scanned for b41 you may have not been in range. I bet if you toggled airplane mode near the towers you know are B41 you would get it. Sent from my Nexus 7 using Tapatalk
  15. Were you camped on 25/26 LTE or 3G? Sent from my Nexus 7 using Tapatalk
  16. Exactly what I was thinking. Having HD voice quality calls across Verizon and t-mobile would be awesome. Sent from my Nexus 5 using Tapatalk
  17. Slightly off topic, but I had the same experience when I tried my t-mobile prepaid SIM in the N5 while in my basement. T-mobile was nonexistent as I expect, but sprint was able to maintain 1x 1900 connection. Sprint and t-mobile share the same tower for the one that services my home. Sent from my Nexus 5 using Tapatalk
  18. I have had very reliable band 41 connection with my nexus 5 using .15, so it's not a hardware problem. Have you tested the nexus 5 and m8 at the same time in the same location? Sent from my Nexus 5 using Tapatalk
  19. Here's the new radio for you guys that don't want to download the entire factory image. https://thelinuxman.us/radio-hammerhead-m8974a-2.0.50.1.13.img
  20. I noticed this too. Usually I would get. 26 from a tower 2.5 ish miles away, but now it's just 3G. This is probably for the better because at the fringe 3G is more stable. Sent from my Nexus 5 using Tapatalk
  21. I noticed that too. 3G/1x signal noticeably improved. The radio doesn't affect wifi. Sent from my Nexus 5 using Tapatalk
  22. Yes all you need to do is flash the new radio. Sent from my Nexus 5 using Tapatalk
  23. Same here. Yes. Sent from my Nexus 5 using Tapatalk
  24. Could just be some weird activation problem. Sent from my Nexus 5 using Tapatalk
  25. It's 30/4 going to 60/4. There is no 30/6 plan as far as I know. Also they're not converting to fiber, they're just shutting off the analog channel broadcasts to free up more room for digital signals. Sent from my Nexus 5 using Tapatalk
×
×
  • Create New...