so I called Verizon Wireless today to complain about my phone..
me - my phone reboots on it's own, when are we suppose to get update for it already? isn't that a google phone and we suppose to get updates directly from google? and what's the hold up anyway?
verizon - updates will come from samsung and not google and we have no information on that
me - maybe you can contact samsung on my behalf and inquire about update?
verizon - ok, please hold ...
few minutes passes by...
verizon - thank you for holding blah blah blah, i just got off the phone from samsung they said check samsung website regularly, they'll announce it there, by that time your phone will receive update.
what a waste of time!
You were fed a total line. Your phone's version of Android is "mysid" which is directly updated by Google. However all updates do need final approval from Verizon.
In fact, to verify this yourself, download the free "GN Official Update Checker" from the marketplace (I refuse to say "google play store" fttb) and run it.
Sleuth255 said:
You were fed a total line. Your phone's version of Android is "mysid" which is directly updated by Google. However all updates do need final approval from Verizon.
In fact, to verify this yourself, download the free "GN Official Update Checker" from the marketplace (I refuse to say "google play store" fttb) and run it.
Click to expand...
Click to collapse
That "official" update checker is nothing more than a user-created app that checks if your device is running yakju or mysid and, if so tells you your device is updated by Google, and if on another build, it says its not updated by Google. Not even close to being official.
No one knows if non-yakju or non-mysid builds are updated by Google or not. It is just speculation. What we do know is that all updates for ALL builds are pushed from Google's servers.
Sent from my Galaxy Nexus using Tapatalk
i just wish they push update already, so that everyone is start being really happy with that phone, my co-worker just updated his to 4.0.4 and extremely happy with it now, which is great! if by end of this month they wont release anything i'm going to update "leaked" version of 4.0.4 myself!
Sleuth255 said:
You were fed a total line. Your phone's version of Android is "mysid" which is directly updated by Google. However all updates do need final approval from Verizon.
In fact, to verify this yourself, download the free "GN Official Update Checker" from the marketplace (I refuse to say "google play store" fttb) and run it.
Click to expand...
Click to collapse
i ran "GN Official Update Checker" and it said exactly what you said.
efrant said:
That "official" update checker is nothing more than a user-created app that checks if your device is running yakju or mysid and, if so tells you your device is updated by Google, and if on another build, it says its not updated by Google. Not even close to being official.
No one knows if non-yakju or non-mysid builds are updated by Google or not. It is just speculation. What we do know is that all updates for ALL builds are pushed from Google's servers.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
what's the difference between one and another?
@efrant: Well, I never said it was the official update checker either, only that it was named the "GN official update checker"
However, its author does keep up with the official status as shown on the androidcentral writeup here (note what it says about mysid in the photo and the clarification posted later).
@OP once you've checked your build with the above app, feel free to find the actual official answer to your question from Jean-Baptiste Queru who is a Software Engineer at Google's Android Open-Source Project.
A link to his answer on Google groups is located here
@efrant: Hopefully this is official enough for you too. At least the AOSP status is being confirmed for yakju and mysid and the supposition by Jean is that this implies direct updates too.
---------- Post added at 02:19 AM ---------- Previous post was at 02:17 AM ----------
a1exus said:
what's the difference between one and another?
Click to expand...
Click to collapse
yakju is the official GSM build for the GNex. Its variants are yakjuXX where XX is two additional lowercase characters.
mysid is the official LTE build for the GNex. I don't believe it has variants.
Sleuth255 said:
@efrant: Well, I never said it was the official update checker either, only that it was named the "GN official update checker"
However, its author does keep up with the official status as shown on the androidcentral writeup here (note what it says about mysid in the photo and the clarification posted later).
@OP once you've checked your build with the above app, feel free to find the actual official answer to your question from Jean-Baptiste Queru who is a Software Engineer at Google's Android Open-Source Project.
A link to his answer on Google groups is located here
@efrant: Hopefully this is official enough for you too. At least the AOSP status is being confirmed for yakju and mysid and the supposition by Jean is that this implies direct updates too.
Click to expand...
Click to collapse
I think there is some confusion here between AOSP support and who updates different builds. JBQ hasn't said anything about who updates any of the builds. And there is nothing official about status shown in that androidcentral article. Like I said, at this point, it is speculation -- no one can say that just because yakju and mysid have AOSP support, that they are the only builds updated by Google.
I'm not trying to be a pain here, but right from the launch, people were making comments about the different builds based purely on assumption, speculation and inference. Case in point: an app was created telling people their device is updated by Google or not updated by Google. But the truth is no one knows. Every OTA update is pushed from Google -- this is all we know for certain about the updates. AOSP is a different topic.
Sent from my Galaxy Nexus using Tapatalk
So it would appear.
Related
So I'm wondering about this phone a friend offered to sell to me. It's a Samsung Taylor developer phone, so I have no idea which forum this goes into.
Will I be able to get software updates to the phone at all? Because right now the phone comes with the prototype ROM, so it can't record 720P. The camera is crap, some things like Facebook and Twitter don't work all the way. The marketplace isn't there. Its not stolen property because he is an independent developer and he says the phone served its purpose and he moved on to actual Win7 phones.
Any opinions? I asked my friend and he says he never tried looking for updated ROMs and he stopped using them after he got a focus.
untrueparadox said:
So I'm wondering about this phone a friend offered to sell to me. It's a Samsung Taylor developer phone, so I have no idea which forum this goes into.
Will I be able to get software updates to the phone at all? Because right now the phone comes with the prototype ROM, so it can't record 720P. The camera is crap, some things like Facebook and Twitter don't work all the way. The marketplace isn't there. Its not stolen property because he is an independent developer and he says the phone served its purpose and he moved on to actual Win7 phones.
Any opinions? I asked my friend and he says he never tried looking for updated ROMs and he stopped using them after he got a focus.
Click to expand...
Click to collapse
connect it to zune and look for updates , there are beta updates for that phone (actually with a higher build number and copy/past) so I would say yes there are updates for .
I have a German Vodafone Optimus 7 that was used a couple of months by a software developer. I don't think it's running the latest (stable) build of WP7 however. When I check for updates with Zune it says that I'm up to date and the current version is: 7.0 (6536). Is this the latest version that every WP7 device is running? And if not, how come that my device doesn't get any updates?
Btw, Marketplace etc. just work fine on the device.
renegadEEE said:
I have a German Vodafone Optimus 7 that was used a couple of months by a software developer. I don't think it's running the latest (stable) build of WP7 however. When I check for updates with Zune it says that I'm up to date and the current version is: 7.0 (6536). Is this the latest version that every WP7 device is running? And if not, how come that my device doesn't get any updates?
Btw, Marketplace etc. just work fine on the device.
Click to expand...
Click to collapse
that is not a developer phone but a pre release , only the Samsung Taylor is a developer phone (and get beta updates )
you have to wait for the official update in 2011.
ceesheim said:
that is not a developer phone but a pre release , only the Samsung Taylor is a developer phone (and get beta updates )
you have to wait for the official update in 2011.
Click to expand...
Click to collapse
The LG Panther was a developer phone too I believe. Thanks for your reply, I'll be waiting for the january update just lik everyone else then
renegadEEE said:
The LG Panther was a developer phone too I believe. Thanks for your reply, I'll be waiting for the january update just lik everyone else then
Click to expand...
Click to collapse
thanks , didn't know of the LG Panther .
ps, the latest official build is 7004.
In theory, the Taylor and Panther have updates to build 7003/7004, and they are available on the net (or if you ask the right friendly WP7 dev).
If you plug the device in to Zune, it should search for an update to 7003, though that might not happen.
73XX and above do also exist for the Taylor/Panther, but they're a lot harder to come by, and won't be coming out via Zune any time soon.
In theory, a dev device running 7003 will be able to do anything a release device running the same build (they wouldn't be much use as developer phones if they behaved differently) so I think updating the device should fix the issues you've got, though it'll never do 720p video, and the camera is terrible!
i dont think my friend's is even running the release. the market doesnt work and the live integration is blank. so if i have him get the update, basically i can upgrade it? awesome.
untrueparadox said:
i dont think my friend's is even running the release. the market doesnt work and the live integration is blank. so if i have him get the update, basically i can upgrade it? awesome.
Click to expand...
Click to collapse
That sounds like an older build then, those are both working on the Taylor/Panther I've got.
Let me know if you need help finding an update.
I don´t know why but I have ROM 7006 installed on my Samsung Taylor, so diff packages from 7004 to 7008 won´t work. Asked lots of devs and MSFTies an no one seems to have ROM 7004 for the Taylor.
Any help?
Follow this guide to get Mango running on the Samsung Taylor: http://www.rudigrobler.net/blog/2011/9/28/installing-mango-on-your-samsung-taylor.html
Leapo said:
Follow this guide to get Mango running on the Samsung Taylor: http://www.rudigrobler.net/blog/2011/9/28/installing-mango-on-your-samsung-taylor.html
Click to expand...
Click to collapse
Update is possible from rev. 7004 only, not from 7003 or 7006 (never heard about that revision).
sensboston said:
Update is possible from rev. 7004 only, not from 7003 or 7006 (never heard about that revision).
Click to expand...
Click to collapse
So you personally tried it the above process, and it failed?
Leapo said:
So you personally tried it the above process, and it failed?
Click to expand...
Click to collapse
I've tried from 7003 and failed.
I tried it with ROM 7006 and it also failed.
At what point is it failing?
Are you absolutely sure you're using the correct "ChevronWP7.Updater"?
The download link was pulled some time ago, so if you downloaded anything off of Chris's blog, it was the wrong updater.
Edit: I would post a link to the correct one, but all the mirrors were on megaupload...which is now gone
Leapo said:
Are you absolutely sure you're using the correct "ChevronWP7.Updater"?
Click to expand...
Click to collapse
Actually, I'm not sure about Rudi Grobler's post. No proof screenshots (even photoshopped!), nothing at all but just words...
Second, search for deleted comments to his article: http://www.rudigrobler.net/display/Search?moduleId=12353177&searchQuery=Samsung+Taylor
The first said (but he left all comments without reply!):
Comment On: Installing Mango on your Samsung Taylor
Journal Entry Comment by r2d2rigo on September 29, 2011
How did you get your Taylor to 7004 in the first place?
Click to expand...
Click to collapse
So, it may be fake... I received Sammy Taylor at August, 2010 and installed all updates MS sent to registered developers/partners but never heard about Taylor on 7004.
In my case, it fails when applying the diff packages, since they are all 7004-7008, adn my rom is 7006.
I have try to find info about the links to 7006-7008 packages with no success so far.
3/7/2011 was awhile ago while we have market 2.x and newer packages has market 5.x. must be reasons why we're stuck with an outdated version
So what's up with the 2.3.4 GApps?
**(Please note, YMMV with all of the following information. Nandroid is your friend!)**
This is a tricky one. The problem here is that Google, unlike what they've done for every previous update to the G1, Nexus One, Nexus S, etc., decided to compile the Talk2.apk and libtalk_jni.so to be compatible only with the neon board, and ARM v7 (aka, the Nexus S), rather than every board, the actual Gingerbread API's, and ARM v6 and Tegra as well. So here's where this leaves us:
20110307: Works just fine on 2.3.4, just as it did on 2.3.3. Just doesn't have the Market updates already in it (you'll get the updates as soon as you launch the Market for the first/second/third time or so), nor does it have the new Google Talk. Because of this, it's still used in ROM Manager for AOSP ROMs such as CyanogenMod, listed as Recommended in the Google Apps listing, and is given at the latest/7/universal page, and the above table.
Click to expand...
Click to collapse
So what can be done? In the meantime... Not much. I'm basically waiting for a manufacturer to release a 2.3.4 OTA update which has a universally-compiled library and app. Otherwise, 20110307 is recommended for everyone on 2.3.3-2.3.4 (CyanogenMod 7.0.x-7.1.x). There might be other options that present themselves (a new OTA for a Nexus device which has the files we need, someone breaking into the Googleplex (that was a joke!), etc.), but until then, there's not much anyone can do.
Click to expand...
Click to collapse
From http://goo-inside.me/gapps/
AKA:
tl;dr blame Google.
Click to expand...
Click to collapse
so basically we won't see market v5.x+ anytime soon
dyetheskin said:
so basically we won't see market v5.x+ anytime soon
Click to expand...
Click to collapse
Probably not.
I forget the yshkxklchzl whatever it is name, but I've checked out the Dev section and all I see are ROMs
I like vanilla - wondering if there's update.zip files out there for 4.0.2 or better. I'm unlocked and rooted - I have the OS that updates via Samsung not Google.
Thanks
dang, thought we'd have those cool update.zip releases just like on my old Nexus One!
guess not??
There are no official updates more recent than 4.0.2. You can follow the instructions in this thread to change your phone to yakju (updates from Google) and install the latest official 4.0.2.
I'm actually looking for 4.0.2 ... it's out for my version but I don't see it posted anywhere...
If you're talking about that Android Central article about the Bell update, they never verified if it was correct and assumed the user that emailed them knew what he was talking about. NOBODY with yakjuux has received 4.0.2 or has been able to confirm they also got the update.
oh boooooooooooooo yeah that's what I was referring to I thought yakjuux would have gotten updated by now.
not that i'm complaining, 4.0.1 is great. Just heard a few minor speed/battery improvements were coming so....
Hi
I purchased my Galaxy Nexus when it first launched back in November from Handtec, the current firmware on my device is version 4.0.2. But for some reason it does not get the notification for OTA updates. I understand from reading the forums that the current version is 4.0.4 and that was pushed over two weeks ago. My device has not gotten the notification to update, I tried the framework suggestion that was suggested on another thread but I got no result I also tried the "check in" code and had no luck. My current carrier is AT&T, is my Nexus defective? Can somebody please help?
Thank you
MEGABYTEPR said:
Hi
I purchased my Galaxy Nexus when it first launched back in November from Handtec, the current firmware on my device is version 4.0.2. But for some reason it does not get the notification for OTA updates. I understand from reading the forums that the current version is 4.0.4 and that was pushed over two weeks ago. My device has not gotten the notification to update, I tried the framework suggestion that was suggested on another thread but I got no result I also tried the "check in" code and had no luck. My current carrier is AT&T, is my Nexus defective? Can somebody please help?
Thank you
Click to expand...
Click to collapse
If your phone is anything but yakju then your in for a wait. Also the 4.0.4 roll out has stopped until google fixes the signal issues some people have.
How can I identify if my phone is a yakju ?
MEGABYTEPR said:
How can I identify if my phone is a yakju ?
Click to expand...
Click to collapse
Dude please read a bit. This exact thread exists every single day of the last week.
Check your version with this: https://play.google.com/store/apps/details?id=de.cbruegg.officialupdate
But the thing is that even if it is "yakju" (updated by Google). The 4.0.4 update has been stopped because it causes radio-related signal drop issues for some users. They recently issued a small 4.0.4 "fix" for it. Once things are sorted out, presumably 4.0.2 users will get moved straight up to the latest 4.0.4.
Wow, the moment we never thought we'd see...it's listed as Archived, Reference Only, but Google has posted binaries, including CDMA/LTE blobs for toroplus at http://developers.google.com/android/nexus/drivers. These are binaries for Android 4.1.2/JZO54K. Go, build, be merry!
stock flash images are available too (GSM version that is, CDMA is still missing)
zephiK said:
stock flash images are available too (GSM version that is, CDMA is still missing)
Click to expand...
Click to collapse
We won't see factory images for toroplus because Sprint's Galaxy Nexus gets updates from Samsung, not Google. This thread is more to talk about the AOSP binaries which many, including myself, thought we'd never see for that exact same reason. Normally Google only releases binaries for devices that they update directly.
oldblue910 said:
We won't see factory images for toroplus because Sprint's Galaxy Nexus gets updates from Samsung, not Google. This thread is more to talk about the AOSP binaries which many, including myself, thought we'd never see for that exact same reason. Normally Google only releases binaries for devices that they update directly.
Click to expand...
Click to collapse
I wasn't asking when factory images for toroplus is coming out. I was just stating that the GSM flash images are available (as non-toroplus users will also visit the thread).
Thanks for your input.
Anyone flashed it yet? Do we get a landscape homescreen as well?
MoosDiagramm said:
Anyone flashed it yet? Do we get a landscape homescreen as well?
Click to expand...
Click to collapse
Flash what? Fastboot flash factory images?
... if you want landscape homescreen just get a alternative launcher such as Apex or Nova and you can do the same.
In terms of binaries, you can't flash binaries.
zephiK said:
Flash what? Fastboot flash factory images?
... if you want landscape homescreen just get a alternative launcher such as Apex or Nova and you can do the same.
In terms of binaries, you can't flash binaries.
Click to expand...
Click to collapse
You seem kind of jumpy. I apologize for discussing the factory images in a thread that is clearly dedicated to the binaries alone.
And no, I don't care much about a possible landscape homescreen, I just wanted to sparkle a friendly discussion about any noticeable changes in this release.
oldblue910 said:
We won't see factory images for toroplus because Sprint's Galaxy Nexus gets updates from Samsung, not Google. This thread is more to talk about the AOSP binaries which many, including myself, thought we'd never see for that exact same reason. Normally Google only releases binaries for devices that they update directly.
Click to expand...
Click to collapse
I'd be willing to bet that they will post factory images whenever Sprint gets around to pushing the 4.1.2 OTA. Which of course will probably be a while but is still very cool.
jesusice said:
I'd be willing to bet that they will post factory images whenever Sprint gets around to pushing the 4.1.2 OTA. Which of course will probably be a while but is still very cool.
Click to expand...
Click to collapse
That would be cool, but I'd be surprised. Historically Google has only released factory images for firmware that they update and maintain. The mysidspr firmware that runs on toroplus comes from Samsung, so if they were to provide factory images, that would be a real first.
oldblue910 said:
That would be cool, but I'd be surprised. Historically Google has only released factory images for firmware that they update and maintain. The mysidspr firmware that runs on toroplus comes from Samsung, so if they were to provide factory images, that would be a real first.
Click to expand...
Click to collapse
I'm gonna have to disagree with you here. I'm pretty sure that Google doesn't update the Verizon Galaxy Nexus or the Sprint Nexus S 4G yet they both have their factory images. Note that both the NS4G and the Toro have their 4.1.2 binaries posted but not the 4.1.2 factory images. This is because for AOSP devices that are not updated by Google they wait until the offical OTA to release the factory images.
jesusice said:
I'm gonna have to disagree with you here. I'm pretty sure that Google doesn't update the Verizon Galaxy Nexus or the Sprint Nexus S 4G yet they both have their factory images. Note that both the NS4G and the Toro have their 4.1.2 binaries posted but not the 4.1.2 factory images. This is because for AOSP devices that are not updated by Google they wait until the offical OTA to release the factory images.
Click to expand...
Click to collapse
For CDMA devices, Google updates the Verizon Xoom, Verizon Gnex, and NS4G. The "trygon", "mysid", and "sojus" firmware that run on those devices respectively all come from Google, they're just subject to carrier approval. You can tell due to the build numbers:
On trygon, mysid and sojus, the build numbers follow normal Google conventions (IMM76D, JRO03H, etc.). The Sprint Galaxy Nexus uses Samsung conventions (IMM76D.L700FG01 for instance). You can also tell by the kernel build dates. On mysid and sojus, the kernels match AOSP. On the Sprint Galaxy Nexus, the kernel has a build date in KST (Korean Standard Time) and was built by [email protected] Clearly the Toroplus (Sprint Gnex) kernel is built by Samsung.
Another way to tell is in the OTA file naming conventions. Any (except the Nexus S as of Ice Cream Sandwich for some reason) has OTA files that follow the naming convention <12-character-sha1-hash>.signed-<firmware name>-<new build>-from-<old build>.<8-character-sha1-hash>.zip...so like abcdef012345.signed-mysid-JRO03O-from-IMM76K.abcdef01.zip. Updates for NS4G, Verizon Gnex, and Verizon Xoom all have these naming conventions. The OTA files for the Sprint Galaxy Nexus follow Samsung's naming convention of abcdef012345.update-IMM76K-to-JRO03O.zip.
In the end though, just look at the build number. If the build number is 5 or 6 characters, it's a Google firmware. Otherwise, it comes from the OEM.
oldblue910 said:
For CDMA devices, Google updates the Verizon Xoom, Verizon Gnex, and NS4G. The "trygon", "mysid", and "sojus" firmware that run on those devices respectively all come from Google, they're just subject to carrier approval. You can tell due to the build numbers:
On trygon, mysid and sojus, the build numbers follow normal Google conventions (IMM76D, JRO03H, etc.). The Sprint Galaxy Nexus uses Samsung conventions (IMM76D.L700FG01 for instance). You can also tell by the kernel build dates. On mysid and sojus, the kernels match AOSP. On the Sprint Galaxy Nexus, the kernel has a build date in KST (Korean Standard Time) and was built by [email protected] Clearly the Toroplus (Sprint Gnex) kernel is built by Samsung.
Another way to tell is in the OTA file naming conventions. Any (except the Nexus S as of Ice Cream Sandwich for some reason) has OTA files that follow the naming convention <12-character-sha1-hash>.signed-<firmware name>-<new build>-from-<old build>.<8-character-sha1-hash>.zip...so like abcdef012345.signed-mysid-JRO03O-from-IMM76K.abcdef01.zip. Updates for NS4G, Verizon Gnex, and Verizon Xoom all have these naming conventions. The OTA files for the Sprint Galaxy Nexus follow Samsung's naming convention of abcdef012345.update-IMM76K-to-JRO03O.zip.
In the end though, just look at the build number. If the build number is 5 or 6 characters, it's a Google firmware. Otherwise, it comes from the OEM.
Click to expand...
Click to collapse
Pfft. Facts. You can prove anything with facts
jesusice said:
Pfft. Facts. You can prove anything with facts
Click to expand...
Click to collapse
Two words for you, sir. Well played!
oldblue910 said:
For CDMA devices, Google updates the Verizon Xoom, Verizon Gnex, and NS4G. The "trygon", "mysid", and "sojus" firmware that run on those devices respectively all come from Google, they're just subject to carrier approval. You can tell due to the build numbers:
On trygon, mysid and sojus, the build numbers follow normal Google conventions (IMM76D, JRO03H, etc.). The Sprint Galaxy Nexus uses Samsung conventions (IMM76D.L700FG01 for instance). You can also tell by the kernel build dates. On mysid and sojus, the kernels match AOSP. On the Sprint Galaxy Nexus, the kernel has a build date in KST (Korean Standard Time) and was built by [email protected] Clearly the Toroplus (Sprint Gnex) kernel is built by Samsung.
Another way to tell is in the OTA file naming conventions. Any (except the Nexus S as of Ice Cream Sandwich for some reason) has OTA files that follow the naming convention <12-character-sha1-hash>.signed-<firmware name>-<new build>-from-<old build>.<8-character-sha1-hash>.zip...so like abcdef012345.signed-mysid-JRO03O-from-IMM76K.abcdef01.zip. Updates for NS4G, Verizon Gnex, and Verizon Xoom all have these naming conventions. The OTA files for the Sprint Galaxy Nexus follow Samsung's naming convention of abcdef012345.update-IMM76K-to-JRO03O.zip.
In the end though, just look at the build number. If the build number is 5 or 6 characters, it's a Google firmware. Otherwise, it comes from the OEM.
Click to expand...
Click to collapse
Needs to be stickied somewhere.
oldblue910 said:
That would be cool, but I'd be surprised. Historically Google has only released factory images for firmware that they update and maintain. The mysidspr firmware that runs on toroplus comes from Samsung, so if they were to provide factory images, that would be a real first.
Click to expand...
Click to collapse
How cool is this!? https://developers.google.com/android/nexus/images#mysidspr
jesusice said:
How cool is this!? https://developers.google.com/android/nexus/images#mysidspr
Click to expand...
Click to collapse
That's about as cool as it gets!
jesusice said:
How cool is this!? https://developers.google.com/android/nexus/images#mysidspr
Click to expand...
Click to collapse
Where were you yesterday when I posted that? Nobody cared, LOL.
The build is FH05 but the radios are FC12 so you have to update the radios if you restore the factory image
Sent from my Galaxy Nexus
adrynalyne said:
Where were you yesterday when I posted that? Nobody cared, LOL.
Click to expand...
Click to collapse
Lol, not checking General! That place gives me eye cancer.
Hopefully this is the beginning of some cool stuff. Hopefully we will have 4.2 images shortly after they release the code to it. I know we will have custom ROMs but stock images would be nice too.