## Environment : Unagi phone, build 2012-10-11 us Taken from default.xml in b2g-distro: * "platform_build" revision= 0d6d050bc37d3167cc82a1885fd7660456bb0f4e * "gaia" revision= 2667536e3b06e46dd193aa6d76ba08dad2d867be * "releases-mozilla-central" revision= c0ea0728044b2a5f9556ca988635140963cff037 * "gonk-misc" revision= 6ec34aa3d66331054de37eabc594ad923654b27c ## Repro : 1. launch camera app 2. select video 3. hit home and come back to video to avoid frame freeze bug 4. select record button ## Expected : 1. video records until you hit the record stop button ## Actual : 1. no indication of recording, video stops almost as soon as it starts. You can verify by looking at adb shell and ls'ing /sdcard/ dir. new VID are incrementally added ## Note :

Sounds like a platform issue, I dont have a unagi to test but when I get will will try diagnosing, it may be drivers or someing mwu related

P1: dogfood blocker

Is this tacking both the "freeze bug", "not knowing if it is recording" and "not showing recorded videos on the gallery"?

Only the fact that video recording doesnt start correctly, and this was a duplicate of various bugs that we had in the video recording. It should now be fixed. Can someone with a unagi test that when you switch to video recording and press record that recording starts with a timer on the left hand side. If so this should be marked resolved, the fact that videos are not shown in the video app is a seperate issue

(In reply to Dale Harvey (:dale) from comment #6) > Can someone with a unagi test that when you switch to video recording and > press record that recording starts with a timer on the left hand side. Still not working because the 'cif' profile isn't supported (bug 804359). When switching to 'high' recording still doesn't work because of bug 805777.

This is because, much like Otoro, Unagi is missing libOmxVidEnc.so and a specific version of media_profiles.xml. Just looking at how those were added to Otoro.

General question: Do changes on the Camera app get delivered off band from the general phone update? I'm currently on 10-24th and I don't know when the next update will come out.

We need a full system update to fix this. Thats still a few days out.

Comment on attachment 676204 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/android-device-unagi/pull/4/files Stealing.

(In reply to Dale Harvey (:dale) from comment #6) > > Can someone with a unagi test that when you switch to video recording and > press record that recording starts with a timer on the left hand side. With the extra files in the github pull request, confirmed: video recording works, and the timer ticks over.

This did not make it into the 11-01 update to the dogfood testers, correct?

(In reply to Armen Zambrano G. [:armenzg] from comment #15) > > This did not make it into the 11-01 update to the dogfood testers, correct? Not sure, but you can check by connecting to the device with |adb shell| and typing |ls -l /system/etc/media_profile.xml| and |ls -l /system/lib/libOmcVidEnc.so|. You should see, respectively: -rw-r--r-- root root 18066 2012-10-30 16:13 media_profiles.xml -rw-r--r-- root root 215512 2012-10-30 16:13 libOmxVidEnc.so If you don't see these files with these sizes, then no.

We need FOTA updates to change those files, and additionally there are some legal issues. For now you can get a manual fix-up.

How far are the legal issues from being cleared up? Would it make sense to disable the feature until it is fully working? (to prevent confusion).

We need to leave the feature enabled so that we can continue to test it. Legal issues are cleared up, but not in a helpful way unfortunately.

I'd say this bug is fixed and OTA/legal issues should be tracked in a separate bug. Just checked what Dale says and it works for me on Unagi with the due library installed.

Milestoning for C2 (deadline of 12/10), as this meets the criteria of "remaining P1 bugs not already milestoned for C1".

What's the current status of this? Can we close it and track the legal issues separately? The bug as titled is no longer occurring.

(In reply to Dietrich Ayala (:dietrich) from comment #23) > > What's the current status of this? Can we close it and track the legal > issues separately? The bug as titled is no longer occurring. See bug 816573.

Verified on unagi build id: 20130103070201 See also https://bugzilla.mozilla.org/show_bug.cgi?id=826459