Related
First CTIA announcement was delayed, then later an announcement without carriers or release dates. Two weeks later and till no US carrier release information. Seems odd considering the other recent "super phone" announcements came with carrier information, release dates, and pricing. Also the usual parties have not received production review units which I'd expect by now.
Even announcing puts the brakes on product purchases of competing models. Look how many people withheld purchases of smart phones the entire quarter prior to an expected iPhone release. Why announce and hold if reducing product competition was the goal?
The only thing I can think of is to steal some of Apple's iOS 5 thunder. Show that Google's Android 4.0 is moving forward too even if it's not really ready.
What do you think?
vzontini said:
First CTIA announcement was delayed, then later an announcement without carriers or release dates. Two weeks later and till no US carrier release information. Seems odd considering the other recent "super phone" announcements came with carrier information, release dates, and pricing. Also the usual parties have not received production review units which I'd expect by now.
Even announcing puts the brakes on product purchases of competing models. Look how many people withheld purchases of smart phones the entire quarter prior to an expected iPhone release. Why announce and hold if reducing product competition was the goal?
The only thing I can think of is to steal some of Apple's iOS 5 thunder. Show that Google's Android 4.0 is moving forward too even if it's not really ready.
What do you think?
Click to expand...
Click to collapse
Even I felt it was odd that there is no official US release announcement yet. I just hope the unlocked GSM model gets released this month. I don't mind paying the full price.
I have to admit I would not have been this anxious if I did not loose my Nexus One . It's hard to survive with a 5 year old phone.
vzontini said:
First CTIA announcement was delayed, then later an announcement without carriers or release dates. Two weeks later and till no US carrier release information. Seems odd considering the other recent "super phone" announcements came with carrier information, release dates, and pricing. Also the usual parties have not received production review units which I'd expect by now.
Even announcing puts the brakes on product purchases of competing models. Look how many people withheld purchases of smart phones the entire quarter prior to an expected iPhone release. Why announce and hold if reducing product competition was the goal?
The only thing I can think of is to steal some of Apple's iOS 5 thunder. Show that Google's Android 4.0 is moving forward too even if it's not really ready.
What do you think?
Click to expand...
Click to collapse
Well, Verizon did say we're getting the Galaxy Nexus "later this year"... But that's about the only US release information to date.
US carriers just released the old galaxy S II. They want to actually sell some and not have everyone wait 45 days for the newer / better device.
I think its slightly unnerving that theres quite a bit of silence from Google when they've already announced a date for Europe.
I think its because they're trying to work with carriers this time. Whereas with the Nexus S they clearly didn't try that hard. Part of that is pretty much requiring that they get VZW (thats why they made the LTE version), and the other part is trying to push it to more carriers too.
We'll see. I'm not "worried" about it, just curious.
If by next week we still don't have the LTE version labels released by the FCC, then something is curious.
Aridon said:
US carriers just released the old galaxy S II. They want to actually sell some and not have everyone wait 45 days for the newer / better device.
Click to expand...
Click to collapse
If that is the reason then why announce in the first place. By announcing they are in fact causing a lot of people to wait and not buy the Galaxy S2, myself included.
Aridon said:
US carriers just released the old galaxy S II. They want to actually sell some and not have everyone wait 45 days for the newer / better device.
Click to expand...
Click to collapse
Normal people don't do this. Only nerds do. You're way off base if you think any normal person knows what a "Nexus" phone is, or cares enough to hold off buying a new phone when they're ready to make a purchase.
martonikaj said:
I think its slightly unnerving that theres quite a bit of silence from Google when they've already announced a date for Europe.
Click to expand...
Click to collapse
You're not alone mate. Here in Europe we have a date but what does it mean? Is it just for the 16 GB version? If yes when does the 32GB arrive? Not a single shop here has a confirmed date when it is in store so we're in the same situation. We can just wait and search the web for infos.
Sent from my HTC Desire using XDA App
Nebucatnetzer said:
You're not alone mate. Here in Europe we have a date but what does it mean? Is it just for the 16 GB version? If yes when does the 32GB arrive? Not a single shop here has a confirmed date when it is in store so we're in the same situation. We can just wait and search the web for infos.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Indeed. I'm constantly looking for information about the 32 GB version as I really need the space and I find it frustrating that there is no information about it. I even asked Samsung Sweden about it and they have yet to reply. They did reply to my other questions I asked them earlier about the GN but not this.
It's pathetic. Google and Samsung screwed up a chance to take the spotlight from 4s.
Carriers ***** slapped both if them and they complied.
Nothing short of bad management to have ZERO information or street dates this far after announcement. The *few weeks* bull**** stopped being believable after gingerbread.
Agreed. I'm not going to reopen any old wounds, because they might be egocentric as another member or two posted, but this is not how you do it.
I just keep looking at that original Nexus One launch and hang my head. If those people involved could only see to now? Dear god they'd be ashamed, I would think.
The more frustrating thing is Google really is so big, the only other people that can bull them into releasing info are more corrupt and more interest centric than Google itself. The actual people that will use the device day in and out, I feel there is no one to speak for our interests.
It would be nice if we could twitter Rubin himself: A number of users, with a simple message: You should be ashamed of the GN launch. #Nexus Fail
bmstrong said:
Agreed. I'm not going to reopen any old wounds, because they might be egocentric as another member or two posted, but this is not how you do it.
I just keep looking at that original Nexus One launch and hang my head. If those people involved could only see to now? Dear god they'd be ashamed, I would think.
The more frustrating thing is Google really is so big, the only other people that can bull them into releasing info are more corrupt and more interest centric than Google itself. The actual people that will use the device day in and out, I feel there is no one to speak for our interests.
It would be nice if we could twitter Rubin himself: A number of users, with a simple message: You should be ashamed of the GN launch. #Nexus Fail
Click to expand...
Click to collapse
I wouldn't be so harsh but I ordered my device and so I would like to know where it is and when I can receive it.
The only thing which probably was a bit fail is the fact that they showed it to early.
Sent from my HTC Desire using XDA App
Nebucatnetzer said:
I wouldn't be so harsh but I ordered my device and so I would like to know where it is and when I can receive it.
The only thing which probably was a bit fail is the fact that they showed it to early.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Don't forget it was meant to be announced a week or two before it actually was, so that would have been even earlier.
So far all we have had is either conflicting information, or none at all. Samsung confirmed yesterday that release in the UK would be on the 17th, and literally a matter of hours later retailers are saying this has now been pushed back to w/c 21st
They have lost quite a bit of momentum with the delays and confusion imo. My attitude has gone from "wow, I need this phone now" to "do I really need a new phone?".
I will probably still buy it though
I bet they're still wringing out bugs/issues.
The conspiracy theorist in me says there are patent issues to work out.
My guess is they will never disclose why the launch has been delayed. But I do agree, it's likely lawyers, not engineers involved in the delay.
I like to feel special. If less people have it, it makes me more special.
I had a Samsung Wave in the U-S-of-A. I felt special. Until I started hating it for being so special (Samsung store didn't work in the US).
xManMythLegend said:
It's pathetic. Google and Samsung screwed up a chance to take the spotlight from 4s.
Click to expand...
Click to collapse
you honestly think that the Galaxy Nexus would be able to take the spotlight from the iPhone 4S?
PM me so I know where to get the drugs you're on....
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
Barkleyfan said:
My guess is they will never disclose why the launch has been delayed. But I do agree, it's likely lawyers, not engineers involved in the delay.
Click to expand...
Click to collapse
There's probably a lot of numbers talk going on between Google and the carriers in the USA atm.
Don't know, might be Samsung not Google. Maybe one reason they bought Motorola I bet the next Nexus will be Motorola's
Sent from my MB860 using Tapatalk
I am tired and weary of combating all of these claims, when they simply are not true.
What makes a Nexus device? Overall, the Google marketing? team responsible for it names the device. They decide what falls under the Nexus moniker. It is a name, and nothing more. I know a lot of people think it means it is a developer phone. No, it does not mean that. The Nexus Q has the Nexus name, but I really doubt you will be seeing AOSP support for it. Time will tell.
Is the Nexus a developer phone? Sure. Is it marketed or expected to be a phone specifically for developers? No.
In the past, Google has released an ADP, short for Android Developer Phone. There was the ADP1, ADP2, ADP3 (which turned out to be the Nexus One). These phones were not sold at carrier locations, not subsidized, and specifically meant for developers. It was before my time with Android, but I believe the ADP1 (basically an unlocked G1) required you to register with Google as a developer. The ADP2 came out later, and once again Google made it clear it was not meant for non-developers.
The Nexus devices were when Google decided to meld developer and end user devices. The Nexus One was provided unsubsidized from Google for a time, and subsidized through Tmobile. Verizon took a shot at it, but canceled the phone early on in testing. These phones did not require registration as a developer, and were sold in carrier stores.
The Nexus S expanded upon this. It was available to multiple carriers subsidized. Sprint received a model called the Nexus S 4G. It had full AOSP support with the exception of WIMAX (I think). Google had resdistribution licenses for Gingerbread and all was right in the world. Yes, the 4G received updates slower than the plain Nexus S, but it still received them. It was a Nexus device.
Fast forward to today. The Galaxy Nexus has been released as GSM, and CDMA/LTE. Verizon gets updated directly from Google, but does not authorize them for OTA until they meet their 'quality standard'. Then Google throws the switch. Google builds them, through and through. The Verizon model has been the center of controversy for some time because Google was unable to obtain redistrubtion licenses for the proprietary blobs. It still had all of the code needed to build from AOSP though, but without CDMA or LTE. This was because Google could not give us the proprietary files needed to make such things work. Their hands were tied, because it is closed source. So, Google threw their hands up in the air and told the world after they tried to obtain the rights for a while when 4.0.3 came out. Did it change anything? A little. It was made clear that because the licenses could not be obtained, that AOSP would include what it always has for CDMA/LTE, but not the proprietaries for download. In addition, it meant that Google would no longer pay someone to test the CDMA/LTE code in AOSP because they cannot even support a full build due to the licensing issues. This ruling extended to all CDMA devices, even the Nexus S 4G. This has never been an issue with GSM, because Google has a license to redistribute the blobs.
What does this change? Well for one, it is up to us to find our own CDMA/LTE blobs from a rom or phone. By the way, we aren't allowed to do this if you follow the license. We do anyway
It also means if/when we find a bug in the CDMA/LTE AOSP code, we cannot expect Google to fix it. I don't really foresee this becoming an issue, but it could.
Now, back to the original subject. Does it mean the Verizon phone isn't a Nexus? I mean, it has BLOAT (apks and libs for Verizon apps to work as well as Backup Assistant for those coming from feature phones).
No! It is a Nexus. Every device has proprietary blobs. The Verizon model has a couple more. The Sprint model has a few more than that. However, who cares? Do you guys think the yakjuxx variants are not Nexus devices? They get updates even slower than Verizon or Sprint. Nexus devices can exist, even if Google cancels AOSP tomorrow. AOSP does not make a Nexus device. A design and vision that Google oversees makes a Nexus. Thats it.
All devices have open and closed sourced items.
All devices have proprietary blobs.
It doesn't matter that Verizon includes a couple extra items, or decides to test updates longer than Google. As I mentioned before, not everything on ANY Nexus device is open source.
GSM requires proprietary blobs.
CDMA requires proprietary blobs.
A licensing issue does not undo a device from being a Nexus. Neither do delayed carrier updates. If you live in the US and have a subsidized or network locked device, you should expect that the carrier has control over your hardware. There is no other way to put it, but it does not change the overall nature of the device. Not all Nexus updates are coming from Google anymore as well. Yakjuxx variants as well as Sprint's Toroplus model get updates built from Samsung.
Ok, I want to say a lot more, but I will stop here.
A nexus is a nexus, but I didn't like that fact Verizon wanted to **** around with the software causing a standoff between them and Google.
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Gromet said:
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I had 4.1 on my CDMA Toroplus within 24hrs of the announcement. That's why I got a Nexus. Who cares when the carriers are gonna push the OTA?
Gromet said:
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
This. I have the sprint nexus and I'm def getting one off the play store and slapping an att sim in there next time.
Sent from my Galaxy Nexus using xda premium
Gromet said:
I'm sorry but I think that the Verizon nexus is a joke for one main reason. A true Nexus device gets updates directly from Google not once the Carrier makes modifications and feels they want release the update.
..Gromet
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Verizon makes no modifications to anything Google does. Verizon doesn't even develop their own software. They send Google what they want on the device. What you like or dislike does not change the device from being a Nexus.
Moving on...
phatmanxxl said:
A nexus is a nexus, but I didn't like that fact Verizon wanted to **** around with the software causing a standoff between them and Google.
Click to expand...
Click to collapse
What standoff? The one the blogosphere invented? I've seen nothing official from Google confirming any standoff.
I sure see a lot of proprietary apks on the Sprint version. Did you here of any dicking around and standoff between Sprint an Google?
Backup Assistant and an Account Management application are hardly a standoff-ish issue. The software was added in, and does not modify any of the actual base code.
jesusice said:
I had 4.1 on my CDMA Toroplus within 24hrs of the announcement. That's why I got a Nexus. Who cares when the carriers are gonna push the OTA?
Click to expand...
Click to collapse
I beat you by 12 hours or so, but yeah, same deal. Try that with any other non-Nexus device (and have it fully working).
Folks, likes or dislikes have nothing to do with this thread. I have my own issues about how Verizon handles things.
The thread is about the device being a Nexus, not personal feelings.
Why do people treat this kind of crap like it's Religion?
I believe the reason why people think this is because of the sensational headlines "blogs" create to draw clicks. There are a handful of Android specific blogs (which I won't name) that post the most far-fetched of rumors and the "doomsday" headlines with the sole purpose of creating traffic.
People need to draw their own conclusions on things instead of taking what "Joe Bag 'O Donuts" on [insert] tech blog as fact.
live4nyy said:
Why do people treat this kind of crap like it's Religion?
Click to expand...
Click to collapse
More importantly, why do people continue to spread FUD regardless of facts?
Funny how people said we wouldn't see 4.0.4 factory images, wrong. This CDMA nexus bashing is lame and tiresome.
Sent from my Galaxy Nexus using Tapatalk 2
El Daddy said:
I believe the reason why people think this is because of the sensational headlines "blogs" create to draw clicks. There are a handful of Android specific blogs (which I won't name) that post the most far-fetched of rumors and the "doomsday" headlines with the sole purpose of creating traffic.
People need to draw their own conclusions on things instead of taking what "Joe Bag 'O Donuts" on [insert] tech blog as fact.
Click to expand...
Click to collapse
This.
What I wouldn't give to see every blog out there nuked from existence. Do you guys remember the Internet, before blogs existed?
Better days...
---------------
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
delete
jesusice said:
I had 4.1 on my CDMA Toroplus within 24hrs of the announcement. That's why I got a Nexus. Who cares when the carriers are gonna push the OTA?
Click to expand...
Click to collapse
^THIS^
adrynalyne said:
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
Click to expand...
Click to collapse
I hate exclusivity. It's like High School all over again.
adrynalyne said:
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
Click to expand...
Click to collapse
This. Especially when I hear comments like, "Enjoy waiting [x] months for an update." Just because I have a CDMA Nexus doesn't mean I don't have a "true" Nexus. Even various GSM Nexus models are still officially stuck on 4.0.2.
Sent from my Galaxy Nexus using xda premium
Not sure why people are blaming blogs for the fact that the VZW Nexus gets updates months after its unlocked GSM brethren. That's not a made-up problem, it's simply a fact being reported.
adrynalyne said:
-snip-
I also can't help but think (especially how some of the inital responses were), that some GSM users feel that Nexus is an exclusive club and CDMA users are not invited.
Just a gut feeling I get from some people. Not relevant to thread or original post content.
Click to expand...
Click to collapse
Unfortunately, I think you will find this mentality with anything. (gadgets, cars, sports teams, race, etc.) "Mine is the best and everything else sucks!"
---------- Post added at 03:05 PM ---------- Previous post was at 03:04 PM ----------
Cabal_ said:
Not sure why people are blaming blogs for the fact that the VZW Nexus gets updates months after its unlocked GSM brethren. That's not a made-up problem, it's simply a fact being reported.
Click to expand...
Click to collapse
That doesn't mean it's not a Nexus device...
Cabal_ said:
Not sure why people are blaming blogs for the fact that the VZW Nexus gets updates months after its unlocked GSM brethren. That's not a made-up problem, it's simply a fact being reported.
Click to expand...
Click to collapse
How about the sensationalist standoffs? Plenty of wild claims out there.
Are those fact?
Once again, that still does not make it a non-Nexus device.
Here is a fact for ya:
There are still some maguro devices out there on 4.0.1 and 4.0.2. I still call them Nexus devices.
Hello to Canadian Galaxy Nexus owners. If, like me, you are angry at the lack of response from Google or Samsung as to when our yakjuux firmware phones are going to be updated, here's where to complain:
Competition Bureau of Canada (I'm too new to post a link, apparently, but you can google it.)
They have a toll free number in "Contact Us". You'll talk to a real person.
This agency is responsible for investigating claims of false advertising in Canada. I have lodged a complaint against both Google and Samsung over the false claims that the phone I bought was a "Pure Google Experience" phone which would receive operating system updates in a timely fashion due to lack of carrier or manufacturer customization. I suggest you do the same, as the more complaints on an issue they receive, the higher profile the problem becomes for them. I don't know if it will help, but if you would like to reference my file number (R608849), feel free.
Individually, Google has been ignoring us for months. Perhaps the Canadian Government will have better luck.
Enjoy,
Fox
considering google doesnt publish the update directly to yakjuux, you cant really be angry at google.
point the finger at samsung.
Just change your phone to yakju and you won't have to complain. I did that months ago and have always been happy. The process was easy and very well documented on this site.
My co-worker stayed on yakjuux until this week. I was always getting updates that he wasn't.
It is okay to complain if you know you will get positive results. But in this case, it will just be a waste of time because there is no legal definition of "timely".
Just flash the phone to yakju.
Sent from my Galaxy Nexus using xda app-developers app
I don't really recall any concrete specific promises that would hold up as "false advertising", but it's been a while since I saw the ads so I don't really remember. The definitions of "timely updates" and "pure Google experience" are probably not set in stone and could be argued by either side for whatever strengthens their argument.
It sucks that yakjuux isn't getting updated, but I have a feeling most people on a developer-oriented site such as XDA would probably just spend a few minutes converting their phone to yakju/takju and be done with it rather than go on a crusade trying to get the government involved. Just saying...
I am fully aware that I can flash my phone to yakju, but I've had several friends buy this phone on my recommendation who won't do such a thing. They'll be stuck with the random reboots, low volume, etc, and I want to help them out too. Again, in this thread, people have repeated the line that Google doesn't publish the update for yakjuux phone, but I have yet to see a source from Google for that claim. The only official statement I've seen is Samsung claiming that it DOES come straight from Google. (Yes, I know that Samsung could be wrong/lying about this, but until I see an official word from Google that contradicts it, it's the only thing close to an official story I have.)
Anyway, it's the principle of the thing, now. I want them to give us what we were all led to believe we would get from this phone.
Not even 'could be' lying. ARE lying.
I think the problem here is with samsung, Google was not even aware of the regional variants when the phones started to roll out. Secondly, I don't think going to the BBB or any other method of escalation is going to do anything. The phones in Canada are not marketed as being updated by Google, nor is there any statement regarding the guaranteed updating of the phone.
Regardless of the marketing, the Nexus line of phones is not for novice phone users who want a seamless experience, for those people, i tend to recommend the Galaxy 2/3 line of phones and/or the iPhone as it suites their needs better.
End recommendation: if you can't be bothered to flash a rom, you should not have gotten a Nexus in the first place. If they still insist on getting the Nexus, it takes 1 minute to flash stock yakju to a phone, do it for them - or have them order it through the play store.
Edit: Just for you FoxHoleAtheist - I posted this a while back.
http://forum.xda-developers.com/showpost.php?p=25535165&postcount=461
Matridom said:
I think the problem here is with samsung, Google was not even aware of the regional variants when the phones started to roll out. Secondly, I don't think going to the BBB or any other method of escalation is going to do anything. The phones in Canada are not marketed as being updated by Google, nor is there any statement regarding the guaranteed updating of the phone.
Regardless of the marketing, the Nexus line of phones is not for novice phone users who want a seamless experience, for those people, i tend to recommend the Galaxy 2/3 line of phones and/or the iPhone as it suites their needs better.
End recommendation: if you can't be bothered to flash a rom, you should not have gotten a Nexus in the first place. If they still insist on getting the Nexus, it takes 1 minute to flash stock yakju to a phone, do it for them - or have them order it through the play store.
Edit: Just for you FoxHoleAtheist - I posted this a while back.
http://forum.xda-developers.com/showpost.php?p=25535165&postcount=461
Click to expand...
Click to collapse
I completely disagree. The Nexus isn't intended as a developer's-only phone.. it's marketed to anyone and everyone who wants a pure google phone. Those regular users who buy them shouldn't be forced to A) search out relatively obscure tutorials on message boards and B) void their warranty to get the updates their phones need to work properly.
FoxholeAtheist said:
Again, in this thread, people have repeated the line that Google doesn't publish the update for yakjuux phone, but I have yet to see a source from Google for that claim.
Click to expand...
Click to collapse
From JBQ himself:
https://groups.google.com/forum/?fromgroups#!topic/android-building/kMhE-Orl5Kk
Can you quote the Samsung source saying the other variants do get updates from Google? (I'm not questioning you here at all, I just haven't seen that and would like to be fully informed on the topic). The Samsung updates are served from Google servers, but as far as I know Samsung prepares the update for Google to host.
FoxholeAtheist said:
A) search out relatively obscure tutorials on message boards
Click to expand...
Click to collapse
Though I can certainly understand less technical people not wanting to do it, or even knowing where to look for instructions, efrant has a great guide: http://forum.xda-developers.com/showthread.php?t=1626895 ... just in case you ever want to point someone to a proper howto.
and B) void their warranty to get the updates their phones need to work properly.
Click to expand...
Click to collapse
I don't know if it actually voids the warranty. Even if it does, you can 100% restore the phone to the stock state so they can never tell. And to my knowledge back to the Nexus One days, no Nexus phone has ever been refused warranty if it was an actual hardware problem that wasn't caused by software.
Sorry, this is getting off the original topic... just wanted to provide some info.
If you are not willing to fix it yourself then file a complaint against Samsung.
Most people complain through the wrong channels or just don't complain because they don't know who will listen and can actually do anything about it.
Thanks for posting the info.
FoxholeAtheist said:
I completely disagree. The Nexus isn't intended as a developer's-only phone.. it's marketed to anyone and everyone who wants a pure google phone. Those regular users who buy them shouldn't be forced to A) search out relatively obscure tutorials on message boards and B) void their warranty to get the updates their phones need to work properly.
Click to expand...
Click to collapse
I never said it was a developers phone. I stated it was not for novices. this phone is on the bleeding edge of android, it's expected to have issues.
Ya I didn't wait or bother, I just unlocked and rooted and be done with being a slave to anyone when my phone gets updated. Never looked back.
FoxholeAtheist said:
Hello to Canadian Galaxy Nexus owners. If, like me, you are angry at the lack of response from Google or Samsung as to when our yakjuux firmware phones are going to be updated, here's where to complain:
Competition Bureau of Canada (I'm too new to post a link, apparently, but you can google it.)
They have a toll free number in "Contact Us". You'll talk to a real person.
This agency is responsible for investigating claims of false advertising in Canada. I have lodged a complaint against both Google and Samsung over the false claims that the phone I bought was a "Pure Google Experience" phone which would receive operating system updates in a timely fashion due to lack of carrier or manufacturer customization. I suggest you do the same, as the more complaints on an issue they receive, the higher profile the problem becomes for them. I don't know if it will help, but if you would like to reference my file number (R608849), feel free.
Individually, Google has been ignoring us for months. Perhaps the Canadian Government will have better luck.
Enjoy,
Fox
Click to expand...
Click to collapse
I know how you feel I have the Nexus S was suppose to get the 4.0 first after Gnex and that didn't happend. Just asking like that in a friendly way. But could Google or Samsung be mad at you cause you modified their device and their rom ?
I'm not pretty sure but I'm pretty sure somewhere there's a word or 2 about not modifying anything of Samsung or Google. Just saying don't want any problem or start a fight
Goes both ways I guess. No offense
Canadian here, but dont care. I'd rather flash my own firmwares.
Although I agree with you FoxholeAtheist, I don't think a forum like xda-developers is the right place to champion your cause, as most of the folks here will have the same response that speedyink just posted above. Maybe go to the Rogers/Bell/Telus forums and post it there. Just sayin'.
I could have swore that Google marketed the nexus line as a developer phone since its conception. I don't see you getting much support for your cause on a forum for developers. Most here have flashed their ROM and moved on.
They marketed the Nexus One as such, and never again. People just ASSumed. It is a consumer device with development abilities.
FoxholeAtheist;28719966If said:
You have no grounds to complain. Nobody is obligated to give time lines for updates. Doing so, and missing the date, means a huge backlash for the company... it's not the risk for them to do that.
As others have suggested. Just flash updates yourself. I'm Canadian and have been running Jellybean since it was first available.
Click to expand...
Click to collapse
You have no right to complain, nor will the Competition Bureau do anything about it.
The Nexus is marketed as a Pure Google phone. This much you are correct about... However 4.0.2 ICS is still a "pure google experience". They never made any guarantees as to when you'd be receiving updates, if you receive them at all. This is all based on what you believe they should do, not what they told you they would do.
Beyond this, flashing to Yakju/Takju is as easy as pie if you follow efrants thread... you don't even have to flash the regional radio... you can keep it completely 100% stock "Pure Google/Updated by Google" experience like I did and be happy.
Your efforts in complaining will be fruitless. The competition bureau will not investigate this claim based on what you believe, they will look at what you were told, which was basically nothing.
Before you all scream heresy, hear me out.
Today marked Verizon officially announcing 4.2.2 for the Galaxy Nexus, thus marking the end of the VZW model being 4 updates behind the GSM models. Here's the thing...every time there's been an update in testing, El Madhatter has informed us because of his testing phone. He never got a 4.1.2, 4.2, or 4.2.1 build. His device went straight from 4.1.1/JRO03O to 4.2.2/JDQ39. Because of that, one can logically deduce that Google never actually released a 4.1.2, 4.2, or 4.2.1 build to Verizon for testing on the device.
There is historical precedent for this. Let's go back to December, 2011 when Android 4.0.3/Ice Cream Sandwich was released to the Nexus S and Motorola Xoom. Only two variants ever got Android 4.0.3:
1. The 900 MHz carrier-unlocked Nexus S (I9020T/I9023 - Got build IML74K)
2. The Wi-Fi Motorola Xoom (MZ604 - Got build IML77)
Here's a list of devices that never saw an update until Android 4.0.4/IMM76(X) was released in late March, 2012:
1. The 850 MHz carrier-unlocked Nexus S (I9020A - Updated directly by Google with no carrier approvals just like I9020T)
2. The Sprint Nexus S 4G (D720)
3. The Korean Nexus S (M200)
4. The Verizon Motorola Xoom (MZ600/MZ602)
5. The carrier-unlocked Galaxy Nexus running yakju firmware (I9250)
6. The Verizon Galaxy Nexus (I515)
The I9250 Play Store (running takju) model was not available yet.
So as you can see, clearly Google picks and chooses which devices get which updates in the event of brand new Android versions sometimes. Some builds (like 4.0.3) were clearly designed to be limited rollouts to test on a more limited scale. Then once they fix bugs, they do a more massive rollout (like they did with 4.0.4). Something tells me that 4.2 was the same thing.
4.2 and 4.2.1 had exactly one difference...the fixing of the December event bug. So, I think it's clear that Google probably intended the 4.2/4.2.1 JOP40(X) builds to be the test builds that they used to gauge the major problems. Now that the major issues with those builds are fixed, 4.2.2 is their "mass rollout" build that they're releasing to absolutely everything.
I think this is actually smart on Google's part, given that Verizon requires testing and approval of all updates to phones they sell.
Also, within that parameter, 4.2.2/JDQ39 hit GSM Galaxy Nexus models on February 12. We on Verizon got the official OTA rollout beginning March 19. That's a little over a month. That's the fastest update the VZW Galaxy Nexus has ever received.
Discuss.
i think its a little of both.
verizon does slow down the update process, but google is the one that releases the update itself.
Good thoughts. I also think it is likely that Verizon started testing and rejected those builds. 4.2 and 4.2.1 had some serious issues and I'm sure big red didn't want to support them.
A buddy of mine from high school works for Verizon corporate. I've asked him why VzW always seems to lag on updates. A lot of it comes down to VzW: It's not that Google never sent the updates to VzW, it's that VzW tests everything and what they don't like doesn't get pushed out to VzW customers.
Makes since to me, but I think Vzw miss handled the public relations aspects of it. I'm mean with all those jelly bean builds being released. They could've let their customers know that they're not interested in those builds but will update our phones with a build that meets their standards
I for one was ready you shout heresy at the top of my lungs, but then I saw it was written by Oldblue and had to give it a chance. I'm halfway convinced. Another peculiarity is the build numbers of late - in the past, each AOSP device typically had a slightly different build number (IMM76K, D, Q, JRO03C, R, O) due to small changes made to the final build for each unique piece of hardware. With 4.1.2 the build was JZO54K across all AOSP platforms, which continued with JOP40C,D and JDQ39. Something has changed in the build process to make Android more universal, and in the case of JDQ39 made it through Verizon testing in record time.
Now, do I believe that Google didn't send 4.2 or 4.2.1 to Verizon? Not sure, but it's worth pondering in absence of knowing what internal conversations occurred.
Sent from my Xoom using xda premium
It just wasn't a good idea for Verizon to take on the nexus. Nexus devices shouldn't be controlled by a carrier at all. Carrier's don't want to deal with the problems that the nexus devices bring.
Google doesn't release perfect builds to the nexus because that isn't the purpose of nexus phones. In order to be on the cutting edge of android development you have to deal with some things not working perfectly. I think everyone can agree that 4.2 and 4.2.1 had some pretty significant issues and Verizon customer support may not know what to do if a customer calls in needing help with something not working.
Winesnob said:
I for one was ready you shout heresy at the top of my lungs, but then I saw it was written by Oldblue and had to give it a chance. I'm halfway convinced. Another peculiarity is the build numbers of late - in the past, each AOSP device typically had a slightly different build number (IMM76K, D, Q, JRO03C, R, O) due to small changes made to the final build for each unique piece of hardware. With 4.1.2 the build was JZO54K across all AOSP platforms, which continued with JOP40C,D and JDQ39. Something has changed in the build process to make Android more universal, and in the case of JDQ39 made it through Verizon testing in record time.
Now, do I believe that Google didn't send 4.2 or 4.2.1 to Verizon? Not sure, but it's worth pondering in absence of knowing what internal conversations occurred.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Well there were past examples of all platforms having the same build number. All Galaxy Nexus devices launched with 4.0.1/ITL41D and 4.0.2 was ICL53F across the board.
On the Xoom, the Wi-Fi and Verizon models shared build numbers sometimes.
For the Nexus S, all variants ran 2.3.4/GRJ22. All except Sprint ran 2.3.6/GRK39F. Also, the Nexus One's Gingerbread builds always matched the GSM Nexus S variants...GRI40, GRJ22 and GRK39F.
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
Well there were past examples of all platforms having the same build number. All Galaxy Nexus devices launched with 4.0.1/ITL41D and 4.0.2 was ICL53F across the board.
On the Xoom, the Wi-Fi and Verizon models shared build numbers sometimes.
For the Nexus S, all variants ran 2.3.4/GRJ22. All except Sprint ran 2.3.6/GRK39F. Also, the Nexus One's Gingerbread builds always matched the GSM Nexus S variants...GRI40, GRJ22 and GRK39F.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
True, but the most striking thing to me is that JDQ39 is on the N4,N7,N10, and GNex. Crossing that many platforms with the same AOSP core seems a bit unusual.
Sent from my Xoom using xda premium
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
iLeopard said:
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
Click to expand...
Click to collapse
In the case of the Verizon Galaxy Nexus variant, Verizon's only role is testing of any update. Beyond that, updates for that device come direct from Google. So Google submits the updates to Verizon, Verizon signs off, Google rolls it out. My point was, I don't think step one (Google submitting the update for testing) ever happened for 4.1.2, 4.2, or 4.2.1.
Sent from my Nexus 7 using Tapatalk HD
iLeopard said:
I don't necessarily think Google has anything to do with the update process of the VZ variant. Android is an open source API. Carriers adopt that API and add any features they deem worthy (TouchWiz, Motoblur, Sense). The carriers also hold proprietary drivers for their devices, which they have to update with progressing versions of the Android platform.
Click to expand...
Click to collapse
You are confusing carriers with manufacturers. TouchWiz is Samsung, Motoblur is Motorola, Sense is HTC. Carriers don't request these features, they come from the makers as a branding mark on top of the Android API. Carriers do on frqeuent occasion have the manufacturers presinstall bloatware from which the carrier receives advertising revenue or promotes its own services. The Nexus (despite being on Verizon) is a Google device, does not come with bloatware, and has no manufacturer skin stuck on top of Android. The vast majority of proprietary drivers for Nexus devices are posted on Googles open source pages as they have licensed them for distribution as intact binary files, aiding third party developers in building AOSP for Nexus devices. The Galaxy Nexus software update battle is between Google and Verizon - Verizon doesn't continue developing the platform, they simply test and decide if they are going to push it out. If not, they notify Google with specific issues and move forward from there.
Sent from my Xoom using xda premium
Winesnob said:
You are confusing carriers with manufacturers. TouchWiz is Samsung, Motoblur is Motorola, Sense is HTC. Carriers don't request these features, they come from the makers as a branding mark on top of the Android API. Carriers do on frqeuent occasion have the manufacturers presinstall bloatware from which the carrier receives advertising revenue or promotes its own services. The Nexus (despite being on Verizon) is a Google device, does not come with bloatware, and has no manufacturer skin stuck on top of Android. The vast majority of proprietary drivers for Nexus devices are posted on Googles open source pages as they have licensed them for distribution as intact binary files, aiding third party developers in building AOSP for Nexus devices. The Galaxy Nexus software update battle is between Google and Verizon - Verizon doesn't continue developing the platform, they simply test and decide if they are going to push it out. If not, they notify Google with specific issues and move forward from there.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Right, I did in fact confuse those two. Thank you.
The VZ variant complies with LTE standards though which does imply driver differences between the GSM and CDMA version?
iLeopard said:
Right, I did in fact confuse those two. Thank you.
The VZ variant complies with LTE standards though which does imply driver differences between the GSM and CDMA version?
Click to expand...
Click to collapse
Yes but Google and Samsung control that. The CDMA and LTE drivers for the VZW Galaxy Nexus are available on the AOSP driver page on Google's developer site.
Sent from my Nexus 7 using Tapatalk HD
Didn't the Sprint Galaxy Nexus get more updates though?
Sent from my Galaxy Nexus using xda premium
Yuhfhrh said:
Didn't the Sprint Galaxy Nexus get more updates though?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Toroplus (mysidspr) is maintained by Samsung, and that device bumped from 4.1.1 to 4.2.1. So no, it didn't get more updates and is actually an update behind the Google maintained Galaxy Nexi (takju, takju, mysid)
Sent from my Xoom using xda premium
My curse is that every thing reminds me of South Park, so I immediately thought "What's important right now, is figuring out whose fault this is."
Maybe you're right, but that answer only welcomes more questions. Could be Google thinks of VZW users as helpless children that can't handle the potential bugs present in the newest firmware. Maybe the opposite: Google thinks of VZW users as elitists who only deserve stable updates?. Or maybe they think, "We are VZW/Google, you know those AT&T jokers don't have service in the more rural areas of the country, you'll pay for it and then wait longer for updates. F you." Or maybe, VZW and/or Google were actually genuinely testing the firmware on the VZW LTE device before releasing it. I imagine it takes a while for the can-you-hear-me-now guy to make his rounds.
If anyone is to blame for lagging updates it's people like you who create threads like these. There has been a whacked sense of entitlement going on these past years and it's easier to find someone to blame rather than demonstrate patience. I would wager people are already asking when the next update is coming out. People call and harass Verizon or whoever and then tell the whole internet about how no one at Verizon knows anything or they are giving you conflicting dates. You're not forced to sign a contract with a particular cell phone carrier...are you? Oh and then the update finally comes and people rush to find and post the latest bugs and then call and harass Verizon or google again and ask them when the next update is coming. Has anyone ever called Verizon after an update and thanked them? Hmmm probably not, too busy asking for more and more. Android updates have become like crack for people and it's time to step away from the white mountains and just relax. They are just phones people!! Call your grandmothers instead of checking for updates everyday!
The op shows no sense of entitlement nor is requesting another update. Simply pondering on why various versions of nexus have updated differently. Fact is, to an extent your right, a lot of people are constantly crying for updates, but this thread is not one of those situations.
I, for one, bought a nexus for the purpose of being at the forefront of updates, but I'm not crying for any. As long as googles follows through with the promise of keeping my bought from Google devices up to date with the latest release I'm happy. That's not a sense of entitlement, its called buying a nexus for a specific reason.
Sent from my Nexus 7 using xda premium
hlaalu said:
If anyone is to blame for lagging updates it's people like you who create threads like these. There has been a whacked sense of entitlement going on these past years and it's easier to find someone to blame rather than demonstrate patience. I would wager people are already asking when the next update is coming out. People call and harass Verizon or whoever and then tell the whole internet about how no one at Verizon knows anything or they are giving you conflicting dates. You're not forced to sign a contract with a particular cell phone carrier...are you? Oh and then the update finally comes and people rush to find and post the latest bugs and then call and harass Verizon or google again and ask them when the next update is coming. Has anyone ever called Verizon after an update and thanked them? Hmmm probably not, too busy asking for more and more. Android updates have become like crack for people and it's time to step away from the white mountains and just relax. They are just phones people!! Call your grandmothers instead of checking for updates everyday!
Click to expand...
Click to collapse
Seriously? Wow. I never EVER hinted at a sense of entitlement. I agree with you that there is definitely a lot of that in this community, but that was not the point of this thread. If you look at any of the work I do around here, my entire purpose on XDA is to catalog stock OTA updates for Nexus devices and help the community with reverting to stock if necessary. Thus, a thread like this would be logical for me to start as this topic is basically at the crux of what I do here.
I should tell you, sir, to go back under your rock and stay there.
The title explains everything..personally, i hoped to see something better than some apps updates and a game playable in chrome. Even if someone says that google is working on a great, big update, a minor update to increase performance,battery and some bug fixes (like system ui memory leak?) would have been very appreciated by me.
(P.S. Worthless to say that the "fused location" update doesn't bring any noticeable battery saving and also that to get rid off memory leak i have to install a custom rom)
Yeah. I was kinda expecting them to talk about 4.3 and then give us a date when to expect it.
I dont think anyone is happy about it (we all love new features)
but i understand why they did what they did.
Google I/O is a DEVELOPER conference. so they did a bunch of stuff for DEVELOPERS so they would be able to make better applications.
and 4.3 is rumored to come June 10th...hopefully that will help you out a little bit with your problems.
i like multiple threads about i/o
Id say google nailed it with this io. This wasnt just for developers. They pushed updates to the whole android eco system. Yes they could've just released a new android version and some neat features to go with it. But that wouldnt move the ecosystem forward. This way the whole android family from 2.2 is affected. And ofcourse the developers knew their being heard , which is in every way VERY VERY good for us users.
Sent from my Galaxy Nexus using Tapatalk 2
Everything suggests, that a 4.3 release is close by, but it was probably supposed to be at I/O but got delayed. In my opinion they actually made up for it by pushing all the play features, which may not seem like an upgrade to the user, but which greatly increases general userexperience in a subtle way.
I agree with ferozfero. What they did unveil at I/O may not be what everyone wanted but looking at the big picture, it paves the way for some good stuff down the road. Google has a lot of other services that arent directly related to Android, which all got major updates. Complaining that we didnt get one little update to Android is pretty ungrateful. 4.3 doesnt need a big event to be released so we should all just be patient and see if the june rumor is true.
On a side note, Android will be celebrating its 5th birthday this september. I find that to be a good time to release version 5.0 if any.
Wrong thread. Thanks for failing Tapatalk. :banghead:
Actually i'm not complaining and i can sleep as every night even if my android version is still 4.2.2, but 2013 i/o was just out of my expectations and i wanted to share with everyone my thought. Another guy created a thread about google i/o, but he was simply disappointed about a "stock-android galaxy s4" instead of a nexus 5 or what ever it could be. This thread deals with android update and i/o no one spoke about it during the conference. I'm sorry if you think that i'm ungrateful, but developers at google are paid for their jobs and i deserve to expect always the top from a such rich and great brand like google.
Angelakaro said:
Actually i'm not complaining and i can sleep as every night even if my android version is still 4.2.2, but 2013 i/o was just out of my expectations and i wanted to share with everyone my thought. Another guy created a thread about google i/o, but he was simply disappointed about a "stock-android galaxy s4" instead of a nexus 5 or what ever it could be. This thread deals with android update and i/o no one spoke about it during the conference. I'm sorry if you think that i'm ungrateful, but developers at google are paid for their jobs and i deserve to expect always the top from a such rich and great brand like google.
Click to expand...
Click to collapse
Yes you can expect top stuff. But you should know that google has not disappointed anyone here. Actually they wer taking a step back for the good of the company and us. Yes they couldv just released a new version and everyone would be like yeeeee we got a new android version with cool features everyone but nexus users wont see for a year. But instead they released a slew of that will be available right then and would affect ALL end users much sooner tha a new android version. This us not to say theyr not gonna release one very soon. That way we would get all these awesome features and also a new android update. Everyone's happy.
Sent from my Galaxy Nexus using Tapatalk 2
I'm just excited for gcm (google cloud messaging).
Api sync notifications is going to be epic. I have two phones work and personal along with a tablet and to be able to sign in, delete notifications, etc from one device to all the others is going to be so nice.
I was satisfied with the io
Sent from my Nexus 10
Angelakaro said:
Actually i'm not complaining and i can sleep as every night even if my android version is still 4.2.2, but 2013 i/o was just out of my expectations and i wanted to share with everyone my thought. Another guy created a thread about google i/o, but he was simply disappointed about a "stock-android galaxy s4" instead of a nexus 5 or what ever it could be. This thread deals with android update and i/o no one spoke about it during the conference. I'm sorry if you think that i'm ungrateful, but developers at google are paid for their jobs and i deserve to expect always the top from a such rich and great brand like google.
Click to expand...
Click to collapse
Sorry if you thought I was soloing you out. I wasn't. I was talking about people who complain in general. A lot of people EXPECTED certain things at Google I/O and all I can say is I blame the rumors. Thats what rumors do to people.
jsgraphicart said:
Sorry if you thought I was soloing you out. I wasn't. I was talking about people who complain in general. A lot of people EXPECTED certain things at Google I/O and all I can say is I blame the rumors. Thats what rumors do to people.
Click to expand...
Click to collapse
Hehe you got that right. And this time the rumors wer so believable it had me going fr a while too.
Sent from my Galaxy Nexus using Tapatalk 2
Hopefully they're working on the #1 feature android lacks. Battery life.
Sent from my Galaxy Nexus using xda app-developers app
ferozfero said:
Yes you can expect top stuff. But you should know that google has not disappointed anyone here. Actually they wer taking a step back for the good of the company and us. Yes they couldv just released a new version and everyone would be like yeeeee we got a new android version with cool features everyone but nexus users wont see for a year. But instead they released a slew of that will be available right then and would affect ALL end users much sooner tha a new android version. This us not to say theyr not gonna release one very soon. That way we would get all these awesome features and also a new android update. Everyone's happy.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I respect your point of view because, actually, you're right. I think the same (that an update will be released soon)...my real disappointment was because they didn't talk about it.
jsgraphicart said:
Sorry if you thought I was soloing you out. I wasn't. I was talking about people who complain in general. A lot of people EXPECTED certain things at Google I/O and all I can say is I blame the rumors. Thats what rumors do to people.
Click to expand...
Click to collapse
Never mind Actually i'm really ANGRY because i thought that they would have released a major update and i reflashed factory 4.2.2 image and relocked the bootloader some days before the i/o, to get ready for the update! (LOL,just joking)
People are acting like if the OTAs come out on the day of I/O...I guess it helps to be prepared.
Sent from my Galaxy Nexus using Tapatalk 4 Beta