yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Chirality:
I think the point is that, by looking at whether the updated baseband has any effect in bootloader mode, we can get a better idea what was wrong in the first place and what the update may have fixed.
[Samsung Galaxy Nexus] nobody850:
i cud not continue using the galaxy nexus, this problem is killing me, one of the mine uses of the phone is to call and some of these calls are important but if sound keeps going up and down while i am talking and with out talking then i can not uses it.

took my sim card and shoved it back to my galaxy S.
[Samsung Galaxy Nexus] neovisage.HD2:
Right my GN don't wanna sent any txt mssg i was trying reboot and I can't is stuck in odin mode wrrrr
[Samsung Galaxy Nexus] nookcoloruser:
Same here. I sadly, just sold my BB Bold 9900, so I've had to go back to using an ancient at this stage Samsung Toco in order to make and receive phone calls....
[Samsung Galaxy Nexus] Skysurfer69:
posted in error; ignore
[Samsung Galaxy Nexus] djcr33p:
I got my Galaxy Nexus on the 25th and haven't experienced the issue yet. I even manually switched to 2G networks only and whenever I checked my ringer volume it was still on full.

The issue I am having is trying to transfer files on my "performance edition" of Windows XP via MTP? I for the life of me can't get Windows to recognise the device. Doesn't even see it in WMP11 - In the device manager it shows as "galaxy!" and another device "MTP!"

I've got the Android SDK with 4.0 and the Google USB drivers but I need to install something to get my machine to recognise this device. Sorry to hijack the thread but if anyone can give me a tip I'd appreciate it. I can transfer files over wifi and such but it's laborious to say the least.

EZ
[Samsung Galaxy Nexus] Dr Doom:
On Friday they said it would be out in the next 2 days. I agree though that Sunday seems somewhat unlikely for a general release
[Samsung Galaxy Nexus] Ladrero:
Do you talked to Samsung directly?
[Samsung Galaxy Nexus] webthingy:
The guys here on xda creating custom ROMs already implemented the fix. I am not sure what keeps Google/Samsung from releasing the fix to the public.
[Samsung Galaxy Nexus] Duddyroar:
They have? Is it confirmed to completely fix the issue?
[Samsung Galaxy Nexus] webthingy:
Yes, they have. How they got it before the general release is yet another mistery. I have not tried personally any of the ROMs, but apparently it should work and it is the same fix that is still to be released.

See Android Revolution HD™ or Ir1 Modaco at Samsung Galaxy Nexus >

Galaxy Nexus Android Development
[Samsung Galaxy Nexus] Dr Doom:
Yup on the phone
[Samsung Galaxy Nexus] Ladrero:
Very interesting, thanks!
[Samsung Galaxy Nexus] Atreus:
I just checked both threads you mentioned, and there's not a word about the volume bug being fixed.

So: Volume bug stays unfixed for the moment. We'll have to wait for the actual release by Samsung/Google.
[Samsung Galaxy Nexus] webthingy:
Please check the following:

Revolution HD

http://xdaforums.com/showpost.php?p=19718107&postcount=135

Ir1

http://xdaforums.com/showpost.php?p=19679932&postcount=19

Yes, the fix has not been even listed among the features of these two ROMs, but reading those two posts made me think the two ROMs got the fix implemented. Could anyone confirm that?
[Samsung Galaxy Nexus] Tom Servo:
I was at my mom earlier. I have spotty EDGE signal there. I had the phone in my pocket most of the time, yet the battery graph took somewhat of a nose dive that time. So the unfixed bug definitely has a decent impact. Someone several hours in a ****ty zone could drain his battery regardless of use or not.
[Samsung Galaxy Nexus] oscillik:
are you running the I9250XXKK5 baseband?

edit: sorry I misread. re-read it and saw that you said "unfixed bug"

my ignorance there! sorry :(
[Samsung Galaxy Nexus] Proyoyo:
No, the fix isn't implemented yet. Apparently from Paul's twitter channel, he just received the bug fix 1 hour ago:

https://twitter.com/#!/PaulOBrien
[Samsung Galaxy Nexus] darkoroje:
Those two posts do not mention that this ROM has the volume fix. Please read them carefully.
[Samsung Galaxy Nexus] oscillik:
so the fix appears to be mostly kernel? Interesting...
[Samsung Galaxy Nexus] webthingy:
Thanks. What about Revolution HD? As I am a junior member, can't post there :(

...or "outside links" for that matter.
[Samsung Galaxy Nexus] Proyoyo:
Nope. None of the custom ROM has the fix for the volume bug yet.

But, I think we'll be able to see it in 1 or 2 days since our developer has received the new update :)
[Samsung Galaxy Nexus] webthingy:
I would not be surprised if the custom ROMs got the fix first anyway.
[Samsung Galaxy Nexus] ameedi600:
Verizon to get galaxy nexus on Dec. 9, the wait is finally over. My source is the local Verizon store.
[Samsung Galaxy Nexus] ericshmerick:
Actually, the wait is 13 days :-)
[Samsung Galaxy Nexus] ameedi600:
I meant the wait for an official release date.
[Samsung Galaxy Nexus] neovisage.HD2:
:(where is the OTA what everyone talk about?should be today buuu I keep checking and nothing :(
[Samsung Galaxy Nexus] s1977:
You might as well follow Paul O'Brien on Twitter here:

https://twitter.com/#!/PaulOBrien

He's just said that the update doesn't fix the Bootloader though, not as if we will be on that mode for a long time anyways!
[Samsung Galaxy Nexus] oscillik:
what does this have to do with the topic of this thread?
[Samsung Galaxy Nexus] burnduck:
Where is the update everyone is waiting for? I didn't pay 530 pounds to buy a 3G only phone :(
[Samsung Galaxy Nexus] mdh007:
tweeted 3 hours ago: "Hope to be able to release the volume bug fix for everyone tomorrow. Watch this space."

from: https://twitter.com/#!/PaulOBrien
[Samsung Galaxy Nexus] bobbysixkiller:
hmmmm will that sucks that he can release but google cant! fair play to the man!
[Samsung Galaxy Nexus] burnduck:
Isnt that a custom rom?
[Samsung Galaxy Nexus] bobbysixkiller:
sounds like it will be a 'fix' rather than one of his roms
[Samsung Galaxy Nexus] Chirality:
What the heck. SamFirmware says the fix is a radio update. Paul O'Brien says the fix is an updated Android kernel. What is going on...
[Samsung Galaxy Nexus] MysteriousDiary:
I think paul is working on an own fix, but he isn't talking about the official one. But not sure.

But well, just wait until we here something official. the samfirmware guy has nothing to do with samsung and it seems like he just copied a tweet..not more.

https://twitter.com/#!/samsguy/status/140808560782225408

https://twitter.com/#!/samsguy/status/140744805306216448
[Samsung Galaxy Nexus] bobbysixkiller:
sometimes you can fix the same issue in many ways,

are samfirmware offical?
[Samsung Galaxy Nexus] terminal.illness:
A radio fix would probably be closest to the issue without it being a hardware redesign.

Though we don't even know if that radio "fix" is official or anything related to the issues we're having.
[Samsung Galaxy Nexus] MysteriousDiary:
No, it's not and he just copied the tweet content of another guy.
[Samsung Galaxy Nexus] mingoid:
Paul O'Brien says he has the kernel but not the source, so I presume that is the official fix.
[Samsung Galaxy Nexus] jackt6509:
thanks for the update!!

for the record its a software problem its a new radio version released with ICS and its not decoding the code on 2g networks correctly causing errors that in this case involve the volume disappearing.
[Samsung Galaxy Nexus] mingoid:
Where do you get that from?
[Samsung Galaxy Nexus] dwj:
+1 for that. Also, the punctuation and grammar make the post difficult to understand anyway.
[Samsung Galaxy Nexus] MatthewPL:
So why bug also appears in bootloader? As far as I know bootloader doesn't decode any network code.
[Samsung Galaxy Nexus] bobbysixkiller:
seriously this is not on, being on o2 and staying on the outskirts of London this week my phone was unusable.

i love this phone, but people should be working day and night to get this fix out in some form, over the air, or downloadable, even if it means wiping the phone, i don't care i just need my phone to be a phone!
[Samsung Galaxy Nexus] neovisage.HD2:
they are think we are loosers I'm słowy so........ off with all this situation
[Samsung Galaxy Nexus] bobbysixkiller:
its not on, i needed to sell my SGS2 to get this phone, and i have been left truly buggered...

i know these things happen but get the whole dam android team working round the clock with updates for us who folked out a lot of money until its fixed!
[Samsung Galaxy Nexus] nookcoloruser:
Similar story, I sold my Bold 9900 which despite lack of Apps, small screen etc, it made great phone calls and had great reception even in weak areas.

The nexus despite its looks and big ass screen has been a dissapointment so far. A phone can be as smart as you like, but without the ability to make calls on it properly it's nothing but a glorified iPod touch, albeit one that is unable to play music because the volume bug still kicks in..... Aghh.

I want to fall in love with this phone, heck it's meant to be an 18 month relationship after all - its very difficult to do so when it's usage is sullied to such an extent on what is sold as the 'flagship' android experience,

It does make we wonder about the method of the testing of hardware like this before it's released. Because such a crippling flaw should have been discovered before launch.

I'm hoping it's released by tomorrow - at the moment I'm suffering a very bad case of early adoptee remorse.
[Samsung Galaxy Nexus] burnduck:
I've been using the phone on 3g mode for the past week, which was kind of fine in london except I got no signal at my work place. The main reason I didn't buy it on contract with 3 is that I need 2g fall back support and my phone is failing me! This is ridiculous Samsung and Google, I didn't like Samsung because I've heard their build quality was poor but thought might give them a chance, at least this phone is backed by Google. Turned out I was wrong, very wrong indeed.

At this point I'm seriously considering of returning the phone. :( I don't deserve to be treated like this
[Samsung Galaxy Nexus] Evostance:
Paul O'Brien tweeted earlier that he might be able to release his fix for it tomorrow :)
[Samsung Galaxy Nexus] PooJou:
Hi guys - a post from Down Under!!

I have not been able to make the volume bug show its face even when I lock to 2G. I believe that Telstra's 2G network is 900GSM as well.

Strange huh?

And there's pretty much no chance of it happening when I have 3G on due to Telstra's network's uncanny ability to blanket everything in beautiful 3G goodness haha.
[Samsung Galaxy Nexus] Proyoyo:
Try to use a old Nokia phone running on 2G 900GSM and put it beside your Nexus. Then, call the Nokia phone using other phone & see whether the bug will appear or not.
[Samsung Galaxy Nexus] PooJou:
I don't think I have a phone that old... will try to find one tho!
[Samsung Galaxy Nexus] Chrono_Tata:
Just a post to clarify, using the 900 MHz won't automatically mean that you will get the interference. As the name implies, a frequency band is a range of frequencies which, in the case of the 900 MHz band, could vary from around 850 to 950 MHz. The actual frequency range that is causing the interference is most likely very low and it's possible that a different network, even using the same frequency band, might not be hitting that particular frequency and at a high enough power to cause the bug.
[Samsung Galaxy Nexus] Evostance:
I had it once at home and once on the train and I'm on o2 and my signal changes in and out of 2g all the time. Twice over 4 days isn't bad
[Samsung Galaxy Nexus] kristovaher:
Well, it is bad since the problem exists. I would like samples where it is not the case at all. This way we could know if it actually affects all phones, or is a faulty batch.

Sadly you're affected by this issue so you can expect to run into this problem more in the future, especially in areas of worse reception.
[Samsung Galaxy Nexus] oscillik:
there are currently two threads regarding this issue (this one, and the Volume down/mute thread). If you look through these threads you will see that the problem doesn't occur when in airplane mode.

I myself have had the phone in bootloader and recovery mode (both of which do not have the radios enabled) and the problem does not occur.

Actually twice over 4 days is bad, since it shouldn't be happening in the first place.

Let me make this clear to people who might be in denial: a mobile phone that has been manufactured to operate on certain frequency bands (in this case, bands 850/900/1700/1900/2100) should work on those bands without causing problems. If the phone does encounter problems while operating on the frequencies it was designed to use, then the phone is defective.
[Samsung Galaxy Nexus] coleburns:
OK, I had thought that this wasn't an issue, however it has happened some many times now it is insane

The worst is when you switch to speakers, it just hangs and the button is unresponsive. Also, The more annoying thing is the placement of the volume buttons. My finger keels accidentally touching it.

Not happy
[Samsung Galaxy Nexus] oscillik:
The placement of the volume rocker has nothing to do with this particular issue. The fault is almost certainly tied to RF interference encountered while the phone is in a 2G network mode (either by choice, or by proxy of the phone being in a 2G-only coverage area).
[Samsung Galaxy Nexus] Duddyroar:
I'm not so sure about that. I only seem able to trigger the issue when I lightly touch (not press) the volume rocker - it's as if my finger is creating a connection which causes the problem.

Although I think I've had instances when the fault has happened when I'm not touching the rocker, I now struggle to replicate the problem without touching it.
[Samsung Galaxy Nexus] oscillik:
I personally have experienced the issue without touching the rocker at all. Many others have also. The only possible correlation would be the phone transmitting stronger due to loss of signal because of something blocking it's reception. This being your hand/fingers.

Regardless, this problem isn't a mechanical issue to do with the buttons being overly sensitive when being pressed. As already mentioned, many of us are experiencing the problem without touching the volume rocker.
[Samsung Galaxy Nexus] Duddyroar:
That makes sense. Like a death grip, I guess?
[Samsung Galaxy Nexus] 318vert:
This morning while streaming music to my car the volume went up to max and i couldn't turn it down for a few mins so its not just mute.
[Samsung Galaxy Nexus] jms.flynn:
I would like to change my vote I am now having this issue :(
[Samsung Galaxy Nexus] timshields:
Just spoke to Samsung - they told me it is a software issue and I need to go back to the retailer to get a replacement.

The girl I spoke to said she was not aware of the issue - I asked how many people would it take before Samsung recognise there is a problem. She simply insisted I got back to P4U...
[Samsung Galaxy Nexus] oscillik:
Kind of...except this doesn't kill phone reception. It just (possibly) exacerbates the issue we're experiencing.

Either way, this problem is extremely troublesome.
[Samsung Galaxy Nexus] jadaress1:
Hi, I've been having problems but its just when I'm making phonecalls but the thing is that I have no data on at the time at all, no 2g or 3g, I always switch it off while I'm at home and just use wifi, I'm getting it on nearly every phonecall happened 7 times yesterday.
[Samsung Galaxy Nexus] Duddyroar:
Sound like a stock company response. We already know that people are getting replacement units with the exact same problem, so taking back to the store isn't going to solve anything.
[Samsung Galaxy Nexus] dg1qkt:
This does not make sense at all, either it is hardware so an exchange might help, or it is software, then an exchange won't help.
[Samsung Galaxy Nexus] Chirality:
I wouldn't rule out mechanical issues just yet. Seeing as some people experience the issue while lightly brushing the volume rocker while others experience the issue without touching the rocker at all, I think it's possible that it's a combination of mechanical issues and electronic issues. Perhaps the volume rocker is faulty - the circuit for the volume down button is being connected when you lightly brush against the volume rocker, or in the more extreme cases, when you are not touching it at all. But because this contact is weak, the circuit has a lot of resistance, and the current passing through this circuit under this light contact condition is being filtered out by some circuitry inside the phone (sorry if this is nonsense, I'm not an electrical engineer.) However, when the 2G radio is transmitting, the circuitry that normally filters out this noise fails, and the system starts getting intermittent currents from the volume rocker. Due to the light contact that the circuit is making, the current fluctuates rapidly from the on state to the off state, triggering very rapid activation events to be registered by the system.
[Samsung Galaxy Nexus] kristovaher:
My humble apologies that I did not make it so that people can change their votes. I simply did not expect it to be an issue that depends on 2G radio. I thought that people either have it straight out of the box, or not at all.

If an administrator could change it so people could change their votes, it would be most welcome!
[Samsung Galaxy Nexus] kristovaher:
That is nonsense by Samsung. If it is a software issue then you do not need a replacement. Replacement is needed only if it is hardware issue, since software is same across the devices.

People in UK should continue calling Samsung, they should notice at one point that something is wrong, since they seem to ignore their Facebook page!
[Samsung Galaxy Nexus] oscillik:
the problem affects volume entirely, not just volume down/mute. Hence why the thread is titled "Do you have an issue with Galaxy Nexus volume changing automatically?"

I am on the phone to them at the moment, the girl I just spoke to is clueless about the problem and advised me to take it back to the store I bought it from. I have asked to be put through to a supervisor and I am currently on hold waiting.

This is most certainly not a software issue.
[Samsung Galaxy Nexus] Duddyroar:
Not sure if this video has been posted on this thread yet, but there's the fault in action:

[YOUTUBE]B6xlZFcgPlo[/YOUTUBE]
[Samsung Galaxy Nexus] PooJou:
Yep, understand - this is what I think is happening here for me. have not seen it drop at all!

(And really don't want to see it drop ever tbh)
[Samsung Galaxy Nexus] Duddyroar:
That only helps people who want to install custom ROMs, though.
[Samsung Galaxy Nexus] Rubu:
He supposedly got hold of the official fix, so at the very least we'll be able to see how it performs, and if there's still anything going on when you introduce interference. I do really have the feeling the OTA will start to roll out any day now :) Hope so too, can't wait to order but since I will be in 2G areas on a 900Mhz network, I'd like to see how it performs before I place my order.
[Samsung Galaxy Nexus] Duddyroar:
Totally understand your perspective, it's just a bit annoying that early adopters are being used as beta testers for everyone else, though.

If the fix isn't released in the next few days then I fear I may break something - the Galaxy Nexus, most likely. I've had several calls now where the volume has dropped right off and I've had to attempt to explain that my new £500+ phone isn't actually that great at making calls...
[Samsung Galaxy Nexus] webthingy:
Judging by how Paul was surprised to see what the fix was, I have this strange feeling that this version of the fix is still to be further tested which may mean further delays for us.
[Samsung Galaxy Nexus] Dr Doom:
Appreciate this may have been asked earlier in the thread but I presume the fix will also remove any issues when the networks switch their 3G to 900mhz?
[Samsung Galaxy Nexus] Mehrsau:
Of course. It's not about the kind of generation they are running on 900mhz. It's the frequency itself.
[Samsung Galaxy Nexus] bobbysixkiller:
poor poor show google

a ruddy update would be nice, with a ETA?
[Samsung Galaxy Nexus] dirtyhank:
Paul just released the Volume Fix:

http://android.modaco.com/topic/348909-28-nov-ir3-mcr-new-volume-bug-fix-faster-rotate-more/
[Samsung Galaxy Nexus] oscillik:
In his own custom ROM.
[Samsung Galaxy Nexus] bushbrother:
Standalone here:

http://android.modaco.com/topic/349073-28-nov-r1-volume-bug-fix/
[Samsung Galaxy Nexus] dirtyhank:
It's a stock kernel so I guess it can be installed on other ROMs. You guys give it a try.
[Samsung Galaxy Nexus] oscillik:
It's really cool that PaulOBrien has been able to cook this up so quickly for those who want to try it. Shows a lot of dedication on his part to the Android community :)

Hopefully Google will also show their dedication to the Android community and release the fix for those of us who do not wish to tinker around with the handset.
[Samsung Galaxy Nexus] kristovaher:
I am still afraid of rug being pulled from under us though. Last week they said the fix was already developed and that they were flashing devices. But now it's all quiet all around, there just might be that the fix will not really be a fix and will not really change anything other than the volume bug - leaving the phone still very unresponsive while the problem happens.
[Samsung Galaxy Nexus] Duddyroar:
Paul says he's still testing the fix (despite it being released and official), which doesn't sound very hopeful.

If the fix isn't 100% tested, what the heck are Samsung flashing all of the withheld phones with as we speak?

---------- Post added at 11:02 AM ---------- Previous post was at 11:01 AM ----------

Agreed, I get the horrible feeling that the OTA fix isn't coming any time soon.
[Samsung Galaxy Nexus] bobbysixkiller:
ffs google update us! we deserve that at least.

i tweeted, everyone who i have linked with official android/google/samsung

not happy.

i moved away from sgs2 so i did not have to root and rom any more, stock android with timely updates, no messing just a good android phone grrrrrrrrrrrrr
[Samsung Galaxy Nexus] Rubu:
Anyone willing to flash and run some tests? Bootloader and CPU load springs to mind...

If it's really the official fix, like Paul said, it will perform identically.
[Samsung Galaxy Nexus] M2281088:
Unfortunately if the fix is not made available in the next day I am going to have to return my phone.

I understand that Samsung and Google have got to test, but we only have a limited amount of time to return faulty goods.

I love this phone but I am not one to sit back and let poor customer support cost me my own money.
[Samsung Galaxy Nexus] oscillik:
I think we're all basing our perceived hopes and disappointment on some internet hearsay.

We have no confirmation from anyone, other than retailers and a twitter account here and there, that Samsung are actually currently flashing handsets before they're being sent back out to retailers. As we know, the retailers have been wrong about information pertaining to not only the release of the Galaxy Nexus but also regarding this particular issue. There are still some retailers that assert the issue is not a hardware related one.

However, if Samsung really

are

flashing handsets with a fix, it really does beg the question: why haven't existing handsets been pushed the fix also?
[Samsung Galaxy Nexus] jabok:
Same here. It's 14 days for faulty goods isn't it?

I feel like it sending it back anyway just as a minor "f**k you" to Samsung and Google given their lack of communication on this!
[Samsung Galaxy Nexus] oscillik:
You have 6 months to return faulty goods under your statutory rights
[Samsung Galaxy Nexus] M2281088:
I still feel that the week has shown how much Samsung care about their customers.

The 14 days is the standard distance selling rules for ANY return. But, yes the statuatory rights give you 6 months to return faulty goods.