WiWavelength

Okay, if you are a "cosplaygirrrl," then you are probably Japanese. And if you are Japanese, then your "holy carp" is koi. Am I right? AJ

If you expect to see 1 Gbps carrier aggregation on a handset in 2015 -- especially in Hagerstown, MD of all places -- well, you need to move. I have some oceanfront property in Arizona that I will sell you for a great price. AJ

If you need simultaneous voice and data while off of Wi-Fi, then you have a few options: stick to handsets from the HTC EVO LTE through Samsung Galaxy Note 2 generation, find an acceptable VoIP solution, or switch to another wireless provider. AJ

Too much spectrum for too few subscribers. Additionally, since it is "sacred cow" pure 3GPP, T-Mobile's network should be a bit more streamlined than Sprint's hybrid network. AJ

Just FYI, for those wondering about the Nexus 5 CDMA1X engineering screen signal metrics, here is what I posted this afternoon in the SignalCheck thread: http://s4gru.com/index.php?/topic/3060-signalcheck-android-app-to-monitor-your-2g3g4g-lte-signal-strengths/?p=234125 Ah, I see now that Mike already linked my post, but the quote above provides the full transcript. AJ

We have a number of recent posts on this phenomenon -- both in this thread and in the Nexus 5 thread. I am not sure where to respond. But I will at least run down the basics here. Since the Nexus 5 is a non SVDO, non SVLTE handset, it is connected to only one airlink at a time. This may seem foreign now, since we grew accustomed to first SVDO, then SVLTE over the past few years. But some of you should recall the years prior to SVDO handsets. You could have an active EV-DO data session yet still receive an incoming call -- even though EV-DO did not support circuit switched voice. The data session was paused, as the handset dropped back to CDMA1X to take the call. Something similar is happening in this case. Support is baked into the 3GPP protocol. Since SVDO and SVLTE are out of the equation, the handset camps on LTE. Meanwhile, the CDMA1X radio is off because there is only one radio path. When a call comes in, LTE signals the handset to drop back to CDMA1X for circuit switched voice. Then, the CDMA1X radio comes alive. This may sound complicated, but it is almost exactly what happens to those high and mighty W-CDMA users. I have posted this numerous times, but many people fail to realize that almost no W-CDMA handsets support SVLTE. They idle on LTE, but LTE signals them to drop back to W-CDMA or even GSM for circuit switched voice -- much as described above with LTE and CDMA1X. Oh, to add one more thing, I would have to double check, but I expect the VZW variant G2 supports SVLTE. So, it may behave differently from the Sprint variant, which does not support SVLTE. AJ

That is like beer. You do not buy beer -- you rent it. Now, if you pay interest on beer, ouch! AJ

The terms "booster" and "repeater," even "translator," may be used interchangeably, but there can be some differences among them. In most cases, the set up is just a pair of separated antennas with an amp in between. In that case, it is amplifying the raw RF -- the type of signal, modulation, FEC, etc., are immaterial. But a far more expensive, sophisticated set up might demodulate and remodulate the signal, potentially even "translating" it to a different frequency. AJ

Look at the post you quoted. It is from Robert. But you are right -- he does not bear the "Premier Sponsor" tag. How can that be? He really should donate. AJ

You are not connected to LTE, as 65535 is not a valid EARFCN. It is just a null value: a 16 bit integer of all ones. AJ

On second thought, the LTE, CDMA setting may do little to help with these non SVLTE handsets. AJ

I cannot write a lengthy tutorial, as I am predisposed. But for those having connectivity issues in mature LTE markets, I recommend LTE, CDMA mode instead of LTE Only. You get most of the same benefits without the drawbacks. AJ

Just a quick tip, when talking about differences between two signals already expressed in dBm, drop the negative sign and the "m" (milliwatt reference). If one signal is -104 dBm and the other is -84 dBm, the difference between the two is 20 dB. And that is a 100:1 ratio, by the way. AJ

You need to make a small fix on the "Samsung" Nexus 5. Thanks for maintaining this list. It is both interesting and helpful. AJ

The LG G2 should be no different from the HTC One and Samsung Galaxy S4. It will come with a removable SIM that is already installed. AJ

Thank you. We appreciate the positive feedback. AJ

---- EDIT: If this is your first time to this thread, please read this article by Robert (S4GRU Admin): http://s4gru.com/index.php?%2Fblog%2F1%2Fentry-357-nexus-5-and-lg-g2-experience-temporary-sprint-lte-connectivity-issues-due-to-circuit-switched-fallback-technology%2F OP: ---- As more and more inconsistent LG G2 and Nexus 5 user observations have filtered in over the past few days, S4GRU has decided to reopen a thread that we created as a placeholder to address LTE connectivity issues, if necessary. So, if you have a Sprint Spark tri band device -- especially but not limited to the LG G2 and Nexus 5 -- please report your LTE connectivity experience and location. See my two hypothetical examples below... Please keep this thread objective and factual. Complaining about the situation serves no productive purpose. But gathering anecdotal evidence that we can cross reference with our Network Vision progress maps can help get to the bottom of the current issues. Finally, expect further edits to this top post, especially as additional insider information and/or S4GRU technical analysis becomes available. Thanks in advance for your reports... AJ ------------------------------------------------ EDIT: Follow this link for a Sprint memo explaining why Tri-Band devices are not connecting to LTE in some areas: http://s4gru.com/index.php?/topic/5001-tri-band-lteecsfb-issues-thread/page-3?p=235876&do=findComment&comment=235876 Follow this link for a breakdown of incumbent and non-incumbent markets, and what that means for your Tri-Band ("Spark") device: https://docs.google.com/spreadsheet/ccc?key=0AhjoCbLKCt72dHJKMTVrc3lrSE95cklOTnB0V0c0M1E&usp=drive_web#gid=0 We're still looking for additional reports, as this does not account for all issues. -David

No, for now, keep all user discussion in this thread. Let staff decide whether an issue thread is warranted. Then, if so, we can move selected posts from this thread to other thread. Thanks... AJ

Okay, I found Kenneth. He had been sleeping. But I woke him up, and this is what he told me. If you are referring to 3GPP2 (i.e. CDMA2000) band class 1 PCS 1900 MHz carrier channel assignments versus PCS A-F license blocks, you can use the following ranges: PCS A block = 25-275 PCS D block = 325-375 PCS B block = 425-675 PCS E block = 725-775 PCS F block = 825-875 PCS C block = 925-1175 The wild cards are carrier channel assignments 300, 400, 700, 800, and 900. Those are centered precisely between two adjacent license blocks. Thus, they are potentially valid assignments only if the same licensees hold both adjacent blocks. And that makes them fairly rare, though Kenneth said he has spotted a few in the wild. See an example below: AJ

No, we need to create one thread entitled "Mah Airwave don't work" because that would cover 90 percent of the content in the countless Airave threads. AJ

Really? And this is not even the entire lot of them... AJ

Yes, I think I know where to find Kenneth. AJ

Might be time for you to take some Midol... AJ

Download Any Cut. Long press a spot on a home screen and select Widgets. Select Any Cut, then hold and drag the shortcut to the desired spot. Select Activity, then scroll down and select Debug. Repeat the same steps but select Testing (or other internal screen APK, such as RTN). AJ

Please do not start a new Airave thread. Use an existing one. We are already overstocked with them. AJ