I've had this issue on and off for quite a while and it's getting more and more frustrating.
There are many apps on the market that are, what I consider, pretty common Android apps (Adobe Flash, Shazzam, Go Locker, Out of Milk, etc) but when I go to the market page I don't even have the "download" button. Instead, I see "Not avaiable for your device"
I've searched around and had little luck in figuring this out. The only thing I can think is maybe my build.prop gets ****ed up when I change my LCD density. That's only a guess as it's all I've really done to the phone short of a kernel/rom. I've tried resetting permissions in Rom Manager, clear cache/data and uninstall/reinstal Market, and now I'm in RA Recovery resetting my permissions. I've been stuck on "Fixing permissions..." for about 30 minutes with no sign of stopping but the software buttons still have haptic feedback so I'm not sure if it's frozen or if it takes a while.
I've tried MarketEnabler but that only accounts for a location based spoof and not the actual device type. Has anyone run into this issue before?
Running CM7 most recent nightly, redstar's kernel, and a LCD density set at 200. Other than that, nothing but apps. Please help me with this as I find it very annoying to go to a third party website to download the APK manually. If I do it that way the apps install/run just fine. The market just won't let me install.
Halp!
Which version do you have?
Nicuu said:
Which version do you have?
Click to expand...
Click to collapse
Of the market? IIRC it was the most recent one.
Right now I'm stuck in recovery on "Fixing Permissions..." and it's been that way for 30+ minutes. Does it normally take this long or should I pull the battery.
I JUST cleared the cache/data and uninstalled the market. I was going to reinstall the most recent GAPPS to see if that fixed it but got hung on this permissions stuff.
Never bothered changing it, but what is the standard LCD density setting? Changing the LCD density will definitely cause certain apps not to recognize your device in the market.
Change your LCD density back to default and then try to reinstall, you should be good to go.
Rod3 said:
Never bothered changing it, but what is the standard LCD density setting? Changing the LCD density will definitely cause certain apps not to recognize your device in the market.
Change your LCD density back to default and then try to reinstall, you should be good to go.
Click to expand...
Click to collapse
It was set at 240 by default and I change it to 200 and increase screen space. I'd recommend it, I can't stand how the phone looks at 240
I reverted to my old build.prop and it didn't work. I did a full wipe and the market works. Did a wipe + density change and it still works. About to install the kernel to see if that made it happen but I doubt it.
I'm not sure what caused it but a wipe/reinstall of everything fixed it. Made a backup so hopefully I don't have to fight this thing again
I'm experiencing this too.
Normally, I would switch my LCD Density to 240 and everything would be fine... but now (yes, now that I'd like to install those cheap 10c apps), I can't!
I'll try to do a wipe & reinstall... I'm itching for those apps and my N1 can't install them..
OK, after a wipe & reinstall.. I'm back in business..
Installed the apps right a way.. I'll change the LCD Density later..
Hope I won't experience the same problem again, when the next wave of 10c apps come-in..
zybertooth said:
OK, after a wipe & reinstall.. I'm back in business..
Installed the apps right a way.. I'll change the LCD Density later..
Hope I won't experience the same problem again, when the next wave of 10c apps come-in..
Click to expand...
Click to collapse
I am still working on the same problem, will try again later.
Everything was working great and without installing anything other than market app updates, it all of a sudden quote working.
I did a restore to my working market backup but the problem persists. I'm going to try a wipe and restore to see if that works. Lets hope so...
Sent from my Nexus One using XDA App
I had the same problem
Sent from my LG-P925 using XDA App
Me too
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
Related
[SOLUTION] "Android.process.acore" FC problem? Yet another solution. (LCD Density)
Hey guys,
For the last 4 days straight I've been pulling my hair out like mad trying to figure out what on Earth was making my Contacts shortcut on my Galaxy S GT-I9000 go mental and tell me that Android.process.acore was dead and must close (on startup of Contacts.apk).
Like 95% of the freaks here, I mess with my Android ALL THE TIME. Adding new widgets, making things look better, customised to my personal taste - you know, we all do it. Now, 4 days ago, I changed a few things and started getting the Android.process.acore FC error whenever I tried to access my Contacts. After a bit of looking around google and XDA, it seemed that the one cause was from having synced your facebook contacts to your phone and having an incorrect birthday. Now, I don't remember syncing any new contacts as I've had problems in the past with the sync program (not related to this).
To rid of this problem, I read that backing up then deleting the Contacts.apk & ContactsStorage.apk cache would solve all my problems; well, it didn't. Even having an empty Contacts file would still bring up the FC error. So after a few dozen attempts, I reflashed back to a stock rom and low and behold, Contact.apk would load up. HORRAH. Thinking it was just Android being silly, I restored my NAND and go back into things. Contacts.apk still working, nice; I'll just restore my widgets and background etc.... BAM, Android.process.acore FC again, what the? Nothing would open that damn thing again.
Ok, Reflashed back to stock; this time, restored using Titanium Backup. Nice! Contacts are back and working; just setup my widgets and Background again... BAM, Android.process.acore DEAD.
Now, after trying each widget one by one to see which one was killing Android.process.acore, nothing changed... no widgets killed it... was still working....
HUH?
Ok, continue using Phone - BAM, dead!!! ARGGHH
Then I came up with an idea. I had been using LCD Density Change. Now, I've had it on a value of 200 for months now with no problems at all... what was my setting at the moment? 180.
Yes guys, CONTACTS.APK HATES a LCD Density value of 180!!!
Can anyone else replicate this problem at all? I haven't tried any other values yet to see what works/doesn't work.
I'm using the lastest LauncherPro Plus & LCD Density Changer 5.1.
Hope this helps some people
thanks for the post i also have the same problem on my captivate
Lcd den dosent work on froyo...
Sent from my GT-I9000 using XDA App
Hana. Sorry. This happened to me ages ago and its a known problem which is even in lcd densitys faq. Contacts wont work below 200. I have since replaced my phone/contacts app with youlu free from market. Atakephone is also another good replacemnt
Sent from my GT-I9000 using Tapatalk
okpc said:
Lcd den dosent work on froyo...
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
5.1 works fine on froyo
Sent from my GT-I9000 using Tapatalk
I can reproduce the problem on values 180 and 181 (haven't tried others yet). I don't have any problem though with a density value of 191 (my "default" density).
I suggest trying different values (maybe go lower, maybe go higher).
It is a well known problem that some apps FC on some specific density values. The "famous" FC is the FC-ing of the TWLauncher when you set it to a density of (I believe) 120 or lower. Please don't try this at home If you start up with that density and use TWLauncher as the default launcher all you can do is restore a nandroid or reflash the firmware. (that's why I explicitely advice in the help file of the Density Changer to first do a preview before saving the density as the system density)
@okpc Why would you say that? I also had some comments on the market saying that it doesn't work on Froyo. I never had any problem on any Samsung firmware Froyo version with it. Do you run a custom rom or kernel?
Note that different kernels can totally change the way rooting apps work on your device (and i mean totally). Or did you installed busybox? Note that all rooting methods install busybox by default except SuperOneClick... Second note: busybox installed by TitaniumBackup can't be used by other apps.
im getting this same issue but have not messed with the lcd density... i actually changed it to 225 to see if it would effect the contacts problem... but nah it didn't
i installed the contact.apk from sgs tools... but that didn't help still a FC when clicking it.
same problem on 180 density, but on 182 it working
DAMN IT. running KINGSROM HYBRID 3D and i have that problem. OVER AND OVER its acore acore acore acore FC FC FC FC. AAHH!!?!?!?!
difference between your problem and mine, mine keeps rebooting, and rebooting, and rebooting, never letting the home screen boot.
now i suggest, FCUK LCD CHANGER.
hey... i uninstalled the entire YouTube app from my phone instead of uninstalling the update. and now i cannot download the app again from the Market. there's no download button showing. does the same thing when i'm looking to re-download Shazam. i don't know what the heck is wrong with my Market all of a sudden. i even went on the web browser based version of Market to see if i could download it from there but it says "This app is incompatible with your T-Mobile HTC HTC HD2." WTF?! it was compatible before.
i found an older version of the YouTube app (v1.6.21), but i would like a newer one (or even the latest one) from a legitimate source. preferably one from a XDA board member. Market won't even try and update the YouTube app i installed. lame. can anyone point me the right way? thanks.
Just reflash a whatever rom you are using and the shop should be reinstalled
Sent from my HD2 using XDA App
Settings > Applications > Market > Uninstall Updates ..
Go to Market > "Accept" > Look for YouTube and install.
Don't know why is this happening with the new market, but I have the same problem, fixed by using the old market.
Clear in your device market cache.then change your screen density to 240 and you will be able to download these apps
Sent from my HD2
oh man. as soon as uninstall the update to the Market app, it updates itself again the moment i start the Market app.
so that avenue doesn't work. someone PM'd me the APK.
but i'm still annoyed that Market it refusing to let me redownload stuff like YouTube and Shazam. i notice it won't even let me try and download Google Books. and i've never installed it before.
Wow thats really wierd, maybe flashing a different rom will help
guys the problem with new market is that it reads screen density.If you have screen density different from 240 you will not be able to download many apps.As far i know hyperdroid rom uses 167ppi density so many apps are not compatible.ofcourse only in the "paper",because if you download and install it,it will work.
If you dont want to change your screen density to 240 permanently use from market the app lcd density
install it,clear market cache,set density to 240,reboot method "kill" and wait to hot reboot.after reboot open market and it will let you to download the app.Then go again to lcd density and put your desired density or make a normal reboot and it will be again in your desired screen density
aaaaaahhh i had no idea it was the density, i'm currently in eu, with a swiss sim, i thought it was something to do with that... -.- now that i find out it's with the density, it almost makes too much sense from what i thought. -.- i didnt uninstall the updates, but i changed my density, and had to clear cache and data. works fine now. thanks guys.
Regarding this thread:
http://forum.xda-developers.com/showthread.php?t=1196417
Thanks for pointing out and after some more tests, seems that its all about DPI.
To fix, edit build.prop and change
Code:
qemu.sf.lcd_density=161
to
Code:
qemu.sf.lcd_density=160
then reboot.
this will change lcd density from 161 to 160. CM7 uses 161 for some reason but seems 160 will get all the blocked apps back.
After rebooting, clear market data and run market again. If you've removed/frozen the market updater app, enable it to get the new market. Those blocked apps should be available then.
Note:
160 will break market at some point per Dalingrin. I'm not sure but it works fine after several reboots so far(n154 on emmc).
I thought Market didn't work at 160?
http://forum.xda-developers.com/showpost.php?p=15629179&postcount=4174
Has this changed?
jameshmiller said:
I thought Market didn't work at 160?
http://forum.xda-developers.com/showpost.php?p=15629179&postcount=4174
Has this changed?
Click to expand...
Click to collapse
Didn't know that, so thats why CM7 uses 161? Anyway, 160 seems to work fine for me(so far), I also read several ppl report 160 is good on new market. If its broken I'll back to 161, no big deal
The market will stop working with 160 in time. But if you force stop market and clear data, it will work for a while longer.
Frank
Thanks. After some more tests I can confirm that its all about lcd density. If clearing data can fix the broken market(on 160) I might still take that route--even its temporarily--instead of 161+old market.
Nice catch, hopefully this new information will lead to a permanent fix, with the lcd density at 160 the movies category now shows up for me too..
This shows that there is some really crappy coding going on over at Google...
Tried switching my lcd density to 160. It did not help at all. Facebook app still won't let me download and several apps do not show updates. Dissent seem like this is a fix.
Sent from my NookColor using Tapatalk
ruthienu said:
Tried switching my lcd density to 160. It did not help at all. Facebook app still won't let me download and several apps do not show updates. Dissent seem like this is a fix.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
did you clear market data?
Nice! Worked for me. Edited the file in root explorer, rebooted. Go to applications in setting to clear cache, and then clear data for the Market application.
after the market stops working do you just redo it or switch it back to get market again?
Worked for me. Found 4 items that needed updating.
Thanks
I can confirm that it's NOT all about DPI, and likely not anything to do with DPI. I tried this, rebooted, cleared market app data, got all my apps back. Then, I switched back to 161, rebooted, and STILL had all my apps. this means that 161 also shows the apps after clearing data.
Then I rebooted again (still at 161), and what-hey-presto, I've STILLLLLL got all my apps!
Screw the DPI. Just clear market app data.
I tried clearing market data without changing the DPI and got nothing back. I had to change the DPI to 160 AND clear market data. After doing both of those things. I had 14 apps that needed to updated. . . who knew?
Can this method be done without restarting? Say, an app like LCD Density to temporarily change the DPI?
PoisonWolf said:
Can this method be done without restarting? Say, an app like LCD Density to temporarily change the DPI?
Click to expand...
Click to collapse
LCD Density for root works, choose "kill all" as reboot method. You can try that but it just looks like a reboot for me...
skwalas said:
I can confirm that it's NOT all about DPI, and likely not anything to do with DPI. I tried this, rebooted, cleared market app data, got all my apps back. Then, I switched back to 161, rebooted, and STILL had all my apps. this means that 161 also shows the apps after clearing data.
Then I rebooted again (still at 161), and what-hey-presto, I've STILLLLLL got all my apps!
Screw the DPI. Just clear market app data.
Click to expand...
Click to collapse
Your data was set/cached at 160 and when you back to 161, market still uses old data with access to all the apps. So this does work but market might refresh the data and broken again.
You may clear data under 161 and check the result. Vice versa, if you were on 161 and just switched to 160, you also need to clear data or the market will still use old data from 161 dpi.
arda99 said:
Your data was set/cached at 160 and when you back to 161, market still uses old data with access to all the apps. So this does work but market might refresh the data and broken again.
You may clear data under 161 and check the result. Vice versa, if you were on 161 and just switched to 160, you also need to clear data or the market will still use old data from 161 dpi.
Click to expand...
Click to collapse
This appears to be correct. After changing my density to 160 in build.prop and rebooting, Market was still limited. I force closed and cleared data, then ran Market again, and had full access. I changed my density back to 187 (what I like) and rebooted, and full access persisted, but after reading the above post, I force closed and cleared Market again, and it's limited again. I just repeated the process, changing density back to 160, and full market's back.
Nice work, arda99.
Taosaur said:
Nice work, arda99.
Click to expand...
Click to collapse
Ditto. Its making sense now, and I'm thrilled to have my paid apps accessible for updates again.
Next question is: how to make this fix persistent?
skwalas said:
Ditto. Its making sense now, and I'm thrilled to have my paid apps accessible for updates again.
Next question is: how to make this fix persistent?
Click to expand...
Click to collapse
Sorry, I'm confused. People are reporting differing results. What would need to be made persistant? 160? That's easily accomplished. But what else does changing this break?
fattire said:
Sorry, I'm confused. People are reporting differing results. What would need to be made persistant? 160? That's easily accomplished. But what else does changing this break?
Click to expand...
Click to collapse
Actually, I think results of late are pretty consistent. What I meant when making the fix persistent is how to get the "compatibility" of 160 dpi in the market data without having to actually have 160 in the build.prop (which supposedly still breaks the market eventually, per Dalingrin).
At the moment, it appears that building the market app data at 160 dpi and then reverting build.prop back to 161 works. The question is how long will it continue to work? Will any market update clear the market data? Will it just eventually pick up that it is no longer at 160? Could someone once and for all figure out WHY 160 doesn't work over the long term so we could keep build.prop at 160 permanently?
Well, this is getting quite irritating.
Half of the apps i use majorly show up on play store as 'not compatible with your device'
i know it is cos am using them.
tried 'play store market fixer', tried deleting cache/data from play store & Google framework services.. still no go..
only option is to restore from titanium backup which doesn't always serve the purpose
does anyone have any idea on fixing this?
letmedanz said:
Well, this is getting quite irritating.
Half of the apps i use majorly show up on play store as 'not compatible with your device'
i know it is cos am using them.
tried 'play store market fixer', tried deleting cache/data from play store & Google framework services.. still no go..
only option is to restore from titanium backup which doesn't always serve the purpose
does anyone have any idea on fixing this?
Click to expand...
Click to collapse
Have you changed your screen density from stock?
Sent from my Incredible S using xda premium
hmm yea!
that's the second time someone's asked me that..
i always do change screen density to 215-200dpi...
is that related??
Yes. It seems to cause issues with the play store.
acme anvil said:
Yes. It seems to cause issues with the play store.
Click to expand...
Click to collapse
Thanks...
i reverted to 240 dpi but it still doesn't show up..
i think something gets screwed up if we change the lcd density at first install.
i flashed fresh and all apps were visible..
but after i changed to 220 and they disappeared..
now reverted back to 240, still they don't appear...
letmedanz said:
Thanks...
i reverted to 240 dpi but it still doesn't show up..
i think something gets screwed up if we change the lcd density at first install.
i flashed fresh and all apps were visible..
but after i changed to 220 and they disappeared..
now reverted back to 240, still they don't appear...
Click to expand...
Click to collapse
Dunno if this is why, but usually when you change LCD density you should be clearing the play store data
Perhaps try that
Sent from my Nexus 7
markj338 said:
Dunno if this is why, but usually when you change LCD density you should be clearing the play store data
Perhaps try that
Sent from my Nexus 7
Click to expand...
Click to collapse
i did clear the data.. well not immediately after changing the lcd density but in due course of time..
didn't seem to help
letmedanz said:
Well, this is getting quite irritating.
Half of the apps i use majorly show up on play store as 'not compatible with your device'
i know it is cos am using them.
tried 'play store market fixer', tried deleting cache/data from play store & Google framework services.. still no go..
only option is to restore from titanium backup which doesn't always serve the purpose
does anyone have any idea on fixing this?
Click to expand...
Click to collapse
Could be the fact that these apps haven't updated their profile that they can run on GB?
tpbklake said:
Could be the fact that these apps haven't updated their profile that they can run on GB?
Click to expand...
Click to collapse
Am guessing you mean JB there
well, am sure they are.. cos i've restored them using titanium backup and they work fine. Just can't find them in the market..
funny part is i can't even find titanium or 4ext recovery, astro & other simple apps...
am quite certain now that it's cos of the lcd density as i re-flashed and without changing the density the apps appear...
just to check i changed the density to 220 and bang! they were off the market saying they are incompatible...
i dunno why that happens, but am very sure that it is the reason for this issue.
anyhow after all this i clean wiped, re-flashed, saw all my apps in the market & felt happy and left it at that
didn't go to fiddle with the lcd density no more..
but i do hope there is some kinda fix for this
Try to change device name in build.prop with the ones had 200-215 LCD density. Idk which one has it but mb it will work
Best wishes,
Sandy Semenov
Hey everyone, i have this problem with the Google Play store which is bugging me.
I've recently reinstalled Temasek 135.3 and found that apps i had before are now giving me a "unsupported device" error.
Anyone have any idea how to fix this?
this is usually the case when you change your display density.
try to clean the market settings (from apps or using titanium backup)
if that doesn't work, edit your build.prop so that the device name is something more generic/supported like galaxy s. for this method i suggest you google the exact steps.
good luck
V.Dragos said:
this is usually the case when you change your display density.
try to clean the market settings (from apps or using titanium backup)
if that doesn't work, edit your build.prop so that the device name is something more generic/supported like galaxy s. for this method i suggest you google the exact steps.
good luck
Click to expand...
Click to collapse
Very true, i did change the LCD density from 240 to 210. I tried setting it back to it's default and rebooted... that didn't work.
I even tried clearing the cache and data to the Play Store and rebooted....still no avail....
...but thanks for the heads up, at least i now know where to start looking.
Actually, i think i may have found a thread to help me out, which refers to an app called LCD Density Modder.
I'll let you know when i get a chance to try it....
...problem SOLVED!
and feeling kinna silly again.... thanks!