It's Tuesday, 11 June 2013, and rumors continue about the much anticipated release of Google Jelly Bean 4.3 (or some variant of it). Though it didn't happen yesterday the 10th as some had expected--others now say July, an article by Robert Triggs just a few hours ago on Android Authority begs the question "Galaxy Nexus passes through Bluetooth SIG, is Android 4.3 incoming?" Apparently, a GT-I9250 (aka "Maguro": GSM/HSPA+ Galaxy Nexus variant on AT&T/T-Mobile networks) was spied being tested against Bluetooth standards, a requirement for new update releases. That, my friends, is a major step toward our beloved GNexes getting another transfusion that's slated to resolve the over-discussed problems of overheating and rapidly draining batteries. Plus, gaining a couple of new features: a new camera UI and a power-saving Bluetooth upgrade to v4.0 that most higher end devices have. To read Robert Triggs' complete article, go to " http://m.androidauthority.com/galaxy-nexus-passes-bluetooth-android-4-3-224336/ " . I'm so (steam)punked, I check my phone's System Updates in Settings every hour or so.
It's Fathers Day, 16 June 2013... I was sure that the moment I turned on my GNex this morning that the 4.3 OTA update would arrive. Didn't happen, but what a nice FD gift that would have been. Day's not over... who knows, could happen.
steampunk, guessing that's a joke...if you've owned a Gnex for a while now on Verizon's network you know it'll be months before we get 4.3, if we ever get it 
Has Android 4.3 been released yet for the unlocked GSM version? Until I'm not going to bother worrying about it. Google has released enough updates on the individual apps and their Google Services app that I have already seen improvements.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
It got released today.. Hope Verizon does not screw up this update as they did with 4.2.2 and they prepared for the 4.3 OTA release to come soon. I will feel sorry for anyone who decides to get a new Nexus 7 LTE on verizon as i am sure it will suffer the same fate as the GN. Cant imagine why google would even give big red another nexus device.
DroidGalaxy wrote:
It got released today.. Hope Verizon does not screw up this update as they did with 4.2.2 and they prepared for the 4.3 OTA release to come soon. I will feel sorry for anyone who decides to get a new Nexus 7 LTE on verizon as i am sure it will suffer the same fate as the GN. Cant imagine why google would even give big red another nexus device.
I saw that it was released on the tech sites. I hooe we won't wait too long. Until then I will will work with the OS my Nexus has installed.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
With the revelation of a security vulnerability that has existed since Android 1.6, an update of some sort is due. The vulnerabilty allows for a previously signed App to be modified (assumedly maliciously) and still appear to be correctly, digitally, signed.
There's an app to test for this:
https://play.google.com/store/apps/details?id=com.bluebox.labs.onerootscanner
Read more here:
http://it.slashdot.org/story/13/07/11/134228/android-master-key-vulnerability-checker-now-live
Google have FIXED it on the server side. There are a couple of posts/articles on AndroidCentral.com that explain it better then I ever could.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
I too am wondering when we are going to get the update. I noticed that on googles factory images, there is not even an image for 4.3 for verizon. I do hope that verizon is planning on rolling this update out to us as it is being reported it helps with things such as the battery life.
I just got 4.3 on my Nexus 10. If history is any guide, the Verizon Galaxy Nexus will be 3-6 months behind. Assuming it gets an update at all. And you'll have to do the Google Services Framework shuffle to get it to notice the update if it ever goes live.
It was a nice six months or so that my phone and tablet were on the same version. I waited for 4.x and specifically chose Nexus devices so that my portable devices would be running the same platform. So much for that plan. The Galaxy Nexus should never have been called a Nexus device. I blame Google, Verizon, and Samsung equally for the pathetic support of this device.
It would be amazing if Verizon can push 4.3 faster than 4.2.2. Galaxy Nexus has been a solid device for me. I did have to warranty my first but my CLN replacement has been solid. I got my 32GB GN for 49.99 last october and at that price its been great phone with no bloat.
Another vote for Verizon to release the 4.3 update and some new radios too. Reception is still a disaster on this phone.
NeedMoreCoffee,
We're always craving new updates to improve the performance of our devices. No word yet on a release for the Galaxy Nexus, but curb your software appetite by checking in frequently for news at http://bit.ly/n5snpq . Regarding reception, what are you dealing with exactly? Voice or data? Zip code? Here to help!
EvanO_VZW
Follow us on twitter @VZWSupport
I've got data reception issues too.
Your (Verizon's) management of this phone is a disaster: You have completely ruined it with slow updates, crappy radio, crappy bluetooth, crappy battery management, and neutering Google Wallet off of the device.
Newsflash VZ: Nobody bought this phone because they wanted a perfect experience. We bought the phone because we wanted bleeding edge updates and features. We don't want Isis; We want Google Wallet. We don't want you to comb through all the code. We want it the day it comes out.
I know you will respond with something like, "Hey! Thanks for the excellent feedback! This will help us tremendously!" You know what would help tremendously? Stop with the self-fellatiating posts, and click the "Release 4.3 to the Nexus devices" button. Also, allow ALL the features. I want updates the frigging DAY the new OS comes out.
Now, for phones that my Mom and Dad buy (Galaxy S3-type), PLEASE QA the software so they don't stroke out when something doesn't work.
I hate you Verizon.
Hi Evan,
I travel all over the country actually and have problems, but that may be gaps in VZW's network. However, I've been a customer a lot of years and know that VZW's coverage in the Baltimore area is generally good, except with this device. The issue is primarily data. Here are some examples and I'm happy to provide more in this forum or another. I previously owned a Motorola Droid 1 and my wife has the iPhone 4S, neither of which gave me these problems.
Zip Code 21202 - 4G and 3G swings back and forth. When it drops down to 3G, I have it for a little bit, then it drops to 0 dbm. The signal drops completely several times a day.
Zip Code 21204 - Similar, but only with certain areas. I should note that the previous two phones I had kept strong 3G everywhere.
Baltimore I-695, Coverage drops completely, 0dbm all over it. Never had this problem before. Not a problem with iPhone.
Arnold, MD area - Even my OG Droid and wife's iPhone had data issues here. Major hole for coverage with VZW, however voice calls were fine. Not now, I enter that area and I literally get the no network message if I try to make a call.
Other times I'm traveling in other cities, I can be in the middle of a major populated area and not even be able to look up something on Yelp because I'm on 3G and it says 0dbm. If my wife is with me, I look at her iPhone and it connects fine. I was in Chicago Midway Airport a few weeks ago and couldn't even load Twitter my signal was so bad. I figured it was because I was in a building, but never had problems in that airport in the past with other phones and I go there frequently.
I'll also add that the radio updates have improved some spots. It certainly made my 3G upload speed go from a palty 2 kilobytes per second to way faster. However, there are vast areas where the adventure is wondering if I'll have access to data, or at least voice calls.
Dear NeedMoreCoffee,
Good afternoon. I appreciate you providing us with such great details on the issue you are experiencing. This will help us tremendously.
I understand you travel quite frequently. Let's first start with refreshing the network on your phone. Please remove/reinsert the SIM card. To learn how to do this click http://vz.to/znMW74 Once you have done this, please test service to see if it has helped. If you still experience service issues, please feel free to reach out to us for further assistance.
Thank You,
MichelleS_VZW
VZW Support
Follow us on Twitter @VZWSUPPORT
Oh it's available ....
https://developers.google.com/android/nexus/drivers#torojwr66v
The link http://vz.to/znMW74 is certainly no help in finding out about it though
Having the binaries available does not equal having the actual update available.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
@Ann154 if you think that you are grossly uninformed, the driver binaries
are the hard part which were released July 24th 2013 outside of Radio
Firmwares this should have been built by July 25th into an official ROM for
Alpha testing.
Once the driver binaries are released it's just a matter of taking the
compile scripts "probably unmodified from 4.2.2, possibly adding in a few
enhancements & building all the source code into proper binaries for our
phone(s) after that is the QA to see if there are any build errors or
firmware issues "Like the one identified in 4.3 for the Nexus 7 which got a
4.3.1 update"
There are many amateur development teams building ROMs off of these
Binaries, and the official 4.3.x ROM Google released... when I say amateur
I mean those who build unofficial ROMs but have daytime jobs outside of ROM
building.
My bet is on any of the following for reasons we haven't seen the ROM yet.
Return on Investment just isn't there for Verizon to put the time into
building it
Problems with Radio Firmware(s) on their network with 4.3.x
Value Added software incompatible with 4.3 needing major rewrites -- See
reason 1
They've already gotten rid of the development platform for the Galaxy Nexus.
I was replying to a VZW Employee who had stated that the update may never occur.
Since the update is available in the Toro flavor from Google now ... Add bloatware (Backup ass't, etc) and let 'er roll (out).
The post I was replying to also said to check the main support site for info ...
Didn't intend to ruffle feathers.
Start a new topic or ask questions in the open forum.
