- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
that's a Good one Pool..b33
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Again they made no distinction what so ever in that claim. To not make the distinction is a lie in the whole. Where did they say carriers would have to make approvals before releasing any update. They could have been forthcoming from the start.
Again, they made a distinction on that. It was specifically said who wrote the code and how it would be pushed to users. You added in the part where there wouldn't be any quality testing approval. Every carrier has to do that with carrier released phones. In fact, I believe that is a part of federal guidelines, and it's said that Verizon takes their testing further than any other company, though I've never seen better results.
Again as I have pointed out Google lied up front about it or left detailed information. If Google was upfront about it may less people would have bought the Nexus. Think about it... They lied from the get go to ensure sales...
If Google, Verizon, Samsung, AT&T, T-Mobile, LG, etc...were upfront about every detail with any of their phones, we probably would not have bought any of them. Google was upfront with how OTAs would work from them on the Nexus.They told you who wrote it and where it would be pushed from. It's naive to think that a carrier released phone would not go through quality testing by the carrier (on any carrier), but Google never stated that it wouldn't.
The problem in 4.0.4 bug is tied to WIFI and BT turned on at the same time for a period of time. Regardless if you turn them both off, or turn off your device will never sleep. Once you revert back to 4.0.2 it'll go away.
Do a search on that problem. You'll find that the same problem has been mentioned as early as 4.0.2 for other people as early as December.
I have not said I was the end all be all when it comes to fixes. I am pointing out what I have seen, and what I see in bug reports and log cats. Not a he said, what he things type of deal. Seems like you are defending Google without thinking about what they leave out.
And I am pointing out that people should be asking Verizon about the update if they want answers to their questions about an update to their Nexus, since every other Nexus device has one except ours. I understand that you see bugs and log cats, but that does not change the fact that every other Nexus has an update except the Verizon Nexus. You keep mentioning the bugs, but that does not answer why every other Nexus device has this update besides Verizon, unless Verizon is the entity stalling this update. Verizon should be making it clear if this is the problem, and it should be doing so as quick as possible. And you of all people should know better than to accuse someone of blindly defending a company on these forums. There are plenty of people on these forums that have accused you of doing the same for Verizon. I'm not going to bat for Google on this. Google has been failing us as far as timely updates for our Nexus devices. It's a frustrating deal, but in this case where people are wondering why they haven't had an update to their Nexus device, they should be asking Verizon because Google released an update. An update that has hit all Nexus devices (CDMA or GSM) except Verizon regardless of whatever bug.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hopefully this debate is over.
Soooooo, about that Galaxy Nexus 4.0.4 update that you are all waiting for – is it ready to roll out as build IMM76K? According to one of our readers, the update appeared for installation this morning on a replacement phone that he picked up over the weekend. He claims to be running stock Android 4.0.2 and to not be rooted.
As anyone in this business knows, readers try to deceive blogs all of the time, but the date on the kernel, the brand spankin’ new radios, and the newer build number over any other Galaxy Nexus including the Sprint and GSM versions, leaves us to believe that this may be real after all. We keep hearing “early May” for a release of this update and being May 1, that certainly matches up. The odd thing here is that he is the only one to have mentioned it, anywhere, on the internet.
Stay tuned for more. And be sure to check your phone immediately and throughout the day to see if you are prompted as well.
Update: After hitting “publish” on the post, another reader received the same update.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well...It looks like the wait may be over soon. There are reports that some Verzion Nexus have received 4.0.4 earlier today, and that Verizon should be rolling out the update. So keep your fingers crossed if you've been waiting for this. And if it's packed full of bugs, then no complaints (like that will happen) cause we asked for it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You beat me to it Pool_Shark...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Bartley wrote:
Again, they did say that. That has been how it's been from the moment any Nexus was released by a carrier and not straight from Google because the Nexus devices released by carriers had carrier support, and no carrier is going to release a phone on their network without quality testing approval. You think they lied to you cool, but I've read the way it works and understood it. You didn't. I didn't add anything. They said the code would be written by them (I stated that) and they said it would come from their servers (I stated that). Just like any of their other Nexus devices. See no tidbits added there. When did they say that there would be no carrier approval for updates on a carrier released Nexus?
They did NO SUCH thing until MONTHS after the sale of the device. When did they say BEFORE the release of the device that there would need to be carrier approval? They said they will treat it like our OTHER Nexus devices. OTHER being Nexus One, Nexus S, and Galaxy Nexus. Which of these need carrier approval? Think about it... Then months later(more like less than a week ago) JBQ says something about carrier approval.
Listen, Google pays me nothing. I have no Google stock. I think they should be releasing updates at a faster rate than they are and have been too engaged in a childish game with Verizon and are as much to blame for Nexus users frustrations. But, at this point for those people who are wondering about an update as referenced in this forum's title, they should be directing questions to Verizon, because an update has been release for every other Nexus besides this one.
Childish games? You know the leaked and the "recent" news about people getting the 4.0.4 update are completely different? They are also different than the one Sprint currently has and their "update" fix is completely different build as well?
There is a fix/ workaround (should have put the workaround there). I never said an official fix. And there have been reports of an awake bug as early as 4.0.2, not just 4.0.4. And it was at the kernel level. Many have blamed Android OS for this happening on the NEXUS S and Verizon Nexus and other devices. And dude, you aren't the end all be all to discovering fixes. And FYI, I never said Google fixed it. I said there has been a fix in forums for a while. Do your homework dude. Anyone reading this, just do a search on 4.0.4 version of Android OS. Most people are reporting longer battery times as opposed to shorter battery times when switching to 4.0.4.
Do your homework. They are DIFFERENT bugs. Learn what the 4.0.2 bug was, and what the 4.0.4 bug is. Just because the effect is similar doesn't make it the same. A cold can give you "flu like" symptoms which we all know a cold isn't the flu. What was happening in 4.0.2 was different than what was happening in 4.0.4.
Most people are reporting longer battery times because of what so they account for everyone on the internet who installed 4.0.4? We didn't include people who finally got it on Sprint and they been having a lot of trouble with their devices. What about those people who don't go on the internet to complain about their problems? Some people may have installed the update but don't say anything about it because well... They'd admit they violated their warranty installing it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Chill......
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sprint Galaxy Nexus got an update today, 11 days after launch.
http://www.engadget.com/2012/05/01/sprint-galaxy-nexus-updated/
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You forget we got 4.0.2 update on release day... I wouldn't praise Sprint just yet.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
They did NO SUCH thing until MONTHS after the sale of the device. When did they say BEFORE the release of the device that there would need to be carrier approval? They said they will treat it like our OTHER Nexus devices. OTHER being Nexus One, Nexus S, and Galaxy Nexus. Which of these need carrier approval? Think about it... Then months later(more like less than a week ago) JBQ says something about carrier approval.
And it has been treated as such. The Nexus was never a carrier release phone, Nexus S had to go through the process, and Galaxy Nexus on Verizon has to go through that process. GSM version in the US is not a carrier phone. Besides as I've stated, they never promised you the Tidbits that you keep rambling on about. You assumed that much. I've understood it as them writing the code and updating from their servers. You didn't? Too bad.
For everyone that doesn't know, Google builds the system image, boot image, recovery image from their source code. Samsung and Verizon build the radio image. There are several files that need change because of the CDMA network. Google doesn't have the licenses to distribute these files. They must come from Samsung and Verizon. When Google builds a version of Android and tests it, the update is ready as far as they're concerned. Google gives the source code to Verizon and Samsung to make required changes to allow the Nexus to work on a CDMA network. During this period, Verizon quality checks the changes they've made, and their testing according to them is very thorough. When finished, they give the green light for the update to be distributed by Google's servers. So Verizon is apart of the update process, and can be a stalling factor though the source code is written and comes from Google servers.
Childish games? You know the leaked and the "recent" news about people getting the 4.0.4 update are completely different? They are also different than the one Sprint currently has and their "update" fix is completely different build as well?
It is a childish game of "which company is doing what their supposed to do." When neither is. And what do your questions have to do with what I stated? They are different builds but same versions. And the 4.0.4 version was released for all Galaxy Nexus phones besides Verizon. And I posted that before even hearing about recent news about people getting the 4.0.4. Dude, you introduce a lot of stuff into a conversation that has nothing to do with what's being discussed. Google and Verizon have been playing childish games since the announcement of the Galaxy Nexus.
Do your homework. They are DIFFERENT bugs. Learn what the 4.0.2 bug was, and what the 4.0.4 bug is. Just because the effect is similar doesn't make it the same. A cold can give you "flu like" symptoms which we all know a cold isn't the flu. What was happening in 4.0.2 was different than what was happening in 4.0.4.
Most people are reporting longer battery times because of what so they account for everyone on the internet who installed 4.0.4? We didn't include people who finally got it on Sprint and they been having a lot of trouble with their devices. What about those people who don't go on the internet to complain about their problems? Some people may have installed the update but don't say anything about it because well... They'd admit they violated their warranty installing it.
Again, do your homework. I'm glad you know the difference between the common cold and the flu, but have you ever heard of a misdiagnosis. There were countless people at the release of 4.0.2 pointing at WIFI and BT being the source of the problem. There wasn't just one bug with 4.0.2. Everyone's problem/ problems weren't the same. Did you know that there were different strains of flu?
AndI don't know what world you're in now buddy, but people will complain about anything over the internet. You think they're going hold in a major complaint about a bug on their phone because they violated their warranty? And your argument against me now is that most people reporting longer battery times doesn't account for everyone on the internet? Well, those who do have that problem doesn't account for everyone either. That's what I was trying to point out to you. I've heard more good than bad, and I don't believe you or anyone else claiming that someone's going to have a major problem on their mobile phone and shut up about it. It's their mobile phone dude. They're going to try and find someone to help them fix it.