yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jaketurbo:
Worth reading about bootloaders for anyone not convinced it's software or any drivers are loaded:

http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html

The second step in the boot process gives it away, unless you are too moronic to understand.

"Once the boot media sequence is established the boot ROM will try to load the first stage boot loader to internal RAM. Once the boot loader is in place the boot ROM code will perform a jump and execution continues in the boot loader."

In case people are getting confused, there's a difference between 'boot rom' and a bootloader... Boot rom is rom, with inbuild hardware instructions to allow the booting of software... usually, the bootloader which is loaded into RAM.

I have never said in any post that the issue isn't hardware related just the down right insistance of one person who seems to think just saying "it's in the bootloader" proves that it's 100% a hardware issue is quite astounding.

It probably is, in fact I'm certain it is a hardware issue but using proof that "It's in the bootloader" and stating that "there are no drivers" is down right stupid.

Basic drivers are loaded as part of the bootloader for simple hardware functions. Fact.

PS. It's day time and I'm not pissed now, so I can read what is being posted.
[Samsung Galaxy Nexus] bleets:
Location: Widnes

that's all i need
[Samsung Galaxy Nexus] oscillik:
and you know that I'm actually from here, how? Not to mention that Widnes isn't part of Merseyside.

you are a troll.
[Samsung Galaxy Nexus] M2281088:
Come on now guys, you are both n00bs, now live with it.
[Samsung Galaxy Nexus] Nail_s:
They just told me by email that my GN has been already sent but I can simply reject parcel collection and they will resend when the issue is resolved... So we're waiting now for response from Samsung/Google regarding this issue and potential solution for this issue...
[Samsung Galaxy Nexus] juicytuna:
Come on people, lets leave the secterianism / racism / xenephobia out.
[Samsung Galaxy Nexus] birdster:
Come on lets get some logic into our thinking, I'm no programmer but a software fix must be able to fix this, how you ask, well to change volume we need to do one of two things, press the rocker switch on the side or tap the screen and pull a slider when the volume bar is onscreen, thus all other forms of changing the volume apart from those two things should be ignored unless there is a physical keypress on sceen or via rocker switches, fixed !!!!

Its a dirty patch that doesnt fix the real hardware issuse, but most systems are patched up due to design problems and constraints !!
[Samsung Galaxy Nexus] Evostance:
Happens in bootloader so can't be
[Samsung Galaxy Nexus] marky9074:
Good to know, thanks :)
[Samsung Galaxy Nexus] paul_one:
thanks, i've been after docu like that for a while. Would like more on the actual bootloader used by android though.

but please, pray tell, what drivers are loaded into the bootloader?

normally its some disk and very basic io drivers, to allow it to then boot into the kernel and allow people to press input keys. as we've already said, the input drivers are interrupt functions which capture and interpret those commands.

are you trying to say in out from different parts of the sysystem might be misinterpreted as keyboard events? as that won't be true.

also, iirc, all wireless device require firmware to be loaded from binary blobs, so i doubt there would be much coming from the wifi chips before that.
[Samsung Galaxy Nexus] Rusty!:
And there is the problem. As far as the phone is concerned, the volume buttons are being pressed.
[Samsung Galaxy Nexus] Nebucatnetzer:
The problem is it will keep the CPU awake which sucks your battery. And at least I wouldn't like to live with this.
[Samsung Galaxy Nexus] sblantipodi:
the problem is bigger than what it could seem.

If it was a software error samsung would have answered now,

since they don't answered it means that they are organizing something that requires more time for an answer, a recall?
[Samsung Galaxy Nexus] SuperUserMovado:
If this is a radio issues can't this be fixed by Samsung updating the radio image on the devices. I am not 100% sure but this seems like this can be fixed in software,someone correct me if I am wrong
[Samsung Galaxy Nexus] jaketurbo:
You're pretty much right, it's only the basic drivers for connectivity (USB), drives, additional ram... modem cpu drivers are a possibility as well. I've got a few other links stashed away, when i'm back on my home pc I'll post them.

I don't claim to be an expert on this by any account at all, just have done my own reading over the years and have a very high level view of what goes on.

From the already quoted article:

"C. The second stage of the boot loader is the first major program that will run. This may contain code to set up file systems, additional memory, network support and other things. On a mobile phone it may also be responsible for loading code for the modem CPU and setting up low level memory protections and security options."
[Samsung Galaxy Nexus] Evostance:
Samsung just called asking for my baseband number..

I gave them I9250XXKK1

That is the default baseband I hope..
[Samsung Galaxy Nexus] ref1ux:
Same as mine.
[Samsung Galaxy Nexus] gambiting:
Your logic is flawed. The phone has absolutely NOW WAY of differentiating between a fake press caused by interference and an actual press by the user. Both of them cause burst of electricity in the volume rocker circuitry and there is no way to distinguish between them(without a specialized hardware which is certainly not available in the phone).
[Samsung Galaxy Nexus] jmbillings:
Has anyone on Orange experienced this? I found the list below which may explain why I haven't, if they don't use 900MHz...

Vodafone GSM 900: 890 - 894.6 MHz 935 - 939.6 MHz

BT Cellnet GSM 900: 894.8 - 902 MHz 939.8 - 947 MHz

Vodafone GSM 900: 902 - 910 MHz 947 - 955 MHz

BT Cellnet GSM 900: 910 - 915 MHz 955 - 960 MHz

Vodafone GSM 1800 &

BT Cellnet GSM 1800: 1710 - 1721.5 MHz 1805 - 1816.5 MHz

T Mobile GSM 1800: 1721.5 - 1751.5 MHz 1816.5 - 1846.5 MHz

Orange GSM 1800: 1751.5 - 1781.5 MHz 1846.5 - 1876.5 MHz
[Samsung Galaxy Nexus] oscillik:
thank you jaketurbo and paul_one

jaketurbo, you have proven my statement saying that there is no software involved in the bootloader to be

wrong

, but you seem to be supporting my theory that there are no device drivers loaded that could be used to access the radios within the handset whilst in bootloader mode.

would really appreciate if you have more information on this, as I believe this will be a crucial factor in completely outruling software based issues here.
[Samsung Galaxy Nexus] birdster:
lol well i did say i wasnt a programmer, now im begining to understand the seriousness of this ty anyhow :)
[Samsung Galaxy Nexus] dcsworld:
Mines the same
[Samsung Galaxy Nexus] Tom Servo:
Actually, I wrote a post in this place explaining how the ****ing phone gets from a button press to volume changes, but near the end, I figured it's a waste, seeing how dense some of the people are being here. I'm almost believing you're a bunch of apologists or Samsung astroturfers!

I hope if this issue gets officially acknowledged or fixed, that there's a separate thread. I quit.
[Samsung Galaxy Nexus] oscillik:
I have already mentioned this multiple times in this thread :rolleyes:

---------- Post added at 05:22 PM ---------- Previous post was at 05:22 PM ----------

someone else who is sharing my frustration at the people in this thread that are refusing to accept the evidence so far!
[Samsung Galaxy Nexus] paul_one:
the secondary stage is used when booting os's.. look at grub for a reference (eg, in stage 2 network stuff is loaded and other stuff, in order to then boot the os.. which can include raid, usb, ethernet, etc).

afaik wifi binary blobs are loaded when the kernel is loaded and the module is activated... that would be waaaay after.
[Samsung Galaxy Nexus] Nebucatnetzer:
Sorry guys I have to. It was already two pages back and I really would like to know this.
[Samsung Galaxy Nexus] gambiting:
Not possible unless somebody writes a custom software that can run in the bootloader mode(just like recovery mode programs on Nexus One). So yes, it is possible,but we don't have right tools to do it yet. And tbh I think it's pretty clear what you will find - the phone will just report lots of button presses at once,and that's it.
[Samsung Galaxy Nexus] paul_one:
I think this and other software stuff needs to go in a seperate thread.. I think you're after how to get to the bootloader?
[Samsung Galaxy Nexus] M2281088:
I wouldn't say that they are refusing to accept the evidence; I think some are missing the knowledge we have had by READING THE THREAD FROM THE BEGINNING. As such they are making the same assumptions that we made in the first few pages.

Please don’t skip the early stuff it does support our belief that the issue is hardware related, terrible induction caused by a 900MHz signal.
[Samsung Galaxy Nexus] ptscon:
Guilty of this :(
[Samsung Galaxy Nexus] SuperUserMovado:
is someone going to write an app to only allow the volume to be adjusted on screen.

Seems quick and dirty,its not a real solution but it would fix the problem.

hey ice cream sandwich is all about being button free and there are no volume buttons on the kind fire either :)
[Samsung Galaxy Nexus] Christuxy:
Although the bug is hardware related, there might be a good software fix.

Atleast, that is what someone wrote here ->gathering [DOT] tweakers [DOT]net/forum/list_message/37182119#37182119. (Dutch)

Translation:

I just spoke with our hardware dev and he says that it is possible to fix this with a software update.

Chips have a great ammount of I/O ports, of which some have the ability to interrupt.

However, it still is firmware that decides wheter or not a port can interrupt or not.

So it is not unthinkable that the volume rocker is now configured as interrupt, but that a software update changes that to polling. This fixes the problem without a big cut on battery life.
[Samsung Galaxy Nexus] gambiting:
As in Android you can intercept pretty much any kind of activity, I am sure it is possible. The bad thing is, that it would still create an event to handle, so the processor would have to wake up, and if there are so many fake presses within a second as we can see in the DDMS logs, it could even lead to the phone being unresponsive, even if nothing was really happening on the screen.

I mean yeah, sure, that would be a dirty "fix" to allow people to use their phones in 2G only zones, but it's a horrible fix and should not be considered.
[Samsung Galaxy Nexus] Nebucatnetzer:
Nope I wanted some more information about what's really happening in the device. I don't say it's not hardware related or it can be fixed with a simple software patch.

I just would like to know what's going on. I hate it when I have a "self solving" issues. You can't learn anything from them.
[Samsung Galaxy Nexus] oscillik:
please refrain from using the word 'fix' as it is disingenuous. 'patch' is more appropriate here.
[Samsung Galaxy Nexus] juicytuna:
Hence he put it in inverted commas. No need to be so touchy.
[Samsung Galaxy Nexus] oscillik:
well there kind of is, since there are many people who will see this word and automatically believe that it is actually a fix, when it is not a fix, it is a patch. and a dirty one at that.
[Samsung Galaxy Nexus] Christuxy:
It depends on that you call the problem, the SAV ghost or the RF interference. If you call the volume the problem, as most people will do because they do not care about the root cause, it is a fix.

Why are we even discussing these irrelevant things?
[Samsung Galaxy Nexus] onyxogen:
What a shame, Samsung.

Launching a defect device is bad.

Not making a statement about this is worse.

The media is gonna destroy this otherwise very capable device - and Samsung does nothing against it. They lose christmas sales. If they told us that sales are stopped and everyone should wait for the fixed version of the phone, most people could understand that. But saying just nothing is simply unprofessional. This will put Samsung back for years, even if they don't know that. Publicity is everything.
[Samsung Galaxy Nexus] juicytuna:
Lets just be patient. They are surely in the labs right now replicating the problem and working on a solution, whether that be a 'dirty patch' or a full product recall. I'm sure they will issue a statement once all the facts have been established.
[Samsung Galaxy Nexus] Dmw017:
How about you calm yourself down. He can call it an effing flying cow, nobody on this forum gives a damn. Anyone who has read through even a handful of pages of this thread is smart enough to know what he meant by "fix".

Spend less effort on trolling and more on contributing in a different way. Thanks bro.

Any reply to this convo is just more time spent corruppting the thread.
[Samsung Galaxy Nexus] oscillik:
according to this they're doing bugger all.

granted, this is just one mans word...but it's certainly not outside the realm of possibility.

---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------

thanks for the self-righteousness. I've contributed more to this thread than you have, and I am not trolling.

if you had actually read this thread in it's entirety you would see that there are actually lots of people that are not smart enough to know what he meant.
[Samsung Galaxy Nexus] gnufabio:
You are right man, I'm sure that Samsung is now looking for the best solution. They can't release a so-bugged Nexus device ;)
[Samsung Galaxy Nexus] onyxogen:
Maybe they thought that with virtual buttons shielding is unnecessary :-O

Oops we forgot the volume rocker...
[Samsung Galaxy Nexus] Dmw017:
The device wasn't even meant to come out yet. It was rushed to "compete" with the iPhone.

Much as I hate to say it, Verizon did right by setting the release of the Nexus for December, which was supposed to be the intended date.

People are having problems with the volume, usb transfers, and a whole mess of other stuff. I just sent word to Handtec to ship out my Nexus in hopes that the bug is only restricted to the UK or that my device will be one of the normal ones. If not, I'll just pay to send it back when the time comes. Shouldn't be too much of a pain if you buy some replacement phone on your carrier and return it when your Nexus is back in your possession lol.
[Samsung Galaxy Nexus] gnufabio:
If they did not release it, lot of people would have bought an iPhone 4S. But yes, they did this nexus too fastly. It seems that they should have tested it more and better than they did.

Here in Italy the Galaxy Nexus should be out December 2nd, I really hope we will get a fixed revision of it, even if here the 900mhz frequency is still not used.
[Samsung Galaxy Nexus] juicytuna:
Erm don't bite my head off but...

What if there was a way of disabling the volume rocker in hardware, i.e the cpu ignores all interrupts coming from the volume rocker?

It could be enabled in the bootloader stage as the buttons are essential for controlling input there, but could be disabled just before the kernel is loaded. Have only software volume control like in the kindle fire. Maybe Android could be updated to have volume controls in the notification bar?

Obviously this solution is not acceptible even if it is possible but I'm throwing it out there anyway.
[Samsung Galaxy Nexus] Bilhouse:
Have you not noticed how many people are getting annoyed by you? Because it seems to be a large number and from what I can see their not all wrong.

Please calm down and stop acting in such a bossy and rude manner. Be a bit more humble and your input will be appreciated far more.
[Samsung Galaxy Nexus] go2mo2:
Back on the subject....

It seems strange to me that some users have said they cannot replicate the fault, even using the proven methods stated in this thread. As it appears to be a shielding issue, surely this must be a manufacturing error? And if so i would expect every single gn to have the same problem
[Samsung Galaxy Nexus] oscillik:
if it is possible to completely disable it at the hardware level, then yes that would fix it. But I'm unsure that you can actually do that. Even if you could, we would be left with volume keys on the phone which are useless. But that would stop the problem from happening, albeit with the side effect of not being able to control volume without using the screen. not a good solution really :(

funnily, the same people that are getting annoyed by my brusque manner are generally the same people that haven't read the thread from the beginning...

---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------

There have been several people who had originally claimed that they couldn't replicate the fault, but have since come forward to inform us that they have subsequently been able to replicate it. Various reasons for this include:

1. Not trying the right SIM card in the Galaxy Nexus / secondary phone to test

2. The secondary phone not outputting a strong enough 900MHz frequency at the time of testing.

There does seem to be an emphasis on the problem occurring when a strong 900MHz frequency is emitted. I have found that older dumbphones (such as older S40 Nokias, original Ericsson handsets, etc) tend to put out a very strong signal. These seem to be the best for testing in this way.
[Samsung Galaxy Nexus] Bilhouse:
Two wrongs don't make a right. Their inability to read the OP shouldn't act as an excuse for you to be so harsh and arrogant. Humility is the key to gaining respect.

Anyway everyone is here for the same reason, to see this issue resolved ASAP so we can continue enjoying the phone.

Lets all focus on the common goal.
[Samsung Galaxy Nexus] Evostance:
Could this simply be an earthing issue?
[Samsung Galaxy Nexus] juicytuna:
Yes, I am unable to replicate the problem with my GS2 in GSM mode but an S40 Nokia dumphone manages to trigger it. At this point I'm inclined to believe that all handsets are affected.
[Samsung Galaxy Nexus] oscillik:
hmmm who knows? Would a mobile phone even need to be earthed? I admit, I am showing my lack of knowledge here and openly admit that I have no clue regarding this point. I thought only electrical appliances that plugged directly into a mains supply needed to be earthed?

thanks for further corroboration there. It does seem like this is a common trigger factor - a particularly strong 900MHz signal. The kind that you would encounter with the handset's built in cellular radio if you happened to be in a low signal area that only had 2G coverage.
[Samsung Galaxy Nexus] gnufabio:
Is there any problem when using the GalaxyNexus itself in 2G mode? For now I've seen people complaining for the fact that GN goes crazy when you put another phone next to it.
[Samsung Galaxy Nexus] go2mo2:
Thats not a bad shout........ no easy way to prove it though
[Samsung Galaxy Nexus] SuperUserMovado:
The kernel is out there I believe. All we need is for a dev to develop the "kindle" patch that "fires" your phones hardware volume keys.

Really making piss out of lemons :eek:
[Samsung Galaxy Nexus] oscillik:
you really need to read the original post

yes we are experiencing the problem with the internal cellular radio when it is in 2G
[Samsung Galaxy Nexus] Evostance:
I was going to try and fix a wire to that screw near the rocker to the battery lol
[Samsung Galaxy Nexus] juicytuna:
Not on mine, but it could depend on the strength of the signal. 2G reception is very good where I am.
[Samsung Galaxy Nexus] go2mo2:
Hahaha, still got your warranty info??

In the words of Dr Pepper.... whats the worst that could happen? :D
[Samsung Galaxy Nexus] neovisage.HD2:
as second day nearly gone touch wood i dont have issue with vol butt only what really suprising me the batery not enough even fir one day!even if i kill unused app.I hope my unit will not suffering from any issue.I just sold my iphone 4 to get hands on nexus and this is third time when i trying to go with android.love the ice cream sandwich and i think its way better than ios 5.Samsung show really you are much smarter than apple!
[Samsung Galaxy Nexus] romerjon:
Handtec Blog reports that there are both phones with and without this issue in their stock:

"Update D: The stock we have is the same as other retailers (same distribution) Not all stock is effected as our initial testing confirmed. Our findings are consistent with http://xdaforums.com/showthread.php?t=1353590&page=75 ."
[Samsung Galaxy Nexus] CJSnet:
After 85 pages my workaround above remains the lesser of 2 evils and the best current option for anyone in a decent coverage area wishing to keep their device for the time being.

I can confirm this has 100% stopped the issue happening, and I haven't been without reception or data once, nor is there noticeable battery drain. I get faster data than ever! :-)

For anyone in a city this will feel like a "fix" and is highly recommended.

There's really nothing else to discuss until a better fix is announced. This thread is going round in circles.
[Samsung Galaxy Nexus] oscillik:
you need to update your post to make people aware that if they find themselves in an area that would normally be serviced by 2G cellular towers because of lack of 3G in the area, they will get

no signal whatsoever

and they will be back in the situation of having a useless phone
[Samsung Galaxy Nexus] go2mo2:
Wait for it...... wait for it.......

Edit: Damn, seconds too late lol
[Samsung Galaxy Nexus] bleets:
I'd just like to point out

http://code.google.com/p/android/issues/detail?id=22021#c128

now i'll just wait for some stupid comment from the scouse guy who doesnt want to wait and see what it actually is/if any info comes from that.
[Samsung Galaxy Nexus] SuperUserMovado:
thats a big caveat in there

"for anyone in a decent coverage area"

it really depends on where you are and which carrier you are riding with
[Samsung Galaxy Nexus] oscillik:
we already know what it is. and i'm not scouse. so you're wrong on both counts.
[Samsung Galaxy Nexus] DoddyUK:
Well, looks like we'll know for certain within the next 48 hours if it's a software problem (unlikely) or not:

Can't post links due to my post count, but go to the Android Issues board on Google Code, look up Issue 20021, post number #128.
[Samsung Galaxy Nexus] bleets:
widnes == scouse etc.

anyways you don't ACTUALLY know what it is...

you have a theory

a possibly/probably incorrect theory

i mean...you can't >know< what it is because neither samsung nor google have actually said what a possible fix could be!

stop spouting theory as fact.

be patient and wait for actual facts to roll in.
[Samsung Galaxy Nexus] oscillik:
i'm not from Widnes. And even if I were, Widnes isn't in Merseyside.
[Samsung Galaxy Nexus] bleets:
since you've ignored the other comments does that mean you're going to get off your high horse, show a little matury and patience and wait to hear what google/samsung will/may say?
[Samsung Galaxy Nexus] stiffn:
At this point in time I don't care if they fix the issues and give the phone away for free, I've lost all confidence in the brand, the complete lack of support and total disrespect for customers to not even put out a "We are looking into the issue" notice. If a company can't be pro-active in helping their customers on a huge launch like this I really don't want to be on the end of any problems down the line when it's no longer a 'Big Release'.
[Samsung Galaxy Nexus] Dmw017:
Wow, yeah, I see your contributing a lot lately. Cool.

edit: Found the answer. Nvm
[Samsung Galaxy Nexus] Evostance:
Dont think this is confirmed. 900mhz is the lowest in the UK (i think)