Galaxy Nexus Software Updates and Bug Fixes
Early problems and fixes
Soon after launch, owners reported a list of issues, though not everyone saw them:
- Weak rear speaker. Users recommended the Volume+ app, and some custom ROMs added volume tweaks.
- Off-white colours. Compared with other phones, white backgrounds had a tint. Some ROMs and kernels let users adjust colour.
- Random reboots and signal drops. The author’s were fixed by flashing the official 4.0.2 factory image, though others still saw them less often.
- Battery life. Complaints were common on forums.
- Update source. It was unconfirmed whether Telus and Rogers models relied on Samsung rather than Google for updates.
The author called it a great phone but said returning one to a big carrier meant a lot of red tape.
The volume glitch
A volume bug showed up on the UK release. Google and Samsung both acknowledged it, Google promised a fix without a date, and Samsung held back shipments to retailers. The problem was tied to the 900 MHz 2G band common in Europe. Canada uses 850 MHz for 3G HSPA, so the hope was that Canadians would be spared, though that could not be confirmed until the phone launched.
Flash and AIR
Adobe said the phone did not initially support Flash Player 11.1 and AIR 3.1, because partner devices ship on different schedules. A minor runtime update for the Galaxy Nexus was promised for December.
Android 4.0.2 rollout in Canada
Bell, Telus and Rogers released the 4.0.2 over-the-air update. Owners who updated found NFC missing and the Android Market crashing almost at once. A factory reset after updating brought NFC back and ended the crashes, and for unrooted users it was the only fix.
Rogers pushed 4.0.2 months later, around when Jelly Bean talk began. One reader first advised against it, then reported that 4.0.2 was the precursor needed before the 4.1.1 update arrived. The NFC functions were still reduced six months on.
Forcing an update check
- Open Settings, Apps, All, find Google Services Framework and clear its data.
- In the dialer enter ##2432546## (the keys spell checkin) and wait for the message that check-in succeeded.
- Go to Settings, About phone, System update and tap check for update.
Android 4.0.4
A changelog for the CDMA Verizon version suggested what the GSM version would get. Highlights: noticeably faster, a fix for the Android OS battery stats bug, better 3G and 4G switching, improved signal strength, a new power menu, faster boot, smoother auto-brightness, camera button refocus restored, multi-touch fix, faster auto-rotate, better browser performance, faster recent apps, camera UI changes, increased volume, keyboard fixes, an updated News and Weather app and improved quick controls in the browser. A flashable Google apps package for 4.0.4 was also published.
Then 4.0.4 was pushed over the air to both the GSM Galaxy Nexus and the Nexus S. Readers called it zippier and smoother, and reports said it held over 100 changes from 4.0.3. CDMA plans were unknown. A follow-up minor update kept 4.0.4 but raised the build from IMM76D to IMM76I. Owners said it fixed intermittent signal loss and a lock screen lag with auto-brightness. As with all Nexus updates, delivery varied by carrier and could stretch into May.
Jelly Bean and later
Android 4.1 Jelly Bean rolled out to HSPA+ Galaxy Nexus phones, with Google Now and updated Voice Search as highlights. Canadian owners saw it later, and one reviewer who compared two phones said Jelly Bean made speed and fluidity far better. If no notice appeared, the advice was to check settings manually.
Android 4.2.1 came to Canadian Galaxy Nexus phones carrier by carrier: Rogers, with Fido expected to follow, and the regional carrier Videotron. CyanogenMod 10.1-m2, based on Android 4.2.2, offered the newest Android on many devices before carriers did. It was not a stable release, and the supported list included the Galaxy Nexus models, Nexus S, Nexus 7, Nexus 4, Nexus 10 and many Samsung, HTC and LG phones.
Legal pressure
After a US court granted an injunction at Apple’s request over a universal search patent, Google and Samsung planned a firmware patch to keep the phone on sale. Google said it would support Samsung’s appeal and challenge the patent.
Nexus S
Google said the Nexus One hardware was too old for Ice Cream Sandwich, so only unofficial ROMs would reach it. The Nexus S was promised the update within weeks, and the T-Mobile model had received an update that was pulled over overheating and battery issues. Later 4.0.4 reached the GSM Nexus S.
Frequently asked questions
How did owners fix the missing NFC after 4.0.2?
A factory reset after the update restored NFC and fixed the Market crashes.
What did the IMM76I build fix?
It stayed on Android 4.0.4 and reportedly fixed signal drops and lock screen lag.
Was Canada affected by the volume bug?
The bug was tied to the 900 MHz band used in Europe, so Canada was expected to be spared.
Did the Nexus One get Ice Cream Sandwich?
Not officially. Google said the hardware was too old.