Earlier today, we reported that some British owners of Galaxy Nexuses were voicing concerns about the volume spontaneously going to zero; at the time, we'd hoped that it was a software issue, but a new video has us worried that there might be something deeper involved. A YouTuber has uploaded a brief video of a Galaxy Nexus in bootloader mode that appears to be cycling through the menu itself when another phone is brought near — in bootloader mode, the menu is actuated by way of the volume rocker, so there's your connection. The phone next to the Galaxy is allegedly connected to a 900MHz 2G network, which appears to be the band where the phones are having the problem. It's way too early to speculate whether Google and Samsung will be able to patch this up with an over-the-air firmware update alone, but the fact that this can be reproduced simply by holding another phone nearby — all the way up in the lightweight bootloader mode, no less — is cause for alarm.
Users have discovered that they can temporarily stop the issue by locking the phone into 3G mode, but depending on where you live and where you travel, that may not be an option. The silver lining for North Americans is that there's no evidence yet to suggest that this bug (assuming it's a real bug) will affect either the CDMA / LTE variant or the GSM variant when operating on US and Canadian bands; we certainly haven't seen anything like this on our review unit, but we'll be keeping an eye on it as it develops.
Thanks, oscillik!


Comments
Today it’s a volume bug, tomorrow it’s Judgement Day by tiny green robots. It’s obvious they’re planning something.
Posted on Nov 21, 2011 | 6:22 PM EST reply Recommend (6) Flag actions
Gen.Droid : Begin Phase 1 of Order 66, disable ringers of all phones, so that when we begin our assault, these puny humans won;t be able to warn each other of their impending destruction!
Little Green Minion Droid: It shall be done, my master!
Gen. Droid: Also, tell the web browser to stop showing off, 1800 on the sun spider? really? Is he trying to give away the fact that we’re smarter than ever? tell him to dumb it down a bit.
Posted on Nov 21, 2011 | 7:08 PM EST reply Recommend (11) Flag actions
Roger Roger!
Posted on Nov 21, 2011 | 11:56 PM EST reply Recommend Flag actions
The real question is, who still uses 2g?
Posted on Nov 22, 2011 | 12:19 AM EST reply Recommend Flag actions
err.. doesn’t everyone slip down to 2G when they move out of 3G range?
Posted on Nov 22, 2011 | 1:37 AM EST reply Recommend (7) Flag actions
A lot of people in the UK.
Posted on Nov 22, 2011 | 4:02 AM EST reply Recommend (2) Flag actions
Seems almost like a RF shielding problem
Posted on Nov 21, 2011 | 6:23 PM EST via mobile reply Recommend (10) Flag actions
That’s exactly what it probably is.
Posted on Nov 21, 2011 | 6:29 PM EST reply Recommend (16) Flag actions
Great phrasing, +1
Posted on Nov 21, 2011 | 7:37 PM EST reply Recommend (10) Flag actions
pretty sure It’s NFC related.
Posted on Nov 22, 2011 | 6:13 AM EST reply Recommend Flag actions
Except the Nexus One doesn’t have NFC.
Posted on Nov 23, 2011 | 12:53 PM EST reply Recommend Flag actions
Should’ve coated everything in Monster material…
Posted on Nov 21, 2011 | 6:32 PM EST reply Recommend (3) Flag actions
A DIYer needs to post a guide for people to get into the device and fix it themselves. For me in the US, I’m going t be to lazy to bother fixing it (since it likely won’t be a problem in the US because we don’t use the 900Mhz spectrum) but would still like to have it fixed without having to live without my phone for a few days.
Posted on Nov 21, 2011 | 6:48 PM EST reply Recommend Flag actions
Looks like an area Samsung needs to focus on:
“If you’re using sensitive in-ear headphones, radio GSM / EDGE noise is as audible, indicating a probable hardware design flaw of the codec or the board. The culprit is poor EMI shielding.”
-From Anandtech’s review of the Galaxy S2.
Posted on Nov 21, 2011 | 8:25 PM EST reply Recommend (6) Flag actions
Sounds like the big news here is that The Verge has a review unit of the LTE version. Or did we already know this?
Posted on Nov 21, 2011 | 6:27 PM EST reply Recommend Flag actions
No, we don’t. Or if we do, no one told me! Now you have me all paranoid…
Posted on Nov 21, 2011 | 6:31 PM EST reply Recommend (9) Flag actions
This issue is only a problem when using the 900Mhz frequency, so the problem will likely never occur in the US since the US doesn’t use that frequency for cellular and on top of that, the Verizon version does not have that frequency on board.
Posted on Nov 21, 2011 | 6:57 PM EST reply Recommend Flag actions
Good thing Americans never go on holiday abroad.
Posted on Nov 21, 2011 | 7:04 PM EST reply Recommend (4) Flag actions
Oh I know, but I am simply stating that this is unlikely to be an issue for those who buy in the states (particularly the Verizon version). And they will likely be able to live with it until a recall can be issued.
Regardless, Samsung needs to fix all the phones because it is a “World Phone”.
But the main point is that it’s not very likely that the Verizon phone will ever have an issue. And for those importing, it will mostly be an non-issue for most.
Posted on Nov 21, 2011 | 7:14 PM EST reply Recommend (2) Flag actions
One example of 900Mhz interference doesn’t, in any way, conclude that it’s the only issue…
Posted on Nov 21, 2011 | 7:49 PM EST reply Recommend (1) Flag actions
We use 900Mhz for some cordless phones.
Posted on Nov 22, 2011 | 10:58 AM EST reply Recommend (1) Flag actions
It’s most likely that I misread the line that mentions the review unit. It sounded like you were saying that the LTE version doesn’t seem to have this problem because The Verge hadn’t had any issues with it’s review unit.
Posted on Nov 21, 2011 | 8:49 PM EST reply Recommend Flag actions
Seems that the GN is suffering from the opposite of what the iphone 4 suffered before…How ironic…
Posted on Nov 21, 2011 | 6:29 PM EST reply Recommend Flag actions
Rockergate!
Posted on Nov 21, 2011 | 8:50 PM EST reply Recommend (2) Flag actions
It’s a feature not a bug.
Posted on Nov 21, 2011 | 6:29 PM EST reply Recommend (1) Flag actions
Probably they are holding it wrong…
Posted on Nov 21, 2011 | 6:36 PM EST reply Recommend (7) Flag actions
they’re holding the phone wrong..
Posted on Nov 21, 2011 | 7:17 PM EST reply Recommend Flag actions
I meant to say they’re holding the OTHER phone wrong.
Posted on Nov 21, 2011 | 10:37 PM EST reply Recommend (1) Flag actions
cheap cam, cheap GPU, mediocre testing, unclear release dates, no 32GB in europe.
Yet I still want this phone. I’m weird.
Posted on Nov 21, 2011 | 6:29 PM EST reply Recommend (7) Flag actions
How is this a cheap camera ?
http://hemorrdroids.net/samsung-galaxy-nexus-vs-samsung-galaxy-sii-s2-camera-test/
Posted on Nov 21, 2011 | 6:38 PM EST reply Recommend (4) Flag actions
I’m just saying they saved some money by putting in this cam instead of the S2 cam.
Posted on Nov 21, 2011 | 6:42 PM EST reply Recommend Flag actions
While I already ordered the phone am starting to build grudge against Google.
Posted on Nov 21, 2011 | 8:00 PM EST reply Recommend (2) Flag actions
That was an awesome comparison. I’d personally take zero shutter lag over a couple of extra megapixels any day.
Posted on Nov 21, 2011 | 10:20 PM EST reply Recommend Flag actions
lol, you think it’s actually zero shutter lag.
Posted on Nov 21, 2011 | 10:53 PM EST reply Recommend (1) Flag actions
There will never be true zero lag, everybody knows that. But if it’s 0.2 seconds or ‘blink of an eye’ speed its close enough to zero for most of us to care about!
In the video below you can see that the Nexus is twice as fast as the iPhone 4s(witch isn’t slow itself):
http://www.youtube.com/watch?v=n0fN55W9erM
Posted on Nov 22, 2011 | 8:23 AM EST reply Recommend Flag actions
One of these two actually takes beautiful shots, and you don’t have to worry about standing absolutely still…
Posted on Nov 23, 2011 | 9:44 AM EST via mobile reply Recommend Flag actions
The actual camera isn’t faster, per se, Apple just added an animation to the process, which accounts for the speed difference. It seems to be another thing that Android makers, and users, seem to completely miss; that the experience, and the way in which things interact (e.g. animations) do affect the perception of performance and usability. There is no real immediate indication on the Android phone that the camera has taken the photo. The animation on the iPhone does slow it down, but for many people, knowing the photo was taken is worth the .5 second delay. Another great example of how Google designs for engineers and for code, and nearly everyone else at least displays an elementary understanding of usability and the larger benefits of good interface design.
Posted on Nov 25, 2011 | 4:11 PM EST reply Recommend Flag actions
I’m in the same boat! Ice cream sandwich is a mesmerizing OS…even the crappy hardware can’t turn me away from it
Posted on Nov 21, 2011 | 6:52 PM EST reply Recommend Flag actions
I don’t see how people still see hardware as an issue (especially with ICS) Phones are blazing fast as it is and very few things require a faster phone than what they are offering. I am much more concerned with hardware features (like NFC) and battery life.
Posted on Nov 21, 2011 | 6:54 PM EST reply Recommend Flag actions
by mediocre testing you obviously don’t mean the sunspider or javascript web benchmarks.
Posted on Nov 21, 2011 | 7:28 PM EST reply Recommend Flag actions
Just like with Chrome, I don’t care if my page loads .01 seconds faster. It’s become quite a pointless benchmark. eeking out milliseconds to claim superiority, when the bottlenecks everywhere else make those milliseconds useless under varying use cases, especially with mobile devices.
Posted on Nov 21, 2011 | 7:50 PM EST reply Recommend (3) Flag actions
that could be true of almost all benchmarks, why have a powervxr543 gpu when there arent going to be any games that test its strength? or whats the point of 60fps, when even 30 or 40 fps is all anyone ever cares about? and the apps that are present are handled more than capably by even an adreno 220?
If software is the bottle neck, then as reviews of the device have already stated, the performance is a 10, the software is a 10.
either you care about benchmarks, or you dont.
Posted on Nov 21, 2011 | 8:56 PM EST reply Recommend Flag actions
Games can be made to take advantage of those specs. Apps/games can be made to take advantage of fps and cpu improvements. Nothing is going to make me care about .01 second faster page loading.
Posted on Nov 22, 2011 | 1:54 PM EST reply Recommend Flag actions
Camera isn’t THAT bad, if you saw the shots it took (pretty good for a 5mpx cam IMO). GPU is really the only thing i could gripe about, i can still handle 16GB of storage, especially if I have access to cloud storage.
BTW, the GN is scheduled to be released Dec 8th in the U.S. after that, you can pretty much buy the phone online from anywhere around the world.
Posted on Nov 21, 2011 | 7:46 PM EST reply Recommend Flag actions
http://hemorrdroids.net/samsung-galaxy-nexus-vs-samsung-galaxy-sii-s2-camera-test/
Posted on Nov 21, 2011 | 8:01 PM EST reply Recommend Flag actions
Well… this sucks =/
Posted on Nov 21, 2011 | 6:30 PM EST reply Recommend Flag actions
LOL, watch them use this video as a way to claim the bug only happens with custom ROMs.
Posted on Nov 21, 2011 | 6:41 PM EST reply Recommend Flag actions
What are the odds that this will affect a Verizon version as well?
Posted on Nov 21, 2011 | 6:44 PM EST reply Recommend (1) Flag actions
If it’s a shielding issue, probably pretty high.
Posted on Nov 21, 2011 | 6:45 PM EST reply Recommend (2) Flag actions
Very low. It appears to only be a problem when using 900Mhz spectrum which isn’t used in the US. Plus the Verizon version doesn’t even have a chip that has 900Mhz enabled.
Posted on Nov 21, 2011 | 6:51 PM EST reply Recommend (5) Flag actions
At this point, it’s hard to say if it’s just a 900Mhz issue, if it’s a real, non-over-hyped, issue at all. Just because the phone here is a 900Mhz one doesn’t mean that’s the only area of weakness. Just have to wait and see though.
Posted on Nov 21, 2011 | 7:46 PM EST reply Recommend (1) Flag actions
Really fun that they’re using a Nexus One to poke at the Galaxy Nexus. It’s like sweet revenge for not being upgradeable to ICS (officially).
Posted on Nov 21, 2011 | 6:47 PM EST reply Recommend (7) Flag actions
Nokia’s built quality is the best in the mobile industry.
Posted on Nov 21, 2011 | 6:54 PM EST reply Recommend (1) Flag actions
Cool story bro.
Posted on Nov 21, 2011 | 6:56 PM EST reply Recommend Flag actions
You’re right, but what has that to do with anything?
Posted on Nov 21, 2011 | 7:00 PM EST reply Recommend (1) Flag actions
You are unintentionally correct in your use of the word ‘built’, which is the past tense.
Posted on Nov 21, 2011 | 7:08 PM EST reply Recommend Flag actions
In the “built of plastic” mobile market maybe.
Posted on Nov 21, 2011 | 7:47 PM EST reply Recommend Flag actions
Duh, just don’t hold the other phone like that.
Posted on Nov 21, 2011 | 6:58 PM EST reply Recommend Flag actions
Gen.Droid : Begin Phase 1 of Order 66, disable ringers of all phones, so that when we begin our assault, these puny humans won;t be able to warn each other of their impending destruction!
Little Green Minion Droid: It shall be done, my master!
Gen. Droid: Also, tell the web browser to stop showing off, 1800 on the sun spider? really? Is he trying to give away the fact that we’re smarter than ever? tell him to dumb it down a bit.
Posted on Nov 21, 2011 | 7:06 PM EST reply Recommend Flag actions
oops, double post. This was supposed to be a reply.
Posted on Nov 21, 2011 | 7:10 PM EST reply Recommend Flag actions
Epic fail British Telecommunications Commission or whatever it’s called there. Here, take and borrow our Part 15 from the FCC. Radio devices must not interfere with other radio devices, and radio devices must accept interference from other radio devices.
" Operation of an intentional, unintentional, or incidental
radiator is subject to the conditions that no harmful interference is
caused and that interference must be accepted that may be caused by the
operation of an authorized radio station, by another intentional or
unintentional radiator, by industrial, scientific and medical (ISM)
equipment, or by an incidental radiator."
Posted on Nov 21, 2011 | 7:28 PM EST reply Recommend (2) Flag actions
translate please. I dont speak british lol
Posted on Nov 21, 2011 | 7:29 PM EST reply Recommend Flag actions
He’s quoting from an American agency you moron. Plus it’s called English.
Posted on Nov 22, 2011 | 7:07 PM EST reply Recommend Flag actions
FCC Part 15.
(1) may not cause harmful interference
(2) must accept any interference received including interference that may cause undesired operation.
Guess it is doing 50/50.
Posted on Nov 21, 2011 | 7:34 PM EST reply Recommend (1) Flag actions
but the problem isnt with the nexus “causing harmful interference”, it’s with it “receiving bad interference”?
isn’t it?
Posted on Nov 21, 2011 | 7:37 PM EST reply Recommend Flag actions
It looks like it from the brief video that a 900mhz device near it causes a problem on the Galaxy Nexus. But it should be designed to withstand such interference.
From what I can see on the video, that’s severe interference!
Posted on Nov 21, 2011 | 7:44 PM EST reply Recommend (1) Flag actions
correct me if i’m wrong, but does “must accept any interference” mean it ’shouldn’t be shielded against‘, or that it ’should withstand ’ said interference?
Posted on Nov 21, 2011 | 9:06 PM EST reply Recommend Flag actions
Means it should withstand it and function normally.
Posted on Nov 21, 2011 | 11:56 PM EST reply Recommend (1) Flag actions
In the US, consumer devices that emit radio waves fall under Part 15 of the FCC regulations. That means that they cannot emit radio waves that harm other, licensed devices, and they must accept interference from other licensed radio devices. I’m unclear on where cell phones fall under the FCC, but these are also Part 15 devices as well ( I think) due to their wifi radios.
It’s basically the same the world over- if you want to operate a radio, you need to have a license. If you don’t have a license you’re restricted to using radio devices that accept interference from other, licensed devices.
All that to say- whoever puts their imprimatur on the Galaxy Nexus should have tested whether it is sensitive to 900 mhz emissions prior to release
Posted on Nov 21, 2011 | 7:38 PM EST reply Recommend Flag actions
That might be the letter of the FCC law, but they are not enforcing that particularly well. Try holding a cell phone next to an alarm clock radio or land line telephone or car radio. Maybe it’s just the signal wreaking havoc with the speaker coil, but that would seem to be “interference” to me.
Posted on Nov 21, 2011 | 8:53 PM EST reply Recommend Flag actions
SHUT UP AND DON’T TAKE MY MONEY, YET !!
Posted on Nov 21, 2011 | 8:11 PM EST reply Recommend (2) Flag actions
Do not care. Still want.
Posted on Nov 21, 2011 | 8:43 PM EST reply Recommend Flag actions
Doesn’t matter, had Nex(us)
Posted on Nov 21, 2011 | 9:03 PM EST reply Recommend Flag actions
On one hand, this bug sucks big time.
On the other hand…look at the new Bootloader! It’s pretty nifty.
Posted on Nov 21, 2011 | 9:05 PM EST reply Recommend (1) Flag actions
It’s the sound robots make when they make bang bang.
Posted on Nov 21, 2011 | 10:57 PM EST reply Recommend Flag actions
I read gang bang.
Posted on Nov 22, 2011 | 1:53 AM EST reply Recommend Flag actions
Next google will issue a statement saying that we are not supposed to hold the phones next to each other.
Oh wait. That’s apple. Google will just fix the problem rather than blame use. Ahh i’m getting confused.
Posted on Nov 22, 2011 | 12:15 AM EST reply Recommend Flag actions
Wrong tech blog, mate. Troll at Engadget.
Posted on Nov 22, 2011 | 1:55 AM EST reply Recommend (2) Flag actions
it seems this issue has also not been noticed in Josh’s review. I’m still looking on the Verge’s front page if they have an article on iOS’s recent wifi issue.
Posted on Nov 22, 2011 | 7:11 AM EST reply Recommend Flag actions
I’m boggled by that “issue” as I don’t know anyone who has been affected by it (off the top of my head I regularly speak with 20+ friends and family members who are on iOS 5.0)
Posted on Nov 22, 2011 | 6:24 PM EST reply Recommend (1) Flag actions
also, I haven’t seen this issue discussed on the macrumors forums. Is it just affecting iPads?
Posted on Nov 22, 2011 | 6:26 PM EST reply Recommend Flag actions
Didn’t anyone notice Homer singing spider pig in the background?
Posted on Nov 22, 2011 | 9:48 AM EST reply Recommend Flag actions
(doing my best steve jobs impression) “don’t hold another phone that close to it that way>”
Posted on Nov 22, 2011 | 2:17 PM EST reply Recommend Flag actions
So I have one of these on order, and I’m still looking forward to getting it despite this issue. My question is this though: If it turns out to be a serious problem (as it looks to be), and is a hardware problem, will they have to recall them all? Or will I be stuck with it?
Posted on Nov 22, 2011 | 7:10 PM EST reply Recommend Flag actions
Comments For This Post Are Closed