Database Users

Sorry! The process android.process.media has stopped unexpectedly. please try again?

So I tried to use the Windows phone android launcher that just came out, I made the mistake of setting it as my default launcher then a black screen comes up and I can't exit out of it, it says something similar to my title (windows phone android has stopped unexpectedly or something like that. I pull out the battery and remove the SD card and it still says it! at this point I'm pretty bummed cause I knew I ruined my second fascinate and I'm not in the return period anymore on this one so i have no choice but to fix my phone with your help...It doesn't end here, I factory reset it from the volume up/down/power/home button press, boot it up, then I get the force close issue! (had this problem on my last fascinate.) at this point I think I'm screwed, I try ODIN to restore back to stock, so I download ODIN, and drivers, and download The ODIN restore file for kernel try it in download mode, still nothing...so I download the recovery one, nothing... at this point I try to squeeze into my SD card even with the force close issue popping up literally every two seconds. I just delete alot of random things off my sd card, hoping it will fix it. nothing. I REMOVE my sd card from the phone, seems to work fine until I try to sync my gmail to it, FORCE CLOSE.... I'm not sure if it will make a difference but im currently downloading and will try the ODIN restore file for system. help is needed, I am a noob

one the file isn't in your sd its on the phone in the data/app folder. your going to have to get into adb and remover the file manully. also since your so far into this there is a new odin file in the development section that has EVERYTHING in one package just go ahead and do that to. when you can make it back into clockwork clear everything as well to make sure
Sent from my SCH-I500 using XDA App

[Q] com.google.process.gapps force close EVO

Question, Im getting alot of "com.google.process.gapps" force closes on my EVO since I restored a few apps thru Titanium Backup. I rooted about a week ago and never had any issues with this. The only apps that I restored was angry birds and a to-do-list app along with all the data that came with the apps. I have tried cleaning caches and restarting the phone and nothing seems to work... what would you suggest? I seen a few threads when i searched - but they were for the G1 and the Captivate, nothing for the EVO... any help would be appriciated...
TIA
JS3

Did u flash any Rom or Theme??

nope, I rooted and am still using the stock ROM... I was going to flash Frost or some thing, but I want to make sure this doesnt carry over to the flashed ROM, or if there is a fix...I would prefere to fix it...
I am also getting a force close on the phone process.... when some one calls me and I ignore the call it force closes the process for the phone as well...

Try reinstalling the gapps.apk. One of them must of been corrupted by the data you restored.

do you know where I can find that at? I have never heard of it...

Also the thing that is confusing, is I can still access my market, maps, latitude, people, gmail... etc
If the apk or files were corrupted, I wouldnt be able to access those apps... i will try to reinstall the apk, but I would like to know what I did to make this error happen, so I know not to do it again...

one thing I think it could have been was there were two "people" files in my Titanium Back up... One was up near the top it said "People 1.00" and then there was one near the bottom with a line thru it that said "People 1.1.1" or some thing to that effect... I deleted the one at the bottom with the line thru it cause I thought I didnt need it any more... could this be wahts up with this error?
I can still access People thru the People widget, but some times it takes abnormally longer to load my list of contacts...
I can also still access Market, Gmail, Maps, Latitude...
I just clciked on Talk and it seems to be the problem, every time I click Talk it brings up the force close issue...
should I just reinstall the Talk.apk?
I also get "com.android.phone" force close when I decline a call...
when I went into my ROM manager, I clicked the "fix permissions" and it says "error occurred while attempting to run privlaged commands"
Any info on any of this would be great...

Anyone out there
Sent from my EVO while tethered into the Matrix thru Wifi...

Okay well I have googled/searched XDA 'til I was green in the face... I still can't figure out how to fix this issue?
Just answer me this, If I do an entire factory reset - will I loose root?
I have wiped the cache thru recovery, Should I try wiping the delvic-cache also, before I factory reset to see if that works??
I can not find any where to download the "gapps.apk" anywhere, I found this one thread that told me to install these in this order:
1. TalkProvider.apk
2. GTalkService.apk
3. Talk.apk
but none of them worked... they wouldnt even install... it just kept saying install failed...so I found another thread with the 2.2 gtalk and it installed...but Im still getting the error...
I have been getting several other errors, like htc.bgp force close (or some thing like that) as well as com.android.phone force close...
So should I just do a NAND restore or should I do a factory reset instead? OR should I run the RUU and start over to root...??
I am at wits end here and am not getting anywhere with searching...
TIA

I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.

Biggest Fro said:
I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.
Click to expand...
Click to collapse
Thanks for the input, I was beginning to think I was invisible... lol... I will try that and see what happens...

Well, I went ahead and tried one more thing before I did what you said to do and I think it worked... I went into my EVO while in Disk Drive mode and I cut my entire Titanium Backup folder out of the phone and copied it onto my Desk top. Then I went into my OLD EVO files from the end of the year and I copied the latest folder into my phone. I then went to Charge only, clicked TB and refreshed the app list... Then I was left with a ton of apps that were not installed on my phone. I then went thru each one and restored the ones that were still installed and deleted the ones that were not... (except for the stock apps that came with the phone), so far so good... I will test it more tonight and see whats up, have not gotten any force closes since I finished...
One thing I would like to know tho - where can I get the stock dialer.apk
Some how it got deleted off my new EVO and when I try to load up one of the htc.dialer.apk from my old EVO - the new one does not recognize it... I am currently useing "dialer one" from the market - but I would prefere to make my NAND back up of the Official stock ROM with all the stock apps...any ideas?
EDIT: Okay, fixed the com.google.process.apps issue but did not fix the other force closes... I guess I will have to try the steps above - and worse case - ill just run the RUU and start all over...

I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App

sw99 said:
I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
But thats the thing - I didnt download anything - I restored two apps, one was opera mini with data and the other was spareparts... then I lost my htc dialer - so I installed Dialer one from the market... I dunno Im just gonna have to do the stpes above and if they dont work - Ill just wipe and run RUU and reroot... no biggie...

Okay I did a NAND restore... then I went thru and set up ALL my apps and settings again and then I did a fresh NAND Backup with clockwork first AND then Amon_Ra... all seemed well except, after I did the Clockwork Backup... I was getting "com.smithmicro.DM has stopped unexpectedly" so searched and read a little and it seemed to have some thing to do with the PRL/Profile updater... so i went into the settings and opened the app manager and cleared the "data" in com.smithmicro.DM and then I restarted the phone and that seemed to fix it... thanks for all the help...
JS3

Horrible market problems

OK so I went from having force closing problems to wifi problems and now it's market problems I'm slowly getting better at this. So when I want to download something on the market it starts, downloads to 10 percent and just stops and I have no idea. This happens almost every 5 or so downloads and I once cleared cache an it worked for just one application and that's it. Thanks for your help guys
Sent from my Liberty using XDA App

Seems to be a known problem, happens to me. Submit a error report!

[Q] marketplace not working
as of today my android marketplace hasnt worked... i click an app to download and install and it starts the download then the thing just disappears from my notification bar and it never actually installs on my device. ive tried this on several different apps, including some that i have downloaded before but decided to uninstall, yet the problem remains. im running cm7 nighty #35 if thats any help. can anyone explain whats up?

First thing I would try is to clear Market cache by going to Settings > Applications > Manage applications > All > Scroll down to Market, select Force Stop then Clear cache, and try downloading the app again.

yeah i had tried that. but no luck, it didnt work. i guess maybe itll fix itself when i update my rom. i dont know

Drum doesn't work did that already I think it's the rom maybe they will fix it soon...
Sent from my Liberty using XDA App

I was having an issue with it as well (but i'm on cm7, if it makes a diff). I did the clear cache/stop updates method which worked great the first time. Then the issue happened again, i cleared cache and rebooted, worked fine. THEN i had the issue again, (but i noticed it seems to have happened after using the clean feature in sd maid). Removed sd maid, cleared cache, havent had a problem since.

[Q] ACS force closing Logs Provider on boot

I'm running the latest version of ACS, and I keep getting a force close loop for "com.sec.android.provider.logsprovider", when I boot. Meaning I tap force close, and it comes right back, giving me no access to my phone. This is after two crashes (using the phone then it turns off). Does anyone have a suggestion? My father's Evo did this too, and he had to scream at Sprint before they'd swap the phone, but it's working fine now. I have the insurance thing on my plan, should I try that? If so, would I have to use Odin first?

Did you try to restore a backup with titanium backup??? I would boot to clockwork recovery and try to fix permissions by going to advanced in the menu.

Already done. I wiped user settings or whatever too. I'm now trying to reflash ACS and it says can't open /sdcard/foo/bar/syndicatefro110-standard-signed.zip (bad) could it be my sdcard? Does Sprint cover those under my hardware thing? I'm using ext4 afaik.

Im not sure if the cover the sd card I want to say no unless it is under a month old. However I wouldnt bring the phone in like that I would odin to a stock unrooted rom. Try to recopy the acs rom to the root of your sd card and then wipe data/factory reset 3 times in clockwork and then try to reinstall the rom.

I've been having issues on all my roms, so I'm thinking it could be my sd card. I'll bring it in as a last resort. Don't want to Odin if I can avoid it. Thanks for the help.

the logs provider has to do with mms and call logs and the sd card shouldn't affect it since it is a system app data/data/com.sec.android.provider.logsprovider. Did you try to clear the dalvik in advanced within clockwork???

That's crazy, I'm having the same exact problem. I was running the latest ACS fine for weeks and then I just rebooted it and BAM, 'Force closes' like crazy!
I reformatted, cleared all cache and factory reset to no avail. I still kept getting the same things pop up. I finally installed it through the zip file the 3rd time and somehow iit's working fine. I lost all my apps and evidently they didn't back up to my google account.
I'm too scared to reboot myphone now since that's what seems to trigger the problem.
Anybody know the source of the problem?

Curious if your getting any oneDram errors in dmesg? Seems like you guys are starting to have those odd errors were seeing in the Bonsai 4.1.0 beta.
Sent from Bonsai 7.0.3

I don't think i saw a oneDram error message, I remember seeing force closes for most of the services or processes that usually run in the background like phone and DRM service.
The persistent force close message that kept popping up was the logs.provider one.

This problem is currently happening to me now
I'm to lazy to fix it now though by the end of the week I'll do something
This happened to me while I had very bad/varying signal
(0-2 bars on a six bar scale)
And low battery
(40%ish)
I clicked on my email app and while it was loading I locked my phone and walked toward a window for better signal
When I looked back at my phone it rebooted by it self and everything is force closing like email and messaging.
Sent from my SPH-D700 using XDA Premium App

Yeah that's very similar to how out started with me too. Actually it might be exactly how it started.
Please let us know what you find out, because I've actually had this problem once before with an ACS rom.

I had my phone do this the other day with the logs provider. Reinstalled the rom (ACS Latest) and the issue went away...
Brother has been having the same issue for weeks on his epic too. He was running Bonsai 4.0.1 getting the same force closes, only his started first when he tried to open his mms app... He installed the latest ACS to see if it was Bonsai, about an hour later got the force closes again until he had an endless loop again.
We checked our memory blocks just for giggles and noticed he has 3 bad blocks while i have 11... cant be the issue...
He would get those force closes on EB13 and DK28 too.
We always do the 3x 3x 3x dance in clockwork before installing a rom too...
Dont know if this info helps or not. He thought about going stock and hitting up a Sprint store today and taking out an insurance claim....

Sorry I missed this thread.
Here's what I want you guys to do.
Back up your sdcard to your pc. ( just the files you wanna save.
Format your sd card with your phone
put the rom zip on your sdcard
Back up everything with your favorite back up program. titanium or mybackup root.
Reboot into cwm make sure it's 3.0.0.6
Wipe data, cache, dalvik 3x's ( don't cheat )
Flash your rom.
Boot your phone.
Restore your back up from your backup program. ( apps only no data )
Reboot into cwm again.
This time only wipe cache and dalvik 3x's ( no cheating )
Reboot and you should be good to go
Sent from my SPH-D700 using Tapatalk

^ This is a guaranteed solution to any unexpected FC problems.

k0nane said:
^ This is a guaranteed solution to any unexpected FC problems.
Click to expand...
Click to collapse
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3

Top Nurse said:
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
I said for FCs, not bricks.

I'm having the exact same problem with the same ROM. The other day it froze after I took a picture and wouldn't respond. Had to do a battery pull after which I was stuck in an endless boot loop.
Tried just reflashing the ROM from SD and no dice, then cleared all caches 3 times and reflashed and I had a working phone again.
Then about 10 minutes ago I was using the phone and it shut down out of nowhere, after that booted back up with a tone of force closes and now the log provider force close won't go away. I'm just going to switch ROMs cause this is ridiculous.

No need to do that. The solution for freezing is excrutiatingly simple - and if it only freezes when you're in the camera, you need only format your SD card.
Do that, wipe data, and reflash, and everything will work 100% perfectly.

i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.

darksideauto said:
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
Click to expand...
Click to collapse
As expected - Nandroid bad data, and your bad data will remain. Use MyBackup Root for that.
Just take a Nandroid backup and restore it when you're running properly - or use the zip in the development section to turn journaling on. No problem.

[Q] CM10 fails after update

Hi,
First time posting here. I've been searching around but I can't seem to find anyone with this issue. Which means I'm likely making a rookie mistake.
I've been running CM7 for a while now w/o issue. Decided to look into the state of ICS and found out JB is where it's at. So I decided to give it a whirl based on some successful posts about it, even at an early stage. I used a 8GB SD and on my latest attempt, I loaded cm-10-20121204-NIGHTLY-encore and gapps-jb-20121011-signed onto EMMC. Afterwards, it booted up fine, got connected to the wifi and looked great. Somewhere along the way, something happens that causes Android to popup a dialog saying it's updating. After that's done, soon after I get a popup that "Unfortunately, Gmail has stopped working." When I open a browser, it immediately closes. If I try the Play store, it pops up, "Network error - retry". So it's like a part of the android comm "stack" gets busted on that update. Weird thing is that if I run the Google search app, it returns results from the web, so some connectivity is still there. But when I click a link, the browser pops up for an instant then closes again. I tried clearing caches, doing resets, reflashing gapps, etc. Nothing seems to work. Is there a log I can activate to maybe get more details?
I've probably tried out 5 installs now, using various recently nightly's up until 1204 w/similar results. I just can't figure out what triggers the update. I even tried w/o installing gapps. In that case, I sent myself a link to the Amazon android app, using the email setup. It installed and I could get apps downloaded and running w/o issue. But eventually after a reboot, android updated and I was right back at the gmail failed mesg, even though I hadn't installed gapps. On another try, I had installed and when I reformatted the SD card, it updated after the reboot and same result.
So, I guess I just don't have a clue at this point as to why this update runs, nor do I know what it changes to break the device. After going rounds w/it for about a week or so, I gave up and reloaded my old 7 image. I'm willing to try again if anyone has a clue what I can do.
Thanks

elmo7 said:
Hi,
First time posting here. I've been searching around but I can't seem to find anyone with this issue. Which means I'm likely making a rookie mistake.
I've been running CM7 for a while now w/o issue. Decided to look into the state of ICS and found out JB is where it's at. So I decided to give it a whirl based on some successful posts about it, even at an early stage. I used a 8GB SD and on my latest attempt, I loaded cm-10-20121204-NIGHTLY-encore and gapps-jb-20121011-signed onto EMMC. Afterwards, it booted up fine, got connected to the wifi and looked great. Somewhere along the way, something happens that causes Android to popup a dialog saying it's updating. After that's done, soon after I get a popup that "Unfortunately, Gmail has stopped working." When I open a browser, it immediately closes. If I try the Play store, it pops up, "Network error - retry". So it's like a part of the android comm "stack" gets busted on that update. Weird thing is that if I run the Google search app, it returns results from the web, so some connectivity is still there. But when I click a link, the browser pops up for an instant then closes again. I tried clearing caches, doing resets, reflashing gapps, etc. Nothing seems to work. Is there a log I can activate to maybe get more details?
I've probably tried out 5 installs now, using various recently nightly's up until 1204 w/similar results. I just can't figure out what triggers the update. I even tried w/o installing gapps. In that case, I sent myself a link to the Amazon android app, using the email setup. It installed and I could get apps downloaded and running w/o issue. But eventually after a reboot, android updated and I was right back at the gmail failed mesg, even though I hadn't installed gapps. On another try, I had installed and when I reformatted the SD card, it updated after the reboot and same result.
So, I guess I just don't have a clue at this point as to why this update runs, nor do I know what it changes to break the device. After going rounds w/it for about a week or so, I gave up and reloaded my old 7 image. I'm willing to try again if anyone has a clue what I can do.
Thanks
Click to expand...
Click to collapse
Did you do a factory reset with recovery before you booted into CM10? It sounds like you have some old apps like Gmail staying on there. Coming from CM7 you really need to wipe first.
Sent from my Nook HD+ using Tapatalk

leapinlar said:
Did you do a factory reset with recovery before you booted into CM10? It sounds like you have some old apps like Gmail staying on there. Coming from CM7 you really need to wipe first.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
CM7 was installed to SD only. CM10 was installed direct to the EMMC.

elmo7 said:
Thanks for the reply.
CM7 was installed to SD only. CM10 was installed direct to the EMMC.
Click to expand...
Click to collapse
What was installed on emmc before? Did you wipe that? You might want to use my format 567 zip on my tips thread linked in my signature.
Sent from my Nook HD+ using Tapatalk

leapinlar said:
What was installed on emmc before? Did you wipe that? You might want to use my format 567 zip on my tips thread linked in my signature.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
B&N stock, whatever ver that was about a year or so ago. I'll check out the 567.
Thanks