According to this leaked document from a while back, the first VZW Nexus update was supposedly coming out in "middle to late January". With only a couple of days left of January and not even a rumor of an impending update, should we now expect it to be sometime in February instead?
Device(s): Galaxy Nexus rooted & ROMmed, OG Droid (retired)
Carrier: Verizon
Thanks: 1,936
Thanked 6,097 Times in 2,803 Posts
There are any number of 4.0.3 ROMs out there based on AOSP, so Google is certainly close to refining it enough to push out to stock devices. If you were in the mood to root & ROM, you could have it now. I prefer to stay stock, so I get to wait. As far as a timeframe? None given.
The only problem with using a 4.0.3 custom rom (which i am ) is your not getting any updated radio drivers or anything like that. Which is what most of the people are after in this next update.
__________________
I used to be Android all the way but bought an Iphone 5 in October. Feel free to ask me how it's going via PM.
GO BRONCOS AND ROLLLLLLL TIDE!!!
The only problem with using a 4.0.3 custom rom (which i am ) is your not getting any updated radio drivers or anything like that. Which is what most of the people are after in this next update.
However you can easily flash any leaked radio in about 3 seconds. I've been running the 4.0.3 radios since the beginning of my rooting, they are marginally better at wifi to data handoggs but nothing major.
If the leaked 4.0.3 radios are any indicator, the radios are crap anyway.
The leaked radios are way better than the EK05/02 radios were on launch, improved handoffs at least for me in my area so dont know if you just live in the boondocks or what.
As for the update if you need it that bad the radios and AOSP roms with 4.0.3 base including a stock build is already out. I guess if you have to be "official" you can keep waiting.. by the time the next update drops heck they might even scrap 4.0.3 go right to .4 but of course who knows its easier to just check forums for a zip and flash it yourself, youve got the developer phone after all , OP!
My guess is that they're waiting until everyone who initially bought the Nexus has kept it past any possible return date so that when the first update doesn't fix the connectivity issues everyone's been experiencing, they don't get swamped with returns.
The Following User Says Thank You to LandLockedPH For This Useful Post:
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,306 Times in 762 Posts
Quote:
Originally Posted by LandLockedPH
My guess is that they're waiting until everyone who initially bought the Nexus has kept it past any possible return date so that when the first update doesn't fix the connectivity issues everyone's been experiencing, they don't get swamped with returns.
My guess is that they're waiting until everyone who initially bought the Nexus has kept it past any possible return date so that when the first update doesn't fix the connectivity issues everyone's been experiencing, they don't get swamped with returns.
Well, isn't it already way after that date?
My guess is they are also implementing other fixes to address OS battery drain, some random rebooting, etc as well as improved radio, so it would take some time.
The Following 2 Users Say Thank You to Sandroidfan For This Useful Post:
Yeah, I guess that would have been it. Mine went back 1/13. Although I loved many aspects of the Nexus, I needed phone connectivity first and foremost.
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,306 Times in 762 Posts
Quote:
Originally Posted by LandLockedPH
Yeah, I guess that would have been it. Mine went back 1/13. Although I loved many aspects of the Nexus, I needed phone connectivity first and foremost.
Yep, you gotta do what you gotta do, and everyone has different requirements. I hardly use the voice part of my cell phone, but what I have used of it hasn't had a dropped call. I had the mute bug once but haven't had it happen since then. I think the mute bug is a software thing anyway.
My only issue at this point is the splotchiness in video, but I'm just reading more on my kindle at night instead of watching videos so it hasn't bugged me too much.
My biggest issue had been the phone freezing up when I make or receive a call. Happens several times a week. Just can't decide on what custom room to run. I wanted to wait until CM9 was ready but I dunno if I can wait. Anyone have any suggestions?
Sorry to be repetitive, but not everybody reads every thread. I've been having awful reception issues with my original and replacement GNex. I finally started squawking louder to customer support and they started a trouble ticket for my reception issue. Today I ran several speed tests and called Tier 2 support to report my results and have them added to my trouble ticket. What I was told (again, by a Tier 2 support tech) is that they are aware of the Galaxy Nexus reception issue throughout their network and that an update to specifically address the reception issue is "coming in March". He did not have a specific date. He gave me the explanation that they have notified the manufacturer and the manufacturer will come up with a fix and release it to VZW. You don't say?! <sarcasm intended>
Take it for what it's worth folks. After all this time time dealing with poor reception at home and at work, I think I'm most irritated with Google. Their silence through what is obviously a real problem with reception ticks me off. I mean, this IS a vaunted Google phone, right? Where's the friggin' support this thing is supposed to get? At least tell us there is a fix in the works. I'm not saying fix it tomorrow, just tell me you know there is a problem and you're at least interested is trying to fix it! I'm so frustrated.
The Following User Says Thank You to red66charger For This Useful Post:
Agreed. He said something like, "I see there's an update coming in March". I don't recall his comment verbatim, but I was definitely under the impression he was reading it from somewhere. It could have been an act, but he repeated it a second time before we ended the call. The one thing I appreciated from this guy is that he didn't treat me like I was a moron. He understood I read the blogs and message boards and that I had enough knowledge of the device to know it's not functioning as advertised.
I was very disappointed he didn't say an update was coming in February. He explained that once they receive enough complaints about an issue, and it indicates it's not just isolated problems, they report the complaints to the manufacturer who then develops a fix. I suppose I can see VZW waiting a month before calling in Samsung, but wouldn't Google be even more pro-active and motivated to get a fix than even VZW? Plus, I would imagine Samsung already monitors their newly released devices along side the carriers. This is why I've said, I had inflated expectations of what a Nexus is. Seems like it's just another VZW phone, albeit without the bloat. C'mon Google, give us something.
The lack of docks and a real car mount that uses at least docking ports (doesn't even have to be the 3 pins on the side) is really making me angry.
The Droid Maxx had a real car mount and multiple docks avail on release day.... grrrrr.
Yep, completely share your grrrrr Definitely agree.. both the car & desk docks should absolutely have been available at release - would have been profitable for Samsung/VZW as I'm sure many, including myself would have snatched them up!
The only promising glimmer of hope - the upcoming release on Sprint/other carriers will broaden user base & demand for accessories.
I really have started to wonder if the reason Verizon commissioned the non-pogo pin car dock was because Samsung told them the pogo pin one wouldn't be ready in time for launch, and Verizon wanted to avoid not having a dock at launch.
__________________
Site Rules & Guidelines
Got some help? Hit Thanks!
See something you like? Hit Like!
See something you hate? Hit Report!
If it's any consolation, my VW customer service rep (with whom I spoke after calling to complain about 4G) told me yesterday that the update appeared to be scheduled end February. Then I got elevated to tier 2 support and he mentioned that it would be in about 1-2 weeks. FWIW. In the interim, tier 2 suggested that I stay on 3G for a couple days and then try 4G again to see if it settles down a bit. He was VERY well aware of the issue and said that they are awaiting a repair to update release. Indeed, if I stay on 3G, things seem to work better so I only turn on 4G when I need it.
The Following 2 Users Say Thank You to nycebo For This Useful Post:
Hopefully this will help things. Honestly I get great 4G so Im not super concerned...its just the hand off for when I go into work and when Im out and about. I have no problem rocking 3G for now though, the phone is still amazing even with slightly less network speed. Besides I dont do any REAL heavy data intensive tasks. Its mainly surfing the web and facebook
__________________
Aloha, Im Matt and I love life.
HP Touchpad with CM7
HTC Incredible 2 with Sense 3.5
Galaxy Nexus LTE stock
Galaxy Note I717 LTE stock
I'm also staying with 3G most of time and turn on 4G only for big downloads, streaming, etc. It's pretty solid in 3G. Even on 3G, browsing in Nexus blows away other 3G phones easily. But they really need to release update to 4G firmware for better connectivity in less than good areas.
@jinwons, better connectivity in less than good areas is exactly it. Mind you, I've also had connectivity issues with 4G even when I'm on all 4 bars. It's just frustrating as heck. So, I'll give it some more time, hope for a fix and then decide from there.
You're gonna have to excuse me for being extremely doubtful of this claim, you're the only person I know of who has received it, and build props are really easy to change.
The Following User Says Thank You to zerocool79346 For This Useful Post:
Device(s): Currently have: Razr HD and many other Android devices
Carrier: Verizon
Thanks: 165
Thanked 293 Times in 235 Posts
Quote:
Originally Posted by suXor
How bout you go look at the history of my posts over on the Fascinate section to see if I am a liar...
Sorry but the second 4 in 4.0.4 looks photoshopped. Might be an optical illusion, but it looks like it was masked from the other one, and then pasted in as viewed on my IPS calibrated monitor.
Instead of saying, "look at something that you have to search for...." why not just distinctly prove that you have 4.0.4 for a SGN?
Sorry but the second 4 in 4.0.4 looks photoshopped. Might be an optical illusion, but it looks like it was masked from the other one, and then pasted in as viewed on my IPS calibrated monitor.
Instead of saying, "look at something that you have to search for...." why not just distinctly prove that you have 4.0.4 for a SGN?
Device(s): Currently have: Razr HD and many other Android devices
Carrier: Verizon
Thanks: 165
Thanked 293 Times in 235 Posts
Quote:
Originally Posted by suXor
How do you suggest I do that?
I'm not saying you don't have it, I'm just playing the role of the skeptic!
Well, engineers are skeptics to begin with
I did see a post in your history at a cursory look where you commented on how an update got out in response to a failed feature. Presumption is that you work for VZW or an affiliate that is related.
Bottom line is that I hope we all get updates very soon for some, if not all, of the common problems.
so the rumored .10 baseband does exist if Im to believe that SS, but what is up with those radios?? same prefix on both the LTE and CDMA whereas the olders were EK and different ... if it is true really hope they fixed that Android OS reporting bug
I'm not saying you don't have it, I'm just playing the role of the skeptic!
Well, engineers are skeptics to begin with
I did see a post in your history at a cursory look where you commented on how an update got out in response to a failed feature. Presumption is that you work for VZW or an affiliate that is related.
Bottom line is that I hope we all get updates very soon for some, if not all, of the common problems.
Not VZW, but certainly in the know. However, I got the OTA update, I didn't manually do it. It was around 25MB.
Device(s): LTE Galaxy Nexus (AOKP b37); Dinc (CM 7.1) [retired]
Carrier: Not Provided
Thanks: 957
Thanked 1,306 Times in 762 Posts
Quote:
Originally Posted by syntrix
I'm not saying you don't have it, I'm just playing the role of the skeptic!
Well, engineers are skeptics to begin with
I did see a post in your history at a cursory look where you commented on how an update got out in response to a failed feature. Presumption is that you work for VZW or an affiliate that is related.
Bottom line is that I hope we all get updates very soon for some, if not all, of the common problems.
Hmm, if the 4.0.4 (or 4.10 or whatever it becomes) has a lot of reports of improved 4G/radio performance or battery life, etc, I may just have to flash back to the stock to get the update Not sure how long it'd be after an OTA from VZW/Google that AOKP would have a new milestone build...
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
No rumblings of an update yet?
LOL
instead of a retort.
