title: After specifying android.hardware.faketouch the app still requires android.hardware.touchscreen?
body: <p>I've been working on an app that originally had no touchscreen requirements specified in it's manifest file, so according to the documentation <code>android.hardware.touchscreen</code> is assumed. Because the app doesn't require advanced gestures, a device with a faketouch screen (<code>android.hardware.faketouch</code>) should also be able to run the app, so I added that requirement to the manifest file for an update.</p>
  
  <p>However, the Android market still lists <code>android.hardware.touchscreen</code> as a requirement (as well as <code>android.hardware.faketouch</code>), and I still can't find the updated app in the market on a faketouch device (HTC Wildfire).</p>
  
  <p>These are the permissions, requirements and libraries I specified:</p>
  
  <pre><code>&lt;uses-library android:name="com.google.android.maps" /&gt;
  &lt;uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"&gt;&lt;/uses-permission&gt;
  &lt;uses-permission android:name="android.permission.INTERNET"&gt;&lt;/uses-permission&gt;
  &lt;uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /&gt;
  &lt;uses-permission android:name="android.permission.CAMERA" /&gt;
  &lt;uses-feature android:name="android.hardware.camera" /&gt;
  &lt;uses-feature android:name="android.hardware.camera.autofocus" /&gt;
  &lt;uses-feature android:name="android.hardware.faketouch" /&gt;
  &lt;uses-sdk android:minSdkVersion="4"&gt;&lt;/uses-sdk&gt;
  </code></pre>
  
  <p>Is this a problem (perhaps the market remembers old requirements, or perhaps the Google Maps library inserts a touchscreen requirement) or is it normal to see both listed when specifying faketouch?</p>