[CM13 Sultan] Unable to send/receive texts (Unfortunately, Messenger has stopped) - ONE Q&A, Help & Troubleshooting

Hi guys!
I recently updated from the 11/24 build of Sultan's CM13 ROM to the 12/6 build and I seem to have broken something as my Messenger app keeps crashing every time I try to open a conversation. I get the error "Unfortunately, Messenger has stopped" and then the app crashes. I also don't seem to be able to receive any texts. I performed the update through the CM OTA Updater.
Does anyone know what I could do to fix this? Thanks!

Hi,
Last week I had the same issue on CM13.
A clean flash should resolve this.

If you don't want to perform a clean flash, you can just wipe data of com.android.providers.telephony and reboot. It worked perfectly for me.

Related

[Q] Unfortunately Maps has stopped

Hi everyone,
I'm aware this issue has been discussed in other threads but the problem is still unresolved and i didn't find anyone with this issue on a Nexus 5.
I'm running on CM11 20140606-NIGHTLY
So this error prompts twice everytime i boot my phone and when i try to launch Google Maps. I tried deleting all the Maps data in Settings/Application, tried to uninstall/reinstall, i tried installing Maps 8.2 and 8.0 as the error occured with 8.1, still get the error pop up.
I don't encounter this issue on the stock ROM. Should i try flashing a new SNAPSHOT version of cyanogen or do you have any idea how i can fix this issue ?
crickets
narthe said:
Hi everyone,
I'm aware this issue has been discussed in other threads but the problem is still unresolved and i didn't find anyone with this issue on a Nexus 5.
I'm running on CM11 20140606-NIGHTLY
So this error prompts twice everytime i boot my phone and when i try to launch Google Maps. I tried deleting all the Maps data in Settings/Application, tried to uninstall/reinstall, i tried installing Maps 8.2 and 8.0 as the error occured with 8.1, still get the error pop up.
I don't encounter this issue on the stock ROM. Should i try flashing a new SNAPSHOT version of cyanogen or do you have any idea how i can fix this issue ?
Click to expand...
Click to collapse
This is the second time this has happened to me, and this last time I was super vigilant about making periodic backups. But even restoring a nandroid of when maps worked doesn't solve the problem. I hate google over this.
Try to find the gapps one by one (not the whole package). Download the Maps one and flash it

[Q] Getting com..android.phone error, unable to send some texts?

Hello,
I am getting the com.android.phone error message very often. It started just under a week ago. To recap:
I am rooted with an unlocked bootloader, installed CyanogenMod 11.0-InstallerXNPQ32P. I keep getting the error when trying to send texts especially. I have cleared my phone cache, rebooted, installed CyanogenMod in recovery mode, updated CyanogenMod, etc. I have also had issues with my service cutting in and out that might have something to do with it, thought I've updated the towers. I use Textra as a texting app, previously using Google Hangouts. Any help would be appreciated, thanks.

[Q] com.android.phone keeps crashing

Hi
Yesterday I flashed the newest CM 12.1 (Android 5.1.1) and GApps on my Oneplus One, after an Update failed.
Everything workes fine, except "com.android.phone" keeps crashing every few seconds and I lose my mobile connection. When in flightmode, this doesn't happen.
Any ideas how to fix this?
greetings
Why update is failed? Maybe problem in this. I sit on Hazy and CyanogenMod and com.android.phone is not crashing.
I know that crashing messages.
I am also having this issue every once in a while. But I've been on COS12 for weeks now.
Well first I was on the default CyanogenOS, shipped by Oneplus. I became the message for a new update and created a backup with TWRP. After updating, I tried restoring the data from my backup and somehow that broke my phone, so I installed the newest nightly. I tried deactivating mobile internet but the error still appears all the time. The phone gets a new mobile connection and shortly after com.android.phone crashes.
R3s1stanc3 said:
Well first I was on the default CyanogenOS, shipped by Oneplus. I became the message for a new update and created a backup with TWRP. After updating, I tried restoring the data from my backup and somehow that broke my phone, so I installed the newest nightly. I tried deactivating mobile internet but the error still appears all the time. The phone gets a new mobile connection and shortly after com.android.phone crashes.
Click to expand...
Click to collapse
Try to freeze com.android.phone(delete if problem is not gone) and install other or same but new version. I don't know is it solve issue, but you can wipe all via fastboot(fastboot flash boot, etc)

Can I undo twrp v.2.8.6.1? Also android.process.acore error msg

I have two problems with my lg g3 att rooted phone.
1st Problem - I have tried to get rid of the android.process.acore error but have had no luck THIS time. (Last time part of the fix was completely uninstalling the facebook app from my phone). This time (and last time) I cleared caches, stopped them, deleted my contacts and the contacts storage, unclicked the app sync button.... I can't really remember what else I did to restore it to normal.
2nd problem - So I clicked on update software from ATT and a TWRP v.2.8.6.0 screen comes up. I don't know what to do with it. Do I click install, restore, reboot, backup? Can I just undo this and try and find some other way to remove the android.process.acore error message without losing all my data with a factory reset? If this twrp is complicated I would prefer to just undo what I just did. I really need some help as soon as possible. Thank you in advance.
Same Error Message
newby1 said:
I have two problems with my lg g3 att rooted phone.
1st Problem - I have tried to get rid of the android.process.acore error but have had no luck THIS time. (Last time part of the fix was completely uninstalling the facebook app from my phone). This time (and last time) I cleared caches, stopped them, deleted my contacts and the contacts storage, unclicked the app sync button.... I can't really remember what else I did to restore it to normal.
Click to expand...
Click to collapse
I am having the same problem and not sure what to do about it. I restart my phone, and it seems to be ok for a while, but then it starts popping up again. I have an AT&T LG G3 (LG - D850), not rooted phone. I have tried to reset all app preferences, but that didn't seem to do anything really. Could really use some help! Thanks!
Software Lineup -
Android Version - 5.0.1
Kernel Version - 3.4.0
Build - LRX21Y
Software - D85020f

OB4 - com.android.phone keeps stopping?

Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
krakout said:
Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
Click to expand...
Click to collapse
I'm on latest beta 4 using a IN2025 OP8Pro. I used the full ROM not the incremental update to upgrade from OB3. I am rooted also. No issues you are experiencing. Sounds like you need to flash the full ROM from fastboot mode and complete wipe for a clean install and start from there.
./
Thanks for the input. How big is the partial update? Because the one I flashed was almost 3GB...
So, no real way to downgrade to OB3 again?
3gb is full ROM not the incremental update.
So that's not the explanation then... I wonder if factory resetting will fix the problem?
Any ideas anyone?

Categories

Resources