Database Info

Lollipop Caller ID Pictures on Incoming Call?

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

Google Voice Calling

I use Google Voice as my main phone number and I never had a problem just installing the Google app and having my calls routed through it, but on this phone a get a "Call Not Sent" error. I searched and it seems this is an issue with other Huawei phones, but didn't find any solution. Any ideas?

Can anyone test to confirm it's an issue? Would flashing a Gapps package help?

maybe, cuz flashing gapps package would make them system apps. just make sure u have enough space left on your system partition...
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

I deleted some system apps and installed open gapps mini. No luck, still getting the same error. Is it possible to replace the phone apk (not dialer), or is that too tied to the hardware?
I've been using the phone for a couple days now, and I'd hate to give it for such a small (but fundamental) bug...

I found a solution: make Google voice a system app

adriangb said:
I found a solution: make Google voice a system app
Click to expand...
Click to collapse
please explain
i still can't figure it out

Actually it may have been a fluke... I placed one single call and confirmed with the other party it was my Google voice number. Now it isn't working again.

I think I may have fixed it. I copied in some telecom files from AOSP. So far I'm like 5 calls and 2 reboots in and it's holding. I'm going to try to update to the new L-29 OTA, root and then follow the same process. If it works, I'll post the ROM. If it's like what I'm on right now, it's a very nice mix of EMUI and AOSP since most of the Huawei stuff is gone, except some of the handy features, and all the Google stuff is loaded and working.

maybe you could also include a howto, which files to add where so that others may cook up their own emui/aosp mix
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

To be honest, I'm really not 100% sure, I kind of brute forced through the testing. What I do know: replacing a couple telecom framework and binaries from the 6P factory image (figured might as well use this), and installing Google voice as a system app, I have gotten it to work every time (for me) as long as it is set to prompt for every call. If set to "use Google voice for all calls", it breaks. My guess is it's a timing issue (emui telecom not giving Google voice the time it needs to make the connection).
I'll attach the ZIP file with all of the telecom components I used (NOTE THAT USING PRIV-APP COMPONENTS -IE TELECOM.APK, SEEMS TO CAUSE A BOOTLOOP).
Also, here is a link to my TWRP backup of my current system. It is 152 with a full Gapps package, Google voice as a system app and the telecom components Frankensteined in. Hopefully it will work on your devices, but just in case it bricks it I won't be giving out my address, least I get picketed
https://drive.google.com/a/adriangb.com/file/d/0B8hgJSh5NMsLVGpicmEwdWpDb00/view?usp=docslist_api

Still no real solution. The ask every time trick works without having to do anything with making Google Voice a system app and it only works 90% of the time.

Can anyone else confirm this issue? I'm discussing it with the vendor I purchased from, they're claiming it works perfectly

adriangb said:
I use Google Voice as my main phone number and I never had a problem just installing the Google app and having my calls routed through it, but on this phone a get a "Call Not Sent" error. I searched and it seems this is an issue with other Huawei phones, but didn't find any solution. Any ideas?
Click to expand...
Click to collapse
This is an old post with little activity, and yet I have this same problem. I have tried all the app setting and permissions, the battery setting etc, but the Mate 8 seems incompatible with Google Voice. The app install fine, sets up normally, and incoming calls to my Google Voice number work. It is just dialing out. All dials get the message "call not sent" and the dialer screen returns to befor the call was placed. The log also does not show an attempted call. I have tried alternative dialers from the play store, but none work. Has anyone solved this, or are there just very few people using Google Voice with this particular phone.

I've been having this same issue and have had the best results just setting it to "ask every time", no other tricks needed.

joburgslim said:
This is an old post with little activity, and yet I have this same problem. I have tried all the app setting and permissions, the battery setting etc, but the Mate 8 seems incompatible with Google Voice. The app install fine, sets up normally, and incoming calls to my Google Voice number work. It is just dialing out. All dials get the message "call not sent" and the dialer screen returns to befor the call was placed. The log also does not show an attempted call. I have tried alternative dialers from the play store, but none work. Has anyone solved this, or are there just very few people using Google Voice with this particular phone.
Click to expand...
Click to collapse
This is broken on the mate 9 as well

Anything on this? i just got a mate 8 and am having the same damned issue.

Phone (app) keeps stopping...

When I go to make a phone call with the Galaxy S8+, the contacts part of the app runs fine, I can select a contact and then click call.
But once the call starts I get the message 'Phone has stopped' & 'Phone keeps stopping', and there is no way for me to end the call...
I have tried booting into safe mode and making a call, but I get the same issue...
Is anyone else experiencing this?
*FIXED*
Uninstall the updates for the package 'com.samsung.android.incallui'.

SmilerOnline said:
When I go to make a phone call with the Galaxy S8+, the contacts part of the app runs fine, I can select a contact and then click call.
But once the call starts I get the message 'Phone has stopped' & 'Phone keeps stopping', and there is no way for me to end the call...
I have tried booting into safe mode and making a call, but I get the same issue...
Is anyone else experiencing this?
Or does anyone know how to fix this?
Click to expand...
Click to collapse
That sounds strange. Never encountered such a behavior on my S8+

SmilerOnline said:
When I go to make a phone call with the Galaxy S8+, the contacts part of the app runs fine, I can select a contact and then click call.
But once the call starts I get the message 'Phone has stopped' & 'Phone keeps stopping', and there is no way for me to end the call...
I have tried booting into safe mode and making a call, but I get the same issue...
Is anyone else experiencing this?
Or does anyone know how to fix this?
Click to expand...
Click to collapse
What version of the phone app are you using?
Do mention other details as well like Exynos or SD, and whether it's a WiFi call, VoLTE or just an ordinary phone call.

I had the same issue a couple weeks after updating the phone or contacts app with an apk file, cant remember which one it was.
Stranger thing was that when I wanted to make a call it actually did make the call while the popup was there that phone app was closed.
As I was not able to uninstall the update I did a factory reset of my S8+. Same issue was there after the reset, I ended up doing a clean flash with odin. Everything is fine now.

thuglife said:
I had the same issue a couple weeks after updating the phone or contacts app with an apk file, cant remember which one it was.
Stranger thing was that when I wanted to make a call it actually did make the call while the popup was there that phone app was closed.
As I was not able to uninstall the update I did a factory reset of my S8+. Same issue was there after the reset, I ended up doing a clean flash with odin. Everything is fine now.
Click to expand...
Click to collapse
That may have been what has happened to me, as I updated the phone/contacts apk's a few weeks back...
Thanks guys!
I'm guessing that I am going to need to find the default apk and restore it (com.android.phone)

*UPDATE/FIXED*
Just in case this affects anyone in the future.
I fixed it by using 'Package disabler pro' to uninstall the updates for the package 'com.samsung.android.incallui'.
I figured it out by monitoring the logcat (to monitor background errors from the developer tools), and I spotted that the error was coming from this package, so after removing all updates for it, now all works fine again.
I hope that this will save anyone from having to re-flash in the future!
I just used PDP to uninstall it as I find that tool to be quite effective at showing all info needed about the package before making any changes, but I'm sure that you can remove the updates with any other app!
@thuglife:
You may want to take note just in case it happens again in the future!

Pixel calls silent on both ends

My Pixel suddenly stopped being able to make and receive phone calls a few days ago. The Phone app is extremely sluggish trying to make a call, will usually finally "connect" and look like the call is open, but I hear nothing but silence on the other side, and the other person can't hear me. It's slow to try and hang up, too. I see calls coming in, and can try and answer, but with the same result. Missed calls are registered. Voicemail also does not work. I can see there is a message, but can't play it.
Running 8.1 with February 5 security patch. Carrier is Verizon. I've gone in the store, and they switched out the SIM card. I've also tried a hard factory reset, all with no difference to the problem. The phone is over a year old, so I think a replacement is not possible...
If anyone can help me or has any ideas, I would greatly appreciate it! Thanks!

It's a hardware problem, Google is aware of the problem, they should replace your device. Contact Google, even if you are out of warranty they will replace the device for you!

OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPOPRT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH, is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issue. I really DOUBT its a 3rd party app.

Thanks for your replies. I've contacted Google, and they didn't seem to think it was justification for replacing the phone out of warranty. They said I could either take it to a repair place to fix it or trade it in for the new Pixel 2 and get some money for it.
The workaround for answering calls works to connect the call and start the timer, but I still can't hear the caller and they can't hear me...
I still after much troubleshooting have found no way in which calls are functional. In addition to the attempts made above, I've since tried to uninstall and reinstall the phone app, and also to install a different phone app. No change to the problem. Even more curious, the problem still persists in Safe Mode.
If anyone has any more ideas, I'm all ears! Thanks!

No Sound on video recording

Went to a gig last night, tried to record some of the songs, got back today and none of them have any sound at all on the videos, anyone have any ideas why this could be

Did you play the videos on the phone or on a PC ?
I sometimes get a very low sound level on the PC while the sound is normal on the phone, depending on the phone used to capture the video and the software to play it back.

There have been a couple of reports of the same problem on a German Android forum. They said the for the last few weeks theyve been having trouble with recordings of all sorts, while speaking on the phone still works. After a restart it's all back to normal for some time but then the problem returns at some point. Sounds to me as if either an app or system update contains a bug of some sort...

have the same problem for about 3 weeks.
even with the C72 now no improvement.
very annoying the whole

In there forum I mentioned someone said according to Oppo Google Assistant is the culprit, it somehow blocks the microphone which is also why the OK Google command still works while sound recording does not. Try deleting the Google App's data and cache and then it should be gone. Should it be back after a while then the app will probably have to be fixed by Google, only way around this in this case probably is deactivating the assistant until the issue's been fixed.