As of Saturday, my Pixel refuses to make or take phone calls. It seems to work flawlessly in all other regards.
If I get a phone call it takes a long time to acknowledge that I've selected to answer the call. I can then neither hear the other person, nor can they hear me (no line noise, complete silence). If I choose to hang up, the Phone app ceases to work, and within a few minutes the whole phone reboots. Making call doesn't even get that far, as as soon as I initiate the call the phone app ceases, and again, within a few minutes the phone reboots.
I chatted with Google Pixel Help twice yesterday. They checked a bunch of things with me, then suggested a factory reset when those didn't work. Yesterday, the issue only seemed to occur after the phone had sat idle from a reboot for a while. So initially after the factory reset things were working. When I got home, however, the problem persisted, and was now occurring every single time the Phone app was used. It's now 100% reproducible:
https://youtu.be/5YSJpLVBR1A
https://youtu.be/sENelMnE4eI
I've tried using 3rd party dialers, but they all seem to throw over to the stock phone app as soon as the call is made. I have no idea what happened.
Google hasn't been helpful, as their support person said I'm out of warranty (purchased in late-Oct. 2016), and thus have to deal with Telus. I have I feeling I know how that's going to go (ie: not well).
Anyone else ever experienced anything like this?
Happend to me too.
I just got an email back from the Google Store Support manager. She just reiterated that the phone is out of warranty and suggested that I visit UBreakIFix to see about getting it repaired.
Overall, I'm quite unimpressed with Google's support on this. If I have to replace the phone, I'm seriously going to consider something other than Google.
saltorio said:
I just got an email back from the Google Store Support manager. She just reiterated that the phone is out of warranty and suggested that I visit UBreakIFix to see about getting it repaired.
Overall, I'm quite unimpressed with Google's support on this. If I have to replace the phone, I'm seriously going to consider something other than Google.
Click to expand...
Click to collapse
Well I mean if the phone is out of warranty they are following the same guidelines literally any other manufacturer would. Their response is kind of a non-problem and your reaction is kinda poor. Anyways for now try rolling back to the factory image before current and then updating back to current, might do something.
Edit: preferably keeping the -w intact but you can try dirty flashing it first
Related
I was going to exchange my phone for a new one before my 30 days is up which is tomorrow, so I did a factory reset. They ended up not letting me because they knew about the GPS problem and said there is a fix coming. I also had my email disappear and wanted to just get a fresh device before I am stuck for 2 years.
So I wanted to see if anyone else who has done a factory reset has noticed the same or differences from before they reset it.
1. Data icon (3G,E) still shows while WiFi is connected. Before the data icon wouldn't show.
2. Facebook pictures sync works much better and actually sync's pictures. Also its doesn't take 20 clicks to select the contacts to DL.
3. Phone overall doesn't seem laggy as much and much more responsive.
4. When I open messages the first time it keeps asking if I want to set a limit, which I have to say no every time. Very annoying, not sure why it keeps asking,
Note: I haven't rooted this time (I was before) yet and I have less apps installed. I haven't installed the official FB app in case it was conflicting, but I doubt it.
I will add more if I notice anything else. Today is the 3rd day since the reset.
Curious to see what replies you receive. And you're saying AT&T wouldn't return it even though there is a "known-issue" with the phone?
RootPhisher said:
Curious to see what replies you receive. And you're saying AT&T wouldn't return it even though there is a "known-issue" with the phone?
Click to expand...
Click to collapse
Yea, thats BS. if the return policy is 30 days you should be able to return it. And who gives a **** if there is a fix on the way. It doesnt work right now, and you signed a 2-year agreement for a phone to have a working GPS unit which doesnt; breech of contract.
iceman4357 said:
Yea, thats BS. if the return policy is 30 days you should be able to return it. And who gives a **** if there is a fix on the way. It doesnt work right now, and you signed a 2-year agreement for a phone to have a working GPS unit which doesnt; breech of contract.
Click to expand...
Click to collapse
They wouldn't let me exchange it, I probably could of returned it, but not sure if I can deal with going back to the Fuze with WinMo. At least I turned the Fuze into a portable Garmin GPS with internet calling via WiFi.
(psst. just tell them it shuts down randomly for no apparent reason.)
I exchanged mine for this (real) reason. It was ridiculous. My Captivate continued to shut down at least 2-3 times a day. I even contacted Samsung about this issue and they said to just exchange it.
I did a Factory reset and hoped that it would fix the problem. Three hours after doing so, it shut down on me again. I have had it. I just exchanged it.
Sorry I can't really help you with the different between stock and a factory reset device since I didn't really take notice of it. Although, after the reset, I went to Settings - About Phone - System Tutorial and clicked Begin. Nothing happened. Yesterday, with my new device after the exchange, the Begin button took me to the Tutorial.
I had 3G connectivitiy problems before, and after doing the odin restore those problems are gone. It may have been poor network conditions for a couple days, but either way, my problem no longer exists.
I posted this almost verbatim to my G+ stream. It says it all, basically, and I don't have time (at work right now) to give a lot of detail but I wanted to get this out there...
----
I received three text messages this morning at 7:25 EDT.
They appeared to be random characters, like when an OS is trying to display characters from a language that requires a codepage it doesn't have installed. They are as follows:
<sisa:68571244:1:1:199:41970681>ezG7k3jzC7mFo6SSm7KUIg
<sisa:65471246:1:1:199:43800551>HE85MqRY33Xf0qmVbaCjyQ
<sisa:65471245:1:1:199:43799818>SpxSbHILo1mHG/EjkMAF2g
All three received at 7:25. I was able to use my phone up to this point because I was able to view the messages normally. Now, suddenly I have no digitizer response. None whatsoever. To use my phone, I have to pull the battery and boot to safe mode then use my trackpad and menu buttons to access certain features.
Now, it seems to me, the first part is like an address packet, maybe including a sequence number. The second part is like what I see when e.g. viewing the output of 'cat somefile.binary' in Linux. At first I thought it was spam from a foreign country, but now I'm wondering if this was some binary code received and interpreted by my phone. I wonder if this is possibly an android virus/remote hack? Is that possible?
I may wind up wiping the phone when I get home and have ability to back stuff up, but this is annoying, to say the very least.
-----------
Now, I did a little googling and it appears that it may just be that T-Mobile was trying to send an update to the phone (maybe the fact I'm on a custom ROM is why it borked). But has anyone had this or anything like it happen to them?
Thanks much in advance,
CJ
Update
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
cj chitwood said:
It appears the digitizer fouling *may* have been a coincidence. Very odd how coincidences seem to keep happening to my electronics. Anyway, I'm about to wipe and reflash, see if it persists. If it was a software bork, it should be 100% resolved with a reflash. If hardware, it'll still be borky.
It is now intermittent, and I tapped the screen pretty firmly a bit ago and it started working almost reliably again. Sounds like a loose connection. Very odd coincidence.
Will update when decided for sure the cause.
Click to expand...
Click to collapse
My evo **** needs a good smack every now and then when the kb gets opened because it has a bad flex cable. since I'm not with sprint and only test roms on that phone I don't need the kb anymore but sometimes the little one opens it
Sent from my myTouch_4G_Slide using Tapatalk 2
Yep, I'm not so lucky. I need the touchscreen more than the keyboard
Still, was on the phone for 45 minutes today talking with two different reps, and my replacement phone (another MT4GS in Khaki) is scheduled to arrive in three days.
Time to see if I can return it to stock. It's a hardware problem, so what ROM is on it shouldn't matter, but I don't want to give them any reason to balk.
My phone is out of the return window now and dealing with customer service is probably my last resort.
My phone is on stock Touchwiz and unrooted, T-mobile variant. I have factory reset my phone 3 times and deleted the cache but these issues remain.
Here are some of the issues I have had. I am hoping they are software, but I couldn't find much information on any of them. If you also have experienced these, please let me know just to know that I'm not crazy and alone in this.
Camera app will be black on launch and crash due to an error. - This reminds me of the Lollipop software issue that I had on my Nexus 5 so I'm not too concerned since an update is coming out, but it is still bothersome when I bought the S6 for the fast camera launch but I have to restart the phone because I get this error. At least restarting the phone fixes this.
Phone vibration is inconsistent or weak. - The vibration was strongest when I first bought it, but it has grown considerably weaker. It still can be strong sometimes, but it fluctuates. Sometimes the vibration is so weak that I can't feel anything unless I put it on max strength under Vibration settings, but it sometimes fixes itself and isn't as weak. It hasn't been as strong since I first got it from what I remember. Restarting the phone does not fix it. It just comes and goes.
Phone does not receive or send sound when answering or making phonecalls. - This is hard to explain, but sometimes when I'm making a call, the dial tone will never sound and if the call looks as if it has gone through, there will be no sound. The person will say they received a call but didn't hear anything as well. This also happens if someone gives me a call and I pick up and hear no sound. A phone restart usually doesn't fix this, but sometimes it just magically works again.
Sound turned off by itself. - This has only happened once or twice so far but it was bothersome. I didn't change or touch any of my settings for this to happen. My sound just stopped working. Youtube app, volume settings, etc. didn't create any sound. When my alarm went off, it made no noise. Restarting the phone would fix it.
Anyway, please let me know if you have had these similar problems. Is it likely they are software related? I can't find any solutions and if a factory reset is not fixing it, I don't know what to do.
Thank you!
Return it
Brava27 said:
Return it
Click to expand...
Click to collapse
I would, but I'm outside the 14 day return window from T-mobile.
Jinora said:
I would, but I'm outside the 14 day return window from T-mobile.
Click to expand...
Click to collapse
So? You have a faulty phone and these issues would be taken care of within your warranty period right?
yes you can do a warranty exchange. theyll replace it
tlxxxsracer said:
yes you can do a warranty exchange. theyll replace it
Click to expand...
Click to collapse
bramgg said:
So? You have a faulty phone and these issues would be taken care of within your warranty period right?
Click to expand...
Click to collapse
I was hoping that I wouldn't have to go through the Warranty process but it looks like there is no choice.
Thank you all for your input! I'll see what happens. I appreciate it.
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,
Anyone else having this issue? There's a big thread on the Google Pixel help pages going back a year or so, most seem to think it's to do with updates, and now I'm having problems the same day as I downloaded the February security update. It's the bottom speaker that notification sounds and ringtones come through to. Music, YouTube ect. just comes through the top one. Making phone calls is ok as the recipient can hear me. Been in touch with Google support and logged a bug report as others have done. Bit frustrating.
Did they get you to do any troubleshooting? Typically I would expect them to get you to try safe mode and, if that doesn't help, a factory reset. If the bottom speaker is still not working after a factory reset, and your phone is still covered under warranty, I would expect a replacement device.
Thanks for the reply. Yes tried all of those. Unfortunately in the UK we only get a years warranty
Well, just an update on my situation.
Having had a few live chats with Google, on the last one they kindly offered to have it back, even though it is purchased on contract with 3UK, and they sent me a new (refurb.) one.
From sending to getting my replacement took less than 4 days! Faith in Google restored!