Slow lane: why Google's new Nexus 4 doesn't have LTE


Recommended Posts

http://www.theverge.com/2012/10/29/3569688/why-nexus-4-does-not-have-4g-lte

The Nexus 4 is an impressive smartphone that ticks off every modern spec checkbox you could ask for, save one: LTE. Instead, the Nexus 4 will only come unlocked with HSPA+ radios. It is a disappointing omission, driven by both Google's complex philosophical desire to build open devices as well as the fairly simple economics of building a halo product for a small niche of early adopters.

For Google, Nexus is a flagship brand that represents the best of Android, with Google leading by example to show other hardware manufacturers what Android can be. And though partners build the hardware, Google wants direct control of the software on Nexus devices with no carrier intervention. That alone means Google can't sell an LTE device, as there's simply no access to LTE networks without working with carriers in one way or another: Verizon and Sprint's LTE networks still require compatibility with their 3G CDMA systems, and there's essentially no such thing as an unlocked CDMA device. AT&T's fledgling LTE network runs on different frequencies than other LTE networks around the world, so Google would have to build a custom phone for just 77 markets in the US. Doing that without AT&T's financial assistance makes little sense.

Android head Andy Rubin calls the lack of LTE a "tactical issue," and cites cost and battery life as major concerns with devices that have to support multiple radios. "A lot of the networks that have deployed LTE haven't scaled completely yet ? they're hybrid networks [...] which means the devices need both radios built into them," he said. "When we did the Galaxy Nexus with LTE we had to do just that, and it just wasn't a great user experience." But the reality now is that many LTE devices ? including the iPhone 5 and the LG Optimus G, which shares common hardware with the Nexus 4 ? use larger batteries and newer, more efficient chips to balance the power draw from LTE

That leaves the issue of control, and the politics of LTE network access tilt almost exclusively towards carriers. For example, Verizon has offered an "Open Development" initiative since 2008, offering other companies the ability to run devices on its networks, including the LTE network. "As long as the person follows our specifications and certification process as outlined on our open access website, they can get a device on our network," a Verizon spokesperson told us. However, that program ? which to date has primarily been used in a business-to-business context ? would still prevent Google from updating its phones in a timely manner. "Firmware pushed to devices over the air must be tested and certified," Verizon told us.

Ironically, Verizon's LTE network runs on 700MHz "C Block" spectrum which has FCC "open access" rules attached to it, which require that any compatible device be allowed to connect. Google fought vociferously to put these rules in place, even participating in the FCC's spectrum auction to ensure Verizon paid the minimum bid price that triggered the rules. But the rules have turned out to be virtually meaningless in practice, as Verizon uses 700MHz in conjunction with CDMA spectrum that doesn?t have similar open access rules ? so while Verizon might be legally required to support an unlocked LTE device, the legacy CDMA network still effectively keeps all of Verizon?s phones locked

For GSM / HSPA carriers, the issues are primarily economic, not access. AT&T, T-Mobile, and international carriers all uniformly allow unlocked devices to run on their GSM / HSPA networks, and AT&T says it will allow any unlocked device to access its LTE network, although the carrier can't guarantee everything will work or that it would be able to provide technical support.

But building an LTE phone is an extremely costly undertaking with sharply limited potential markets. Although Verizon, AT&T, Sprint, Everything Everywhere, and other carriers are working quickly to roll out LTE networks, it's still a nascent technology with significant interoperability problems across many spectrum bands, requiring companies to create different hardware variants of their phones for each network. Profitably building all those variants requires either financial assistance from the carriers or a large addressable market for an unlocked device. So while Verizon has by far the largest LTE network in the world, covering over 400 markets and over 250 million people in the US, Google has no access to those customers. Other LTE networks are much smaller: AT&T currently has LTE in just 77 markets covering 135 million people, and Everything Everywhere in the UK has a goal of covering only 20 million people by year's end.

n short, the number of people that Google could reach with any single unlocked LTE Nexus 4 is relatively small. And while the Nexus 4 looks like a solid flagship device, Nexus phones have never been bestsellers, shrinking an already-small potential market to virtually nothing. Google may be getting serious about selling hardware with the Nexus 4, but not so serious that it's willing to compromise with carriers, and compromising with carriers is the only way to make LTE work.

And there's precious little to suggest working with carriers is even in Google's best interests, or in the best interests of Nexus customers. The Galaxy Nexus was announced last year with a promised LTE version on Verizon, but the carrier held back releasing the phone for months to promote its own Droid RAZR instead. Google eventually grew tired of waiting and sent unlocked HSPA+ devices to reviewers. And software updates for Nexus phones sold through carriers have been problematic as well: it took the Verizon three full months to disseminate the Android 4.1 Jelly Bean update to its Galaxy Nexus, slightly longer than Sprint. That's actually better than it used to be with carrier-partnered Nexus devices, but still much longer what Google can achieve without carrier intervention ? and far too long in a marketplace where Apple has set a standard for simultaneous worldwide software distribution across multiple carriers.

Andy Rubin put it this way: "Tactically, we want to make sure the devices are available for every network on the planet." For now, that means that the Nexus 4 will only be available as an unlocked HSPA+ device. Whether the fault lies more with carriers for forcing Google?s hand or with Google for refusing to work within the standard carrier model, the end result is a flagship phone that?s missing an essential flagship feature.

  • Like 1

The Nexus 4 has one big disadvantage out of the gate.....it's made by LG, one of the worst manufactures in the world. I would have to think long and hard (and read plenty of positive reviews) before I would buy one.

which is sad because LG used to make great dumb phones

which is kinda ironic actually because it used to be Samsung that got bashed for having crappy phones in the dumb phone age :rofl:

anyway, from all the specs and news about the Nexus 4, for whatever reason the Galaxy Nexus still sounds more appealing :/

Is this for all the new Nexus devices? Or just the one LG is releasing?

the one LG is releasing will be called the Nexus 4 to go along with googles new naming scheme of their devices (4", 7", 10")

The Nexus 4 has one big disadvantage out of the gate.....it's made by LG, one of the worst manufactures in the world. I would have to think long and hard (and read plenty of positive reviews) before I would buy one.

google wouldn't put all their weight behind a crappy phone, its their flagship device. LG may have in the past made some not so great things, but if they want to work with google on this they wont get away with it.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!