[Q] voice mail notification issue - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

i recently had a problem with my rooted gs3 so i reflashed it and now everytime i turn my phone on it says i have 2 new voice mails but when i check them i dont have any? how can i fix this?

atrix2017 said:
i recently had a problem with my rooted gs3 so i reflashed it and now everytime i turn my phone on it says i have 2 new voice mails but when i check them i dont have any? how can i fix this?
Click to expand...
Click to collapse
You could try clearing your cache/dalvik in recovery. I'm not sure why it would keep telling you that if your box is empty.

BWolf56 said:
You could try clearing your cache/dalvik in recovery. I'm not sure why it would keep telling you that if your box is empty.
Click to expand...
Click to collapse
yea i tried it could it be that i had messages when i flashed back to stock then back to root?

atrix2017 said:
yea i tried it could it be that i had messages when i flashed back to stock then back to root?
Click to expand...
Click to collapse
Highly doubt it. The notifications should come from your carrier so I'm thinking it's either a bad data (somewhere) or your carrier sending bad info.
Do you have any saved voice mails?

Try this...call your phone from another phone and leave a voice message, Then go in and clear the voice message (7). That might clear the others as well

I've been using Google Voice and I have the same issue. Never found a solution unfortunately.

Related

Unable to receive phone calls

Heya,
For about 3 weeks now I haven't been able to receive phone calls, everytime a call is incoming the process.core.android.phone crashes and the call doesn't go through. However I can make calls and send messages etc.
If I open the Phone app > hit 3 dots and try > settings it crashes with the same message. Also if I try to open the 'Sounds' section of the settings the settings process crashes.
I'm on Android version 4.3, using rom ProBam 4.4.6 EndevourU (I was previously using 4.4.1 where my phone was working normal, once it stopped working I upgraded to 4.4.6 but the error is still persistent)
I've tried clearing cache, wiping contacts data, wipe phone data, and a few various other things, but can't get it to take a single call.
Any ideas? Thanks in advance,
- Beau.
M1nistry said:
Heya,
For about 3 weeks now I haven't been able to receive phone calls, everytime a call is incoming the process.core.android.phone crashes and the call doesn't go through. However I can make calls and send messages etc.
If I open the Phone app > hit 3 dots and try > settings it crashes with the same message. Also if I try to open the 'Sounds' section of the settings the settings process crashes.
I'm on Android version 4.3, using rom ProBam 4.4.6 EndevourU (I was previously using 4.4.1 where my phone was working normal, once it stopped working I upgraded to 4.4.6 but the error is still persistent)
I've tried clearing cache, wiping contacts data, wipe phone data, and a few various other things, but can't get it to take a single call.
Any ideas? Thanks in advance,
- Beau.
Click to expand...
Click to collapse
You should go to ProBam thread.
virgolib said:
You should go to ProBam thread.
Click to expand...
Click to collapse
+10 posts required... not 'experienced' enough.
M1nistry said:
+10 posts required... not 'experienced' enough.
Click to expand...
Click to collapse
You go and study at http://forum.xda-developers.com/showthread.php?t=2291291, now coming out 4.4.7.
virgolib said:
You go and study at http://forum.xda-developers.com/showthread.php?t=2291291, now coming out 4.4.7.
Click to expand...
Click to collapse
Updated to 4.4.7 and both errors (+ phone calls can't be received) still persist. I've done as much self research to try fix it myself but to no avail.
Sorry I have no idea, try with another different rom.
virgolib said:
Sorry I have no idea, try with another different rom.
Click to expand...
Click to collapse
Yeah I installed another one which doesn't have any of the aforementioned errors, just moving my data across as it's a massive pain to redo everything..
M1nistry said:
Yeah I installed another one which doesn't have any of the aforementioned errors, just moving my data across as it's a massive pain to redo everything..
Click to expand...
Click to collapse
After pain, more gains with enjoy it.
Sent from my HTC One X using xda app-developers app

[SM-N900T] CF-Auto-Root

Please see the 'generic' Note 3 CF-Auto-Root thread here:
http://forum.xda-developers.com/showthread.php?t=2466423
This actual thread will become a proper CF-Auto-Root thread once I'm finished tying up all the lose ends. Please comment in this thread, but read the instructions and grab the file from the thread linked above.
--- reserved #1 ---
--- reserved #2 ---
Thanks
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
FIX looks like it was on googles servers. Back to normal but this is on stock after I odin, Ill wait on the root to see if others are still getting problems.
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
Click to expand...
Click to collapse
I was getting the above error too even after performing a device reset. I reflashed the root a second time and it is working. The only difference is I enabled USB debugging in the Developer options the second time, not sure if that really made a difference though.
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
Click to expand...
Click to collapse
Me too I p m chain fire like 15 min ago. It could be a Google issue
Sent from my SM-N900T using Tapatalk 4
transitoyspace said:
Has anyone else been getting RPC:S-5:AEC-0 errors?
I tired wiping both caches and data from app manager. nothing
Tried wiping cache from recovery. nothing.
tried wiping cache and factory restore. nothing.
After I rooted apps were installing fine but then it just stopped.
Any suggestions? Im gonna try to see if I can find an odin file of it stock.
EDIT: So I used a odin stock image. Still getting error. Any suggestions?
Do tmobile employees check to see if it has been flashed?
Gonna try to go back to store and see if can get it replaced with another. But cant till later. This sucks....
Click to expand...
Click to collapse
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
XooLoo said:
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
Click to expand...
Click to collapse
Thanks I will give it a try
Edit: it worked Thanks a million
Sent from my SM-N900T using Tapatalk 4
Ah wow, I was getting these errors too. Thought it was unrelated and a server side issue (still might be, account specific?)
I'm writing this without reading the suggestions above but, what eventually worked for me (after removing accounts, factory reset, clearing play store data & play framework whether necessary or not)..
Went to Google dashboard (all on PC), made sure device was there, went to play.google.com (computer)-- it errored and froze, logged out, back in, worked eventually, viewed my installed apps (took like 5 minutes to load), started installing apps from there. Once that was working, it worked on my device.
The curious part was, initially, when I'd search for ANY app on play.google.com, it would show no results. Opening in incognito (not signed in), it worked fine.
XooLoo said:
I have been getting it (wasn't up until I rooted!). Was driving me insane.............. Tried all the tricks I found on the internet with absolutely zero luck.... until I came across this dude's video: http://www.youtube.com/watch?v=uv8d-nl04qI. It worked but I followed it to the t! So delete your Google account. Force close and erase Data for the 3 services he's mentioning. Turn it off. Turn it back on. Go to Play, it asks for your Google Account; add it.... Enjoy!
Click to expand...
Click to collapse
Yes, had the same problem on my SM-N900T, not on either of the other two [N900/A], it took creating a new google account and also clearing the cache for google services framework, google play and uninstalling the play store update. I had to do this a couple of times, seemed to work better for me without a reboot, but this is the right path for fixing this problem.
Hope this helps,
Bob
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
bob_beringer said:
Yes, had the same problem on my SM-N900T, not on either of the other two [N900/A], it took creating a new google account and also clearing the cache for google services framework, google play and uninstalling the play store update. I had to do this a couple of times, seemed to work better for me without a reboot, but this is the right path for fixing this problem.
Hope this helps,
Bob
Click to expand...
Click to collapse
I just force stopped play store and cleared data and it worked after that.
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
How do we se our Knox status and also....does it do anything to the phone when its like that? Should we wait for a method of root that doesnt trip knox
bdorr1105 said:
How do we se our Knox status and also....
Click to expand...
Click to collapse
go to download mode .
unlockingsky said:
go to download mode .
Click to expand...
Click to collapse
If you have both Kies and Android SDK installed, go to command prompt (cmd) and go to where adb.exe is, and type:
adb reboot download
---------- Post added at 11:43 PM ---------- Previous post was at 11:43 PM ----------
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
Mine is 0x1
unlockingsky said:
Can someone with a rooted note 3 confirm this doesn't t change Knox to 0x1 ?
Click to expand...
Click to collapse
it changes it. what does knox do for the normal user? i
transitoyspace said:
it changes it. what does knox do for the normal user? i
Click to expand...
Click to collapse
None, basically it detects flash so that they can void your warranty.
zoth said:
None, basically it detects flash so that they can void your warranty.
Click to expand...
Click to collapse
it voids your samsung warranty to be exact. if you take it back to tmobile with tmobile warranty, they will still fix/replace hardware issues.
About to root for the simple fact I can not stand the headphones auto adjusting. I need it louder then normal and tired of playing music at maxed settings just to hear music and then a few songs later it acts like its supposed to. (work in a factory)
Anywho: Does this method still give you the option of having auto updates from Tmobile for bug fixes and stuff or do we need to manually keep an eye open for updates?
(coming from Rooted Stock Note 2 thats why im asking. Not big on romming)
Thank you

Android System Error Message

When I switch my Z1C on from being completely off, I get the following error message:
Unfortunately android.process.acore has stopped working.
Is there a resolution for this?
Stock rom? Rooted? Does it boot up or not? Come on, some info would be nice
Schlengge said:
Stock rom? Rooted? Does it boot up or not? Come on, some info would be nice
Click to expand...
Click to collapse
Rom that came with the phone so stock rom I'd say, not rooted.
Yes it boots up.
Information supplied, any ideas?
Schlengge said:
Stock rom? Rooted? Does it boot up or not? Come on, some info would be nice
Click to expand...
Click to collapse
Info supplied.
Try clearing contacts and contact storage app data and see if that works. Sync/save your contacts before doing this. If not you can always do a factory reset and the problem should be gone. Backup your sms and make a list of the apps before though because you will have to reinstall all of them.
Funny thing is that it only started doing this after I had factory reset the phone.
templeka said:
Try clearing contacts and contact storage app data and see if that works. Sync/save your contacts before doing this. If not you can always do a factory reset and the problem should be gone. Backup your sms and make a list of the apps before though because you will have to reinstall all of them.
Click to expand...
Click to collapse
Do you think that it would cause any issues if I just hit on OK and left it at that?
Well you posted the issue so up to you what you want to do. I just googled that error for you lol and that's what I found, contacts and contact storage.
I switched off completely then on again after a min and no message about acore so maybe its nothing to worry about.

Oneplus 3 Dialpad doesnt work during calls for inputs during customer care calls etc

Hi, Can someone help me. My Oneplus 3 Dialpad doesn't work during calls causing problems for inputting options or joining a conference call. I am unable to input Option 1 or dial in a conference id because the numbers dialpad doesn't show up during call. I installed a few other dial apps and nothing seems to work. Thanks in advance for helping me.
harharryhar said:
Hi, Can someone help me. My Oneplus 3 Dialpad doesn't work during calls causing problems for inputting options or joining a conference call. I am unable to input Option 1 or dial in a conference id because the numbers dialpad doesn't show up during call. I installed a few other dial apps and nothing seems to work. Thanks in advance for helping me.
Click to expand...
Click to collapse
Isn't there a button to bring It up? I'm pretty sure there is..
When I click on the button the numbers dont come up, it used to work but I think sometime after the Nougat update it stopped working. I am thinking is there any way other than the full flash of the update?
I cleared cache in recovery mode and also wiped the cache of all the apps. It still doesn't work. So if I do a factory reset will the dialer work or is it better to reinstall OOS 4?. I think something might have been removed or something, not sure why it doesn't work.
Is there anyway rather than factory reset or reinstalling the OS? Thx for the help.
I had this problem.. I push and wait a second, and it will take. But if you just push in the numbers like texting on a keyboard, it won't. Easy does it.
harharryhar said:
I cleared cache in recovery mode and also wiped the cache of all the apps. It still doesn't work. So if I do a factory reset will the dialer work or is it better to reinstall OOS 4?. I think something might have been removed or something, not sure why it doesn't work.
Is there anyway rather than factory reset or reinstalling the OS? Thx for the help.
Click to expand...
Click to collapse
OnePlus OTAs suck. I have been reading about umpteen issues for people who went that route.
Better to clean flash the full ROM. Don't wipe internal storage and you won't lose data.
tnsmani said:
OnePlus OTAs suck. I have been reading about umpteen issues for people who went that route.
Better to clean flash the full ROM. Don't wipe internal storage and you won't lose data.
Click to expand...
Click to collapse
Thanks, I am a bit of a noobie is there any link for clean flash without losing data. Thank you so much. If there is no link that you know please let me know, I will factory reset or something. Thank you.
harharryhar said:
Thanks, I am a bit of a noobie is there any link for clean flash without losing data. Thank you so much. If there is no link that you know please let me know, I will factory reset or something. Thank you.
Click to expand...
Click to collapse
There are at least a couple of threads which I have seen on XDA. Unfortunately I am unable to locate them immediately. Search in XDA OP3 forums and you may get them.
I doubt that factory resetting will solve the problem.
Another option would be to install googles dialer + framework
Allan_Hun said:
Another option would be to install googles dialer + framework
Click to expand...
Click to collapse
Not sure Google Dialer is working on OOS v2.5.

random problems after unlock and root

hey guys, so i've an interesting problem that I've searched all over xda and google, but can't find a definitive answer/solution. Here goes:
I recently unlocked the bootloader of my t-mobile z2 force. rooted via temp flashing TWRP and magisk, everything went fine, no issues. restoring my phone went great, got a few "app unexpectedly closed" type messages every now and then, but it's settled down for the most part. the problem is that, periodically, my phone will lose sync with google (i think that's whats happening anyway). I will have no contacts in my phone app, text messages cannot be received, gmail fails to open, calendar has no events, etc etc. a quick reboot fixes everything, but then it will randomly happen again, with no indication, other than i think "i haven't recv'd any texts recently, lemme check" and i find it's happened again.
I hope this makes sense, because I'm not even sure i'm looking up the right thing in google or other xda forums. Has anyone experienced this? anyone know the answer?
Thanks in advance
Just a bump...anybody run into this or have any ideas?
I haven't had any problems like thoes. My Bluetooth goes a lil dumb from time to time and when I have wifi and Bluetooth on at the same time Bluetooth will just loose signal randomly. I'm just stock Rooted on T-Mobile.
bobdallama said:
hey guys, so i've an interesting problem that I've searched all over xda and google, but can't find a definitive answer/solution. Here goes:
I recently unlocked the bootloader of my t-mobile z2 force. rooted via temp flashing TWRP and magisk, everything went fine, no issues. restoring my phone went great, got a few "app unexpectedly closed" type messages every now and then, but it's settled down for the most part. the problem is that, periodically, my phone will lose sync with google (i think that's whats happening anyway). I will have no contacts in my phone app, text messages cannot be received, gmail fails to open, calendar has no events, etc etc. a quick reboot fixes everything, but then it will randomly happen again, with no indication, other than i think "i haven't recv'd any texts recently, lemme check" and i find it's happened again.
I hope this makes sense, because I'm not even sure i'm looking up the right thing in google or other xda forums. Has anyone experienced this? anyone know the answer?
Thanks in advance
Click to expand...
Click to collapse
My suggestion is to unroot, clear cache and Dalvik, and re root. See what happens and post results. Your app permissions are on for Google correct?
fastboot boot <TWRP file name>.img
Only now that you’re inside TWRP temporarily flash the TWRP .zip file you’ve saved into the phone
Reboot into TWRP again, flash Magisk
https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
climbhigh77 said:
My suggestion is to unroot, clear cache and Dalvik, and re root. See what happens and post results. Your app permissions are on for Google correct?
Click to expand...
Click to collapse
Thanks. Yes all permissions are granted for Google app. I also stopped battery optimization for it and any other phone related apps I could find. I'll give this a shot.

Categories

Resources