A friend got a new S6 he gave me it to setup bunch of things for him then out of nowhere on 5.1.1 from time to time error comes up: Unfortunetly Settings has Stopped. It's random it depends which app you open.
Anyone knows why is that happening?
Related
I've got a Samsung Galaxy Tab 2 10.1 (P5113), wi-fi only. About a month or so back, I got stuck in a reboot loop, where the tablet would simply reboot itself (almost) constantly. I hadn't installed any new apps or done anything of note to 'trigger' this, that I was aware of. Finally I got fed up and did a system reset.
This seemed to fix the rebooting issue, but introduced a new issue: I would, upon startup of the tablet, get a message that stated: "com.android.phone has stopped unexpectedly". Everything would work fine after that, except for the small detail that I couldn't open my settings. When I attempted to click on Settings, it would clear to the home screen, but nothing would happen after that.
I assumed I could deal with that for a little while, but we just moved and I needed to get the tablet to connect to our new wifi. Without Settings, I didn't have any way to connect, so I decided to try another factory reset, hoping it would fix the issue. That's left me where I'm at now:
The system boots to the Samsung Setup wizard, but I immediately get that same error "com.android.phone has stopped unexpectedly", and it's followed by another error, which says "Unfortunately, Samsung SetupWizard has stopped". Therefore, I can't get the tablet running again, in any meaningful way.
Does anyone have any suggestions? I'd really rather not just assume it's broken if it's not, but I'm at a bit of a loss.
Thanks,
Dan
Hi, I've had my 1+ for about a month now running on stock (but rooted). Today my phone has been showing the "Unfortunately, the process com.android.phone has stopped" dialog. I click ok and the signal is lost. Few seconds later signal reappears but then dialog pops up again. It only started this morning. I haven't changed anything or flashed any fw or basebands.
It's a bit of concern. I've got a phone interview this afternoon and I really don't want the phone to cut out during it!!!
Does anyone know of how this happens and what mighht be done to resolve the problem. I'd rather not have to do a reset.
Many thanks.
Update: I seem to have resolved the issue by flushing the cache and data + force closing all phone/txt/contact apps. I also flashed a different modem for good measure. So far (over an hour now) I've not had the message come back. I suspect there was some conflict somewhere with the afore mentioned apps.
I have this issue after 1 week with the phone.
Same problem as yours, I only rooted the phone still running Stock 11S.
This problem happens this morning out of no where.
Been foreclosing all these apps and clear cache/data and hopefully it'll fix it...
OnePlus One - unfortunately the process com.android.phone has stopped
HI,
I have recently bought oneplus one and just couple of hours back I have upgraded to latest updates. After upgrading I am getting "unfortunately the process com.android.phone has stopped" and not allowing me to touch the home screen. Can you guys plz help me out to resolve this?
THanks
Ganesh
virgopunk said:
Hi, I've had my 1+ for about a month now running on stock (but rooted). Today my phone has been showing the "Unfortunately, the process com.android.phone has stopped" dialog. I click ok and the signal is lost. Few seconds later signal reappears but then dialog pops up again. It only started this morning. I haven't changed anything or flashed any fw or basebands.
It's a bit of concern. I've got a phone interview this afternoon and I really don't want the phone to cut out during it!!!
Does anyone know of how this happens and what mighht be done to resolve the problem. I'd rather not have to do a reset.
Many thanks.
Update: I seem to have resolved the issue by flushing the cache and data + force closing all phone/txt/contact apps. I also flashed a different modem for good measure. So far (over an hour now) I've not had the message come back. I suspect there was some conflict somewhere with the afore mentioned apps.
Click to expand...
Click to collapse
So last night on my nexus 5 ( running lollipop 5.0.1) i finally got the notification saying system update(5.1) available. So i pressed download update and it said "waiting to download update". It kept showing "waiting to download update" for several minutes so i thought something was wrong with my connection. At first i turned of my wifi and then turned it back on. When the issue still did not resolve i switched off my phone.. Now here comes the bad part the phone turned on, showed google and android logo and then showed the message android is upgrading for few seconds. then everything was normal but when i went to system updates i started getting the error - "....process com.google.process.gapps has stopped" .. Whatever i did i kept getting this error. Instead of my play store an app is there with the name com.android.vending.
Also now when i press the system update tab, nothing seems to happen..
I am not a huge expert in these type of things, but what i think is that while showing "waiting to download update" it was already downloading (probably the important google apps or other system apps) and when i restarted my phone it tried to update those apps with the unfinished downloaded app and thus turning my sweet, easy update into a nightmare. All apps like games and other are functioning properly. The google apps are the only ones seem to be the problem and also cannot get into system update.
So can any kind soul help me to resolve this issue? Thanks a lot in advance
Hi,
I have been putting off updating my OnePlus for a couple of months now. It was working fine and I didn't see much of a point to it. The constant notifications to update the phone started getting to me so I finally did the deed and accepted the update. Low and behold my phone keeps throwing errors and now I cant send messages or really do anything.
Error list:
"unfortunately the process com.google.process.gapps has stopped", this error pops up every time I hit 'OK' to clear it.
Google Play services unable to run. I also get notification to update Google Play Services but when I go to download it the download get stuck and doesn't complete.
Messages also will not send. I'm not sure about receiving messages, not enough friends where I get texted that much .
I have been looking for over 2 hours now and cant seem to find a fix. I am not the best with phones by any means, I just use it mainly for texting and calling plus reddit and occasional games on the side. If there is any recommendations to fix this problem I would greatly appreciate it. Thanks!
Hi, i hope to be posting in the correct section since this is my first thread here.
i recently bought a Z3 Dual and everything was fine, i updated firmware to Marshmallow and did factory reset (just to be sure that everything was ok after update), so i started installing various apps i had on other phones (Avast, Truecaller, Dropbox, CCleaner, Clean master, Games and other stuff, i'll post the entire app list if needed) and the phone started randomly crash with on-screen message "System UI unfortunately stopped" giving me only "ok" button, with the message continuously popping out, so i can't pass lockscreen and i'm forced to shutdown phone or reset via power button.
As the phone is on again everything is fine, but after some time it crashes again.
I tried to do a "Manual Debug" and find which app needed to be uninstalled so i tried one by one but without any luck (i've successfully get the device running without problem for 2 days but unfortunately i have not understood which app was causing the crash)
i did a Logcat but since i can't read it (i only found "BEGINNING OF CRASH" with Notepad++) i don't know what else to do, I thank you in advance for your willingness to help me with this (probably the stupidest) problem
HTML:
https://pastebin.com/MWknKjnM
it happened again, here's another logcat, exactly at 02-19 16:05:27.079
HTML:
https://pastebin.com/StBycp9H
just resolved... last poweramp (beta) update caused the issue.
a rollback to stable release solved the problem