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?
Related
[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.
I searched and tried a couple of the posted fixes for this problem, but they didn't work for me.
The camera works fine for a couple of hours if I do a reboot, but then I get the "Unfortunately, Camera has stopped working." message eventually (in the stock Camera app, and also all camera-related apps (e.g. Snapchat, Instagram))
I'm on SlimKat 4.4.2 Build 3, with BMS 20140305.
Logcat: http://pastebin.com/raw.php?i=eHDgpeeB
Any help would be greatly appreciated! Thank you.
GenericAsianGuy said:
I searched and tried a couple of the posted fixes for this problem, but they didn't work for me.
The camera works fine for a couple of hours if I do a reboot, but then I get the "Unfortunately, Camera has stopped working." message eventually.
I'm on SlimKat 4.4.2 Build 3, with BMS 20140305.
Logcat: http://pastebin.com/raw.php?i=eHDgpeeB
Any help would be greatly appreciated! Thank you.
Click to expand...
Click to collapse
Someone may have had a different experience than I have, but I've been on several 4.4.2 ROMS and the camera always has slightly different versions of this same problem for me. It either gives me the same message you're getting or suddenly says "cannot connect to camera" until I reboot. I don't believe the KitKat camera has been fully worked out yet as I haven't found an apk that works without this issue.
Please don't use BMS. Stick with the Stock Kernel of SlimKat and see if the problem repeats. If it does not then you will have to ask the BMS Dev to update drivers if he has not done so already.
Hi there,
I got a refurbished otter at the beginning of the week. I followed the guides here to install FFF, TWRP and CM11 on it.
First, a big thanks to everyone involved.
I'm getting what look like UI crashes, which I've been able to reproduce with Firefox but it seems they are not limited to it.
To reproduce:
flash FFF, TWRP and CM11 M6
install FF from the Play Store
configure Firefox sync
browse to any page
I should note that I configured my Google account at boot, and that I use a Hebrew locale.
On my device, I get a blank screen, followed by a return to the launcher or previously opened app, followed by more crashes until the CM boot animation shows on top of the launcher. When it completes, a dialogue appears noting the system UI has stopped working. It returns after confirming the message.
Should I report this to Mozilla and/or CM? I'd like to collect more information, where can I find any relevant logs? If so, is it possible to increase the logs' verbosity?
Thanks in advance.
Idontwantausername said:
Hi there,
I got a refurbished otter at the beginning of the week. I followed the guides here to install FFF, TWRP and CM11 on it.
First, a big thanks to everyone involved.
I'm getting what look like UI crashes, which I've been able to reproduce with Firefox but it seems they are not limited to it.
To reproduce:
flash FFF, TWRP and CM11 M6
install FF from the Play Store
configure Firefox sync
browse to any page
I should note that I configured my Google account at boot, and that I use a Hebrew locale.
On my device, I get a blank screen, followed by a return to the launcher or previously opened app, followed by more crashes until the CM boot animation shows on top of the launched. When it completes, a dialogue appears noting the system UI has stopped working. It returns after confirming the message.
Should I report this to Mozilla and/or CM? I'd like to collect more information, where can I find any relevant logs? If so, is it possible to increase the logs' verbosity?
Thanks in advance.
Click to expand...
Click to collapse
I'm getting those same notification/notification bar/UI crashes on Nook HD+ using CM11 (nightlies and M6). I don't use firefox, so that is not your problem
I was actually getting them more in the previous nightly builds. CM11 M6 seems to have helped a little.
Mine happen seemingly randomly when I get notifications for a new email or hangout and I try to swipe down the notification bar to see what they are.
I've tried wiping the davlik, the entire cache, and even doing a factory reset. Nothing seems to work.
Anyone else have some advice?
_Boondock_ said:
I'm getting those same notification/notification bar/UI crashes on Nook HD+ using CM11 (nightlies and M6). I don't use firefox, so that is not your problem
I was actually getting them more in the previous nightly builds. CM11 M6 seems to have helped a little.
Mine happen seemingly randomly when I get notifications for a new email or hangout and I try to swipe down the notification bar to see what they are.
I've tried wiping the davlik, the entire cache, and even doing a factory reset. Nothing seems to work.
Anyone else have some advice?
Click to expand...
Click to collapse
I have the exact same issue for about 2 months i believe.
This happens usually when pulling the notification panel down. It think it happens when you chain a lot of actions one after other. Like unlocking phone and pulling down the notification than tapping another thing etc...etc...
Hope this will be fixed soon, it usually disturbs the usage a lot. I was hoping M6 would solve that.
Back to m5 guys, my Galaxy Nexus has the same problem here, so I revert back to m5 and everything works fine, except the stock browser has startup crash sometime
Does anyone know if the devs are aware of this issue?
I just reproduced this on today's OtterX CM build.
I'm having the same problem. Had been running one of the earlier nightlies without any notification bar problems at all. Updated to the M6 release and now this problem occurs every few minutes. System is now totally unstable with M6. Firefox crashes more frequently now too.
CYAN-4047, if anyone's interested.
Idontwantausername said:
CYAN-4047, if anyone's interested.
Click to expand...
Click to collapse
ARG! Sure wish I had seen this before spending the whole day restoring my Kindle to the older nightly after having to wipe it.
Idontwantausername said:
Hi there,
I got a refurbished otter at the beginning of the week. I followed the guides here to install FFF, TWRP and CM11 on it.
First, a big thanks to everyone involved.
I'm getting what look like UI crashes, which I've been able to reproduce with Firefox but it seems they are not limited to it.
To reproduce:
flash FFF, TWRP and CM11 M6
install FF from the Play Store
configure Firefox sync
browse to any page
I should note that I configured my Google account at boot, and that I use a Hebrew locale.
On my device, I get a blank screen, followed by a return to the launcher or previously opened app, followed by more crashes until the CM boot animation shows on top of the launcher. When it completes, a dialogue appears noting the system UI has stopped working. It returns after confirming the message.
Should I report this to Mozilla and/or CM? I'd like to collect more information, where can I find any relevant logs? If so, is it possible to increase the logs' verbosity?
Thanks in advance.
Click to expand...
Click to collapse
I followed your steps exactly and I am not able to get this problem to occur. Are there any other steps you you may have omitted? Any other apps you installed or any other actions you performed in addition to what you listed here? Also, are you sure it's "any page"? Is there a specific site you were trying to go to when this happened? I'm trying to work on a fix for this issue and was hoping I could reproduce the problem based on your information but my device is still functioning fine. The more information you can provide the better and ideally I'd like something that can be reproduced consistently.
0xD34D said:
I followed your steps exactly and I am not able to get this problem to occur. Are there any other steps you you may have omitted? Any other apps you installed or any other actions you performed in addition to what you listed here? Also, are you sure it's "any page"? Is there a specific site you were trying to go to when this happened? I'm trying to work on a fix for this issue and was hoping I could reproduce the problem based on your information but my device is still functioning fine. The more information you can provide the better and ideally I'd like something that can be reproduced consistently.
Click to expand...
Click to collapse
Since I have now reflashed back to my older nightly I can't give you exact steps but here is what I experienced. I also got a stock KF a while ago and since I didn't want the stock release, followed the instructions to reflash it. At that point I did the full device wipe and flashed the 20140407 nightly build. No problems at all, the system ran beautifully. This week, I got the notification that M6 was available for installation so I went to Settings->About tablet->CM Updates->Available Updates and clicked the download. It downloaded and installed without any problem. Rebooted and problems began immediately. Firefox was immediately unstable and began crashing frequently. The "UI" would hang and go black then crash and come back up in lock screen. Pulling the notification bar open would hang and then the system would crash. Things really became completely unuseable.
So today I tried rolling back to the previous nightly that had worked well. This time, I didn't wipe the device, just reinstalled the nightly and wiped the cache after installation. See my previous thread about how that turned out. The status bar was totally hosed, the quick settings panel didn't work, the home button didn't work, the extended power menu was gone. Just a complete mess. So... I wiped the device and reinstalled the nightly and brought everything back to life again.
Now I don't know if the issues were caused by a flakey M6 release, or the installation process which left some droppings behind as I didn't try installing the M6 release after a full wipe. But I do know that after a full wipe the 20140407 nightly is working without a problem. I can't say for sure but my expectation is that it had something to do with the installation process not doing a clean install rather than a bad M6 release.
I made a test build which reverts a change I suspect may be the culprit. If anyone cares to try it out, here is the link. Please do not go around sharing this will a lot of people since it is currently hosted on Dropbox and they will throttle it if too much traffic is received.
https://dl.dropboxusercontent.com/u/2151597/cm-11-20140511-UNOFFICIAL-otter.zip
md5sum: f9747d68e833bae9db12f548116f9551
Dropbox is still syncing so if you get an error 404 just try again in a couple minutes.
0xD34D said:
I followed your steps exactly and I am not able to get this problem to occur. Are there any other steps you you may have omitted? Any other apps you installed or any other actions you performed in addition to what you listed here? Also, are you sure it's "any page"? Is there a specific site you were trying to go to when this happened? I'm trying to work on a fix for this issue and was hoping I could reproduce the problem based on your information but my device is still functioning fine. The more information you can provide the better and ideally I'd like something that can be reproduced consistently.
Click to expand...
Click to collapse
I saw in the bug report you've already found a way to reproduce, but just in case, as I wrote there I've found it reproduces by installing Adblock Plus - I close the app completely in the app drawer to make sure FF restarts with the add-on installed. After it restarts it should show a quick configuration page where you can enable blocking of secondary things like tracking and malware. In the first paragraph is a link to another settings page. In this other page all I have to do is zoom in or scroll around and most of the time I'll get a crash within a minute.
0xD34D said:
I made a test build which reverts a change I suspect may be the culprit. If anyone cares to try it out, here is the link. Please do not go around sharing this will a lot of people since it is currently hosted on Dropbox and they will throttle it if too much traffic is received.
https://dl.dropboxusercontent.com/u/2151597/cm-11-20140511-UNOFFICIAL-otter.zip
md5sum: f9747d68e833bae9db12f548116f9551
Dropbox is still syncing so if you get an error 404 just try again in a couple minutes.
Click to expand...
Click to collapse
Downloaded, will be tested later today (in about 12 hours).
Edit: been testing this for about an hour now. The system seems very stable, even more than M5.
M6
I have this snapshot M6 build a week ago..I didn't notice any problem ...like firefox crashing.
I do a full wipe(clean) install...Data,system, cache, dalvik cache
0xD34D said:
Please do not go around sharing this will a lot of people since it is currently hosted on Dropbox and they will throttle it if too much traffic is received.
Click to expand...
Click to collapse
I hope you don't mind I took the liberty of submitting this to a public bt tracker:
URL deleted
Idontwantausername said:
I hope you don't mind I took the liberty of submitting this to a public bt tracker:
http://burnbit.com/torrent/289563/cm_11_20140511_UNOFFICIAL_otter_zip
Click to expand...
Click to collapse
Actually I'd prefer you not do that.
0xD34D said:
Actually I'd prefer you not do that.
Click to expand...
Click to collapse
It looks like there has been a fix for this problem. Has the fix been incorporated into one of the nightly builds or is it still only available as a patch?
mpuckett54 said:
It looks like there has been a fix for this problem. Has the fix been incorporated into one of the nightly builds or is it still only available as a patch?
Click to expand...
Click to collapse
Does anyone know if this has been fixed in one of the nightly builds? Has anyone tried any of the post M6 nightly builds yet?
cm-11-20140602-NIGHTLY- i9300
mpuckett54 said:
Does anyone know if this has been fixed in one of the nightly builds? Has anyone tried any of the post M6 nightly builds yet?
Click to expand...
Click to collapse
Had the same issue with M6 but now I thing they have fixed the issue, not sure which nightly build but build dated 20140602 fixed the issue for me.
I did a clean install.
Followed following steps.
1. Boot into recovery(CWM).
2. Factory Reset.
3. Cleared Dalvik cache.
4. Installed zip and run "defy_fullwipe_ext3.zip"
5. Installed "cm-11-20140602-NIGHTLY- i9300"
6. Installed Gapps for kitkat.
7. Reboot.
I have not faced the same UI crash issue so far will update if I face in future .
For "defy_fullwipe_ext3.zip" refer following link(I used the first one):
http://forum.xda-developers.com/showthread.php?t=1818520
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 .
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