yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] oscillik:
All that tells me is that they have had calls regarding the issue. Looks like they're just as clueless. When they contacted you, did they even ask for DDMS logs?
[Samsung Galaxy Nexus] kristovaher:
Clove told me the following when I asked about the volume issues reported:

So it is unclear if Samsung tested for this before or not, it is very unlikely (too little time), but here's hoping.
[Samsung Galaxy Nexus] forumache:
You are partially wrong ;)

You need ClockworkMod, but you don't need to install ClockworkMod.

You can send it via usb and boot from it with just one command (in bootloader mode):

fastboot boot the_name_of_the_clockworkmod_image.

Already described and used successfully in this thread, search for posts belonging to me.
[Samsung Galaxy Nexus] rs20:
Well put, I completely agree. Just to expand and be incredibly pedantic -- I'm entertained by the idea that the bootloader is "pure hardware." It just isn't -- maybe you want to call it firmware, maybe it's stored on a different chip (maybe you call that chip the 'BIOS' if it's anything like PCs), but you don't draw a basic menu on the screen and a funny picture of an Android having an operation in pure hardware. There is a tiny crumb of software in charge there.

So if they had spotted this problem at the outset, they would have coded the bootloader to deal with it (debounce??) properly. Is the bootloader updateable OTA? Not sure, it's kind of like flashing a BIOS via a Windows update -- odd. Would it be a good idea to do so if possible? Probably not, because the device would be totally bricked if it went wrong. So yeah, you're absolutely right, the problem is genuinely best left unfixed.

But of course, if this problem had been spotted earlier, the bootloader would have been coded right in the first place. So the whole 'hardware vs software' thing is still up in the air -- what percentage of other phones out there have exactly the same level of interference, but just coded it away before release? It's just a false dichotomy, pure and simple.

(Yes, it is poor that the phone was released in the state that it was. Personally, I take the glass half-full approach and am glad that I will have this phone before the year 2037 because it hasn't been tested to the Nth degree according to military specifications. Early adoption ftw!)

In other news: I just ordered myself one! :D :D :D
[Samsung Galaxy Nexus] floateruk:
Hi guys!

I saw this last night, but it doesn't seem to make any difference how many times I press retry download, it just isn't downloading it.

Does anyone have any idea how I can get it to clear or download??

Many thanks in advance!

EDIT:

Also, sorry for the MASSIVE picture. I'll try and resize later.
[Samsung Galaxy Nexus] N0matter:
Finally got my update through on sat night. Volume issue no longer a problem. :)
[Samsung Galaxy Nexus] FirstToTheLast:
at last patched this morning!

Floateruk- prob a connection issue try connecting to wifi (or data connection if you were wifi connected)
[Samsung Galaxy Nexus] floateruk:
Thanks for the response!

I'm actually staying in a hotel at the moment, so I was using their wifi. I have since left and I am on a HDSPA connection, but it's still not downloading or clearing. I've tried restarting the phone too...

Stupid thing. I could really use this update too.
[Samsung Galaxy Nexus] tylose:
Not lower, it should show ZERO spike.

If it shows even a tiny spike, then they patched it on the OS level. Which means: Galaxy Nexus is a phone with defective hardware, and this defective hardware causes you to have unnecessary CPU interrupts, higher battery consumption, and lower performance. It also causes you not to buy a Samsung phone again (hopefully).

If this is the case, we can't call it a fix, just a workaround.
[Samsung Galaxy Nexus] enlli:
You can always put it on eBay whilst the prices are high :)
[Samsung Galaxy Nexus] mark.m.moran:
Got my update this morning guys.....FINALLY!
[Samsung Galaxy Nexus] burnduck:
Why is everyone getting it but me :(
[Samsung Galaxy Nexus] charlie_cc:
Yep, I got mine this morning. That's everyone now, apart from this ^^ guy.
[Samsung Galaxy Nexus] simonjoh:
It's because everyone (at least me) is waiting for you to do a demonstration of CPU usage with the bug fix applied.. Maybe Google is aware of the situation? :eek:
[Samsung Galaxy Nexus] MatthewPL:
Why Google should be aware of this situation? It is not their fault. Samsung makes phone with hardware bugs and stops care about it (it is not easy to find abut galaxy nexus on samsung pages, there is no problem with sgs2 or note). Probably they said to Google: "So what it has hardware bugs? We can stop production if you don't like it". Samsung is even more annoying when you realize that Nexus could be even better that sgs3 and be release 2-3 mounts before it. But because Samsung doesn't want to have phone better than sgs3 so they create something weaker.

Google only tries to fix this but they cannot do much. Next Nexus will be from Motorola (probably) so situation should be better.
[Samsung Galaxy Nexus] burnduck:
I'm very much looking forward to the motorola nexus, their hardware build quality is definitely better than those korean manufacturers, it's just they need some expertise in marketing and after-sales service which google can provide.
[Samsung Galaxy Nexus] bleets:
if there's going to be a moto nexus...

nothing is for sure.

google are trying to show they won't be favouring motorola, one of the ways may be to get another manufacturer to make their phone for them.
[Samsung Galaxy Nexus] burnduck:
I thought that was the case *before* they bought motorola, now motorola mobility became (edit: is becoming) part of google i don't see any reason why they should not make a moto nexus :confused: what you have said was like asking Apple not to use icloud but to use google to sync the iphone
[Samsung Galaxy Nexus] tylose:
Exactly. I think Samsung is trolling Google. They are making sure the Nexus phones are either defective, mediocre, or lacking something, so that when they ship their new Galaxy S, there will be no competition. Remember Galaxy S II. It came just 4-5 months after Nexus S (in Europe). But it wasn't just a better phone. It was much much better.

I think Galaxy Nexus will have a very short lifespan and very soon we will be talking about it as the "worst ICS phone".
[Samsung Galaxy Nexus] jaketurbo:
I think that's complete and utter nonsense.

Many phones, ones that aren't even dual core will have ICS and will be far worse than the nexus.

The Nexus is a standard platform for google and other developers to create updates to the OS and to apps on. It's THE google phone... It doesn't need to be the most hardware advanced phone, it's meant to be a stable representation of the ideal base tech for Android 4.0.

The other more and less powerful phones will get such updates at a later date or possibly never. It will be a similar situation to the Nexus one.
[Samsung Galaxy Nexus] mjdyson:
Dont worry, you're not alone! I'm still waiting too...

I got mine from the first clove batch. Operator is GiffGaff, but that shouldnt matter.
[Samsung Galaxy Nexus] burnduck:
:o thanks

i've been trying to figure out how google roll out the updates but seemingly it's all random, fingers crossed!
[Samsung Galaxy Nexus] mcgon1979:
First batch from handtec. Still waiting too.... :confused:
[Samsung Galaxy Nexus] kms108:
i think it's samsung thats doing the update and not google.
[Samsung Galaxy Nexus] noobdeagle:
i thought we already confirmed that this is the case, cause it still happens in the bootloader hence its only 'fixed' in the os, so.....
[Samsung Galaxy Nexus] cellzealot:
http://xdaforums.com/showthread.php?t=1373879

Check that thread for a complete explanation of the volume issue fix.
[Samsung Galaxy Nexus] tylose:
By ICS phone, I mean "a phone that ships with ICS". My argument is that every single phone that is going to ship with ICS (Galaxy S3 etc), is going to be much better than GN. That's why I called GN a product with a short lifespan.
[Samsung Galaxy Nexus] kristovaher:
Eh?

Unless other phones are released by Google and be native Android 4.0, this one will have a lifespan of at least a year (and one more year, if you take into account that GN will get next major version of Android too).

Nexus phones are just about the longest lifespan Android phones out there.
[Samsung Galaxy Nexus] bleets:
hopefully it will have the lifespan of 2 years! or at least until june 2013 when i'm next due for an upgrade.
[Samsung Galaxy Nexus] tylose:
You're probably right. However, we still haven't seen anyone doing a CPU stats test. We can't really be sure until we see the test results :) But yes, the fact that the bug still exists in the bootloader suggests that it was unfortunately fixed at the OS level. And even if it still does cause a spike in the CPU usage, it is interesting to see how much. Maybe it is negligible.
[Samsung Galaxy Nexus] rs20:
What so many people seem to think:

Hardware: Hey, software, OMG OMG OMG SO MANY BUTTON PRESSES GAAAHAAHAH

Software: Oh crap, filter, filter, no, this button press doesn't look legit.

Hardware: Hey, software, OMG OMG OMG SO MANY BUTTON PRESSES GAAAHAAHAH

Software: *sweating* Oh crap, filter, filter......

etc, etc...

A perfectly reasonably alternative explanation:

Hardware: Hey, software, OMG OMG OMG SO MANY BUTTON PRESSES GAAAHAAHAH

Software: Excuse me hardware, please increase debounce time to 2ms

Hardware: Oh, K.

Hardware: (Nothing to report.)

<10 minutes later>

Software: *snore...*

Hardware: Woah, someone pressed the volume button.

Software: Score.

Even though you come to the right conclusion that this problem has every chance of being practically perfect, no matter how 'hacky' it looks, I still feel obliged to call you out on this ridiculous "Android OS / hardware" false dichotomy. They've fixed the bug in the Android software, and they haven't bothered (quite rightly) to fix the bug in the bootloader software. And if you think that "bootloader software" is a contradiction in terms, think again.

Furthermore, judging from the code posted here, the debounce code was already present (which implies that it's dead standard fare), and just not initialized properly. Either that, or the debouncing is in hardware, but not properly initialised by the software. Hardware can go mental if the hardware drivers (again, software) feed in the wrong initialization, or fail to do so entirely. So a purely software fix has every potential to be perfect.

But holy crap, why has no-one reported CPU load yet?
[Samsung Galaxy Nexus] burnduck:
Because some of us (me included) are still waiting for the OTA to become available on our phones. :(
[Samsung Galaxy Nexus] MatthewPL:
1. It is not so high

OR

2. People are afraid to check it and doesn't want to know if there still are some problems.

Anyway: could tell me anyone: before fix bug was only when interference where from outside (another phone) or from inside (calling in 2G from Nexus) too?
[Samsung Galaxy Nexus] braingravyuk:
If the Nexus is operating on a 900Mhz 2G network then you will get interference/volume issue. Think I've had my fill on waiting just about to unlock my bootloader.. taking the mickey moving the location of a signed update on the stock recovery.
[Samsung Galaxy Nexus] MatthewPL:
But whole time or occasionally (when I am making a call or somebody near me)?
[Samsung Galaxy Nexus] braingravyuk:
At my work place I very rarely get a 3G connection so pretty much 99.9% of calls I receive result with me having to keep hold of the volume up key, not experienced it with anyone near me being the cause. Like I said though if your network isn't running a 900Mhz 2G then you'll be fine.
[Samsung Galaxy Nexus] rokfor2000:
For those curious out there. I don't know how good Norton Utilities is, but it doesn't show a single spike on a CPU when I try to reproduce a bug.
[Samsung Galaxy Nexus] MatthewPL:
Unfortunately in Poland (we will have, probably, Nexus in 2nd half of December) 3G network is rare but as many people said before software fix resolve the problem and:

so there is no reason to not buy this phone (this will be my first smartphone and/or android).

Only hope that next Nexus will be made by Motorola or at least SE. And will be tested much better.
[Samsung Galaxy Nexus] mcgon1979:
The fact my 600euro phone is still useless after 11 days is useless. Getting very annoyed with the lack of urgency about this "rollout".... :mad:

Yes I could apply the fix manually but that doesn't excuse this tardy rollout.
[Samsung Galaxy Nexus] dunetails:
Update is rolling out in the UK right now,ive just installed it OTA
[Samsung Galaxy Nexus] attu90:
Ive just recieved the update and installed it but im stuck at the green android with the red triangle, its been like that for about 10 mins ...is this normal ?

im tempted to pull the battery but will that brick my phone ?
[Samsung Galaxy Nexus] burnduck:
My GN finally got an OTA!!

youtube video showing CPU usage in Android and Bootloader after the break!

Here!: (or you can click to the next page) http://xdaforums.com/showthread.php?p=20021386#post20021386
[Samsung Galaxy Nexus] dunetails:
A red triangle doesnt sound good,i got a blue spinning tetrahedron (or somethjng)
[Samsung Galaxy Nexus] burnduck:
you should see an android with a spinning hexagon ball ("Buckminsterfullerene" anyone??) and a progress bar at the bottom of the screen

this stage took me about 2 minutes then the phone will restart and you will see "android is upgrading" and another progress bar optimising all your apps.

---------- Post added at 12:09 AM ---------- Previous post was at 12:01 AM ----------

Post-OTA CPU Usage Test (and Bootloader test)

http://www.youtube.com/watch?v=h3T4my6Eyf8

So from this not-so-scientific test this patch (ITL41F) does seem to address the volume bug without significant impact on CPU or system responsiveness.

Like someone mentioned earlier this patch was applied to the Android OS but not the lower level (such as firmware) so the volume bug can still be triggered in boot loader mode.

I've also tried pressing the volume button on GN while another phone was emitting 900MHz GSM signal, and there was no problem controlling the volume of my Galaxy Nexus.

(GN responded to human input without erratic behaviour)
[Samsung Galaxy Nexus] MatthewPL:
The happiest day of our lives. :D
[Samsung Galaxy Nexus] attu90:
Ive pulled the battery and im back up and running, havnt a clue why its not installed the update correctly.

My phone is routed but is on the standard rom and the update came through to my phone ota and i just pressd "yes" to update and it restarted with the green androind and red triangle ?

Im on 3 so dont realy need the update but its a bit of a worry for future updates.
[Samsung Galaxy Nexus] Tom Servo:
If I've seen the correct diffs, then nothing in the kernel changed at all, except some runtime parameters, i.e. setting debounce times.
[Samsung Galaxy Nexus] burnduck:
That's the one I'm talking about
[Samsung Galaxy Nexus] wolfedude88:
So I live in the US and have the Galaxy Nexus on AT&T and anytime I am in edge or 2g as it is referred, I experience the volume bug. How is that possible? I thought we weren't on the 900mhz frequency?

Also it appears I have the samsung build number as someone else pointed out in another thread? So what does that mean for OTAs?

Thanks
[Samsung Galaxy Nexus] rs20:
I don't understand what's so contradictory about your situation -- the bug appears to always be exhibited when using 2G at 900MHz, which is what you just described.

And yes, you have a samsung build number. ITL41D is the old version with the bug, ITL41F is the fixed version.

The OTA upgrades you from ITL41D to ITL41F, and thereby fixes the bug.
[Samsung Galaxy Nexus] cellzealot:
Except that the US carriers don't use 900mhz, they use 850/1900 band, so that doesn't make much sense. :confused:
[Samsung Galaxy Nexus] wolfedude88:
Exactly, that is why I was so confused why my phone keeps doing it. Also I cannot get the OTA because of my phone being shipped with the Samsung build as described in another thread here.
[Samsung Galaxy Nexus] GrkEngineer:
I also got the red triangle with exclamation mark. Was not able to upgrade and not getting notification for upgrade anymore. I want to just do it manually, but feel like I'd rather wait to try the OTA again to see if it was a fluke. I am running CWM recovery. Would this cause the OTA to fail?
[Samsung Galaxy Nexus] l1233799:
Got mine last night finally.

Clove (first patch) + O2 UK
[Samsung Galaxy Nexus] enlli:
But 850 may also be affected as it is quite near the 900MHz band whereas 1800/1900 isn't
[Samsung Galaxy Nexus] malliktajmahal:
I am from India and got gn from clove(unlocked). will i get OTA...??

when I tried to update it says your system is up to date.

between i do have volume bug.

And also please mention, to get OTA what should I need other a working internet?
[Samsung Galaxy Nexus] s.m.knipe:
People in the US and Canada have gotten the update, so there is no reason why you would not. The update server(s) (at Google) just needs to be able to trigger the notification in your phone when your phone's ID number is selected for the update (i.e. a working internet connection).

---------- Post added at 12:07 PM ---------- Previous post was at 12:04 PM ----------

Yes, the issue might actually be at the lower end of the 900 mHz range and upper end of the 850 mHz range (an "850 mHz" signal might actually hit a high enough frequency to hit the minimum threshold that triggers the "bounces" or false key presses)...

Also, there are things in the US that do use the frequencies including and surrounding both 850 - 900 mHz (old garage door openers, household cordless phones, even aircraft landing/takeoff protocols)
[Samsung Galaxy Nexus] Fpad77:
Got mine last night too, Clove as well. I almost imagine it that someone was having to manually type in all the ID's of the phones given the speed they've been dishing out the OTA hah.
[Samsung Galaxy Nexus] attu90:
Ive done a factory reset and the update came down again but it failed to install the update just as it did the first time, infact ive tried a third time so i havnt a clue why it wont install.

Has anyone else who has routed had the problem or is it just GrkEngineer and myself ?
[Samsung Galaxy Nexus] cellzealot:
You must be stock to apply the update because its signed and asserts specific parts of the OS before it runs. It will also unroot you because it overwrites permissions for the system.

After applying the update you can easily reroot by fixing those permissions via adb shell.
[Samsung Galaxy Nexus] kms108:
is it because the bootloader is unlock, so phones wont update if bootloader in unlocked.
[Samsung Galaxy Nexus] pratik88:
Post OTA update volume problem

I received the OTA update a couple days back and updated the OS. The build number now shows ITL41F, which i believe is what it should show once its updated. I never experienced the serious volume problems (in-call volume drops, rapid fluctuations etc.) but i have been having a minor one, which has persisted even after the update. While using GTalk, almost every time i receive a message, the volume drops. I got a volume locker app for now which works well, so its not really a deal breaker. I was just wondering if anyone else has experienced this.
[Samsung Galaxy Nexus] enlli:
I use GTalk quite a bit and I can't say I have any problems. Used it with messages and with Video
[Samsung Galaxy Nexus] malliktajmahal:
Thanks I have got my OTA after an HR..Its fine now.
[Samsung Galaxy Nexus] Equinox102:
I'm running ITL41F with modem XXKK6 and I'm still experiencing the issue when I fall back to GSM. (Once a week if that)

Is anyone else in the same boat? Very weird. I applied ITL41F manually.
[Samsung Galaxy Nexus] enlli:
Can't say I have experienced any problems at all since the upgrade. Been in a couple of 2G only spots (like driving through a tunnel!)
[Samsung Galaxy Nexus] trickyrickxx:
Hi i have my first andriod phone and love it apart from the fact it randomly switchs itself to airplane mode and it is really starting to get on my wick . I have the samsung galaxy nexus if anyone could help i would be very happy thanks rick
[Samsung Galaxy Nexus] Duddyroar:
I sent the log you mentioned, not sure if they've looked at it.

They want me to send my handset in so they can check it. I pointed out that most phones seem to have the fault, but they're keen to have a device which has been out in the field and is 'confirmed'. Seeing as my phone is the one in the video being linked to by Engadget and Gizmodo, I guess it's a suitable candidate!

Again, I'll keep you all posted on events.
[Samsung Galaxy Nexus] justabrake:
someone changed there mind here Don't know why after a couple of days of saying he didn't have a problem but now has one and wanted to change his vote , so maybe he went into another zone
[Samsung Galaxy Nexus] oscillik:
Well, sounds like this is the best news we're going to get on the matter at the moment. So Samsung want your clothes, your boots and your motorcycle (read as: your handset). Hopefully some good can come of this.
[Samsung Galaxy Nexus] jms.flynn:
I take it you mean me, I want to change my vote because genuinely I did not have an issue. I only picked the phone up on the Friday, been at home all weekend where I get a constant 3g/HSDPA signal. I am in work today 20 Miles away and it is doing it like crazy.
[Samsung Galaxy Nexus] gambiting:
I had the same situation - got the phone Saturday morning, was playing with it all weekend long, but I've got a full 3G signal at home. Went to university in town today, as soon as the signal dropped to Edge the issue started.
[Samsung Galaxy Nexus] coleburns:
ok, volume issue aside, is no one else bugged out with the placement of the volume buttons? Even when i'm not experiencing the volume issues, i am constantly either turning the volume up or down.........

ARRRGGGGHHHHHHHHHHHHH!!!!!!!!!!
[Samsung Galaxy Nexus] paul_one:
luckily (or disappointingly) 3 have emailed me saying I need to ring and verify some details before my order will go through.

I've been thinking about cancelling that and trying to buy in store anyway.

BUT given this opportunity, do you guys still think it's valuable to try and grab the nexus for some tests or is it more worthwhile to wait until we get more news from Samsung/google?
[Samsung Galaxy Nexus] HUNZwiebel:
Is it only on "G" network?

Is it only affect the phone when it is on the G (GPRS) (2G) network and not when it is on HSDPA, or on 3G? Can it be a software problem...? (I think)
[Samsung Galaxy Nexus] oscillik:
please read the thread. especially the first post.
[Samsung Galaxy Nexus] gambiting:
I already have the phone,and amazing as it is, I would wait for a solution if I were you. It's just a massive let down, that as soon as you enter a 2G only zone, your phone stops being....a phone.
[Samsung Galaxy Nexus] Tom Servo:
Here's something people could try: Find some very fine and tight meshed wire grid at the hardware store and put it beneath the battery. It can't be too thick, or else the cover would presumably not close.

If the antenna is placed on the casing, the offset of the battery compartment could be used for additional shielding, to some electronics. There's a slight possibility the interference isn't caught at the knob itself but elsewhere.

A guess only, tho, for a temporary fix.
[Samsung Galaxy Nexus] paul_one:
tbh it could well be a driver issue with the newer kernel/module.

I'm guessing ginerbread wouldn't work normally due to a lack of specific driver for that wireless chip.

I like the idea of it being hardware, but am finding it hard to believe that you'd get a specific sort of resonance at 900mhz to change volume, while 1800mhz is just fine..
[Samsung Galaxy Nexus] cymatty:
I would be interested to see if anyone on Orange or Tmobile has this issue as I am aware that they use different parts of the spectrum for thier network.

Looking at picking one up on Thursday and obviously do not want to if the bug is present on Orange.

Thanks