Database Users

MIUI 2.4.20 gets utterly destroyed by an app install sometimes

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.

[Q] Nexus 7 Google Play Crash Problem

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.

Anyone know how to read a logcat?

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

com.androiphone stoped

Need help. In all rom 12.1 cm I install it appears me the message com.androiphone stop . already installed cm12.1 by Rox , Blissboop and Resurrection Remix all the times with clear install. Ihave I9301 and 2.8.5 TWRP. What can I do?

noslen69 said:
Need help. In all rom 12.1 cm I install it appears me the message com.androiphone stop . already installed cm12.1 by Rox , Blissboop and Resurrection Remix all the times with clear install. Ihave I9301 and 2.8.5 TWRP. What can I do?
Click to expand...
Click to collapse
Do you use xposed by any chance.
I have this same problem with CM 12.1, Galaxy S3 Neo GT-I9301i. I did a logcat which looks like so, at the moment of process crash:
Code:
--------- beginning of crash
E/AndroidRuntime( 1256): FATAL EXCEPTION: main
E/AndroidRuntime( 1256): Process: com.android.phone, PID: 1256
E/AndroidRuntime( 1256): java.lang.NullPointerException: Attempt to invoke virtual method 'void java.util.ArrayList.clear()' on a null object reference
E/AndroidRuntime( 1256): at com.android.internal.telephony.dataconnection.DcTracker.createAllApnList(DcTracker.java:2546)
E/AndroidRuntime( 1256): at com.android.internal.telephony.dataconnection.DcTracker.tryRestartDataConnections(DcTracker.java:1541)
E/AndroidRuntime( 1256): at com.android.internal.telephony.dataconnection.DcTracker.handleMessage(DcTracker.java:3085)
E/AndroidRuntime( 1256): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1256): at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime( 1256): at android.app.ActivityThread.main(ActivityThread.java:5294)
E/AndroidRuntime( 1256): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 1256): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 1256): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime( 1256): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
E/AndroidRuntime( 1256): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:115)
And the last line leads me to believe it's the xposed issue. In the first few short tests I made with xposed framework uninstalled, this seems to fix the problem. And I'm trying to find other people to corroborate the issue.
Cheers

No. I dont have xposed instaled. Thanks

Please help me. Her is my logcat about the error com.androidphone stop in every CM 12.1 that i install in my s3 neo 9301I.
Any solution or back to stock. Thanks if someone cold help me, because i like CM 12.1 very much.
This is my first Logcat and i dont now if is allright.
http://forum.xda-developers.com/attachment.php?attachmentid=3515979&stc=1&d=1445597496

UI subsystem crashes when power-menu should be displayed or another user is selected

Whenever I long-press the power-button or try to switch to another user, the System-UI completely crashes.
My device is rooted with magisk 13 (beta) and has Substratum installed.
Deactivation of Substratum does not help, and uninstalling Magisk leaves the device unbootable (have to reinstall TWRP and restore a backup then).
Code:
07-06 10:40:02.911 E/AndroidRuntime( 1394): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui
07-06 10:40:02.911 E/AndroidRuntime( 1394): android.content.res.Resources$NotFoundException: File res/layout/zzz_op_global_actions_view_port.xml from xml type layout resource ID #0x5030004
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.content.res.ResourcesImpl.loadXmlResourceParser(ResourcesImpl.java:990)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.content.res.Resources.loadXmlResourceParser(Resources.java:2103)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.content.res.Resources.getLayout(Resources.java:1115)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.view.LayoutInflater.inflate(LayoutInflater.java:424)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.view.LayoutInflater.inflate(LayoutInflater.java:377)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.policy.OpGlobalActions.initView(OpGlobalActions.java:258)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.policy.OpGlobalActions.show(OpGlobalActions.java:181)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.policy.OpGlobalActions.showDialog(OpGlobalActions.java:172)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.policy.PhoneWindowManager.showGlobalActionsInternal(PhoneWindowManager.java:1569)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.policy.PhoneWindowManager.powerLongPress(PhoneWindowManager.java:1414)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.policy.PhoneWindowManager.-wrap15(PhoneWindowManager.java)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.policy.PhoneWindowManager$PolicyHandler.handleMessage(PhoneWindowManager.java:896)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.os.Handler.dispatchMessage(Handler.java:102)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.os.Looper.loop(Looper.java:154)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.os.HandlerThread.run(HandlerThread.java:61)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at com.android.server.ServiceThread.run(ServiceThread.java:46)
07-06 10:40:02.911 E/AndroidRuntime( 1394): Caused by: java.io.FileNotFoundException: res/layout/zzz_op_global_actions_view_port.xml
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.content.res.AssetManager.openXmlAssetNative(Native Method)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:542)
07-06 10:40:02.911 E/AndroidRuntime( 1394): at android.content.res.ResourcesImpl.loadXmlResourceParser(ResourcesImpl.java:975)
07-06 10:40:02.911 E/AndroidRuntime( 1394): ... 15 more
Any idea, how to fix this?
Thanks in advance!

do you have black notifications?
For dark notifications, android and systemui both overlays must be installed. skipping one of them will give you unreadable notifications
Android overlay causes softboot when power button is pressed (instead of showing power menu). This is not a theme bug and happens on all ROMS without OMS. If you cant live with this, dont use dark notifs and dont install android overlay

tadessi said:
do you have black notifications?
Click to expand...
Click to collapse
No, I have the standard theme and notifications show in light colour.
Had installed Rounded UI theme in substratum, but the problem persists, when all overlays are deactivated.

kr_ke said:
No, I have the standard theme and notifications show in light colour.
Had installed Rounded UI theme in substratum, but the problem persists, when all overlays are deactivated.
Click to expand...
Click to collapse
I suggest you the below
First reboot to TWRP and flash the legacy zip
/sdcard/substratum/SubstratumRescue_Legacy.zip
Reboot and check
If it still doesn't work dirty flash the complete 4.5.5 zip which will overwrite your system ui and your problem should be fixed.
Sent from my OnePlus5 using XDA Labs

Meanwhile the problem seems to be solved.
Cause the last OTA caused the device to stuck in boot process, I tapped on 'forget my password' on the OnePlus-Recovery. This really cleaned up everything.
But be carefull: I don't know if the internal storage gets wiped too.
After this I flashed TWRP and Magisk and everything works again.