I'm sure this is thr wrong section but its hard finding the right forum on this app so I'm sorry to any mod to has to fix that.
Im using cyanogenmod 5.0.8 for quite a long
time now but suddenly youtube app keeps
force closing, i solved this by going to system/
apps and just reinstalling it but now its going
back to force closing as soon as iv exited it and
relaunched it...
I then tried restoring a backup but this has not
worked, i then updated the youtube app to the
new youtube app from gingerbread or froyo
cant remember but this does the same thing,
fix permissions just totaly f**ked my phone
and i had to restore my backup again.
So does anyone know how i can fix this issue?
Sent from my HTC Dream using XDA App
This is the red errors from logcat moments after it force closing, iv discovered that the you tube app seems to work fine so long as I'm not signed in but as soon as iv signed in with my gmail account and iv exited the app I imedidiatly tested it and its back to force closing.
W/dalvikvm( 5831): threadid=3: thread exiting
with uncaught exception (group=0x4001e178)
E/AndroidRuntime( 5831): Uncaught handler:
thread main exiting due to uncaught exception
E/AndroidRuntime( 5831):
java.lang.IllegalArgumentException: activity is
null
E/AndroidRuntime( 5831): at
android.accounts.AccountManager.getAuthToken
(AccountManager.java:503)
E/AndroidRuntime( 5831): at at.run
(SourceFile:406)
E/AndroidRuntime( 5831): at
android.accounts.AccountManager$9.run
(AccountManager.java:812)
E/AndroidRuntime( 5831): at
android.os.Handler.handleCallback
(Handler.java:587)
E/AndroidRuntime( 5831): at
android.os.Handler.dispatchMessage
(Handler.java:92)
E/AndroidRuntime( 5831): at
android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 5831): at
android.app.ActivityThread.main
(ActivityThread.java:4363)
E/AndroidRuntime( 5831): at
java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 5831): at
java.lang.reflect.Method.invoke
(Method.java:521)
E/AndroidRuntime( 5831): at
com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 5831): at
com.android.internal.os.ZygoteInit.main
(ZygoteInit.java:618)
E/AndroidRuntime( 5831): at
dalvik.system.NativeStart.main(Native Method)
Sent from my HTC Dream using XDA App
When I receive a SMS, instead of having a notification, the following error is shown, and the phone go back to the bootanimation. I'll already tried to wipe everything, like dalvik cache, factory reset and reinstalling the rom with no success.
I'm using the MIUI 2.3.16 ROM (http://forum.xda-developers.com/showthread.php?t=1258073)
Code:
E/AndroidRuntime( 4453): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 4453): java.util.MissingFormatArgumentException: Format specifier: 3$s
E/AndroidRuntime( 4453): at java.util.Formatter.getArgument(Formatter.java:1131)
E/AndroidRuntime( 4453): at java.util.Formatter.doFormat(Formatter.java:1096)
E/AndroidRuntime( 4453): at java.util.Formatter.format(Formatter.java:1062)
E/AndroidRuntime( 4453): at java.util.Formatter.format(Formatter.java:1031)
E/AndroidRuntime( 4453): at java.lang.String.format(String.java:2177)
E/AndroidRuntime( 4453): at android.content.res.Resources.getString(Resources.java:286)
E/AndroidRuntime( 4453): at com.android.server.am.PackageGuardian$PackageBehaviorWitness.<init>(PackageGuardian.java:883)
E/AndroidRuntime( 4453): at com.android.server.am.PackageGuardian.seekWitness(PackageGuardian.java:1534)
E/AndroidRuntime( 4453): at com.android.server.am.ActivityManagerService$3.handleMessage(ActivityManagerService.java:1041)
E/AndroidRuntime( 4453): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4453): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 4453): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1529)
Did you try to reinstall MIUI? Applying the ZIP + full data wipe?
thiagomtl said:
Did you try to reinstall MIUI? Applying the ZIP + full data wipe?
Click to expand...
Click to collapse
Yes, but no success, the same error appears.
It seems to be an error when sending sms in french, because I found the same problem for MIUI HD2 (http://forum.xda-developers.com/showpost.php?p=16080760&postcount=482)
Posting it here since I don't have access to the dev forum just yet.
This ROM gets utterly hosed by something the Play Store does during install. It doesn't happen every time, or with specific apps, but I've reproduced it twice, and when it happens the only way to get the tablet back into a usable state is to wipe data and system and reflash from scratch, which, honestly, is a major pain, so I'm gathering what I can right now.
The problem is caused by Play Store installing an app. As soon as the app is finished and the installed notice pops up, MiuiHome will crash. I haven't caught that specific crash, but trying to get to your homescreen will just get you in a loop of crash dialog -> brief second of live wallpaper -> crash dialog again. Here's the backtrace out of the logcat for that crash:
Code:
E/AndroidRuntime( 1330): FATAL EXCEPTION: main
E/AndroidRuntime( 1330): java.lang.ArrayIndexOutOfBoundsException: length=4; index=4
E/AndroidRuntime( 1330): at com.miui.home.launcher.CellLayout.a(CellLayout.java:483)
E/AndroidRuntime( 1330): at com.miui.home.launcher.CellLayout.addView(CellLayout.java:207)
E/AndroidRuntime( 1330): at com.miui.home.launcher.Workspace.a(Workspace.java:324)
E/AndroidRuntime( 1330): at com.miui.home.launcher.Launcher.a(Launcher.java:1995)
E/AndroidRuntime( 1330): at com.miui.home.launcher.Launcher.a(Launcher.java:1833)
E/AndroidRuntime( 1330): at com.miui.home.launcher.bA.run(LauncherModel.java:1245)
E/AndroidRuntime( 1330): at com.miui.home.launcher.K.handleMessage(DeferredHandler.java:47)
E/AndroidRuntime( 1330): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1330): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1330): at android.app.ActivityThread.main(ActivityThread.java:4429)
E/AndroidRuntime( 1330): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1330): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 1330): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime( 1330): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime( 1330): at dalvik.system.NativeStart.main(Native Method)
But it gets worse.
You can invoke settings from the pullup menu, but if you try to select ANY app (not just the app that triggered the bug) in the Apps tab, Settings force-closes. Here's that backtrace.
Code:
E/AndroidRuntime( 1355): FATAL EXCEPTION: main
E/AndroidRuntime( 1355): java.lang.NullPointerException
E/AndroidRuntime( 1355): at com.android.settings.applications.InstalledAppDetails.gI(InstalledAppDetails.java:479)
E/AndroidRuntime( 1355): at com.android.settings.applications.InstalledAppDetails.onResume(InstalledAppDetails.java:401)
E/AndroidRuntime( 1355): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:873)
E/AndroidRuntime( 1355): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1032)
E/AndroidRuntime( 1355): at android.app.BackStackRecord.run(BackStackRecord.java:622)
E/AndroidRuntime( 1355): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1382)
E/AndroidRuntime( 1355): at android.app.FragmentManagerImpl$1.run(FragmentManager.java:426)
E/AndroidRuntime( 1355): at android.os.Handler.handleCallback(Handler.java:605)
E/AndroidRuntime( 1355): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 1355): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1355): at android.app.ActivityThread.main(ActivityThread.java:4429)
E/AndroidRuntime( 1355): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1355): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 1355): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime( 1355): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime( 1355): at dalvik.system.NativeStart.main(Native Method)
Here's the worst part. Removing the app that triggered it using the pm commandline tools (since literally no other method of uninstalling apps is accessible) doesn't solve the problem. Uninstalling EVERY app you ever installed through Play Store doesn't solve the problem. The ONLY way to get the tablet back into a usable state is to go back into TWRP, wipe cache, dalvik, data, AND system, then reflash the ROM.
I keep wondering if it's just my device -- I mean, nobody else has reported this issue. But pains have been taken to work around bad spots in flash -- right? And besides a software bug, what else could it be?
Yeah thats no fun at all start helping people out get your 10 posts in and post in development for sure what apps may I ask even though Im on AOKP I am on the new kernel maybe we can find out whether it is specific to the rom or a kernel issue hopefully a dev will look at your logcat soon.I have had simular but not with the runtime error and not after app install so far I havent had the crashes your experiencing either.
I updated my Nexus 7 from 4.2.1 to 4.2.2 via OTA.
After updating, the google play app always crashes with message "Unfortunately, Google Play Store has stopped".
Below are some logs taken from the device when the app crashes.
E/AndroidRuntime( 2242): FATAL EXCEPTION: main
E/AndroidRuntime( 2242): java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.remoting.protos.Response$Payload, but got null
E/AndroidRuntime( 2242): at com.google.android.volley.MicroProtoHelper.getParsedResponseFromWrapper(MicroProtoHelper.java:38)
E/AndroidRuntime( 2242): at com.google.android.finsky.api.DfeRequest.deliverResponse(DfeRequest.java:456)
E/AndroidRuntime( 2242): at com.google.android.finsky.api.DfeRequest.deliverResponse(DfeRequest.java:49)
E/AndroidRuntime( 2242): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:99)
E/AndroidRuntime( 2242): at android.os.Handler.handleCallback(Handler.java:725)
E/AndroidRuntime( 2242): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 2242): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2242): at android.app.ActivityThread.main(ActivityThread.java:5041)
E/AndroidRuntime( 2242): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2242): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2242): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
E/AndroidRuntime( 2242): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
E/AndroidRuntime( 2242): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2242): Caused by: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.remoting.protos.Response$Payload, but got null
E/AndroidRuntime( 2242): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2242): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2242): at com.google.android.volley.MicroProtoHelper.getParsedResponseFromWrapper(MicroProtoHelper.java:36)
E/AndroidRuntime( 2242): ... 12 more
Can anyone provide a possible solution?
Thank you.
Under both Android KitKit 4.4 and now 4.4.2, when I reboot my Galaxy S4 Google Play Edition phone, I am getting an error box as soon as the lock screen shows up that says "Unfortunately, the process com.android.phone has stopped." I hit okay and continue and am seeing no other problems, but it is annoying and a bit disturbing. This happened both before and after rooting and installing CWM recovery. I am running a stock installation.
Has anyone else seen this and/or know of a fix? Thanks much
Try cache wipe. If that doesn't work try factory reset. If that still doesn't work, try reflashing back to stock
Sent from my GT-I9505G using Tapatalk
I wanted to follow up with what I did to fix this problem. As suggested, I did wipe cache, which didn't help. I then did a factory reset via CWM recovery. To my surprise, this didn't fix the problem initially. Upon boot, I still received the app stopping message. But I found a thread in another forum that showed others having this problem, also noting that a factory reset didn't fix the problem. But one report said that continuing through to sign into Google after the reset had fixed this person's problem. Sure enough, the same worked for me. There is another report that says just resetting app preferences would also fix the problem, but I had already done the factory reset and thus didn't have a chance to test this.
The thread in the other forum is here:
http://forums.androidcentral.com/samsung-galaxy-s4-google-edition/338363-galaxy-s4-google-play-edition-official-android-4-4-kit-kat-rolling-out-now.html
Also, here is the logcat stack dump indicating the problem with com.android.phone:
I/BrcmNfcNfa( 1368): GKI TASK_DEAD received. exit thread 3...
D/AndroidRuntime( 1363): Shutting down VM
W/dalvikvm( 1363): threadid=1: thread exiting with uncaught exception (group=0x4159ad40)
E/AndroidRuntime( 1363): FATAL EXCEPTION: main
E/AndroidRuntime( 1363): Process: com.android.phone, PID: 1363
E/AndroidRuntime( 1363): java.lang.NullPointerException
E/AndroidRuntime( 1363): at com.android.internal.telephony.BaseCommands.unSetOnSs(BaseCommands.java:464)
E/AndroidRuntime( 1363): at com.android.internal.telephony.gsm.GSMPhone.dispose(GSMPhone.java:266)
E/AndroidRuntime( 1363): at com.android.internal.telephony.PhoneProxy.deleteAndCreatePhone(PhoneProxy.java:261)
E/AndroidRuntime( 1363): at com.android.internal.telephony.PhoneProxy.phoneObjectUpdater(PhoneProxy.java:217)
E/AndroidRuntime( 1363): at com.android.internal.telephony.PhoneProxy.handleMessage(PhoneProxy.java:127)
E/AndroidRuntime( 1363): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1363): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 1363): at android.app.ActivityThread.main(ActivityThread.java:5050)
E/AndroidRuntime( 1363): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1363): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 1363): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1264)
E/AndroidRuntime( 1363): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1080)
E/AndroidRuntime( 1363): at dalvik.system.NativeStart.main(Native Method)
highvista said:
I wanted to follow up with what I did to fix this problem. As suggested, I did wipe cache, which didn't help. I then did a factory reset via CWM recovery. To my surprise, this didn't fix the problem initially. Upon boot, I still received the app stopping message. But I found a thread in another forum that showed others having this problem, also noting that a factory reset didn't fix the problem. But one report said that continuing through to sign into Google after the reset had fixed this person's problem. Sure enough, the same worked for me. There is another report that says just resetting app preferences would also fix the problem, but I had already done the factory reset and thus didn't have a chance to test this.
The thread in the other forum is here:
http://forums.androidcentral.com/samsung-galaxy-s4-google-edition/338363-galaxy-s4-google-play-edition-official-android-4-4-kit-kat-rolling-out-now.html
Also, here is the logcat stack dump indicating the problem with com.android.phone:
I/BrcmNfcNfa( 1368): GKI TASK_DEAD received. exit thread 3...
D/AndroidRuntime( 1363): Shutting down VM
W/dalvikvm( 1363): threadid=1: thread exiting with uncaught exception (group=0x4159ad40)
E/AndroidRuntime( 1363): FATAL EXCEPTION: main
E/AndroidRuntime( 1363): Process: com.android.phone, PID: 1363
E/AndroidRuntime( 1363): java.lang.NullPointerException
E/AndroidRuntime( 1363): at com.android.internal.telephony.BaseCommands.unSetOnSs(BaseCommands.java:464)
E/AndroidRuntime( 1363): at com.android.internal.telephony.gsm.GSMPhone.dispose(GSMPhone.java:266)
E/AndroidRuntime( 1363): at com.android.internal.telephony.PhoneProxy.deleteAndCreatePhone(PhoneProxy.java:261)
E/AndroidRuntime( 1363): at com.android.internal.telephony.PhoneProxy.phoneObjectUpdater(PhoneProxy.java:217)
E/AndroidRuntime( 1363): at com.android.internal.telephony.PhoneProxy.handleMessage(PhoneProxy.java:127)
E/AndroidRuntime( 1363): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1363): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 1363): at android.app.ActivityThread.main(ActivityThread.java:5050)
E/AndroidRuntime( 1363): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1363): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 1363): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1264)
E/AndroidRuntime( 1363): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1080)
E/AndroidRuntime( 1363): at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
I have the same problem and a factory reset didn't fixed it. Can you explain me better how to fix this problem without doing a factory reset again please? Thanks
Ok, I restored apps preferences but the problem is still there.
MattyDip said:
I have the same problem and a factory reset didn't fixed it. Can you explain me better how to fix this problem without doing a factory reset again please? Thanks
Ok, I restored apps preferences but the problem is still there.
Click to expand...
Click to collapse
For me, it was the factory reset and logging into Google that fixed the problem, so I can't give any more details on the non-reset fix, unfortunately.
highvista said:
For me, it was the factory reset and logging into Google that fixed the problem, so I can't give any more details on the non-reset fix, unfortunately.
Click to expand...
Click to collapse
I did a factory reset, logged with Google and the problem is still there
I dont have the message popping up but I did notice when i try to go to settings to check my connection to sprint that I get com.android.phone crashing when I hit carrier settings. I have been very annoyed by this as it also affects my text messaging where I am limited to only sending one text. Like I get the countdown for remaining words and it wont let me type anymore.
I am so annoyed at this and not being able to fix it that I might boot back to stock ROM. But is this an issue with version 4.4 kitkat or is this a cwm recovery error? I am a bit confused from reading different peoples problems of where this error is actually coming from. Will going back to stock actually fix the problem? or am I screwed since I rooted my phone and installed a aftermarket ROM already?
Thank You
Thanks highvista! I had the same problem on my S4 GPE and resetting app preferences and rebooting fixed it. Didn't have to hard reset the phone. <rant>Now if only I can figure out how to get my app store to download apps, and G maps to speak out street names in turn by turn nav, I'll be a happy customer. And this is stock android 4.4.2 without any rooting or custom ROMs. Sometimes I wonder why I switched from iphone.</rant>
Wont read SIM
Greetings..
I see that I'm not the only one with this issue although mine has kinda resolved now, but I cant get the SIM to work.. Android just wont read it..
It actually happende after I rooted my GS4/I9506(which went fine and I uninstalled alot of apps with link2SD), after restart the com.android.phone has stopped msg kept on popping up on the screen in addition to 'Unfortunately, Messages has stopped' when trying to send sms. So I re-rooted it again, still wouldnt stop. Rebooted with vol. up key + power button, selected to reset to factory, and it doesnt pop up anymore (the com.android.phone has stopped msg) but I still get the Messages has stopped when I'm trying to write messages.
Another thing is that it wont read the SIM, so I suspect an issue lies with reading the micro-SIM. As mentioned elsewhere in this forum, I've tried to select Mobile Networks through the Settings, but it says 'Insert SIM card to access network services'.
If anyone has come with a solution to this, let us know.