Google currently require an in-built camera to pass the compatibility
tests, so devices without cameras are unlikely to get much attention
from them (see 8.9 in
http://source.android.com/compatibility/android-2.1-cdd.pdf)
Al.
On Jul 7, 1:22 pm, Daman wrote:
> Thanks for confirming the reliabili
> 1. Are there plans to support pluggable USB webcams (e.g. on
> netbooks)? In such a case, would the same Android APIs work for them
> too?
I don't expect an answer from Google on this (because they never tell
in advance what they will come up with), but just want to say that I
am very interested
Thanks for confirming the reliability of these APIs.
I have few related questions -
1. Are there plans to support pluggable USB webcams (e.g. on
netbooks)? In such a case, would the same Android APIs work for them
too?
2. Would hasSystemFeature(PackageManager.FEATURE_CAMERA) return true
if a USB ca
You need to do this on a real device.
On Wed, Jun 30, 2010 at 3:45 AM, Daman wrote:
> I did try that, but this doesn't work.
> I created an emulator image with no camera support. But
> PackageManager.hasSystemFeature(PackageManager.FEATURE_CAMERA) still
> returns true.
>
>
> On Jun 30, 5:12 am,
I did try that, but this doesn't work.
I created an emulator image with no camera support. But
PackageManager.hasSystemFeature(PackageManager.FEATURE_CAMERA) still
returns true.
On Jun 30, 5:12 am, Dianne Hackborn wrote:
> Use PackageManager.hasSystemFeature(PackageManager.FEATURE_CAMERA).
>
> O
I am afraid using using ErrorCallback wont work.
You can only place the ErrorCallback on an Camera object, but you wont
get a camera object until you call Camera.open().
Hope you got my point.
Thanks,
Daman
On Jun 30, 3:47 am, Indicator Veritatis wrote:
> I think the intent of the designer of An
Yes, this is the better method. The only thing I would add is that the
class PackageManager is itself in the Java package android.content.pm
-- not an obvious place, but not too hard to figure out.
On Jun 29, 5:12 pm, Dianne Hackborn wrote:
> Use PackageManager.hasSystemFeature(PackageManager.FEA
I think the intent of the designer of Android is that instead of
detecting camera presence at runtime, developers should declare the
CAMERA permission in the AndroidManifest file. Also, include the tag. Then your application would be downloaded only to
devices that have a camera.
But just in case
I too am trying to figure this out - is there a reliable way to know
whether a device has camera hardware at all?
Thanks,
Ashutosh
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@goog
9 matches
Mail list logo
