yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Roni1979:
A Information from Samsung Mobile in Facebook. Sorry if I've overseen any statement about this.

They write nothing special only that the SAV Bug will be fixed soon.

I can't set a link to it because I'm writing with my mobilephone.
[Samsung Galaxy Nexus] Emama:
I can only see complaints in Samsung UK in facebook,

did not check other though
[Samsung Galaxy Nexus] PaulCayard:
I didn't find it :(
[Samsung Galaxy Nexus] qwerp_:
btw, i just found out something old (new), if you want to re-produce fault, the other phone must be in 2G only, not even EDGE, when the phone is on EDGE, the fault will not kick in.

i was at one of the phone 2U store, trying to demo the fault, because the signal there is strong, even switching it to 2G only gives me EDGE, and i am not able to re-reproduce the fault, in the end, i have to show him a video i made earlier.
[Samsung Galaxy Nexus] Roni1979:
Sorry my fault. I've seen that this Facebook page is only a fan page. http://www.facebook.com/mygalaxynexus?sk=wall

Sorry again.

'
[Samsung Galaxy Nexus] 318vert:
In case the fix they release sorts the issue out by reduces the radio power or changing the frequencies can we do any logging before they fix it incase the fix means we lose signal easier so we have something to go back to them with? Can we measure signal strength etc...
[Samsung Galaxy Nexus] oscillik:
You can find out signal strength by going into the Phone app and hitting

*#*#4636#*#*

and then going into Phone Info

however, the signal strength will fluctuate wildly due to the nature of mobile phone signals, so you wouldn't really be able to get anything conclusive.
[Samsung Galaxy Nexus] paul_one:
is it possible to get a CPU graph/history while the volume bug is shown?

That way we can see:

1) how much it affects CPU

2) If it is effectively 'hidden', if the CPU is still affected by external forces
[Samsung Galaxy Nexus] oscillik:
we can grab DDMS logs via the Android SDK

here is an extract from one of my logs I force the phone into 2G mode on line 28, and you can clearly see multiple buffer overruns immediately after it.
[Samsung Galaxy Nexus] MysteriousDiary:
Don't have a GN so far but if I've seen it correctly in a video there should be a new option in the developer options to see the cpu usage all the time in the top right corner.

http://www.youtube.com/watch?v=gctWY0m2-M0 (at 28 seconds he activates it)

Would be nice if someone could check how much it increases while the bug happens so we can compare it to a value after a possible patch.
[Samsung Galaxy Nexus] Evostance:
I'll just take it to a shop in bootloader and show them the hardware is defective
[Samsung Galaxy Nexus] paul_one:
Cheers, I did see that earlier... But doesn't that rely on the underlying kernel/libraries passing it up to the dalvik layer?

What I mean is, if they fix the lower level keypress interpreter, we may see a blip in CPU but not any debug messages being produced at the higher level, as they are being 'dropped' earlier on.

Thanks very much for that - I forgot I had seen that on youtube.

Would be helpful to have a graph (easier to show you moving an external phone nearer+farther and the graph showing up+down) but that might also do.
[Samsung Galaxy Nexus] mike freegan:
I'm so glad that someone who knows stuff is irate about this. It annoys me how people are so spineless that they won't kick up a fuss. Samsung need to be pressured into releasing a fix here pronto, as people's return periods are expiring soon. Or at least have the decency to say something. It seems pointless me returning it if I'm going to buy it back next week if it gets fixed.
[Samsung Galaxy Nexus] her0n:
I'm still exchanging for a sensation xe tomorrow. Nexus had a fit today whilst I was at work. Had enough of the drama!

Also i've had problems with the phone being on charge on usb.. charges to 100% but if you leave it plugged in too long, it will turn itself off. V odd.
[Samsung Galaxy Nexus] coolbho3000:
Yes, a damn software fix is possible (in the kernel, yes, the kernel, even if this problem occurs in the bootloader which doesn't run on Linux kernel), and I'll try tomorrow when I get my GN from Handtec (I told them to ship anyway).

The key is pressed and released very quickly when a 900MHz signal is near the phone, right?

It seems bad at first, but it's really not that bad. Hang on to your phones for now, you have plenty of time to return them…
[Samsung Galaxy Nexus] Equinox102:
Things like this get patched via low-level software all the time and you'd never know about it. I'd bet similar issues were apparent in prototypes and were fixed via software. (Radio firmware, etc)
[Samsung Galaxy Nexus] robaldred:
Very disappointing, the rest of the phone and ICS is excellent, definite worthy upgrade from my N1

Here's my Galaxy Nexus volume issue in action, repeatable by enabling and disabling '2G only networks' option

youtube.com/watch?v=coJi1SRqo8c

We have really poor 3G coverage in the UK, it's often only available in or close to major cities.

I live on the outskirts of Manchester, 3G here is particular poor from all the networks.
[Samsung Galaxy Nexus] Mr.Kakarot:
I told handtec to ship as well, but I hope it's a non issue.. I rarely see 2g/edge... If ever
[Samsung Galaxy Nexus] Erazor786:
Hers my experience in trying to replicate the fault everyone is seeing. Received my phone via an upgrade with Orange via Phones4U.

I've tried with the GN in Airplane mode. Got an old Samsung E900 with an O2 sim as my current phone is the HTC Desire with an Orange sim. I've rang the E900 and tried holding the bottom of the phone near the volume rocker and nothing has happened, tried different postions of the phone and still nothing. From my limited understanding of this, the fact that the GN has my new Orange sim in there which is currently not activated should not make a difference in my ability to replicate this problem should it?
[Samsung Galaxy Nexus] paul_one:
You're right, it should not stop this test working.

Can you please collect your ODIN information here:

http://xdaforums.com/showthread.php?t=1357340

Is it possible for you to put the O2 card into the Nexus and retry on 2G only?
[Samsung Galaxy Nexus] Hosh0:
Question, it seems Clove have sold out, would that mean that their new stock would be from a second batch?
[Samsung Galaxy Nexus] Erazor786:
Posted my ODIN details over on that thread. Their the same as Oscillik's and many others.

Tried to replicate with the O2 sim in the GN and forcing only 2G connections and added my HTC Desire on GSM only to the mix and rang the phone to create some interference and still nothing.
[Samsung Galaxy Nexus] oscillik:
no it doesn't mean anything - someone else tried doing the same test earlier with the exact same phone as you and couldn't get it to work straight away. Then after they had tried a few more times it triggered the fault. It seems that certain phones are not putting out enough 900MHz signal, which means when people are doing these tests they're no getting a bad 2G signal (which is required so that the 2G phone can transmit more 900MHz signal).
[Samsung Galaxy Nexus] Erazor786:
So even though I tried with the O2 sim in the phone and forced 2G only, is not of any real significance?
[Samsung Galaxy Nexus] oscillik:
no because your HTC Desire likely didn't put out enough 900MHz interference for it to happen - there needs to be a strong 900MHz signal happening, and this usually occurs when the 2G phone has poor signal (as the phone then transmits more 2G signal to latch onto the cell tower)

Were you actively in a call while you did the test on the HTC Desire, or did you just wave the Desire by the Galaxy Nexus while it was idle? If so, this would do nothing as the HTC Desire needs to be in an active call to perform this test with any result.
[Samsung Galaxy Nexus] Erazor786:
When I tried with the E900 the phone was being called, when I put the O2 sim into the GN, I used my HTC Desire to call the GN and had the HTC Desire set on GSM only as well, as well as holding the bottom of the phone near the volume rocker.
[Samsung Galaxy Nexus] oscillik:
In my own personal tests I have found that using the second phone to call the Galaxy Nexus yields no results...whether this is because the secondary phone doesn't need to transmit so much 2G signal, or some other reason...I don't know.

Would you be able to come back and update us if you encounter the problem in future?
[Samsung Galaxy Nexus] Erazor786:
Of course mate, I'm going to be having another crack at it tomorrow. Got a Samsung G600 somewhere and also a HTC Touch HD with a Dutty Rom flying around somewhere (ahhh the memories :)).

The more info we get the better we can understand what is happening. It seems that you pretty much know the fault but any extra info wouldn't hurt. Ill report back tomorrow if I get the time.
[Samsung Galaxy Nexus] oscillik:
Exactly, more information cannot hurt. From what I've seen, the best secondary phone to use for testing is an older generation, so for example an older S40 Nokia phone (or even older would be better - the likes of the Nokia 3310!) or an older Ericsson....basically a dumbphone from a few generations ago. These seem to put out a consistently strong 900MHz signal, from what I've gathered.
[Samsung Galaxy Nexus] Erazor786:
I think I may have an old Nokia 6230 somewhere. Ill have a look and see If I can find it and test with that. See if It wields any different results.
[Samsung Galaxy Nexus] oscillik:
that would be awesome, thanks for going to the trouble of performing any tests in the first place :)
[Samsung Galaxy Nexus] Erazor786:
No problem at all mate, glad I can be of any assistance. I'm not the most tech minded individual but I'll do my best to help in anyway I can.
[Samsung Galaxy Nexus] arcynum:
So oscillik, what would be your advise to customers who want this phone, but haven't actually ordered yet?

I'm from Australia with a network still actively operating on the 900mhz band.

I want this phone, but I've no idea whether to lay down the money now (my impatient side) or wait until theres some sort of official remedy (safe side).
[Samsung Galaxy Nexus] oscillik:
truthfully, only you can make that call (pun intended)

if I had known there was a major issue afflicting a large portion of handsets, I personally wouldn't have bought the handset, and would've waited until reports came through of no issues. I bought my phone on the 18th November, the day after they first went on sale. So I wasn't to know, as the first report of the fault only came through on the evening of the 18th.
[Samsung Galaxy Nexus] Duds44:
Oh that's unfortunate man! The evening of your purchase? Sounds like me, "what!? It's available!? MINE!!!"

Hahaha but seriously, that is unfortunate :mad:
[Samsung Galaxy Nexus] Hosh0:
Voda use the 3g 900mhz frequency in rural areas in Australia. Otherwise its the 2100mhz 3g signal. In saying that, Vodafone are so bad over here that I wouldn't be surprised if they ran the 900mhz even in the cities.
[Samsung Galaxy Nexus] oscillik:
I didn't find out about the fault until I experienced it for myself early morning on Saturday 19th, because I was travelling in a car on the motorway to Birmingham to visit family. The motorways here in the UK are notorious for having terrible 3G signal, and if you can even get hold of any mobile phone signal it is usually only 2G. I had the problem the entire trip (nope I wasn't driving, in case anyone asks!). When I arrived in Birmingham, the problem went away. But I checked the forums here and lo-and-behold, there was a post regarding this fault.

Anyway, that's again, how I experienced the fault in the first place.
[Samsung Galaxy Nexus] Dmw017:
You didn't really just say that :/
[Samsung Galaxy Nexus] Duds44:
I laughed! haha :D
[Samsung Galaxy Nexus] mtoti:
Personally I think you'd be mad to order, in fact I have asked Clove to cancel my order because I just didn't want the hassle of getting support from afar (and having to pay to ship back to the UK) when it looks so likely that there will be problems. I know on Virgin/Optus I frequently drop down to 2g, I'd guess on Vodafone you'd be even worse.

If you do buy then get from Handtec as it looks like they will only ship subsequent phones once they are sure that Samsung has sorted the issue.
[Samsung Galaxy Nexus] arcynum:
I'm actually not contracted to Vodafone, got moved over from 3 and can leave whenever. But even so, I think I'll end up waiting for a fix.

I personally think its a hardware fault, but Samsung/Google will attempt to fix it with a software band-aid.
[Samsung Galaxy Nexus] Duds44:
I'm on 3 in AUS in Melbourne and never drop to 2G but I still want to know when I travel into the country that my phone is not going to be going spastic.

Alas, I haven't cancelled my order with Clove; I think I have a blind trust in Google that they won't let this continue (I know it's a Samsung issue, but a little nudge nudge from Google will help).
[Samsung Galaxy Nexus] Brandon3003:
Here's the way I see it.

There hasn't been any major comment from Samsung nor Google. While some might think this means the worst, I believe the opposite. If this were in fact a hardware issue that couldn't be fixed/avoided in a decent way through software, I would have thought one of the two would have said something by now to avoid bad public image. Not to mention Samsung would have halted sale far earlier if this were going to be a recall to prevent further financial loss. Also take into account the fact that prototypes didn't face this problem, and those are typically very close to the final product.

That being said, we have 3 key pieces of information to consider (aside from the above).

1: We heard early on that Samsung was blaming this on Google. While this at the time meant nothing, the next two somewhat go along with it.

2: P3Droid (whom apparently has connections on the inside) claimed on his twitter that it was resolved with a software update, confirming point 1. While this again could be taken with a grain of salt.. Look at point 3.

3: We then heard from a Google software engineer on the android IRC channel that he believed it was resolved in a software update (keep in mind we'd already heard of a possible 4.0.2 so this isn't too far fetched).

That being said, I'm going to place my bet on a software fix/workaround. You have to keep in mind that this is Google's phone, as well as their phone that developers tend to go for. I highly doubt Samsung would be stupid enough to make such a silly mistake (not their first Rodeo) and Google would screw around their developer crowd.

Just my .02, only my opinion.

Oh, and don't ask me to cite posts, I'm not going back and looking all that up, but if you've kept up with everything you'll know what I'm talking about.
[Samsung Galaxy Nexus] Jebus99:
Vodafone in Sydney. Haven't had major reception issues (despite the constant whine of Vodafail). Mine is already on the way here but I clarified with Handtec whether to accept the shipment (if it's faulty). They told me that since these are phones shipped before they halted shipments, that I should have no out of pocket costs involved in returning the device should this buy require a return/exchange. So I'm quite happy with how its turned out so far. Handtec have had some excellent customer service.
[Samsung Galaxy Nexus] Duds44:
That's good customer service; at least you are getting communication from Handtec! Clove haven't communicated anything to myself yet, just that it's been posted.

But we are getting off track here.... Haha :cool:
[Samsung Galaxy Nexus] mnexusaud:
Nexus on Telstra 850

Hi

I've just ordered the Nexus from Handtec Uk and it will arrive within the next week. I'm on Telstra Australia which uses a variety of signals including 900.

When I get the phone I should be able to deselected the 900 frequency and select 850 frequency - from my understanding I won't have the problem correct since I'm not using the 900 frequency? Please correct me if I'm wrong.

I can report back with results once I get it. According to Telstra I will 100% not get this problem if I block out the 900mhz.
[Samsung Galaxy Nexus] Proyoyo:
I thought Telstra is using GSM900 as their 2G network. The UMTS850 is only for their NextG network.
[Samsung Galaxy Nexus] mnexusaud:
Apparently according to Telstra I can use the 850 frequency without every needing to use the 900.

I'm not sure what their 2G frequencies are but I thought that there was more than just GSM900?
[Samsung Galaxy Nexus] Proyoyo:
I think it will use 850 in areas that are covered by the NextG network. In some areas that aren't covered by NextG, it will use the 2G 900 network instead.
[Samsung Galaxy Nexus] mnexusaud:
I had a look around and I found that Telstra is using for their 2G network: GSM850, GSM900, GSM1800. I found a few sources mentioning this but I'm not sure if they are correct.
[Samsung Galaxy Nexus] Proyoyo:
I see. I'm not quite sure about this as well. Oh well, we just need to wait until our phone arrive & try it ourselves.
[Samsung Galaxy Nexus] Robboftw:
Does anyone know what band Netcom/Telenor in Norway use for 2G?
[Samsung Galaxy Nexus] infernalman7:
Errr.. I think we are not exactly on topic here (refering to the previous page or two)

We should be discussing the volume issue itself, not "OMG which telco is using 900MHz or is it using 2G". As it has already been identified that the problem is due to 900MHz 2G radio interference.
[Samsung Galaxy Nexus] Vash63:
Has anyone tried putting other 900MHz interference near it? Like a cordless land-line handset or a baby monitor?
[Samsung Galaxy Nexus] Rusty!:
The Nexus One hard a hardware fault with the screen, it would randomly go mental and register touches in the wrong place, making it impossible to type etc. You had to turn the screen off/on to fix it. This was never fixed, and all phones suffered from it. I'm not sure it was ever officially acknowledged.

You can't pick what frequencies the phone uses, it does it all automatically.
[Samsung Galaxy Nexus] mnexusaud:
Apparently I can block the phone from trying to select a 900mhz frequency according to Telstra and therefore it will default to the 850mhz frequency.
[Samsung Galaxy Nexus] atomic_dude:
You force the phone into 3G mode only on NextG rather then select frecquencies. Telstra 3G coverage is quite good, can't see why you'd ever need 2G. Indeed, for 2G Telstra is using 900 MHz. Seriously, I can't see how you could be affected by the volume bug unless you get a 2G phone in a call on top of it :-) Can't wait to get it. I will run some tests just for info/fun using my Xoom in 2G mode.
[Samsung Galaxy Nexus] mnexusaud:
That must be what was meant by bypassing the 900mhz frequency. I did read Telstra has two or three kinds of 2G networks: 850mhz, 900mhz and 1800mhz - is this correct?

The reason people would want to have 2G enabled would be to conserve battery life since running constantly in 3G/NextG will drain the battery super fast. My brother has a Galaxy S2 and the second he put it in 3G mode the battery was dead in 8 hours from a full charge. In 2G it lasts for days.
[Samsung Galaxy Nexus] andygw:
One thing I need cleared up, which I seem to be getting confused about. So say the phone is not running on 900MHz (as it would be very unlikely to on Telstra) - does this mean the phone will be free from this issue so long as it never runs on 900MHz? The impression I seemed to get was that any nearby devices (some cordless phones, other mobiles, whatever other wireless devices running on 900MHz) would cause the interference too. So say you're running on NextG, but sitting next to someone running 900MHz, wouldn't you get the interference?

Or, is it ONLY when your phone is running on 2G?
[Samsung Galaxy Nexus] viniturb0:
I bough t mine today from PHONE4U innpcworld Llandudno and mine suffers the same problem. I'm returning it tomorrow.
[Samsung Galaxy Nexus] dumb donkey:
I've been out for about 4 hours and been on HSPA with quite heavy usage and not had the bug at all... came home and data switched to GPRS and i've had the fault twice in the last 10 minutes.
[Samsung Galaxy Nexus] Tung_meister:
Since posting this I've experienced the volume issue several times, it's really annoying I do hope it's software based :(
[Samsung Galaxy Nexus] oscillik:
this is looking more and more like a hardware related issue rather than it being software.

The info so far:

1. Occurs when the cellular radio is in 2G mode. It doesn't seem to matter whether the phone has the WiFi radio switched on and connected, only that the cellular radio is in 2G mode. 2G mode includes GPRS and EDGE connections (so that means whenever you see a G or an E in your status bar next to the cellular signal).

2. Seems to be affecting those people who are on a network that uses 900MHz for their 2G coverage. So far, those networks confirmed to use 900MHz are O2, Vodafone, giffgaff, Tesco Mobile.

3. The problem could be exacerbated by being in a low signal area. This would make sense, as when you're in a low signal area, the phone will have to transmit more RF to keep hold of a signal and thusly the interference would increase. low signal is not a requirement for the problem to occur, low signal would just make the problem happen more often.

I am definitely going to be calling Samsung tech support about this tomorrow.
[Samsung Galaxy Nexus] sblantipodi:
please keep us posted.
[Samsung Galaxy Nexus] Tung_meister:
What you're saying does make sense, I only experienced the issue when I had relatively low signal though I have experienced the issue when I had half bars on edge so it' not just isolated to 2g.
[Samsung Galaxy Nexus] oscillik:
you do realise that EDGE is 2G, right?
[Samsung Galaxy Nexus] Duddyroar:
Yep, let us know how you get on.

On a totally unrelated note, I'm actually reviewing the phone for CNET UK. The review will be going live tomorrow and will mention this issue.
[Samsung Galaxy Nexus] oscillik:
that's great news, that it will get a rather widely publicised exposure of the problem. my Google+ post aimed at a few Google employees has gone completely unanswered. I'm hoping that this will get picked up by some of the other major tech sites too, this problem really needs a lot of exposure otherwise the likelihood of having any conclusive answer to this will be zero.
[Samsung Galaxy Nexus] Duddyroar:
If this is a hardware fault, then Google and Samsung will have to do a recall. This is their flagship Android device, and it's a developer device too - you can't have your prime tool for developers displaying this kind of issue.
[Samsung Galaxy Nexus] sblantipodi:
Flagship with volume problems, bad camera quality (photo too often out of focus due to the fast shutter speed), it lacks usb otg, it lacks microsd slot, it has only 16GB, no UMS support, visible screen banding.

what a great flagship, I'm thinking that this phone has only a flagship price.
[Samsung Galaxy Nexus] oscillik:
I am also going to try to go into the O2 shop where I bought the phone, let them know what is going on, and try to see if either they can get in touch with their own Devices and Tech department, or if they will give me a way to get in touch with them.

If I have the time to go into Liverpool again tomorrow, that is.
[Samsung Galaxy Nexus] Tung_meister:
Sorry thought you were just referring to GPRS.
[Samsung Galaxy Nexus] keridel:
remember guys the reason the vote is biased towards people WITH the problem is that they are the people searching xda for solutions.

i have no issues at all. i cant even get it to duplicate. mine was sent direct from Phones4u
[Samsung Galaxy Nexus] Tung_meister:
I'm not so sure, I voted saying I didn't have the problem, I looked at the thread initially as the issue intrigued me. I would change my vote now if possible.
[Samsung Galaxy Nexus] Duddyroar:
You're on Orange, right? They don't use the 900MHz 2G signal, so you won't get the problem.
[Samsung Galaxy Nexus] BiGMERF:
how will this act in the usa?
[Samsung Galaxy Nexus] oscillik:
if you're on a network that uses 900MHz, then you're screwed.
[Samsung Galaxy Nexus] LadFromWales85:
Vodafone and o2 also use 900MHz 3G in some places...