[CM12.1] Dialer has stopped working - Sony Xperia M

Hello, I just flashed the latest nightly of cyanogenmod 12.1 and the recommended open gapps (ARM,5.1,nano) and I noticed that when I make or receive a call, I get a "Dialer has stopped working" message. However after a bit of testing I realized the call is actually made and I can speak with the other person so it's likely just a problem from the app. Do you have any suggestions? I already tried the clear cache thing I read somewhere ,it didn't work .

Related

[Q] New ROM. "com.android.phone has stopped." when a phone call is placed/received.

[Q] New ROM. "com.android.phone has stopped." when a phone call is placed/received.
Just recently switched from Paranoid Android 3.6 to the latest 2 PAC man nightlies (tried 2 because of this problem), and now I'm unable to make/receive any calls. I get the message "Unfortunately, the process com.android.phone has stopped." This happens as soon as i place a call or accept a call. When this happens, I also lose cell signal and wifi momentarily. I can open the phone and the contacts app with no issue, sync works, and SMS and data connection also works fine. I tried clearing data for contacts storage and phone but that did not help.
Sometimes, the call would go through even when the app closed message pops up. The proximity sensor works and the recipient can hear me and vice versa. The call would go on as normal and a call log entry is made, although the time is wrong (a call i made a few minutes ago is recorded as 2 hours ago. The system time did not change).
I initially didn't wipe data when changing roms, but when this began to happen I went back and wiped system, data and cache and did a full clean install. After that, the phone was working, however as soon as I download apps from the Play store (i didn't restore any data using helium backup) the phone stopped working again. After that, tried safe mode and uninstalling every app, but the phone still doesn't work.
I tried using both the latest PA gapps and the PACman gapps but the issue persists with both. Currently running PACman nightly from 24/6 with PA gapps from 2013-04-27 and AK kernel.
Any help is appreciated.
gabokazu said:
Just recently switched from Paranoid Android 3.6 to the latest 2 PAC man nightlies (tried 2 because of this problem), and now I'm unable to make/receive any calls. I get the message "Unfortunately, the process com.android.phone has stopped." This happens as soon as i place a call or accept a call. When this happens, I also lose cell signal and wifi momentarily. I can open the phone and the contacts app with no issue, sync works, and SMS and data connection also works fine. I tried clearing data for contacts storage and phone but that did not help.
Sometimes, the call would go through even when the app closed message pops up. The proximity sensor works and the recipient can hear me and vice versa. The call would go on as normal and a call log entry is made, although the time is wrong (a call i made a few minutes ago is recorded as 2 hours ago. The system time did not change).
I initially didn't wipe data when changing roms, but when this began to happen I went back and wiped system, data and cache and did a full clean install. After that, the phone was working, however as soon as I download apps from the Play store (i didn't restore any data using helium backup) the phone stopped working again. After that, tried safe mode and uninstalling every app, but the phone still doesn't work.
I tried using both the latest PA gapps and the PACman gapps but the issue persists with both. Currently running PACman nightly from 24/6 with PA gapps from 2013-04-27 and AK kernel.
Any help is appreciated.
Click to expand...
Click to collapse
is a pacman bug
you need to install 22.06 nithly or take the phone apk from it and replace the new one in system/app of the new nightly
Replaced the phone apk and it worked. Thanks!
gabokazu said:
Just recently switched from Paranoid Android 3.6 to the latest 2 PAC man nightlies (tried 2 because of this problem), and now I'm unable to make/receive any calls. I get the message "Unfortunately, the process com.android.phone has stopped." This happens as soon as i place a call or accept a call. When this happens, I also lose cell signal and wifi momentarily. I can open the phone and the contacts app with no issue, sync works, and SMS and data connection also works fine. I tried clearing data for contacts storage and phone but that did not help.
Sometimes, the call would go through even when the app closed message pops up. The proximity sensor works and the recipient can hear me and vice versa. The call would go on as normal and a call log entry is made, although the time is wrong (a call i made a few minutes ago is recorded as 2 hours ago. The system time did not change).
I initially didn't wipe data when changing roms, but when this began to happen I went back and wiped system, data and cache and did a full clean install. After that, the phone was working, however as soon as I download apps from the Play store (i didn't restore any data using helium backup) the phone stopped working again. After that, tried safe mode and uninstalling every app, but the phone still doesn't work.
I tried using both the latest PA gapps and the PACman gapps but the issue persists with both. Currently running PACman nightly from 24/6 with PA gapps from 2013-04-27 and AK kernel.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry to hear that.
It's time to check if this is a software issue of the custom roms/kernels running on your device, and we do this by returning to stock. If this issue still persists, then I'm afraid your radio has died.

[Q] Slimkat 4.2.2 "com.android.systemui stopped working"

I am using slimkat 4.4.2 and there's a button to the right of the homebutton that usually opens a popup where i can see other apps that i have opened but after a while it stops working and gives me this error: com.android.systemui has stopped working and after that the UI disappears and restarts itself. Any ideas?
This is the most recent post relating to this issue, so here it goes.
I've been having this issue with CM11 and more recently with Pac man, I've tried many nightlies on both ROMs with the same result, "com.android.systemui stopped working" then the screen goes into a loop, the only way to get is to work again is by doing a factory reset and starting over, I've also tried flashing the same ROM and other variations in the order of installing everything again, same deal.
This really got to me so I've spent most of the day re-installing everything from scratch, one application at a time, and making a nandroid each time, until I installed Google+, once installed, it goes into a loop (as above), so I reverted back to the previous backup, and just to prove that it was Google+, I did it again , same deal, restored again, and installed all my apps except Google+, and I've had no issues. I've read across heaps of other places where they mention the problem is relate to something trying to make a change in the status bar, or related, well, I've noticed that without Google+, the top left profile icon doesn't update with my Google profile (as per my other set up in other incarnations of CM11 and Pac man nandroids),, so could there be a link where Google+ is causing this problem as it tries to update the profile?

Problems with CyanogenMod 13 (apps) (d855/2gb)

As soon as the CM 13 build was released for the LG G3, i flashed it on my phone. All was good and every thing worked fine. I missed the CM apps package that i had before flashing CM 13, so i downloaded and flashed the apps package. Most of the apps worked fine, but the dialer simply won't work for me. Every time I try to make or receive a call, I get an: "unfortunately Dialer has stopped" message. It is very frustrating and i don't know how to overcome it. By the way the calls appear in the call history, as though i made a call, and the message keeps reappearing until the call ends. I have tried reflashing CM with only a factory reset, but the cm apps were still on my phone therefore I still had the problem. After that fail, I did a full wipe of the phone, flashed CM 13 (latest build), and flashed Gapps (again, latest build), but still no success. The CM apps are still on my phone.
I would appreciate any help you can give me, as this is very annoying and disables the main function of the device.
Thanks, Yonatan.
I'm on build 17/12 and it's working fine for me.
bmyonatan said:
. Every time I try to make or receive a call, I get an: "unfortunately Dialer has stopped" message.
Click to expand...
Click to collapse
I'm also on 17/12 and got the same problem.
I also have the same issue at LG G2
petenoni said:
I'm on build 17/12 and it's working fine for me.
Click to expand...
Click to collapse
Do you have the CM apps package installed?
Would appreciate any help, as I still have this problem
bmyonatan said:
Would appreciate any help, as I still have this problem
Click to expand...
Click to collapse
Were you able to solve this problem?

CyanogenMod 13 nightlies

I will update this tomorrow, I'm at work all day today. NOTE MODS: I AM THE ACTUAL CYANOGENMOD MAINTAINER FOR THIS DEVICE
XDA:DevDB Information
CyanogenMod 13, ROM for the AT&T Samsung Galaxy S III
Contributors
Nardholio, invisiblek
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: NJ1 or NJ2 bootloader/modem for US variant (SGH-i747), otherwise latest available for SGH-i747m
Based On: CyanogenMod
Version Information
Status: Nightly
Current Stable Version: never
Created 2016-03-20
Last Updated 2016-03-20
Reserved
sweet
Are matrixzone and arunscape going to continue helping you with these nightlies¿
Lol @ current stable version
Nardholio said:
Current Stable Version: never
Click to expand...
Click to collapse
So really never? Ever... ever? Or wait till N...
Got some strange behavior on 03.23 nightly. When somebody calls me - gui is restarting until call ends and caller hears usual beeps. On 21 or 20 ( forgot) nightly all was working.
Update. Flashed back 21 nightly, incoming call is working again, after flash got android.process.acore is stopped error. To fix it all you need is go to apps find Contacts Storage and clear data.
spiderkr said:
Got some strange behavior on 03.23 nightly. When somebody calls me - gui is restarting until call ends and caller hears usual beeps. On 21 or 20 ( forgot) nightly all was working.
Update. Flashed back 21 nightly, incoming call is working again, after flash got android.process.acore is stopped error. To fix it all you need is go to apps find Contacts Storage and clear data.
Click to expand...
Click to collapse
I'm also on the 23 nightly with the incoming call issue. Have you tried any of the later nightlies?
Also seem to have a problem with gapps. Whenever I flash it, I get an error: "unfortunately setup wizard has stopped".
Apart from these, cm13 runs just fine
Just want to report that on the 25 nightly, bluetooth audio still doesn't work. Guess I have to go back to stone-age tech - wired earbuds.
c.s.n said:
Just want to report that on the 25 nightly, bluetooth audio still doesn't work. Guess I have to go back to stone-age tech - wired earbuds.
Click to expand...
Click to collapse
One of matrix's latest unofficial build has bluetooth audio (14th).
I'm hoping the nightlies will get the fix (or revert?) soon.
geearf said:
One of matrix's latest unofficial build has bluetooth audio (14th).
I'm hoping the nightlies will get the fix (or revert?) soon.
Click to expand...
Click to collapse
Iirc, some people couldn't get Bluetooth calls to work on the 3/14 unofficial, but media was working, and it's the reverse on the 3/13 build. Could be wrong, I'm sure I'll be corrected if I am.
No you're correct, I use more my phone for bluetooth media than bluetooth calls these days and forgot.
Has anyone tried the latest nightly? (26)
Heads up to anyone who's just about to flash cm13 for the first time..flash gapps immediately after cm13 before you reboot so you don't have to go through what I went through.
If per adventure you do flash gapps after rebooting and you run into some glitches, just calm down and follow these steps:
1. Go to settings>apps and grant setup wizard all permissions
2. Delete data/system/users/0/runtime-permissions.xml
That should resolve all Google play error popups
Coming from lollipop 5.1.1 did you guys factory reset installing 6.0 Marshmallow? If so any problems restoring TB backups?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
blasterrr said:
Coming from lollipop 5.1.1 did you guys factory reset installing 6.0 Marshmallow? If so any problems restoring TB backups?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
I went cm 11 -> 12 -> 13 . only thing I did moving between major versions was wipe dalvik, cache, and system and then flash ROM and then gapps and reboot.
Latest nightly is running pretty solid. Only issues I've come across is a few Front Facing Camera hiccups. Also, whenever I send or receive a MMS my data symbol has an exclamation point and stops working. The only workaround I've come across is to toggle airplane mode but, this becomes rather bothersome as I am in numerous group chats and constantly toggling airplane mode is rather annoying. This issue isn't present when on wifi.
Thevenine said:
Has anyone tried the latest nightly? (26)
Heads up to anyone who's just about to flash cm13 for the first time..flash gapps immediately after cm13 before you reboot so you don't have to go through what I went through.
If per adventure you do flash gapps after rebooting and you run into some glitches, just calm down and follow these steps:
1. Go to settings>apps and grant setup wizard all permissions
2. Delete data/system/users/0/runtime-permissions.xml
That should resolve all Google play error popups
Click to expand...
Click to collapse
I have issues with constant Google Services and Google Play Store stopped working messages.
These are the ways I tried to install CM13, I used TWRP 3 and I did a full format (wipe cache dalvik data and repart).
1) Flashed CM13-latest, Flashed GAPPS-6-latest, rebooted.
2) Flashed CM13-latest, rebooted, flashed GAPPS-6-latest, rebooted.
Method #1 makes the phone loop on "Checking software updates" during the setup wizard.
Method #2 makes the phone constantly pop-up messages about google stuff stopped working.
I tried your method but it did not work. Setup Wizard had already all of its permissions, I removed the xml file and my phone rebooted and it did the usual "optimizing app x of x".
I don't know what to do... The phone is not really usable.
expertmax said:
I have issues with constant Google Services and Google Play Store stopped working messages.
These are the ways I tried to install CM13, I used TWRP 3 and I did a full format (wipe cache dalvik data and repart).
1) Flashed CM13-latest, Flashed GAPPS-6-latest, rebooted.
2) Flashed CM13-latest, rebooted, flashed GAPPS-6-latest, rebooted.
Method #1 makes the phone loop on "Checking software updates" during the setup wizard.
Method #2 makes the phone constantly pop-up messages about google stuff stopped working.
I tried your method but it did not work. Setup Wizard had already all of its permissions, I removed the xml file and my phone rebooted and it did the usual "optimizing app x of x".
I don't know what to do... The phone is not really usable.
Click to expand...
Click to collapse
Grant all Google apps permissions too. I skipped that
So. Much. MOD...
hi...i wanna say about a bug..it's happening to me.. most times the sortcuts icons on the lock screen disappears..also there is no white glow while swiping the icons...also animation is gone,, if some one also have this issue..report.. nightly is of 04/02..thanks..also when i swap camera there is error..please have a look...again thanks

SMT310 CM13 and CM14 Messaging apps forceclose

Hello everyone,
I am not new to flashing...... ROMs. I have been having an issue with sending SMS on my SM T310 after flashing cm13 and cm14. I go back and flash cm12 and have no issue with it. I have tried all the open Gapps packages from aroma down to pico and keep getting force closes when I use hangouts or Google messages. The app starts but when I touch the screen to type the first letter it force closes. I can make telephone calls through hangouts though. Weird. I also can get messages and read them. Just can't send them.
Any clues will help.
Thank you

Categories

Resources