Related
Can anyone shed some light on the issue I'm having? My nexus s after a while and I mean a while of sitting there not being used goes completely unresponsive to the point that I have to pull battery and reset! I've tried different Rom's and continue to experience same thing! It was working fine until a few days ago! I've wiped data and cache and davlik cache thru cwr and still have same problem. If anyone has had this issue and can point me in the right direction it would be greatly appreciated.
Sent from my Nexus S using XDA Premium App
Time to start looking at apps that might be running amok.
Maybe install a log collector and leave it running and autosaving, then review post-problems to see if anything stands out as crashing the system.
It's painful, but a Factory Reset might be your best recourse, then re-consider what apps, kernel and rom you're using and put back on a few at a time to isolate in groups what may or may not be causing issues.
distortedloop said:
time to start looking at apps that might be running amok.
Maybe install a log collector and leave it running and autosaving, then review post-problems to see if anything stands out as crashing the system.
It's painful, but a factory reset might be your best recourse, then re-consider what apps, kernel and rom you're using and put back on a few at a time to isolate in groups what may or may not be causing issues.
Click to expand...
Click to collapse
thank you for your quick response, i've tried factory rest to no avail, i quess i will start with the apps and slowly monitor them.
i'll go a little more drastic...
wipe the phone factory reset
then re-install apps that are known to be safe, and then monitor it
ALL GAMER in the process of doing that now, thanks for advice. Will report back findings! Fingers Crossed!
Extremely glad you posted this!
I have been having the exact same problem since the past 10 days, and it has gotten extremely frustrating. I use my phone as my main alarm, and I ended up going late to work a couple of days back because my phone had completely shut off. I performed a factory reset yesterday, and the same thing happened this morning. I leave my phone on and charging with the wall charger, so now I'm beginning to suspect if there's something wrong with the charger or the battery. I've registered a ticket with Samsung but i'm reluctant to send it in, because I've babied my phone and wouldn't like an misuse or scratches on it from being in the repair shop.
Please help! I love my Nexus S, and i'm running Stock 2.3.3 GRI40.
Hi, I have bad news for you guys.
there are already thread for this issue here:
http://forum.xda-developers.com/showthread.php?t=986181
And Google help forum here:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en
Please go to those and post comments as there are more and more of us with this problem. We've also got some sort of response from Samsung via Twitter - supposedly they are looking into this.
Also, flashing phone does not seems to help, but please go to those threads, its all there.
Just wanted to update on how my problem was going. I've tried everything you guys suggested but still experiencing the same thing. It's seems like it's a hardware issue from what I read from the previous posters post! I brought the best buy protection plan so they are sending me a new one! I think this is the only resort to anyone experiencing this issue. They gave me a loaner phone which is done lg piece of sh*t, man am I having withdrawals! I don't know if this issue was caused due to excessive flashing or not! I hope not cause that would definitely suck. I've only had the device for 3 months!
Nexus 5 all of sudden stopped working?!
I also experienced it. The damage in wifi module but I did claim the warranty. have you explain what happened to customer service?
Just to offer my input into how I resolved the "Turning Wi-Fi on" message on my Galaxy S4. It seems I had misconfigured the Profiles, so I reset them (Settings>Profiles>Reset), restarted the phone (hard reset) and voila.
There are probably many different causes, but hopefully my method helps someone.
Adding my two cents
"I am having issues with my wifi not even turning on at all on my Nexus 5. It all started after I got a regular 5.0 OTA update. It didn't happen immediately but soon after the update my wifi quit working and I would have to reboot to get it to work. Me working in tech support and having experience with android I tried everything I knew how to do. I started with wiping cache and that didn't make a difference. Then I did a factory reset and that didn't help either. Then I flashed the factory 5.0 image and that still didn't work. Then I tried downgrading to 4.4.4 and flashed that factory image and the issue still persist. Then I put 5.0 back on and just lived with it. Then 5.0.1 came out so I flashed that and still the same issue. I did it this time as a brand new device and wiped everything and just flashed the image and it didn't even try to work. I think it may be a hardware issue but I never had an issue before the 5.0 OTA update."
This is the info I contacted google nexus support with and he didn't have me try anything because he said I already did basically everything. I am OUT of warranty and my only help would be repair through LG which I would rather not do. Anyone else have any ideas on how to fix it or is it a hardware issue?
http://forum.xda-developers.com/showthread.php?t=2947784
I'm really not sure what happened at first I thought it was a software problem but after checking all the roms on my Multirom including my OG stock ROM and it seems to me my mic is broken. I noticed it because I use voice to text and voice search allot and it was working fine on Preview LPX13D and the white Preview LPX13D for the N5 and then it just seemed to stop working at some point. I was going to post this in the Preview LPX13D thread but after testing it in all rom and doing a factory reset to stock unrooted and the problem is still there. so i'm guessing I'am just burnt and have to send my phone back to Google. My step dad gave it to me for xmas last year tho so I don't have the order # and or was not bought by me. I guess I will contact him and see if he will send it back for me. I was posting this to see if there was a solution i was unaware of because I did see a few people posting about the same problem when L first dropped but I didn't see any solutions and i'm guessing most people just sent there's in. If I'am not able to send it back to Google What part should I order to fix it. Is it the Speaker phone part that has both mics on it or the flex cable? Thanks to everyone for their help and advance and to all of the Devs for all their hard work.
NUGZZ420 said:
I'm really not sure what happened at first I thought it was a software problem but after checking all the roms on my Multirom including my OG stock ROM and it seems to me my mic is broken. I noticed it because I use voice to text and voice search allot and it was working fine on Preview LPX13D and the white Preview LPX13D for the N5 and then it just seemed to stop working at some point. I was going to post this in the Preview LPX13D thread but after testing it in all rom and doing a factory reset to stock unrooted and the problem is still there. so i'm guessing I'am just burnt and have to send my phone back to Google. My step dad gave it to me for xmas last year tho so I don't have the order # and or was not bought by me. I guess I will contact him and see if he will send it back for me. I was posting this to see if there was a solution i was unaware of because I did see a few people posting about the same problem when L first dropped but I didn't see any solutions and i'm guessing most people just sent there's in. If I'am not able to send it back to Google What part should I order to fix it. Is it the Speaker phone part that has both mics on it or the flex cable? Thanks to everyone for their help and advance and to all of the Devs for all their hard work.
Click to expand...
Click to collapse
I got that too, definitely same problem. I can't send it to Google too. What to do guys?
maarcnylmz said:
I got that too, definitely same problem. I can't send it to Google too. What to do guys?
Click to expand...
Click to collapse
I ended up sending my phone back I tried everything to fix it.
I am having the same issue. I can't make out what the fault is. I have googled extensively and it could be one of these:
1. Noise cancellation microphone
2. Earphone jack that doesn't recognise when the earphones are removed
3. A hardware malfunction.
The thing is that I have tested all of these.
1. Covering the noise cancellation mic or fiddling with the build.prop makes no difference
2. I have tried to turn off the headphones while they were in using an app from the play store. Didn't solve the problem
3. Installed a noise meter app and when I blow /tap straight on the grill were the mic is house, there is recognition. Also tested using Google voice search. Also recognised some words. Finally, if i make a call and put the phone in speaker mode the person on the other side hears me loud and clear. So not the hardware (I don't think)
I google some more and noticed that a number of phones have this issue not just the Nexus 5. For example the OnePlus One (https://forums.oneplus.net/threads/microphone-problem.91832/page-3), the Moto G (http://www.androidpure.com/how-to-fix-the-no-sound-during-calls-issue-on-the-moto-g/) the HTC One X (http://forum.xda-developers.com/showthread.php?t=2283990), the LG Optimus (http://forum.xda-developers.com/showthread.php?t=2461432) and probably more.
So, could this be a broader problem with Android itself? I have too many questions.
Hopefully somebody brilliant from this forum will see this and apply their genius minds.
i have the same issue, need help
Lucas1 said:
i have the same issue, need help
Click to expand...
Click to collapse
I was unable to find a solution for it. I sent my phone back to Google and got a New one. If you got yours from the play store less than a year ago you maybe able to get them to replace it.
I just updated to Oreo via OTA and the phone worked great for a day. After that, I couldn't make calls and people couldn't call me. My phone would randomly reboot or get stuck on the G logo.
I wiped and reinstalled Oreo, and now the same thing is happening. Plus I see this weird 'colourful static' after trying to make a call, before my phone just shuts off. I tried safe mode and the same thing happens.
Currently in an urgent situation where I need my phone to be functioning, hoping someone here can help.
Thanks
I am having exactly the same issues since the Oreo OTA. If I reboot the phone, the issues go away for a while, but eventually it's back to problems where I'm unable to make/receive calls, screen is flickering (even that colored static you mentioned), lag when unlocking the phone, etc.
Have you found out anything?
erc. said:
I am having exactly the same issues since the Oreo OTA. If I reboot the phone, the issues go away for a while, but eventually it's back to problems where I'm unable to make/receive calls, screen is flickering (even that colored static you mentioned), lag when unlocking the phone, etc.
Have you found out anything?
Click to expand...
Click to collapse
I have no such problems. I am running stock. It is running really smooth. I also have september security update. Unfortunately, only thing I can suggest is factory reset.
rohitece06 said:
I have no such problems. I am running stock. It is running really smooth. I also have september security update. Unfortunately, only thing I can suggest is factory reset.
Click to expand...
Click to collapse
I am also running stock, never rooted, never unlocked the bootlader, also running the september security update. I have factory reset, and I have even run into the issues while using the phone in Safe Mode. There are a number of people with similar issues leaving feedback on Google's issue tracker, but I was hoping to find someone who maybe has found a solution.
erc. said:
I am also running stock, never rooted, never unlocked the bootlader, also running the september security update. I have factory reset, and I have even run into the issues while using the phone in Safe Mode. There are a number of people with similar issues leaving feedback on Google's issue tracker, but I was hoping to find someone who maybe has found a solution.
Click to expand...
Click to collapse
I am sorry to hear that man! I hope you/google figures it out.... may be try flashing the factory image manually.
I'm having the same issues and verizon Chat support told me they are having issues with the OS upgrade and the Pixel. Did the factory reset and everything else. Replacement phone coming now. If it's the Oreo OS, I bet it's going to have the same problem... This is a major problem, as I am a single Dad and have a long drive to get my daughter - do they really want me to text while I drive instead of calling?? This is Day 5 of this issue and 4 trips to their stores.... ugh. Suggestions?
Update
Just wanted to post an update. After factory resetting a few times the problem persisted. I sent it back to my wireless carrier and they sent it to Google. In the meantime I had a loaner phone from my carrier. Google sent back a refirb (it was practically new with new screen and camera), and the issue hasn't come back in the new phone. My suggestion is to send back to your carrier to get a replacement. Good luck!
i am on stock too (from google store), oreo update and have exactly the same problem, it also occurs with "ok google".
after reboot, calls and "Ok google" work perfect so the mic is okay. but sooon after it just stops working and i got randoom reboots.
same is happening in "safe mode"
i did factory reset via android and id did not help.
now i tried a factory reset via boot menu and will check it out.
Has anyone else experienced problems with call quality on their Pixel 3 or Pixel 3XL?
The issue I'm referring to is the one where you can hear the other party, but they cannot hear you.
I have a Pixel 3 (my wife) and 3XL (mine). Both my wife and I are told nearly every call we make that we are breaking up or sound like we are robots or underwater. I even RMAed the P3 and have the same problem.
Its a tricky problem to notice right away, because it depends on other people telling you that the call quality sucks. The quality is fine on the P3 side.
Google seems content to ignore the issue.
There are multiple threads on this over on the official Google product forums with hordes of people chiming in that they have the same issue, and nothing fixes it. I'm starting a thread here, because I've seen almost no mention of it on XDA.
Yeah, there are a few threads on XDA about this already. There is no real fix or solution, but my personal opinion is that it is caused by relatively weak signal strength, but not because of the carrier, but because something in the Pixel 3 does not grab onto cellular signals as well as it should. My wife and I have both suffered with this until T-Mobile gave us a cell spot to install in our house. Now, the issue is gone when calling from home but pops up again when we leave the house. And we are not in small town (Houston, TX). This issue didn't happen with either of our Pixel 2, iPhones, or Honor 8 Devices. RMA replacement didn't fix it either.
Me too. Call issues with Pixel 3XL on 4G/LTE. Telus, Canada.
Sent from my [device_name] using XDA-Developers Legacy app
Same here on T-Mobile US.
Sent from my Pixel 3 using Tapatalk
Just a thought. Couldn't we just start a petition on one of the free petition sites and point all forums and sites to that location to get Google to address the problem? Eg.
Google Pixel 3/3XL Calling Issues
Google has failed to even acknowledge many of the known 4G/LTE issues of the Pixel 3/3XL. Through this petition I hope to make visible how large this problem is and force Google into acknowledging and addressing these various issues.
Poor connection issues during 4G/LTE phone conversations including but not limited to:
a.) buzzing, static, interference
b.) dropped calls
c.) voice delays
d.) inaudible voice
A large amount of users have already tried resolving these problems through Google's customer support channels and RMA's processes to no avail.
Although various users have discovered temporary workarounds by disabling features and settings on their phones, nothing has totally rectified these aforementioned problems. Google's customers deserve to have their devices operate as advertised. By failing to acknowledge any problem exists with these phone's during regular 4G/LTE conversations Google has demonstrated bad faith. Furthermore they continue to sell the device knowing people will experience these issues. If you are experiencing any of the aforementioned problems please take the time to sign this petition.
Sent from my [device_name] using XDA-Developers Legacy app
Do it up and I'll sign it. Online petitions don't really have a great track record for being effective, but anything to raise awareness. Its not getting a lot of traction on this forum, but the activity on other sites and social media indicates that its affecting a very large number of people. After doing more research on this, I would go so far as to say it is the most important and widespread defect that exists in the Pixel 3 line at the moment, and Google is totally ignoring it.
It literally stops people from using their phone as a phone.
I suspect this issue might heat up in the near future. Lots of people will have received the P3 over Christmas, and will soon be discovering that no one can hear them when they talk. There is likely to be an influx of confused, disappointed, and frustrated people throughout January.
Google has been able to ignore it because of the lack of coverage. Anything to spread awareness is good. I would sign a petition. I will say that I'm hoping not to be a Pixel 3 owner in the near future. I'm fighting with Google to authorize a return for my 3XL and my wifes 3, but their support has been a nightmare to deal with. I may have to go through Mastercard for a charge-back. I know someone I work with who did that, and she claims that the person she dealt with at Mastercard was well aware of the issue and the Pixel 3 is a popular charge-back over the last month.
I plan on purchasing a Oneplus 6t for myself and my wife. I will do so out of pocket if I have to. Its not perfect, but Oneplus seems to be on point with acknowledging issues, and the model has a fairly solid track record so far.
A $1500 lesson learned not to buy hardware from Google again.
JohnnyRebel said:
Just a thought. Couldn't we just start a petition on one of the free petition sites and point all forums and sites to that location to get Google to address the problem? Eg.
Google Pixel 3/3XL Calling Issues
Google has failed to even acknowledge many of the known 4G/LTE issues of the Pixel 3/3XL. Through this petition I hope to make visible how large this problem is and force Google into acknowledging and addressing these various issues.
Poor connection issues during 4G/LTE phone conversations including but not limited to:
a.) buzzing, static, interference
b.) dropped calls
c.) voice delays
d.) inaudible voice
A large amount of users have already tried resolving these problems through Google's customer support channels and RMA's processes to no avail.
Although various users have discovered temporary workarounds by disabling features and settings on their phones, nothing has totally rectified these aforementioned problems. Google's customers deserve to have their devices operate as advertised. By failing to acknowledge any problem exists with these phone's during regular 4G/LTE conversations Google has demonstrated bad faith. Furthermore they continue to sell the device knowing people will experience these issues. If you are experiencing any of the aforementioned problems please take the time to sign this petition.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll sign it as well. Nice write-up
Sent from my Pixel 3 using Tapatalk
---------- Post added at 10:59 AM ---------- Previous post was at 10:55 AM ----------
When it's family or friends on the other line it's a nuisance, but when it's an important business call and you've been forwarded through several layers of customer service with no way to call back if it happens it really creates a headache.
Sent from my Pixel 3 using Tapatalk
Well one thing that has fixed mine was simple troubleshooting. These are the steps I've done.
1. Force Stop the Phone app
2. Clear both cache and Storage for Phone App
3. Uninstall and reinstall the updates for the Phone App
4. Reset WiFi, Mobile, & Bluetooth
5. Restarted the phone.
So far going 3 days without any issues with it. Still monitoring it but so far so good.:fingers-crossed:
rtlalipon said:
Well one thing that has fixed mine was simple troubleshooting. These are the steps I've done.
1. Force Stop the Phone app
2. Clear both cache and Storage for Phone App
3. Uninstall and reinstall the updates for the Phone App
4. Reset WiFi, Mobile, & Bluetooth
5. Restarted the phone.
So far going 3 days without any issues with it. Still monitoring it but so far so good.:fingers-crossed:
Click to expand...
Click to collapse
Why didn't I just think of "simple troubleshooting"? If that fixed your problem I'm happy to hear it. The closest I came to eliminating the problems was my 4th complete factory reset. Then instead of restoring settings, apps, etc. via the cable from my 2016 Pixel, I manually restored my contacts from my Gmail account online. I made sure to not install any additional apps for testing. Then I installed the latest updates/security patches. This did seem to eliminate some of my other minor issues but did not fix the calling issue. Disabling 4G did, but why should I have to use the 3G network on my brand new phone. I also tested various beta apps like phone (Google's dialer) to see if they might address the problem. I tried different dialers and also preformed various safe-mode tests. I tested my phone in multiple cities (London, Windsor, Sarnia, Goderich, Wasaga Beach). I'm pretty sure at this point software cannot fix it. Don't get me wrong, a patch might come along that can mask or hide the problem but I think the only true fix would be hardware replacement.
Sent from my [device_name] using XDA-Developers Legacy app
Well just saw there was a new carrier services update. Maybe a glimmer of hope.
Sent from my Pixel 3 using Tapatalk
Same problem, T-Mobile NL here.. sometimes I'm hard to hear..
Same issues here, Partner (Orange) IL.
Weird buzzing (really weak though) static background noise, sometimes people tell me that I'm cutting off (I hear them great on my end).
Luckily, I don't use the device so much for phone calls these days, but it's a damn shame.
Carrier Services?
perfoliate said:
Well just saw there was a new carrier services update. Maybe a glimmer of hope
Click to expand...
Click to collapse
This one? Carrier Services
I have an older version installed. The Google Play web site shows a newer version. They must be rolling it out in waves?
perfoliate said:
Well just saw there was a new carrier services update. Maybe a glimmer of hope.
Click to expand...
Click to collapse
Unfortunately, no.
Carrier Services doesn't effect call quality. It's an RCS client, which has to do with messaging.
Besides, people on the official product forum are saying the issue persists following the Jan 9 carrier services upgrade, the Jan security upgrade, and with the beta phone app.
Sadly, it looks like this is hardware.
Most people, including myself, notice that the problem goes away when you disable WiFi. I suspect there is a conflict between transmitters (eg. phone and wifi radios fighting over power, etc). It really should be a recall, but I bet Google will just band-aid it with a software patch that automatically disables then re-enables WiFi during phone calls. Most people won't notice their WiFi turning off during phone calls anyway.
Either way, QA on google hardware seems to be steadily declining since the Pixel 1. Looks like Google is realizing they can get away with it.
To those of you in this thread who are having problems, please check your signal strength and report your results to this thread:
https://forum.xda-developers.com/pixel-3/how-to/finally-solve-call-quality-issue-t3888549
I got an RMA device. Still have the issue with VoLTE enabled. I still get the screen flash with unlock, too. I will have to go back to plaguing their customer service for a refund. I'm not going through six phones. I just want my money back so I can get the hell away from this company.
I've used WiFi calling to help in house with weak coverage
It looks like this problem wont ever get any traction with Google even though there seems to be a lot of people having the same sound issues. Its sad though because this is such a great phone to have such a profound basic issue. I like to use my speakerphone when I receive calls and no one can hear me when they first call. I have to play with the speakerphone button switching it off and on for them to even hear me a little bit?? I guess millions have to have the same problem in order to get a fix. I see some people say to turn off advanced calling,,,well I shouldnt have to do that for one,,,and if I do my android wear watches wont work.
Wonder if anyone has tried a custom rom here and if the problem still exists?
It frustrates the living **** out of me, I am sorry - but reading about all the people here who has this TOTALLY unacceptable issue with their brand new Pixel 3 saddens me deeply! Google doesn't seem to really give a dang about it, as there are no official comments either confirming the issue or reporting on it as some work-in-progress.
Is it paranoid to think that this is a deep hardware issue that is "too expensive" for Google to acknowledge? Because, I mean, as a professional who relies on my phone in work, I have pissed off about 10-15 potential customers the last month, and my mom and dad, quite a lot as well. To the point where they get frustrated because of the choppy quality.
When it happens I tend to get a small x over my signal. As if signal is lost.
I am following all threads closely and will report back if Google support ever hits me back with that promised phone call...
Sending peace and love to my fellow brothers who has this frustrating issue! I feel you
pacificwing said:
Has anyone else experienced problems with call quality on their Pixel 3 or Pixel 3XL?
The issue I'm referring to is the one where you can hear the other party, but they cannot hear you.
I have a Pixel 3 (my wife) and 3XL (mine). Both my wife and I are told nearly every call we make that we are breaking up or sound like we are robots or underwater. I even RMAed the P3 and have the same problem.
Its a tricky problem to notice right away, because it depends on other people telling you that the call quality sucks. The quality is fine on the P3 side.
Google seems content to ignore the issue.
There are multiple threads on this over on the official Google product forums with hordes of people chiming in that they have the same issue, and nothing fixes it. I'm starting a thread here, because I've seen almost no mention of it on XDA.
Click to expand...
Click to collapse
I get this, it's reception issue. I fixed it by keeping data on so it uses VoLte 4G HD voice whatever it's called.
I have the issue with my Mate 20 Pro as well but the Mate doesn't have VoLte to fix it.