Jump to content

WiWavelength

S4GRU Staff Member
  • Posts

    18,133
  • Joined

  • Last visited

  • Days Won

    429

Everything posted by WiWavelength

  1. Under the best of signal conditions, the max possible downlink throughput on a 5 MHz FDD LTE carrier is 37 Mbps. So, 32 Mbps is near the max and is not sustainable -- unless Sprint is building out an LTE overlay just for you. As more and more new and existing Sprint subs adopt LTE handsets, average downlink speeds will likely settle in to the 7 Mbps range, and since that is an average, sometimes speeds will be even lower. AJ
  2. Before Rickie moved to the middle of Misery, he observed that Nex-Tech was expanding into the I-135 corridor, which is Sprint corporate territory. So, Sprint and Nex-Tech may have had a falling out over that, not to mention, the Lower 700 MHz A block spectrum for LTE. And Nex-Tech, United, and PTCI all seem to march in lock step, since at least Nex-Tech and United treat each other as fully native footprint. AJ
  3. Well, good, I thought that my joke had fallen flat. I was going to try this one next: Miss Residency? Who the heck is that? The young, pretty MD at the hospital? AJ
  4. Does slide 36 remind anyone else of a famous Annie Liebovitz photographic juxtaposition? AJ
  5. Samsung's interest in using its own Exynos SoC is to pair it with its own 3GPP baseband. But if a device requires a CDMA2000 baseband, expect Qualcomm to remain the supplier. Like it or not, nothing else compares to Qualcomm in that arena. And see Brian Klug's tweets about the Galaxy S4 international SKU, which uses a Samsung baseband, lacking Rx diversity. AJ
  6. Beware what you wish for, though. Isolated pockets of roaming mitigation footprint mean call drops at those cell edges, whereas ubiquitous roaming coverage is just that -- ubiquitous. Now, as less and less traffic is voice, more and more is data, maybe those hard transitions between native and roaming coverage become less of an issue. AJ
  7. Well, I live in the state most affected by this loss of pseudo native coverage, and while I am not pleased, it should hardly affect usage. Nex-Tech, United, and PTCI will remain as roaming partners. And as the posted maps show, even EV-DO access will continue. The people that it will affect most are those, like ggore, who are using Sprint services irresponsibly. They are Sprint subs (who should not be Sprint subs) living in pseudo native coverage. Why? If it were worthwhile, Sprint would have built out western Kansas itself, rather than deed that area to Nex-Tech and United. And keep in mind that T-Mobile still has less native footprint in western Kansas than Sprint does, while VZW and AT&T each had none until VZW bought out both Alltel and RCC, then had to divest RCC's western Kansas assets to AT&T. AJ
  8. ggore is such a tool. I posted this response in the HowardForums thread: http://www.howardforums.com/showthread.php/1797104-Sprint-getting-rid-of-more-native-coverage?p=15121326&posted=1#post15121326 AJ
  9. Oh come on, digiblur. Since you have renounced HTC, what do you really know about the One? It is not a miracle, but it is a large advance from the EVO LTE. Basically, the One performs as intended -- it acquires and retains LTE in deployed cells and falls back to eHRPD in not yet deployed cells. As for RAM, this specs race is getting to be ridiculous. Too much RAM makes developers lazy, as they do not care if their OSes or apps are RAM hogs. AJ
  10. by Josh McDaniel Sprint 4G Rollout Updates Thursday, May 2, 2013 - 9:35 AM MDT Last year, LG released a mid-range device that made its way from one CDMA carrier to another. This year appears to be no exception. The LG LG870 recently passed through the FCC OET (Office of Engineering and Technology) with Sprint LTE and band 10 CDMA2000 on board. If the LG Viper (LS840) last year is any indication, it was released as the Connect (MS840) on MetroPCS, and then as the Lucid (VS840) on Verizon before it came to Sprint. In January of this year, MetroPCS released the Spirit (MS870), and earlier this month, Verizon released the Lucid 2 (VS870). Now, it seems to be Sprint’s turn again. However, it currently appears that Sprint is releasing this handset on its Boost brand under the codename FX1, as the model number is LG870, not LS870. (As of now, the name and that it may be released only on Boost has not been confirmed.) But all previous Sprint LG phones from last year have model numbers beginning with LS. The Bluetooth 4.0 profile supports HSP, HFP 1.6, A2DP, AVRCP 1.3, OPP, FTP, PBAP, SPP, HID, GAVDP, SDAP, PAN, and MAP, according to the Bluetooth SIG, which also lists the phone as “(LG870 (for Sprint/Wholesale)).” Sprint wholesale partner Ting, anyone? As for specs, if this phone is like its 870 model counterparts, it will have a 1.2 GHz dual core processor (possibly Qualcomm Snapdragon S4 Plus MSM8960) with 1 GB RAM, 5 MP rear camera with 1080p HD video recording, and 1.3 MP front facing camera. According to the FCC authorization docs, LG sent the handset to testing with Android 4.0.4 on board, but according to cloud4sites mtest, it has Jelly Bean 4.1.2 on board. So, hopefully it will be released with 4.1.2. CDMA1X + EV-DO band classes 0, 1, 10 (i.e. CDMA1X + EV-DO 850/1900/800) LTE band class 25 (LTE 1900; PCS A-G blocks) LTE 3, 5, 10 MHz FDD channel bandwidths SVLTE support, including SVLTE and simultaneous 802.11b/g/n 2.4GHz Wi-Fi tether Maximum RF ERP/EIRP: 26.60 dBm (CDMA1X 850), 26.26 dBm (EV-DO 850), 26.53 dBm (CDMA1X 1900), 26.16 dBm (EV-DO 1900), 25.06 dBm (CDMA1X 800), 25.20 (EV-DO 800), 25.11 dBm (LTE 1900, 3MHz FDD), 24.93 dBm (LTE 1900, 5MHz FDD), 24.70 dBm (LTE 1900, 10 MHz FDD) 802.11a/b/g/n Wi-Fi NFC In their FCC OET authorization filings, OEMs customarily request temporary confidentiality regarding internal and external photos of their devices. But in an unusual move, LG has requested permanent confidentiality for, among other things, antenna distance and simultaneous scenarios for SAR analysis. So, no antenna diagram is available at this time, nor maybe ever unless a teardown review is forthcoming. Sources: FCC, Bluetooth SIG, Cloud4sites mtest
  11. We do not need continuing Galaxy S4 info fragmented across two different threads. So, this thread will be closed sooner or later. Why is that a problem? AJ
  12. Ah, good old Samsung "LTE Enginerring." I do not see anything that has changed post Galaxy S3. Does anyone else? Will you post another LTE engineering screenshot? Give the fields 15 seconds or so to stabilize before you take the screen cap. In the screenshot that you posted, the uplink and downlink EARFCNs are not valid. I just want to see if those fields will populate correctly. AJ
  13. "Oh, there she is, Miss Residency..." Wait a minute, I think she is drunk. AJ
  14. Correct, it does have separate basebands. The CDMA2000 chipset is VIA Telecom, while the LTE chipset is Samsung homebrew. AJ
  15. Not exactly. T-Mobile will offer... + AJ
  16. Will someone please post a few Galaxy S4 engineering ("enginerring") screenshots to see if any screens or fields have changed since the Galaxy S3? AJ
  17. Guys, themuffinman started the Galaxy S4 user thread a few days ago, but no one seems to be using it. Let us shift most discussion over there now, since the phone has been released. I will likely be moving some of the recent posts from this preview thread to the user thread, then potentially closing this thread in the near future. http://s4gru.com/ind...s4-user-thread/ AJ
  18. It is a known issue. The EV-DO engineering screen on the HTC One does not populate with valid data. The CDMA1X and LTE engineering screens, though, function normally. AJ
  19. T-Mobile will give you "about tree fitty." AJ
  20. Forgive digiblur. He disowned HTC after one minor misstep. Now, he keeps his plastic handset locked up inside a plastic protective box. AJ
×
×
  • Create New...