"Unfortunately, the process android.process.media has stopped" on MIUI 8 by shumxin
I would like to use MIUI on my OnePlus X, but the error mentioned in the title of this post keeps on popping up very frequently and it renders this beautiful ROM unusable for me.
I've downloaded the ROM from here - https://drive.google.com/file/d/0BzLtOy-IJENIVHpFVURBbjF4UVE/view (after watching this video - https://www.youtube.com/watch?v=7u25-UAe6JA).
In order to resolve the issue, I've tried a lot of things like clearing data/cache for apps like Google Play Services, Downloads, etc. but nothing helps.
I've installed GApps from http://opengapps.org (ARM, 6.0, pico), but this issue is seen even without GApps.
Any help in resolving the issue would be highly appreciated.
Here's the logcat snippet pertaining to the crash:
09-05 15:28:54.818 29920 29920 E MediaProvider: Can't obtain external volume ID even though it's mounted.
09-05 15:28:54.819 29920 29920 D AndroidRuntime: Shutting down VM
09-05 15:28:54.820 29920 29920 E AndroidRuntime: FATAL EXCEPTION: main
09-05 15:28:54.820 29920 29920 E AndroidRuntime: Process: android.process.media, PID: 29920
09-05 15:28:54.820 29920 29920 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider com.android.providers.media.MediaProvider: java.lang.IllegalArgumentException: Can't obtain external volume ID for external volume.
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:5270)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.app.ActivityThread.installContentProviders(ActivityThread.java:4862)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4802)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.app.ActivityThread.access$1700(ActivityThread.java:155)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1482)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5539)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Can't obtain external volume ID for external volume.
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at com.android.providers.media.MediaProvider.attachVolume(MediaProvider.java:5458)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at com.android.providers.media.MediaProvider.onCreate(MediaProvider.java:656)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.content.ContentProvider.attachInfo(ContentProvider.java:1748)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.content.ContentProvider.attachInfo(ContentProvider.java:1723)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: at android.app.ActivityThread.installProvider(ActivityThread.java:5267)
09-05 15:28:54.820 29920 29920 E AndroidRuntime: ... 10 more
Click to expand...
Click to collapse
Clean flash the ROM and try not to use gapps. See whether the problem persists. if not use this to app to get play store
https://drive.google.com/file/d/0B1MKgV6T8Z20YWFCVUtmOHhkY28/view?usp=sharing
sundhar88 said:
Clean flash the ROM and try not to use gapps. See whether the problem persists. if not use this to app to get play store
https://drive.google.com/file/d/0B1MKgV6T8Z20YWFCVUtmOHhkY28/view?usp=sharing
Click to expand...
Click to collapse
What do you mean by clean flash? My OnePlus X was running Paranoid Android 7.2.1 ROM and TWRP 3.1.1.1 version. I installed the MIUI ROM by shumxin after cleaning system, boot, data, cache partitions. Also, as mentioned in the OP, I get this issue even without any GApps installed. Also, the link you shared gives this message "We're sorry. You can't access this item because it is in violation of our Terms of Service".
amaldhure said:
I would like to use MIUI on my OnePlus X, but the error mentioned in the title of this post keeps on popping up very frequently and it renders this beautiful ROM unusable for me.
I've downloaded the ROM from here - https://drive.google.com/file/d/0BzLtOy-IJENIVHpFVURBbjF4UVE/view (after watching this video - https://www.youtube.com/watch?v=7u25-UAe6JA).
In order to resolve the issue, I've tried a lot of things like clearing data/cache for apps like Google Play Services, Downloads, etc. but nothing helps.
I've installed GApps from http://opengapps.org (ARM, 6.0, pico), but this issue is seen even without GApps.
Any help in resolving the issue would be highly appreciated.
Here's the logcat snippet pertaining to the crash:
Click to expand...
Click to collapse
Download this rom, its pretty stable than the one installed https://drive.google.com/file/d/0B1MKgV6T8Z20STNiUGN2R09iazg/view
cva_kabil said:
Download this rom, its pretty stable than the one installed https://drive.google.com/file/d/0B1MKgV6T8Z20STNiUGN2R09iazg/view
Click to expand...
Click to collapse
I've tried that ROM as well. But it was giving the same error after installing GApps.
I think I've figured out the root cause of this issue. This issue does not occur for me in case of no SD card in my phone. Could formatting the SD card from MIUI help?
Do not flash gapps with MIUI, Which is the cause.
And clean flash mean you don't have to wipe system. Before flashing MIUI try to flash OOS (latest), boot it up, reboot to recovery and then flash the MIUI.
And PLEASE DON'T USE GAPPS FOR MIUI. IT WON'T WORK AND EVEN IF IT DOES IT MAY CAUSE PROBLEMS.
sundhar88 said:
Do not flash gapps with MIUI, Which is the cause.
And clean flash mean you don't have to wipe system. Before flashing MIUI try to flash OOS (latest), boot it up, reboot to recovery and then flash the MIUI.
And PLEASE DON'T USE GAPPS FOR MIUI. IT WON'T WORK AND EVEN IF IT DOES IT MAY CAUSE PROBLEMS.
Click to expand...
Click to collapse
Ah, I see. So if I follow the flashing process you suggested, will the gapps from Oxygen OS be used in MIUI?
amaldhure said:
Ah, I see. So if I follow the flashing process you suggested, will the gapps from Oxygen OS be used in MIUI?
Click to expand...
Click to collapse
NO.
But there will be less errors
Did you download MIUI from this thread?
https://forum.xda-developers.com/oneplus-x/general/rom-miui-v8-oneplus-x-t3591453
Use this app (chinese app) to get play store. It is the only working way.
https://drive.google.com/file/d/0B1MKgV6T8Z20YWFCVUtmOHhkY28/view?usp=sharing
No, I'm using the ROM from this thread https://forum.xda-developers.com/oneplus-x/general/rom-miui-8-oneplus-x-ported-shumxin-t3479012
The other Google Drive link you've shared gives error.
Also, I'm unable to flash OOS 3.1.4 build. Tried from TWRP recovery as well as adb sideload. The process appears to be stuck at 8% progress, tried to keep it for about 35-40 minutes. Also, I'm unable to boot into stock Oxygen OS recovery.
I think I'll try doing a clean flash of the ROM, and install that Play Store app from somewhere.
Related
I use CM10.2, but this bug existed also on CM10.1, I don't know if this is a hard- or software problem.
When I try to use the front facing camera (in various apps, doesn't matter if it's just Camera or Instagram), the application crashes. Here's the log. The most interesting part (I think) is:
Code:
08-28 16:38:17.407 16834 17189 E AndroidRuntime: FATAL EXCEPTION: Camera Handler Thread
08-28 16:38:17.407 16834 17189 E AndroidRuntime: java.lang.RuntimeException: startPreview failed
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.hardware.Camera.startPreview(Native Method)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at com.android.camera.CameraManager$CameraHandler.handleMessage(CameraManager.java:181)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
Bump.
r7s said:
I use CM10.2, but this bug existed also on CM10.1, I don't know if this is a hard- or software problem.
When I try to use the front facing camera (in various apps, doesn't matter if it's just Camera or Instagram), the application crashes. Here's the log. The most interesting part (I think) is:
Code:
08-28 16:38:17.407 16834 17189 E AndroidRuntime: FATAL EXCEPTION: Camera Handler Thread
08-28 16:38:17.407 16834 17189 E AndroidRuntime: java.lang.RuntimeException: startPreview failed
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.hardware.Camera.startPreview(Native Method)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at com.android.camera.CameraManager$CameraHandler.handleMessage(CameraManager.java:181)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.Looper.loop(Looper.java:137)
08-28 16:38:17.407 16834 17189 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse
It definitely a Software problem as CM 10.1 & CM 10.2 are in Nightly state. Problem has been reported in known issues section in CM 10.2 thread here at XDA. It says "Front-facing Camera buggy".
Problem has been reported in known issues section in CM 10.2 thread here at XDA. It says "Front-facing Camera buggy".
Click to expand...
Click to collapse
Thanks, didn't know about it. The thing I've been experiencing this problem under 10.1, too, but I haven't seen anybody complaining about it in the 10.1 thread.
I just flashed another ROM (Chameleon 3.0.3) and I still have the same problem. I think it might be a hardware issue.
Bumpity bump.
Have you tried flashing full stock ROM? Non point in concluding it's a hardware fault unless you've eliminated the software side of things. So far you haven't.
Sent from a galaxy far, far away
Hey guys
This app is a result of me getting tired of some roms providing some features and some not.
So I created the PocketMode app in almost 6 hrs and it was my first android app.
This is the second iteration of the app and is completely revamped and greatly improved(I mean a lot....lot).
FEATURES:
1) Disables all enabled gestures and the fingerprint sensor while in pocket.
2) Full control of your phone's pocketmode service.
3) You won't see the fingerprint sensor getting unresponsive sometimes. Greatly improved the pocketmode part of the app.
4) You can toggle all the available gestures
5) Swap Home and Back Buttons
6) A little bit of theming
7) Starts automatically at boot, so you don't need to do anything except grant superuser rights.
8) HBM and sRGB modes included.
9) It works. 'nuf said !!
INSTRUCTIONS:
1) Download the apk from the second post.
2) Install like normal app.
3) open it for first time and grant root access.
4) Then enjoy the great UI
NOTE:
1) It performs perfectly fine in presence of other conflicting apps, like the cyanogenmod/LOS shipped pocketmode app. But I would suggest if you find the performance better of this one, then either uninstall the other app or freeze it because of redundancies in the system.
2) Although I've tested this rigorously, still bugs may be found and you may report them here.
HUGE SHOUTOUT OUT TO YETI-DESIGNS for the 2 amazing icons on this app. @Yeti12
Original thread :: https://forum.xda-developers.com/oneplus-3/themes/app-pocketmode-roms-compatible-t3546798
Downloads, Sreenshots and Changelog
DOWNLOAD FROM HERE
Changelog:
V1.0.0 :: 08-02-2017
LOOK FOR YOURSELVES.
V1.2.0 :: 06-03-2017
1) Added option to disable the "Double Tap power button to launch camera" while in pocket.(if your ROM supports it)
2) SUPORT for OxygenOS is added although the features are very limited as OOS handles everything quite well already.
3) Added Sweep2Wake toggles.
4) Added option to restore settings on boot on each page.
5) Various cosmetic changes.
6) Added 2 new icons. All thanks to @Yeti12 (look in the screenshots)
7) Squashed many bugs here and there
8) Many performance updates.
V1.2.1 :: 07-03-2017
1) Fixed force closing on OpenBeta 7.1.1
NOTE :: Uninstall the previous app(if you have it) before installing this.
That's awesome. Instead of mindlessly complaining you actually went out your way to do something about it.
Downloading now. Will give you feedback.
Can not install. Parsing error.
Schrotty35 said:
Can not install. Parsing error.
Click to expand...
Click to collapse
On what rom are you installing? It clearly states 7.1.1 ONLY.
rituj26 said:
On what rom are you installing? It clearly states 7.1.1 ONLY.
Click to expand...
Click to collapse
Latest oos 4.0.2.
Parse error
Have install on 7.1.1 but whene i start get error and fc.
Schrotty35 said:
Have install on 7.1.1 but whene i start get error and fc.
Click to expand...
Click to collapse
Pls provide a logcat and in earlier post you said parse error. What exactly is the problem. Report rom and kernel too.
rituj26 said:
Pls provide a logcat and in earlier post you said parse error. What exactly is the problem. Report rom and kernel too.
Click to expand...
Click to collapse
I use lineage-14.1-20170202-UNOFFICIAL-oneplus3 and whene i start the app i get only a fc.
Pls post a logcat then
Okay guys
People facing the random FCs is due to the new gestures commit. I'll have to take a look at it. And will release soon. But I need to prepare for my exams too, so it might take some time.
rituj26 said:
Okay guys
People facing the random FCs is due to the new gestures commit. I'll have to take a look at it. And will release soon. But I need to prepare for my exams too, so it might take some time.
Click to expand...
Click to collapse
Older roms still work though
App crashes on official lineage os for OP3T at first start
Code:
02-07 22:39:50.044 11074 11074 D AndroidRuntime: Shutting down VM
02-07 22:39:50.045 11074 11074 E AndroidRuntime: FATAL EXCEPTION: main
02-07 22:39:50.045 11074 11074 E AndroidRuntime: Process: com.rituj.pocketmode, PID: 11074
02-07 22:39:50.045 11074 11074 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.rituj.pocketmode/com.rituj.pocketmode.MainActivity}: java.lang.NumberFormatException: For input string: ""
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2665)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6126)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: Caused by: java.lang.NumberFormatException: For input string: ""
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at java.lang.Integer.parseInt(Integer.java:533)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at java.lang.Integer.parseInt(Integer.java:556)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.rituj.pocketmode.MainActivity.isEnabled(MainActivity.java:191)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.rituj.pocketmode.MainActivity.onCreate(MainActivity.java:80)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6679)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2618)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: ... 9 more
02-07 22:39:50.046 3486 4550 W ActivityManager: Force finishing activity com.rituj.pocketmode/.MainActivity
dago said:
App crashes on official lineage os for OP3T at first start
Code:
02-07 22:39:50.044 11074 11074 D AndroidRuntime: Shutting down VM
02-07 22:39:50.045 11074 11074 E AndroidRuntime: FATAL EXCEPTION: main
02-07 22:39:50.045 11074 11074 E AndroidRuntime: Process: com.rituj.pocketmode, PID: 11074
02-07 22:39:50.045 11074 11074 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.rituj.pocketmode/com.rituj.pocketmode.MainActivity}: java.lang.NumberFormatException: For input string: ""
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2665)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6126)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: Caused by: java.lang.NumberFormatException: For input string: ""
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at java.lang.Integer.parseInt(Integer.java:533)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at java.lang.Integer.parseInt(Integer.java:556)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.rituj.pocketmode.MainActivity.isEnabled(MainActivity.java:191)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at com.rituj.pocketmode.MainActivity.onCreate(MainActivity.java:80)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6679)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2618)
02-07 22:39:50.045 11074 11074 E AndroidRuntime: ... 9 more
02-07 22:39:50.046 3486 4550 W ActivityManager: Force finishing activity com.rituj.pocketmode/.MainActivity
Click to expand...
Click to collapse
OP UPDATED!!!
Fixed FC bug and a lot lot more.
Still parsing error on stock OOS 4.0.2.
Sent from my ONEPLUS A3003 using Tapatalk
Kickoff said:
Still parsing error on stock OOS 4.0.2.
Click to expand...
Click to collapse
It's for 7.1.1 only
Working fine on latest official LOS
Hi,
Thanks for the app :good:
Do you thinnk you can add a setting to set the capacitive buttons light timeout? It would be great!
Since you add the option to swap back and recent buttons maybe this is something possible?
Thanks in advance
well I wish this would also work for 7.0 roms on
Oos any luck that it will work in near future ?
I have an Lg G5 (H850), unrooted and fully up to date.
A few months ago I began to have trouble with the Clock app. It crashes several times during use.
I've been able to deduce that this problem occurs when Android Wear is installed, and it makes no difference if my Lg G Watch R is connected to my phone or not.
Another event that seems to trigger Clock crashing is when my phone toggles between service and WiFi, but I cannot be sure if that's the cause.
Here are the failed solutions I've tried:
- Install previous version of Android Wear dating back to before the issue started
- Cleared Data/Cache from Clock app
- Tried to disable Clock, but button is grayed out
- Installed Google Clock. Made no difference
- Disconnected watch, but problem persists
- Reset the watch to manufacturer's
I should add (although I am not sure it's a bug) that every time I clear data/cash from Clock, a new alarm appears set (though tuned off) at 7:00 am January 1st. I've never set this alarm, and whether I leave it there, delete it or switch it on and off (so it changes to current date) doesn't make a difference.
I am including a copy of LogCat that shows the crash. Unfortunately I do not know what to do with the information it provides.
Thanks for any help anyone can provide.
--------- beginning of crash
07-31 10:26:09.541 10690 10690 E AndroidRuntime: FATAL EXCEPTION: main
07-31 10:26:09.541 10690 10690 E AndroidRuntime: Process: com.lge.clock, PID: 10690
07-31 10:26:09.541 10690 10690 E AndroidRuntime: java.lang.IllegalArgumentException: Receiver not registered: [email protected]
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:1047)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:1332)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:608)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.gM(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.gJ(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c.d(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.common.api.c$2.onConnected(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jm.f(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jm.dU(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$h.b(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$h.g(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$b.hy(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.google.android.gms.internal.jl$a.handleMessage(Unknown Source)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6247)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:872)
07-31 10:26:09.541 10690 10690 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:762)
Unexpected solution
After months of fiddling with this problem, I accidentally came across information that lead me to solve another problem and through it; fixing this issue I described.
Kinda silly to answer my own post, but it might help people out there.
While live monitoring Logcat, I decided to toggle WiFi on and off to see what the phone did. My Lg G5 has always been pretty slow to connect.
I noticed that, upon turning WiFi on, my phone went through the whole list of "saved" networks before even attempting to connect to the available ones.
I had a LOAD of saved networks. Most of them from countries I visited.
I cleaned up the list, removing most networks I had saved et voila! Not only did my phone started connecting to WiFi instantly, but my clock app stopped crashing.
I hope this helps someone out there.
Today, completely out of the blue, Whatsapp has started crashing, the log says:
09-15 07:17:09.827 7242 7392 E AndroidRuntime: java.lang.IllegalArgumentException: Jid [email protected] is not fully qualified; should end with @s.whatsapp.net
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at com.whatsapp.a.c.a(SignalProtocolStore.java:88)
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at com.whatsapp.jobqueue.job.SendE2EMessageJob.<init>(SendE2EMessageJob.java:171)
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at com.whatsapp.messaging.v.run(SendMessageRunnable.java:91)
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6
07)
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at com.whatsapp.a.c.b(SignalProtocolStore.java:76)
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at com.whatsapp.a.e.run(Unknown Source)
09-15 07:17:09.827 7242 7392 E AndroidRuntime: at java.lang.Thread.run(Thread.java:762)
Can anyone give me a hint what might be wrong here? Obviously "s.whatsapp.ne" is missing a letter, but why?
I have this issue:
01-09 11:58:07.691 22967 22967 E AndroidRuntime: java.util.concurrent.RejectedExecutionException: Task [email protected] rejected from [email protected][Running, pool size = 17, active threads = 17, queued tasks = 128, completed tasks = 52]
I'm on Nougat 7.1.1, the problem fix after reset and then after two days it's on again.
I'm searching on the internet and some one says is related to background data disabled for some apps, and other says due to AsyncTask queue pool is over 128, it reject every new task to execute.
The devices affected are Google Pixel 7.1.2 7.1.1 samsungs, motorolas and others devices and versions. Some known tracked issues can be found on post similar to this: https://productforums.google.com/fo...ZFBIyW2KE;context-place=forum/phone-by-google
Some one posted the bad code causing issue and the solution to fix it but on AOSP (If I can retrieve the link I will attach to this post for furter analysis)
Trying to speak with Sony support the only thing they can do, is to send the device for repair (thankyou )
So, I wish to know if there's a solution trough ADB or some wise app that can flush Pool queue and free it to permit execution of usage data, or something else
I'll post the entire log for further info
01-09 11:37:22.687 14737 14737 E AndroidRuntime: FATAL EXCEPTION: main
01-09 11:37:22.687 14737 14737 E AndroidRuntime: Process: com.android.settings,PID: 14737
01-09 11:37:22.687 14737 14737 E AndroidRuntime: java.util.concurrent.RejectedExecutionException: Task [email protected] rejected from [email protected][Running, pool size = 17, active threads = 17, queued tasks = 128, completed tasks = 74]
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2049)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:814)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1360)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask.executeOnExecutor(AsyncTask.java:623)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.AppDataUsagePreference$UidDetailTask.bindView(AppDataUsagePreference.j
ava:93)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.AppDataUsagePreference.<init>(AppDataUsagePreference.java:49)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.DataUsageList.bindStats(DataUsageList.java:483)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.DataUsageList$3.onLoadFinished(DataUsageList.java:656)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.settings.datausage.DataUsageList$3.onLoadFinished(DataUsageList.java:653)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.app.LoaderManagerImpl$LoaderInfo.callOnLoadFinished(LoaderManager.java:489)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.app.LoaderManagerImpl$LoaderInfo.onLoadComplete(LoaderManager.java:457)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.content.Loader.deliverResult(Loader.java:144)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.content.AsyncTaskLoader.dispatchOnLoadComplete(AsyncTaskLoader.java:265)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.content.AsyncTaskLoader$LoadTask.onPostExecute(AsyncTaskLoader.java:92)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:667)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask.-wrap1(AsyncTask.java)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:684)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.os.Looper.loop(Looper.java:241)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6274)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
01-09 11:37:22.687 14737 14737 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)