GNSS: Subtle Improvements

Section by Brian Klug

Like the iPhone 4S and the iPhone 4 CDMA before it, Apple has gone with the GNSS (Global Navigation Satellite System) leveraging both GPS and Russian GLONASS which lives entirely on the Qualcomm baseband. In the case of the iPhone 4S and 4 CDMA, that was onboard MDM6610 and MDM6600 respectively, both of which implemented Qualcomm’s gpsOneGen 8 with GLONASS tier. Going to on-baseband GNSS is really the way of the future, and partially the reason why so many of the WLAN, BT, and FM combos don’t include any GNSS themselves (those partners know it as well). In this scheme GNSS simply uses a dedicated port on the transceiver for downconversion, additional filtering (on RTR8600), and then processing on the baseband. The advantage of doing it all here is that often it eliminates the need for another dedicated antenna for GNSS, and also all of the assist and seed information traditionally needed to speed up getting a GPS fix already exists basically for free on the baseband. We’re talking about both a basic location seed, precision clock data, in addition to ephemeris. In effect with all this already existing on the baseband, every GPS start is like a hot start.

There was a considerable bump in both tracking accuracy and time to an assisted GPS fix from the iPhone 4 which used a monolithic GPS receiver to the 4 CDMA and 4S MDM66x0 solution. I made a video last time showing just how dramatic that difference is even in filtered applications like Maps.app. GLONASS isn’t used all the time, but rather when GPS SNR is either low or the accuracy of the resulting fix is poor, or during initial lock.

With MDM9615 now being the baseband inside iPhone 5, not a whole lot changes when it comes to GNSS. MDM9615 implements gpsOneGen 8A instead of just 8, and I dug around to figure out what all has changed in this version. In version 8A Qualcomm has lowered power consumption and increased LTE coexistence with GPS and GLONASS, but otherwise functionality remains the same. MDM9x25 will bring about gpsOneGen 8B with GLONASS, but there aren’t any details about what changes in that particular bump.

I spent a lot of time playing with the iPhone 5 GNSS to make sure there aren’t any issues, and although iOS doesn’t expose direct NMEA data, things look to be implemented perfectly. Getting good location data is now even more important given Apple’s first party turn by turn maps solution. Thankfully fix times are fast, and getting a good fix even indoors with just a roof between you and clear sky is still totally possible.

Cellular Connectivity: LTE with MDM9615 WiFi: 2.4 and 5 GHz with BCM4334
Comments Locked

276 Comments

View All Comments

  • A5 - Tuesday, October 16, 2012 - link

    He said pretty clearly and repeatedly that all browser tests on Android were run in Chrome.

    Rooting the phone to install a new kernel to improve benchmark scores would be insane. That's like asking why he didn't overclock it, too.
  • edsib1 - Tuesday, October 16, 2012 - link

    But his benchmarks scores are all crap.

    My HTC One X (Tegra) with official 4.04 RUU gets 1684 compared to 1131 in Anands tests.

    Something is seriously wrong with his testing.

    It should also be pointed out Geekbench has errors. It reports memory sequential reads for android devices incorrectly.
  • doobydoo - Friday, October 19, 2012 - link

    Dunno why you're even talking about Geekbench.

    Anand has noted several times that you can't use it to accurately compare cross platform.
  • Kidster3001 - Monday, October 22, 2012 - link

    umm, you do know that for Kraken and Sunspider... lower is better.
  • Spunjji - Friday, October 19, 2012 - link

    I agree that rooting the phone and installing a new kernel for benchmarking is silly, but at least having up-to-date figures for a phone known to have received significant performance increases since its release would be a nice idea. This chap's numbers certainly make the phone look very different in terms of attractiveness.
  • Kidster3001 - Monday, October 22, 2012 - link

    I also believe you will see better browser performance from the highly customized Intel Android browser than you will from Chrome for x86 Android.
  • Krysto - Tuesday, October 16, 2012 - link

    Something seems very wrong with RAZR M. It uses the same S4 processor as One X, has smaller 4.3" screen, has lower qHD resolution, bigger battery, and yet it still significantly underperforms the S4-based One X in Sunspider performance, in battery life, and other stuff as well. That shouldn't happen, and it seems like the issue is some very sloppy software that Motorola put on top of the RAZR M hardware.
  • Arbee - Tuesday, October 16, 2012 - link

    Yes, it's called Motoblur ;-)
  • Spunjji - Friday, October 19, 2012 - link

    I thought they killed Blur already? :/
  • magnimus1 - Tuesday, October 16, 2012 - link

    Thanks! This was one phone I was waiting for. The other one I want to see is the Motorola RAZR i. Do you guys have any plans to review that?

Log in

Don't have an account? Sign up now