It looks like the overview docs are not yet mentioning this, but you can use
android:required to say you don't need the feature:

http://developer.android.com/reference/android/R.styleable.html#AndroidManifestUsesFeature

On Thu, Dec 17, 2009 at 9:12 AM, Mark Wyszomierski <[email protected]> wrote:

> >> So if my app does (sometimes) use autofocus but works OK without
> autofocus I should use
>
> What if the app uses the camera if one is available, but also works
> fine on a device *without* a camera? By adding the following to the
> manifest:
>
>  <uses-permission android:name="android.permission.CAMERA" />
>  <uses-feature android:name="android.hardware.camera" />
>
> are we going to block all devices that don't have a camera?
>
> Thanks
>
>
> On Dec 3, 7:58 pm, steve <[email protected]> wrote:
> > While we are at it , any idea why the exif interface is not
> > availableon the tattoo ?
> >
> > On Dec 2, 12:08 am, "[email protected]"
> >
> >
> >
> > <[email protected]> wrote:
> > > After I rebuilt my app a few times w/o change the AndroidManifest.xml,
> > > my user told me now he can see it on the Android market. This seems a
> > > bit strange, but I am happier now.
> >
> > > SoftwareForMe.com wrote:
> >
> > > "I guess Google expects others to fill the void and build business
> > > around the services we all need. For
> > > example, online market listings: there are now many."
> >
> > > How can anyone build such a business when the market data is not
> > > available (without hacking, etc)? I have used many of the online
> > > market listings. None of them allow me to contact the user. Only one
> > > allows viewing multi-language comments, but that's very clumsy to use.
> >
> > > I am frustrated because Google has all the data. If it decides just to
> > > lift its little finger for a few engineer-days, the data can be
> > > exported to Developer Console. And Google has not done anything for
> > > more than a year. And that's because it thinks developers like us a
> > > shiite.
> >
> > > On Dec 1, 11:22 am, "SoftwareForMe.com SoftwareForMe.com"
> >
> > > <[email protected]> wrote:
> > > > @Nemat,
> >
> > > > Would you mind telling me if you can see PhoneMyPC in the Market on
> your
> > > > Tattoo?
> >
> > > > @tomei,
> > > > I too would like some of those services. I guess Google expects
> others to
> > > > fill the void and build business around the services we all need. For
> > > > example, online market listings: there are now many.
> >
> > > > I hope you're wrong about HTML5/Chrome; I'd like to see the idea of
> on-board
> > > > apps continue. There are many things you can do with an app that
> won't be
> > > > possible in HTML5 for many years to come.
> >
> > > > SoftwareForMe.com
> > > > Makers of PhoneMyPC
> >
> > > > On Mon, Nov 30, 2009 at 10:21 PM, [email protected] <
> >
> > > > [email protected]> wrote:
> > > > > No, it's not protected.
> >
> > > > > On Nov 30, 10:12 pm, westmeadboy <[email protected]> wrote:
> > > > > > Is your app copy-protected?
> >
> > > > > > On Dec 1, 1:48 pm, "[email protected]"
> >
> > > > > > <[email protected]> wrote:
> > > > > > > Hi SoftwareForMe.com,
> >
> > > > > > > Sorry for my ranting. I was/am really frustrated by Google's
> lack of
> > > > > > > developer support, especially related to the Market.
> >
> > > > > > > I really would like to have features like these:
> >
> > > > > > > (a) When I upload my app, it would be nice for them to give me
> a
> > > > > > > warning -- your app will not show up on these devices because
> of
> > > > > > > reason XXX.
> >
> > > > > > > (b) contact a user to address bad comments he posted about my
> app
> >
> > > > > > > (c) see comments from users, in all languages, in real time via
> the
> > > > > > > web
> >
> > > > > > > (d) see ranking, per-country statistics, etc
> >
> > > > > > > The Market has been operating for more than a year. I can't
> believe a
> > > > > > > company who claims to be a web company can't even do such basic
> stuff.
> >
> > > > > > > My only conclusion is -- Google doesn't want Android apps to be
> "too
> > > > > > > successful". They want everyone to use HTML5, web, etc, so that
> they
> > > > > > > can sell more ads. That's the direction they want to go with
> Chrome
> > > > > > > OS. So for developers like me who write a local, non-ad-based
> app, I
> > > > > > > can go screw myself.
> >
> > > > > > > On Nov 30, 9:06 pm, "SoftwareForMe.com SoftwareForMe.com"
> >
> > > > > > > <[email protected]> wrote:
> > > > > > > > Being a real lover of the Android platform, I'm a little
> frustrated
> > > > > that
> > > > > > > > things aren't perfect, that there are some devices that can't
> [yet]
> > > > > see some
> > > > > > > > apps, and that there are splinter devices (Archos) that won't
> have
> > > > > access to
> > > > > > > > the de-facto Android App market.
> >
> > > > > > > > Nonetheless, Google's market is amongst the top selling
> points for
> > > > > all
> > > > > > > > Android phones, is a key point of comparison when pitting
> Android is
> > > > > pitted
> > > > > > > > against Apple, WimMo, etc., and as such, will succeed and
> continue to
> > > > > grow,
> > > > > > > > in my opinion.
> >
> > > > > > > > I would very much like to chase phone models and make sure
> they can
> > > > > all see
> > > > > > > > our apps--we want sales as much as the next team--but I
> really
> > > > > believe this
> > > > > > > > thinking is backwards. OEMs should be the ones working to
> make sure
> > > > > their
> > > > > > > > phones have access to the widest array of apps possible.
> >
> > > > > > > > As long as we developers follow the standards, practice good
> > > > > development
> > > > > > > > practices and do the 'right thing' to make our apps run on
> all
> > > > > phones, the
> > > > > > > > continued problem of 'disenfranchised phones' will attract
> attention,
> > > > > and
> > > > > > > > it's the OEMs who will pay (HTC, being that they are so far
> the kings
> > > > > of
> > > > > > > > "can't do that").
> >
> > > > > > > > SoftwareForMe.com
> >
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > > > Groups "Android Developers" group.
> > > > > To post to this group, send email to
> [email protected]
> > > > > To unsubscribe from this group, send email to
> > > > > [email protected]<android-developers%[email protected]><android-developers%2Bunsubs
> ­[email protected]>
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/android-developers?hl=en-Hide quoted
> text -
> >
> > > - Show quoted text -
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<android-developers%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>



-- 
Dianne Hackborn
Android framework engineer
[email protected]

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to