Ed Morley [:emorley] Reporter
	Description • 9 years ago

Now that bug 1176967 is fixed, when doing the device discovery for WebIDE with my foxfood phone, I now correctly get the camera activated when choosing "scan and remember".

However, no matter how long I point the phone at the QR code, or at different distances/angles etc, the phone does not see that there is a QR code in the preview image shown on the screen, and I cannot get any further with the process.

The QR code in the preview image looks pretty blurry - maybe the camera needs to have macro focus mode enabled when activated for device discovery?

	Ed Morley [:emorley] Reporter
	Comment 1 • 9 years ago

My phone has a "build identifier" of 20150727151800, and a "build number" of eng.worker.20150619.224059 (the distinction between the two isn't very clear IMO). Checking for updates as of today, returns no more, on the dogfood update channel.

	Ed Morley [:emorley] Reporter
	Comment 2 • 9 years ago

If I instead use the front camera, it works fine (the preview image seems much higher quality... or at least more in focus).

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)
	Comment 3 • 9 years ago

Huh, yeah, I have also noticed it's much harder to scan in the latest foxfood OTA version.

Back in the initial foxfood release that was pre-installed at Whistler, scanning worked well the back camera and proceeded smoothly.

So, it seems something has regressed, but it's not clear what it is yet.

The current QR scanner uses the getUserMedia API (not the Camera app) which has a lot less control over fine details of the camera.  So, perhaps something has changed in the Gecko gUM implementation that regressed this behavior.

It will take a bit of sleuthing to find the cause, especially since there was a Gaia error preventing the scanner from appearing for a while.

I am glad you were at least able to get a connection finally!

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)
	Comment 4 • 9 years ago

With a more recent foxfood build ID (20150812...), if I choose the back camera, I get "InternalError: Starting video failed" (only visible via ADB today), and no camera preview is displayed at all.  The front camera continues to work as expected.

The error is more visible if you test on the gUM test page[1], choose "Video", and choose the back camera.  The error message is displayed on the web page.

[1]: https://mozilla.github.io/webrtc-landing/gum_test.html

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)
	Comment 6 • 9 years ago

This appears to be specific to the Aries / Z3C device.

I checked new FOTA for the Flame today, and WiFi debugging is working well there.