Jump to content

guirae

S4GRU Member
  • Posts

    27
  • Joined

  • Last visited

Posts posted by guirae

  1. **I came here to figure out how to see if I am on CA on my 6S.

     

     

    I went through this whole thread. Yes, I've experienced the borking of numbers. Yes I've got the B41 to show up again. But no, haven't figured out a way to see if i'm connected to two towers..

     

    Anyone have any leads on how to figure it out? An app possibly mentioned on Reddit or some other outlet? Been researching for hours and haven't been able to figure this out. Can we get to the bottom of this?

  2. Some of you may remember the issues I was having with LTE. Thanks for helping me out.

    I hope my explanation can help others to assess their LTE issues.

     

    Currently on: 4th Nexus 5 (3 of them were refurbished; current one is refurbished). 

    • 1st and 2nd ones had bleeding/dead pixel issues
    • 3rd one had LTE issues. It was would latch onto B26/41 but not transmit data. Was only transmitting data on B25. In the places that I ran tests, I was hitting 20 mb/s on my 1st N5.
      • When I called Advanced Tech Support, I was told that the three areas that I was frequently in were having "EVDO Problems" and that "latching onto B26/41 yet not transmitting data" was a known "EVDO Problem". I patiently waited for the 3 days they told me they would take. Nothing changed. 
      • I dropped to 3G very often
      • When switching towers when driving/walking to another area, I would lose signal COMPLETELY then have service again. **THIS HAPPENED A LOT
        • I thought it might have been the SIM Card. I swapped SIM Cards (chatting to swap SIM Cards is super convenient) and low and behold, it made a difference: I didn't drop service as much and i stayed on B25 more often.
        • BUT I would still latch B26/41 but NOT TRANSMIT DATA
    • 4th Phone
      • I contacted Google and they were nice enough to send me a 3rd refurbished device. 
      • ****IT WAS THE PHONE, NOT TOWERS OR SIM CARD (in regards to "latching onto B26/41 yet not transmitting data)
      • Now I latch B41 in doors (-112 dBm; 15 mb/s) 60% of the time (switch to B26 10% and B25 30%). 
      • An issue I had with the 1st N5 was dropping to 3G very often and taking forever to go scan back to LTE. When driving from a span of 15 miles, I'm on LTE 90% of the time. I think this may have to do with a new SIM Card (comparing phones 1st and 3rd phone).

    I write all this because when I had problems, hearing others problems helped me qualify and isolate the my phone's problem.

    • Like 1
  3. Considering switching to the GN4. I'm currently on the Nexus 5. 

    **I'm asking in purely RF Performance, how well it stays on LTE, how much it drops to 3G terms. 

     

    Anyone have experience with both phones and can recommend which phone has better reception/data latching/data speeds?

  4. I have suspicions it may be tech support giving you a line of technobabble that makes no sense.. stay on the phone until someone gives you an answer that at least is plausible. No "EVDO issue" would be relevant to you only having data on B25 and not the other bands you connect to.

     

    I apologize if you already mentioned this, but do other devices work properly in this particular area? Have you tried using yours somewhere else? Just trying to rule out a site issue.

     

    -Mike

    No I have not. I might have to RMA again..

  5. EvDO issue sounds to me like something's wrong with eHRPD...? But that shouldn't affect LTE. Do you get eHRPD from that tower?

    Didn't really check because most of the time it would go straight to B25. 

     

    When speaking to this tech, he told me that my issue is characteristic of "an EVDO issue". Just wanted to see if anyone had it...I still have suspicions it may be my phone's antenna....

    • Like 1
  6. LTE Discovery tells me that I'm connected to Band 26/41 but am not able to have any data transmitted to me. I then lose service completely then it latches onto B25. When on Band 25, data is flawless as before. Anyone have this problem?

     

    I called Sprint advanced tech and was told that the specific towers have a EVDO issue. What exactly is that? Doesn't sound like a eCSFB issue..

  7. B25 is the only band I'm receiving data. When it connects to B41 or B26, I am connected (verified via LTE Discovery) but I receive no data. Anyone know why? I just swapped SIM Cards and that seemed to help the data a little bit. 

    *This is a refurbished device. Could this be the antenna? Any fix suggestions? 

  8. I went through three RMA returns before I got a good one. They are all refurbished. I had one where it wouldn't connect to band 41 or 26 even after doing fresh factory flashes.

     

    The google guy I was emailing was nice to make sure I had one. He even followed up on me a few weeks after I got the good one which honestly is performing better than the original.

     

    Ah, I see. Did you ever try to swap UICC SIM Cards? That's what they told me to try out..

  9. I returned my Google Play Store 32 GB Nexus 5 to Google for a RMA. This new one is having a hard time sticking to LTE and is slower in speeds. In places where I would literally stand and consistently hit 15-20 mbps, I would have a hard time even holding LTE. I often disconnect completely, it searches/scans for a while then reconnects. I never had these problems on my previous phone. It doesn't seem like a ecfb issue; it re-connects but also, i didn't have the problem in the same place before.

     

    1.       I’m using the same UICC SIM card. I have a brand new one they sent me. Would this make a difference if I swapped it?

    2.       I’m updated PRL/Profile a bunch. I also have LTE band priorities (41 – 1; 25/26 – 0).

    3.       Could this be a hardware issue? The antennae? 

  10. Connectivity

    A better internet connection everywhere and more powerful Bluetooth low energy capabilities

    • Improved network handoffs resulting in limited interruption in connectivity. For example, continue your video chat or VoIP calls without interruption as you leave the house and switch from your home Wi-Fi back to cellular

     

     

    Do you guys think this will address the 3G to LTE issue that's been discussed the past few weeks?

    • Like 2
  11. I use my N5 on AT&T. It has been a plague of it not scanning back to LTE for 3-5 minutes since the day I started AT&T service. However, not everyone seems to have this problem. Not even on Sprint. Is it an early production issue? I don't know. I ordered my N5 in less than an hour after the went on sale. I also have the issue when I use Tmo.

    Could there be an issue with the fact that the N5 has many more radios (since it isn't limited to only the 3 bands Sprint uses for Sprint) than other Sprint branded (radio-ed) phones? Bit of a stretch and not quite logically cohesive but could it be that the N5 could be scanning through all the different bands/radios before it checks B25/26/41?

     

    Also some are stating that Build KTU84P has a different modem than KTU84Q. Could this be an issue? I'm on 84P and it is 4.4.4. Anyone have 84Q and have better results in regards to going to 3G to LTE in a faster time?

  12. **Sorry for posting twice. For some reason, I wasn't able to edit or delete the previous post.

    How about another Sprint device?


    Anyone else put there take shorter than 3 minutes to go from 3G to LTE? 

     

    Is there a way to quantify this data: When on 3G, how long it takes to recan and reconnect to LTE? 

     

    Also, with LTE priorities, I currently have 
    B25- 0
    B26 - 0
    B41 - 1

    What if I gave B26 and B41 the value of "2" and B25 the value of "1"? I'm wondering what the value of each number is or if it's just a number that signifies priority. If "1" has a different value than "0", maybe when the phone is on 3G, it'll affect which bands it scans for in a faster manner.
     

  13. No. Not all. And on AT&T, the Nexus 5 is a Quad Band device. And the problem still occurs. I can be there next to a BlackBerry Z30, HTC 8X and Samsung Galaxy Mega on AT&T LTE and they will rescan and acquire LTE between 5 and 30 seconds. And the Nexus 5 will take 3-5 minutes. So neither operating system, nor band support is relevant. The common denominator is the Nexus 5. Regardless of network.

    How about another Sprint device?

     

    Anyone else put there take shorter than 3 minutes to go from 3G to LTE?

  14. Don't think you can edit the scan times on the nexus 5. :(

     

    Sent from my Nexus 5

    Every phone does this though, correct? If it drops to 3G, any phone, any carrier will scan what in the appropriate time, correct? As in, it'll never just go back to LTE before 5minutes

  15. Having a problem recently (last couple of days) of going from LTE to 3G. In areas where I usually stay LTE, recently, it's been dropping to 3g and staying there until I toggle. Odd thing is, it can go back to LTE in LESS THAN 5 minutes (I hear usually it won't scan again for 5 minutes by default).

     

    1) Anyone know what the problem is?

    2) Where can i edit the LTE Scan Times (##3283# doesn't work and can't seem to find it in either *#*#3282#*#* or *#*#33284#*#*)

  16. There is no distinction that will impact your usage.  CSFB is a generic term to describe all Circuit Switched Fallback.  eCSFB is CSFB.  Kind of like saying all pairs of Levi's are jeans.  But not all jeans are Levi's.  Not all CSFB is eCSFB.  But all eCSFB is CSFB.

     

    eCSFB is just the newest iteration of CSFB technology that Sprint is deploying in Network Vision.  For most intents and purposes to all but our most advanced network enthusiasts they are synonymous and can be used interchangeably.  Any Sprint Triband device will operate on any CSFB or eCSFB technology deployed on the Sprint network.

     

    Is there a difference between a Sprint store purchased N5 and a Play Store N5?

  17. I've done it both ways without any issue. So I don't think that matters.

    Also, if I am in a region (different state/region) where CSFB is an issue, is there a way to force only voice and SMS? I don't mind if I don't have data but if I can't even have voice/SMS, that is a deal breaker for me...

     

    Also, when you said that CSFB isn't that big of an issue anymore, is that included eCSFB? or in your reference of "CSFB", is it distinct from "eCSFB".?

  18. You need to have a Sprint Micro SIM card and you will need to call or go online to your account and add your IMEI. If you don't do both, you'll have problems.

     

    Additionally, you cannot use an N5 that originally was purchased from Tmo. It must have come from Google Play or Sprint initially or it cannot be activated on Sprint. Only N5's from Sprint or Google are in the Sprint database whitelist.

     

    Whew, glad I came here. When I read up on this before, it seemed like any given N5 was going to be acceptable. Really appreciate the heads up!

     

    Is there a certain order that is necessitated? (E.g. call before popping Micro SIM | pop in Micro SIM THEN call)

    • Like 1
×
×
  • Create New...