I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
japzone said:
I'm running Stock 4.1.2 with busybox installed, root, and XposedFramework.
Last night my device froze so I had to hard-reboot it. I turned it off then turned it on, it was late so I went to bed. I woke up in the morning went to pick it up and it was still on the boot screen. It was hot and after booting into recovery it said that I had only 15% battery left. I was dumbfounded. I tried to boot again, and it got stuck again. After all the trouble shooting I could think of(Including disabling and removing Xposed), I wiped my /system partition and flashed the Stock /system image. Sadly that didn't help. It seems the problem resides on my /data partition somewhere but obviously if I'm wiping that I might as well start from scratch.
Below is my Logcat. If you can gleam anything from it please let me know. I'm pretty-tech savvy but I still have zero expirience reading Logcats. At the very least I'd like to know what the error is exactly so I can endevor to avoid it in the future.
Click to expand...
Click to collapse
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Thanks for the reply. Nice crash course on log reading I have gone ahead and flashed a fresh install of PA ROM.
I really just wonder how the error might of happened. It occured at a bad time for me where my External Harddrive died on me taking my backups with it, and leaving me with nowhere to put new ones. My new Laptop with a 1TB drive is coming in August so I was planning on backing up and Flashing a Custom ROM then. But this error took out my device before I could make a backup. Oh well, I managed to scavenge most of my apps and hopefully will be able to restore them. Sadly I lost a day off to resuscitating my Nexus
Red Devil said:
Hi there ! This seems to be the problem in your case :
Code:
Sending signal. PID: 349 SIG: 9
E/AndroidRuntime( 349): *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager
E/AndroidRuntime( 349): java.lang.ArrayIndexOutOfBoundsException: src.length=8192 srcPos=1 dst.length=8192 dstPos=0 length=-1
E/AndroidRuntime( 349): at java.lang.System.arraycopy(Native Method)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.fillBuffer(KXmlParser.java:1489)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.skip(KXmlParser.java:1574)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.parseStartTag(KXmlParser.java:1049)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:369)
E/AndroidRuntime( 349): at org.kxml2.io.KXmlParser.next(KXmlParser.java:310)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFLOCK(UsageStatsService.java:376)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.readHistoryStatsFromFile(UsageStatsService.java:357)
E/AndroidRuntime( 349): at com.android.server.am.UsageStatsService.<init>(UsageStatsService.java:274)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:1534)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:160)
E/AndroidRuntime( 349): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1405)
E/AndroidRuntime( 349): Error reporting crash
E/AndroidRuntime( 349): java.lang.NullPointerException
E/AndroidRuntime( 349): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
E/AndroidRuntime( 349): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
As you can see the lines start with E:/ which stand for error .
V stands for Verbose
I for information
D for Debug.
And some others . more about these.. I suggest you Google. Now you will ask how I found out the error ? Well if you take a closer look to the log you will notice that once the kernel is initialized ( which happens at the Google logo ) the netd framework starts booting by the kernel.
Normal boot sequence is kernel > its init.rd and init.rc then the init.d and then the framework. How I came to know all this ? Take a log of a normally booting ROM
If you again carefully observe the log .. You will notice log re iterates. It goes on an infinite loop. Hence the term boot'loop'.
The start of the loop is
Code:
AndroidRuntime( 369): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 369): CheckJNI is OFF
And this Is the dead / bad code
Code:
ygote ( 369): Exit zygote because system server (508) has terminated
I/ServiceManager( 118): service 'sensorservice' died
I/ServiceManager( 118): service 'entropy' died
I/ServiceManager( 118): service 'power' died
That's roughly how you read a logcat.
And about your problem. I suggest a clean wipe and reflash the ROM. Its always better to keep backing up your data from time to time. I also ensure I wipe clean even during flashing nightlies .
Sent from my HTC using xda app-developers app
Click to expand...
Click to collapse
Related
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
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've had random reboots on my N4 running MIUI. It happens maybe 1-2 times daily. I caught the last one on logcat. Need someone to decipher. Thanks in advance.
You can attach it as a text file.
sent from tapatalk
eksasol said:
You can attach it as a text file.
sent from tapatalk
Click to expand...
Click to collapse
Here you go...... (w/ phone info, first 20 lines)
...next post....
I think I attached wrong one.... this one looks like the correct time....
11-30 13:24:18.840 F/libc ( 508): @@@ ABORTING: LIBC: ARGUMENT IS INVALID HEAP ADDRESS IN dlfree addr=0x2a4de920
11-30 13:24:18.840 F/libc ( 508): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 653 (PowerManagerSer)
Some Googling say it might be due to a function that is called by two different threads at the sametime, maybe related to Bluetooth from what is shown. Also the first file you post have a lot about the qualcomm sensor error(?) as well.
It also help if you mention the rom and kernel you're using. Since you're on 4.2.2, maybe an update to kitkat could solve the issue.
Thank you very much for your response. I'm running miui v5 port. It's a 4.2 Rom. Using default kernel that came with Rom......Franco I believe. I've tried a few different kernels and problem happens same way. The correct logcat is the one shown as attachment. Thank you again.
Sent from my HTC One
full wipe and install the lastest miui. flash modem .84 and if still happens, along with logcat post the last_dmseg (/proc/last_dmseg or something like that).so we can see if its rom or kernel problem.
opssemnik said:
full wipe and install the lastest miui. flash modem .84 and if still happens, along with logcat post the last_dmseg (/proc/last_dmseg or something like that).so we can see if its rom or kernel problem.
Click to expand...
Click to collapse
I appreciate the feedback. Is there something you see in the logcat that leads you to believe a wipe is in order?
Sent from my HTC One
Flyin18T said:
I appreciate the feedback. Is there something you see in the logcat that leads you to believe a wipe is in order?
Sent from my HTC One
Click to expand...
Click to collapse
11-30 13:24:20.132 D/libEGL (28504): loaded /system/lib/egl/libGLESv2_adreno200.so
11-30 13:24:20.132 E/AndroidRuntime( 952): FATAL EXCEPTION: main
11-30 13:24:20.132 E/AndroidRuntime( 952): java.lang.RuntimeException: android.os.DeadObjectException
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.net.TrafficStats.getMobileIfaces(TrafficStats.java:581)
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.net.TrafficStats.getMobileTxPackets(TrafficStats.java:270)
11-30 13:24:20.132 E/AndroidRuntime( 952): at com.android.internal.telephony.DataConnectionTracker$TxRxSum.updateTxRxSum(DataConnectionTracker.java:400)
11-30 13:24:20.132 E/AndroidRuntime( 952): at com.android.internal.telephony.DataConnectionTracker.updateDataActivity(DataConnectionTracker.java:1204)
11-30 13:24:20.132 E/AndroidRuntime( 952): at com.android.internal.telephony.DataConnectionTracker$2.run(DataConnectionTracker.java:326)
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.os.Handler.handleCallback(Handler.java:725)
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.os.Handler.dispatchMessage(Handler.java:92)
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.os.Looper.loop(Looper.java:137)
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.app.ActivityThread.main(ActivityThread.java:5071)
11-30 13:24:20.132 E/AndroidRuntime( 952): at java.lang.reflect.Method.invokeNative(Native Method)
11-30 13:24:20.132 E/AndroidRuntime( 952): at java.lang.reflect.Method.invoke(Method.java:511)
11-30 13:24:20.132 E/AndroidRuntime( 952): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:808)
11-30 13:24:20.132 E/AndroidRuntime( 952): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:575)
11-30 13:24:20.132 E/AndroidRuntime( 952): at dalvik.system.NativeStart.main(Native Method)
11-30 13:24:20.132 E/AndroidRuntime( 952): Caused by: android.os.DeadObjectException
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.os.BinderProxy.transact(Native Method)
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.net.INetworkStatsService$Stub$Proxy.getMobileIfaces(INetworkStatsService.java:232)
11-30 13:24:20.132 E/AndroidRuntime( 952): at android.net.TrafficStats.getMobileIfaces(TrafficStats.java:579)
11-30 13:24:20.132 E/AndroidRuntime( 952): ... 13 more
app crash at boot is not a good thing.
The app crash occurred after the phone rebooted from the initial lockup/crash. Either way, it doesn't sound good. I'll get going with wiping and reinstalling. I'll follow up tomorrow with results. Thanks again.
Sent from my HTC One
i know, but that lib crashing means at least 2 other things crashed earlier(didnt read all logcat).
opssemnik said:
i know, but that lib crashing means at least 2 other things crashed earlier(didnt read all logcat).
Click to expand...
Click to collapse
:beer: :thumbup:
Sent from my HTC One
Flyin18T said:
:beer: :thumbup:
Sent from my HTC One
Click to expand...
Click to collapse
every1 needs one from time to time DDD
OK, done, and back online. I'll run around today with the phone and we'll seed what happens.
Sent from my Nexus 4
Had one reboot. Darn. I'll try to get a logcat of it now.
Sent from my Nexus 4
Flyin18T said:
Had one reboot. Darn. I'll try to get a logcat of it now.
Sent from my Nexus 4
Click to expand...
Click to collapse
can u flash stock, and see if it occors on stock? im saying that because i was using cm10.2(4.3.1,b4 kk was out)with my modified franco.kernel with 487mhz gpu oc and 2.05 ghz cpu oc. and it didnt reboot
I am using the stock kernel that comes with miui. Is that what you mean? Shall I try another? On a good note......although it rebooted once today, it did not reboot in its usual manner while I was driving and on the phone. I had the logcat recording anticipating it would reboot and nothing happened.
Sent from my Nexus 7 using Tapatalk
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.
I'm having the same problem. Except I can't use the phone at all. I took the SIM card out of the micro sd port where the phone has been working somehow. It was a qlink wireless phone. I put the SIM card in the appropriate spot and factory reset it and now it is saying Unfortunately the Process.com.android.phone Has Stopped. Non-stop. It sometimes stops most of the time it's on the screen 24/7. Idk what to do. I want to use this phone. Please help.
Same Thing (Sprint Prepaid)
I am having the same issue as well, my phone was running crappy so i had performed a factory reset, upon reboot i have been receiving the com.android.phone repeatedly, and its no longer registering with the Sprint prepaid service. From there i decided to enable USB debugging to see if i could get some kind of info with "adb logcat" and this is what i received:
I/ActivityManager( 803): Process com.android.phone (pid 8149) has died.
I/com.skyfire.browser.toolbar.ProcessObserverService( 1302): On process died 8149,1001
I/ActivityManager( 803): Start proc com.android.phone for restart com.android.phone: pid=8196 uid=1001 gids={41001, 3004, 3009, 3005, 1006, 3002, 3001, 3003, 1028, 1015}
V/PhoneApp( 8196): onCreate()...
D/ItsOnAPI( 8196): Unable to load ItsOnOemApi implementation: java.lang.ClassNotFoundException: Didn't find class "com.itsoninc.android.impl.ItsOnOem" on path: DexPathList[[],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
I/ItsOnAPI( 8196): ItsOn is not enabled
I/RoamingUtils( 8196): loadOdmSettings loaded:0
I/RoamingUtils( 8196): load odm settings start:
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/HomeOnly value:0
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/MenuDisplay value:1
I/RoamingUtils( 8196): load odm settings node:./SPA/DomDataGuard/Enabled value:N
I/RoamingUtils( 8196): load odm settings node:./SPA/DomVoiceGuard/Enabled value:Y
I/RoamingUtils( 8196): load odm settings domVoRoam:null domDaRoam:null domVoRoamGd:Y domDaRoamGd:N homeOnly:0 showMemu:1
W/dalvikvm( 8196): threadid=1: thread exiting with uncaught exception (group=0x415cbd58)
E/AndroidRuntime( 8196): FATAL EXCEPTION: main
E/AndroidRuntime( 8196): Process: com.android.phone, PID: 8196
E/AndroidRuntime( 8196): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4439)
E/AndroidRuntime( 8196): at android.app.ActivityThread.access$1600(ActivityThread.java:145)
E/AndroidRuntime( 8196): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1288)
E/AndroidRuntime( 8196): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 8196): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 8196): at android.app.ActivityThread.main(ActivityThread.java:5109)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:800)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
E/AndroidRuntime( 8196): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8196): Caused by: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at java.lang.Integer.invalidInt(Integer.java:137)
E/AndroidRuntime( 8196): at java.lang.Integer.parse(Integer.java:374)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:365)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:331)
E/AndroidRuntime( 8196): at java.lang.Integer.valueOf(Integer.java:489)
E/AndroidRuntime( 8196): at com.android.internal.telephony.RoamingUtils.loadOdmSettings(RoamingUtils.java:315)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaServiceStateTracker.<init>(CdmaServiceStateTracker.java:277)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaLteServiceStateTracker.<init>(CdmaLteServiceStateTracker.java:90)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.initSstIcc(CDMALTEPhone.java:104)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMAPhone.<init>(CDMAPhone.java:162)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.<init>(CDMALTEPhone.java:83)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:129)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:57)
E/AndroidRuntime( 8196): at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:549)
E/AndroidRuntime( 8196): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:44)
E/AndroidRuntime( 8196): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4436)
E/AndroidRuntime( 8196): ... 10 more
W/ActivityManager( 803): Process com.android.phone has crashed too many times: killing!
E/RLOG ( 7954): command timed out pid:8062
It appears that it has something to do with an invalid variable "Y" not being an integer. I am not super familiar with the Android OS, and have only dabbled with it briefly, but i am assuming the problem has been caused by the stock Recovery not wiping the cache on factory reset. Also im assuming that without root access and fastboot working, clearing the cache via ADB isn't going to work either . But as it stands right now I have 2 bricked phones and I just started freelancing, so i am going to be forced into figuring this out, because i need a phone. That's all the insight i can provide as of now, hopefully somebody else around here has more experience in the matter and can give us a hand.
I also experienced the same thing
I need twrp backup for recovery
hi
Your baseband is unknown ?
hoost3in said:
I am having the same issue as well, my phone was running crappy so i had performed a factory reset, upon reboot i have been receiving the com.android.phone repeatedly, and its no longer registering with the Sprint prepaid service. From there i decided to enable USB debugging to see if i could get some kind of info with "adb logcat" and this is what i received:
I/ActivityManager( 803): Process com.android.phone (pid 8149) has died.
I/com.skyfire.browser.toolbar.ProcessObserverService( 1302): On process died 8149,1001
I/ActivityManager( 803): Start proc com.android.phone for restart com.android.phone: pid=8196 uid=1001 gids={41001, 3004, 3009, 3005, 1006, 3002, 3001, 3003, 1028, 1015}
V/PhoneApp( 8196): onCreate()...
D/ItsOnAPI( 8196): Unable to load ItsOnOemApi implementation: java.lang.ClassNotFoundException: Didn't find class "com.itsoninc.android.impl.ItsOnOem" on path: DexPathList[[],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
I/ItsOnAPI( 8196): ItsOn is not enabled
I/RoamingUtils( 8196): loadOdmSettings loaded:0
I/RoamingUtils( 8196): load odm settings start:
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/HomeOnly value:0
I/RoamingUtils( 8196): load odm settings node:./Customization/RoamPreference/MenuDisplay value:1
I/RoamingUtils( 8196): load odm settings node:./SPA/DomDataGuard/Enabled value:N
I/RoamingUtils( 8196): load odm settings node:./SPA/DomVoiceGuard/Enabled value:Y
I/RoamingUtils( 8196): load odm settings domVoRoam:null domDaRoam:null domVoRoamGd:Y domDaRoamGd:N homeOnly:0 showMemu:1
W/dalvikvm( 8196): threadid=1: thread exiting with uncaught exception (group=0x415cbd58)
E/AndroidRuntime( 8196): FATAL EXCEPTION: main
E/AndroidRuntime( 8196): Process: com.android.phone, PID: 8196
E/AndroidRuntime( 8196): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4439)
E/AndroidRuntime( 8196): at android.app.ActivityThread.access$1600(ActivityThread.java:145)
E/AndroidRuntime( 8196): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1288)
E/AndroidRuntime( 8196): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 8196): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 8196): at android.app.ActivityThread.main(ActivityThread.java:5109)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 8196): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:800)
E/AndroidRuntime( 8196): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
E/AndroidRuntime( 8196): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 8196): Caused by: java.lang.NumberFormatException: Invalid int: "Y"
E/AndroidRuntime( 8196): at java.lang.Integer.invalidInt(Integer.java:137)
E/AndroidRuntime( 8196): at java.lang.Integer.parse(Integer.java:374)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:365)
E/AndroidRuntime( 8196): at java.lang.Integer.parseInt(Integer.java:331)
E/AndroidRuntime( 8196): at java.lang.Integer.valueOf(Integer.java:489)
E/AndroidRuntime( 8196): at com.android.internal.telephony.RoamingUtils.loadOdmSettings(RoamingUtils.java:315)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaServiceStateTracker.<init>(CdmaServiceStateTracker.java:277)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CdmaLteServiceStateTracker.<init>(CdmaLteServiceStateTracker.java:90)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.initSstIcc(CDMALTEPhone.java:104)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMAPhone.<init>(CDMAPhone.java:162)
E/AndroidRuntime( 8196): at com.android.internal.telephony.cdma.CDMALTEPhone.<init>(CDMALTEPhone.java:83)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:129)
E/AndroidRuntime( 8196): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:57)
E/AndroidRuntime( 8196): at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:549)
E/AndroidRuntime( 8196): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:44)
E/AndroidRuntime( 8196): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
E/AndroidRuntime( 8196): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4436)
E/AndroidRuntime( 8196): ... 10 more
W/ActivityManager( 803): Process com.android.phone has crashed too many times: killing!
E/RLOG ( 7954): command timed out pid:8062
It appears that it has something to do with an invalid variable "Y" not being an integer. I am not super familiar with the Android OS, and have only dabbled with it briefly, but i am assuming the problem has been caused by the stock Recovery not wiping the cache on factory reset. Also im assuming that without root access and fastboot working, clearing the cache via ADB isn't going to work either . But as it stands right now I have 2 bricked phones and I just started freelancing, so i am going to be forced into figuring this out, because i need a phone. That's all the insight i can provide as of now, hopefully somebody else around here has more experience in the matter and can give us a hand.
Click to expand...
Click to collapse
Ever make any progress on this? This is the second time this happened to me and I don't want to wait another week for sprint to replace it again! What kind of pos can't be factory reset without basically bricking the phone!
binthe920 said:
Ever make any progress on this? This is the second time this happened to me and I don't want to wait another week for sprint to replace it again! What kind of pos can't be factory reset without basically bricking the phone!
Click to expand...
Click to collapse
Wondering the same as well.
I have the same problem and I can't even go to Sprint, as I don't have service with them
Please help
Solved, sort of, restore a working backup.
The only solution I could get to work is to root using the new aio app method that also installs TWRP. Someone was kind enough to share a functional backup at that point which I restored to mine. Pretty sad that Sharp and Sprint released a phone that you can't factory reset. It's not my backup to share but if you do a search you should be able to find someone to share theirs with you.
binthe920 said:
The only solution I could get to work is to root using the new aio app method that also installs TWRP. Someone was kind enough to share a functional backup at that point which I restored to mine. Pretty sad that Sharp and Sprint released a phone that you can't factory reset. It's not my backup to share but if you do a search you should be able to find someone to share theirs with you.
Click to expand...
Click to collapse
Can you tell me exactly which tool you used to root and custom recovery?
Is it this one? http://androidforums.com/threads/tool-aio-root-unroot-and-recovery-installer-gui-edition.705515/
I know you won't share that other person's backup, but can you send me your own?