Lollipop Caller ID Pictures on Incoming Call? - Nexus 5 Q&A, Help & Troubleshooting

I have received a half dozen or so phone calls since I upgraded to Lollipop, and so far every call that I've had has a caller ID picture assigned in contacts, but none have shown up with a picture while the call is actually ringing my phone.
Has Google removed caller ID pictures on incoming calls, or is there something else going on here?
Have other people seen this happen?

GldRush98 said:
I have received a half dozen or so phone calls since I upgraded to Lollipop, and so far every call that I've had has a caller ID picture assigned in contacts, but none have shown up with a picture while the call is actually ringing my phone.
Has Google removed caller ID pictures on incoming calls, or is there something else going on here?
Have other people seen this happen?
Click to expand...
Click to collapse
Hep happening with me as well.
Seems intermittent...
more often it doesnt display it.

tzuyang said:
Hep happening with me as well.
Seems intermittent...
more often it doesnt display it.
Click to expand...
Click to collapse
Alright, at least I'm not alone.
Figures there would never be a problem with something so basic before, but Lolliflop can't seem to manage it.

HI, just noticed that too.
I played with stock Phone app settings and it seems to fix it for me.
Tell me if it helped.
Tal

Only 2 other people?
How are more people not complaining about this?

I have the same issue. Since the update on my nex 4, this issue has been there. When i call, the photo shows but incoming calls dont show the photo. Its annoying. I hope there is a fix soon.
Sorry to post on nexus 5 thread as i couldnt find it on nexus 4 forum

It seems to be only if your phone is locked (PIN, Pattern, etc), if your phone is on, and unlocked the picture shows.

Only using slide unlock.
Never an issue before.

talsuk said:
HI, just noticed that too.
I played with stock Phone app settings and it seems to fix it for me.
Tell me if it helped.
Tal
Click to expand...
Click to collapse
What setting did you play with? Went through every settings and didn't see anything that could help.(and it didn't)

androidnr1 said:
What setting did you play with? Went through every settings and didn't see anything that could help.(and it didn't)
Click to expand...
Click to collapse
Yes this??

Same thing here, i flashed xTraSmooth 2.3.3 .
Sometimes the image appears, but usually it does not.... Very annoying

Hmm tried every setting . Cleared contact storage and cache still same thing..

Same thing for me
Sent from my Nexus 5 using XDA Free mobile app

256
Has anyone managed to find a solution?

Working fine for me, although I flashed the factory image and set my phone up from scratch

Even I flashed factory image and set up my device from scratch. But problem is there

Same thing for me. Did clean install and removed google account and back sign in again with no luck.

Have the same issue here.
Reimaging of the device didn't help.
This happening only on the locked device. While device is unlocked - picture appearing.
Using stock dialer and contacts applications.

Not yet. I've tried all kinds of things from disabling Google's Caller ID service, to setting new contact pictures for people, and I have so far been unable to make my caller ID pictures work reliably. I'll see it maybe one out of ten incoming calls. Extremely frustrating. My Moto Razr from 2004 could reliably display caller id pictures, but Lollipop seems unable to perform in the most basic of functions.

Same issue here. On factory image as well as a few different ROMs

Related

Text messages out of order

Anyone else experiencing their text threads being out of order? For instance, i can send a text that shows that it was sent at the right time, however if someone texts me, the time is a couple of minutes off. Thus, throwing the chronological order off.
If im reading and thinking of ur problem rite it may be the same as mine was. When i first send text sometimes it would fail and wouldnt resend till i reopen text. So it would have wrong time at least i thought it did.
chvybeatsford said:
If im reading and thinking of ur problem rite it may be the same as mine was. When i first send text sometimes it would fail and wouldnt resend till i reopen text. So it would have wrong time at least i thought it did.
Click to expand...
Click to collapse
No, my texts don't fail. When I send them, they show the same time as my clock. However, if someone sends me a text, it shows they sent it about a minute or two ahead of my actual time.
I'll try to give an example: 6:45PM- actual times that these text are sent.
Me (6:45PM)- aaaaaaaaaaaaaaaaaaa
Me (6:45PM)- ccccccccccccccccccc
Someone Else (6:46PM)- bbbbbbbbbbbbbbbbb
See, how it places the incoming texts at 6:46, even though it is really 6:45 still, throws the order off on my reply. It makes it seems like both of my texts were sent before I even received a response.
Very frustrating......
Are you having this problem in the stock messaging app? I noticed it every once in a while, but haven't had the problem yet with Handcent.
If you're using the stock app, try downloading Handcent or ChompSMS or something, and see if it goes away
i have this same issue, its made me switch to handcent because the problem hasnt occured using that. Plus it lets me have vibrate functionality ONLY in the vibrate setting and retain only audio notification in a sound profile
60HertzJig said:
Are you having this problem in the stock messaging app? I noticed it every once in a while, but haven't had the problem yet with Handcent.
If you're using the stock app, try downloading Handcent or ChompSMS or something, and see if it goes away
Click to expand...
Click to collapse
Yeah, I'm using the stock messaging app. I'll try Handcent, apparently a lot of people like it. I'll update ASAP
i'm still using my fuze and i have the same problem. i wonder if it has something to do with the time on att , the other persons phone and/or other carriers servers
Handcent all the way! It corrects the out-of-order issue and is way more customizable, including assigning ringtones for each contact. Just remember to turn off the notifications on the stock messaging app, otherwise you'll receive double notifications on each message received.
Im having the same problem on my Captivate...But my N1 gets it right. Im getting replys before I even send a text...according to the time stamps.
Sorry to report that, although ive only experienced it once, i have seen the same problem with Handcent SMS
All these little issues on this thing are starting to pile up :/
Intervenient said:
All these little issues on this thing are starting to pile up :/
Click to expand...
Click to collapse
But this is true, at least for me, for every device.
soul4rent said:
i'm still using my fuze and i have the same problem. i wonder if it has something to do with the time on att , the other persons phone and/or other carriers servers
Click to expand...
Click to collapse
No cuz my iPhone worked just fine...
This problem happens to me if I reply back really quickly... It'll put my text above the one I replied to.
Intervenient said:
All these little issues on this thing are starting to pile up :/
Click to expand...
Click to collapse
Beauty is there's ways around it (other apps) and we don't have to rely on anyone to fix it.
My wife and I both have Captivates. Her phone has the text messages out of order, while mine does not. Something we noticed is that when we do an auto sync of the date/time, her phone is consistently 4 minutes behind mine. For example, my time will be 6:06, and her phone says 6:02. I believe this is what is causing the text app to "re-arrange" the messages. The text app just looks at the time stamp of the message, and not the actual order of the send/receive process.
I am not sure how to correct this other than manually setting her phone forward by 4 minutes.
tikicult said:
The text app just looks at the time stamp of the message, and not the actual order of the send/receive process.
Click to expand...
Click to collapse
This is exactly the problem.
If I get a text at 9:01... And I reply at 9:01... It puts mine as having been sent before the one I received.
just use handcent people.
Yeah, but like I said, Ive reproduced the problem once, even with Handcent. On a side note, does anyone know how or where to get more skins for Handcent?
domin8 said:
just use handcent people.
Click to expand...
Click to collapse
That does not solve the root problem... Some phones are getting the wrong time from the network when set to auto-config.
tikicult said:
My wife and I both have Captivates. Her phone has the text messages out of order, while mine does not. Something we noticed is that when we do an auto sync of the date/time, her phone is consistently 4 minutes behind mine. For example, my time will be 6:06, and her phone says 6:02. I believe this is what is causing the text app to "re-arrange" the messages. The text app just looks at the time stamp of the message, and not the actual order of the send/receive process.
I am not sure how to correct this other than manually setting her phone forward by 4 minutes.
Click to expand...
Click to collapse
tikicult, somone else reported that their phone was off by 4 minutes. Solved it by getting a new SIM Card.
Guess I'm a new user so I can't post a link to the forum thread, but here is the url:
forum.xda-developers.com/showthread.php?p=7280990#post7280990
TexUs said:
This is exactly the problem.
If I get a text at 9:01... And I reply at 9:01... It puts mine as having been sent before the one I received.
Click to expand...
Click to collapse
I've been having this problem as well.
I went to the AT&T store today to try and get a new SIM, as per one of the suggestions in this thread. Problem still occurred. Tried it on a fresh straight out of the box Captivate. Problem still occurred. Sales guy threw his SIM from his iPhone in a demo Captivate. Problem still occurred on both Captivates.
Later I tried adjusting the time manually up by a minute or 2. Problem still occurred after a text with a response approx. 20-30 seconds later. Still showed the text coming in at 1:23, and my response which was 30 seconds later as being sent at 1:22.
Seems like a Samsung software issue.

[Q] Can't receive calls when phone is locked (Sense 3.0)

Hi guys
My girlfriend updated her UK unrooted stock O2 Desire S with the OTA update yesterday with no problems. However, since then, she has not been able to receive calls when the phone is in a locked state.
When the phone is unlocked, it goes to the screen with buttons at the bottom and is fine (call is answered, taken, hung up, no problem). However, when the phone is locked and the "rings" come up to answer or reject, the call is taken, the phone.android.process (I think) force close, the call is cancelled and signal is lost for a few moments before the phone returns to normal
I have tried pulling the battery and turning off fast boot, neither have helped.
Just wondering if anyone else has had these issues, and if so, is there a fix?
Cheers
boch501 said:
Hi guys
My girlfriend updated her UK unrooted stock O2 Desire S with the OTA update yesterday with no problems. However, since then, she has not been able to receive calls when the phone is in a locked state.
When the phone is unlocked, it goes to the screen with buttons at the bottom and is fine (call is answered, taken, hung up, no problem). However, when the phone is locked and the "rings" come up to answer or reject, the call is taken, the phone.android.process (I think) force close, the call is cancelled and signal is lost for a few moments before the phone returns to normal
I have tried pulling the battery and turning off fast boot, neither have helped.
Just wondering if anyone else has had these issues, and if so, is there a fix?
Cheers
Click to expand...
Click to collapse
go to the market and download and install the app called "no lock" this will disable the lockscreen.
although i do not know the main cause for your issue, this will be a temporary fix until you manage to sort it properlly
my friend has a similar problem,but only with one contact calling him - me
he added fb account (I left my number on my fb account) ,fb for htc account(both)
to his phone,so after mergin my 3 contact details or even 4,when I call him his phone goes FC,out of network,sd preparing etc,etc..so I just unlinked FB(only FB not FB for htc) from other contact details and thing sorted out. its a shot in the dark,but try something like this.
I have the same issue on my Desire S. Although my error message is "com.android.phone has stopped unexpectedly".
I am then forced to enter my 4-digit pincode for the SIM card.
So far I also think it is only when one person is calling me (he has a Legend, other frequent callers are Samsung old one, and Iphone 4, if it makes a difference).
Titties said:
I have the same issue on my Desire S. Although my error message is "com.android.phone has stopped unexpectedly".
I am then forced to enter my 4-digit pincode for the SIM card.
So far I also think it is only when one person is calling me (he has a Legend, other frequent callers are Samsung old one, and Iphone 4, if it makes a difference).
Click to expand...
Click to collapse
my friend has the same issue,pin and all that. but only when I call him. im usin desire s,its not the phone i think and im sure its coz of the facebook account and facebook for htc sense. as i already said,he has my number in phone and i have my number on mu fb profile,so when he sync all those accounts and link them into one contact thats when the trouble starts. when I call him phone gets fc and restarts (sort of) preparing sd and pin input. so after i unlink only contact detail thats synced from Facebook app,and call him then everything's ok,and the picture shown is from fb profile not the contact from phone. hope u get what im trying to say my english is not that good
djomla43 said:
my friend has the same issue,pin and all that. but only when I call him. im usin desire s,its not the phone i think and im sure its coz of the facebook account and facebook for htc sense. as i already said,he has my number in phone and i have my number on mu fb profile,so when he sync all those accounts and link them into one contact thats when the trouble starts. when I call him phone gets fc and restarts (sort of) preparing sd and pin input. so after i unlink only contact detail thats synced from Facebook app,and call him then everything's ok,and the picture shown is from fb profile not the contact from phone. hope u get what im trying to say my english is not that good
Click to expand...
Click to collapse
Thanks for the suggestion - I have now removed my phone number from my FB account, and unlinked my friend from syncing with FB in the contacts. I'll have him call me tomorrow to see if it works.
I'll let you know.
Titties said:
Thanks for the suggestion - I have now removed my phone number from my FB account, and unlinked my friend from syncing with FB in the contacts. I'll have him call me tomorrow to see if it works.
I'll let you know.
Click to expand...
Click to collapse
you are welcome friend,but you didn't have to remove your number,just unlink his fb contact from phone contact,and try,if the trouble goes on then we'll call Chuck Norris (just kiddin)
Update: unlinking my contact from FB did the trick. Thanks a lot for advise.
Titties said:
Update: unlinking my contact from FB did the trick. Thanks a lot for advise.
Click to expand...
Click to collapse
you are welcome,just hit the thanks button

[Q] SMS Issues

Hey guys,
I just got my OPO today and have been loving every bit of it, but it seems that my SMS isn't working correctly. I checked the APN settings multiple times and even tried some of the preset ones with no luck. My issue is that I can both receive SMS messages as well as send and receive MMS messages, but when it comes to sending an SMS, I get a "Message note sent. Touch to retry" message. I've tried both the default app AND Google Hangouts with no luck from either. It's not a huge issue because I use mostly group chats and my gf can use hangouts, but it's still incredibly frustrating. Do you guys have any hints or tricks I should try out? I seriously love this device, but I am going crazy over the SMS issue.
I'm running the stock CM11S rooted with TWRP 64GB model on AT&T. Mobile data, LTE, everything else works. Just not actually sending SMS. I thank you for the responses ahead of time.
Hey @Bliznade.. .i see you posted about this sms issue. I am also having exact same issue now with my oneplus. Did you manage to find a solution of your issue? If yes, then can you share it with me? It is driving me crazy.
OR if anyone else can help me here?
Guys, basically you have to get the apn that is used by AT&T. Idk if you already have that apn, but the preset ones are made for the T-Mobile bands not really AT&T as I know it.
Parvinder25 said:
Hey @Bliznade.. .i see you posted about this sms issue. I am also having exact same issue now with my oneplus. Did you manage to find a solution of your issue? If yes, then can you share it with me? It is driving me crazy.
OR if anyone else can help me here?
Click to expand...
Click to collapse
Yes, I was! It was actually Google Voice setting itself up wrong or something and after I factory reset my SMS/MMS was working fine. I turned off Google's auto-app-restore and installed only the apps I needed and one at a time, trying SMS inbetween, since I knew it HAD to be an app if it worked after a factory reset but didn't after setting up my phone. I'd say if you have Google Voice to uninstall it completely. Some setting in there messed up my phone. If you don't have Voice installed, honestly the best thing to do is factory reset and makes sure SMS is working, then install each app one at a time. I know it sounds like a lot but that's what worked for me.
If that doesn't work, this is what OnePlus's customer service had to say. It was seriously a lot of back and forth, and they were incredibly helpful, even if it didn't fix my issue, it might fix yours, so I'll post out conversation below:
Email with R (OnePlus) said:
Jacob K
Jul 20 09:34
I got my device today, the 64GB sandstone black, and put in my AT&T sim card. The phone worked as usual-or so I thought. My data works. 4g LTE on the wireless network, group MMS works, and I even receive SMS fine. But I'm not able to send out any SMS for some reason. I get left with a "Message not sent" notification. I tried this first with the stock app then tried Hangouts and neither worked. I checked my APN and everything seems to be correct. I'm just at a loss, as it's odd that I can receive both SMS and MMS and even send MMS but I can't send out SMS. Is there something I can do to resolve this?
R (OnePlus)
Jul 22 13:27
Hi Jacob,
Let's try a few things to help you solve your SMS problem.
First, turn off your OnePlus One, carefully remove the SIM tray, and then power on your OnePlus One. Let it finish booting up. Obviously it will say there is no SIM inserted, cause there isn't!
Next, turn off your OnePlus One again. Carefully put the SIM tray/card back in the same way you took it out and power on again. Give your phone a few minutes to register on the network and get settled. Now, try to send an SMS, see if it works.
If we are back to square one, I'm going to have to gather a bit more info. As you probably already know, this problem is typically APN related. Are you using the PTA APN on At&t?
Would you mind downloading an SMS app called Textra (free) to see if you can send an SMS using this app please? Let me know if any of this stuff works, or not. Thanks.
Jacob K
Jul 22
to OnePlus
Alright, I tried all of the steps you gave me and it didn't work, so I tried again waiting longer in between each step and no luck. I also tried Textra and upon hitting the send button got an immediate notification that the message failed. I realize this seems to be a very specific problem because I've searched all over the internet and I've come up with no solutions. I posted in multiple forums with just one reply from someone else with the same issue. But since putting the ticket in I've also tried inputting the correct AT&T SMSC in all 4 formats to no avail. Every time I press update and re-enter it goes back to the old, which is in fact one of the correct SMSC's for AT&T (the one in quotes) with a ,145 tailing it (not sure what that's for). But any information you need I'll be glad to provide, and I greatly appreciate your response. I've been living off of Facebook messages and group chats the last few days, haha.
R (OnePlus)
Jul 22 14:46
Hey Jacob,
Cool, thanks for enduring a little troubleshooting and glad you understand the language of tech. Just to remove another obvious layer of doubt, please make sure you have updated to the latest version of CM via OTA. The fact that you can receive SMS messages makes this an interesting puzzle to solve.
For our next attempt, we will try something a little more drastic before I ultimately suggest a factory reset, but lets put that on the back burner for now.
Go to settings/apps and then swipe right 2 times to reach the 'All' category
For each of these apps: Phone/Messaging Storage , Messaging , Hangouts , and com.android.smspush
Perform this process: Force stop, Clear cache, Clear data
Do a restart when you are done and fire off an SMS when you are rebooted to a stable state. Any luck?
Jacob K
Jul 22
to OnePlus
Alright, no luck with that either, so I just sucked it up and did a factory reset. I tried sending an SMS immediately after and it worked, so I thought I was good. But then after I allowed Google to install all of my old apps, I tried it again and no luck. But I did notice when Google Voice installed, CM asked me if I wanted to use Voice+ (or something along those lines) and I said yes, chose my Gmail and allowed it to access my G+ info, but after that it asked me which email to use again and wouldn't go away until I clicked out of it. Then I had to swipe the notification away, so I figured Voice might be the culprit, uninstalled and voila, working SMS.
So maybe something in the Voice settings was messing things up, or maybe the CM Voice+ thing messed it up since it worked fine on my old phone. Not sure, but I'm happy to have fixed it. Everything works great now! And even though we weren't able to fix the problem through the troubleshooting steps you provided, I realize this was a difficult and very specific and local issue.
[insert nerdy thank you note here]
Click to expand...
Click to collapse
Bliznade said:
Yes, I was! It was actually Google Voice setting itself up wrong or something and after I factory reset my SMS/MMS was working fine. I turned off Google's auto-app-restore and installed only the apps I needed and one at a time, trying SMS inbetween, since I knew it HAD to be an app if it worked after a factory reset but didn't after setting up my phone. I'd say if you have Google Voice to uninstall it completely. Some setting in there messed up my phone. If you don't have Voice installed, honestly the best thing to do is factory reset and makes sure SMS is working, then install each app one at a time. I know it sounds like a lot but that's what worked for me.
If that doesn't work, this is what OnePlus's customer service had to say. It was seriously a lot of back and forth, and they were incredibly helpful, even if it didn't fix my issue, it might fix yours, so I'll post out conversation below:
Click to expand...
Click to collapse
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Parvinder25 said:
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks.. Didn't find that setting but uninstall works perfect.
Sent from my A0001 using XDA Free mobile app
Parvinder25 said:
Well I got to know the real reason behind it. It is Google voice but you don't need to uninstall it.
When you install Google install, there's an extra setting of voice+ in connection settings. (click more in connection settings to get it). If you enable voice+ which then says it'll use Google voice to send all sms from handset, then your sms won't work. If you disable it, then sms work fine just as before.
So no factory reset or uninstall of Google voice is required. Uninstall of Google voice worked bcoz it removes that voice+ setting as well.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Parvinder25: Could you perhaps elaborate on exactly where these "connection settings" are located? I could not find them anywhere within the Google Voice app. I'd like to keep using GV for its visual voicemail feature, however it seems to completely disable my ability to send MMS messages (although they do send after GV is uninstalled). I've located a toggle to receive text messages either within google or through the messaging app, however the messaging app was already selected. That would be the only toggle I could locate within GV that remotely relates to messaging. Thanks in advance.
Hello Parvinder,
It was glad that you have resolved this issue, i am also facing similar issue with my One Plus One mobile - MESSAGING. I am using AT&T network. I couldn't fine Google Voice+ in the apps or settings. I can just see Google Voice but, i am not able to find which setting needs to be disabled or Uninstalled? Could you please provide exact navigation for the same would be great help for me and other users on this blog.
Appreciate your help.
Thanks,
Venki

Can't Answer or Make Calls

So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou
It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.
Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon
I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.
The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.
Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.
Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!

Question Microphone not working for some specific apps

Hi,
I've got a problem. Suddenly a couple of apps won't recognize any sound when using the microphone, e.g. WhatsApp. When I want to record a WhatsApp voice message the app does not record any sound. The sent message is completely silent. Strangely it does work when the screen recorder is running, presumably because the microphone is activated by the recorder. Has anybody an idea why that could happen? It worked till a couple of days ago.
I am on the current Android 12 Version on the latest patch (01.05.).
Thanks!
This is a guess. WhatsApp may have lost the "Allow Use Microphone" permission.
Newer versions of Android can revoke permissions if it wants.
Usually in Settings there is an App Permissions option. Or, long-click the icon and press the "I" for information. You may be able to view/set permissions from there.
This is only a guess - where I would look first.
Sorry, I forgot to mention, that it does have the permission to use the microphone.
WhatsApp Calls, Video recording, ... do work. The problem only occures with voice messages.
As I said, WhatsApp isn't the only App that does not work, there are a couple more, that all the sudden so not recognize the microphone anymore.
I had similar problem with my zflip 3 . I sugest you to make a diagnostic with the samsung members aplication. My secundary microphone was broken , so I had to replace the charging port card (sub pba) .
I don't have a solution but this exact thing, has just happened to me today too! You are the first person I've found with the same problem! Have you heard anything yet? Or had any luck? I've gone as far as to do a full factory reset and still nothing.
Were you able to fix it?
I'm also on Android 12.
Rayrsn said:
Were you able to fix it?
I'm also on Android 12.
Click to expand...
Click to collapse
Nope still broken. Samsung have offered to look at it under warranty but would need it for 2 weeks so I'm waiting until that's viable!

Categories

Resources