Related
Hello all:
I am on my first replacement phone, and am experiencing a recurring problem that I also had on my original phone. At times during the call, the person on the other end will not be able to hear me (a la 'mute'), but I can hear them. I have confirmed that the mute function is not activated (even turned it on then off), but no luck. My initial impression was just a faulty microphone/hardware, but given that my second phone is also experiencing then same problem, I wonder if it is something that I am doing. I can assure you that I am not in any way blocking the microphone hole at the bottom of the phone (experimented with that to see if it was the cause). I can also rule out network issues due to moving between cells - I have experienced this problem driving and sitting still at my desk.
This problem, more than the GPS issue, will be the deal breaker for me - this is a business phone and I spend a substantial amount of time every day on work related calls.
Thanks in advance.
Thomas
I have the same issue. My coworker had the same issue with his the replacement under warranty.
If I use the headset it works fine. If I mute the phone and un-mute it it starts working.
Something is fishy with the microphone of this model ...
Okay, now this is getting ridiculous. Either I have really bad luck, or I am doing something wrong. On my second replacement phone, and like the last two, I have problems with the microphone cutting out during the middle of calls. Am I completely alone, or am I just lucky in getting phones with bad mics?
I keep the phone in my pocket with a body glove case. The mic is not plugged up, and it seems random. Could there be a software issue (ie a piece of software interfering and taking over the soundstream from the mic)? Even though the person on the far end cannot hear me, I can hear them.
Thanks
T
@ banesong: I'm having similar issues. I've had my phone for a little more than 24 hours. last night i couldn't hear anything coming from my mic and obviously could not communicate from my end. taking the battery out and back in fixed it for me. but i look at this as only a temporary solution. hopefully this isn't a hardware issue
I am having the same issue. I've had my Captivate since the end of July and it is running stock 2.1 that came with it and unrooted. I can't remember when the issue first started. But it has been doing it a lot more lately. It seems to happen around 8 or 9 minutes after I am on the phone call. At first I would hang up and just call back. Then I discovered that the mic would start working again if I just turned the speakerphone on and then off again.
It is really starting to get annoying now. I am thinking about getting a warranty replacement. The only reason why I didn't get a warranty replacement sooner is because I don't feel like having to remember and reinstall all the apps that I have on my phone now.
Having the same issue here and I have an idea about the problem.
If you remove the lid on the back that covers the battery the microphone is disabled and no warning appears on the screen. This is the same behaviour we are all experiencing.
There are two round blank spots on the inside of the cover matching two contacts on the phone. My idea is that the 'lid open' detection checks if the lid connects these two contacts.
My microphone usually starts working when I squeeze the phone.
Not sure about a workaround yet but connecting the two connectors directly inside the phone should solve it permanently (but voids the warranty).
Hope that helps.
T
Sorry, please ignore my previous message. I couldn't reproduce it yesterday so it must have been coincidence.
However, I have the same microphone problem and would like to know if there is a fix for it.
Cheers
T
Possible fix
I know this is an old thread but I have one of these old phones and was having this problem. After fiddling with the settings a bit I found a setting under Call Settings->Voice Call->Noise suppression. I unchecked the box and the mic seems to be working - for now.
Hi Guys,
Just got my phone replaced because the screen was sometimes unresponsive when layed flat on a surface.
Now I got a problem with the rear facing camera. When I open the camera app the auto focus doesn't always work. As result I get very blurry photo's
I made a short video to show you guys the problem:
Can you guys tell me if this could be a hardware or software problem. I performed a hard reset and reboot but the problem still occurs from time to time.
Ps. I didnt drop my phone and I removed the plastic of the camera lens and led flash, so that cant be the problem.
Since the problem cant be solved with a hard reset, I guess it's a hardware problem. So I contacted my carrier and I will get a new phone. Hopefully this time a phone without problems/bugs.
I will keep you guys updated.
I have that problem too, shaking the phone unlock the focus. It seems to be hardware problem, using the manual focus in pro mode change nothing, only way to fix it for me is wait like 30 to 60s or shake the phone.
I try to get a replacement but obviously, it works perfectly the two times they check :silly:
I had the same problem in the store like you. When I wanted to show the problem to a shop assistant, the camera worked perfectly :silly:
But (thankfully) they believed me and one of these days I will get a replacement because they didnt had any in stock to give me right away.
Maybe you can show them the video on YouTube and tell them that there are more people with the same problem?
I think I will keep it like this for now, and I will ask for a replacement just before the warranty end, so I will have a new phone ^^ I'm used to it now, if it bug, I just shake it and all is fine.
Yeah that would be great. Only I'm afraid that here in the Netherlands the phone will be send to get repaired instead of getting replaced. Only in the first two months i can get it replaced, at least that is what the T-mobile shop assistant said to me.
One of my friend has the same issue. She figured out that she "just" needs to hit the phone on its front top left corner (not hard) and it suddenly works.
yeah thnx, that works most of the time. Still I would bring it back to get it repaired or get a replacement. Yesterday for example, I wanted to take a picture of a fast bike passing through but I ended up with a blurry picture. That shouldnt had happened and I dont want it to happen again.
Still thanks for the tip.
i have the same problem.. the camera take too long to focus or does not focus at all, i need to shake the phone.. i called tmobile and they will give me a replacement.
root the phone then add this to build.prop to fix it
ro.ril.sensor.sleep.control=0
aloric said:
root the phone then add this to build.prop to fix it
ro.ril.sensor.sleep.control=0
Click to expand...
Click to collapse
Where do I add that line in the build prop?
I have almost the same problem. Only facing this issue on third party camera apps like Snapchat or Facebook messenger, besides that it works fine. No problems on stock (yet).
Similar Issue
I went hiking one day back at the end of May, and inadvertently left my S6 in the car, which of course, got very hot during the day. After getting back to my car almost 9 hours later, my phone was almost too hot to even touch. I promptly removed the slim case that was on it, and held it up to the A/C (not ice cold, was trying to avoid condensation).
Ever since then, when going into 3rd party apps (most notably Snapchat, and sometimes even the stock camera app) the auto-focus motor seems to get stuck.
The easiest fix for me so far seems to be shaking my phone up and down rapidly 1-2 times. Upon doing this, I can hear a faint *click* and the focus works as normal.
This is very obnoxious as I've missed many shots due to having to do this (and sometimes it doesn't always work). Hard reset has done nothing, so I'm assuming maybe something in the camera got damaged due to excessive heat.
***Edit: After talking to my insurance provider (Squaretrade), they told me that this was still under manufacturer warranty, and to go through my carrier. After taking the phone to Verizon, it was discovered that the water-damage indicator had the slightest bit of red/pink on it, deeming it "water damaged". I later checked this myself at home and there definitely was some red on the strip.
Contacted Squaretrade again, informing them of the new situation, and they advised they would send a refund for the phone (since it was from eBay).
Hopefully the new phone will not have this issue!
Hi guys ..
I was suffering from the same problem .
The problem is the focus of the camera in galaxy s6 just like the Video, .
The solution is:
delete this line : ro.ril.sensor.sleep.control = 0
from ( build.prop )
you can find it in : system/build.prop
Using this program with root access : (Root Browser)
*i can not insert the link because i am a new user here .
after you click on build.prop chose (RB Text Editor)
note : (i am arabic man so my english is not good )
Anyone managed to fix this issue with the method above?
Yup..This is still common.. How does one fix without root?
Solution not working for me I did non fount the line ro.ril.sensor.sleep.control = 0 in my build.prop.. i tried to add the line but nothing changed problem still remains
I had the same camera issue. I took my phone to Samsung and they replaced the camera module.
Now it works perfectly.
Saludos ?
I can't go to Samsung, i have knox counter altered..no warranty for me
yourlifeupdated said:
I can't go to Samsung, i have knox counter altered..no warranty for me
Click to expand...
Click to collapse
So what? I have that to, went to an official Samsung Store and they (tried) to fix it
Having the problem myself btw, but if i aim the sensor to the ground en go back up its fixed, not so big problem. Only when selling the phone i want it fixed so its worth more...
its been only 26 days I purchased this phone. I was very happy to buy this phone, but it didn't lasted long. I have to take this phone to Samsung Service Centre after a week due to OTA 5.1.1 update failed. Samsung Service Centre personnel had flashed 5.1.1 using ODIN and I thought everything will be fine but I am experiencing the below problems frequently
Multiple times screen freezes and no option other than soft reset (volume down + power button).
in gallery, pictures taken through camera, the picture becomes green and all its pixels gets disturbed. happened for at least 5 pictures.
in idle / standby mode, phone will not wake up only led light flashes & screen remains black. Only option for me is to soft reset.
sometimes fingerprint unlock doesn't work (there is a message that says the same) and I have to enter the backup password manually.
Phone restarts by itself at-least couple of times (2-3 times) in a day in home network, while roaming it is pathetic.
Phone restarts while using camera, opening Google play, opening Google maps, any software application.
Phone restarts while in safe mode also (suggested by one of customer support executive to monitor my phone in safe mode)
Phone restarts during a call, this happened twice
Model #: SM-G920I
Android Version: 5.1.1
Baseband version G920IDVU2COF8
Kernel Version: 3.10.61-5228538 [email protected] #1 Thu Jun 25 17:43:05 2015
Build Number: LMY47X.G920IDVU2COF8
kishore927 said:
its been only 26 days I purchased this phone. I was very happy to buy this phone, but it didn't lasted long. I have to take this phone to Samsung Service Centre after a week due to OTA 5.1.1 update failed. Samsung Service Centre personnel had flashed 5.1.1 using ODIN and I thought everything will be fine but I am experiencing the below problems frequently
Multiple times screen freezes and no option other than soft reset (volume down + power button).
in gallery, pictures taken through camera, the picture becomes green and all its pixels gets disturbed. happened for at least 5 pictures.
in idle / standby mode, phone will not wake up only led light flashes & screen remains black. Only option for me is to soft reset.
sometimes fingerprint unlock doesn't work (there is a message that says the same) and I have to enter the backup password manually.
Phone restarts by itself at-least couple of times (2-3 times) in a day in home network, while roaming it is pathetic.
Phone restarts while using camera, opening Google play, opening Google maps, any software application.
Phone restarts while in safe mode also (suggested by one of customer support executive to monitor my phone in safe mode)
Phone restarts during a call, this happened twice
Model #: SM-G920I
Android Version: 5.1.1
Baseband version G920IDVU2COF8
Kernel Version: 3.10.61-5228538 [email protected] #1 Thu Jun 25 17:43:05 2015
Build Number: LMY47X.G920IDVU2COF8
Click to expand...
Click to collapse
Seems like a broken update install. Go to the service center again and list them all the problems thats been happening with valid proof. They will again flash the OS and give it back to you. It might possibly go but most probable that it won't, so repeat the same thing until they take it seriously so that they give you either a refund or replacement or a proper repair! The problem is, Samsung India never does replacements!
Reflash is needed otherwise have Samsung replaced your S6.
update on 30-July-2015
I am just got my S6 checked with Samsung Service Centre. The personnel has understood my problem clearly and told me that he will reflash the IMEI that will make the phone to Factory OS and then he do some random hardware test and then flash the Adroid ROM.
But unfortunately, IMEI flash failed giving errors. he says there is a problem with PBA and it has to be replaced, in other words he says it is a Mother Board issue.
[What is PBA issue? if IMEI flashing fails will imply a hardware problem?]
So, at-last it is figured out that there is a hardware problem. They asked me to go for a Service Warranty and get the Mother Board replaced. But I didn't agree to the Service Warranty. I asked for a replacement. They say, they can't help me out on phone replacement, I need to check with Direct Customer Centre team.
Thanks for your suggestions.
kishore927 said:
I am just got my S6 checked with Samsung Service Centre. The personnel has understood my problem clearly and told me that he will reflash the IMEI that will make the phone to Factory OS and then he do some random hardware test and then flash the Adroid ROM.
But unfortunately, IMEI flash failed giving errors. he says there is a problem with PBA and it has to be replaced, in other words he says it is a Mother Board issue.
[What is PBA issue? if IMEI flashing fails will imply a hardware problem?]
So, at-last it is figured out that there is a hardware problem. They asked me to go for a Service Warranty and get the Mother Board replaced. But I didn't agree to the Service Warranty. I asked for a replacement. They say, they can't help me out on phone replacement, I need to check with Direct Customer Centre team.
Thanks for your suggestions.
Click to expand...
Click to collapse
Any updates after this? Samsung India will never give in a replacement! NEVER EVER. I've tried arms and legs for my previous samsungs even within just 28 days but still they never did. They keep on insisting that the quality of repair will be excellent and i don't need to worry etc etc. Also, once you lose your 7 day window, you aren't eligible for a DOA. But, with increasing complexities in smartphone hardware, its difficult to replicate an issue within 7 freaking days! Please let us know what happened with your phone now! And yea, PBA is nothing but "printed board assembly" which is that green electrical board with all circuits and capacitors and other ICs.
ultraquantum said:
Any updates after this? Samsung India will never give in a replacement! NEVER EVER. I've tried arms and legs for my previous samsungs even within just 28 days but still they never did. They keep on insisting that the quality of repair will be excellent and i don't need to worry etc etc. Also, once you lose your 7 day window, you aren't eligible for a DOA. But, with increasing complexities in smartphone hardware, its difficult to replicate an issue within 7 freaking days! Please let us know what happened with your phone now! And yea, PBA is nothing but "printed board assembly" which is that green electrical board with all circuits and capacitors and other ICs.
Click to expand...
Click to collapse
Thanks for the follow up & sorry for the late response.
Yes, after this, I had to go through a difficult time. First they insisted me to go through repair, which i denied. After justifying the problems and pain that I was going through, they offered me a new handset as a replacement. When went to see this new replaced handset, the box is of dirt and a pen mark. It was looking like a potential tampered set. When questioned about this, they responded that they are giving a new handset and the dirt on the box is of mishandling by office boy & delivery person. When Opened the box, i was shocked to see the dirt hand print on the warrant card box also, & more disturbing is that there was dirt on the screen of the phone.
It was hard to believe myself, this was happening to me and for a one month old phone. When I rejected the new handset and demanded my money back. Again they took several days for process and finally did a refund. After nearly 2 months, a happy ending.
As I was in love with S6, did 2500 rupees insurance valid for 2 year, bought tough Armor case from Sipgen & Spigen Screen Gaurd, both together I spend around 3500 rupees. Tough Armor and screen guard are not used at all, now got wasted. Need to find someone who can use the same.
Now, I am back to my SII, which is still a reliable phone for me. SII is loaded with 5.1.1 which is being developed by Lysergic Acid. Thanks for his contribution and support.
S6 & services in India made me to think of moving to iOS. New Samsung devices with New Android features are being developed, but the core OS is not stable. Now, it is time for Android developers to concentrate on OS Stability, battery consumption so that people like me should feel secured when using new phones with new Android versions.
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
reyscott said:
try troubleshooting the phone based on the articles here https://support.google.com/pixelphone/topic/7078141?hl=en&ref_topic=7078170
if nothing is working here then call google so that we can see if RMA is possible for you. but i guess you should because pixel is just less than a year old.
Click to expand...
Click to collapse
It has to be at a point now to contact the OEM. On countless occassions I've factory reset and gone to different ROMs from scratch with the issue returning. Thanks.
Hats off to Verizon! I had purchased their total protection plan awhile back where you warrant your phone for 11 bucks a month. If it's lost or stolen you pay a deductible. With this issue I was hesitant but went in anyways.
For one, I didn't have to pay anything because I brought it in on the premise that it's a manufacturer defect (microphone hardware issue). Now if they determine my phone is damaged, the warranty company charges you 299. Mine won't be.
I go in yesterday and they told me I'll be receiving the replacement at my house TODAY. I even got the FedEx shipping memo for it being delivered tonight. Then I can just sent my old one in the same box that's a prepaid label.
Super happy about this!
No Sound
davidisflash said:
For about 6 weeks now I've seen this issue on 7.1.1 and 7.1.2 across three different custom ROMS and a few of their builds (PureNexus, Resurrection Remix, PixelDust, all testing with latest and a few versions beforehand). I am now back on stock (the latest May update for Google Pixel). I ran the flash-all.bat on both phone slots too.
The issue: sometimes, when I try to make a call:
- The dialer says "dialing" for an insane amount of time and phone is getting slow
- When it connects the call, I can't hear the other person. They can't hear me.
- When I try hanging up, I see "hanging up." It hangs there for a good few minutes, screen goes black. Phone unresponsive. Sometimes I get a reboot with a ramdump message.
- Unless I restart the phone after this issue, in this phone "session", calls will never work again. Even when rebooting the phone, it's a 50/50 hit and miss.
- If I flash a new ROM or factory reset, the issue seems to be "better" for maybe a few uses.
At first I'd think maybe a memory leak with the Dialer app. Maybe once I auto-update from the store to the new carrier services, maybe that's it. BUT, I then saw this thread where the mic is susceptible to a hairline crack, and phones manufactured before January are known to have bad solder joints:
https://productforums.google.com/forum/#!topic/phone-by-google/qUYytUuTRww;context-place=topicsearchin/phone-by-google/category$3Acontacts-calls-and-voicemail%7Csort:relevance%7Cspell:false
Now, I have a case on my phone and I have dropped it a few times. Maybe the mic is dying, I just don't know. Through verizon I have one of those protection plans so getting a replacement wouldn't keep me out of a phone so long as they have a replacement in stock (going through Google's 1 year warranty would take weeks). The problem is that if I use my warranty, I'm paying 150 deductible for what could simply be a software issue.
Can anyone comment on this? I'm torn about taking it to verizon when it may not be hardware but it really is hard to say. For them to diagnose it I would imagine would again be sending out the phone and that could take time.
Click to expand...
Click to collapse
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
cc999 said:
Thats a known problem with the Pixel. It has something to do with the soldering on the board that eventually breaks loose. Google is aware of this and should give you a replacement. Supposedly phones with a manufacturing date of 2017 will not have this issue and was addressed at the production.
What year was it manufactured?
CC
Click to expand...
Click to collapse
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
New Pixel
davidisflash said:
It was made in 2016. I just got the replacement phone and no longer have the issue with the replacement.
Click to expand...
Click to collapse
What's the manufacture date of the new phone?
CC
cc999 said:
What's the manufacture date of the new phone?
CC
Click to expand...
Click to collapse
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
davidisflash said:
2017. What sucks is that it came with 7.1.1 so now I can't unlock the bootloader then root.
Click to expand...
Click to collapse
better than having a broken phone. I was under the impression that the newer replacements came from google and were unlockable, but I guess only a lucky few,
Hey guys,
My mic and headset are not working at all when making or recieving calls. When I restart my phone it works for a while but it reoccurs after few minutes. I tried reflashing and wiping my phone still it's persistent. I get bluish greenish lines flickering at the screen rarely which does does cause the screen to freeze sometimes. Any help? Is it a software or hardware isssue?
Thanks in advance
My mic stopped working this week. Talked to support and they got me a new phone should be here monday or tuesday. Still inside of the one year warranty. I was on beta O came back to 7.1.2 still did not work. it is a hardware malfunction. Its weird because ok google works but i have to yell at the phone for it to hear me. I have a buddy that has a similar issue to what you have going on. He drops his all the time so I am assuing that is why his is broke. If you have the extended warranty through google just use that its no cost.
Having issues as well, though a little different. When I plug in a wired headset - but only one with a mic - things go haywire. The volume starts gradually going down, and the Google Assistant screen comes up.
Sounds like this is a hardware issue, so need to start the return process. Problem is, I am not the original owner. The original owner said she bought it direct from Verizon in November. So still under warranty. Do I need a receipt or do they just go my the IMEI or serial number?
fungo45 said:
Having issues as well, though a little different. When I plug in a wired headset - but only one with a mic - things go haywire. The volume starts gradually going down, and the Google Assistant screen comes up.
Sounds like this is a hardware issue, so need to start the return process. Problem is, I am not the original owner. The original owner said she bought it direct from Verizon in November. So still under warranty. Do I need a receipt or do they just go my the IMEI or serial number?
Click to expand...
Click to collapse
Just the IMEI and serial. When they ask for the account associated with the pixel just give them your gmail account that you signed into the pixel with.
I had the same problem, thought it was a software problem but then it wasn't, talked with Google support and they shipped out my replacement phone!! Within 2 days I got it and ever since then it worked fine!
I didn't had warranty but they made an exception for this one time so I was blessed!!
this is odd. i have the same issue. I can get it back temporarily by rebooting... didn't start for me until yesterday.