Whenever i start a phone call, the phone reboots. I tried wiping cache and dalvik, deleted phone appdata. I tried several 6.0.1 ROM's but same problem everytime.
Try Settings > Apps > Gear icon > Default Apps > Phone App and set Phone as default
Had the same problem, this fixed it
Related
Hi all,
Even after reboots, if i go to start menu > settings. The HD will freeze forcing me to soft reset it.
one solution i found (maybe it's just luck) is to open the settings by first going to START MENU > PROGRAMS and after that START MENU > SETTINGS.
Did this freeze happened to any of u ?
well it didn't just happen out of the blue right? Why don't you start off by mentioning the program you installed to cause this problem.
I installed a program before that caused this problem and i couldn't delete it via Remove because it kept freezing everytime i accessed Settings, so i had to delete the program from ActiveSync.
So I sideloaded the Google Dialer from the Nexus devices on my rooted Verizon Galaxy S5. I downloaded the APK, copied it to /system/priv-app, changed the permissions to 644 (rw-r--r--), then ran the APK to install the dialer. I tried launching both from the app drawer and through Nova's shorcut, Actions, Google Dialer and then the first phone option; both ways loads the launcher and then immediately crashes with the error "Unfortunately, Google Dialer has stopped." Has anybody had any success getting the Google Dialer to work on their Galaxy S5? If so, any workarounds that you had to do to get it to work or did it just work? I'm wondering if it's because I froze a bloatware or installed an app that's causing a conflict. My stock Samsung dialer works fine, but I'm not a fan of that dialer and I like the local business search feature of the Google Dialer.
I installed it, but it crashes as soon as I try to search for a person (type any key and crash). I'm not really interested in rooting my phone til CM is ready, but I hear you need to to get it working properly.
Crashing here too, something with S5 firmware or software?
Same here
I'm on a Verizon Galaxy S5 rooted with GEL and I tried making a shortcut to the Google Dialer with QuickShortcutMaker. The dialer crashes every time. Would love to be able to use the Google Dialer again. Coming from CM11 on a Galaxy Nexus.
To stop it crashing, you need to clear your system caches.
Go to the Applications manager in the Settings menu and find the Google dialer in the "all" column
Choose force stop > clear cache > clear data
Now reboot to recovery mode (power phone down, then volume up + home + power)
And select clear cache
Then a normal reboot and you should be good
.
I am having a problem with the stock Samsung dailer, it crashes at least once whenever making a call. I tried clearing the cache that helped for a little bit but now the issue is back,. Any idea of how to get rid of this problem permanently?
fffft said:
To stop it crashing, you need to clear your system caches.
Go to the Applications manager in the Settings menu and find the Google dialer in the "all" column
Choose force stop > clear cache > clear data
Now reboot to recovery mode (power phone down, then volume up + home + power)
And select clear cache
Then a normal reboot and you should be good
.
Click to expand...
Click to collapse
thanks a lot for posting, this solved my issue on my phone : "gm5 plus d" , android 7.1 / cm14.1
Hey, I need some help. In the service code *#9900# I hit "Enable silent logging from boot" and now I can't disabled it?! I get a toast notification on startup that silent logging cannot start check my debug setting. I hate this and there is a service running called "SiletLogging" siletlogservice and com.sec.modem.settings. It is annoying and taking up resources. Any help would be great! I went o the silent logging app in the ap manager and cleared cache, tried clearing cache partition on the phone itself, etc. I tried enabling debug and then enabled silent logging and disabling but I am unable to stop the silent logging from running? I tried going to the silentlogqcom file and changing from a 1 to a 0 but it didn't work. I don't want to have to reset my phone to undo this. Arg, I'm an idiot! This is a stock T-Mobile Note 3 running Android 5.0.
Thanks a million!
5th
Fifth313ment said:
Hey, I need some help. In the service code *#9900# I hit "Enable silent logging from boot" and now I can't disabled it?! I get a toast notification on startup that silent logging cannot start check my debug setting. I hate this and there is a service running called "SiletLogging" siletlogservice and com.sec.modem.settings. It is annoying and taking up resources. Any help would be great! I went o the silent logging app in the ap manager and cleared cache, tried clearing cache partition on the phone itself, etc. I tried enabling debug and then enabled silent logging and disabling but I am unable to stop the silent logging from running? I tried going to the silentlogqcom file and changing from a 1 to a 0 but it didn't work. I don't want to have to reset my phone to undo this. Arg, I'm an idiot! This is a stock T-Mobile Note 3 running Android 5.0.
Thanks a million!
5th
Click to expand...
Click to collapse
OK I think I fixed it. I went into the application manager in settings and went to apps diagmonagent, devicetest, factory mode, service mode and silent logging and cleared data and cache in each. Then I cleared all cache data in storage settings, then went to recovery (turn off phone and hold volume up and home while pressing and holding power until you see recovery in little text on the Samsung logo you can release) and cleared system cache and also disabled cp logging in there too for good measure. When I restarted the phone the silent logging was gone and my normal system resources were back to normal. Man I got lucky! Won't mess with that anymore but at least if someone else does they have a fix which is why I am leaving this here for future people who mess up like myself!
Once using silentlogging its in autostart. You can use an App like Power Clean or ES task manager then look for autostart option find silentlogging and disable its autostart. That is easiest way to fix and it works. I had same Problem. Please be careful and do not disable every task.
Good day.
Hi everyone,
after updating to cm-13.0-20160430-NIGHTLY-d802 and, afterwards, facing this problem:
https://forum.cyanogenmod.org/topic/124602-phones-screen-seems-to-go-dark-after-going-into-standby-since-nightly-install/"]https://forum.cyanogenmod.org/topic/124602-phones-screen-seems-to-go-dark-after-going-into-standby-since-nightly-install/
I tried the following:
1) Wipe System + Data
2) flashed cm-13.0-20160501-NIGHTLY-d802
3) restore app+appdata+system data with Titanium Backup
Now everything but phone app, works.
It crashes every time i launch it/answer call. I tried to clean data and cache of phone app but it didn't work.
I discovered that after disabling/freezing "contact storage" phone app works perfectly, but i don't have contacts this way.
Any help is much appreciated.
Regards.
alby81 said:
Hi everyone,
after updating to cm-13.0-20160430-NIGHTLY-d802 and, afterwards, facing this problem:
https://forum.cyanogenmod.org/topic/124602-phones-screen-seems-to-go-dark-after-going-into-standby-since-nightly-install/"]https://forum.cyanogenmod.org/topic/124602-phones-screen-seems-to-go-dark-after-going-into-standby-since-nightly-install/
I tried the following:
1) Wipe System + Data
2) flashed cm-13.0-20160501-NIGHTLY-d802
3) restore app+appdata+system data with Titanium Backup
Now everything but phone app, works.
It crashes every time i launch it/answer call. I tried to clean data and cache of phone app but it didn't work.
I discovered that after disabling/freezing "contact storage" phone app works perfectly, but i don't have contacts this way.
Any help is much appreciated.
Regards.
Click to expand...
Click to collapse
what i would do is wipe all including sd card..and or download rom again..
place all your files on pc while in twrp clean all the flash roms gapps .. then on twrp again copy back all files you had saved..
seeing the same issue. Were you able to fix it?
d800_is_mine said:
seeing the same issue. Were you able to fix it?
Click to expand...
Click to collapse
maybe bug in rom try new update..or other rom cm has bugs. sometomes when new update older things that worked. have bugs..
Check open gapps faq: https://github.com/opengapps/opengapps/wiki/FAQ
9. My device reboots when I receive or make a phone call. Why?
If your device has Google Dialer installed, it requires to be set as the default Phone application. If not set, it will reboot your device. Go to 'Settings -> Apps -> "Gear Icon" upper right -> Default Apps -> Phone App' to set Google Dialer as your default.
Hello chaps.
Anyone have any idea how to clear this?
I have tried, uninstall the 2 software update APK, clear data on settings, tried a cache clear in recovery.
But still it remains!!!
Ignore, i have solved it
Open applications, show system apps, find "badgeprovider" and force stop/clear data > reset phone.