So I have a MyTouch 4G (not slide) running Cyanogenmod 7.2 (latest release canidate). I've got LCD density at 220 and I've installed the DARKSIDE ICS Kernel using Kernel Manager. I've been trying to customize my phone as much as possible (because I think it's kinda fun), but most of the time when I try to download something from the market (example: GoLauncher) I get the "not compatible with your device" message and no option to download the app. I've tried switching lcd density back to 240, clearing market data, and then even uninstalling maket updates, but none of it worked. So I even decided to tweak my build.prop to make my phone appear as the Nexus S (see below), but even that didn't work.
So is there something I'm doing wrong, or is there something different in the updated market (now Google Play Store) that renders these methods useless?
Here's what I did with my build.prop...
ro.product.model=Nexus S
ro.product.manufacturer=samsung
ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys
ro.build.description=soju-user 2.3.4 GRJ22 121341 release-keys
Cm7.1 build fingerprint is generally pretty compatible
The play store does not like modified LCD density.
Sent from my HTC Glacier using Tapatalk
Related
I kept having this problem with android market. Is there a way to fix this with the market on the nook color?
More info please...ROM, version...so on.
Sent from my NookColor using Tapatalk
Android version is 2.2.1, kernel is 2.6.29-oomap1, build is FRG83
Maybe it isn't? hehe.
Install CM7
kruuth said:
I kept having this problem with android market. Is there a way to fix this with the market on the nook color?
Click to expand...
Click to collapse
Sooo, any specific app here, or are you referring to the market apk itself?
Please search before posting
There is a search function guys. This is my fourth time posting this as a reply to this very issue for someone.
This will fix it 90% of the time:
http://forum.xda-developers.com/showpost.php?p=11626645&postcount=425
I had this problem when I published an app, so I monkied around with it until I figured it out. When I disabled copy protection on my app, suddenly it was compatible with my device (Sony Xperia Play) and I was able to install through the android market.
Copy protection is now deprecated and is being replaced with a new licensing feature, so assuming licensing doesn't have the same bug this problem will in theory be phased out.
So if you are a developer and some people can't see your app, disable copy protection and use licensing instead. I also suggest using the Android SDK built in ProGuard feature to obfuscate (scramble) your code to make it harder to reverse engineer.
Hmmmm. it seems that my problems with Android Market was due to the DPI change which I made - the display density.
I changed my HTC Desire back from 200 dpi to the default value if 200 dpi, after that I cleared Android Market data and cache and restarted the phone.
After that on Android Market the problem with the "This item is not compatible with your device" error on some applications was fixed.
P.S. For changeing the display density you can use one of this apps from the Market: LCD Density or LCD Density Changer
Download the nook tweaks and nook odds and ends apps from the market.then go to display settings in one of the apps,I forget which,and change LCD density to160 reboot try then
Sent from my NookColor using xda premium
I get this on many apps including facebook. They all say they need to be updated but when I try to update they complain. I'll try to upgrade to the latest nightly when I find some free time.
s52m3 said:
I get this on many apps including facebook. They all say they need to be updated but when I try to update they complain. I'll try to upgrade to the latest nightly when I find some free time.
Click to expand...
Click to collapse
You may want to avoid the latest as it has a few issues. 7.1 stable would be a better choice.
ErroneousBosch said:
There is a search function guys. This is my fourth time posting this as a reply to this very issue for someone.
This will fix it 90% of the time:
http://forum.xda-developers.com/showpost.php?p=11626645&postcount=425
Click to expand...
Click to collapse
Didn't work.
Lewis Moon said:
Didn't work.
Click to expand...
Click to collapse
Ditto. It didn't work for me either.
h t t p : / / w w w . groovypost.com/howto/nook-color-device-not-compatible-this-item-android-market-error/
(Sorry, my n00bness won't allow me to post a hotlink.)
This fix worked for me after trying all of the previous in this thread.
Only thing missing in the link is granting SuperUser permission to FileExpert. If it doesn't have SU "mount" won't show up in the list.
.
emerson.biguns said:
h t t p : / / w w w . groovypost.com/howto/nook-color-device-not-compatible-this-item-android-market-error/
(Sorry, my n00bness won't allow me to post a hotlink.)
This fix worked for me after trying all of the previous in this thread.
Only thing missing in the link is granting SuperUser permission to FileExpert. If it doesn't have SU "mount" won't show up in the list.
.
Click to expand...
Click to collapse
I'm using HTC HD2 with haldricc's Rom "SENSATION XL V 3.0 stock ALL IN ONE (marc v0.1.8 ker)".
I have the same problem, I cannot install some applications. Once I find the apk file, I installed it and worked but not thru market.
THe solution does not fit in my problem since my lcd density is already 240. I guess every application looks for some parameters.
Any solution for me ?
thanks
tikado said:
I'm using HTC HD2 with haldricc's Rom "SENSATION XL V 3.0 stock ALL IN ONE (marc v0.1.8 ker)".
I have the same problem, I cannot install some applications. Once I find the apk file, I installed it and worked but not thru market.
THe solution does not fit in my problem since my lcd density is already 240. I guess every application looks for some parameters.
Any solution for me ?
thanks
Click to expand...
Click to collapse
Last time we set to 160 and the problem magically went away.
have you tried using marketenabler?
clear your market cache,
open marketenabler -> settins->long press [us] T-mobile -> fake this provider now
open the market
try
Zorkman said:
have you tried using [LINK REMOVED]
clear your market cache,
open marketenabler -> settins->long press [us] T-mobile -> fake this provider now
open the market
try
Click to expand...
Click to collapse
Link is no longer valid
Any update on this ? I'm running stock 1.4.3 with ManuelNooter 5 and I'm getting that dreaded compatibility message for "Subsonic Music Streamer"
I have the newest version of ICS installed (January 19th), but can't seem to get all the market apps to show. I've tried altering my build.prop a few ways. Has anyone been able to get it to work on ICS?
I have the same issue with the Market, I can't find Twitter and Facebook for example.
I installed those apps using the .apk but the Market still doesn't recognize it.
I have that rom too.
the only problem im having with the rom is the market wont download new apps or update the current ones
it doesnt even try
try to turn off Wi-Fi, then turn on
that worked for me
wcastillosalva said:
try to turn off Wi-Fi, then turn on
that worked for me
Click to expand...
Click to collapse
How in the world will that fix it lol
tjrocks91 said:
How in the world will that fix it lol
Click to expand...
Click to collapse
i think he was trying to reply to something else
Market shows "error 403" while downloading
Hi Everyone,
I recently rooted my desire z and am playing with customs roms now. I observed that Play Store doesn't let me download anything when I'm using a ICS rom (I checked it with VC rc3, QS v1.2, AM v1.1.2, and EliteMod 120728). It shows "error 403". Surprisingly, Play Store behaves normal when I'm using any Non-ICS rom (I checked with CM7, BeatMod BlissSense Hybrid, V Glite, ILWT, and EliteMod 120316). This makes me believe that this is perhaps an ICS-ROMs specific issue! A google search showed that this error is troubling a lot other people also. I tried the usual tricks suggested like 'clearing Market data' etc. but nothing seems to work. I wonder if anyone has successfully solved this issue of failure in app download from market.
Please reply as it is the only issue that is keeping me away from ICS roms (I tried EliteMod 120728 today, and my God, It's awesome!!!).
Thanks in anticipation,
Durgesh
Phone: Desire Z; Vision Pvt Eng S-Off; HBOOT: 0.84.2000 (PC1011000);
Radio: 26.03.02.26_M; ROM: EliteMod-120316-CM7-vision
Possible fix for Play Store/Market download error
Hi,
I was facing peculiar 'error 403' while downloading anything from Play Store. Interestingly enough, this error was cropping up only with ICS ROMs and not with gingerbread or sense based ROMs. I came across a suggestion at XDA (don't remember the members' name but would search him and thank him) that if we remove Server and Proxy settings from the APNs, it would solve the problem. Another suggestion was to open browser and login to 'checkout.google.com' and then leave the page open and go to Play Store on device. I tried both simultaneously and it worked. In order to confirm whether the 'Server and Proxy' thing is working, I put these setting again in APN and the Play Store started giving same 'error 403'. Removed these settings and everything is fine now. Hope this helps to others again.
And thanks for the member who originally suggested these options.
Regards,
dcpathak
Phone: Desire Z; Vision Pvt Eng S-Off; HBOOT: 0.84.2000 (PC1011000);
Radio: 26.03.02.26_M; ROM: EliteMod-120728 (elitemodded-aokp_vision_milestone-6_20120723)
has anyone downloaded the new hulu plus tablet app? it said that iconia is supported but i didn't see it on google play. has anyone else got it?
Do you have ICS installed??
I think you have to have HC installed since I can't see it in the market either, but if I go to the market on my pc it shows it available.
All of the custom ICS roms for the A500 have unsupported product descriptions and fingerprints. Don't forget that there isn't an official A500 ICS rom, so there is no official support even if you are using the Acer description/fingerprint. I just changed my description/fingerprint to that of the new ICS build for the Asus eeepad Transformer ( TF101 ), and I can buy and see apps that I couldn't before ( including Hulu Plus ).
Ummm.
I changed two lines in my build.prop
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.2.1.17-20120312 release-keys
ro.build.fingerprint=asus/US_epad/TF101:4.0.3/IML74K/US_epad-9.2.1.17-20120312:user/release-keys
Works for me...
( Note: I changed the build.prop after backing it up, stopped the Google Play Store and cleared its cache, stopped the Google Services Framework and cleared its data, and then rebooted. )
sounds easy enough
RageAgain said:
All of the custom ICS roms for the A500 have unsupported product descriptions and fingerprints. Don't forget that there isn't an official A500 ICS rom, so there is no official support even if you are using the Acer description/fingerprint. I just changed my description/fingerprint to that of the new ICS build for the Asus eeepad Transformer ( TF101 ), and I can buy and see apps that I couldn't before ( including Hulu Plus ).
Ummm.
I changed two lines in my build.prop
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.2.1.17-20120312 release-keys
ro.build.fingerprint=asus/US_epad/TF101:4.0.3/IML74K/US_epad-9.2.1.17-20120312:user/release-keys
Works for me...
( Note: I changed the build.prop after backing it up, stopped the Google Play Store and cleared its cache, stopped the Google Services Framework and cleared its data, and then rebooted. )
Click to expand...
Click to collapse
Didn't work for me. Still can't find the app on the store after making the changes.
Sent from my A500 using Tapatalk
bahurd said:
Didn't work for me. Still can't find the app on the store after making the changes.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Did you also do what the note said.
cruise350 said:
Did you also do what the note said.
Click to expand...
Click to collapse
Assuming you mean "Note: I changed the build.prop after backing it up, stopped the Google Play Store and cleared its cache, stopped the Google Services Framework and cleared its data, and then rebooted."
Yes I did, several times in fact. No luck for me.
I guess I'll just cancell my Hulu+ account instead. Saves money.
Or you could just use this
http://www.mediafire.com/?trjo8teyc0sd325
Works for me flawlessly
Sent from my A500 using xda premium
Hello, I have JB NexusHD2 rom and i can't update to latest maps app relased yesterday. Now i have unsupported phone. How i can bypass that?
EDIT: OK, i got it. I've changed build.prop - ro.product name & ro.product.brand from passion to pyramid (from Google Nexus One to HTC Sensation)
EDIT2: Now wibration and notification light doesn't work. And phone is unresponsible...
.michal said:
Hello, I have JB NexusHD2 rom and i can't update to latest maps app relased yesterday. Now i have unsupported phone. How i can bypass that?
Click to expand...
Click to collapse
What is your screen resolution? Play store doesn't like anything but 240 or 160. This has nothing to do with build.prop
---
I’m as confused as a baby in a topless bar...
I have patched Google Play app. Answer is simply - i havn't change all build.prop positions. In NexusHD rom there are three options setting device type. It's ok for now.
Anyway - Google dropped support for it's first good smartphone?
After installing cm 10-20130414 nightly I get the message device not compatible when trying to download some apps like hulu plus. Any ideas? Thanks.
Nightlies are experimental versions I assume that you are aware of it? Try to install stable version and tweak it some nighltly features you may find them on google.
Sent from my GT-I9100G using xda premium
fuusob said:
After installing cm 10-20130414 nightly I get the message device not compatible when trying to download some apps like hulu plus. Any ideas? Thanks.
Click to expand...
Click to collapse
There are many device properties that Play Store checks to see if an app is considered compatible. Screen resolution and density, permissions like telephony, location services, gps, and not the least of which is the device name in build.prop. Sometimes changing those things makes Play Store say they are now compatible.
But just because Play Store says it is not compatible does not mean it will not run on your device. It just means Play Store will not let you install it. The solution is to get the app somewhere else, like the Amazon Store, 1mobile.com store or from another device. I have found that the majority of apps that Play Store says is not compatible actually run well on the Nook Color.
Sent from my Nook HD+ running CM10 on Hybrid SD
try download from other market, or just download the apk.
or maybe the app is just not compatible with jellybean (cm10)