Database Info

Market app acting weirdly

Hi guys, I was installing titanium backup the other day, and somehow after the download it got stuck @ installing. I tried restarting my phone, force closing the market app and reopening it but whatever i do it still comes out as 'installing' after it opens. Does anyone know how to fix this? btw im on nordic 2.1 rooted.
Thanks in adv.
(Ive tried going into the market app and clearing the cache, but it didnt help, also i had no 'uninstall updates button both in the market app and market updater app)

Yeah, I've noticed a number of my Market downloads (mostly app updates) tend to get stuck at "Installing". Usually at some point thereafter, the Market app will crash and reload, and things tend to startup sometime after that.
I haven't had any apps get completely stuck like you describe though.

Hm thanks, guess i'll keep waiting till it clears itself :x

hey I'm actually happening the same problem. did you ever figure it out?

Yeah the 2.1 Market seems a lot more flaky than the 1.6. I get a lot of stuck downloads and force closing. (Mostly when I use the Update All function)

ive had a similar problem before. i went into settings > applications > manage applications > market, then chose the options to clear cache and uninstall updates. restarted phone. ran market app, accepted terms n conditions again n all was well.. hope it helps
P.s - jus read your other bit on first post, dont have nordic 2.1 so cant really say, plus in my application settings i have only market, theres no market updater that i can see at mo

Mobzter said:
ive had a similar problem before. i went into settings > applications > manage applications > market, then chose the options to clear cache and uninstall updates. restarted phone. ran market app, accepted terms n conditions again n all was well.. hope it helps
P.s - jus read your other bit on first post, dont have nordic 2.1 so cant really say, plus in my application settings i have only market, theres no market updater that i can see at mo
Click to expand...
Click to collapse
yeah I found this on google shortly after posting this. this worked for me! thanks for the quick reply.
p.s. btw, I'm on global generic.

I had this issue on nordic version, switched to rogers and no issues at all with market now.
Sent from my Canadian Beaver and rooted 2.1 x10a

ptesmoke said:
I had this issue on nordic version, switched to rogers and no issues at all with market now.
Sent from my Canadian Beaver and rooted 2.1 x10a
Click to expand...
Click to collapse
Well i was on nordic, then on global and now on rogers and I had all kind of Problem with the Market, not downloading, force closing/restarting, not installing ect...
I don't think it's related to the firmware since my experience.
Now it doesn't want to finish installing updates or stuff I downloaded from the market and when I try to install, Market force close and restart.

I post about it yesterday
http://forum.xda-developers.com/showpost.php?p=9222129&postcount=7
Did anyone here using fast web installer? Cause it stop working for me too.

zyryck said:
Well i was on nordic, then on global and now on rogers and I had all kind of Problem with the Market, not downloading, force closing/restarting, not installing ect...
I don't think it's related to the firmware since my experience.
Now it doesn't want to finish installing updates or stuff I downloaded from the market and when I try to install, Market force close and restart.
Click to expand...
Click to collapse
Have you by chance been deleting google talk? Without google talk the market encounters all sorts of wonky errors.
Sent from my Canadian Beaver dam and rooted 2.1 x10a

ddanat said:
yeah I found this on google shortly after posting this. this worked for me! thanks for the quick reply.
p.s. btw, I'm on global generic.
Click to expand...
Click to collapse
Yeah, I actually ran into a problem after my previous flash (and then again when I re-flashed today) that when installing or updating an app from the market once it was downloaded and the install actually started, the Market would FC. As such, I couldn't install apps from the market.
I fixed it with the same process, and both times it has corrected the problem and made the market work reliably.

ptesmoke said:
Have you by chance been deleting google talk? Without google talk the market encounters all sorts of wonky errors.
Sent from my Canadian Beaver dam and rooted 2.1 x10a
Click to expand...
Click to collapse
I did in the nordic version and it actually causes the downloads to be "active" but actually not downloading.
I was encountering a different problem but got it resolved by uninstalling the market updates.
I guess one of market's update Is not very stable

Google play error 491

I just got miui 2.5.25 and when I click to download an app from google play I get error 491....
What can I do:'(
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

Clear data in settings/Apps/Google Play Store and try again.

aryehzev said:
I just got miui 2.5.25 and when I click to download an app from google play I get error 491....
What can I do:'(
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Delete your Google account from accounts & sync.
Reboot to recovery, wipe Cache +dalvik.
Reboot.
Add your Google account.
Do this, and it should be fine.

Thank you kgs1992. Worked like a charm on my vzw GSIII after I restored from Titanium Backup and got the 491 error. Found your answer thru a google search. Thanks again.

kenmorgan said:
Thank you kgs1992. Worked like a charm on my vzw GSIII after I restored from Titanium Backup and got the 491 error. Found your answer thru a google search. Thanks again.
Click to expand...
Click to collapse
So is this essentially the same as a 403 and 927 then? Or just same remedy...

sgs22012 said:
So is this essentially the same as a 403 and 927 then? Or just same remedy...
Click to expand...
Click to collapse
It's the only solution to most play store errors.
This should solve it, unless you've modified something or you're using a modified version of play store.
Sent from my Xperia Z using XDA Premium

kgs1992 said:
It's the only solution to most play store errors.
This should solve it, unless you've modified something or you're using a modified version of play store.
Sent from my Xperia Z using XDA Premium
Click to expand...
Click to collapse
Just recently I came across this error more frequently. This only happend to on 4.1.2. Either on Stock Rom or Custom. Happend on my Note 2,the Note 10.1 and on my gf's SGS-2. Until then, having different phones over the years, different Android Versions, I never saw this error. Since its multiple Phlnes, Tablets and Roms over the years, there is no common connection what this could be. Except the Playstore and Android 4.1.2.
Any thoughts on that?

wpkwolfseye said:
Just recently I came across this error more frequently. This only happend to on 4.1.2. Either on Stock Rom or Custom. Happend on my Note 2,the Note 10.1 and on my gf's SGS-2. Until then, having different phones over the years, different Android Versions, I never saw this error. Since its multiple Phlnes, Tablets and Roms over the years, there is no common connection what this could be. Except the Playstore and Android 4.1.2.
Any thoughts on that?
Click to expand...
Click to collapse
It could be some versions of Google Play services I think.
Changing your lcd density is one major cause.
Sometimes changing Roms without wiping triggers it too.
Hard to point out a single culprit when there are so many possible triggers for play store errors.

kgs1992 said:
It could be some versions of Google Play services I think.
Changing your lcd density is one major cause.
Sometimes changing Roms without wiping triggers it too.
Hard to point out a single culprit when there are so many possible triggers for play store errors.
Click to expand...
Click to collapse
I always wipe for different Roms. But out of curiosity, what has changing LCD density to do with that error? Really strikes me odd that something like that could have anything to do with such an error.
However, it seems likely that Google screwed something up with theit Market Services, at least with 4.1.2. Didnt notice that error in other Android Versions.

wpkwolfseye said:
I always wipe for different Roms. But out of curiosity, what has changing LCD density to do with that error? Really strikes me odd that something like that could have anything to do with such an error.
However, it seems likely that Google screwed something up with theit Market Services, at least with 4.1.2. Didnt notice that error in other Android Versions.
Click to expand...
Click to collapse
I'm not sure myself.
Changing density makes some apps unavailable to you on most versions of play store, but on some versions, the app is still available, but downloading it causes an error.

kgs1992 said:
I'm not sure myself.
Changing density makes some apps unavailable to you on most versions of play store, but on some versions, the app is still available, but downloading it causes an error.
Click to expand...
Click to collapse
It recently happens to both our phones (NOTE 2, SGS-2) and the tablet (NOTE 10.1) a lot. All have 4.1.2 running, different ROM's though. And every time deleting the Play Store data, removing the Google account and going into CWM for clearing Cache and Dalvik Cache is not an acceptable solution.
Why is this coming so often recently ?
---------- Post added at 05:44 PM ---------- Previous post was at 05:23 PM ----------
I found this as a possible solution, among several so called solutions which didn't work for most people. I tried that.
Settings -> Language & Keyboard settings -> Select language -> again set English(United States)
Click to expand...
Click to collapse
It works for me again, however I don't see the point that I would need to do that when my native language is a different one. If thats a solution indeed, then surely Google screwed something major up. They can't expect people to switch language to English (US) just for that.

gooooood
kgs1992 said:
Delete your Google account from accounts & sync.
Reboot to recovery, wipe Cache +dalvik.
Reboot.
Add your Google account.
Do this, and it should be fine.
Click to expand...
Click to collapse
you :good: man
that's work with me ...

I want to know why this error happens.
I've had it before and wiping dalvik and cache worked after deleting google account and then re-adding it
However, that was 2 weeks ago and I downloaded some stuff but it's back again and constantly wiping and re-adding is some super BS.
Is there something I can do or anyone can do to get to the bottom of this?
It would help if we knew what exactly error 491 means as well so we could track it down better and squash this.

joshka89 said:
I want to know why this error happens.
I've had it before and wiping dalvik and cache worked after deleting google account and then re-adding it
However, that was 2 weeks ago and I downloaded some stuff but it's back again and constantly wiping and re-adding is some super BS.
Is there something I can do or anyone can do to get to the bottom of this?
It would help if we knew what exactly error 491 means as well so we could track it down better and squash this.
Click to expand...
Click to collapse
Exactly, because the solution everyone says is only a temporary solution at best. And annoying to do everytime. But why does this Error come back all the time and why did I never witness this error over the years before. Only recently in months.
Wolf

have you tried actually using another google account? (just a suggestion)
i too faced a problem with google play after i restore back my apps using titanium backup
and google play wouldn't let me download any file.
I just removed my google account and added it back.
it works.

dannysam said:
have you tried actually using another google account? (just a suggestion)
i too faced a problem with google play after i restore back my apps using titanium backup
and google play wouldn't let me download any file.
I just removed my google account and added it back.
it works.
Click to expand...
Click to collapse
Yes, that works but its not the point. It'll come back, that error. And how often is doing that the point when there is no permanent fix ? I think, and I am really not good with stuff like that so I can't say anything I am really sure about, it is actually a problem with permissions. I am running the ARHD 8.0 on my Note 10.1 and the OMEGA v17 on my Note 2. Two different devices, two different Android Roms.
And yet, after (several times a week) get this Error, I go into CWM and "Fix Permissions". After reboot my Updates start working again on the Market. Until next time. I dont know if that has something to do with it, but it seems too big of a coincidence to just be random, if the "temporary" solution by "Fix Permissions" is making it work again.
I have no idea why that is but I don't seem to be the only one with that Problem as it seems. I dont know if what I assume has any value or is just an assumption but I think it might be worth thinking about it. However, why 2 different Roms on 2 different devices seem to have that problem in common I really dont know.
Wolfseye

wpkwolfseye said:
Yes, that works but its not the point. It'll come back, that error. And how often is doing that the point when there is no permanent fix ? I think, and I am really not good with stuff like that so I can't say anything I am really sure about, it is actually a problem with permissions. I am running the ARHD 8.0 on my Note 10.1 and the OMEGA v17 on my Note 2. Two different devices, two different Android Roms.
And yet, after (several times a week) get this Error, I go into CWM and "Fix Permissions". After reboot my Updates start working again on the Market. Until next time. I dont know if that has something to do with it, but it seems too big of a coincidence to just be random, if the "temporary" solution by "Fix Permissions" is making it work again.
I have no idea why that is but I don't seem to be the only one with that Problem as it seems. I dont know if what I assume has any value or is just an assumption but I think it might be worth thinking about it. However, why 2 different Roms on 2 different devices seem to have that problem in common I really dont know.
Wolfseye
Click to expand...
Click to collapse
go to settings-> accounts and synch(or whatever it says)->google->location settings
disable it
check then google play store

rzr86 said:
go to settings-> accounts and synch(or whatever it says)->google->location settings
disable it
check then google play store
Click to expand...
Click to collapse
Thanks man, I will try that. I just did that Permission thing 10 minutes ago, so I won't see the difference right now. But if the Problem does not come back, I for sure owe you a beer.
Cheers
Wolfseye
P.S: However, by doing that I disable Google Location services entirely. Isn't that kinda counter productive in case of other location dependent things going on ?

Worked for a while, now I get the same error again. Even though Location Services are still deactivated. This is one hell of a annoying error and persistent like hell.
If that continues I will go back to Stock Rom since I have never seen that on my gf's stock SGS-2 yet. Wonder if thats only custom Rom related. Really making me wanna buy and ..... no I wont say it.
Wolfseye

I just rebooted and it all works normal now.
At first I thought wow! Another error but I just remembered I had tb clear the cache for all my apps and dalvic. So just rebooted. No deleting or fixing permissions

Amazon app store won't stay signed in

I'm on a Nexus 7 2013 Cm 10.2.... All else works great but Amazon App store just won't stay signed in. I have the latest version I checked for updates and no luck. Friend has same issue on another phone...
Are there any known issues / fixes? Tried searching couldn't find anything. Thanks

berardi said:
I'm on a Nexus 7 2013 Cm 10.2.... All else works great but Amazon App store just won't stay signed in. I have the latest version I checked for updates and no luck. Friend has same issue on another phone...
Are there any known issues / fixes? Tried searching couldn't find anything. Thanks
Click to expand...
Click to collapse
I´ve experienced the same issue if I kill the Appstore forcefully. Maybe some app ("RAM cleaning/optimizing"...) is doing that in the background?

jesterhead82 said:
I´ve experienced the same issue if I kill the Appstore forcefully. Maybe some app ("RAM cleaning/optimizing"...) is doing that in the background?
Click to expand...
Click to collapse
I don't have anything like that active on my device or the friends.
I also notice when I exit the Appstore, it says Appstore has closed as if it crashed.

The only other idea would be to delete the app data (Manage Apps -> Clear App Data)

berardi said:
I'm on a Nexus 7 2013 Cm 10.2.... All else works great but Amazon App store just won't stay signed in. I have the latest version I checked for updates and no luck. Friend has same issue on another phone...
Are there any known issues / fixes? Tried searching couldn't find anything. Thanks
Click to expand...
Click to collapse
I have a rooted Nook HD+ and this just started happening to me yesterday after I updated to 10.1.3-RC2-ovation.
I tried clearing the cache and data but it didn't work. I finally just deleted and reinstalled the Amazon App Store and now I don't have to log in every time but it does seem slow. I'll report back if it changes.
Hope this helps.

wyrmbyte said:
I have a rooted Nook HD+ and this just started happening to me yesterday after I updated to 10.1.3-RC2-ovation.
I tried clearing the cache and data but it didn't work. I finally just deleted and reinstalled the Amazon App Store and now I don't have to log in every time but it does seem slow. I'll report back if it changes.
Hope this helps.
Click to expand...
Click to collapse
Thanks,
I did the same uninstall / reinstall and it started working right again.
I tried clearing data previously and it didn't resolve, so I guess a full uninstall is required.

berardi said:
Thanks,
I did the same uninstall / reinstall and it started working right again.
I tried clearing data previously and it didn't resolve, so I guess a full uninstall is required.
Click to expand...
Click to collapse
Or maybe not. (sigh) I just had to sign in again to play a game.

Play store error: Insufficient storage available. Help.

Ive searched google and only found topics from a few years back, but for some reason Spotify and SoundCloud will not update in the play store. I get the "insufficient storage available" error. I have about 10gbs of space left over so that's not an issue.
I've cleared the data/cache in the play store and the individual apps and no luck. I've also reflashed Cataclysm thinking that would solve it but still nothing. Any ideas?

Don't know if this will resolve your issue, but have you changed your dpi? Might want to try downloading Multi DPI Play Store

Aria807 said:
Don't know if this will resolve your issue, but have you changed your dpi? Might want to try downloading Multi DPI Play Store
Click to expand...
Click to collapse
I changed my DPI in the cataclysm settings to 82% but i went back to 100% and it didnt fix it. Thanks though. I read something that you can delete a certain file and it should fix it. I used ES file explorer to try and find it but i couldnt find the app folder.

bump

bump

Theres gotta be somewhat of a fix for this. No?

I had this also for quite some time, honestly I suspected an application who caused that message.
After a few days it got fixed by itself.
Maybe it helps to clear the cache

Yea, its pretty weird. It is only happening with 2 apps. Every other app updates fine. Its not a deal breaker as I dont use Spotfy and SoundCloud too much, its just annoying. I've also tried reinstalling the latest Cataclysm but I get a failed attempt everytime. We shall see.

bump

I got the same error when I started using aoip 4.3, and it's just the amazon app for me. It works just fine, but it hasn't been able to update for weeks. I thought it was something to do with amazon's update, since it was isolated on only the one app.
Sent from my Hisense Sero 7 Pro using xda app-developers app

yea now Netflix decided to join the party. Its pretty annoying. Im thinking about switching roms but Cataclysm is just too good.

randysoto5 said:
yea now Netflix decided to join the party. Its pretty annoying. Im thinking about switching roms but Cataclysm is just too good.
Click to expand...
Click to collapse
-Uninstall the problem apps
-Look in /data/data for leftover files with the same or similar name (e.g., Netflix is com.netflix.mediaclient) and delete them.
-Try reinstalling the apps.
Sent from my Nexus 5

So I uninstalled all spotify, soundcloud, es file explorer, and netflix. I used root explorer and went to data/data and found just a spotify file and deleted it. Now they wont download at all and still giving the same insufficient storage error.

Settings>Apps>All
Force stop Google Play. Clear Data/Cache
Force stop Google Services Frameworks. Clear Data/Cache.
Reboot.
That has worked for almost every play store error that I've seen. Let me know if it works for you. Note that the reboot is important.

theesotericone said:
Settings>Apps>All
Force stop Google Play. Clear Data/Cache
Force stop Google Services Frameworks. Clear Data/Cache.
Reboot.
That has worked for almost every play store error that I've seen. Let me know if it works for you. Note that the reboot is important.
Click to expand...
Click to collapse
Followed instructions exactly and am still getting the error.

randysoto5 said:
Followed instructions exactly and am still getting the error.
Click to expand...
Click to collapse
Ouch. Sorry man the cure all doesn't seem to work for you. Go into Play services and see what it says about Storage. Attach a screenie if you can. Worse case I'd reboot recovery and wipe cache/dalvik then format system and reflash again. Does cataclysm have gapps included?

Worst case solution is a data wipe aka factory reset. I had this problem on my old phone. That was always a sign it's time for a fresh flash and wipe.
Sent from my Nexus 5 using Tapatalk

I just got this same error for Netflix. I am running rooted stock 4.4.2 with XPosed (using GravityBox and RootCloak) and TWRP.
Error first occurred last night. No significant changes preceding, Plenty of storage left. Last significant change was the recent update to BusyBox (just throwing out anything). Can still update/install other apps. Since error I have updated my SU Binary.
Additionally I have a Nexus 7 running the exact same setup except for ClockworkRecovery instead of TWRP and it accepted the Netflix update without issue.
On the N5 I tried using TWRP's "Fix Permission" option (hell if I know what it does but why not), but didn't work.
Only other thing I can think of that is relevant is I had to re-flash everything about 2 weeks ago because my initial install had apparently set my "storage space" as 16GB when I have a 32GB device. But that issue is fixed and I've tried freeing up extra space just in case.
Edit: After more research I found one person who mentioned BusyBox along with the insufficient storage issue. I tried going back one release to 1.21.1 and restarting the phone but was unsuccessful. Was on 1.22.0, 1.22.1 just released so I'll see if that helps.

This is now happening to me as well. Two apps only, Twitter and Amazon apps.
I've tried deleting old files, reinstalling, one touch cleaning, you name it, I've tried.
Is the only way to fix this is to reflash ROM?
I'm running CyanogenMod, with Franco kernel on a 16gb Nexus 5.

Go data/app-lib and delete the relevant folder for the app your having problems with
Sent from my Nexus 5 using Tapatalk

[Q] Album crash

If I launch Google Photos everything looks good. If I then switch (via the sidebar) to "Albums" it crashes each and every time.
This is on 5.0 and 5.1_r3
Any ideas how to figure this one out?

Most FCs/hangs on Google+ can be resolved by reseting the app's data. Look in Settings>Apps>Google+
Press on force close, then delete data und restart your device.

MIKM.xda said:
Most FCs/hangs on Google+ can be resolved by reseting the app's data. Look in Settings>Apps>Google+
Press on force close, then delete data und restart your device.
Click to expand...
Click to collapse
No luck. This crash has survived upgrades from 5->5.1r3->5.1r5... but I tried it anyway and still crashing.

Hmm, any custom kernel running?

MIKM.xda said:
Hmm, any custom kernel running?
Click to expand...
Click to collapse
At the moment I'm totally stock, not even rooted, on 5.1_r5. But in the past I had the same crash on Franco and Elemental.

Same issue for me. Clearing data and cache of google + will not solve it
Sent from my Nexus 5 using XDA Free mobile app

crash
I have the same problem just updated to 5.1.1 (LMY48B) and its still crashing. did a factory reset flash factory image nothing helped

Tried a clean flash to a Carbon rim nightly, and now on the new factory image for 5.1.1... Seeing it in both of those too.
These are the times I'm jealous of the genius bar... At least someone would hear my complaint instead of just hitting submit bug. :/
Sent from my Nexus 5 using XDA Free mobile app

franek83 said:
I have the same problem just updated to 5.1.1 (LMY48B) and its still crashing. did a factory reset flash factory image nothing helped
Click to expand...
Click to collapse
Had similar with gmail. There was an update in play store for it. Updated and end of problem. If you've not got update in your play store maybe check out apk mirror and see if your on the latest release. Update if needed. See if it fixes your problem.
Good luck.

gaosphappy said:
Had similar with gmail. There was an update in play store for it. Updated and end of problem. If you've not got update in your play store maybe check out apk mirror and see if your on the latest release. Update if needed. See if it fixes your problem.
Good luck.
Click to expand...
Click to collapse
Been through several of the latest versions of G+ and Photos and still seeing this. My best guess is this is related to something specific in the album setup for people who are experiencing it. Either an odd character, or something else. Since google has gone through so many different versions of albums it wouldn't surprise me.
In fact, if I had to guess, I would suggest every one who is seeing this crash has at some point in the past used picasaweb albums, would I be correct?

fix
i think i fix the problem by removing old hangouts folders that i did not use anymore hope it help you guys to

franek83 said:
i think i fix the problem by removing old hangouts folders that i did not use anymore hope it help you guys to
Click to expand...
Click to collapse
Was it just called "hangouts"? I don't have one like that. I've tried deleting all the old system like folders I can find that it will let me, but still no luck :/

rbrenart said:
Was it just called "hangouts"? I don't have one like that. I've tried deleting all the old system like folders I can find that it will let me, but still no luck :/
Click to expand...
Click to collapse
go to google+ then photos albums and there i had hangouts... person name that i had the hangout with

Well, guess this isn't relevant any longer. No crash on new photos.
Sent from my Nexus 5 using XDA Free mobile app