Jump to content

First Sprint LTE handset when?


Recommended Posts

That's what happens whenever an Galaxy S series is announced in the spring. The U.S gets it that fall.

 

Released, sure - but announced by a carrier?

 

I can't think of a device that was announced by a carrier and took six months to get to market. Any history buffs here?

Link to comment
Share on other sites

Released, sure - but announced by a carrier?

 

I can't think of a device that was announced by a carrier and took six months to get to market. Any history buffs here?

 

I agree this is different than an international model/US model delay. It's not even a GSM/CDMA delay. The only thing they HAD to change from Verizon's Nexus was the frequencies of the radios. Shouldn't take this long. There has to be something else holding it up.

Link to comment
Share on other sites

I agree this is different than an international model/US model delay. It's not even a GSM/CDMA delay. The only thing they HAD to change from Verizon's Nexus was the frequencies of the radios. Shouldn't take this long. There has to be something else holding it up.

 

I am assuming that it has to do with no LTE commercially available anywhere.

 

I think once they even get a few sites up and running, fully tested, and commerically turned on they will launch the Galaxy Nexus.

 

April is still seeming like the most likely time for that to happen.

Link to comment
Share on other sites

The Palm Pre.

 

Close, palm pre was not announced by Sprint, it was announced by Palm. It was entire CES event put on by Palm, not sprint.

 

More technically, it was announced on Jan 8th and was released on June 6th - not six months.

 

Either way, no go :)

Link to comment
Share on other sites

Lots of things might be holding it up.

  1. The handset or software may not be signed, sealed and delivered just yet. Perhaps the Sprint GN is getting an updated Android build.
  2. Might be waiting until at least one LTE market is fully lit up (or nearly so) to showcase the flagship.
  3. Could be the logistics within Sprint, from system updates to the probably larger task of getting tens of thousands of Sprint sales/support people up to speed on what exactly LTE is/means and how to support it.
  4. Maybe it's just a complicated process to actually roll out a new network with new technology, while making sure it plays nice with the old stuff.

It'll be released when Sprint believes all it's ducks are lined up. April/May seems most reasonable.

Edited by oversight
Link to comment
Share on other sites

Sprint keeps trying to put bloatware on the nexus I bet. And Google won't let them have it on there...

 

Sent from my Galaxy Nexus using Tapatalk

 

Taking what you said there as a joke btw.

 

But i do love how ppl associate bloatware with sprint when out of all the US carriers they are one of the most responsive with it making a lot of it removable at least in newer devices.

 

Also whatever they are doing it will be better than VZ version as they somehow got the OK to strip features off the Nexus like Google wallet...still can't believe Google was ok with that.

 

Sent from my PG86100 using Tapatalk

Link to comment
Share on other sites

I personally don't have an issue with pre loaded bloatware. I just don't want to be blocked from removing it.

 

Posted via Forum Runner

  • Like 2
Link to comment
Share on other sites

The carrier bloatware is some of the most uninspired engineering ever. IMO it's mainly just put on there so that people who don't know where to get the good apps can still have some functionality of a smartphone. Verizon uses it to nickel and dime you to death. Sprint uses it to fill up your internal memory...

  • Like 3
Link to comment
Share on other sites

The carrier bloatware is some of the most uninspired engineering ever. IMO it's mainly just put on there so that people who don't know where to get the good apps can still have some functionality of a smartphone. Verizon uses it to nickel and dime you to death. Sprint uses it to fill up your internal memory...

 

At least from what I've experienced, bloatware is usually installed into the /System/app partition. Technically, I wouldn't say that it is quite fair to say that that fills up your internal memory. The phone memory when manufactured is partitioned into a few partitions: boot, recovery, user, system, radio (real time os for the CDMA), wimax (real time os for the wimax chip) and data partitions. System is usually 256 or 512 MB or something like that. An AOSP Gingerbread Android build is about 90 MB and about 120 to 180 MB for Ice Cream Sandwich (4.0). And HTC Sense/Gingerbread takes at least 200 MB, I think. But this software is installed into the /System partition which has already been partitioned. So any extra space in the /System area could be loaded with bloatware applications. And then because user-installed apps are installed on the /Data partition, extra bloatware installed into /System has no effect on the free space on the /Data partition.

 

A small nitpick I know, but I feel it deserves to be mentioned. Of course, the extra icons shown in the launcher for bloatware is a valid concern as that can be bothersome; however, in ICS you can disable those applications.

Link to comment
Share on other sites

Thanks for the info, strung. That's good to know. My biggest complaint about bloatware was security/privacy. I didn't like when Sprint did an update on the Evo and put a game called Nova on there. It had access to everything on my device. Including SMS. That did not sit right with me. And the fact that I couldn't remove it ticked me off. There was no legitimate purpose of why that bloatware had access to everything on my device. So it left me to conclude the worst.

 

:imo: Its my device and I should have everything or nothing in my device. Whatever I so choose.

 

Thanks again for your post. Very informative.

 

- Robert

 

Posted via Forum Runner

  • Like 1
Link to comment
Share on other sites

The LG Viper was FCC approved on January 9, and it is likely in production. It had to lose EVDO capabilities on ESMR to gain LTE on PCS (1900 MHz) capability, but it does do SVDO on 3G and SVLTE of course on 4G. If you want more details on it, check for the FCC ID with the model number LS840 under LG.

The Samsung Galaxy Nexus LTE for Sprint hasn't been approved by the FCC yet, but they're probably reworking the Verizon model now. They'll have to change the pre-amp and LNA on the LTE chip to work in the PCS band rather than the 700 MHz band. They'll also have to redesign the receive antennas (they can be closer together) for proper 2x Rx diversity on LTE. They'll also need to add a pre-amp and LNA and antenna set to do ESMR CDMA and EVDO. Sprint will also probably force them to change to a Qualcomm CDMA baseband-- the cheap Chinese Via baseband they use works fine with Verizon's strong signal, but Sprint's PCS signal in most areas is too marginal to use it-- search the forums and you'll see why changing that baseband is a smart move...

  • Like 5
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
    • At some point over the weekend, T-Mobile bumped the Omaha metro from 100+40 to 100+90 of n41! That's a pretty large increase from what we had just a few weeks ago when we were sitting at 80+40Mhz. Out of curiosity, tested a site on my way to work and pulled 1.4Gpbs. That's the fastest I've ever gotten on T-Mobile! For those that know Omaha, this was on Dodge street in Midtown so not exactly a quiet area!
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...