yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] wilskywalker:
Different SIM card, different results...

I got my handset the other day, it is a SIM unlocked factory unit, not direct from any network, I have also unlocked the bootloader with fastboot oem unlock. No other modifications made. Running Android 4.0.1 currently.

My new contract is with Vodafone UK, I have had the same issue with the sound dropping. I can quite reliably recreate the problem by just stroking the volume button when the phone is using a data connection with the Vodafone UK SIM inserted.

My Number has not yet been ported over to Vodafone yet, so I have also been using my old O2-UK SIM, I am unable to reproduce the problem during either network or wifi connection whilst the O2-UK SIM is inserted.

This seems to me that the issue may be more software based than hardware!?
[Samsung Galaxy Nexus] samizad:
How bloody odd?!
[Samsung Galaxy Nexus] evolad:
I have both o2 and orange sims...doesnt make a difference it still drops

*EDIT... ok i might be wrong here...ive took out a orange contract and waitin for the number to swap from my o2 contract so ive been using the o2 sim...just swapped over 2 orange sim and i dont have the problem even when i switch to 2G or mess mess with wifi??? will keep testing
[Samsung Galaxy Nexus] Duddyroar:
Has anyone tried using a case on their Galaxy Nexus? I'm wondering if gently brushing the volume rocker is creating some kind of connection which is making the phone act strangely.

As much as i want this to be a software issue, i have a horrible feeling it's due to either a faulty batch of hardware or an design flaw (like the iphone 4 death grip).
[Samsung Galaxy Nexus] Gho57:
Someone try with phone in "airplane mode" !
[Samsung Galaxy Nexus] oscillik:
please could you test to see if:

1) When your Vodafone SIM is inserted, what kind of connection you are getting (G, E, 3G or H)

2) When your O2 SIM is inserted, what kind of connection you are getting (G, E, 3G or H)

as has already been noted multiple times, it seems to happen most when the phone has a 2G connection (either G or E).

If your Vodafone SIM is only getting 2G coverage, while your O2 SIM is getting 3G or better, then that would explain why you have differing results with different SIM cards.
[Samsung Galaxy Nexus] burnduck:
My phone started turning down it's volume as soon as i unboxed and powered on my phone :/

So it's definitely not related to any software installed on the phone.
[Samsung Galaxy Nexus] evolad:
My orange is on G cant get it to do it...o2 sim is E and goes mental
[Samsung Galaxy Nexus] Duddyroar:
Just tried it, the issue vanishes in airplane mode.

As soon as i switched airplane mode off, the volume went crazy. Then, when i got a text message a few minutes later, it did it again. I'm in a poor reception area so I'm stuck on 2G.
[Samsung Galaxy Nexus] keridel:
hey guys.

i have tried to reproduce the Bug but to no avail.

nothing i do will make the volume adjust on its own. nothing at all.

i would assume a faulty batch
[Samsung Galaxy Nexus] MysteriousDiary:
So maybe it's just some weird Sim Card problem?
[Samsung Galaxy Nexus] her0n:
Or, you have good 3g signal so have not seen it yet?
[Samsung Galaxy Nexus] evolad:
Not got a clue all i know is that using my orange sim it seems to be ok even on 2G.... makes me happy though im still unsure if i should get it replaced...
[Samsung Galaxy Nexus] wilskywalker:
The O2-UK signal is a fairly steady 3G - H, whilst the Vodafone signal ranges from G - H, though I should mention that I realized this was the case so forced the O2 SIM onto 2G network and still couldn't reproduce the problem.

I have since managed to recreate the issue just once with the O2 SIM which knocked out the power button for a few seconds too (I should mention though I was purposely rubbing the volume button a lot and quite hard to get this result). Only once though, it was happening a lot with the Vodafone SIM. The apparent random behavior and different experiences between users still leads me to think it is a software issue to be honest.

I have only noted this problem when

actively

accessing the network in some form though, so perhaps your hand is interacting with a component in the phone at this moment. Perhaps a software update could stop that interaction affecting the system sound toggle even if it is a hardware issue?
[Samsung Galaxy Nexus] Gho57:
i hope it's a radio software problem, not hardware :(

in this video: http://www.youtube.com/watch?v=B6xlZFcgPlom

if you put the volume up when the error occurs you can hear a tipical radio interference or i am wrong?
[Samsung Galaxy Nexus] keridel:
i have turned it on to 2g. been in a bad 3g area. tried it on wifi. tried it on airplane. tried everything. i cannot reproduce it.
[Samsung Galaxy Nexus] oscillik:
yes it does appear to be when data is being transferred. it is still an intermittent thing though - i was trying to demonstrate to someone, and it took a few minutes of playing about with apps that transfer data to get it to trigger.
[Samsung Galaxy Nexus] bhu1:
U guys took me wrong , I was just trying to tease ya guys . I know every single part is different.
[Samsung Galaxy Nexus] Evostance:
Got a video? Stroking the button does nothing for me

I just looked at my phone to find I was on gprs and my sound was muted
[Samsung Galaxy Nexus] burnduck:
It has something to do with 2g radio, it would act crazy whenever it falls back to 2g. It could be mitigated by new software handling the volume control, but the intereference will still occur and could cause other problems in a long run :( will talk to phones4u tomorrow and see what can be done
[Samsung Galaxy Nexus] electric0ant:
I doubt its a button issue, at first i did think it was a over sensitive button but then the volume thing happened even when i had my fingers no where near the buttons.

As someone said earlier it def is an issue related to the 2G radio.

I had the issue on friday when I was going around richmond area in london which i was mainly on 2G and it kept happening.

I am using O2 and been mainly at home this weekend and been on 3G the whole time and did not have the issue.

I changed the option to use 2G only and then left my phone on my desk, when i next picked up the phone and unlocked it the volume suddenly went all the way down.

seems like this is a software or firmware issue with the 2G Radio, as it doesn't happen all the time while on 2G as well.

Obviously this is a major issue as i can't have my phone randomly drop the volume all the way down when i'm out of 3G coverage. The question is how long before a fix comes out, or am I going to have to return it and wait for the issue to be fixed before buying it again.

I will see if i can post a video, on friday i caught moments when the volume was going up and down like crazy as well, (it would randomly happen while i was using the phone)
[Samsung Galaxy Nexus] burnduck:
Just force the phone to use 2g and you will see it go nuts
[Samsung Galaxy Nexus] electric0ant:
yeah i've been doing that but its behaving itself now... even tried using data on 2G and it's not doing anything...

I guess I will see how it goes at work tomorrow. I only get GPRS or EDGE in my office, so if its playing up there, then I will definitely take to back to phones4u.
[Samsung Galaxy Nexus] mcgon1979:
What a community on here. 24hours to figure out and narrow down the volume issue to a 2G radio problem. Superb. Hopefully a fix is not far away
[Samsung Galaxy Nexus] Evostance:
I'm on 2g now. Seems OK to me
[Samsung Galaxy Nexus] escrivel:
So guys, whats the matter?

-SIM-Card?

-2g net?

Hopefully there will be no issue with the t-mobile sims in germany!
[Samsung Galaxy Nexus] kristovaher:
Well in order to really say that we need to find samples of all the SIM cards used so far. Is there a SIM card that has not had this problem at all? Since so far it seems that some people have it and others don't even while they are customers of the same company.
[Samsung Galaxy Nexus] evolad:
Not had a prob on mine since swapping to orange sim... with the o2 i could get it to happen 80% of the time by brushing the volume button and playing with the wifi.
[Samsung Galaxy Nexus] electric0ant:
since having my phone on 2G it has happened twice in the past 3 hours.
[Samsung Galaxy Nexus] TonyHoyle:
Most people seem to set their forum profiles up with their provider, so getting a sample of which sims are problematic should be just a matter of going through this thread with a pen and paper...

Would be interesting to know if anyone on three has it, as they have no 2g support so it wouldn't be a factor.
[Samsung Galaxy Nexus] WhiterThanWhite:
I seriously doubt if this is something to do with SIM cards. The probable reason for people on the same network not experiencing the same symptoms is because they live in different geographical locations, with differing 2G signal strength.
[Samsung Galaxy Nexus] gogol:
What if you set to use WCDMA Only?
[Samsung Galaxy Nexus] electric0ant:
Just happened to me again, my phone had one of the longer "seizures" this time where i would try to increase the volume and it would fight with me to keep dropping it down.

I managed to start getting a video of it halfway into it:

http://youtu.be/TqOiIfO0AWE

as you can see nothing else on the screen responds when its turning the volume down.
[Samsung Galaxy Nexus] appelflap:
Lol.. never happened to me before. But I tried to do the test with forcing 2G and the thing went crazy...
[Samsung Galaxy Nexus] burnduck:
It's highly possible that the "ghost" is actually the phone itself picking up it's own 2G signal interference and somehow it's "jamming" the volume down control of the phone.

It is like when you put a 2G phone next to a speaker and make calls. How ironic they've got the "Radiation" ringtone in settings and 2G radiation is causing itself go nuts.

I seriously doubt if it's a software issue, to me it's more like poor EM shielding and grounding. I'm simply an amerture radio guy not a professional EM engineer, but if it is proven to be a design fault Google could either force Samsung to recall the phone (which is going to cost the kimchi-brewing company £££), or they could come up with some form of "software updates" which recognise this pattern of "volume down requests" and ignore it. If they've chosen to go for the later, it's hard to say whether this is the end of the story.

---------- Post added at 07:17 AM ---------- Previous post was at 07:12 AM ----------

By the way I'm on Vodafone contract if anyone cares to report which network they're on and how badly they're affected. Because my hypothesis is all Galaxy Nexuses should be affected except for those who are on 3 (network), as they don't have any 2G network to fall back onto.

(This was the words from one of the 3 corporate people, I have spoken with them a while ago and they confirmed they've switched off the entire 2G network and rely purely on their 2100MHz 3G network. But me personally doubt that as some of my friends still manages to get 2G signal in places like coventry)
[Samsung Galaxy Nexus] rakh1:
I swapped hardware (thanks O2) and it's gone away. Batch related?

R
[Samsung Galaxy Nexus] oscillik:
3 customers do get 2G reception, but it's via Orange. This is why 3-UK will generally tinker with the firmware of a phone so that you cannot switch to a 2G network manually, because it costs 3-UK a lot of money if you use the 2G network.

but anyway, back to the discussion...
[Samsung Galaxy Nexus] burnduck:
can you please try putting the phone in 2G mode and see if it goes crazy while doing data transfer / phone calls?

in settings ->Wireless & Networks -> More... -> Mobile networks -> Use only 2G networks (tick)

I hope it's batch problem not design fault because I do love this phone!
[Samsung Galaxy Nexus] electric0ant:
i hope this gets resolved soon, i wouldn't be so bothered if vibrate was still working if volume goes down, but it actually turns vibrate off as well.
[Samsung Galaxy Nexus] oscillik:
I have just returned from the O2 shop with a brand new replacement handset.

Turned it on, set the phone to use 2G networks only. Within 5 mins, the problem happened.
[Samsung Galaxy Nexus] bhu1:
Man although I don't have a GN, but I can feel how much u guys are fed up of this problem. Its really annoying to buy one of the latest and best phones in the market and end up knowing that it has a major bug . Just keep going back to their shop and keep reporting the bug, they will know how big and annoying this bug is and will work faster to fix it.
[Samsung Galaxy Nexus] noobdeagle:
im pretty sure that google will fix this issue, its a massive issue but being google and a nexus device its bound to get fixed fast.
[Samsung Galaxy Nexus] oscillik:
by all indications, this is not something that Google can fix. It is very likely a hardware issue, and thus needs to be sorted by Samsung.
[Samsung Galaxy Nexus] BiGMERF:
my question is are there field testers this f'n dumb?!
[Samsung Galaxy Nexus] kristovaher:
It was likely tested in Korea or parts of asia that do not use GSM 900.

Let's face it, Samsung did not really put that much effort into the phone, other than the screen. They are more interested in pushing upcoming Galaxy S3 .
[Samsung Galaxy Nexus] oscillik:
that's no excuse though - the phone should've been tested, both by Samsung themselves and by Google. Looks like neither of them have tested the 2G connectivity.
[Samsung Galaxy Nexus] kristovaher:
Oh I totally agree that it is not an excuse. I very much doubt Google will be using Samsung for their next Nexus phone, I wrote about it a little here.
[Samsung Galaxy Nexus] BiGMERF:
atleast that bodes well for us that are importing to the USA
[Samsung Galaxy Nexus] tjtj4444:
It is very common to work around hardware issues in software. In this case it might be enough to filter the volume button signals a bit more, i e require a longer and more stable indication from the hardware before judging the button as pressed.

This might cause slightly longer response time when changing the volume though, but that is a small problem compared to the current problem.
[Samsung Galaxy Nexus] Niksko:
You are a very smart man. Honestly, when do you need to make split second adjustments to your volume. Perhaps if it's turned down too low during a call and your environment becomes suddenly very loud, but even then you can just ask the other person to repeat what they said.

I'm sure a patch will come along soon.
[Samsung Galaxy Nexus] oscillik:
that doesn't stop there being an actual hardware issue though. if a baseband update is applied, or an update to Android, it doesn't stop the phone receiving RF interference where it shouldn't be getting interference.
[Samsung Galaxy Nexus] bhu1:
Google has bought Motorola so its obvious who Google will be using for next nexus device.
[Samsung Galaxy Nexus] oscillik:
Google haven't bought Motorola yet. They have announced that they will acquire Motorola. These things take months and months to happen, so Google won't actually own Motorola until sometime in 2012.
[Samsung Galaxy Nexus] tjtj4444:
I agree, work around hardware issues with software is not an elegant solution... But better than nothing :)

If the cause is interference from 900 MHz then this is a true engineering failure, doing EMC tests thoroughly with all the relevant frequenceies is very important when developing a smart phone (http://en.wikipedia.org/wiki/Electromagnetic_compatibility ).

And appearantly the didn't have enough time for enough field tests with the final hardware either.

I must admit though that there is an electromagnetic nightmare in a modern smartphone, but that is no excuse.
[Samsung Galaxy Nexus] kristovaher:
Of course.

But this will not stop Google from developing the next Nexus phone with Motorola at all. Google does not own Samsung either. Motorola board has already agreed to the purchase already.

Motorola knows that Google will be their new 'employer', Google will have more control over the next Nexus handset and Motorola has proven that they are a very capable handset maker, Droid RAZR has been a success.

If the next Nexus phone won't be manufactured by Motorola I'll buy you lunch.
[Samsung Galaxy Nexus] oscillik:
my post was just to point out that Google don't actually own Motorola Mobility yet. And even when they do, Google have already gone on record to say that the Motorola division will operate as a separate company. Of course, all corporate statements should be taken with plenty of salt and pepper...
[Samsung Galaxy Nexus] Chrono_Tata:
The Motorola acquisition was made primarily to acquire the large amount of patents Motorola has to fight against Apple's patent lawsuits anyway. We'll yet to see how much influence Google will exert on their normal operations.
[Samsung Galaxy Nexus] M2281088:
I'll take you up on that bet ;)
[Samsung Galaxy Nexus] DJ_Steve:
i havent got a gn but i thought id throw this out their as a idea, has anyone tried forcing 2g but turning mobile data OFF so its only running calls/sms and seeing if it gets the same result when a call/message comes in/is sent/made
[Samsung Galaxy Nexus] oscillik:
CNET have already mentioned about their inability to hear calls when in 2G mode here
[Samsung Galaxy Nexus] Duddyroar:
Just tried it, the problem remains even with mobile data switched off.
[Samsung Galaxy Nexus] iamhermes:
ww w.you tube.com/watch?v=qXjARxvErjk

It seems to be a hardware issue. I'll wait for the next revision of this phone :(
[Samsung Galaxy Nexus] Nebucatnetzer:
ooohhh that's bad.
[Samsung Galaxy Nexus] Gho57:
another antenna gate, but in this case even there are no excuses about the hold the phone in a wrong way :(
[Samsung Galaxy Nexus] TonyHoyle:
"You're using the wrong sort of 2G"
[Samsung Galaxy Nexus] evolad:
Can anyone tell me why i cant reproduce this with the orange sim at all..even using 2g only or placing another phone next to it... though the o2 will?
[Samsung Galaxy Nexus] oscillik:
because the problem only happens when on 900MHz

O2 uses 900MHz for 2G connections

Orange doesn't use 900MHz at all
[Samsung Galaxy Nexus] whyamihere:
Because Orange 2G operates at 1800Mhz frequency.

The bug only happens at the 900Mhz frequency that O2 and Vodafone use for 2G.

Orange, T-Mobile and 3 are unaffected.
[Samsung Galaxy Nexus] jaketurbo:
Neither can i. I can with vodafone sim.

Ive even tried airplane mode and holding an n1, desire and a galaxy s next to it.
[Samsung Galaxy Nexus] burnduck:
haha now it gets even more interesting!

so it has nothing to do with it's radio Tx component but the volume circuit somehow managed to pickup the EM and interpret it as some sort of input!

It definitely has nothing to do with Google, and even if it's "fixable" it has something to do with the kernel on how it handle those fake inputs
[Samsung Galaxy Nexus] oscillik:
it has nothing to do with the kernel, the problem shows up even in bootloader mode which doesn't load any kernel, drivers, baseband, or anything Android related.
[Samsung Galaxy Nexus] electric0ant:
been to phones4u and tried to get a refund, bunch of cowboys refusing to give me a refund even when i quoted them the consumer rights.

they gave me an exchange which i've just tested and of course still has the same issue.

I guess from the posted video it has shown that the issue lies with the 900mhz gsm band so only vodafone and o2 customers will really be affected. which would explain why the issue isn't so widespread since phones4u didn't sell vodafone contracts i believe.

i there a way to manually set the phone not to use the 900mhz band?

guess i will be calling phones4u head office and my credit card company tomorrow.
[Samsung Galaxy Nexus] oscillik:
they are breaking UK law by not honouring your request for a full refund. the handset is defective by design, and under the Sale of Goods Act 1979 you are entitled to a refund from the point of sale.
[Samsung Galaxy Nexus] electric0ant:
how the crap did samsung miss this?

I am so f***ing pissed right now, i only get 2g reception in my office at work so I have a phone which does this all day during work.

so i essentially have a £530 semi brick which phones4u is refusing to refund.

tbh the guys in phones4u even have to phone some office to get authorization to do an exchange so when their head office is closed i don;t have a chance of getting a refund.
[Samsung Galaxy Nexus] saster2:
Maybe the they had to use less shielding for NFC to work?
[Samsung Galaxy Nexus] oscillik:
this is nothing to do with NFC. please read the facts
[Samsung Galaxy Nexus] saster2:
I meant that GN might have less shielding than other phones, because of the NFC capability.
[Samsung Galaxy Nexus] oscillik:
The Nexus S had NFC capability and didn't suffer from this hardware defect.
[Samsung Galaxy Nexus] burnduck:
well it's down to hardware design fault then
[Samsung Galaxy Nexus] oscillik:
really, you think? it's already been discussed to death in the other thread that this is definitely a hardware related issue. if you check back on my posts you'll see that the majority of my posts have been asserting to disbelieving users on here that this is a hardware issue and not a software issue.
[Samsung Galaxy Nexus] Hands0n:
Here's a shortie video of the fault happening with my SGN - I couldn't make it happen just by being set to 2G on the giffgaff (O2) network. But a nearby 2G handset triggered the fault off quite spectacularly.

http://youtu.be/LjwMzooNVCE

Meanwhile, where's the word from Samsung? Even if its "What fault?" it would be a start.
[Samsung Galaxy Nexus] Archon810:
The bug is software related, Google is releasing a software fix shortly: http://www.androidpolice.com/2011/1...ware-related-software-fix-already-on-the-way/

So it's not hardware after all.
[Sony Ericsson XPERIA X10 Mini] aleedee:
As the topic's title suggests, the installation of this wonderful ROM disabeled mms functionality. In the conversation window the message status is Sending... Settings are correct, I checked them with my carrier. What could be wrong? This is the second installation of the same ROM, and I have the same problem again.
[Sony Ericsson XPERIA X10 Mini] coversnail:
It's a problem with all ROM's based on Cyanogenmod 7. When using stock the phone automatically activates mobile data to send and recieve MMS. Cyanogenmod doesn't, its been listed on their bug-tracker so they are aware of it but nothing has been done yet.

To send MMS you have to turn mobile data on, and make sure your APN settings are correct
[Sony Ericsson XPERIA X10 Mini] aleedee:
Mobile data is on and my mms settings are correct, I cheched them. Is there any log file that I could upload?
[Sony Ericsson XPERIA X10 Mini] coversnail:
Try rebooting the phone then turn mobile data on, but make sure that wifi is off. Then resend the message. The log file won't mean much to me I'm afraid!
[Sony Ericsson XPERIA X10 Mini] chints108:
lol...people still use MMSs nowadays?
[Sony Ericsson XPERIA X10 Mini] aleedee:
LOL, people still think sms and email are almighty? How do I send a picture to someone, that doesn't use email on his not-so-smart-phone?
[Sony Ericsson XPERIA X10 Mini] aleedee:
Don't tell me I'm the only one with this problem??
[Sony Ericsson XPERIA X10 Mini] aleedee:
Could a complete wipe out and reflash fix this problem? I also get FC when taking pictures with the camera, so I'm thinking about starting from scratch...
[Sony Ericsson XPERIA X10 Mini] collectric:
No, you're not the only one. I have the exact same problem. I am trying every possible setting for the mms APN, turned off and on the data communication, rebooted the phone again and again - no mms, send or receive.

I guess we'll have to keep on searching for a solution...
[Sony Ericsson XPERIA X10 Mini] aleedee:
I'm gonna try reflash... Let you know if it works...
[Sony Ericsson XPERIA X10 Mini] aleedee:
Reflashing didn't help, and I can't post it to the official theme, because I don't have enough posts....
[Sony Ericsson XPERIA X10 Mini] meer_mortal:
maybe enable national roaming data. just in case your carrier roams on another carriers network.

what messaging app you using?