Related
[SOLVED]
I can not get into the phone call (green phone button) to the dialer, this is the main problem; when I open it, it hangs for a few seconds then I get a message box centered in the middle of the screen: Contacts has stopped. - only OK button to press; and pressing returns to homescreen.
Everytime after sending an SMS I get: "messaging has stopped", although still I can send.
I can access the contacts normally and also everything else is fine. when I start calling someone from there, it works also fine, with the resemling dialer(?) look while talking. But then right after finishing call, again a message pops up: com.android.phone has stopped
- resulting that the calls are not being logged.
the app "GO Contacts Ex" would be ok as an alternative, but here again, after the call ends, the message comes up: com.android.phone has stopped. also other apps like contact+/dialer+ and exDialer&contacts seem like that all using somehow com.android.phone in the end and causing that error message box coming up.
if no fix, is there an alternative app totally replacing the usage of com.android.phone? so that I could use another app?
I have found and tried some suggestions from google to this problem, but none of them helped..
deleting cache in: apps -> all -> contacts memory and contacts and phone, & reboot; - several tries, also SIM card out, and reloads, re-sync;
uninstalled recent updated apps; reboots, sim out, re sync etc.
It seems like there is one small thing interrupting but I can be wrong.
I dont wish to do a factory reset first, and lose all my apps and settings. Before doing that desperately, I would like know if someone could help me out in here? It could be one small setting or stuff to do
I am using JB 4.1.2 rooted
it is possible that I disabled some important processes earlier which caused that, but I enabled them all again and restarted, still nothing changed. otherwise this problem started surely after recent app updates, which i also tried undone and checked
any help is appreciated!
SOLUTION
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. Activate these apps. Reboot again.
Another reason for "com.android.phone has stopped" coming up is when you previously deactivated com.movial.ipprovider, or if it is damaged, which is needed to connect to the internet. The error starts coming permanently as soon the phone trys to connect to the internet.
Solution: just stop com.movial.ipprovider, delete its cache and reboot! (or reinstall it)
I can avoid the first two problems (contacts and messaging has stopped) by simply using a different app which I at least like better (Dialer+ / Contacts+ including sms), and have deactivated the stock versions now (contact and messaging). - and I am happy with that!
the problem with com.android.phone still remains after each call, for both incoming and outgoing. the bothering thing is that error message box, and that the calls are not being logged at all, but sms messages are logged fine.
(I could not find any app that could be an alternative to this com.android.phone, similar to the contacts and messages app. all the 3rd party caller and dialer apps uses com.android.phone in the end when dialing. if i uninstall com.android.phone, there is only skype as an alternative to call. and uninstalling skype gives then no possible ways to call a number. so I need to fix this somehow.)
problems:
1. message "the process com.android.phone has stopped" after every calls.
2. no calls are logged
please find attached a logcat logs when that happens, maybe someone can understand what is causing this (look for com.android.phone).
what is for example E ActivityThread: Failed to find provider info for logs ?
and what can you suggest me?
I got it !!!
I searched and located the file on where the calls logs are being saved: data/data/com.sec.android.provider.logsprovider/databases/logs.db
As I thought it could be damaged. I cleared the cache from LogsProvider and restarted it, and the error is now gone since then!
But clearing also deleted all the files in its folder including the logs.db. Unfortunately it doesnt recreate this files, even after a reboot. How can I get these structure and basic files again?
Can someone copy this for me? or can I use any logprovider files from internet?...
will check ...
SOLVED !!!!
after reactivating Contacts & Phone, also a brand new folder structure with logs.db was recreated automatically !!!!!
Everything is running smoothly now!!! yay!!!
Just FYI and to summarize, in case it happens to you. it was either logs.db file or something in logsprovider folder damaged.
SOLUTION: just stopped com.android.phone and logsprovider service, and deleted the cache from both. then reactivating them should be ok! then just reboot!
cheers
You mention this "reactivating" step. Can you explain more about how to do this part?
kenkamm said:
You mention this "reactivating" step. Can you explain more about how to do this part?
Click to expand...
Click to collapse
Hello Kenkamm,
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. And activate these apps. Edit: reboot again.
esilence said:
Hello Kenkamm,
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. And activate these apps again.
Click to expand...
Click to collapse
Thanks! Next time I feel brave and re install xposed I will give this try.
kenkamm said:
Thanks! Next time I feel brave and re install xposed I will give this try.
Click to expand...
Click to collapse
I forgot to mention, also after the 2nd step you need to reboot.
THANK YOU!!!!
esilence said:
I forgot to mention, also after the 2nd step you need to reboot.
Click to expand...
Click to collapse
OMG, I've been dealing with that darn com.android.phone error for nearly a year now ==== and you solved it for me!!! I can't tell you how happy and thankful I am. After every call in/outbound I would get that pesky error! NOW I'M FREE AGAIN!!!!! WOOO HOOOO!!!
I am glad that I could help! you obviously just joined and posted because of me to tell about this.. thank you
Namecards cannot be shared
esilence said:
[SOLVED]
SOLUTION
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. Activate these apps. Reboot again.
Another reason for "com.android.phone has stopped" coming up is when you previously deactivated com.movial.ipprovider, or if it is damaged, which is needed to connect to the internet. The error starts coming permanently as soon the phone trys to connect to the internet.
Solution: just stop com.movial.ipprovider, delete its cache and reboot! (or reinstall it)
Click to expand...
Click to collapse
I was looking at this and hoping these drastic moves could fix the reason I cannot share my contacts using the share command. It force closes afterwards.
Sadly, I've tried all of this and my contacts still cannot share. So you have any idea what could be wrong with my Galaxy S Relay? I am rooted (but using stock 4.1.2) at this time, and have only removed bloatware such as Evernote, Slacker, etc.
Thank you !!
esilence said:
Hello Kenkamm,
1. Just stop and deactivate the apps "phone", "contacts" as well as the "logsprovider". And delete each caches.
2. Reboot. And activate these apps. Edit: reboot again.
Click to expand...
Click to collapse
Worked like a charm on Samsung S5 Mini.
sorry @furboom1240 i missed that topic here and didnt see your message earlier. but i have no idea what could have solved your issue either. it relates to something else i guess, hope u had luck in the meantime and solved
@DeViBos thanks another new user and first post, i appreciate! welcome to xda and have fun
Is it possible to try this method to other brand like HTC example? Because Phone can't force stop and there's no logsprovider. Where it can be found?
Just as I will do now. Thank you sooooo much I thot my phone was a hacked mess. The world just became a better place!
Same problem on my Redmi 1S
esilence said:
I got it !!!
I searched and located the file on where the calls logs are being saved: data/data/com.sec.android.provider.logsprovider/databases/logs.db
As I thought it could be damaged. I cleared the cache from LogsProvider and restarted it, and the error is now gone since then!
But clearing also deleted all the files in its folder including the logs.db. Unfortunately it doesnt recreate this files, even after a reboot. How can I get these structure and basic files again?
Can someone copy this for me? or can I use any logprovider files from internet?...
will check ...
Click to expand...
Click to collapse
Sorry for waking an old thread. I am facing a similar problem.
My Device is -
Xiaomi Redmi 1SW (Rooted)
Android 4.4.4
MIUI 7.2.3.0 KHCMIDA
I have removed all bloatware as mentioned in this post (http://forum.xda-developers.com/xia...-to-remove-bloatware-list-miui-t2999283/page2) and also another app called 'Xiaomi Service Framework' if these are causing the problem.
I was earlier facing this problem when I was using MIUI 7.1.1.0 KHCMICH (Rooted and Xposed installed). It suddenly started occurring as soon as I connected my phone to the PC before even doing anything. The pop-ups (Unfortunately Phone has stopped) became irritating. Luckily, I had USB debugging enabled. I connected the phone to the computer and put the following in the CMD -
adb devices
adb shell
su
pm disable com.android.phone
exit
exit
exit
Then the window stopped appearing. So I (mark this) turned off Wi-Fi and disconnected phone from PC. I was using the phone normally for few hours. But I realized that outgoing calls on my phone were not possible (the system dialer (com.android.contacts) closed after pressing the call button) and no incoming calls were being recorded (I use the in-built call record feature in the system dialer app). So I connected my phone back to the computer and wrote
pm enable com.android.phone
in place of pm disable com.android.phone keeping all above mentioned commands same.
This time the window did not appear. I was able to make and record calls perfectly. But on the same day, when I again switched on Wi-Fi, the window started reappearing. So I used my device by keeping the com.android.phone disabled for few days.
After few days, I got an OTA update to MIUI 7.2.3.0 KHCMIDA. I thought it would solve the problem.
I also wanted to reset my device because it had lot of junk. So, I flashed the update, rooted the device, removed all bloatware apps again (which came after the update) and shut down my phone. The error window hadn't appeared yet though com.android.phone was enabled and Wi-Fi was connected.
Then I booted into recovery and erased the cache and data partitions (NOT the internal storage). Then after phone was booted and as soon as all setup was done, the error window started coming up again.
So, I don't think that data/data/com.sec.android.provider.logsprovider/databases/logs.db has any problem because it was erased completely after I wiped data.
I need HELP !!!
I get the same message (com.android.phone and a few others) over and over again and my phone is veeeeery slow. It all started after I put my SIM-card into the phone for the first time. I have an S7 with SuperMan-ROM installed. I can't deactivate my "contacts", it just doesn't let me push the deactivate-button. Plus I can't find the phone-app or logsprovider. Is there a different appmanager apart from the stock which I could use to delete and deactivate?
Hi
i have problem in samsung j5 2016 regarding com.android.phone has been stop this message shown after each second and also not showing mobile network
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
First issue is app badges. When i read message or check missing calls whatever it is general issue, the notification badge on app icon does not reset it self. Badge keeps as it is for 1 hour and then reset. Tried clearing badge provider but no solutuon.
Cant install apps from google play normally, it downloads to %100 and stays as it is. When i kill the google play and restart it then it installs the app.
Randomly getting really laggy with device.
When i am on call with bluetooth headphone and using my device, the device gets laggy. Cant switch wifi or install apps. Its like device gets my actions but does not proceed. When i end calls it starts proceed my actions one by one.
Tried factory reset, reinstalling stock firmware, all same. My device is stock and never rooted.
Btw, I see touchwiz update on sammobile but neither samsung apps or google play does not update the launcher. I try to install the apk from sammobile manually but it gives error like i have an app as same name as it is. So cant update to last version of touchwiz i stuck at 6.1.02
Any help for these issues or explinations? Thanks.
Is your device snapdragon version?
Sent from my SM-G955F using Tapatalk
emremutlu said:
First issue is app badges. When i read message or check missing calls whatever it is general issue, the notification badge on app icon does not reset it self. Badge keeps as it is for 1 hour and then reset. Tried clearing badge provider but no solutuon.
Click to expand...
Click to collapse
I hate this, only choice is either install a new launcher or long press the icon and select "clear badge."
emremutlu said:
Cant install apps from google play normally, it downloads to %100 and stays as it is. When i kill the google play and restart it then it installs the app.
Click to expand...
Click to collapse
Not sure, it hasn't happened on my phone sorry.
emremutlu said:
Randomly getting really laggy with device.
Click to expand...
Click to collapse
Not sure, it's something that generally happens with Samsung devices.
emremutlu said:
When i am on call with bluetooth headphone and using my device, the device gets laggy. Cant switch wifi or install apps. Its like device gets my actions but does not proceed. When i end calls it starts proceed my actions one by one.
Click to expand...
Click to collapse
Odd, I haven't seen that before.
emremutlu said:
Tried factory reset, reinstalling stock firmware, all same. My device is stock and never rooted.
Btw, I see touchwiz update on sammobile but neither samsung apps or google play does not update the launcher. I try to install the apk from sammobile manually but it gives error like i have an app as same name as it is. So cant update to last version of touchwiz i stuck at 6.1.02
Any help for these issues or explinations? Thanks.
Click to expand...
Click to collapse
You tried everything, could be a hardware issue. As for the touchwiz update, it could be for a different version then yours. I wouldn't be worried if you don't see the update unless your seeing other people with the sane phone get the updates.
Sent from my SM-G955F using Tapatalk
None issue you mentioned I face it, by the way mine is Exynos edition.
Suggest Factory reset your phone, don't restore anything (this part is freaking important). Start as flash new phone setup.
As for Touchwiz, 6.1.02 is the latest version.
Snapdragon here, none of these issues are present on my device.
Exynos here. I did not facr these issues until last firmware update. After factory reset it was awsome for 1 week. Then again here my problems.
I highly suggest to return the phone to samsung and get a new one.. your phone seems to have a hardware issues.
I only have the common issues which is fingerprint sensor stops working sometimes. I never tried bluetooth so i can't confirm if i have any.
As many here also suggest that you should start fresh factory reset your phone and install your apps directly from the play store. If you had any problems with the playstore don't bather your self to fix the problem go directly to nearest samsung center and ask for an exchange unit.
Sent from my SM-G955F using Tapatalk
Snap dragon here and I have no clue what these problems are....thank goodness of course
Use Nova launcher. Problem solved.
Galaxy S8+ Black
clear cache from the boot menu. May help before you return it.
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!
I am desperate, I can't find the issue here. I have a S10 (Xfinity unlocked on Verizon) , I can't seem to update apps, they get stuck at 100% or 99%, AND some things like Gmail and Instagram do not seem to notify that I am getting messages.
Here's the kicker, I factory reset the phone some 5 times now, and still have the issue. The Reset fixes it for a few days (if even a day) and then the issue starts up again!
the phone was just upgraded to 10, but it was happening on 9 also!
no clue what the problem is ! it kills me! Please anyone have any idea? I even had an authorized Samsung dealer do a "software refresh" and then wiped out the phone again, and I'm still having the same issue..
HELP! please.
thank you
eatonjb said:
I am desperate, I can't find the issue here. I have a S10 (Xfinity unlocked on Verizon) , I can't seem to update apps, they get stuck at 100% or 99%, AND some things like Gmail and Instagram do not seem to notify that I am getting messages.
Here's the kicker, I factory reset the phone some 5 times now, and still have the issue. The Reset fixes it for a few days (if even a day) and then the issue starts up again!
the phone was just upgraded to 10, but it was happening on 9 also!
no clue what the problem is ! it kills me! Please anyone have any idea? I even had an authorized Samsung dealer do a "software refresh" and then wiped out the phone again, and I'm still having the same issue..
HELP! please.
thank you
Click to expand...
Click to collapse
Boot into safe mode, it will only load your system apps and not your user apps. Then try to update your apps, if it works then you know the issue is being cause one of your user apps. Then you just need to identify which user app is the offending app.
It also might be caused by a conflict between various settings or maybe you have some things disabled or turned off that are causing this.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Boot into safe mode, it will only load your system apps and not your user apps. Then try to update your apps, if it works then you know the issue is being cause one of your user apps. Then you just need to identify which user app is the offending app.
It also might be caused by a conflict between various settings or maybe you have some things disabled or turned off that are causing this.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
That kinda works.. but again, as said, I have reloaded the phone over and over, and it works fine, until a few days later and stars over.. And updating is not the only problem, Geolocating is slow, sluggish or not working sometimes, Push updates of emails are slower or not happening. just weird things..
I am not sure what it could be! its like the phone is the problem!
eatonjb said:
That kinda works.. but again, as said, I have reloaded the phone over and over, and it works fine, until a few days later and stars over.. And updating is not the only problem, Geolocating is slow, sluggish or not working sometimes, Push updates of emails are slower or not happening. just weird things..
I am not sure what it could be! its like the phone is the problem!
Click to expand...
Click to collapse
Ok, everything I posted went completely over your head, I'll try again.
If it is working like it is supposed to while in safe mode(which is only loaded with system apps and system settings and not any of your user apps or data) that tells you that the issue is caused by some user app that you have installed or something in your user settings. In other other words, it is very likely something that you, as the user, have installed or setup/selected, it is probably not the device. It keeps happening after resetting because you are not changing what you are doing that it is causing it, it is something that you keep returning to after resetting the device. You just need to figure out which user app is causing the issue or whatever settings are causing the issue.
The way to do that will be trial and error. Uninstall one of the apps that you have installed, then use the device for a few hours, if the issue continues, that wasn't the app causing the issue, reinstall that app then choose another user app to uninstall and then use the device for a few hours, if the issue continues, that is t the app, reinstall that app, and so on and so on, etc... Get the picture? When you uninstall an app and the issue stops, the last app uninstalled is probably the app causing the issue.
I suggest resetting the device again. Then, only install one of your usual apps but don't install any others and don't change any settings, use the device a while, if the issue does not occur, install another one of your usual apps but don't install any others, basically, install one app at a time until the issue occurs, when it does, the last app installed is probably the offending app.
Or, if you don't find it that way and you get all of your usual apps installed without triggering the issue during the trial and error process, then you need to go through settings by trial and error. Changing one setting at a time and using the device a while to see if the issue occurs, if it does, it probably has something to do with the last setting that you changed before the issue occured.
Slowly changing one thing at a time over an extended amount with time between each change, will allow you to isolate exactly which app or setting is causing the issue.
Or maybe you need to flash your stock firmware via PC tools to start over with a clean installation.
Sent from my SM-S767VL using Tapatalk