yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Hosh0:
I don't get what they have done wrong hey? They have said there is an issue and they are working on a fix? Is this not enough? Or do you expect daily updates on where the fix is up to etc? Samsung and Google will address this issue once they are happy with their fix, they can't give more information than that surely? I mean if they say it will be out tomorrow and then don't meet that timeline due to some internal testing issue then people complain more.

If their statement doesn't provide you with enough confidence then you have the right to return the item, but just saying this shows how much they care about their customers is a bit silly.
[Samsung Galaxy Nexus] Rubu:
I think most of you guys are being a bit harsh. Ofcourse the communication is lacking, but this really isn't uncommon for companies like these. For some reason they'd rather just keep quiet than keep their costumers informed. I really doubt that other companies would do a better job at keeping the public informed.

Chill. The fix will get here.
[Samsung Galaxy Nexus] M2281088:
Other companies can be as bad, but Samsung have said that they aknowledge there is a fault, on their facebook page. I have not seen anything anywhere else. We have heard nothing official since. Even Apple said oops and tried to keep people happier.

When I spoke to Samsung I was told "We have not heard of this issue before". I wouldn't have minded but this was 2 days before they admitted a problem and more than a day after they publicly gave out a phone number to ring.

They promised a call IF there was an issue, not a word from them.

I am ranting as this is not good enough from their publicity people. [/RANT]
[Samsung Galaxy Nexus] jabok:
The problem is that their one and only update said they had DEVELOPED a fix. i.e. past tense - the fix is done. This obviously creates expectation that it will be delivered with alacrity given the nature of the problem. If they hadn't tested it at that point then they should have said so - thereby creating less expectation.
[Samsung Galaxy Nexus] Matcarroll:
Mines got to be back on Thursday so not long left. Don't want to send it back but not going to risk it. I won't get another android phone though, this was my first phone away from apple and although I love the phone, the customer service from Samsung and google is terrible.
[Samsung Galaxy Nexus] oscillik:
Well it has to be said - Samsung caring about their customers is irrelevant where getting a refund/replacement on a faulty item is concerned. As the Sale of Goods Act clearly states, it is the retailers responsibility to honour your statutory rights, not the manufacturers. Now, many retailers will try to shove that responsibility onto the manufacturer and palm off it's customers by telling them to deal with the manufacturer directly. This is disingenuous, since when you paid for the goods you entered into a contract with the retailer, not the manufacturer. As such, it is the retailer's responsibility to deal with the issue. If you have been sold a defective item (and in this case, you have), then you are entitled to a refund in full or a brand new replacement.

I can understand you maybe not wanting to haggle with the retailer over this issue, but please remember that these are your statutory rights and any UK retailer not upholding them is breaking UK trading law.

The main reason why people are getting annoyed here is that we have some hearsay reports that Samsung are already in the process of flashing handsets with the fix before sending them out to retailers. If this is the case, then the fix is ready for primetime, and there should be no excuse as to why we haven't had the fix pushed out to us.

As I said,

this is hearsay

and we have had no confirmation from anyone at Google or Samsung that this is happening. So I think people getting angry about this is, at the moment, a little misplaced also.
[Samsung Galaxy Nexus] giryan:
Looks like Paul at Modaco's got a fix.

I can't post a link, so you'll just have to go look at the Galaxy Nexus forum there :)
[Samsung Galaxy Nexus] darkoroje:
Isn't the fact that there is no official comment from Samsung a problem in itself? They have, after all, released the Nexus with a glaring bug of not being able to be used as a phone on 2G. This is the same company that released the original Galaxy with a non-working GPS, which was also a hardware flaw. That was never fixed.

The safest option right now is to return the Nexus and the re-buy it after a fix has been released and confirmed working.
[Samsung Galaxy Nexus] M2281088:
Wish I could, but mine was given as part of the renewal of my contract, which was done through Phones4U so I could get GN.
[Samsung Galaxy Nexus] oscillik:
If you're talking about in terms of getting a refund, It doesn't matter whether there is no official word from Samsung on the matter. The fact is that this defect is well publicised, and is easily reproducible. Within the first 6 months of purchase, the onus is on the retailer to prove that there is no fault with the phone.

If you're just speaking generally that it is a bit of a PR nightmare that they haven't really said much, I would agree with you. But then, this is what companies are like. It took Nokia a long time to publicly acknowledge the lens cover issues with the N97, after all.

---------- Post added at 12:06 PM ---------- Previous post was at 12:02 PM ----------

Ahh you're in a contract :( Then yes, you would need to return it during the cooling-off period. Hopefully it won't come to that.
[Samsung Galaxy Nexus] mark.m.moran:
He mate, did you get yours from Vodafone in Ireland? I sent mine back today. Was in London over the weekend and was roaming and it happened many many times!! Was on a call when the volume dropped one time!!

Cheers,

M

---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------

Same here mate. Sent mine back to Vodafone today. Very very disappointed to do it as love everything else about the phone....

Cheers,

M
[Samsung Galaxy Nexus] bushbrother:
Anyone taken the plunge and tried this?
[Samsung Galaxy Nexus] kristovaher:
That might murderize warranty, so I haven't dared. I still fear I have to send the device back.
[Samsung Galaxy Nexus] bushbrother:
I guess someone who has already been brave enough to root already needs to try it out :)

I am still awaiting my dispatch from clove ... hoping that it will have this already on there!
[Samsung Galaxy Nexus] Duddyroar:
Just had this from Samsung's tech guy (who has been very helpful throughout this process, I might add):

So we're basically looking at the end of the week, if all goes to plan.
[Samsung Galaxy Nexus] oscillik:
That's promising news...thanks for letting us know about this!
[Samsung Galaxy Nexus] Fpad77:
It's promising but it isn't soon enough given the seriousness of the side effects this is causing. Their ineptitude in resolving this swiftly is somewhat disappointing, as well as their complete lack of open communication to those affected by it, its pretty appalling from a PR perspective.
[Samsung Galaxy Nexus] Shodney:
Paul tweeted that the issue hasn't been resolved while in Bootloader mode.

It will be interesting to test CPU load on a "fixed" unit though while interference is introduced externally (as in the Youtube tests), to see if the fix has any negative impact (and therefore have an effect on the battery).

For the record, I have rooted my phone but I'm trying to keep it as stock as possible until the fix is rolled out officially. If the fix turns out to be hurting performance in some way then it will easier to get back to stock and return the phone, but this is just me hedging my bets ;)
[Samsung Galaxy Nexus] mnexusaud:
Hantec said they are getting a new shipment of new phones (I emailed them) today (28th) and will send out immediately.

If the fix is being released later this week as someone stated apparently, does this mean Hantec's new batch of phones does NOT include the fix? If it doesn't then why delay orders in the first place since the phones are still broken?

I'm based in Australia and I need the phone asap. They promised expedited shipping but didn't say if it included international buyers.

Any more news on new batches being sent out to suppliers? It's interesting to see if they actually have the fix on these new phones.
[Samsung Galaxy Nexus] noobdeagle:
yeah i have no idea whats going on if they were flashing the fix it makes sense HOWEVER! if that is the case why isnt the update out already ?, imo come tomorrow there will be another delay, cause from what i read handtec were last told it would be this week but they are waiting for confirmation
[Samsung Galaxy Nexus] bushbrother:
I have mine on pre-order with Clove and they are still stating Tuesday for next batch to be in stock, no word on the "patch" status of these phones though ...
[Samsung Galaxy Nexus] mnexusaud:
It's absolutely ridiculous that Hantec have such little information to give out and even moreso that Google/Samsung have maintained a lack of information. Apple give better customer service than these guys, this is pathetic. I got better service with Microsoft.

If Hantec delay until tomorrow I better get my phone by Friday (with their expedited shipping promise - does this cover international buyers). Not having a phone a week or two late without any explanation is crazy.
[Samsung Galaxy Nexus] gambiting:
My friend from Phones4U called their own dedicated Samsung support line,and they told him that the update will be pushed OTA this week. No specific date though.
[Samsung Galaxy Nexus] qwerp_:
i have just applied the fix from paul MoDaCo..

will report back if it helps.
[Samsung Galaxy Nexus] justabrake:
Is this right ! Are you kidding, Didn't everyone just return them and get refunded ?
[Samsung Galaxy Nexus] bobbysixkiller:
well if it is due this week google should get off their arse and give us an update, i would retune mine but then what i still wont have a working phone and will only go and rebuy when it fixed
[Samsung Galaxy Nexus] malliktajmahal:
qwerp_ //

Hi Waiting for your reply...:)
[Samsung Galaxy Nexus] qwerp_:
all seems good so far. (as advertise).

no problem with the volume.

even try with my original interference from another phone, it does not trigger it.

i am however not able to comment if this will drain more battery usage or not yet.
[Samsung Galaxy Nexus] bushbrother:
Good to hear :) Does it still occur in bootloader?
[Samsung Galaxy Nexus] sethyx:
Thanks for the report!

Can you pls check the cpu usage while trying to trigger the bug? I'm going to be sad if it still jumps up to 30-40%...
[Samsung Galaxy Nexus] breezasib:
+1 on the bootloader question
[Samsung Galaxy Nexus] sethyx:
It happens in the bootloader, Paul (who released the patch) already tweeted this.
[Samsung Galaxy Nexus] qwerp_:
no, it will/did not fix the boot loader.

but this does not affect your daily life..
[Samsung Galaxy Nexus] oscillik:
No it doesn't affect daily life, but knowing more about the issue and the patch that has been applied doesn't hurt.

If the patch that PaulOBrien has put out is indeed similar to what is going to be pushed out by Google soon, then it does show that those of us who have theorised that it is a hardware issue were right all along.
[Samsung Galaxy Nexus] Shaldy:
The main thing: does it still load cpu with button readings after fix? Can anyone test this?

There are tons of apps on market, something like OS Monitor (can't link) should work.
[Samsung Galaxy Nexus] SuperUserMovado:
So this is a patch done just for userland??
[Samsung Galaxy Nexus] qwerp_:
i am not sure how accurate this is..

it seems to spike only once from average of under 10 to around 50% when there is a 2G interference. it just a spike, then drop back to normal.

almost like a trap where once it detected it, it just drop and ignore it. other than that, i can't see anything much more.

hope that helps.

i believe if u want a more understanding, its better to ask the creator of the fix on what/how is his logic on solving this issue.

its good as gold for me now as i live in a area where the bloody o2 signal is rubbish and is affecting me (not anymore).
[Samsung Galaxy Nexus] bongadadu:
Just got my GN on O2 and it has this bug. Caused the phone to crash whilst i was listening to music. Had to take battery out and reboot.

Reading reports now that this is hardware and the software fix might cause performance issues such as cpu cycles and battery drain is making me paranoid.

I asked Paul Brien on twitter if the software fix is just for the faulty handsets and a hardware iteration is due later, and this is what he said:

i*imgur*com/uPysj*png (replace * with .)

I later asked him if they are going to silently roll out a new hard ware iteration and have yet to hear a response.

---------- Post added at 05:37 PM ---------- Previous post was at 05:29 PM ----------

After a day of normal use, can you let us know if you experience any performance / battery issues please. Thanks

I'm also on O2 and paranoid that the fix might just be to shut us early adopters up (although Paul Brien says all devices get this and there is no hardware iteration).
[Samsung Galaxy Nexus] gambiting:
Qwerp, is there any chance you could connect your phone to DDMS and see what's going on? It might say something useful, like "interference detected,ignoring" or something along these lines. Thanks!
[Samsung Galaxy Nexus] oscillik:
Considering the explanation of the software fix, I think it's highly unlikely that Samsung will produce a new hardware revision to combat this hardware related fault. As long as the software patch does it's job, from Samsung's perspective there is no reason to change the hardware configuration.
[Samsung Galaxy Nexus] Alexander T.:
Yep.

Considering their ignorance towards I9000's GPS malfunction, this sounds very likely!

Moreover, when the SGS3 is released, no one in Samsung will ever remember GNexus.
[Samsung Galaxy Nexus] onyxogen:
That's lame. So its really just kind of a workaround :mad:
[Samsung Galaxy Nexus] SuperUserMovado:
Its a patch that works. Its not the fix you want but the fix you need

As long as you are not flashing roms in a 2g area you will be fine.
[Samsung Galaxy Nexus] jabok:
What about the volume control - does it work normally when you're in your crappy 2g area? ;) I.e. They've stopped it going mental but can you control it normally without lag/missed presses/duplicated presses, etc, during a call?
[Samsung Galaxy Nexus] mjdyson:
I thought that was a given! Forgive me if I mis-interpret what's going on but...

A hardware issue due to improperly configured components is something completely different to a hardware issue due to flawed design.

Given Samsung's experience in the hardware game, I hope it to be the former. I'm not entirely sure what effect a patch to the OS would have - deep in the Android OS, there will be event monitors for touch events, location events, whatever.. it's just another event. Only time will tell.

It would be nice to have a quick fix for 4.0.2 and a more long term baseband fix in 4.0.3. We can but dream...
[Samsung Galaxy Nexus] Shaldy:
Okay, one more question, when you are doing the test, try to push the button.

Will it work ok, or will it go crazy again? Or will it stop working altogether, because phone is trying to ignore it?
[Samsung Galaxy Nexus] onyxogen:
But I will!!!!!!!
[Samsung Galaxy Nexus] Vash63:
More precisely, as long as you're not flashing ROMs in a 2G area with a different phone on an active call within a few centimeters, you should be fine. The local radio is not connecting to anything in the bootloader so outside interference should be the only issue, and I doubt it's a major one.
[Samsung Galaxy Nexus] Luxferro:
I'm debating if I should cancel my galaxy nexus order. From what I have read it seems they didn't actually fix the problem, and just applied a band-aid so you won't see it. That it still exists in the bootloader.

IMO, this is not how to properly fix things, and seems kinda shady that there is no official publications acknowledging the problem, and why they are just applying a band-aid and not a real fix.
[Samsung Galaxy Nexus] CanaganD:
Apparently, my Korean coworkers say that Samsung never tests their hardware. Often, they release to the Korean public with known bugs. The Korean people are then the beta testers.

Coworkers advised me to stay away from Samsung as they often have this track record (no so public in the West because it mostly affects Koreans).

If anything, the fix was probably just this: (in psuedo code)

Yes, it can probably be more sophisticated, but basically, some software logic to mitigate the volume issues by detecting known symptoms and causes which means it probably won't work 100% of the time.

// External Vars

int staleVolTime = <time that the volume had not changed>

int staleVolLevel = <level of volume associated with stale state>

List listVolChangeRequests = <list of 10 latest vol change requests>

// Volume Down event triggered by hardware calling the code

public volDownEvent()

{

// if the volume button was not depressed for more than half a second, exit, don't drop volume

if notVolButtonHoldHalfSecond()

staleVolTime = currentTime

return()

end if

// If there are on average, more than 2 requests per second (from a pool of 10 recoreded requests)

if moreThan2RequestsIn1Second(listVolChangeRequests) AND 2Gmode then

systemVolLevel = staleVolLevel

staleVolTime = currentTime

end if

// If Volume Level was stable for more than 4 secondsAND the above 2reqs per second was satisfied, drop volume

if staleVolTime.diff(currentTime) > 4 seconds

systemVolLevel = systemVolLevel - 1

endif

}
[Samsung Galaxy Nexus] bleets:
how can anybody actually comment on what the official fix will be until the official fix is officially release to the official public officially?

at the moment you have a 3rd party modder saying "oh yeah...err...this is it, download it from me!"
[Samsung Galaxy Nexus] bobbysixkiller:
i agree, we need to wait for the patch and then dissect it. i just wish google would friggin update us!
[Samsung Galaxy Nexus] MatthewPL:
Because "official" there is no issue/bug. Samsung and Google doesn't say anything about this. No bug no problem? Tell it this all people who spend lot of money to buy this phone and now they cannot use it.
[Samsung Galaxy Nexus] bleets:
except both samsung and google have released statements acknowledging the bug and promising a fix.
[Samsung Galaxy Nexus] Luxferro:
Show an official link by either samsung or google PR stating this, and not some employee posting on his personal blog/page, ect. And not something referring to some unknown source.

Originally I figured this would be easily fixed, and be done right. Now that Paul Obrien says he has the fix, and it only fixes it at the OS level, I am not happy with all the unknowns anymore and rethinking my pending purchase.

I just posted this on the thread on Dan Morrill's google+ page where he acknowledged the bug. Not that I think he will reply or care. Someone needs to step up and make make a real PR acknowledgement of this problem and the fix.

https://plus.google.com/u/0/112413860260589530492/posts/1a4hY7VeqiG

anyone who has concerns, blow up his page!
[Samsung Galaxy Nexus] MatthewPL:
Funny because only Samsung should do this. I want to this be "only" software bug and Google will soon fix it (and we all be happy) but I don't believe it. Only what I see is that Samsung doesn't care about it.

But! I will give whole month of beer for the first person who show me that Samsung cares (and they make new revision with hardware-fix) and show me shop where I can buy fixed version.
[Samsung Galaxy Nexus] bleets:
why should only samsung do that? if you havent noticed, it says "google" on the back of the handset aswell as samsung. and the phone was co-developed by the 2.

and it doesnt need a hardware revision since all phones will be susceptible to interference.
[Samsung Galaxy Nexus] MatthewPL:
Because Samsung make hardware? And Google adds only software? Google cannot fix this because it is hardware-bug? Ohhh... and because it is Samsung fault.

But OK, I will be happy with any solution better than new kernel or new bootloader - so everything that fix this bug in way that it will never-ever shows again in any case (including performance, battery life, etc).
[Samsung Galaxy Nexus] Nebucatnetzer:
Hmm they made a statement on their facebook page.

Several newspapers (at least in my country) and several websites wrote about it and they didn't deny it. I would say that's official enough.
[Samsung Galaxy Nexus] Hosh0:
I don't get why people think this is a band-aid fix? If it has no impact on user experience and next to no impact on battery life (I mean surely we are talking one cpu cycle here!) then who cares?? Do you really think this is the only place in the phone something like this happens?
[Samsung Galaxy Nexus] Fpad77:
The main problem here is that both samsung/google have exacerbated the issue by releasing the device to market with the issue, as well as not providing a timely patch to fix what is actually quite serious for those using the device in the UK (and other countries with the frequency). Not only does it demonstrate pretty appalling product testing and quality control, it also acts as a worrying indicator at what mess they're going to try and strap on to fix the issue.

Now that they've missed their golden opportunity, and let this drag out, I think its safe to say that people feel within their right to not want a 'bandaid' fix (which by definition will now be clear if it still occurs in the bootloader), again, if they'd snuffed out the issue quickly then all this wouldn't have come up, or made to be a bigger deal.

I for one feel let down that its taking 2 weeks to fix something so detrimental to the functionality and usability of the device, and any fix that gets put on better be ****ing perfect after this amount of time.
[Samsung Galaxy Nexus] bleets:
so...what you're saying is you'd have preferred to have an ultra rushed fix than something they're making sure is right before releasing? :) i see your logic!
[Samsung Galaxy Nexus] Fpad77:
Close but no; what I'm saying is that such a glaring issue should have not even made it to the market at all. It's called quality control.

And now we're in that situation, increasing its seriousness, the following should be applied:

- Good communication between both parties and consumers

- More detail on when to expect an update (rather than hearing it on the grapevine)

- Round the clock working to fix it

Do you see the logic!? :)
[Samsung Galaxy Nexus] Hosh0:
How does any of this relate to the point I was making about the fix not being a band aid one?

But anyway, the current communication method is EXACTLY what big comapnies should and do currently do. You simply acknowledge there is a fault and say a fix will be delivered soon, you never ever give a time frame due to people then getting upset that you missed it and that hurts the companies name more. Also how do you know they aren't working around the clock to fix it? I would also say 2 weeks is a pretty good turn around time.

I agree that it should have never made it to the market though.