yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Chirality:
I don't know what to think anymore. The close placement of the volume switch ribbon to the radio power amp and antenna makes me suspect hardware problem. But all these scrambling commits to fix some bug in the GPIO interrupt handler code makes me suspect some kind of software problem. Argh, the worst part is we may never know.
[Samsung Galaxy Nexus] oscillik:
All this proves is that Google might actually have been aware of the problem before the phone released, and were trying desperately to patch the problem up with software workarounds. This does not mean that the fault doesn't have it's roots in a physical interference. Which is what this is.

As an aside, if Google actually did know about this before shipping, it means that they knowingly allowed a defective product to ship.
[Samsung Galaxy Nexus] Alexander T.:
Should we ask Colin Cross? :)
[Samsung Galaxy Nexus] mcgon1979:
I don't give a SH## about any of this, except WHERE is the god damned OTA update? They are selling flashed units and I still have issues. I have a returns authorization from Handtec that I got last friday. I said I would wait and see if OTA arrived. Think Im going to return it now. To much of a pain in the hole, and no response from google and samsung? Ok so it started rolling out yesterday was it? Not here it didn't. Dublin. I bought one of the very first batch. Pre-ordered on Oct 22nd. Where is the fix.
[Samsung Galaxy Nexus] oscillik:
I'm sure Mr. Cross wouldn't be able to say anything on the matter at all. I'm still pretty sure that Romain Guy said more than he should've when he spoke to me on IRC last week...
[Samsung Galaxy Nexus] webthingy:
And it is a well-know fact that Google tends to release many faulty products with some never getting proper fixes/updates. I am sure they knew about this issue the whole time.
[Samsung Galaxy Nexus] oscillik:
If you scroll up, you'll see that the assertion by various retailers that Samsung has been flashing handsets is now thrown into dispute.

Oh I agree, it's just that we now have what seems to be some form of proof.
[Samsung Galaxy Nexus] AntonyStark:
Seems these retailers/ phone companies are using the bug to cover up the fact that they didn't have stock or enough of it, or couldn't sell stock, or Samsung delayed selling them stock.

Samsung are being totally Manufacturer and just said it will be fixed, thats all they need to do, its not there fault if who you are actually purchasing the phone from are choosing to make these statements.

Fix exists, hopefully we get it soon.
[Samsung Galaxy Nexus] pienut:
Nope, nothing. All of a sudden I received a phone :-)
[Samsung Galaxy Nexus] bushbrother:
Wow this is all getting a bit messy, so now it seems I too will have to wait for OTA if Clove are now saying the latest batch is indeed NOT patched :(

Seriously though, I am so confused as to why Google/Samsung just don't come out and give an OTA date, even if it was 2 weeks away then people would at least have an answer!
[Samsung Galaxy Nexus] bleets:
common sense and logic dictates they were witholding shipments until they knew if the software fix would work or if it would need a recall, seems like good practise to me.
[Samsung Galaxy Nexus] oscillik:
Google have come out officially with a date

It's just that it seems no-one has actually received the update. I was told by a reliable source that the update was supposed to go live at 5pm last night. 19hours later, and no-one has received the update.

---------- Post added at 12:05 PM ---------- Previous post was at 12:03 PM ----------

Yes this would seem to be the case. Unfortunately, yet again, the retailers have misinterpreted it or just downright lied about the handsets having been flashed.
[Samsung Galaxy Nexus] Chirality:
It's pretty clear that the root cause of the issue is hardware interference. But that doesn't mean it's a hardware issue. The way I look at it, there are two possibilities.

1. There's nothing wrong with Samsung's hardware design. The kind of interference we are seeing is common and expected, and the IO handling code of these SoCs by default deal with this. But Google released a broken Android kernel that didn't handle this correctly. They were trying to fix up the kernel up until release but couldn't make the deadline.

2. The interference we are seeing is not common or expected, Samsung's design was just defective. And now Google is forced to add new functionality to the kernel to work around this defect.

So depending on whether this kind of radio/IO interference is common or not, it can either be a hardware or software issue. It doesn't really matter that the root cause is hardware interference. What matters is who released a broken product: Samsung's hardware design, or Google's kernel?
[Samsung Galaxy Nexus] justabrake:
is it really samsung or is this google
[Samsung Galaxy Nexus] bleets:
According to slashgear

http://www.slashgear.com/galaxy-nexus-volume-bugfix-rolling-out-ota-30198835/
[Samsung Galaxy Nexus] oscillik:
Well, we obviously won't ever get any official admission from either party.

But considering what PaulOBrien has already said about the patch, and what you're saying here after what you've perused in the kernel, it does seem more likely that Google are at fault here.
[Samsung Galaxy Nexus] Matcarroll:
I have just spoken to a guy called sean at o2 technical support and he was very helpful. I explained my 14 days cancellation ends on Friday and wanted clarification what's going on and whether or not I am sending my phone back. He said he had notes on his system saying the ota patch was released last night at 5pm to 1000 phones and would be ongoing to 1000 phones at a time. I am basically going too see if I receive by cob Tuesday and if not, send back my phone, cancel contact and wait for either iPhone 5 or galaxy 3 next year. This was my first upgrade from apple to android and although I love the freedom of android am regretting it from a customer service/feedback point of view.
[Samsung Galaxy Nexus] bobbysixkiller:
so looks like what i said was correct. they are shipping with the fault and will continue to.

shame you poo poo'ed that statement i made yesterday
[Samsung Galaxy Nexus] oscillik:
The information that slashgear have there has been gleaned from Clove, and as such, is about as reliable as a chocolate teapot.

Really? Because none of us have received the OTA update, and we've been hitting check for updates for 20 hours. Anyone who receives a handset from Clove are in exactly the same boat as us - awaiting this mythical update that was supposedly released 20 hours ago.
[Samsung Galaxy Nexus] kristovaher:
Samsung delayed the shipments and made no statements about the issue, even misinformed sellers about flashing the devices, which was apparently untrue. Google respons to users, in fact the bare-minimum statements have only come from Google in this whole situation, the only thing Samsung has told us - customers - is repeat the quote from Google.
[Samsung Galaxy Nexus] bleets:
it might just be a case of the distributor talking crap, who probably arent even samsung themselves...so all clove can do is repeat what they themselves have been told by another 3rd party etc
[Samsung Galaxy Nexus] oscillik:
the only statement you made yesterday that I poo-poo'ed was the suggestion of using Volume Locker. That is in no-way pertinent to this current discussion.

Yeah, I can get behind that. Either way, the retailers have been perpetuating misleading information.
[Samsung Galaxy Nexus] bushbrother:
But at least they have been giving updates :)
[Samsung Galaxy Nexus] oscillik:
Misleading updates are worse than no updates, in my opinion.
[Samsung Galaxy Nexus] bobbysixkiller:
no you said what i was told from o2 was properly a load of tosh, when in fact it seems to be true. all phone for the foreseeable future will ship with the bug and the ota is a user responsibility
[Samsung Galaxy Nexus] oscillik:
this is what I said

At the time, it was hearsay.

Now that we have more information from other sources that corroborate what you were told by O2, it seems the information you were told may be correct.

My statement there was more making light of the fact that you were talking about internet rumours, and then making an internet rumour yourself. I will not apologise for bringing that point up.

I will however apologise for casting doubt on the meat of your statement though, which was that O2 told you the stock wouldn't have the fix.

I am sorry for doubting the veracity of your claim.
[Samsung Galaxy Nexus] marky9074:
I find it odd that Handtec tested their initial stock, then released the new stock with seemingly no testing.. will find out in ~1hr when its delivered....
[Samsung Galaxy Nexus] Rubu:
Wouldn't some carefully placed and calculated ferrite beads and/or caps also possibly get rid of the interference? Seems doable from the iFixit pictures (considering there is room when you put everything back together) Anyone crazy enough to give it a shot? :)
[Samsung Galaxy Nexus] IvanDobskey:
Just recieved my Nexus, finally. Here is the system info:

Android version 4.0.1

Baseband I9250XXKK1

Kernel version 3.0.1 -ge2433f2

Build number ITL41D

Don't think this is an updated phone. Not seen the volume bug yet, but I get 3G in my house. Only a matter of time tomorrow at work I guess.
[Samsung Galaxy Nexus] oscillik:
You're missing a little bit more info there from the Kernel version section, but from what you've posted so far it's obvious that you are running the exact same version of Android and baseband as the rest of us.
[Samsung Galaxy Nexus] IvanDobskey:
Yep, looks like the new stock being fixed was total BS. They better hurry up with the damn fix!
[Samsung Galaxy Nexus] bleets:
im guessing it didnt prompt you to install an update either? :rolleyes:
[Samsung Galaxy Nexus] oscillik:
Supposing that one of us does actually receive the OTA update, can someone post details of how to find the URL after having received the update so that others can download and apply manually?

Is it simply just a case of running DDMS and looking back through the logs after the update has been performed?
[Samsung Galaxy Nexus] s.m.knipe:
DDMS works or CatLog (app) if it has been updated for ICS (I haven't checked it yet).

EDIT: Had "CatLog" down as "LogCat" and posted market link

EDIT: It works fine!
[Samsung Galaxy Nexus] marky9074:
Mine has clearly been opened as there are two seals one on top of each other and the underlying one is broken...
[Samsung Galaxy Nexus] oscillik:
Can you post the following details?
[Samsung Galaxy Nexus] Rubu:
Also, if possible, some details about shipping and such, what store, when did you order, when did it ship/arrive etc. Thanks!
[Samsung Galaxy Nexus] :
Some german users just came back from a chain which has the GN on sale as of today.

Here is there info

baseband i9250xxkk1

kernel 3.0.1-ga052f63

build ITL41F.I9250XWKK8

requesting more info, but kernel is different as it seems
[Samsung Galaxy Nexus] marky9074:
Handtec, 17th November, 29th November/30th November... at the moment fighting to get a connection in the bootloader..
[Samsung Galaxy Nexus] :
4 units in Germany report:

Kernel changed on units on sale.

3.0.1-ga052f63

android-build@apa28#1
[Samsung Galaxy Nexus] marky9074:
Still cannot get adb talking and tried two different Samsung USB drivers :/

Below is what I have so far...
[Samsung Galaxy Nexus] bongadadu:
Thanks. Exactly the same as the 'old' batch
[Samsung Galaxy Nexus] oscillik:
No it isn't. This is from the 'old' batch

edit: i messed up! leaving evidence that i messed up. Sorry bongadadu
[Samsung Galaxy Nexus] Rubu:
And are you able to reproduce the bug?
[Samsung Galaxy Nexus] oscillik:
His handset is susceptible to the issue because he is running the exact same Android version, build number, and kernel version as the rest of us.
[Samsung Galaxy Nexus] bongadadu:
Lol cool, thought my eyes were going funky at work after reading that post
[Samsung Galaxy Nexus] ande_uk:
i got my phone from p4u in original batch and my kernel is:

3.0.1-ga052f63 android-build@apa28 #1

would flashing pauls volume fix boot img have changed my kernel version?
[Samsung Galaxy Nexus] bongadadu:
Looking at the post above stating the new models in germany have the same kernel as you do now, I assume that yea it might have.
[Samsung Galaxy Nexus] bushbrother:
I am guessing yes as it was a kernel update, I take it you applied it?
[Samsung Galaxy Nexus] Rubu:
Earlier, he said:

So I was just checkin'
[Samsung Galaxy Nexus] oscillik:
Yes it would change your kernel version, since Paul has already said that the changes were at the kernel level.
[Samsung Galaxy Nexus] ande_uk:
yes, flashed it earlier..

the fix paul was given fix must be the official fix then...
[Samsung Galaxy Nexus] bongadadu:
He did say his fix was based on what was being internally tested by Google. Have you noticed any performance / battery impacts after you applied the fix ?
[Samsung Galaxy Nexus] oscillik:
Yep, Paul said that the version he put out was based on a version of the official fix that was being put through testing at the time.
[Samsung Galaxy Nexus] :
Details from german kernel

Linux version 3.0.1-ga052f63 (android-build@apa28.mtv.corp.google.com) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Mon Nov 21 16:05:10 PST 2011
[Samsung Galaxy Nexus] ande_uk:
8.30 hrs on battery - 73% left... generall pissing about at work usage, texting mates, websites etc...
[Samsung Galaxy Nexus] bongadadu:
So no then. Thanks
[Samsung Galaxy Nexus] oscillik:
interesting....so the kernel on those handsets was built on Monday 21st November, less than 3 days after the first reports of the problem....
[Samsung Galaxy Nexus] bushbrother:
Wow, battery a little better than my current Desire :) Roll on tomorrow for my shipment of Nexus goodness
[Samsung Galaxy Nexus] :
sorta fits with the infos we had. google was quick to state they fixed it. Monday was when most of us complained about it :)
[Samsung Galaxy Nexus] marky9074:
Completely unrelated.. but anybody having trouble with the USB drivers.. connect as a (PTP) device rather than (MTP) to get adb working under windows...
[Samsung Galaxy Nexus] qwerp_:
no it didn't the fix is at the boot image.

i have a backup copy of my original boot. once i reflash the original boot image to the phone again, the problem comes back.

then i flash the fixed boot image again, the problem goes away.

plus after i have applied the fix,

my kernel is still at

3.0.1-ga052f63
[Samsung Galaxy Nexus] bongadadu:
hmm... that kernel is diff to what everyone else has. maybe paul released another revision of the fix
[Samsung Galaxy Nexus] oscillik:
*shrugs* I'm just saying what Paul has said, which has been confirmed to me by a source that wishes to remain nameless.

Maybe there is more at play here than just kernel changes?
[Samsung Galaxy Nexus] 318vert:
Could be a bug in windows 7. My phone connect with MTP to my laptop but my canon dslr will only connect using its PTP option but once connected work exactly like MTP
[Samsung Galaxy Nexus] cellzealot:
The boot.img contains the kernel and the ramdisk, so by changing the boot.img you are changing the kernel.

Also, FWIW, regarding the timing of the fix, we were told by our source that Google isolated the issue and formulated the fix within one hour of becoming aware of it and actually examining the problem.

Since that info was entirely unsubstantiated and impossible to verify, I chose not to discuss it here, given the highly charged environment surrounding this issue.
[Samsung Galaxy Nexus] marky9074:
I think you misunderstood me... my phone connects fine in MTP mode, but I cannot use adb under MTP mode... the phone seems to have defaulted to MTP, whereas the ADB interface driver only installed once I had changed it to PTP... if your not using adb then its not applicable... ;)
[Samsung Galaxy Nexus] oscillik:
Really? If that is indeed true (and so far I am inclined to believe you considering the information you've already gave us), I have to take back any disparaging comment I've said about Google being work-shy fops on this issue :eek:

Google, I'm sorry!
[Samsung Galaxy Nexus] MatthewPL:
But they should take Samsung and slap their in the face until Samsung doesn't release fixed hadware version... I think that Google try do something about this but Samsung said "we don't care" and go back to promote note and create sgs3.

Maybe a good idea is to create a video how "good" fix is (showing what improve and what still doesn't work and how phone behave in 2G environment)?
[Samsung Galaxy Nexus] oscillik:
Well, I really do not believe for one second that Samsung will make a new hardware revision. It would be too costly, considering that this software fix (by all accounts from people in this thread) will sort the issue out so that it is transparent to the user.

And considering what Chirality found out in the kernel it seems that Google might've been aware of the issue even before the product shipped. Personally, if I had to choose between a product being released on time with bugs, and a product released a couple of weeks later that actually works properly, I would choose the latter. It would seem that someone didn't think the same way...
[Samsung Galaxy Nexus] bleets:
thats one of the stupidest things i've read, with terrible english and grammar.

why would samsung have a dont care attitude? the unit is still branded a samsung, for all intents and purposes it is a samsung phone and would they really risk their reputation with an attitude like that?

one would think not.
[Samsung Galaxy Nexus] cellzealot:
I think there is probably enough blame to go around and plenty of egg for all the faces to be well smeared.

While I really want to resist throwing anymore fuel on the fire here, we were also told that they did NOT test for 900mhz EMI from the legacy 2g network at all...they were completely caught off guard. This seems to me to be patently insane and inexcusable under the circumstances.

Again, I have no independent verification for any of this info, but this source is extremely reliable from our experience.
[Samsung Galaxy Nexus] A.Ik:
My apologies for posting off topic. But Samsung Canada lists the Galaxy Nexus as having expandable memory. I think it's fairly dubious. Why would Canada alone get a Nexus with expandable memory. I'm sure this is a mistake but I certainly hope not. http://www.samsung.com/ca/consumer/...dex.idx?pagetype=prd_detail&tab=specification

Bottom right of the page
[Samsung Galaxy Nexus] oscillik:
I agree completely - The phone launched in a territory that still has a large majority of it's surface area only covered by 2G. In the UK, this is largely served by the 900MHz frequency and is used by the top two leading networks. This should absolutely have been tested.

---------- Post added at 04:28 PM ---------- Previous post was at 04:28 PM ----------

Yes you are severely off topic. Go to the correct thread.
[Samsung Galaxy Nexus] A.Ik:
They've already found it there; thanks for the link though.
[Samsung Galaxy Nexus] MatthewPL:
But how "much" transparent it is? Do it increase CPU usage (and/or decrease battery life) in 2G mode because of software fix? Will it work (except bootloader) as normal, not bugged phone? Or better wait for Nexus 4/something else?

To order or not to order? That is the question!

(I really hate Samsung now...)

I would choose on time without bugs. ;D

Dreams are nice...

EDIT:

Sorry for terrible English and grammar - I am bad in learning "normal" languages.

Maybe Nexus is still branded a Samsung but tell me, what are you thinking about while hearing "Nexus"? Samsung? No! Google? Yes.

For normal people high-end smartphone is SGS3 or iPhone 4S. Even if Galaxy Nexus is better. GN is something similar to Nokia with MeeGo - nobody really care. Only few geeks will remember that phone after few months. Look at webpages - when iPhone has problem with antenna every site wrote about it. Nexus? yeeeaaa, there is some volume problem but not big deal - even if Nexus problem is much bigger than iPhone.

"Funny" thing is that Nexus should be a main Android-phone for developers. They should buy it and creating apps until other companies will release ICS updates or new phones. But how buy and use something that just doesn't work?

One again - sorry for my English and grammar.
[Samsung Galaxy Nexus] oscillik:
Again, more proof that your post in this thread related to the rumour of expandable memory for Canada is completely irrelevant to this thread and should be kept to the right thread. Sorry to be brusque, but you're not the only person to have come in here with stuff that is not pertinent here.

So far, indications show that there is no perceptible effect on the phone, other than patching the problem.
[Samsung Galaxy Nexus] A.Ik:
Yes ma'am. Never said it wasn't ma'am.
[Samsung Galaxy Nexus] ferraristu:
oscillik for Prime Minister - gets my vote
[Samsung Galaxy Nexus] oscillik:
Change we can believe in.
[Samsung Galaxy Nexus] agormog:
edit: oh damn, I always miss if theres a new page and post.
[Samsung Galaxy Nexus] A.Ik:
ma'am   [mam, mahm; unstressed muhm]

noun

1.

madam ( def. 1 ) .

2.

(in Britain) a term used in addressing the queen or a royal princess.

Queen oscillik?
[Samsung Galaxy Nexus] oscillik:
more trolls. how wonderful :rolleyes:
[Samsung Galaxy Nexus] A.Ik:
Stickler for discipline eh?
[Samsung Galaxy Nexus] cellzealot:
While I find it amusing to watch you Brits spatting with one another in such well spoken terms, it's also rather annoying and unnecessary here! ;)
[Samsung Galaxy Nexus] oscillik:
Well said.

Do you have any more insights you might be able to put into the relevant discussion? :)
[Samsung Galaxy Nexus] A.Ik:
Correct! On with waiting here refreshing the page every two minutes waiting for the fix to roll out! Productivity.
[Samsung Galaxy Nexus] FISKER_Q:
Personally i still think that the next production batch they make(if they make any) will have the issue fixed on the hardware.

Just seems kind of a "Why not?" situation, but of course i have no experience on how costly it is to add simple shielding, just saying that if it's something they could simply do, i think they will.
[Samsung Galaxy Nexus] oscillik:
Well, I do disagree because the software patch should sort the problem out. When a company has a choice between spending no money or spending money, if doing either has the exact same outcome, they will chose spending no money.