yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kristovaher:
They should give an option to people to download the update when they manually request it. The fix is working, forum is all over it, why should I have to wait for a week to get the official update without having to resort to unlocking and whatever other methods required to update it? Let the roll-out happen to people who do not manually request updates or don't even know about it.

This whole week-long roll-out for small number of devices with an update less than 1MB in size is just stupid. There is a final update out there, so I could use the phone as a phone. But I cannot.

Apparently hard enough that it doesn't work.
[Samsung Galaxy Nexus] qwerp_:
ICS, new update and changes. demm.
[Samsung Galaxy Nexus] bushbrother:
W00t my Nexus just arrived in the post :) Strong 3G signal here so not seen an issue yet ... checking bootloader info ...

OMAP-Samsung HW Information

Board Name: tuna REV 9

Board Rev: HSPA - 9

Boot Type: USB MMC1

Device Type: HS

Build Date: Oct 30 2011 12:32:21

Android Version: 4.0.1

Baseband: I9250XXKK1

Kernel: 3.0.1-ge2433f2 android-build@apa28 #1

Build Number: ITL41D

So that confirms the 2nd batch from Clove was the same as the first :)
[Samsung Galaxy Nexus] oscillik:
I have to agree with kristovaher here.

There are not that many handsets in the wild. It shouldn't be taking so long to push such a small update to handsets.

I bought the handset on the first day of general availability in the UK, and as kristovaher has pointed out - Google do not consider IMEI identification to be valid way to identify phones. I still do not have the update, almost 24 hours after the actual roll-out began.
[Samsung Galaxy Nexus] ref1ux:
He hasn't experienced the problem once, so how am I selfish? I've experienced it multiple times, so I need it more than him.

Kindly refrain from making random insults please :mad:
[Samsung Galaxy Nexus] Duddyroar:
Same here, bought mine on the day of release, still no sign of the update. I suffer from volume dropping terribly when I'm at home, and have missed text messages and calls on a daily basis due to this fault.
[Samsung Galaxy Nexus] enlli:
Mine was from O2, but first day of release - and again no update as yet. Those that have got updates seem to be on a 1800MHZ network, so if Google are trying a few to see how it goes, it's not very scientific. :rolleyes:
[Samsung Galaxy Nexus] mehalaktas:
This waiting is something like a headache. I am sick of check now button :-)
[Samsung Galaxy Nexus] darkoroje:
I agree that the phone erasing itself after an unlock is a pain. However, if you have backed your phone to Google, which is the default, the phone will automatically restore all the settings and applications on the first reboot after unlocking. However, it will not restore other data such as music.
[Samsung Galaxy Nexus] oscillik:
That has not been my experience.
[Samsung Galaxy Nexus] IvanDobskey:
I'm on o2 and have only had the phone a day yet i've seen the volume bug numerous times already! No sign of the damn patch here either :(
[Samsung Galaxy Nexus] bleets:
so you perceive yourself as being more important as he hadnt yet experienced the issue, even though there is plenty of scope for it to occur? Well good news for you, he won't get the issue now! :)

As they say, patience is a virtue. And from the look of this place people everywhere have a series lack of virtue!
[Samsung Galaxy Nexus] floateruk:
I have just read about this fix five minutes ago, so I turned my phone off, then on again, and lo and behold it said "android updating".

Clearly can't guarantee that this will happen for everyone evertime, but for those who are clearly as impatient as I am, this may well do it.
[Samsung Galaxy Nexus] s.m.knipe:
Android updates from Google like this always roll out slowly. I guess they use small batches to protect their servers or whatever.

I wish the stock recovery could still flash an "update.zip" but I can see where that can be a security risk
[Samsung Galaxy Nexus] oscillik:
Ice Cream Sandwich says "Android updating" every single time you turn the phone on. This means nothing in pertinence to this update we're waiting on.
[Samsung Galaxy Nexus] floateruk:
Oh really? Haha. Excuse my android n00bness. I got all excited then as well. I don't turn my phone off that often to know....
[Samsung Galaxy Nexus] darkoroje:
Go to "Backup & Reset" in settings and make sure that "Back up my data" is on, and that it is using the right Google account.
[Samsung Galaxy Nexus] N0matter:
Same here. Bah!
[Samsung Galaxy Nexus] ref1ux:
Dude, seriously. There's no need to micro-analyse every last thing I say. It's irritating.
[Samsung Galaxy Nexus] marky9074:
Sorry this doesnt make sense (to me). Do you therefore, know where to put the update.zip file if it is different to /cache (which didn't work for me either incidentally)...
[Samsung Galaxy Nexus] bleets:
such is the way of forums on the internet, if you feel the need to comment expect a retort!

Either way, quit whining and be patient.
[Samsung Galaxy Nexus] stanleywinston:
different volume issue?

I've just got off the phone from Samsung.

My phone completely hangs and eventually reboots if I hit the volume key a couple of times. Samsung support are insisting it's the same issue and will be fixed with the OTA but I'm concerned that the only thing the two issues have in common is the word 'volume'.

Has anyone else heard of this issue. Apologies if it's already in this thread but searching in here (and google in general) for 'galaxy nexus volume' is kind of overloaded with posts about the other issue.
[Samsung Galaxy Nexus] ref1ux:
I think I've seen you in a few other threads. That tells me all I need to know tbh...

---

Regardless of anything, I really shouldn't have signed up for another 2 years on Vodafone. Their 3G coverage is pants compared to T-Mo and 3. Maybe I should buy out the remainder and switch...
[Samsung Galaxy Nexus] Matcarroll:
Exactly the same here! Ffs, hurry up!
[Samsung Galaxy Nexus] bleets:
nope, would not have seen me in other threads. :)

Also, i find vodafone have better 3G coverage than orange did when i was on them 2 years ago. but hey, i'm not in yorkshire (where men are men and sheep are wary...)
[Samsung Galaxy Nexus] Matcarroll:
Is seems like everyone waiting is on o2. Maybe the roll out is on providers not imei numbers?
[Samsung Galaxy Nexus] Nail_s:
I've got mine from Handtec-first batch and stil waiting for OTA. So I think you're wrong... :)
[Samsung Galaxy Nexus] oscillik:
I know where the setting is. It doesn't work properly.
[Samsung Galaxy Nexus] webthingy:
(Un)fortunately no, I'm on Vodafone and still have not received the update.

And yes, Vodafone is said to have the best coverage (that is why I am with them), but this is one of those rare moments when I regret that (not that it's Vodafone's fault).
[Samsung Galaxy Nexus] kristovaher:
Well, it seems that the rumoured 24h+24h roll-out will not happen, majority here still haven't gotten it and it will take a whole week. Damnit. I seriously would get a replacement if I lived in UK that has the fix. This buggy 2G is annoying as hell.
[Samsung Galaxy Nexus] oscillik:
But as has already been proven by people receiving 'new' stock from online retailers, there is no stock out there that has already had the patch applied by Samsung.

I'm going to look back through this thread to see if flashing via CWM will mean that I have to apply updates that way all the time. If not, then I will go ahead and oem unlock my bootloader and go through with the manual update. This 'roll-out' is seriously taking the piss.
[Samsung Galaxy Nexus] webthingy:
Does anyone why why OTA update was streched over so long period of time, especially if it is fairly small in size?
[Samsung Galaxy Nexus] bleets:
the announcements did mention a week so i dont know where your getting your info from
[Samsung Galaxy Nexus] cellzealot:
I can assure you it does not mean you must continue to use CWM once you have OEM unlocked and rooted. You can revert back immediately afterwards to non rooted and stock configuration or whenever you so choose.

On principle, I highly recommend doing this, particularly for a user of your inclinations, to assume much fuller control over the device and your user experience.

If you need help at all with any of the procedures, please feel free to PM me or ask.

I find it hard to believe that after all the furor and angst over this mess that there is not a thread started to completely detail all of the options for managing this yourselves.
[Samsung Galaxy Nexus] zipr0:
Well, I bought mine from Clove and I'm on Sunrise Switzerland - no sign of the update, either. I have the feeling, the bug is getting more and more annoying every day - but that's probably just because I want Google / Samsung to hurry the f up. Really man - they can't have sold more than 1000 devices before they halted the shipments. How can it take so long to deploy to so few devices? WTF?
[Samsung Galaxy Nexus] mark.m.moran:
Got mine (second one) from Vodafone here in Dublin and it too has the bug....all will be OK once I get the OTA update though.....still waiting!!

Cheers,

M
[Samsung Galaxy Nexus] mehalaktas:
This information is from Samsung UK facebook:

"Samsung UK

We're currently rolling out a fix for the Galaxy Nexus volume issue which will reach everyone in the coming week."
[Samsung Galaxy Nexus] davej777:
The size is irrelevant. The number of active handsets is irrelevant. All updates are done like this.

They really should have made an exception here though.
[Samsung Galaxy Nexus] Mayflex:
GOT IT!!! :D from Media Markt Germany without volume bug as far I can see. I will do further testing tomorrow and post here!
[Samsung Galaxy Nexus] Alexander T.:
Please, test it in bootloader as well to figure out if it has any difference in hw version.
[Samsung Galaxy Nexus] IvanDobskey:
They all have the volume bug unless patched ota. You just wont see it on certain networks.
[Samsung Galaxy Nexus] ferris2375:
Sorry if I missed it, but this update broke my root. I have my bootloader unlocked, CWM flashed and it was rooted. Do I have to just re-root with the same process or is there an easier way to re-enable root?

Thanks!
[Samsung Galaxy Nexus] oscillik:
Great. Absolutely great.

I am unable to apply the patch manually using this method due to the fact that my computer seems to be unable to see my Galaxy Nexus when in fastboot mode.

This whole situation is a big clusterfuck.
[Samsung Galaxy Nexus] ferris2375:
Did you install drivers yet?
[Samsung Galaxy Nexus] Rusty!:
You'll probably need a driver from the SDK for it.
[Samsung Galaxy Nexus] cellzealot:
Did you load the Samsung USB drivers?

If so and it's still not seeing the phone then uninstall all Samsung drivers and re install the latest fresh set of drivers and reboot your PC and try again.
[Samsung Galaxy Nexus] oscillik:
Yes. I have already installed drivers. And made sure my PATH is correct.

ADB sees the phone, fastboot does not.

---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------

You wouldn't happen to have a link to these fresh set do you? The latest drivers I have installed are 1.3.1900.0
[Samsung Galaxy Nexus] cellzealot:
Give me a few min to boot PC and put them in Dropbox.
[Samsung Galaxy Nexus] Nebucatnetzer:
Are you probably using win7 64 bit? IIRC there is a solution for your problem in one of the rooting threads.
[Samsung Galaxy Nexus] ferris2375:
So no one lost root because of this update? I can't be the only one...
[Samsung Galaxy Nexus] oscillik:
Thank you very much, that would be awesome. :cool:

Yes I am running Windows 7 64 bit, like the vast majority of people with modern computers are these days. Are we really still in a period of time where 64 bit operating systems need workarounds just to get things to work? :confused: :mad: fuuuuu Samsung / Google
[Samsung Galaxy Nexus] macfre:
Everybody did. It's normal as the update script for this OTA changes permission for everything in /system/bin. It's trivial to fix it though by using fastboot.
[Samsung Galaxy Nexus] phillipm:
I had the same problem and had to install PdaNet and select the samsung USB drivers to get it working.
[Samsung Galaxy Nexus] Chirality:
The problem isn't that you are running a 64-bit version of Windows. The problem is that you are running Windows.
[Samsung Galaxy Nexus] oscillik:
You may be right...I might have to restore my clonezilla of my arch installation onto my laptop, just to get this working... :mad:
[Samsung Galaxy Nexus] cellzealot:
Just to be clear, the error you are getting in fastboot is "waiting for device"?

I just want to be certain we understand your issue to avoid further frustration.

Unfortunately, I have very low bandwidth internet here and the upload to Dropbox is taking a bit...it's a 24mb zip.
[Samsung Galaxy Nexus] oscillik:
I'm not even getting that far, when I run "fastboot-windows.exe devices" it returns nothing. Back when I had my Nexus S, running that command and variable would return with a device connected.

If it's a hassle to upload the drivers, I apologise. If it's easier for you to not upload due to your bandwidth, then I wouldn't want you to go to a lot of trouble to upload!
[Samsung Galaxy Nexus] Chirality:
Just get VirtualBox and run Linux in a VM.
[Samsung Galaxy Nexus] ferris2375:
Thanks, do you mind explaining what the trivial fix is?
[Samsung Galaxy Nexus] cellzealot:
I am running Win7 64 and there is no reason this shouldn't work.

PCs and driver issues are part of modern life...we want the latest stuff...we deal with it!(Linux users may be excused now, thanks! ;) )

These are 1.3.2410 Samsung USB drivers and are definitely the latest available and will work.

I just need another minute or two to finish the upload, sorry.

Edit: http://dl.dropbox.com/u/7632904/Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.zip

The nomenclature is different on the zip file but the MSI installer says 1.3.2410.

Remove all Samsung drivers first and then install this set and reboot.
[Samsung Galaxy Nexus] oscillik:
Yeah that's definitely later than the drivers I have installed. Thank you very much for going to the trouble of uploading, I appreciate it :beer:
[Samsung Galaxy Nexus] cellzealot:
I am going to take a shower and run some errands.

I hope to return and see that you are back to being a dangerously correct asshole...minus a bug or two! ;)
[Samsung Galaxy Nexus] oscillik:
I've just gotten my clonezilla of arch reinstated on my laptop (was the easiest thing considering i already had SDK on there and udev rules sorted out) so i'll see if i can get my phone booting CWM via fastboot, and attempt this patch! :cool:
[Samsung Galaxy Nexus] kristovaher:
Is there a way to manually get the patch installed on the device without having to lose all the data on the phone? Since in this guide they mention that all data will be lost.
[Samsung Galaxy Nexus] oscillik:
Unfortunately no there isn't.

I just carried out the instructions in that guide and it works.
[Samsung Galaxy Nexus] macfre:
Please look at posts from yesterday evening in this thread. Basically you either boot (without flashing) insecure boot.img and correct the permissions via adb, or you boot CWM image and apply superuser zip.
[Samsung Galaxy Nexus] seakins:
I had problems getting the drivers to stick until I followed this guide:

http://xdaforums.com/showthread.php?p=9861928#post9861928
[Samsung Galaxy Nexus] oscillik:
If you are still uploading those drivers to dropbox, I would still appreciate them! Thanks :)
[Samsung Galaxy Nexus] cellzealot:
oops...geez...check my edit in that post a page back, they have been up for an hour. :(
[Samsung Galaxy Nexus] oscillik:
:beer:

Thank you very much!

---------- Post added at 06:42 PM ---------- Previous post was at 06:23 PM ----------

Unfortunately, even with those updated drivers, I'm still getting the exact same outcome - adb can see the phone, but fastboot will not.

I guess I'll have to keep Linux on my laptop, which is something I really didn't want to have to do :(
[Samsung Galaxy Nexus] jabok:
Same here, it's doing my head in! Tried umpteen different things that have been suggested (on Win7 64) - various Samsung driver packages, PDANet, etc - and yet in fastboot it will not be seen. Getting right pissed off with it TBH! :mad:
[Samsung Galaxy Nexus] cellzealot:
OK, I was afraid that might be the case.

I can try to troubleshoot this with you but I am leaving now for work and it may be a very inconvenient time frame for you around midnite EDT. (GMT -5)If you haven't been able to figure it out by then we can give it a shot. My schedule is awful enough for me, let alone someone on the other side of the pond, sorry. :D
[Samsung Galaxy Nexus] oscillik:
Thanks for offering to help! There's no massive rush on getting this sorted, so I can try to catch you another time. I will likely be sleeping then, even though my sleep pattern is pretty messed up.

I really do appreciate you offering to help :D
[Samsung Galaxy Nexus] jms.flynn:
This sounds like the trouble I had, see my post below and let me know if it helps.

http://xdaforums.com/showpost.php?p=19788732&postcount=24
[Samsung Galaxy Nexus] oscillik:
Thank you, that seems to have worked. What a complete ballache just to get it working in 64 bit Windows 7!

:beer:
[Samsung Galaxy Nexus] jms.flynn:
No worries, pain in the arse for sure.
[Samsung Galaxy Nexus] mehalaktas:
Hi every body. I was trying to apply the OTA update manually. But I couldn't find out where I need to copy the zip file... Where is the /sdcard folder and how I can access it

I solved it thank you...
[Samsung Galaxy Nexus] marky9074:
The latest drivers I have found are on the manual root thread v1.4.6.0

Yesterday I had the same problems, could not detect the phone in either the bootloader or when booted up (and it wasnt a case of selecting the driver in devices, there physically was nothing detected at all....).

In bootloader mode, I happened to change USB ports and hey presto it detected and worked fine. When booted up I changed the USB mode from MTP to PTP and then it (adb devices) magically started to work...

Hope this helps someone..

Edited: lastest drivers are 1.4.8.0 here
[Samsung Galaxy Nexus] declanh:
Guys,

dunno if this merits a separate thread or not.

I'm still contemplating buying the Galaxy Nexus - but need some convincing on how successful this bug fix is.

q1) has anyone checked that the bug fix has no adverse cpu or performance/battery issues on the phone (in some semi-scientific way)?

q2) would it be worth having a poll from those who applied the patch to see how happy they are its fixed with no bad effects ?
[Samsung Galaxy Nexus] MatthewPL:
(my) q1.5) and CPU usage?

(my) q3) there is still bug in bootloader?

(why I am asking? While viewing the patch files (update is full of patch (different between old and new files) files - that is why update is only 1MB) I saw some interesting files and scripts, looks like this patch try to do something with omap block device... update firmware? I don't know, that is why asking about bootloader)
[Samsung Galaxy Nexus] rubiconjp:
What's weird is that mine came today (new batch) with a second Samsung seal on the box, on top of the first seal, indicating Samsung probably opened and flashed and resealed. But the build still ITL41D?!?
[Samsung Galaxy Nexus] marky9074:
Exactly the same as mine... two seals, but no update.
[Samsung Galaxy Nexus] rbs_uk:
And same as mine - two seals, volme bug present :(
[Samsung Galaxy Nexus] escrivel:
Uhm are they serious not giving us a statement asap?
[Samsung Galaxy Nexus] Duddyroar:
Are you forgetting that no one will have been in the office over the weekend?
[Samsung Galaxy Nexus] BiGMERF:
itss monday so its time to barrage there facebook, twitter and g+accounts with this info.. get to it guys
[Samsung Galaxy Nexus] samizad:
If I have just launched my flagship device on a Thursday, I will be in the office until the cows come home and I will have the whole bloody company in as well on double overtime, watching every post on this very forum.
[Samsung Galaxy Nexus] Duddyroar:
I'm not sure the business world operates quite like that, but I appreciate what you're trying to say. ;)
[Samsung Galaxy Nexus] Jebus99:
Engadget have reported on it - expect front page news in other places now.

http://www.engadget.com/2011/11/21/european-galaxy-nexus-owners-complain-of-erratic-volume-issue-v/
[Samsung Galaxy Nexus] Shodney:
Yeah, fair point
[Samsung Galaxy Nexus] paul_one:
any more info Duddyroar?
[Samsung Galaxy Nexus] Miracle_Nosh:
No issues here - but then I'm on Orange, and I believe they only use the 1800mhz frequency.

Sounds like a software issue, rather than hardware to me.
[Samsung Galaxy Nexus] kristovaher:
Samsung has finally posted on their Facebook page. Except not to the multiple posts about the handset. Apparently they figured it is more important to let us know that they have partnered with MSN to give you the chance to be a Samsung Mobile Explorer for the London 2012 Olympic Games.
[Samsung Galaxy Nexus] oscillik:
you are wrong.
[Samsung Galaxy Nexus] mrcliffo:
I bought the handset from 02. Whilst in areas of 3g connection the handset was fine the minute the connection dropped to a 2g the problems occurred.

I rang Samsung tech support and they advised me that it was a faulty handset and that I should get a replacement.
[Samsung Galaxy Nexus] kristovaher:
Well there's a small chance that it still might have something to do with software, or firmware at least, but that chance is pretty small. The chance of this being fixed with software is a bit larger.

This is amazingly bad if this actually affects all handsets though. Whoever was responsible for that bundle of joy is likely about to lose their job.
[Samsung Galaxy Nexus] oscillik:
granted, the problem may possibly be alleviated by a baseband update, but the problem is still a hardware issue. it is nothing to do with software causing the problem.
[Samsung Galaxy Nexus] :
It just happened to me again but this time during a conversation. The volume dropped until I couldn't hear the other party and I was unable to adjust it until I dropped the call. This bug is really annoying!
[Samsung Galaxy Nexus] kristovaher:
Correct. The issue is because of hardware, not because of Android 4.0.
[Samsung Galaxy Nexus] sblantipodi:
why are you so sure that it is a hardware issue?
[Samsung Galaxy Nexus] oscillik:
this

it is directly related to RF interference.
[Samsung Galaxy Nexus] gogol:
How do you know it is a hardware issue for sure?

Has there any confirmation made by Samsung / Google already?
[Samsung Galaxy Nexus] kristovaher:
Look at the bright side people. Now that unlocked handsets are about to be shipped all over the place, it is either possible that this issue will blow exponentially huge, or we'll see that this was a batch issue on phones released last week.

Either way a lot of new information will pour in even if Samsung keeps ignoring the problem.
[Samsung Galaxy Nexus] s1977:
Hmmm.... Could it have been that Samsung did something that only they could have done, maybe nominal changes to the hardware, but left the software for us to update as we could anyways. Its the former that we wouldn't... Just my 2p's worth.

It seems normal to me that they will (or already may be in production) correct the hardware in the coming devices as clearly it only benefits them... and if the sales are great this christmas, then its another money spinner for Samsung!

Again, its just me imagining after a few pints....:D
[Samsung Galaxy Nexus] simonjoh:
Just a thought, isnt it possible that the reason why it's got two seals is because Clove (or whatever retailer) opened the package when they were testing the devices..

Because they did say that they have tested some of the devices.. Didnt they?
[Samsung Galaxy Nexus] rubiconjp:
I bought mine from Handtec. Both seals are from Samsung.
[Samsung Galaxy Nexus] naijishi:
my first SG had 2 samsung seals and a three mobile seal as they had oviously locked it to them. my replacement from three has 2 samsung seals only and was unlocked. so looks to me as it was done at samsung.