Related
Sent from my PC36100 using XDA App
Just thought this would be a good idea for all of us having voicemail problems.
Post solutions and comments on developing a fix here instead of clogging up the cyanogen thread.
PS the spiicytuna method posted on page one of cyanogen does nothing to fix the 9016 issue.
Sent from my PC36100 using XDA App
Call the number included in the text you get. It will ask you if you have a sms voivemail phone or smth. Press one for no, and you stop getting the texts.
/fixed
MediocreHippie said:
Call the number included in the text you get. It will ask you if you have a sms voivemail phone or smth. Press one for no, and you stop getting the texts.
/fixed
Click to expand...
Click to collapse
Tried that. You get a new text telling you to call a certain number to retrieve your voice mail.
Blacklist the number?
One way around it
Well. It seems you can go to Sprint and block the text message at the source. Just log into your account and add them to your block list.
Will have a voice mail sent to me and see if it works. I've read in other forums that it can take a month to work.
-JZ
Update: Blocking 9016 did NOT work. My VVM updates, but I still get the annoying texts.
Any suggestions?
im not sure what that 9016 issue is but i do have a voicemail notification issue so i will speak of that
the sms you receve can be avoided while messing with ur settings in google voice online... when u click edit on ur mobile number there are options to uncheck sms notifications as well as transcriptions.. mess with ur settings and that fixes that issue, now onto the annoying one...
the way that i have figured out how to temporarly remove the icon is to flash whatever the latest nightly build is using rom manager and the use the option to wipe and adding the google apps, i then wait for my phone to reboot and let rom manager do its thang then as soon as i put in all my gmail information i wait till the menu starts to pop up then quickly press menu, call settings, voicemail number then change that *86 to my 10 digit phone number then press okay then i quickly change my carrier to google voice then go through all of those settings quickly till i click finish then press okay even though i may get that error that says something like my carrier doesnt support google voice or whatever it is then i go back to the carrier option and even though google voice is already selected i click google voice again and it tells me that my number has changed... no more voicemail notification UNTIL i reboot my phone, so any new fix that maybe come out involving any other issue i choose to ignore if it means that i have to reboot my phone... also a good thing to know is once u have success of finally getting rid of the icon whenever a new build is released just install it using rom manager once again but this time DO NOT select the wipe option and rom manager will install the latest build without the voicemail icon and all ur settings will be good to go right after the install however the same rules still apply, one u reboot it will come back, so after installing the latest build just dont wipe and dont reboot after all is said and done...
even though some tard thinks me mentioning *86 as the issue is me "wasting bandwidth" i feel that that is where the issue is.. this is the only rom that i have to change the carrier settings right off the bat instead of defaulting to our sprint voicemail... im not saying im *****ing about the issue in any way but this is an issue ive been having so i thought i would mention that...
now onto things ive tried that never worked....
ive tried just keeping my sprint number as the default but that never works, my only solution has been changing to google voice quickly...
ive called myself exactly 10 times and left myself voicemail messages, then after installing the latest nightly ive change to my voicemail number to sprints and deleted all 10 msgs and that did nothing...
ive gone into the application settings and deleted the phone data cache then quickly change to google voice without success, even after changing the settings i quickly pulled my battery and then started my phone so that it would default to googlevoice and still nothing...
since rom manager has worked for me as a temp fix ive tried doing all the same stuff using ar recovery doing all wipes and whatever else is possible without success, rom manager is the only one that works for me so i just stick to that...
and for those that say the google voice is too hard to setup its really not, just quit being lazy and do ur initial setup through google.com/voice and get urself a number and play with ur settings in there and when ur done with that then start the tutorial up top
i never had this issue until went from a cm6 nightly to zenfx2.2 to update my prl then I nandroided back and now i get these texts every 5 min
I think you guys should think of using Google Voice... Unless I am misunderstanding something, this is a Sprint VVM problem right?
Jykinturah said:
I think you guys should think of using Google Voice... Unless I am misunderstanding something, this is a Sprint VVM problem right?
Click to expand...
Click to collapse
+79 10char
Google Voice is the ****! Use it, enjoy, problem solved!
Man thats some good weed!
I don't like Google Voice... It doesn't give me anything I want. I shouldn't have to get Google Voice to fix a silly problem.
//not complaining about text messages, just Google Voice.
Rudementry said:
I don't like Google Voice... It doesn't give me anything I want. I shouldn't have to get Google Voice to fix a silly problem.
//not complaining about text messages, just Google Voice.
Click to expand...
Click to collapse
Thanks for sharing. I wish my phone came root, also I like pie.
fr0st said:
Thanks for sharing. I wish my phone came root, also I like pie.
Click to expand...
Click to collapse
My phone keeps saying "fresh" over and over again and won't turn on. I am running stock froyo android CM6.0.
Can you help?
Maybe I need to update my PRI.
jwhitney83 said:
Google Voice is the ****! Use it, enjoy, problem solved!
Man thats some good weed!
Click to expand...
Click to collapse
Problem with google voice is that it sometimes disconnects for no reason. I was using it and had to change because it kept dropping me and people would tell me my voicemail did not work.
I'd be cool with G-Voice if it did not do this.
jwhitney83 said:
Google Voice is the ****! Use it, enjoy, problem solved!
Man thats some good weed!
Click to expand...
Click to collapse
Hmm my original answer is showing now after I had a small crash and rewrote the other response. Ignore this one.
Ninjack said:
The problem I had with G-Voice is that it would stop working without notice. I had people call me and say your VM is not working. That's no good.
I'd be cool with G-Voice without that problem
Click to expand...
Click to collapse
I have been using gv for awhile now no problems on cm6 nightlies
Rudementry said:
My phone keeps saying "fresh" over and over again and won't turn on. I am running stock froyo android CM6.0.
Can you help?
Maybe I need to update my PRI.
Click to expand...
Click to collapse
This is just an educated guess and not a statement of fact, but having run the Fresh ROM in the past, it sounds like at some point you flashed your phone with the Fresh ROM, and then maybe flashed back to CM6 but forgot to wipe everything?
When the Fresh ROM boots up, it does indeed say, "Fresh!", so if you're stuck in a boot loop with that ROM's data, you could hear "Fresh!" repeatedly and your phone not start up.
I would go to recovery, do the full factory reset wipe, wipe cache, dalvik cache, and then do your nand-restore or reflash of CM6, google apps, etc.
I hope that this helps.
Thank you for your time,
I would try to just wipe the dalvik and cache first and only do a factory reset if that doesn't work.
jwhitney83 said:
I have been using gv for awhile now no problems on cm6 nightlies
Click to expand...
Click to collapse
I may try it again, as I did not mind G-Voice. But it had happened a few different times. Now I admit I have not tried it since I went to RC2 and the 8/24 nightly.
I'll try setting it up again and see what happens.
[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
I added a new dialer and thought that i could deleted the default apk that came with the phone and now i have lost everything and do not know how to get it back. i can call out but cant take incoming calls i only can hang up from the true phone app that gives me the option to end call, but i can not dial a number if needed while in the call. (like when calling the bank) Someone please help i am pretty knowledgeable but made a stupid mistake and thought it was backed up but my sd card crashed and it never said what i deleted so I am not experience enough to deal with this.
I need immediate help best to reach me by email [email protected] or facebook maurice v dawson sr
goatrider357 said:
I added a new dialer and thought that i could deleted the default apk that came with the phone and now i have lost everything and do not know how to get it back. i can call out but cant take incoming calls i only can hang up from the true phone app that gives me the option to end call, but i can not dial a number if needed while in the call. (like when calling the bank) Someone please help i am pretty knowledgeable but made a stupid mistake and thought it was backed up but my sd card crashed and it never said what i deleted so I am not experience enough to deal with this.
I need immediate help best to reach me by email [email protected] or facebook maurice v dawson sr
Click to expand...
Click to collapse
Did you root the phone and delete the default Dialer app??
Anyway, try installing some other Dialer app and Contacts app from Play store.
See if the default Dialer or Phone app is disabled in Settings->Apps->Disabled.
If it's disabled, enable them
Reply
I have tried everything but I still can't answer. When I make the phone blinks as its going to call screen but nothing happens and it stays on the dialer screen. I have installed dw contact, phone, dialer and still no change. I think there something with the system but there is limited information on this phone model
GokulNC said:
Did you root the phone and delete the default Dialer app??
Anyway, try installing some other Dialer app and Contacts app from Play store.
See if the default Dialer or Phone app is disabled in Settings->Apps->Disabled.
If it's disabled, enable them
Click to expand...
Click to collapse
Yes that is what I did. I thought I was deleting the dialer part only not the whole call/answer screen too
More info!!!
goatrider357 said:
Yes that is what I did. I thought I was deleting the dialer part only not the whole call/answer screen too
Click to expand...
Click to collapse
Phone model?
Rooted?
What have you tried?
Do you have a custom recovery?
Do you have set up ADB?
Phone model? Alcatel onetouch fierce 2
Rooted? Yes
What have you tried?
Install dialer app from Play.(true phone, dw phone, dialer, contact; Google dialer Download dialer apk/odex and install to system using es root explorer
Do you have a custom recovery? No stock recovery
Do you have set up ADB? Don't know if I do or how to properly use it
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!