Database Users

Market Randomly FC?

ok so i was reading some older threads but they dont seem to help...all of a sudden i decided to download an app in the market and it lets me click install and it says "your app is now being installed" and then bam im hit with a force close...ive tried clearing data reinstalling my rom...i even upgraded CWM3 (not that would do anything) but ive tried a few things and it still force closes...

Did you try clearing the cache on the market? You can also look for the new market APk somewhere. I've heard it runs a lot better. I think the newest is 2.2.11 hope that helps

thanks...i tried it cleared data and cache...and actually saw that my newest version was .11 but it still force closed ...i got the app to d/l to 100% but then it FC...so i tried flashing a diff rom which sucks cuz i lost all my data had to start from scratch no FC so i flashed back to quantum again and everything looked good then bam FC...

[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.

Help, lost market updating Civato mix from c3 to c6.

I just updated Civato's c3 mix to c6. I did not do a full wipe reset ( I didn't want to reinstall everything) and have lost Market. I downloaded the vending.apk linked in his rom section and installed rebooted.
Still nothing.
Everything else works fine so far. I just keep getting "no application installed".
Other than reinstalling with a reset wipe, any ideas on fixing my mistake?
Thank You

GullyFoyle said:
I just updated Civato's c3 mix to c6. I did not do a full wipe reset ( I didn't want to reinstall everything) and have lost Market. I downloaded the vending.apk linked in his rom section and installed rebooted.
Still nothing.
Everything else works fine so far. I just keep getting "no application installed".
Other than reinstalling with a reset wipe, any ideas on fixing my mistake?
Thank You
Click to expand...
Click to collapse
Interesting. Just yesterday I had issues with my Phones Market app. Force Closes after it started. So I downloaded and installed the new market app. Here's where it got interesting.
Not sure if I deleted the old on the first attempt, or before the second attempt, but when I finished, I selected Market from the launcher "no application found". So I uninstalled all market apps. Installed the new, and from the launcher "no application installed" again! Checked my "apps" and the market icon worked! Had to delet the old icon from my launcher, and drop the new one there.
So my guess, is uninstall the old before installing the new. Remove all traces of it.

I did fix it.
I tried the Civato fix of renaming vending.apk and dlding another placing it in system/app and rebooting. No luck. I tried installing the app manually and received the "no application found" warning.
Luckily I had one sitting in Titanium backup. It reinstalled an older version and I did have to delete the old icon.
Just strange that it would not install the way it should.

Yeah, I remember reading about it in that roms thread. Seems to be a rom specific issue with it. Glad you're up and running.

GullyFoyle said:
I did fix it.
I tried the Civato fix of renaming vending.apk and dlding another placing it in system/app and rebooting. No luck. I tried installing the app manually and received the "no application found" warning.
Luckily I had one sitting in Titanium backup. It reinstalled an older version and I did have to delete the old icon.
Just strange that it would not install the way it should.
Click to expand...
Click to collapse
I know and sorry for the trouble , it has got something to do with the 3.1.6 and 3.2 Market. If you install that version it is hard to revert back to the original A500 market (1.0.28) without doing a full wipe.
I posted it on my thread , that it is better to stay with old market , make a NANdroid backup and then flash the rom with new marked to check it out if you like it.
I'm really sorry for your trouble , I didn't notice the problem myself until I tried to revert back to the Old market.
I think all the roms with New (leaked) 3.2 market will have the same problem if you want to revert back to the old market. A full wipe or a titanium backup is the only solution then.

I've only had my A500 for a couple of weeks, but I've already tried quite a few ROM's since then, and the funny thing is, 75% of the time, there's a market issue! Dunno if it's just me or what. It typically only happens with the ICS market leak. Maybe some devices just don't like it. But anyway, I seem to have come up with a universal fix that has worked every time I've tried it. I just posted about it here. Basically, what you're doing is completely removing the market and all traces left behind, rebooting, injecting the 3.1.6 market, and rebooting again. It's almost too easy

Bloodflame said:
I've only had my A500 for a couple of weeks, but I've already tried quite a few ROM's since then, and the funny thing is, 75% of the time, there's a market issue! Dunno if it's just me or what. It typically only happens with the ICS market leak. Maybe some devices just don't like it. But anyway, I seem to have come up with a universal fix that has worked every time I've tried it. I just posted about it here. Basically, what you're doing is completely removing the market and all traces left behind, rebooting, injecting the 3.1.6 market, and rebooting again. It's almost too easy
Click to expand...
Click to collapse
Thanks and yep , I think it is some problem the way 3.2 market (leaked version) is intigrated into the system , on the full ICS 4.0 there will be no problem I guess but on HC3.2 it got some problems.
Edit:
The A500 uses a market simular like the website android market , it is intigrated into the system , I did a test , even when I delete the vending apk and marketupdater apk in the rom before flashing it , it still installs the 1.0.28version and I think that there it goes wrong when you install a other Market version and then try to go back.
I stick with the 1.0.28 version on the A500 , I think this web-layout is the more clearer one , 2.3.6 is ok but 3.1.5 and up to 3.2 got to small fonts and icons for me and is good for phones but not tablets in my opinion , the only good in those new versions is the rotation where the 1.028 only got horizontal view.

civato said:
I know and sorry for the trouble , it has got something to do with the 3.1.6 and 3.2 Market. If you install that version it is hard to revert back to the original A500 market (1.0.28) without doing a full wipe.
I posted it on my thread , that it is better to stay with old market , make a NANdroid backup and then flash the rom with new marked to check it out if you like it.
I'm really sorry for your trouble , I didn't notice the problem myself until I tried to revert back to the Old market.
I think all the roms with New (leaked) 3.2 market will have the same problem if you want to revert back to the old market. A full wipe or a titanium backup is the only solution then.
Click to expand...
Click to collapse
Don't be so hard on yourself. You have the nerve to give people new roms to play with. Nothings perfect and will always have minor issues we learn to work around. Just keep doing your thing. Believe me, people appreciate it more than you know

civato said:
I know and sorry for the trouble...
Click to expand...
Click to collapse
No need to apologize. I read the instructions and tried it anyway.
I'm very happy with your rom so thank you for all the time and effort.
I'm using Thors kernel and have no complaints.
We only learn from our mistakes and this was a very minor lesson.
I just discovered I have the "Error purchasing" problem.
Any ideas on a fix? I cleared cache no luck.
Thank You

go to the android market with Google webbrowser. Market acount settings .Make sure your device isn't hidden in menu.
Try downloading and installing true android market from the webpage and see if your tablet starts installing the picked app. If it doesn't. Your tablet is hidden in menu of the devices and you need to change that in your market account settings.

Fixed it, fingers crossed.
I tried to uninstall it from Titanium Backup and received the message that Finsky.apk would uninstall.
Since I was not certain which version of Vending.apk and Finsky.apk were on the tablet, I pulled them both from Thors 10 rom.
I then did the usual, rename the old ones, copy the new ones, force stop, clear cache and data, delete account, reboot, login, create new account.
Works fine now.
Are Vending.apk and Finsky.apk linked in some way? Previously I tried different versions of just Vending.apk and had either the error purchasing or fc when checking my apps.
Thank You

Well it seems to be that the finsky.apk is linked.
Thanks for the info.

civato said:
Well it seems to be that the finsky.apk is linked.
Thanks for the info.
Click to expand...
Click to collapse
It is linked - I have noticed this before. But check my last post on the first page. It's not necessarily required for the market to run (at least, with version 3.x) because I have removed it entirely. By removing all traces of the market (finsky.apk, vending.apk, and clearing cache) a fresh market apk can be pasted into /system/app with the permissions set to rx-r--r-- and it should run just fine.
Another thing which apparently works (who knows why) is going to Android settings, and selecting your language (even though it's already selected) and then running the market again. Not sure if that applies to tablets, but I remember having to do it with my phone on certain ROM's & market versions.

Problems with a new CM7 install

Hey guys. I've had it with MIUI. and i'm ready to switch to a new rom. i figured now was as good a time as any to try out CM7. So i downloaded the latest stable version, backed up my existing install and flashed. The phone got stuck at the bootscreen. I assumed it was because i neglected to wipe data and cache, so i went back, wiped everything, reflashed and booted into CM7(after an extensive wait)
Everything was running great and i just finished restoring my apps with MyBackup. I was getting FCs on a few apps, but i chocked it up to CM7 not having all the components that some of those apps require. I was about to start removing the offenders when the phone crashed and went back to the bootscreen. It sat there for 2 hours before i pulled the battery and restored back to MIUI.
In short, i really want to try out CM7, but if it's going to be this unstable, obviously it won't cut it. Am i doing something wrong??

Some apps just do not play nicely when being restored from a backup. Can you restore apps 1 at a time so that you only get the apps that you know work? Then re-download the apps that are causing problems.

Possibly. That seems like an unnecessary step though. Would a rom really crash because of app incompatibility? I thought they would just FC every time i tried to run them, not blow up the whole ROM.

If you are using ROM MANAGER you can try to use the utility for "Fix Permissions". I'm sure there is a way to do it in the recovery them selves, but the process escapes me.
This is not an uncommon requirement when restoring from one complex ROM to another.

I had some quirkiness restoring a few apps with Titanium backup. I ended up just reinstalling them from Market and haven't had issues since. Also, after restoring my contacts with Mobile Backup II, I could not edit them from the phone. Force closes. Had to delete them and re-sync with Gmail and exchange server. No problems after that.

I have flashed Synergy, Swagged Out Stock, SavagedZen, and a few others and always wandered back to CM7. In my experience, whenever you switch ROMs like that, there are always quirks, so I have taken to getting apps one at a time from MyBackup Root when I do switch. And yeah, I have had App conflicts cause forced bootloops before, it is not completely unheard of. I second the notion of installing one at a time, and Market DLing any that force loops. And as always, I reccomend a cache/dalvik/data whipe when switching full roms.

Market Issues

I've been running EI22 since the first OTA day and I now have an interesting issue. I've tried stock, deodexed, and ACS 3.5 and had no issues. But I switched back to the latest deodexed stock rom and now my market won't update. I can't clear the cache or user data in the applications menu either.
Wouldn't be a big deal but it keeps giving me a network error when I try to go to my apps from the market screen.
Anyone know a fix short of reflashing?

frostedunit said:
I've been running EI22 since the first OTA day and I now have an interesting issue. I've tried stock, deodexed, and ACS 3.5 and had no issues. But I switched back to the latest deodexed stock rom and now my market won't update. I can't clear the cache or user data in the applications menu either.
Wouldn't be a big deal but it keeps giving me a network error when I try to go to my apps from the market screen.
Anyone know a fix short of reflashing?
Click to expand...
Click to collapse
Try using Titanium Backup to clear Market data and also in Google Services Framework. Then with 3G on (icon in notification bar) connect to Market (making sure you signed into Gmail the first time). It should connect. If not make sure your ROM didn't delete the SprintAndroidExtensions and Sprint_updater apks.
Sent from my SPH-D700 using XDA App

Thanks kenny. Clearing the data in Titanium Backup worked. Still took a bit of dirty talk and a few ugly looks to get the market to update though.