WebCamTexture.device on the Kindle Fire returning a camera

The Kindle Fire doesn’t possess a camera, yet a call to WebCamTexture.devices returns a singular camera with the WebCamDevice.name property “Camera 0”. Can anyone else replicate this? I am using Debug.Log to output info and reading it via adb logcat. I assume Unity should be notified of this as a bug on Kindle Fire if it can be replicated on other people’s devices.

If you’re wondering why I would need to be checking for an existing camera on a device that doesn’t have one, it is to prevent a certain feature to be activated in the game we are developing.

Thanks.

UPDATE

I messaged the Amazon Tech Support team about the issue to see if they knew about anything their end and this is how they replied:

Thanks for letting us know about this. I haven’t had a chance to check the Unity API, but this is the feature set I get from the standard Android function “getSystemAvailableFeatures”:

10-02 17:22:00.929: V/DUMP_FEATURES(22382): android.hardware.wifi
10-02 17:22:00.929: V/DUMP_FEATURES(22382): android.hardware.touchscreen.multitouch.distinct
10-02 17:22:00.929: V/DUMP_FEATURES(22382): android.hardware.touchscreen.multitouch
10-02 17:22:00.929: V/DUMP_FEATURES(22382): android.hardware.sensor.accelerometer
10-02 17:22:00.929: V/DUMP_FEATURES(22382): android.hardware.touchscreen
10-02 17:22:00.929: V/DUMP_FEATURES(22382): android.software.live_wallpaper
10-02 17:22:00.929: V/DUMP_FEATURES(22382): android.hardware.sensor.light

Looks like it could be a Unity problem after all. I’ve filed a bug report so hopefully, when they get around to it, it’ll get fixed. For now, I’m simply checking SystemInfo.deviceModel against the literal strings “Amazon Kindle Fire” and “Amazon KFOT”. These are the model names of the two non-HD Kindle Fires (Redirect | None).

Hope this helps anyone else who gets stuck with this.

I received an e-mail back from the Unity bug support team. They were able to reproduce the bug and have assigned it to their developers to fix. It should be fixed in the next Unity update or so.

Thanks :slight_smile: