I was sooooo expecting to see a youtube link to someone following turn-by-turn into a lake or something :P
Thankfully, I have had no issues. I assume you're using Google Nav? Is it during anything else, like when a text comes in or something? Only thing I can think of, would be try clearing the data for the nav app in your settings, or also try downloading and running another nav app (like mapquest or whatever), and see if it happens with that one as well. If not, you may want to check with customer service to see if they've had other reported issues (it doesn't sound too familiar - I don't remember reading too many cases of it). It's also perhaps something that the 4.0.3 might fix regardless, but trying to get to the root of the issue would be good anyway. Also, is a factory reset doable for you? If another app, or clearing data don't have any effect, it'd be the "last resort" thing to try before replacing the phone.
A roadtrip thru rural flatlands and hill-country with the Nexus
I've driven this route down many times and it takes me thru several areas in rural OH,IN, KY, and TN with a wide variety of Verizon coverages. There is a large dead area I drive thru that always rendered the Original Droid useless. The dead region was so large that if used for navigation, I would drive "off the map". It was not just a lack of data, but a total lack of signal. Not even voice. This was true as of late August 2011...my last drive thru the area prior to this trip.
Nexus and Signal
-The dead zone was NOT A PROBLEM FOR THE NEXUS! Not only did I maintain navigation ability at all times, I never lost voice and only lost data for a few minutes. Never long enough to empty the map buffer. -Vast majority of the route had usable 3G. -Indianapolis had good 4G as I drove by on I-65 and I-69.
Nexus is one hard worker
The Nexus was always doing at least double duty as navigator and media server. Most of the time it was doing triple: nav, music, & torrent.
At one point the Galaxy Nexus was simultaneously giving spoken turn-by-turn nav, streaming music thru bluetooth, downloading 4 movies, and wirelessly tethering internet to both an iPod touch and a laptop PC!
While the sheer amount of data moving thru the poor thing was enough to occasionally cause the music to skip briefly and the data was split into a near-useless streams, the phone never overheated, rebooted, or FC'd any app. Every function remained completely stable and usable.
Nexus for the long haul
At one point I managed to go 27 hours without a charge. CDMA only, but LTE was all I sacrificed during that stretch. Obviously, this was essentially all idling. A few texts and time-checks during that, but not else. Regular use was worry free and without restriction thanks to one extra battery and external charger. Even with the heaviest phone use the charger could easily refuel a spent battery before I needed to swap.
Device details
LTE Nexus GummyNex 0.3.0
Apex 1.35 kernel using the default voltage
4.0.3 baseband
Nova Launcher Beta 5
No other mods or tweaks.
Device(s): Galaxy Nexus rooted & ROMmed, OG Droid (retired)
Carrier: Verizon
Thanks: 1,963
Thanked 6,142 Times in 2,826 Posts
I have used Google Nav for short test trips and TWO 6 hours big trips. Not a hiccup. No crashes or loss of signal. Hope that gets working for you, as I find it indispensible
@ asmallchild: I would like to confirm CharlesO's suggestions, however it does sound like it really could be a hardware issue. I would try a factory data reset and if that doesn't fix it, then there is a one year warranty from Samsung for this device; I would use it.
good luck
__________________
If you are helped by one post, hit the "thanks" button.
If you are helped by a whole thread, hit the "like" button
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,308 Times in 763 Posts
Happened to me when I had my Nexus. It was the one and only lockup I had. Didn't have the phone long enough to do exhaustive testing I was NOT prepared to conclude anything after just one incident. :-)
This happens to me all the time. My phone (Thunderbolt) just powers off. I called Verizon and they acted like they had never heard of this problem. Sent me a replacement phone which sucked battery big time, so I sent them back their phone and kept mine. Turns out it seems to be a Google Navigator problem. I use Waze without any issue at all. I like Google Navigator, but don't like it powering down my phone randomly.
I used the nav once on a trip and had 2 reboots during the 2+ hours I had it on. Have not used it since, so never investigated it further. Have never had a reboot except those 2 times so I assume it had something to do with the nav app.
My VZW Galaxy Nexus reboots allllll the time when I'm using Nav...usually when I need it the most. It usually requires at least one battery pull to get it back to normal.
The Galaxy Nexus is the third official phone contracted by Google and the first phone to come with Android 4.0 Ice Cream Sandwich. Specs include a 1.2GHz dual-core processor, 1GB of RAM, 16/32GB of internal storage, a 4.65 inch 720p HD Super AMOLED... Read More
crashing while navigating?
I was NOT prepared to conclude anything after just one incident. :-)
