StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9474051
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2012-02-27T23:29:05.603
FavoriteCount
0
LastActivityDate
2012-02-27T23:46:55.993
LastEditDate
2012-02-27T23:46:55.993
LastEditorUserId
1101070
OwnerUserId
1101070
ParentId
9471448
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
From the <a href="http://developer.android.com/guide/topics/manifest/uses-feature-element.html#market-feature-filtering" rel="nofollow">Android Market and Feature-Based Filtering</a> documentation: <blockquote> Android Market filters the applications that are visible to users, so that users can see and download only those applications that are compatible with their devices. One of the ways Market filters applications is by feature compatibility. To determine an application's feature compatibility with a given user's device, the Android Market service compares: <ul> <li>Features required by the application — an application declares features in <code><uses-feature></code> elements in its manifest with...</li> <li>Features available on the device, in hardware or software — a device reports the features it supports as read-only system properties.</li> </ul> </blockquote> What this means is that the reason your app isn't compatible with certain devices (as per Android Market) is because you have explicitly stated features that aren't available on that device. For example, by using <code>android.hardware.telephony</code>, you are effectively excluding most tablets currently available as they're not traditional phones. As such, Android Market will state that your app is not compatible with these devices. The same logic applies to <code>android.hardware.microphone</code>, <code>android.hardware.camera</code>, etc. Edit: @ManfredMoser correctly pointed out that you set all those boolean elements to false and since you haven't posted your entire <code>AndroidManifest.xml</code>, have a look through the <a href="http://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions" rel="nofollow">implicit feature requirements</a> and see if any of the permissions you requested correspond to hardware that isn't available on your test device(s).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAndroid Market: "This item is not compatible with your device."
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMarvin Pinto
UserOwnerUserId
1. USMarvin Pinto
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.