Market filters:
When a user searches or browses in Android Market, the results are filtered, and some applications might not be visible. For example, if an application requires a trackball (as specified in the manifest file), then Android Market will not show the app on any device that does not have a trackball.
The manifest file and the device's hardware and features are only part of how applications are filtered — filtering also depends on the country and carrier, the presence or absence of a SIM card, and other factors.
Changes to the Android Market filters are independent of changes to the Android platform itself. This document will be updated periodically to reflect any changes that occur.
Click to expand...
Click to collapse
Does anyone have any idea what the market filters are checking against?
That's not really a good reason to do anything, let alone not using 2.2
dik23 said:
That's not really a good reason to do anything, let alone not using 2.2
Click to expand...
Click to collapse
Not being able to get apps? Did you read the link? Doubtful. Uh sure. Have fun with vanilla 2.2 and 0.0 apps.
I'm sorry, did you read your own link? If you had scrolled down, it shows several examples of what can be filtered. The filters are implemented by the application developer themselves, and if they don't, they still show up in the market.
Besides, filtering by the application has been in Android since 2.0. Any application that deems a device incapable of running it (for example, a lack of a light sensor) can stop itself from running.
some kind of filter (the ones I've heard of so far are incompatible screen resolution, unverified builds, and protected apps) is already being applied to 2.1 in the AOSP build. I couldnt see Yelp, the Android Community and TMZ apps for whatever reason
cashless said:
Not being able to get apps? Did you read the link? Doubtful. Uh sure. Have fun with vanilla 2.2 and 0.0 apps.
Click to expand...
Click to collapse
Oh yeah, how suspicious. French people couldn't possibly prefer apps in French and people with that new Dell pad thing probably still want SMS and contact apps.
Yeah
so you are saying not upgrade to 2.2 because marketplace will filter apps for our phone, but stick with 2.1 because it doesn't?
well genius, why don't you go and install http://www.appbrain.com/app/com.yelp.android on your phone and let us know how that 'no filtering' works out for you.
When I was running my Vougue we ran into this problem as well, its not a big deal at all. from what I remember it was checking about the build.prob and screen size that is setup in your startup. what I used to do was set my phone to my the specs for the G1, then install the apps after adjusting the density to fit everything on screen and then reboot using factory startup. it worked pretty well for most of the apps since many only blocked off whatever border the developer had.
heres the problem though but with the pace we are going it wont come up for a while, once we decide we have a rom stable enough to flash we lost the abilty to change the settings since WM is copletely gone and no haret was used. I switched over to the Touch Pro and we had the exact same problem which was solved in the EXACT way but we were not flashed still(TP2 still has a LOOOONG way to go sad to say), kept the touch pro 2 for only a few weeks before they replaced my Sprint Line TP with a Touch pro 2 due to all the TP1 problems and i'm still saddened by the slow progress. I am a developer myself and even an avid budsmoker and was still able to help out. now Refer has done a great job but from my understanding he is just doing most changes to the Android Filesystem, theirs a couple other guys working on the kernels which would be were all the hardware problems are going to be fixed from. no matter what build we use something in the kernel is either not right, or we dont have the driver in place for Android itself and since we have few Hardware level developers working on these things it seems to be low progress.
I'm running a stock rooted T-Mobile G2 Gingerbread ROM (http://forum.xda-developers.com/showthread.php?t=1314541) and I just noticed that I no longer have field test available to me (fieldtest.apk / fieldtest.odex). I tried checking some other stock G2 Gingerbread ROMs and none of them had it either. I checked a Froyo ROM and that did have it. So, this brings me to two questions essentially:
1. Does anyone know why "they" seemed to have gotten rid of the field test app?
2. Does anyone know how I could get a working version of field test on gingerbread?
What I've tried so far is taking the fieldtest.apk and trying to install it...the installation failed. I then realized that the app doesn't get "installed" like other apps and then tried placing it and the .odex file in /system/app using Root Explorer, but it was not able to launch.
If anyone has any ideas or suggestions I'd be interesting in hearing them. The reason why I would like the field test back is because I used to used to determine which ARFCN I was on when on 2G networks. I could not find an app in the market that would do this...I've found an arfcn calculator, but that doesn't tell me what arfcn I'm on. Network Info II doesn't tell me this either, although it is a nice app with other good info. Thanks.
This thread will help you with getting missing apps from the Market. ICS handles these things differently and changing the build.prop won't necessarily give you everything.
http://forum.xda-developers.com/showthread.php?t=1466940
Okay so I have the Xperia Arc S with 4.0.4 and I would like to change the secondary backround which is just plain horrible. By secondary I mean the one that shows when you are on settings, messages, phone, email etc. Is this possible without rooting the phone? Because I've tried that and getting damn tired of failing on it, because I cant and dont know how to install adb drivers etc and I wouldnt like to risk my warranty.
I also have additional problem with the home screens. By default there are 5 of the homescreens and you can just swipe across them, have different widgets on every screen etc. The problem is that I dont like them, I only use 1 screen and would like to delete others. Is that possible? It was on my previous phone samsung xcover but cant seem to find option for that.
I am not good with these things so any help would be greatly appreciated, thank you.
Hey,
Got a nexus 7 2013. I bought Modern Combat 3 for it a while ago, and never got it to start. I had the same problem for my Galaxy Nexus, but I fixed it by installing a previous version of the app through an apk. Whilst it worked flawlessly for my Gnex, when installed on my N7 it tells me that my device is incompatible. I know this is not true as I downloaded the app from the playstore and installed it no problems; running it was the issue.
So I need to ask if changing the device name in the build.prop, letting the game install then putting it back has a possible chance of causing a brick. Either way, please let me know asap.
If there is a different way to get the game working, or to make the app think I have a compatible device, please also let me know.
I'm rooted, running stock 4.4.2 with Xposed.
Thanks,
-Riku
For the most part anything under ro.build and ro.product is safe to edit, they're generally for display purposes or for market to do app compatibility checks like what you might be having issues with.
The exceptions are
ro.product.cpu.* (I simply have not tested changing these)
ro.board.platform (this will definitely break booting if you change it)
Whether or not this actually helps you though, I dont know.
TheManii said:
For the most part anything under ro.build and ro.product is safe to edit, they're generally for display purposes or for market to do app compatibility checks like what you might be having issues with.
The exceptions are
ro.product.cpu.* (I simply have not tested changing these)
ro.board.platform (this will definitely break booting if you change it)
Whether or not this actually helps you though, I dont know.
Click to expand...
Click to collapse
This is useful and I will apply that to future questions, but i just want a solid answer. If you have a N7, would you main testing it and seeing if it still boots? If you don't, is there a way you could confirm an answer for me?
Your help is greatly appreciated.
-Roku