Error: Oops! Current has stopped responding, a report has been sent to our developers - Nexus 5 Q&A, Help & Troubleshooting

Hi everyone. I've been facing a curious error message on my Nexus 5 and I was hoping I could find some answers here in XDA. I bought the phone about 3 weeks ago and right upon the unboxing I've installed the ROM Cyanogenmod 11 M6. However, several times a day I notice this error message (as shown in the attached snapshot):
"Oops! Current has stopped responding, a report has been sent to our developers."
I don't use the phone so much during the day, but the few times I pick it up, I notice the error popping up on my screen, randomly.
Another remark: I had already noticed this error in my previous phone, Samsung Galaxy Nexus, even without CM installed (at the time it was up-to-date to the latest available Android version, v4.3 JWR66Y).
Does anyone have any idea of what may be causing this error? I have no app installed with such name as "Current" (the only one is "Google Currents", but even when uninstalled the error persists and thus shows no relation whatsoever with the error message).
Thanks a lot!
--
André

Related

[Q] Chrome to Phone Issue

Anyone having any issues with Chrome to Phone app from the market? Everytime I try to go through the setup i'm getting "Error: Unable to connect". Working fine on my Nexus 1 still, but can't seem to get my sensation to setup.
Doing this on 4G (Tried WIFI); tried reboot, tried uninstall, cleared cache...dunno what else could be up unless it's account related.
No issues here. Seems to be running fine for me.
Likewise working well here.
dellybelly said:
Anyone having any issues with Chrome to Phone app from the market? Everytime I try to go through the setup i'm getting "Error: Unable to connect". Working fine on my Nexus 1 still, but can't seem to get my sensation to setup.
Doing this on 4G (Tried WIFI); tried reboot, tried uninstall, cleared cache...dunno what else could be up unless it's account related.
Click to expand...
Click to collapse
same issue here. havent found a fix yet
Looking over the reviews on the market it seems there may be a server issue with some accounts; counted at lest 5 people stating the same error hmm. Went to retry the setup on my N1 by removing and re linking now i have the same error on the N1. Using my secondary (read: porn account) it works fine :/
Hopefully it's a temp issue; C2P is invaluable for my travel!
Just bumping this with some more info; since all you guys are going to be flashing again now; you may hit up against this issue also.
They merged a couple bug reports into this one:
http://code.google.com/p/chrometophone/issues/detail?id=158
Please Star and comment if your having the issue also; they've yet to acknowledge this one just yet although it's been close to a year since first reported but as people began flashing more it will likely continue to increase; it went from about 5 till like June then jumped to almost 30 in July.

[Q] com-android.phone has stopped

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

Nexus 5 turned of while downloading update 5.1

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

Oh please halp. Peregrine soft bricked

I'm usually able to bodge my way through this sort of thing, but am at a loss here.
Just downloaded and flashed the latest nightly build for my Moto G 4G (Peregrine) direct from the inbuilt updater.
When it boots up i repeatedly get com.android.phone has stopped and it appears that it has no sim installed.
Have tried wiping everything and reinstalling but doesn't seem to have made much difference.
I'm an intermediate n00b - that is, I don't REALLY know what I'm doing but can usually bodge my way along blindly following forum posts to root/unlock/flash roms etc, but am at a loss this time. Can anyone please help?
OK I seem to have been able to bodge myself back to working phone more or less.
Installed Twrp 2.8.7 and CM13.0 20151204
Everything SEEMs to be ok now except that t keeps popping up a message saying my network (3UK ) is unavailable
This MAY be a problem with the network, but seems a bit of a coincidence seeing as I've been buggering about with the phone
Any known issues with network connectivity in CM13
EDIT: Still somehow managed to receive an SMS message when it said network unavaialbe
Try removing /data/data/com.android.providers.telephony/databases/telephony.db when com.android.phone keeps crashing!
Phone seems to be working now. Though not sure what i did to fix it
Now I can't install apps from Google play. Get the error "Chrome Browser - Google" can'r be downloaded. Try again and if the problem continues, get help troubleshooting
error code RPC:S-7:AEC-7 JZLQ-5JDI-W4ZW6
Edit: Also can't open the clock (eg to set an alarm) tap on the widget and it just says unfortunately clock has stopped

Z3 Dual keeps crashing (System Ui unfortunately stopped)

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

Categories

Resources