Seems like everyone else that has a handset with the name "Nexus" is getting updated to 4.0.4. Why am I not surprised that Verizon customers are getting left out in the cold? Yes, the CDMA version is different than the GSM but damn it why the hell can't we get anything to go right with this phone. I don't care if the problem lies with Google, with Samsung, or with Verizon. I just want the damned update pushed out so I can see if it fixes my phone. If it does, great. If it doesn't then I guess I'll enter the realm of the "Certified Pre-Owned" world.
<word filter avoidance> you Verizon and your great network. <word filter avoidance> you Verizon and your always cheerful customer service people. If only every other part of Verizon sucked as bad as my experience with this phone then I could justify switching to another carrier.
http://www.engadget.com/2012/03/28/android-4-0-4-rolls-out-to-hspa-galaxy-nexus-and-gsm-nexus-s/
Message was edited by: Verizon Moderator
Wow You seem really worked up over the amazing features the 4.04 adds, like Quicker screen rotation
..
...and the signal fix, the wifi reboots, the text lag, javascript, the volume, etc.
I believe it would be Qualcomm patents also the Nexus S 4G, and the CDMA panda board iirc isn't getting the update...
You crack me up...even IF youre right....LMAO
Who cares about Qualcomm!! Fix the phone!! Just dont know who to tell to fix the phone!!!! LMAO
Too funny! And tragic...
Carseller! Get the certified! Either way, you'll get covered and if it doesn't fix mine, i was promised a new model! I'm thinkin' a Razor Maxx if it comes to that....though i hope it doesn't!!
fastearle86 wrote:
You crack me up...even IF youre right....LMAO
Who cares about Qualcomm!! Fix the phone!! Just dont know who to tell to fix the phone!!!! LMAO
Too funny! And tragic...
Carseller! Get the certified! Either way, you'll get covered and if it doesn't fix mine, i was promised a new model! I'm thinkin' a Razor Maxx if it comes to that....though i hope it doesn't!!
Zzzz of course you wouldn't. You don't know the complexities and don't care for them. I work around these types of field and know more about the inner workings. By the guys statement saying why are we getting is last is completely wrong as there are other devices that don't have them.
You know, personally, i dont think you want anyone to understand...
I think you just like to argue....
Most of what you are saying doesnt really have any relevance to anyone in here except you and those that want to argue...
I got caught up in it, then resolved my issue without you or any..wait, one more time, ANY suggestions from you that were meaningful... If you think about it, you know im right
Also, this all comes back to what many, including me have all said, Verizon, whether they really are or not, ARE acting responsible when confronted as i did....
You are just throwing a buch of smoke screens and crap that doesnt really help anyone when people are looking to someone like you for help? You must have a pretty boring life to live in here and have no vested interest....(Which i don't believe)
Take care...go to the beach or something...lol
fastearle86 wrote:
You know, personally, i dont think you want anyone to understand...
I think you just like to argue....
Most of what you are saying doesnt really have any relevance to anyone in here except you and those that want to argue...
I got caught up in it, then resolved my issue without you or any..wait, one more time, ANY suggestions from you that were meaningful... If you think about it, you know im right
Also, this all comes back to what many, including me have all said, Verizon, whether they really are or not, ARE acting responsible when confronted as i did....
You are just throwing a buch of smoke screens and crap that doesnt really help anyone when people are looking to someone like you for help? You must have a pretty boring life to live in here and have no vested interest....(Which i don't believe)
Take care...go to the beach or something...lol
I think you guys don't want to understand or even trying to understand what I am saying. People are always complaining about this or that to Verizon or any carrier for that matter about their devices not working right. By blaming Verizon you are giving a free pass for what manufacturers are not doing. Verizon didn't make the device. Sure Verizon CAN help you out, but it furthers allows manufacturers to cheap out.
I am trying to open your eyes, and debunking misconceptions about things people think are true for example AOSP support, "pure Google experience"...
Cheap out? hows that? Samsung cheap out? Maybe, but, Verizon told me...and I quote "We test everything to Verizon Standards and if they don't pass, we don't sell" That being said, let them cheap out...If they do, sounds like they wont sell phones to Verizon...
The standard person, IE: Me, doesnt have time or the desire to debunk or learn all the ins and outs of whatever device and whoever is responsible or any of the things that you are talking about.
I will not buy into what you are selling simply because it doesnt matter as long as Verizon is willing to rectify the issue to the user. Again, IE Me. The rest is just fluff and crap...
I get where you're coming from but its useless to most..well, almost all and i can appreciate that you know all these details. Truth is, like you already said, i don't care about them, I care about me and considering i pay twice, at least, what the other guys charge, its the least they can do and the funny thing is.....The support tech agreed saying "You do pay more money and you get better support for it." end quote. That is all i need to hear. Not saying it will work for everyone but still....
so far about 90% of the "updates" you guys are hoping for should already be working now.. my buddy has the nexus and he hasnt had any of the problems in this thread
I did, then called Verizon and got a new one. One week in and works fine so far. My advice will be, contact verizon support asap and let them know how you feel. I didnt have to get angry, just told them what was going on. Ultimately if this doesnt work, i can pick a new model phone.
At least it worked for me but some in here would say i know nothing... about inner workings? Nope, but who cares!! lol
If that's all this update addresses then I will be worked up. I'd just like to be able to send and receive picture messages with some consistency, hear my phone when it rings, and be able to determine when my phone shuts off.
In addition, this update should make the USB port on the GNex useful for something other than charging. USB I/O is broken under 4.0.2.
Been waiting since the day I got my phone, which was the day it came out. Not impressed at all; I don't care WHO is responsible for getting the OTA out.
-- Sam
I transfer files all the time using USB on my Nexus.
On 4.0.2? If so, you're one of the lucky few, it seems. USB timeouts have been plaguing the GNex since product launch. http://androidforums.com/samsung-galaxy-nexus/465494-known-issues-galaxy-nexus.html item #1.
Still waiting for my update, less patiently every day...
-- Sam
The USB timeout is an actual issue with the Galaxy Nexus? Then I might be experiencing that problem. I didn't connect my Nexus to a computer via USB until a month after I had it. I thought it was a bad cable. The HTC cable worked much better than the supplied Samsung cable. The HTC cable wasn't perfect either just better. I was able to transfer the files I needed.
I still haven't ruled a bad USB port on the computer.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
Its the cables or drivers in most cases. Most people want to blame the phone which requires a removal and reinstall to the drivers, or a new cable. Both my GSM and CDMA cables were bad when I got both Nexus.
My wife's laptop I had to turn UAC off for the drivers to install correctly. My server and my desktop had no trouble.
Actually, no, that's not the case.
Some people have experienced difference in operation with different cables. But it goes back to the issue being intermittent; What works with "cable a" one day won't the next, but might work with "cable b", which then won't work two days later.
If it's weren't a GNex/Android issue there wouldn't be an open issue on the Android Development site, with several thousand "me, too!"s.
It is said the problem is fixed in 4.0.3, and continues to be fixed in 4.0.4 and 4.0.5. I have been working closely with a developer who has been tracking the issue and trying to work around it.
-- Sam
That's a driver issue. I said this months ago. Turn UAC off and see if the drivers install correctly. I won't go into detail why it's not the device as most people won't read it.
Windows XP. No UAC.
Using the latest driver (ver 1.4.6.0, 13-Dec-2011) from Samsung.
Just Google the issue and you'll see lots of info about it. It is an Android 4.0.2 issue.
-- Sam
If you say so. Let me know when the update happens and it doesn't fix your problems. 4.0.4 is already out Basically in more than one way.
FYI if you go through most of those Google searches most of them solved their problems going to a different computer and it works without a hitch 99% of the time. Some have fixed their problems by changing their cable or uninstalling their drivers the right way and reinstalling them.
Seems like it's not a problem with the device software and more about hardware whether it's the computer the cable or the port.
Start a new topic or ask questions in the open forum.
