yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] birdster:
Yep right next door to the slider, other phone is a htc desire set to 2g only couldnt make it flip out here !!
[Samsung Galaxy Nexus] ref1ux:
Is the Desire on O2/Vodafone?
[Samsung Galaxy Nexus] rabhw:
To me, Handtec's public admittance of a problem is quite serious. As an authorized retailer they either have to decide whether to continue selling a broken handset, or deal with Samsung about getting the issue fixed.

Handtec will be motivated to push Samsung to get it sorted out ASAP, as it will be affecting their sales in a crucial time of the year.
[Samsung Galaxy Nexus] oscillik:
please could you carry out the test in this thread and post your details?

would be most helpful.

edit: also, what network was your 2G phone running on? this is important
[Samsung Galaxy Nexus] paul_one:
holy flying cows... didn't expect handtec to drop that bombshell.

birdster, can you try posting your odin data over in the odin thread?
[Samsung Galaxy Nexus] gogol:
No appleflap, NO!

For the thousand times already, this is HARDWARE issue!!!

This CANNOT BE FIXED via SOFTWARE!!!! FGSK!! :P :P

/s

/jk
[Samsung Galaxy Nexus] oscillik:
you can troll all you like, gogol.
[Samsung Galaxy Nexus] DoddyUK:
Just phoned O2. Needless to say I managed to get a lot more out of them than I did with Samsung.

- While the company hasn't made any public announcement about the fault, their staff are aware of it. It's currently on their internal common issues board.

- A mass recall is the likelier option given the nature of the problem, citing a Nokia recall from a few years back as an example.

- If that does happen, O2 will likely give you a temporary phone until Samsung fixes the issue.

Now, this is one CSR's analysis of the situation as opposed to an official announcement by O2, but this is the biggest amount of information I've been able to get from anyone all day. It's encouraging that O2 are acknowledging that they've had lots of complaints about this issue.
[Samsung Galaxy Nexus] oscillik:
yeah, great solution there! only makes it impossible to change the volume while you're in a call, and on top of that it eats up CPU cycles and battery power.

NICE SOLUTION.

edit: just in case people can't tell. i'm being sarcastic.
[Samsung Galaxy Nexus] birdster:
Done seems to not differ from the rest of the results in that thread :)
[Samsung Galaxy Nexus] oscillik:
this is certainly some development in actual news about this. Thanks very much for the update here.
[Samsung Galaxy Nexus] paul_one:
actually it is a silly idea. how will it know the difference between a hundred invalid volume commands and in the middle of that a valid user input to change it?

I'm sure someone can produce a rom just for you which ignores all volume in out though and so you can't easily change volume and get a hand set with lower performance and battery issues.

btw, has anyone noticed they are pointing at the blog in their twitter - but no update on the blog yet?

blog now updated!!
[Samsung Galaxy Nexus] oscillik:
I hope you don't take this as offensive, but considering the overwhelming evidence that supports the theory that the entire current batch of handsets in the UK are suffering from this problem, would you please be willing to record a video showing that your handset isn't suffering from this problem?

In this video, could you also prove that the secondary handset is operating on 2G Vodafone?

I don't mean to come across as disbelieving, but we need cold hard facts here, and considering that the evidence thus far is conclusive with an issue with the entire batch, it seems incredible that you are not experiencing the problem.
[Samsung Galaxy Nexus] gogol:
Eh? I was helping you to tell people about your propaganda (this is hardware issue and it cannot be fixed with software), and now you are calling me troll?

*sigh*
[Samsung Galaxy Nexus] oscillik:
it's not propaganda, it is scientifically proven* fact.

*scientifically proven in the context that the issue has been narrowed down to a highly reproducible reliability, corroborated by many other people.
[Samsung Galaxy Nexus] go2mo2:
I tip my hat to handtec, this should hopefully get things moving at samsung to sort this problem sooner rather than later!
[Samsung Galaxy Nexus] paul_one:
this is a MASSIVE plus for handtec IMO.

I am now almost certainly buying through them, as they have done all the right actions here.

will defo keep an eye on their twitter/blog.
[Samsung Galaxy Nexus] MrMarques01:
LOL

You have just proven that you know nothing about scientific evidence.

Where's the evidence for your statement? Until you're not able to deliver it, your statement remains a long-shot guess.
[Samsung Galaxy Nexus] Tom Servo:
I wonder if I get a phone before Christmas. :(
[Samsung Galaxy Nexus] oscillik:
read the thread.

all of it

. you obviously haven't yet.
[Samsung Galaxy Nexus] regorsnas:
Hi I'm from Spain. When I read this post of xatakandroid I thought that the problem was solved.

I read all the pages of this thread. But I still don't understand why 4.0.2 doesn't solve the problem in the European devices, but does for Verizon.

The update isn't globaly the same for all the Galaxy Nexus ?

If you use a Verizon Galaxy Nexus with the 4.0.2 and next to him a mobile with 2g the problem doesn't appear. I understand that this is what 4.0.2 solves. Then if I update a European Galaxy Nexus 4.0.2 it has to work, don't ?

I don't want to sound rude. Is that I don't understand.
[Samsung Galaxy Nexus] ref1ux:
The Verizon Nexus uses different frequencies and has different hardware to the GSM Nexus.
[Samsung Galaxy Nexus] Tom Servo:
The Verizon version uses CDMA and LTE. A specific GSM band causes the issue.
[Samsung Galaxy Nexus] bleets:
all the thread shows is

a) you know how to replicate the fault

b) you have an idea of the specifics of the stimulus to replicate it.

what you don't know is

a) the root cause (i.e. where the failure actually is)

b) 100% if it's hardware or software since you dont have in depth knowledge of either the platform (hardware or software)

all you do is state your theory as fact and it's tiresome.

let experts actually deal with this and tell people what the issue is rather than guessing.
[Samsung Galaxy Nexus] her0n:
4.0.2 will only fix the Nexus LTE version which is for 4G networks in the USA.

We don't have the LTE model here in Europe.
[Samsung Galaxy Nexus] DoddyUK:
The Verizon Nexus hasn't launched yet. On top of that, the Verizon Nexus won't be affected anyway since Verizon uses CDMA, not GSM. 4.0.2 will likely be skipped for the GSM Nexus.
[Samsung Galaxy Nexus] oscillik:
We

do

know the root cause - electromagnetic interference received by the phone from it's own internal cellular radio and from external RF sources that is causing hardware interrupts at the CPU level in relation to the volume rocker.
[Samsung Galaxy Nexus] bleets:
in repair terminology the root cause normally refers to where the failure actually is, what component or software part has gone wrong.

and stop getting EM and RF mixed up, it's irritating.

Also, go have a google of teardowns of various phones and tell me how many you see if RF shielding around the various buttons around the edge of a phone.
[Samsung Galaxy Nexus] oscillik:
tell me, how software can see signals that it has no access to hardware that can interpret said signals?

considering that you have made absolutely zero contribution to this forum, I suppose you must be a troll!
[Samsung Galaxy Nexus] qwerp_:
i wouldn't be too sure about it.

all we know is, the 2G signal will affect a G Nexus, what is it actually affecting, we are not sure.

they do have a different modem, no doubt, but if the interference is cause to some other hardware (eg CPU/GPU) that is similar accross a LTE and a HSPA+ model, i would say the problem will still exists.

it will not hurt the americans as they do not have 900 GSM radio frequency in the states to get interfered with.
[Samsung Galaxy Nexus] Tom Servo:
Holy ****! How is radio interference making a GPIO chip go ****ing crazy not a hardware issue?!
[Samsung Galaxy Nexus] oscillik:
qwerp_ has a point - the hardware fault, considering all the evidence thus far, is related to the volume rocker switches, the Verizon version is likely using the same hardware and the same inadequate RF shielding and would thus be susceptible to the same interference.

However, since this is a hardware issue and not a software one, it is not fixable by a software update. it may be patchable, which is different, and doesn't fix the issue - only masks it.

in any case, this supposed 4.0.2 update is for a completely different version of the handset.
[Samsung Galaxy Nexus] paul_one:
shielding will only be required if that particular hardware cannot deal with external radio transmissions properly (ie this case).
[Samsung Galaxy Nexus] bleets:
i usually spend my time reading to get information of various things and dont really like to comment.

What i'm trying to point out to you, which you dont seem to want to listen it is pretty much all smartphones don't have shielding around components like the volume rocker (i dont think many devices have EMI or RF shielding on all components anyway!)

what you think is the cause may not be completely and if you can't show exactly how a bootloader runs and what exactly it's running rather than just hypothesising you yourself are a troll and you may very well be preaching false information based on erroneous theories
[Samsung Galaxy Nexus] gambiting:
Guys, I bring fresh news. I just came back from a Phones4U store, the guy there was really friendly and really knew what he was talking about(what a pleasant surprise), and he said that they received a new batch of Galaxy Nexuses in the store today, and they have one of them open. So I asked him if we could try it with my O2 card to see if the issue still exists. He said sure, so we booted it up, and I checked - both the baseband and build numbers are the same as in my Nexus from last week. The issue is still there, when connected to a 2G network volume goes crazy. And then the guy said that he can actually call the Samsung support line, but a one dedicated to the stores, so they might know more. And here is where the bull**** begins - the guy from Samsung said that from their early investigation it seems like an android issue,and they are not responsible for that, so they have forwarded this issue to Google and they are awaiting a reply. I took over from there, and after making sure that the guy knows what a bootloader is, I told him that this issue exists even when in the bootloader mode and can be caused by another phone interfering with the nexus' hardware. He said that he can't confirm that so all he can say for now it that it's probably google's fault,but if it turns otherwise they will take an appropriate action.

So no definite statements right now, Samsung has officially the worst technical team in the world, we have to wait and see what happens.
[Samsung Galaxy Nexus] juicytuna:
I reported yesterday that I tested and couldn't reproduce the issue on my handset. Well, I tried again with a nokia dumphone in 2g mode and the SAV bug did rear its ugly head this time.

I'm thinking now that maybe all handsets form the initial batch are affected?
[Samsung Galaxy Nexus] basketor:
It's not because there is a little icon showing a plane, and that you can't functionnally call and send sms, that on a hardware level the radio device is really off.

There might be a bug in the firmware that prevent a right change of state or put radio device in a wrong state from the first moment the device is initialised.

the radio device might be accidentaly on in bootloader mode or plane mode because of a bug

That's a bad bug, but that really is a possibility that just can't be ruled out, and wich for me unless proven wrong, just prevent to be 100% sure it's a hardware bug.
[Samsung Galaxy Nexus] Luxferro:
How about this for a theory?

Perhaps the phone has a noise cancellation mic, and that is picking up radio interference, and lowering and raising the volume. If that is the case, then it could easily be fixed in the phones firmware.

Anyone can speculate what the problem is, but until you know the root cause it's just speculation. Perhaps it is hardware, but it can also be something that is controlled by the hardware's firmware. Like maybe an input for autoadjusting volume is turned on when it shouldn't be, or needs squelch levels adjusted, ect. who knows :p
[Samsung Galaxy Nexus] ref1ux:
Thanks for the update, interesting to know :)
[Samsung Galaxy Nexus] oscillik:
it happens in bootloader mode.
[Samsung Galaxy Nexus] qwerp_:
people.. more and more people is getting confused and thinks that this has to do with what ever airplane more or even turning 3g off.

the fact is (at least base on my test and i believe in), its another hardware within the G Nexus that is actually affected. it seems like it will only triggers when you are in 2G mode (not on other 3G networks like 3, or t-mobile), is because at some time/point, the radiation on the phone itself (from the 2G modem) is stronger that it interfere with the problem(not shielded properlly) hardware where it goes crazy. hence it do not happen all the time, only some times.

and we can be sure because when we introduce a external "strong" 2G signal to it, it will react to it at 100% reproducibility.

so for once, please just forget about putting it in 3g mode, or airplane mode or what ever, as this will not help, as external RF will be able to still interfere it.
[Samsung Galaxy Nexus] Tung_meister:
Surely that can't truthfully be Samsungs current stance on the matter, anyone with two brain cells can clearly see that it's entirely a hardware error, all you need to do is prod the nexus with a 2G phone operating on a 900Mhz carrier and the buttons will go crazy. If this really is the case then i'm VERY unimpressed with Samsung as this will drag out the entire problem if they are not properly dealing with the issue.
[Samsung Galaxy Nexus] basketor:
so what, it's the same issue

It's not because there is no light adjustement in bootloader mode, that the light sensing device might not be accidentaly enabled.

the bus/cpu might be fed with datas and there might be no piece of software to trigger a light adjustement on screen

if bugs always maked sens that would be easy, but unfortunely it's not
[Samsung Galaxy Nexus] oscillik:
you can believe what you want to believe.

I am going to stick with the evidence that we have gathered here thus far. Which points to a hardware issue related to the volume rocker switches and is affected by 900MHz GSM band signal.
[Samsung Galaxy Nexus] basketor:
you might as well bet on a horse, or flip a coin, there would not be much more scientifical value

what i believe is that there is still room for a software bug wich I just explained you
[Samsung Galaxy Nexus] kristovaher:
It is interesting to point out that at the moment there is apparently NOT A SINGLE DEVICE WITHOUT THE PROBLEM. The devices that do not have the issue are simply not using 2G. Samsung must start mass recall immediately, this is a disaster device launch unlike any I've seen before since Google TV.
[Samsung Galaxy Nexus] bleets:
this is the problem with scousers, they only believe what they want to believe!
[Samsung Galaxy Nexus] oscillik:
you can provide proof that I'm a scouser?
[Samsung Galaxy Nexus] seakins:
My volume always goes haywire when talking to someone on the phone. Haven't had one good call yet!

Its actually just muted itself while I type this! Called and getting a replacement today. Hope I have better luck!
[Samsung Galaxy Nexus] Tung_meister:
I've not experienced this issue yet and I was messing with the phone for practically the entire day yesterday. For everyone else I hope it's just a software bug though :(
[Samsung Galaxy Nexus] Shodney:
I don't think anyone is in the position to be able to give you an opinion with any certainty, I'm afraid :(

------

Mods - On another note, comments seem to be spread over two threads now. Is it not possible to merge, so that everyone is on the same page? (pun intended :D)
[Samsung Galaxy Nexus] kristovaher:
Good job on those additional posts on Samsung UK Facebook wall. At least most of them still seem to be posted there and haven't been removed by Samsung, but they still haven't replied to single post about the issue, while they do reply to useless, often Samsung-praising, posts.
[Samsung Galaxy Nexus] oscillik:
Telephone number for Samsung Mobile Product/Customer Support

- 0845 67267864

I suggest people start calling this number on Monday.

Also, If you can message people pertinent to Android development via the social networks, this may help spread awareness of the problem.

and if you are having this problem, please star this issue on the Android bug tracker page
[Samsung Galaxy Nexus] Evostance:
Guys,

If you have the issue and on Facebook, just like my wall post:

https://www.facebook.com/SamsungUK

Hopefully it will make Samsung more aware rather than lots of posts
[Samsung Galaxy Nexus] kristovaher:
It is becoming obvious that this happens to some users when phone is on 2G connection. Is there someone who does not have this issue when on 2G data? This could potentially be the case with -all- phones and others have simply not noticed it due to not using mobile data and not being on 2G.

It sounds pretty bad though if phone is unusable on 2G, especially if it is hardware flaw and a broken batch.

It may also be something related to phone being locked, are there any unlocked phones that have this issue?
[Samsung Galaxy Nexus] Chrono_Tata:
My phone is unlocked and it does have the problem. Doesn't seem to make sense if only locked phones have this problem since we all have the same hardware and firmware.

But yeah I have to agree many people who report that they don't have this issue probably live in a good reception area and don't get dropped to 2G a lot. It would be good if people who haven't got the problem to try to reproduce the steps and see if their phones really suffer from it.
[Samsung Galaxy Nexus] kristovaher:
Are you on O2?
[Samsung Galaxy Nexus] tingyue:
Phones4u market street Manchester bought it yesterday got a replacement today see how i get on with this one.
[Samsung Galaxy Nexus] tingyue:
I bought the phone yesterday and was playing with it most of the day at home. The reception is really poor in my house, most of the time I'm on 1 bar. Sometimes 3g but most of the time 2g. I am on wifi too but reception from the router is poor too this causes switching from wifi to mobile internet often. i noticed the bug many times yesterday until i went over to my girlfriends house. i get full bars of reception and good wifi too, didn't have a single problem. I exchanged the phone today and left it with my girlfriend she'll be using it for a few days see if she has any problems. I'll give you an update in a few days time. It does seem like it has something to do with 2G at the moment though.

Jimmy
[Samsung Galaxy Nexus] kristovaher:
The O2 SIM seems to be reported very often with people replacing with Orange SIM seemingly not having a problem. Is there anyone with Orange SIM that has the issue?
[Samsung Galaxy Nexus] LadFromWales85:
Could it be that it happens more on o2 and Vodafone due to their 2g being 900MHz and Orange and TMobile being 1800MHz. And even then, it makes more sense that it happen during low signal due to increased power. Does sound like interference causing the input device to go haywire, but its not happened on a phone before, and Samsung have made many many GSM phones.

Not having the phone yet its hard for me to judge. As all of the keys are one 'input',it makes sense that the power button stops working while the under run is occurring.
[Samsung Galaxy Nexus] Duddyroar:
I'm on Tesco Mobile, which uses O2's masts...so that could be correct.
[Samsung Galaxy Nexus] ferraristu:
Just read on the XDA links this is happening when signal drop to 2G - this makes sense. Had my phone since Friday - live in Liverpool, no signal issues. Have been in North Wales all afternoon out in the country - bad signal.

My phone has been faultless until today in Wales - then the volume started going crazy, adjusting down all the time - could watch it doing it all by itself. Got itself into a loop at one point - had to reboot

Back home in Liverpool for the past couple hours - no problems at all since I got home

Any advice welcome - should I request a new handset ? or wait for a bug fix ? If its a software issue I don't mind waiting, if its hardware I guess I need a new handset.

Cheers

Stu

Bought from o2 online
[Samsung Galaxy Nexus] kingronnie:
I don't want to tempt fate, but I've not experienced the problem. I have held back from voting until now so that the phone had some different types of usage.

I got my phone yesterday from the 3 shop in Chippenham, Wiltshire, and have now used it on three different wi-fi networks, 2G, 3G, HSDPA and with patchy reception. Apart from a few hours sleep I've been playing with it pretty much constantly for the past 32 hours. :rolleyes:

Whilst I'm glad I've not had the problem, I can't help but think it's a matter of time... :eek:
[Samsung Galaxy Nexus] bigsav:
I didn't have this fault at all until tonight.

Turned the mobile network off for about 2 hours. Volume prob happened for a while just after I turned mobile network back on. Seems to have stopped again now though.

I'm coming from HTC Desire and although it's far from perfect but I love it!

Looking forward to hearing some kind of statement from Samsung/Google about this during the week? Surely they can't ignore it for too long, esp with the US release?
[Samsung Galaxy Nexus] kristovaher:
What SIM card do you have? (What service)
[Samsung Galaxy Nexus] kingronnie:
I think it's called SIM600 (can't remember the name tbh, but it's a 12 month SIM only contract for £15 per month if that makes sense!)
[Samsung Galaxy Nexus] ptscon:
Why are you guys so sure this is a hardware issue. It's still software that controls everything, be it low level one.

There is no mechanical aspect to volume control, pressing the volume rocker triggers a software action. It's no a volume knob that's connected to a resistor.

They will push out a software update to fix this.
[Samsung Galaxy Nexus] paul_one:
.. by my guesstimation, samsung won't acknowledge the fault until Thursday or Friday. recall next week and investigation, along with going back to production... Product wont be properly available until next year, late Jan or Feb. especially with the holidays.

very very poor launch.

by then the hardware is several months old, and severely behind others.
[Samsung Galaxy Nexus] Nebucatnetzer:
I guess nowbody of us is able to read out what's happening when the phone is in bootloader mode, right?

Just for further data collection.
[Samsung Galaxy Nexus] sblantipodi:
is there any official statement from google/samsung on this problem?

many days passed since the first launch we need an answer.
[Samsung Galaxy Nexus] marky9074:
Good to know that handtec are not shipping any more units... but it does sound like they've already shipped some, so there might be a few unlucky people receiving them :(
[Samsung Galaxy Nexus] oscillik:
you obviously haven't been reading the thread. there is no software involved with reading data sent by hardware interrupts to the CPU