[Q] Muffled Outgoing Voice Quality? - Atrix 4G General

I was just wondering for those that have the Bell version of the Atrix, how many of you guys are experiencing muffled outgoing voice quality?
I am so far on my second one and it is still muffled regardless of what noise suppression option I use.
I am thinking of exchanging for a third one but I'm not sure if I will just get another dud or not.
For those that do not have this issue, what is the manufacturing date on your Atrix? I think its that date on the side of the box. Both phones I have gotten had the date 3/1/2011.
Are there any possible remedies to this problem?

I am suffering from muffled call quality, but I'm on AT&T. Ive never had this problem on my other phones in the same exact area. I would like to know whether or not it effects all phones, and if I should exchange it.

Casing
My buddy bought an atrix the other day and he said he could hear me clearly out of my atrix but his was horribly muffled, but then I asked him what case was using, I had him remove the poorly designed case I think it was the bodyglove model,so if anyone is using a poorly designed case and they have this issue consider this variable. As soon as he took off the case his voice was perfectly clear and before it was muffled and unclear

I can only speak on behalf of my AT&T Attic experience, but im sure it is not too different in the voice quality issue.
This 'muffled' voice issue is a well documented and widespread issue. You may want to check out the motorola forums, where there exists a thread with hundreds of replies about this issue.
I experienced this poor call quality with 2 Atrix phones. Only on my second exchange (3rd phone), did I get a unit that did not suffer from the call quality issue. As a side note, turning off noise suppression did nothing to aleviate my call quality problem (as it might be suggested by some).
This issue has also been discussed in length here on XDA.
My advice, keep exchanging units until you find one that does not have the muffled call quality. (Talk about QC on Motorola's part!)
Good luck!

I guess I'll try exchanging for a third one and hopefully third is the charm.

I've had this problem intermittently since February 22nd. I kept it, thinking a software update would help. The last update did not help. Here's what AT&T did for me. Nothing. Because it was intermittent, I couldn't reproduce it on demand so they wouldn't warranty it. They wanted a hard reset, I had already done that and it didn't help so I refused to do it again. I have two of these and made it pretty clear the other one didn't suffer the issue. You gotta love these "scripted" calls where these people aren't allowed to use their brains and just provide some good old fashioned customer service.
So I had to send it back directly to Motorola for repair. That means no phone in the mean time.
AT&T should decide if they will warranty products or not. Pretty half assed experience. But I suppose I'll do better by sending it directly back to Motorola.
-James

I had the same problem done many test on with different cases and then done some researching after doing all that i found a setting on the phone. and it fixed it. Settings/ Call settings/ Noise suppression/ then choose off. i have done several tests with the 3 different settings and that seemed to fix it now everyone i talk too says they hear me clear again.

I have had this issue since I got the "phone". I say "phone" because it's basically unusable as a phone, unless you use speakerphone and hope they can make out what you're saying, good luck trying to give a chinese order. Took me 15minutes last night because my bluetooth headset was in the truck. I went through 3 different people trying to give my order to before one guy could FINALLY understand me after practically having to scream my credit card number at him 16 times. Once you pair a headset and use it however, it's fine.
There are hundreds of people complaining about this and Motorola just keeps telling people they fixed it in the latest update (two updates ago).
Do some google searches for "atrix call quality" and the like, you'll actually be surprised at how many people have returned phones and went with something else entirely. Getting a new phone does nothing to solve this issue for most people. Sadly, the majority of consumers don't realize their phones are affected and just chock it up to just phones generally being bad, not realizing how good it *SHOULD* sound.
EDIT: Forgot to mention I have an AT&T Atrix and bought it directly from them.

dosmac said:
I have had this issue since I got the "phone". I say "phone" because it's basically unusable as a phone, unless you use speakerphone and hope they can make out what you're saying, good luck trying to give a chinese order. Took me 15minutes last night because my bluetooth headset was in the truck. I went through 3 different people trying to give my order to before one guy could FINALLY understand me after practically having to scream my credit card number at him 16 times. Once you pair a headset and use it however, it's fine.
There are hundreds of people complaining about this and Motorola just keeps telling people they fixed it in the latest update (two updates ago).
Do some google searches for "atrix call quality" and the like, you'll actually be surprised at how many people have returned phones and went with something else entirely. Getting a new phone does nothing to solve this issue for most people. Sadly, the majority of consumers don't realize their phones are affected and just chock it up to just phones generally being bad, not realizing how good it *SHOULD* sound.
EDIT: Forgot to mention I have an AT&T Atrix and bought it directly from them.
Click to expand...
Click to collapse
Not all Atrix units are affected by this problem. I returned my phone twice and only on the third phone, did I not have any more call quality issues with the "muffled" sounding voice calls.
BTW, as a side note, the first two phones were from the same batch of phones(same store, etc..) The third, and finally usable one, was from a different batch.
My guess is that entire manufacturing batches came out with this problem.

wirednix said:
Not all Atrix units are affected by this problem. I returned my phone twice and only on the third phone, did I not have any more call quality issues with the "muffled" sounding voice calls.
BTW, as a side note, the first two phones were from the same batch of phones(same store, etc..) The third, and finally usable one, was from a different batch.
My guess is that entire manufacturing batches came out with this problem.
Click to expand...
Click to collapse
So, then this is looking more like them denying a quality control issue :/ great. Is it hardware causing this issue? Or just oversensitive noise-cancellation software? I don't think Motorola even knows.. haha

mudd_cat23 said:
I had the same problem done many test on with different cases and then done some researching after doing all that i found a setting on the phone. and it fixed it. Settings/ Call settings/ Noise suppression/ then choose off. i have done several tests with the 3 different settings and that seemed to fix it now everyone i talk too says they hear me clear again.
Click to expand...
Click to collapse
Thanks for the tip. Highly appreciated. Didn't know this was possible.

dosmac said:
So, then this is looking more like them denying a quality control issue :/ great. Is it hardware causing this issue? Or just oversensitive noise-cancellation software? I don't think Motorola even knows.. haha
Click to expand...
Click to collapse
I would venture to say that it's either hardware or a deeply rooted software issue. If it was just a SIMPLE software problem, then flashing different SBFs would technically get rid of the problem, maybe? Have you checked out the thread on the Motorola forums? It's insane.
Anyways, yeah. It's a major QC problem. I had other problems: 1. My LED flash would turn on, stay on for about 10 secs and then one of them would start flashing and eventually turn off. 2. Another problem with the phone's LCD behaving really erratically at different times of the day. 3. The muffled voice. All these are hardware problems that should not have made it out of the factory.

jmacdonald801 said:
I've had this problem intermittently since February 22nd. I kept it, thinking a software update would help. The last update did not help. Here's what AT&T did for me. Nothing. Because it was intermittent, I couldn't reproduce it on demand so they wouldn't warranty it. They wanted a hard reset, I had already done that and it didn't help so I refused to do it again. I have two of these and made it pretty clear the other one didn't suffer the issue. You gotta love these "scripted" calls where these people aren't allowed to use their brains and just provide some good old fashioned customer service.
So I had to send it back directly to Motorola for repair. That means no phone in the mean time.
AT&T should decide if they will warranty products or not. Pretty half assed experience. But I suppose I'll do better by sending it directly back to Motorola.
-James
Click to expand...
Click to collapse
Did you get your warranty replacement phone back yet? Did it fix the problem? I just sent mine in today to get warranty replacement, this better fix the voice problem...do not want to have to send another one back on my dime!!!

jank0023 said:
Did you get your warranty replacement phone back yet? Did it fix the problem? I just sent mine in today to get warranty replacement, this better fix the voice problem...do not want to have to send another one back on my dime!!!
Click to expand...
Click to collapse
Just got it in the mail. I'll report back in a few days. They did actually claim to have replaced two parts and sent back the same unit.
On the plus side, once they got it, it only took them 3 days to fix it and they fedexed it back overnight.
-James

One day after the repair. About 10 phone calls, none were garbled or suffered low volume on the receivers end. So far.
I think I'm glad I sent it back to Motorola for an actual physical repair instead of risking getting a refurb from AT&T that might possibly suffer the same issue.
-James

Hmm that's interesting. I have given up on getting new replacements after the 3rd showed the same problem. I may consider going the repair route.

yes, but on AT&T

Is anyone else still having this issue? I haven't made enough phone calls to realize the problem until now. I'm running on CyanogenMod so I don't have the noise suppression feature to turn off. Would they still repair an unlocked phone? I've been making more calls lately and it is driving me nuts.

Related

My Experience with Replacing the Nexus

Hi all,
This is not so much of a ranting thread (although I am really frustrated), but just a gentle reminder to please check your screen for dust, as well as any other known issues BEFORE rooting. Thankfully, I did that, and my phone had dust under the screen UPON arrival. I got it at 2pm, and returned it to HTC by 5pm.
The other problem is, do remember Google takes no responsibility with hardware related issues. As much as I hate it, find HTC. I had a horrible experience with them, and I just want to share it with the rest of you. Also, I'm from Singapore, just in case.
I got my phone at 2PM from DHL, and was really happy about it (who wouldn't)? I opened it, booted it, and it was really fast. Then I checked the screen. There was not one speck, but at least 5 specks of dust under the screen. I immediately called HTC Singapore's hotline, and it was outsourced to another country (I'm guessing China, cause when they called me back it was +86). I can speak Mandarin, but only barely, and it was really difficult trying to tell them my problem in English. They really tried to help, but the communication barrier proved to be very frustrating. In the end, I was told to go down to HTC Care (at Keppel Bay Tower) to return the phone.
At this point in time, I didn't really want to make a huge fuss or anything. **** happens, I can accept that. All I want now is my phone replaced, as quickly as possible. I reached HTC Care around 4.15PM, but was only served at 5PM. Even worse, the staff at HTC Care Singapore had NO idea what to do with the Nexus One. They told me it was dealt differently from other HTC phones. As a consumer, I seriously do not care. I just want my phone fixed/replaced/whatever. I then waited for 20 minutes while they tried to log into the Nexus One system of theirs or something.
As though that was not bad enough, they had no idea what to collect from me. Some of them said I should return only the phone, while others said the entire box set. In the end, I returned the entire box set. They did not even bother to check the contents inside. Also, the courier service used this time is M3 express instead of DHL, and I was not given any tracking number despite them telling me the order has already been placed.
Also, there were other discrepancies. The phone staff told me to expect it within 3 working days, while HTC Care staff said to expect it within 3 to 5 working days. To be fair to the HTC Care staff, I doubt they were even briefed on what to do with Nexus Ones.
Below is the email I've sent to HTC, although at this point in time I doubt the response will be good:
To whom it may concern:
I placed my order for Nexus One with Google on January 9, and finally got it today, January 15, at 2pm. I understand that weekends are not considered work days, so effectively it took 5 working days to reach, which is reasonable to me.
I opened the Nexus One only to find dust under the screen. Doing a quick search on Google shows that it is a common problem. In fact, I read on some posts that it is considered to be a DOA problem by HTC, as seen from http://www.google.com/support/forum/p/android/thread?tid=29bc1e80107f01f7&hl=en. The first thing I did was to call the Singapore HTC helpline. I had a hard time communicating with them, but they did their best to help. I was told to go down to HTC Care (Singapore) at Keppel Bay Tower. The person on the phone had also opened a ticket for me.
I reached Keppel Bay Tower at 4.15PM, and was only served at 5pm. The service staff were polite but very unsure of what to do with the Nexus One. Apparently, Nexus Ones are dealt with differently from other HTC phones, though I do not see the point of them informing me of that. I have already accepted that there is dust under the phone and instead of making a big fuss, my main aim is to get my phone replaced on a one-to-one basis since I am still within the 14 days.
Once the staff managed to retrieve my information using the ticket number given to me earlier by the person over the phone, I was told I had to return the phone, but they were unsure whether to collect the phone, or the entire box set. In the end, they collected the entire box set. I had been told to expect it within 3 days by the person over the hotline, but the staff at HTC Care informed me that it was 3 - 5 days.
I am now requesting that you replace the entire box set, and deliver it to me within 3 days. In addition, I would like to know why the courier service used
is M3 Express instead of DHL (which was used when I first got my Nexus One). Moreover, I was not given any tracking number to track the status of my delivery, despite the service staff telling me that the order has already been placed.
I find it disappointing that the service staff had no idea what to do with Nexus One cases. It seems to me that HTC does not care because it is not really HTC's phone and more like Google's phone in this case. I hope you understand where I am coming from. It is my first time dealing with HTC's service, and the experience has been a let down. I have always thought highly of HTC's products since my previous HTC phones were all well-built, and I never had to visit the service centre.
I will appreciate if you could get back to me by Monday.
My ticket number, as well as product serial number are as follows:
Ticket No.:
Phone S/N:
Thank you.
Regards,
Click to expand...
Click to collapse
To end it, please remember to check before rooting!
bro sad to hear this from you.
I also got my nexus one today and i notice the screen's bottom left and right corners are making loose noise when pressed with some pressure..
so i used some pressure on the problemic areas for 20secs and so far, no more loose noise..
Hopefully it will prevent my unit from dust..
I have been consistantly checking mine as well. This sucks
melterx12 said:
man now im really going crazy. it seems that everyone is having this problem. I cant seem to find any dust under the screen but what if im just not seeing it??? Whats the chance that my phone DOES NOT have this problem???
Click to expand...
Click to collapse
From what I understand, this is still a problem with a small minority of phones.
People who do not have this problem (as you might have noticed) are not going to be very vocal about not having it.
For the record, I have an N1 and have had zero problems whatsoever, screen or otherwise.
melterx12 said:
man now im really going crazy. it seems that everyone is having this problem. I cant seem to find any dust under the screen but what if im just not seeing it??? Whats the chance that my phone DOES NOT have this problem???
Click to expand...
Click to collapse
Mine doesn't have it either. If you can't see it, then why is it bothering you? Mine doesn't have jam (jelly if you're in the USA) in it either but I'm not going to keep checking for jam.
SC
ScaredyCat said:
Mine doesn't have it either. If you can't see it, then why is it bothering you? Mine doesn't have jam (jelly if you're in the USA) in it either but I'm not going to keep checking for jam.
SC
Click to expand...
Click to collapse
its bothering me because I REALLY want to root but REALLY will go out of my mind if I see this problem after rooting (because my warranty will then be long in the void ). So I want to track this problem down now and some how be 100% sure that my phone is safe.
Wow, this dust problem is become quite large. Small quantities doesn't sound like a good enough example of the problem. I don't have my Nexus One yet, but I do hope - that when I get it soon - the newer models (if they are starting to correct the issue) doesn't have this problem.
melterx12 said:
its bothering me because I REALLY want to root but REALLY will go out of my mind if I see this problem after rooting (because my warranty will then be long in the void ). So I want to track this problem down now and some how be 100% sure that my phone is safe.
Click to expand...
Click to collapse
Well, you either wait for the warranty to expire or you root it before.
If you're really that worried power it off and check it with a magnifying glass. TBH Right now there are 1001 reasons not to root it and only a couple of reasons to root it. Unless there's something you really need/want root for you may as well wait.
SC
I know, I am waiting for now, probably until Cyanogen Mod comes out for N1. However I do not want to wait a year
ScaredyCat said:
Well, you either wait for the warranty to expire or you root it before.
If you're really that worried power it off and check it with a magnifying glass. TBH Right now there are 1001 reasons not to root it and only a couple of reasons to root it. Unless there's something you really need/want root for you may as well wait.
SC
Click to expand...
Click to collapse
exactly i think one of the main reason i root my G1 was to apps2sd....and then some themes...but with this much RAM on the N1 i do not see a reason to root...
DKM119 said:
exactly i think one of the main reason i root my G1 was to apps2sd....and then some themes...but with this much RAM on the N1 i do not see a reason to root...
Click to expand...
Click to collapse
Theres more to root than apps2sd. For example, Internet tethering is a feature I really want and only possible through root.
Since we're talking about rooting here, I just wanna root to upgrade to un-released Android firmwares, themes, changing things inside the phone that aren't possible stocked. There are lots of reasons to root in my eyes, and I really don't care about the negatives.
kozm0naut said:
From what I understand, this is still a problem with a small minority of phones.
People who do not have this problem (as you might have noticed) are not going to be very vocal about not having it.
For the record, I have an N1 and have had zero problems whatsoever, screen or otherwise.
Click to expand...
Click to collapse
Same here. Zero problems with mine.
Also I don't plan to root until the S-ON/S-OFF issue is either resolved or root without unlock is discovered.
melterx12 said:
Theres more to root than apps2sd. For example, Internet tethering is a feature I really want and only possible through root.
Click to expand...
Click to collapse
yeah i undertand you point but is not for everybody...like myself i do have wi-fi at home and at work...so i never used the internet tethering....so for me when i rooted my G1 is was only for the apps2sd and themes....
melterx12 said:
Theres more to root than apps2sd. For example, Internet tethering is a feature I really want and only possible through root.
Click to expand...
Click to collapse
There are always alternative. Although not as elegant of a solution, PDAnet allows you to connect your phone to your computer so it can use your data connection. Works pretty well.
as someone who had to unroot and use the warranty on my rooted G1 like 11 months after I got it, I definitely will not root my N1 when I get it unless there is a way to revert to the full factory settings. I'm not a dev but I have faith they will figure it out though.
I woke up to find this thread now has 3 pages of useless conversation :|.
Anyway, if you take a torch and shine it it'll be obvious if there's dust on it.
I need root cause of Market Enabler and internet tethering. Will update this thread when I get a response from HTC.
That's a truly depressing story!
The warranty situation is the main reason I use to keep myself from buying this phone. Since I had a hardware issue with my G1 that needed to be replaced (stopped accepting USB input, so it wouldn't charge or transfer data), this is kind of a deal-breaker for me.
Not repairing hardware defects because of a software issue is complete bull****.
My contract comes due in November, hopefully by then, HTC will have changed their policy. If not, the phone I buy definitely won't be unsubsidized! I've had good luck just contacting tmobile and saying the phone broke. Since it doesn't work, I'll have to cancel my contract and pay the ETF.....in the past they've given me a good price on a replacement. This probably wouldn't work if I wasn't on contract with them.
I agree and some of these pointless posts have been reported, so please keep this thread on topic.
I have cleaned this thread up so please refrain from from spamming and flaming. (and will continue to do so!)
Greetz.
i may be sending mine in for a repair soon, i have a stuck/dead baby blue pixel.

Thoughts on why swapping Vibrant would solve issues?

Howdy...
So I have a dilemma...
First of all, overall I LOVE this phone, and have had very few issues with it. The only "issues" I HAVE had have been the "too-long-to-get-a-fix" GPS and the stuttering/inaccurate compass in G-Maps. Sure the occasional lag-spike but every phone gets that. I performed the GPS-fix and it gets a fix MUCH faster now... so I'm happy there. Only problem left is the stuttering compass.
Now my question... I've seen threads about how people have swapped their phones and fixed the issues... my question is HOW? Why would swapping make a difference? I doubt it's a "new batch" off the line, and it sure as hell isn't new software, so why the difference?
Any ideas? Thinking about doing this but not sure if it's worth it or if I should just wait and see about a potential software fix from Samsung.
I think people are just quick to assume. Its the same phone with the same firmware. I just swapped mine today and yeah the GPS and Compass worked fine at first. Now im back to the same issue. Same with laggin. I tried to not install a Task Killer and at first it was cool. But after about 5 hours of heavy use.....lagging was back. Installed task killer and now everything is cool.
SO in short....no swapping WILL NOT fix the issues.
I don't know why people are sure this works. If new phones were shipping with new software, it would have been released. I think, anyways.
Swaps of hardware would work for hardware defects if the manufacturing date is indicative of new hardware configs.
So I don't know. I'm going to call T-Mobile soon anyways. Their online chat isn't working for me at all.
You wouldnt think it would solve anything. I did a swap and both mine had the same date on the box but the second one is a bit better. It takes better night mode shots and loads quicker than my first one did out of the box. Perhaps I just had a faulty one to begin with. GPS does work better on my second one but not great and the compass is still wacky.
A swap really shouldnt fix anything but I figured why not, it's worth a shot. Worked out ok for me but I'll see in a week.
I have the home key issue and I think that swapping will help that. Seems to me that the handset has lower than normal build quality. Its possible that is why there seems to be such a difference in how the handset performs out of the box.
I am not sure why it might exactly help out with the GPS issue but guess what! I just swapped mine about 10 mins ago. It locks on near instantly now. Maps work inside my house as well so awesome.
Just to help clear up (you know, working in customer care at T-Mobile and all) the firmware on exchanged devices is Identical, so if you are having a software issue such as the several clearly discussed and posted issues, exchanging the device won't solve a thing, since the phone you will get is Identical.
You basically have two choices, either return the phone and wait for a firmware update, or enjoy the amazing phone until Samsung releases an update. (Mind this doesn't mean don't complain, by all means complain, make your voices heard, things get fixed faster if you voice your discontent.)
Since this is a flagship Samsung device and essentially is the only phone worth mentioning (including all variants) that they've had released for a while I'm sure they will support the device with timely updates. The thing is that they have to actually fix the problem, and test the fix on multiple devices, then they have to test the fix on a limited number of devices over the air, to make sure they aren't bricked, then they roll out a tiered update to all subscribers using the device, this takes at minimum a few weeks and on average 6-8 from my experience. More if your company is named Motorola.
They are usually pretty careful about this stuff especially since bricked phones cost the company a lot of money in exchanges. They want to get it right when they send the updates.
Aphotix said:
Just to help clear up (you know, working in customer care at T-Mobile and all) the firmware on exchanged devices is Identical, so if you are having a software issue such as the several clearly discussed and posted issues, exchanging the device won't solve a thing, since the phone you will get is Identical.
You basically have two choices, either return the phone and wait for a firmware update, or enjoy the amazing phone until Samsung releases an update.
Click to expand...
Click to collapse
A very reasoned analysis. But it does beg the question a bit by assuming that there is no hardware issue implicated as all or part of the root cause of the very serious GPS problem. Right now it is only speculation that a firmware update alone can solve this problem. Meanwhile, the clock is ticking.
It does seem that another option for a customer with defective phone is to return it for a refund during the 14-day period -- or the new 14-day period that resets with the replacement phone that still doesn't work right -- and wait to see what concrete solution emerges. Or just keep requesting replacements every 14 days until there is an actual fix.
I swapped mine because of a different issue but I will say that the gps worked extremely fast on the first boot. So I also assumed that the new phone made a difference, it however did not. The phone has begun to revert back to the slow gps signal grabbing. Only thing we can do is wait for an update, which is not good business if you ask me.
Sent from my SGH-T959 using XDA App
boodies-how is the accuracy of your location when it has a fix? What does Maps say about accurate to within X meters?
My opinion is that swapping doesn't fix the problem. I did an exchange anyway just in case, and I'm ending up with the same issues (plus, new phone has a loose volume key). Both phones worked fine at first and then the GPS started screwing up. I've also noticed that GPS works ok after a reboot, but I'm not going to keep restarting my phone so the GPS will work like it should.
Not sure if I'm giving up for now and waiting for a confirmation of the GPS fix before getting another one; or maybe I'll stick it out.
Keslynn said:
My opinion is that swapping doesn't fix the problem. I did an exchange anyway just in case, and I'm ending up with the same issues (plus, new phone has a loose volume key). Both phones worked fine at first and then the GPS started screwing up. I've also noticed that GPS works ok after a reboot, but I'm not going to keep restarting my phone so the GPS will work like it should.
Not sure if I'm giving up for now and waiting for a confirmation of the GPS fix before getting another one; or maybe I'll stick it out.
Click to expand...
Click to collapse
well hope you're wrong because so far with my exchanged unit, I can tell it locks on much much quicker and the accuracy goes down below 50m finally. It hovers around 8-9 meters so far. It will even lock inside the house where before it almost never did. maybe it's the exchange, maybe it's a reset that will do it. Either way, mine works now.
its in your head...
boodies said:
well hope you're wrong because so far with my exchanged unit, I can tell it locks on much much quicker and the accuracy goes down below 50m finally. It hovers around 8-9 meters so far. It will even lock inside the house where before it almost never did. maybe it's the exchange, maybe it's a reset that will do it. Either way, mine works now.
Click to expand...
Click to collapse
Does it stay working, or does it start to crap out after a while as some have reported?

Major Galaxy S II issue that needs to be brought to light!

Hey everyone, I know this is going to be a lengthy post but do please read on and feel free to post your thoughts.
Here's the story... I have had my Galaxy S II for 4 weeks now and every phone call I have made & received has been problematic. Everybody I spoke to was complaining about poor quality, an echo to be more specific, they reported their own voice was being echoed back but the call is always fine on my end. What this means is the call is almost impossible to hear for the other person and they end up calling me back on another phone, its driving me mad and it really is a big issue so I decided to get it exchanged with the company I got it from (Dial-A-Phone). I only arranged the exchange today so I have to wait 3 - 5 days for the bag to arrive to post it back in.
In the meantime I was looking online to see if anyone else had this problem and I can across a thread on AndroidForums (Can't post a link here because im a new user). So it looks like it's not just me its actually a lot of people and seems like it's most Galaxy S II's! Reading the posts on the thread its clear to see that the problem only exists when a case is on the phone and that is exactly what I have been finding (I have a CaseMate Gelli).
So this is now making me think exchanging it will be pointless as the new unit will most likely be exactly the same... I did some more looking around and was pretty shocked to find how many people have this issue. I simply searched Google for "Samsung Galaxy S2 call echo" and there are a lot of results, they are all the same issue just on different forums and posted by many different people.
So my options are as follows: Not use a case which I don't want to do because I want to protect this expensive phone, take it out of the case everytime I get a phone call but that is not practical in any way! people have also said to turn off Noise Reduction when a call connects but again I don't want to have to hit "Menu" > "NR" everytime I answer or place a call! Other people say that putting tape over the Noise Reduction mic and cutting bigger mic holes in the cases makes the problem better... But once again I should NOT have to do this! I should be able to use the phone with all functions normally with a case as protection, especially as this is one of the best phones of the year, costs about £500 and none of the other brands such as HTC have problems like this!
A friend of mine who also has this issue showed me an Amazon.co.uk case review entitled "The FACTS about the Galaxy S2 echo problem & the Case-Mate Tough Case" (Again; Can't post a link) but another person who has had the issue and Samsung even tried to cover it up by discontinuing their own case because it was uncovering a problem with their flagship phone.
Anyway that's probably enough on the subject but I just thought this needs to be brought to people's attention and I am also stuck on what to do, As I said I should not have to do any silly workarounds or not use a case, and exchanging it is 99% certain to be pointless... All I can think of is get the replacement phone brand new, don't open it and sell it on eBay brand new then buy a different phone like a Galaxy Nexus for example. But it does annoy me because I love the Galaxy S II, it's a great phone in every way, its just this that ruins it.
Finally, what do you guys think I should do?
Thanks for reading this and feel free to contribute, I just think this needs to be brought to light instead of just secluded in various forums, afterall, its a phone and if the phone calls are useless it's not going to be very good for many people.
You really should search the SGS2 threads before posting. This issue is old news and if you search you will find tweaks to solve the problem.
Edit: But if you reply you will get your post count up a bit
I never had this problem since i bought it, but it's a scary thought since i am doing a lot of calling with it.
I just talked to my G.F. she said my voice comes threw like butter, no problems on any end.
But i do use a plastic casing for my Sgs2, maybe the metal case that you use is the problem my friend, why not try the plastic one's?.
Can't speak for anyone else, but I've had absolutely no issues with call quality either on my end or the person I've been speaking to. None of my friends who have a SII have complained about it either.
Now it may seem like a lot of people are complaining on forums, but Samsung have reportedly sold 10 million units according to an article on Cnet in October. How many complaints have been made in comparison to that number? I doubt it will be as high as 0.1%. So to claim that it "seems like it's most Galaxy S II's!" is a bit over dramatic. Have you really seen about 8 million (that to me would roughly equate to most), different users on one forum? Keeping in mind that it probably the same people moaning on the different forums.
Personally I'd say go for the replacement, the SII is by far the best phone I've ever had. Yes like any electronics there's going to be issues, but I'd be willing to bet the call echo issue is for a small minority of handsets.
I use the samsung official case, vented back cover, not the best protection but i never mess with noise reduction, volume on my end is normally set half way (otherwise the whole world can hear both ends of my conversation) and it has worked perfectly fine, clear as crystal since day 1.
After getting a drink spilled on mine, and subsequently replacing the charge port PCB which also houses the microphone and speaker connectors, i can tell you that there are clear variations in hardware, although minor, still significant enough to potentially be a problem.
It may be totally unrelated but if you search general for "charge port problem" you can see the discussion on different hardware revisions.
Failing that, the easy test is to try this without your case on, also try lowering speaker volume during call and try even blocking the NR mix hole, if nothing fixes it, then its clearly a hw problem and so should really be replaced by Dial A Phone or Sammy.
Sent from my GT-I9100 using Tapatalk
ajh94 said:
So it looks like it's not just me its actually a lot of people and seems like it's most Galaxy S II's!
Click to expand...
Click to collapse
Yep, i agree. Quite cleary most GS2s are faulty because some people have mentioned it on a forum. Nevermind the other 10 million people that havent. Lets generalise anyway
As mentionned, old news. Workaround posted on multiple threads. Alot of people just deactivated noise reduction in the dialer... Next caller please!
skimminstones said:
Yep, i agree. Quite cleary most GS2s are faulty because some people have mentioned it on a forum. Nevermind the other 10 million people that havent. Lets generalise anyway
Click to expand...
Click to collapse
^^^^
This.
And I've had my SGS2 since May and also use the Case-Mate Tough Case. But thanks for bringing this major issue to light that appears to effect you and maybe three other people.
BarryH_GEG said:
^^^^
This.
And I've had my SGS2 since May and also use the Case-Mate Tough Case. But thanks for bringing this major issue to light that appears to effect you and maybe three other people.
Click to expand...
Click to collapse
LOL! Yeah dude, I've been using the phone for 7 months now, no issues of this sort at all. Had a hard case, moved to a soft case a few months later (it was a gift) and all my calls have been fine
ajh94,
So you have eliminated the possible issues originated from the network operators?
No problem here, too.
Yeah I have the same problem but seem to have mostly fixed it.
I removed the rubber housing the microphone as it seemed to be blocking the hole and made the microphone hole larger by wedging a small screwdriver in it.
But I agree with some of the other posts, there are ship loads if threads on this topic. I have posted specifics of my fix on one of them.
Sent from my GT-I9100 using xda premium
Wasn't aware of this problem at all.
Had mine since May, been using a Casemate "Barely There" since September, no problems at all here.
OMG.... my SGS-II must be faulty as I didn´t receive any complaints from my callers since I got my SGS-II in May
skimminstones said:
Yep, i agree. Quite cleary most GS2s are faulty because some people have mentioned it on a forum. Nevermind the other 10 million people that havent. Lets generalise anyway
Click to expand...
Click to collapse
not being funny but do you think everyone who owns phone looks at forums reports problems or even notice them. Example nice lady where i work thought her sII was perfect, I looked at it showed her pink spot and yellow tint on screen she hadent noticed and wasent that bothered tbh but point being it was there yes its wrong to generalise but arent you doing the same ?
tonnytech said:
not being funny but do you think everyone who owns phone looks at forums reports problems or even notice them. Example nice lady where i work thought her sII was perfect, I looked at it showed her pink spot and yellow tint on screen she hadent noticed and wasent that bothered tbh but point being it was there yes its wrong to generalise but arent you doing the same ?
Click to expand...
Click to collapse
So a nice lady showed you her new phone to you and your natural reaction was to show her "faults" with the phone that she hadn't even noticed?
Let's make sure we eliminate the network operator before creating such bold statements as "major issue". I know tons of people that own this phone at not any of them have reported this issue. Trust me, I'd here about it if there was one.
Sent from my GT-I9100 using xda premium
So is there a fix for this? Because my phone does the same thing when i receive and make calls. I know someone said to lower to noise.reduction on the dailer. But no clue where to find or how to do that. Thanks.
Sent from my GT-I9100 using XDA App
Solutions:
- Send it to the service center, they should replace the mic with a newer revision.
- Disable Noise Reduction. It's only available during a call and cannot be disabled permanently (Unless phone is rooted, see below), so you have to manually disable on each call.
- You can disable it permanently if your phone is rooted, by using VillianTweaks 1.3.1. There is a fix by LeoMar that supposedly work.
- Use a cover that doesn't cover the top and bottom sides. I've heard that the Case-Mate Barely There cases work, haven't tried it though.
Check this thread for more details.
I have the same problem and my phone is currently at the Samsung service center, though they seemed clueless about the problem so I'm not holding my breath.
tonnytech said:
not being funny but do you think everyone who owns phone looks at forums reports problems or even notice them. Example nice lady where i work thought her sII was perfect, I looked at it showed her pink spot and yellow tint on screen she hadent noticed and wasent that bothered tbh but point being it was there yes its wrong to generalise but arent you doing the same ?
Click to expand...
Click to collapse
Thats my point. Do you think of the 10million GS2s sold that they all have a "major fault" because of a few people mentioning it on a forum?
The vast majority of mobile phone users dont use forums to either report a fault or not to. Using a forum as proof of anything is ridiculous.
If there was a "major issue" do you not think it would be all over the news with 10million units sold? How many of the new nexus phones were sold before the volume bug was reported everywhere?

RMA'd 2013 Nexus 7 for multitouch issue, nothing was fixed.

So I was having the multitouch issues.. putting two or more fingers closely together caused major freakouts, and some swipes would just count as taps, as well as phantom taps happening. I RMA'd. got it back, only to find out all they did was a factory reset, which I had already done. Obviously this did nothing to fix the problem. I was very angry. I went to Asus support and did a chat with a support guy ( trying to remember this is not his fault ) and politely stated that the RMA had done nothing. I set up a new one, explaining that it is a hardware issue and that I wanted the screen/digitizer to be replaced. I'm sending it tomorrow, so I'll let you guys know how that goes. Has anyone else RMA'd for this and gotten it back in perfect working condition?
WackyClash said:
So I was having the multitouch issues.. putting two or more fingers closely together caused major freakouts, and some swipes would just count as taps, as well as phantom taps happening. I RMA'd. got it back, only to find out all they did was a factory reset, which I had already done. Obviously this did nothing to fix the problem. I was very angry. I went to Asus support and did a chat with a support guy ( trying to remember this is not his fault ) and politely stated that the RMA had done nothing. I set up a new one, explaining that it is a hardware issue and that I wanted the screen/digitizer to be replaced. I'm sending it tomorrow, so I'll let you guys know how that goes. Has anyone else RMA'd for this and gotten it back in perfect working condition?
Click to expand...
Click to collapse
Yes, me too, my N7 was returned to Amazon yesterday :crying:
unfortunately, I couldn't find any tablet like N7 spec and price.
sauofee said:
Yes, me too, my N7 was returned to Amazon yesterday :crying:
unfortunately, I couldn't find any tablet like N7 spec and price.
Click to expand...
Click to collapse
My device only exhibits some multitouch jumpiness when not grounded. I decided to wait for Asus and Google to sort it out internally and then I will send it for repair. Now from what I heard they only replace one faulty units with another. Mine seems to be one of those better ones even though it has serious problems with basic pinch to zoom gestures when ungrounded. I keep it for now because I do not want to risk replacement with a worse one.
One question to the those of you who got a replacement. When you got your replacement devices what was the manufacturing date? Did anyone get a device from September production batch? Was it any better?
I just mailed mine in for repair yesterday. I was hoping this would resolve my screen issues but I'm getting the impression that I will be very lucky if it does.
Plan B will be to buy another one and return the first one with that receipt. Rinse repeat until I get one that works.
Sent from my Nexus 7 using Tapatalk 4
gadzooks64 said:
I just mailed mine in for repair yesterday. I was hoping this would resolve my screen issues but I'm getting the impression that I will be very lucky if it does.
Plan B will be to buy another one and return the first one with that receipt. Rinse repeat until I get one that works.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
So annoying that's what you have to do just to get one that works. Asus..... I don't know why they didn't just go samsung or htc, as badly as asus fudged up QC on the 2012 N7
I just mailed mine in for repair today, I don't know if I did right. Mine is also from the best ones between the bad ones and I don´t want to get one in worst conditions. I know a guy who send it to asus and got it back with the screen, front and gps changed, they did not even talk about the gps or gps problems at all, so we thought it was solved because they knew what to change. When he got it back at first it was perfect, he use to had a realy faulty unit, but the next day he came saying that it was failing again, much less than before but not perfect at all. He keeps talking with the people on asus and they told him to send it back, that may be an app... ???? I guess they don't have any idea on what the problem is.
bokoy said:
He keeps talking with the people on asus and they told him to send it back, that may be an app... ???? I guess they don't have any idea on what the problem is.
Click to expand...
Click to collapse
Yeah, the app is called JSS15* OTA update.
sfhub said:
Yeah, the app is called JSS15* OTA update.
Click to expand...
Click to collapse
There is a problem with that solution, I have the grounding issue, how could just a software problem do that? Mine works nearly perfect in my hands but if you put it over a sofa... Could be a software problem with some apps but not all.
The 15x updates contained firmware (which effects the hardware) as well as software.
Sfhub's firmware patches have been 80-90% successful in minimizing or eliminating the touch problems for those who've tried them.
He knows what he's talking about.... :thumbup:
gadzooks64 said:
Plan B will be to buy another one and return the first one with that receipt. Rinse repeat until I get one that works.
Click to expand...
Click to collapse
So in essence, commit fraud?
Apparently.
Sad that the sellers have to take it in the shorts because Google/ASUS are so clueless and unable to provide anything remotely resembling customer service.
They'll end up with a bunch of money tied up in defective stock that they'll have to sit on until they get credit.
Next time, how many Google/ASUS tablets do you think they'll be ordering?
goofball2k said:
So in essence, commit fraud?
Click to expand...
Click to collapse
Are you from the police? Is that fraud? So how would you call what asus/google are doing...
I think people that buy a device and return defective units to the place of purchase are heroes. Especially if they return 3-5 or more. They beta test the devices, and take out the bad ones for the rest of us.
Is it fraud to buy model ABC and return model ABC to the same store? The stores have a ASUS wonderful warranty program where they can return the devices for a full year for repair and resell them to unsuspecting customers. For example, I noticed Best Buy selling a Google device recently at full price that had an extra small sticker - Bug Fix A. Isn't that fraud? LOL
Seriously, it should be fraud to sell a consumer faulty devices and expect thousands of customers to deal individually with the known problems.
Even if you buy one in one shop, then buy another in another, or the same shop, and return the first one as the second, that is what the user said. If that's the way to get a good one working... but be careful with bar codes, they will know you are not returning the same item.
There's no damage for any shop as Bob said, they just return the unit and gets new one. The biggest problem is for the user, Google is just lucky for not having more returns.
They are are all screwed up I think. Some more then others. It can be fixed with Sfhub's patches for the most part. Mine still gets strange when I play extended periods of Terraria but it is only for a second or two. I don't even think it is the device at this point but rather the game itself.
Best thing to do is go into Dev options and turn on show touchscreen inputs. Before it would skitz out and I could see like 5 touch inputs randomly on the screen. Now after Sfhubs fix, I don't see any, even when the game gets wonky.
This is why everyone knows it can be corrected via a proper patch from Google. Whether they adjust the sensitivity to touch or grounding or whatever. If Sfhub can do it, Google can. Plus it is a tiny download, his directions are precise, you don't have to be unlocked or rooted to do. There is absolutely no harm to just patch it yourself until Google makes with a fix.
Touchscreen Patch Fix:
http://forum.xda-developers.com/showthread.php?t=2428133
player911 said:
They are are all screwed up I think. Some more then others. It can be fixed with Sfhub's patches for the most part. Mine still gets strange when I play extended periods of Terraria but it is only for a second or two. I don't even think it is the device at this point but rather the game itself.
Best thing to do is go into Dev options and turn on show touchscreen inputs. Before it would skitz out and I could see like 5 touch inputs randomly on the screen. Now after Sfhubs fix, I don't see any, even when the game gets wonky.
This is why everyone knows it can be corrected via a proper patch from Google. Whether they adjust the sensitivity to touch or grounding or whatever. If Sfhub can do it, Google can. Plus it is a tiny download, his directions are precise, you don't have to be unlocked or rooted to do. There is absolutely no harm to just patch it yourself until Google makes with a fix.
Touchscreen Patch Fix:
http://forum.xda-developers.com/showthread.php?t=2428133
Click to expand...
Click to collapse
Correction - "Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies"
That is extracted from his post.
So no one's had a positive experience RMAing the nexus? Do the majority of units have the multitouch problem?
Sfhub's fix helped but I still get the "grounding issue" where the touchscreen goes insane if I place the nexus on certain materials. It sometimes exhibits the same problem when connected to the charger.
Other than that, the tablet works great when I hold it in my hand, no other issue to report... so I'm worried about RMAing my N7 and getting back one that not only has the same multitouch issue but now also randomly reboots or has dead pixels or dust or whatever. My warranty applies to north america only because I bought it off ebay and I don't live in the US so shipping it off to get replaced will get costly if I can't guarantee I get a working replacement back. Can I be sure that like, the newest batch of nexus 7 has been fixed and the replacement will be of that batch?
Since they're not sure what the problem is (one Google groups poster states that ASUS has had his for a month with no ETA on a fix, or when he'll get it back) I'm not sure how they can fix anything , or be certain that what they've been shipping is 'good'.
https://productforums.google.com/forum/#!topic/nexus/mG4JXaT-SHs[1-25-false]
Come and join in the fun.... :/
Looks like loads of fun. Seems I should be grateful I was lucky enough that my touch-based tablet only has a malfunctioning touch screen.
danvee said:
Since they're not sure what the problem is (one Google groups poster states that ASUS has had his for a month with no ETA on a fix, or when he'll get it back) I'm not sure how they can fix anything , or be certain that what they've been shipping is 'good'.
https://productforums.google.com/forum/#!topic/nexus/mG4JXaT-SHs[1-25-false]
Come and join in the fun.... :/
Click to expand...
Click to collapse
Dude, that forum is almost like spam. I reported my issues early, 3 weeks ago or more.
Since then I get from 10+ to 20+ reports (of multiple posts) per day of people reporting issues in email. People might be worrying about me when I get two or three reports in one meeting and I'm chuckling at the comments. LOL
Seriously, it is a good idea to report your issues at that location. But, think twice about subscribing to the topic.

I am very disappointed with Google

To whomsoever it may concern. Yes that's what my state of mind is right now.
I will begin from the beginning then.
So heard on 4th October 2016 that google is launching it's Pixel phones. Couldn't have been more excited with the news as I am a big android fan boy. I had been using the Nexus 6p then, so the news of the Pixel phones was really pleasing to me.
I wait for the Pixels to get launched in India. 26th October 2016 is the date. I pre-order my Pixel XL very silver 128 GB before hand and receive the handset on 26th! Very happy!!
I haven't ever used a better phone than the Pixel XL. The smoothest android experience. Period.
So a month passes by. The phone does overheat from time to time but other than that it worked fine. My "rock solid" Pixel XL gets about 40 GB full. One fine day, while I was trying to open a PDF from my drive, the device freezes and reboots. Nothing to worry, sometime android does that, I think to myself. Same day, Gmail freezes and the phone reboots. Then the Camera freezes and it reboots. Now I started to see a pattern. Tried uninstalling apps one by one, to pin point the root cause. Found nothing. Tried Safe Mode. Still it would freeze and reboot. Finally, made my peace with a factory reset. The phone started behaving. I told myself that I must be some rogue app.
This cycle continues again when the phone reaches that 40 GB mark. It would freeze and reboot. Factory reset once again. It works fine.
So I start suspecting the phone internal memory. I fill up the around 80 GB with random videos and music. The restarts start happening like clockwork.
Come 6th December 2016, and I receive the 7.1.1 update. Everything goes smooth. The phone acts normal, for sometime at least. I call up Google Support on the 8th and the guy tells me to take my phone to the service center.
Moments after, I see my phone restarting. It boots up and it's sitting on my table. In about five minutes, while lying idle on the table, it reboots. And this time, it reboots to boot-loader. I try to start the phone with the power key and the volume keys by choosing the right option. It boots back to boot-loader. Doesn't load up android. So somehow my phone was soft bricked just sitting idle on the table.
I am not new to the fastboot mode and decide to flash the stock rom. However, there is this issue that i suddenly see. The fastboot screen on my phone says Baseband : N/A and my bootloader is locked! The only option I see to get android up and running is using stock recovery and sideloading the Stock ROM, which should have worked as Google Stock ROMS are signed and might have not need unlocked bootloader(I did my research). I select recovery, and surprise surprise! The phone says recovery can't be loaded, press any key to go back!!
So now my phone has no OS, no baseband, no recovery with a locked bootloader! And i don't know how it happened!
I take the phone to the service center today around 11 am. They can't make sense of what happened. They say they would keep the phone for sometime. I get a call from them around 4, which was like half an hour back. The guy tells me there is a power button issue and another hardware issue(which he doesn't specify) and tells me they will keep the phone for 2 days. And repair it!
WHAT!?! WHY THE HELL ARE YOU REPAIRING MY PHONE GOOGLE!?! It's a new phone, not even 2 months old! And it doesn't come cheap! For the price amount I would expect it to work flawlessly!! I ask the service guy for replacement unit, and he says it is more than 14 days old, and gives me all terms and conditions! The problems that I had with this phone couldn't have been foreseen!! Till the time the internal storage gets to about 30 percent full the restarting issue did not show itself.
I expect a replacement unit or a full refund. Because this is just not fair! Not really happy with you Google. Thanks!
P.S.: thanks for reading this.
TL;DR
Cliff notes?
I am not getting it! You mean that the phone you had, had no hardware problems? So if its software only, then why did you submit the phone at service centre at first place? And in case they are offering you a repair service, or a new phone, what is the problem with that? From the sound of it it does sound like a hardware problem anyway, repetitive problems are never software. In fact you should be rather thankful that they accepted the phone and offering you a free service, cause a lot of reviews say that HTC service centre is asking money for a phone which is just one month old and sorts like that.
And you probably are one unlucky fella where the phone might have come with a hardware problem, cause most seem happy with theirs anyway. I am not defending Pixel or its ridiculous price point anyway.
Honestly what's the difference? If they fix it and it's working again then it should be no different than a new unit. unless you've damaged the device and wanted to get a new one with no damage I don't understand.
So if you get a new car from a dealer and it has an issue you would demand a new car instead of letting them repair it? Sounds pretty dumb to me.
Sent from my Pixel XL using Tapatalk
Guarantee this is caused by a bad memory chip. The only way to fix it is to replace the chip (which I highly doubt can be done at a service center) or the motherboard. I had a Nexus 4 that had the same issue. Eventually I could not even write a new system image at all.
At least demand a written explanation of what was done to correct the problem so if it continues after being repaired you can demand a new unit. If they are replacing the board you should be good to go.
So you are angry that Google are fixing the device for you at no charge to yourself? Things go wrong sometimes, sounds like Google are looking after you nicely.
You will get your phone back in the same condition you gave it to them - with the issues resolved.
Or
If they can't fix it, they will replace it.
What's the issue?
Mdizzle1 said:
So you are angry that Google are fixing the device for you at no charge to yourself? Things go wrong sometimes, sounds like Google are looking after you nicely.
You will get your phone back in the same condition you gave it to them - with the issues resolved.
Or
If they can't fix it, they will replace it.
What's the issue?
Click to expand...
Click to collapse
He wants a new phone. I understand. From my experience when things like this go wrong like this they keep going wrong. It is a phone not a new car. I am surprised they did not give him a new phone and call it a day.
johnciaccio said:
He wants a new phone. I understand. From my experience when things like this go wrong like this they keep going wrong. It is a phone not a new car. I am surprised they did not give him a new phone and call it a day.
Click to expand...
Click to collapse
Agree
Pretty sure that the NAND chips are faulty. That is why after that chip gets written with data, phone starts to act up.
It may not be easy to replace just the faulty chip. Either they will replace the whole logic board or give you a new piece.
ithehappy said:
I am not getting it! You mean that the phone you had, had no hardware problems? So if its software only, then why did you submit the phone at service centre at first place? And in case they are offering you a repair service, or a new phone, what is the problem with that? From the sound of it it does sound like a hardware problem anyway, repetitive problems are never software. In fact you should be rather thankful that they accepted the phone and offering you a free service, cause a lot of reviews say that HTC service centre is asking money for a phone which is just one month old and sorts like that.
And you probably are one unlucky fella where the phone might have come with a hardware problem, cause most seem happy with theirs anyway. I am not defending Pixel or its ridiculous price point anyway.
Click to expand...
Click to collapse
It is a hardware problem only, the phone worked fine till the 40 GB or so mark. And yeah, seem to feel unlucky about this now.
Also, I am not bashing HTC for this, they were pretty nice and they are doing their job. I understand that. Just not happy about the situation I am in that's all.
superchilpil said:
Honestly what's the difference? If they fix it and it's working again then it should be no different than a new unit. unless you've damaged the device and wanted to get a new one with no damage I don't understand.
So if you get a new car from a dealer and it has an issue you would demand a new car instead of letting them repair it? Sounds pretty dumb to me.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I wish i would have damaged the device just so that I would have something to blame this on.
And as for the car issue, you would want a new car, won't you? They will indeed repair it, however, a customer asking for a new car which works doesn't sound dumb to me.
johnciaccio said:
Guarantee this is caused by a bad memory chip. The only way to fix it is to replace the chip (which I highly doubt can be done at a service center) or the motherboard. I had a Nexus 4 that had the same issue. Eventually I could not even write a new system image at all.
At least demand a written explanation of what was done to correct the problem so if it continues after being repaired you can demand a new unit. If they are replacing the board you should be good to go.
Click to expand...
Click to collapse
Thought as much. Thanks for reading the long post!!:good:
sanke1 said:
Pretty sure that the NAND chips are faulty. That is why after that chip gets written with data, phone starts to act up.
It may not be easy to replace just the faulty chip. Either they will replace the whole logic board or give you a new piece.
Click to expand...
Click to collapse
The problem is when they eventually return the phone, it would be hard for me to understand if the problem persists until I get a PC in front of me and fill up the device. And the problem is pretty random too. Thanks for the reply though.
No problem. Been in similar shoes. You are not getting anything for free here.. It is one of the most expensive phones out there and you paid for a new device. Not one that has been reopened after being assembled. Check it carefully for scratches after getting it back.
I do not even like my car being worked on. Nothing is as perfect as when it comes from the factory.
dc/dc said:
TL;DR
Cliff notes?
Click to expand...
Click to collapse
Got a faulty Pixel XL, issue with the logic board(based on what i have read on this discussion so far), not really happy with HTC opening my new phone and repairing it. I paid for a new phone and I want a new phone which works! I know I am whining a bit.
johnciaccio said:
No problem. Been in similar shoes. You are not getting anything for free here.. It is one of the most expensive phones out there and you paid for a new device. Not one that has been reopened after being assembled. Check it carefully for scratches after getting it back.
I do not even like my car being worked on. Nothing is as perfect as when it comes from the factory.
Click to expand...
Click to collapse
You read my mind!! Totally agree!!:good:
At least it will be fixed. I purchased my Nexus 4 from a reseller so Google refused to warranty it even though it was completely sealed and new when purchased. Google hates resellers, which I understand the reason, but it is not a good policy to have.
johnciaccio said:
At least it will be fixed. I purchased my Nexus 4 from a reseller so Google refused to warranty it even though it was completely sealed and new when purchased. Google hates resellers, which I understand the reason, but it is not a good policy to have.
Click to expand...
Click to collapse
It surely is not a good policy to have. And with the pixel devices the resellers were a part of the launch process. It was not like we had to wait for a few days after it was available online. It was almost the same time. I hope i get my device as soon as possible in working condition, because as I mentioned earlier, I love the phone. Also I have been using a prehistoric Nokia 1100 which I found in some corner of my house as I don't have any other back up device currently.
I'm just impressed that Google had a service center in Bangalore.
Yeah sucks. Let us know how it goes.

Categories

Resources