Hi,
I use black shark 2 pro joyui 11 20.09.25 DLTR2009250OS00MQ2, my machine has an android.process.media error. I have tried everything but it did not solve the problem. So do you have a way to deal with it. Thank you.
Related
hello friends,
i have htc buzz, bought a half year ago, then rooted my device and installed diff roms like cm7, zeromod, and yesterday install splashmod v1.5 final it was running fine after few hours, i chose to install radio_13.55.55.24h, after installing radio i coudnt be able run some apps like i cannot run gallery, camera...
the error says like this when i try use my mobile " the process android.process.media has stopped working unexpectedly" ---> force close. this error is annoying me as i cudnt use my mobile properly.
i think the problem is in the radio_13.55.55.24h, bcz before flashing the radio my mobile worked gud..
plz suggest me the best possible solution friends..
thank u
take a nandroid back up first..
Try these..
First goto recovery and in advance goto fix permissions.if this falls to solve your problem, try flashing another radio version.
Sent from my HTC Wildfire using xda premium
01-23 22:34:40.767 F/DLApplication(5062): DLApplication mListNavitationAvailable: [com.skt.skaf.l001mtm091, com.google.android.apps.maps, kt.navi, com.mnsoft.lgunavi, com.autonavi.xmgd.navigator.samsung, com.here.app.maps]
Had a random reboot and this was the only FATAL error from the catlog. Anyone know what this means?
i got this problem also and the log is same as yours.
something my note4 got crash and freeze. The only solution is remove the battery and reset. I have tried to remove xposed , unable supersu, or install other xda rom. Now i flash back to the oldest custom rom but the problem still randomly appear. This made me very annoying.
I found no sudden crash happened if i playing music. somtimes signal change will crash also. (form lte to 3g). anyone can help me?
Sorry to drag up an old thread but did you figure this out?
Mine had 2 random crash/reboots today, so I installed catlog, and same issue as you guys, but I was only looking through gallery, it's come up in the log again, but hasn't crashed my note 4 again.
Greetings fellows! Today I have flashed CM 13.0 on my Redmi 3S Prime (land). After flashing, the device worked like a charm. However, after 1 or 2 reboots, the Wi-Fi stopped working. I can't turn it on. The button is also grayed out. I reflashed /persist and tried everything. The MAC-address has become 02:00:00... etc. Did anyone have the same issue? Could anyone help me? Thank you in advance! (I also tried reflashing stock Stable global MIUI, same issue. I don't think it would be a hardware issue, since the problem persist since the ROM flashing).
Edit: Solved it somehow. After I flashed MIUI, a few reboots later the wireless worked. No idea why.
coda00 said:
Greetings fellows! Today I have flashed CM 13.0 on my Redmi 3S Prime (land). After flashing, the device worked like a charm. However, after 1 or 2 reboots, the Wi-Fi stopped working. I can't turn it on. The button is also grayed out. I reflashed /persist and tried everything. The MAC-address has become 02:00:00... etc. Did anyone have the same issue? Could anyone help me? Thank you in advance! (I also tried reflashing stock Stable global MIUI, same issue. I don't think it would be a hardware issue, since the problem persist since the ROM flashing).
Edit: Solved it somehow. After I flashed MIUI, a few reboots later the wireless worked. No idea why.
Click to expand...
Click to collapse
I'm also facing the same problem . . Plz help out
Hi! My brother has this phone (X Force) and he gets "com.android.phone has stopped" errors every ~6 months. The phone is unusable in this state (this error appears constantly).
Question: have you had this issue or know how to fix it?
Only full wipe helps, clearing phone system apps does not help. I would flash unofficial ROM, but I'm not sure if it will be stable enough for my brother.
Thanks a lot!
It's 25.221.9 OS version (Android 7.0, security: 1 Oct 2017)
Hello,
i have a very frustrating problem with my Redmi Note 7 global.
It started on stock global rom after ca. 2 weeks of usage.
The UI crashed randomly with the error message "find device closed unexpectedly".
When phone was idle or in use. It doesn't matter. Sometimes it happens 3 times in 5 Minutes, sometimes it's stable for 2 days....
So i decided to unlock bootloader and go for .eu rom. Same problem...
I debloated everything with the SAKI tool. Same problem...
I even removed com.xiaomi.finddevice. Same problem but without the error message.
After that, i had enough of that "find device" thing. I went for bootleggers.
And, guess what, same problem. Of course without the error message.
Now i'm back at an untouched and locked Global Stable via MiFlashTool.
And the problem is still there...
I think it's faulty hardware, right? Or maybe my SIM card? Anyone with the same issue?
Because i'm going to get a refund. I can't waste more time on that issue. My old Mi A1 runs without any problems.
Thanks in advantage.