yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Thyrus:
Righty then, really willing to help you guys.

Thats actually normal. This is how it is supposed to behave, no battle anticipated. Same behaviour on my 3 phones.

Again, my questions:

- Which volume is affected? Media volume, ringtone volume or all volume (master). When this happened, what did the display say which volume is being adjusted?

- Up and down, or down only (ie decrease only? or up down as it wants)

- If you have seen it adjust volume and it says "Media Volume", did it also happen during a call (which would then say call volume or similar). It is really important as both volumes are actually independant from each other. Meaning if more than one type of volume is affected, it may point more towards hardware than software. I can hardly believe that ICS or any app for this matter would trigger this behaviour in different threads/apps.

- Can you reproduce it? If so, please help us with logs to see whether HW or SW (see below)

- Can you interrupt this behaviour by either holding VOL up or VOL down? If you can interrupt it, does it keep doing it or would your interference stop the SAVing for a while?

- State of phone. Was the phone in use or did that happen with display off (if you come back after a while and the Volume is lower?

- If it did, go to the settings and volume - are all volume bars now lower or only one?

So, as far as I heard, it even happened with vanilla handset without apps right?

can you guys execute DDMS (comes with the Android SDK) and check the logs?

i.e. when it happens, you will be able to see the debugger code lines. The code as to WHEN and when it happens would be very important to see whats causing this behavior. Little pic attached for those that want to try

Once you reproduced the issue, copy the relevant lines (you can verbose the log) here?!
[Samsung Galaxy Nexus] seakins:
The volume ghost happened this morning again when my alarm went off. I was already awake and I heard my alarm go off with just one beep and then silent. When I picked it up I saw the volume was down again and then had a battle with it pressing volume up but the phone was insistent on going down. So it must be all volumes getting turned down and not just ringer volume cause even if phone is on silent, the alarm should still go off as normal. At least it did on my N1.

Moral of the story, don't trust the alarm to wake you up cause it may just turn itself down leaving you sleeping in.

I am hoping its sw related cause I love this phone and don't want to return it!
[Samsung Galaxy Nexus] Thyrus:
@seakins please have a look at my questions. Also check when it does that are all volume settings down or just the one (alarm in that case)
[Samsung Galaxy Nexus] Duddyroar:
I'm having the same problem. It usually happens when i unlock the phone, but has happened at other points, too.

I really hope this isn't hardware-related.

---------- Post added at 08:25 AM ---------- Previous post was at 08:23 AM ----------

In my case, it's just notifications and ringer. Media and alarm volume are unaffected.
[Samsung Galaxy Nexus] kristovaher:
They did not say it is not hardware related! You are putting words in their mouth. It is hardware related. What they are saying is that they will release a software fix that will likely mask the problem from the worst thing it does, cause volume drops.
[Samsung Galaxy Nexus] noobdeagle:
exactly however it begs the question maybe interferance filtering is done in software on other devices to just they forgot to add it to this one :P, lol crazy thought trying to be optimistic lol
[Samsung Galaxy Nexus] FishTaco:
If people don't like the fix they are free to return their phones and get their money back. What a bunch of whiners. No wonder the world is falling apart.
[Samsung Galaxy Nexus] el3ctrik:
Or maybe they're just going to change the code where volume controls are implemented so that it requires a sustained input with little fluctation (ie a button is pressed, rather than interference being picked up) before ICS registers it as valid user input?
[Samsung Galaxy Nexus] oscillik:
This started happening to me this morning, after having the phone approximately 24 hours.

Volume is schizophrenic, randomly adjusting down. Does it for both the Notification volume and the Media volume.

Really annoyed about this. Was about to call O2 and get them to reserve me a replacement handset, but it seems like there's quite a few of us having this problem.

I'm going to call the store I bought it from anyway, and just inform them of the issue. And to let them know that I may be coming in to get replacement handset.
[Samsung Galaxy Nexus] si450:
Hi, got my Nexus yesterday and straight out of the box I have the volume down issue. Only happens to me when using the internet on mobile data, not wifi, also have to be lightly touching volume up rocker. Can pretty reliably recreate the issue. I'm probably taking it back to the O2 shop Monday.
[Samsung Galaxy Nexus] STi489:
Interesting issue for sure...Maybe it just does not like noise...lol

I'm sure it's a software issue and will be fixed soon.
[Samsung Galaxy Nexus] :
Strange. From what I have read so far it appears to change the volume of the current mode one is on. Ie in a call it would adjust call volume. Alarm goes off it changes alarm volume. If no specific mode is selected it changes the ringtone volume. If a notification comes in it adjusts that. Could be sw.

Then again normally android lets the volume rkr change the current mode. Means that any behavior of the rocker will change current mode. The volume modes are triggered by different threads and that in itself would mean it may be more hw related.

I would need more info really.
[Samsung Galaxy Nexus] seakins:
Its just done it again and its only the ringtone and notifications volume. Alarm and media are not affected. But it affected the alarm volume.
[Samsung Galaxy Nexus] Duddyroar:
I'll hook my phone up to the SDK tonight and see if i can spot anything.

Btw, i've noticed that if i keep my finger away from the volume rocker, it doesn't seem to happen...worried that this is hardware related.
[Samsung Galaxy Nexus] Gho57:
it's Steve Jobs from heaven :p
[Samsung Galaxy Nexus] Shodney:
When it happens to me, only the main (notification) volume is affected.

During navigation yesterday for example, the mute icon was displayed in the notification bar but the navigation voice was still coming through.

When I get to my computer, I'll try answer the questions you posted.

Thanks :)
[Samsung Galaxy Nexus] Duddyroar:
Just made something of a breakthrough...

I can replicate the fault by switching the wifi on and off using the power control widget, and lightly touching the volume rocker. Even the slightest brush of my finger causes the volume to drop out, and the volume rocker becomes entirely unresponaive for a couple of seconds.

This looks like a fault which is triggered by a connection status change, like wifi or netwwork changing.
[Samsung Galaxy Nexus] Fred23:
Maybe they're saving the working ones for those who pre-order the unlocked phones weeks ago, and sent the factory seconds to Phones4U and the networks. :p
[Samsung Galaxy Nexus] kristovaher:
The 'slightest touch' makes it totally sound like it is hardware issue. Slight touch of volume button should not do anything in the phone (it is not capacitive, is it? As in, it doesn't react to 'touch', only press right?).

This means that if a phone reacts to physical actions that it should not react to, then it is a hardware issue, which is quite bad. Sounds like a bad batch, if not all phones are affected, perhaps a poll would be a good idea.
[Samsung Galaxy Nexus] evolad:
Not happy...i have the same issue... now i have to wait 5 days for a replacement!! ordered online .
[Samsung Galaxy Nexus] Shodney:
That seems to reproduce it for me, although I have to physically press the volume rocker for it to start happening (in other words - it takes more than a slight brush for me)
[Samsung Galaxy Nexus] kristovaher:
Everybody who has a phone, please vote here if you have or do not have the volume problem. This will give us an idea about how many handsets are affected and if it is a batch issue: POLL
[Samsung Galaxy Nexus] :
All I need is the logs if you can now reproduce it to check whether more likely software PR hardware
[Samsung Galaxy Nexus] spences10:
I have the issue I think it's a grip related thing as it was happening when I was looking at it the other day whilst listening to some music on the way home from work

I was trying to recreate the exact grip but couldn't work out exactly how to hold it
[Samsung Galaxy Nexus] Shodney:
I've got DDMS open now trying to recreate it, but it seems to be playing hard to get :rolleyes:
[Samsung Galaxy Nexus] :
here is what we need to look for

it will give you an indication at least. if you see, without touching it, a hardware intend that then triggers some behaviour from android, well then we may be closer

Obviously it will look different for you guys with a GN than my HTC device. Asking some other people to chip in that have the device as this makes root causing it easier. I will get mine on Monday.
[Samsung Galaxy Nexus] dumb donkey:
Ok I've had a go at getting a log for you. I have no clue what i am doing though so don't now if it is of any use.

I have included screen shots of as soon as i could when it happened but as i say i dont know what to look for at all and there is alot going on in that box to try and get the exact part. lol.

http://dl.dropbox.com/u/24851860/screen 1.jpg

http://dl.dropbox.com/u/24851860/screen 2.jpg

http://dl.dropbox.com/u/24851860/screen 3.jpg

*Edit got another one that you can see something that mentions volume control

http://dl.dropbox.com/u/24851860/screen 4.jpg
[Samsung Galaxy Nexus] :
can you dump the log somewhere? hard to see from screenshots- I gotta run for a couple of hours befure my honey gets supermad :)

but there are plenty of people here on XDA that can help I am sure. Will take a look later tonite
[Samsung Galaxy Nexus] dumb donkey:
i'm on my way out too, i'll try and get one later. Just had it happen to me on voice volume during a call, really annoying as i couldnt hear what they were saying at all and it wouldnt let me turn the volume up!
[Samsung Galaxy Nexus] :
sounds more and more like a "stuck vol down key" - or something similar making the hw think you are holding it down....
[Samsung Galaxy Nexus] Duddyroar:
I took some video, be warned that a lot of it is me trying to trigger the fault, so it's not that exciting!

[YOUTUBE]NU5QR_wWrGE[/YOUTUBE]
[Samsung Galaxy Nexus] kristovaher:
No no, that won't work. I traced it based on your username on YouTube though, here's your video:

http://www.youtube.com/watch?v=NU5QR_wWrGE

The exact moment it happens:

http://www.youtube.com/watch?v=NU5QR_wWrGE&t=01m32s
[Samsung Galaxy Nexus] Shodney:
I can't get it to reproduce at all now, which is frustrating.

Perhaps it was a hardware issue, which has been fixed by mashing the volume keys trying to reproduce it! :confused:
[Samsung Galaxy Nexus] jaketurbo:
It's wifi related.

If you turn wifi off and keep it off... try to get the issue to happen - I can't.

Reconnect wifi, the issue starts happening again.

I don't believe its the volume button.
[Samsung Galaxy Nexus] garok89:
what i meant was that....when the bug happens, it often doesnt let you turn the volume up at all, even if you hold volume up button whereas the normal behaviour would override the volume down and start volume up.

so it is either software based and keeps sending the volume down signal too quick for volume up to make a difference, or the hardware fault is happening multiple times very quickly

it probably wasnt too clear what i meant since i fell asleep about 2 minutes later :P
[Samsung Galaxy Nexus] Shodney:
I've been doing that - it used to reproduce the problem, but now it won't.

I'll keep trying.
[Samsung Galaxy Nexus] Duddyroar:
I'm sure i've had it happen with wifi disabled.

I also noticed that when the volume rocker goes haywire, the power/lock key also becomes unresponsive.

---------- Post added at 01:32 PM ---------- Previous post was at 12:55 PM ----------

I've turned wifi off now, will report back if the bug happens again.

Anyone know if this has been reported to Google as an official fault yet?
[Samsung Galaxy Nexus] BiGMERF:
wow this is really bad news.. i hear apps like tweetcaster and facebook also do not work.. very bad news on a lot of fronts !
[Samsung Galaxy Nexus] Duddyroar:
More video evidence, note how the volume goes mad even after I lift my thumb away

[YOUTUBE]B6xlZFcgPlo[/YOUTUBE]
[Samsung Galaxy Nexus] kristovaher:
Alright, this seriously looks like a hardware issue. There's just no way around it. Software bugs rarely work that way.
[Samsung Galaxy Nexus] Shodney:
Thats the exact same behaviour that I get. I'm just trying to make it do it again, so I can get a log :rolleyes:
[Samsung Galaxy Nexus] oscillik:
except that the phone doesn't do this when in bootloader or recovery mode.
[Samsung Galaxy Nexus] BiGMERF:
woooooooooooooooooooooow. i am concerned
[Samsung Galaxy Nexus] TonyHoyle:
Device drivers can easily do that if they get into a funny state.. To determine hardware or software you'd have to have someone logging the actual button state when it happens - which I'm sure someone will do eventually (suspect it'd need a custom kernel, but XDA is full of people who can do that :p).
[Samsung Galaxy Nexus] kristovaher:
Not many who have the problem have tried recovery mode yet I assume, but if true, this could possibly happen because WiFi antenna is off? Maybe this has something to do with WiFi antenna and wiring?
[Samsung Galaxy Nexus] spamlucal:
could it be GSM radio interference? (or related to that in some way) in that video it seemed to match data transmission (you can see the little arrows when there is data movement).. that would explain why the problem manifests in-call too. And it would explain the turning wifi on or off moment (that initiates or terminates a data call, so there is gsm radio movement)

to those having the problem, if you enable "Only 2G networks", and start transmitting data, does it show then?

edit: wifi disabled, of course! Note that I'm talking about GSM and not UMTS, so that would explain that some people can't replicate today, it would affect those that do not get 3G
[Samsung Galaxy Nexus] Shodney:
That made it happen straight away

I attached a log

EDIT: It's still not consistent behaviour though. It started happening as soon as I switched to 2G networks, and started using data. Now it won't happen again, even though I still have 2G only ticked.
[Samsung Galaxy Nexus] whyamihere:
Sounds logical to me.

If this were the case, it could be resolved via radio drivers couldn't it?
[Samsung Galaxy Nexus] WhiterThanWhite:
If this is the cause, it could be linked to the OMAP 4 SoC. I remember the first OMAP 3 phones skipping during music playback whenever there was radio activity (downloading, receiving a text message, tower handovers).
[Samsung Galaxy Nexus] spamlucal:
Well, it's something! there are a lot of variables in radio transmission (power is strongest at the beginning of a call, and such) that might explain why you only saw it at first, but I think we're onto something here ;)

edit: try doing something like a death grip (to force the phone to transmit at a higher power level)
[Samsung Galaxy Nexus] Shodney:
Yeah, it didn't like that too much. It's still not 100% consistent, but it's happening with greater frequency now.

It may be why I couldn't reproduce it properly earlier as I have very spotty 3G connection here. It usually gets just enough for a 3G connection, but sometimes drops to 2G.

Have another log! :D
[Samsung Galaxy Nexus] kurt1189:
Thank's a lot.

In your file we can see lot events like: Dropping key up from device tuna-gpio-keypad because the key was not down. keyCode=25, scanCode=114

KeyCode=25 - KEYCODE_VOLUME_DOWN

Volume Down key. Adjusts the speaker volume down.

Constant Value: 25 (0x00000019) Proof. -

developer.android.com/reference/android/view/KeyEvent.html

Probably it is software bug reated with new screenshot feature (vol down + power)...
[Samsung Galaxy Nexus] [hfm]:
Are you sure about that? Steve's location I mean.
[Samsung Galaxy Nexus] gogol:
Someone please open a thread in the official Google Android support forum. This is really bad, and I can't believe it was not detected before launch :(
[Samsung Galaxy Nexus] seakins:
I did a factory reset 3 hours ago after this happening to me since yesterday and the problem hasn't returned yet. Touch wood :-)
[Samsung Galaxy Nexus] evolad:
Ive reset it 3 times and still going crazy! It does both with wifi on or off..
[Samsung Galaxy Nexus] mikecoffee:
I've not noticed this but I use volume control plus....
[Samsung Galaxy Nexus] :
Hi guys,

the behavior on the vid (thanks a lot) is not comforting.

I think you guys with the issue should report to

Contact Samsung

Contact Samsung directly: 0330 SAMSUNG (7267864)
[Samsung Galaxy Nexus] NatTheCat:
Ive followed this thread but I don't seem to have this issue what so ever. I've attached some info if you guys need it.
[Samsung Galaxy Nexus] gun:
It may have something to do with pressing wifi toggle right next to volume and bad micro switch for volume up
[Samsung Galaxy Nexus] :
Actually, the fact that some users are affected when others are not at all points to a HW/Batch issue by itself.

If it was SW with drivers or ICS , it would be present in all Galaxy Nexus phones.

However, we need to ask all of the owners to try to reproduce with the 2G/Wifi approach that spamlucal posted.

That would give us proof - if the ones without it showing report the issue, then this is more likely something different than a batch problem-
[Samsung Galaxy Nexus] dumb donkey:
Another way i have found to replicate the problem is by switching wifi teather on, which adds to the wifi/ data suspect.
[Samsung Galaxy Nexus] Duddyroar:
I opened an issue thread over on the official Google Android page:

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

If anyone wants to add to that, please do so!
[Samsung Galaxy Nexus] Duddyroar:
Nice find! So we can be pretty sure that this is a software issue, then. I'm assuming the people that have yet to experience this must live in areas with brilliant 3G coverage
[Samsung Galaxy Nexus] oscillik:
not necessarily, this could still be a hardware issue related to the radio. We really need some Google employees to look into this. I've tried alerting a few by Google+, and i've also put this information on the Google Code Issues bug page. Hopefully someone will look into it.
[Samsung Galaxy Nexus] Evostance:
I've has the phone for 3 days now and I've not had the volume issue.

Came to use it tonight and was fighting it. Then the volume indicator on screen stayed on and I just kept fighting it but it wouldn't go away.

Its OK now so it seems like a tempremental software issue
[Samsung Galaxy Nexus] oscillik:
you will probably find that if you set your phone to use 2G networks, that the problem is reproducible. Can you remember if you had a G or E signal on your phone while the problem happened?
[Samsung Galaxy Nexus] Chirality:
Those are buffer overruns, not underruns. Something is triggering those input events at such a fast pace that the system event handlers can't deal with them fast enough.
[Samsung Galaxy Nexus] StuMcBill:
So that's a software issue then?

Sent from my Amiga 500 using Workbench!
[Samsung Galaxy Nexus] Chirality:
Can't draw that conclusion yet. Could be buggy software process triggering those events, or faulty hardware triggering them.
[Samsung Galaxy Nexus] Duddyroar:
Expect this issue to gain some serious attention come monday, only one Android site (Eurodroid) has reported on this issue, but when everyone else is back behind thier desks monday morning, i can imagine that this will be a hot topic.
[Samsung Galaxy Nexus] gogol:
I would hope so. I think we should report this issue also to all those major websites and blogs. To get more coverage.
[Samsung Galaxy Nexus] kristovaher:
I tipped TechCrunch and The Verge.
[Samsung Galaxy Nexus] Shodney:
Thanks for posting the link to the Google page - I couldn't find the damn thing :D

Anyway, I've put a comment on there now so hopefully there will be someone taking a look at it.

You can seem to stop this from happening temporarily by going into the phone info, and choosing "WCDMA Only" in the preferred network type (which locks the phone to 3G networks).

It stops the problem occurring (or at least seems to in the time I had tried it), but it obviously has the drawback of not being able to connect to 2G networks at all. In other words - if your phone has low signal it will simply drop the connection (data, voice, whatever) altogether, rather than changing to a 2G network like it would normally. Because of that it can't be used as a solution, but it was worth noting.

The phone by standard has "GSM/CDMA Auto (PRL)" selected, which uses 3G networks where possible but prefers a 2G network if the 3G signal is low (i.e. if the 3G connection is poor, it will readily drop to a 2G connection rather than hold onto the poor 3G connection).

I have tried selecting "WCDMA Preferred" instead, which works the opposite (in effect). This mode prefers a 3G connection over 2G - i.e. if the 3G connection is poor, it will still hold on to it as long as possible rather than drop to a 2G connection. Unfortunately I can't get it to stick - when I back out of the menu, it reverts to GSM/CDMA Auto. Using my extensive academic resources (i.e. Google :D), it seems this may be dictated by the network and was a problem with the Nexus S. I don't know if I'm correct on this, or if there is a way around it.

If we can get WCDMA preferred to stick, it won't stop the problem from happening - but it should reduce the frequency of occurrence, as the signal will drop to 2G less often. It will probably also have a negative effect on battery life, as the phone will be using more power trying to hold onto a weak signal.

That is, of course, if it IS related to the 2G radio. This could all just be a red herring :D
[Samsung Galaxy Nexus] deadlast28:
Publicity

Hi Gents,

I'm in Australia and i've ordered one of these phones, hoping to have it shipped out on the 23rd November, however concerned whether this is a hardware or software bug at this point. Obviously having to ship it back to the UK would be a pain.

I've just submitted this thread and the official google problem to several android news sites and on the Samsung UK Facebook Page.

Hoping the more widespread the details, the more attention Samsung/Google will give to it.

Hoping this is a software bug, cause I really want this phone :)
[Samsung Galaxy Nexus] Evostance:
I was on wifi at the time but it might have dropped. If so then it would have defiantly been G.

The only thing is, I only get G around this area and I've never had the issue before or since that once
[Samsung Galaxy Nexus] saquib:
Would be interesting too see if the Nexus S guys running ICS have experienced the same issue.
[Samsung Galaxy Nexus] Evostance:
By the way. I cannot replicate this in anyway
[Samsung Galaxy Nexus] bhu1:
It looks like the volume button of the GN has feather touch. My sgs with ics port works perfectly no such problem.
[Samsung Galaxy Nexus] Evostance:
Can't be as the only single time I had it was when I was changing the volume on my phone.
[Samsung Galaxy Nexus] oscillik:
if you look at my log, you'll see that is not the case
[Samsung Galaxy Nexus] Shodney:
Wouldn't the SGS be using a different radio?
[Samsung Galaxy Nexus] Evostance:
Probably a different everything :)
[Samsung Galaxy Nexus] Highland3r:
No such issues running the SDK port (any of the versions) BUT I've not had the issue on the Galaxy Nexus either yet - despite trying to replicate by forcing 2g etc.
[Samsung Galaxy Nexus] RieGo:
no such issue on nexus s aosp. i tried to reproduce it...

it's most likely a hardware or driver issue (which could probably also be fixed with software update)