973689 - [B2G][inari][camera]: Unable to record videos

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Camera, defect)

Description

[pazos]

Attachment: full logcat during error

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Steps to reproduce:

in B2G v1.3 (lastest nightly) with blobs from 1.1.0B02.

 - Open camera app:
 - Go to record video option:
 - Press the center icon to start the record


Actual results:

Screen gets frozen by a couple of seconds, then an error (in spanish:video no grabado. Un error impidió que la aplicación Cámara grabara el video)

Video is not recorded


Expected results:

The icon in the middle turns it red and the video starts recording

Comment 1

[pazos]

Attachment: "DEBUG" logcat during an error

Comment 2

[Mike Habicher [:mikeh] (high bugzilla latency)]

On Inari, I see the b2g parent process consuming all available CPU time:

# adb shell "top -d 1000 -m 10 -s cpu -t"
User 35%, System 65%, IOW 0%, IRQ 0%
User 32 + Nice 3 + Sys 65 + Idle 0 + IOW 0 + IRQ 0 + SIRQ 0 = 100

  PID   TID PR CPU% S     VSS     RSS PCY UID      Thread          Proc
  111   228  0  89% R 159244K  73244K  fg root     Gecko_IOThread  /system/b2g/b2g
  444   444  0   7% R   1096K    448K  fg root     top             top
  360   360  0   2% R  80392K  30912K  fg app_360  Usage           /system/b2g/plugin-container
  360   373  0   2% R  80392K  30912K  fg app_360  Chrome_ChildThr /system/b2g/plugin-container
  361   364  0   2% R  87248K  39828K  fg app_361  Chrome_ChildThr /system/b2g/plugin-container
    8     8  0   0% S      0K      0K  fg root     suspend         
    9     9  0   0% S      0K      0K  fg root     sync_supers     
   10    10  0   0% S      0K      0K  fg root     bdi-default     
   11    11  0   0% S      0K      0K  fg root     kblockd         
   12    12  0   0% S      0K      0K  fg root     khubd           

This makes the device very sluggish, and possibly prevents it from being able to record video.

Possibly due to bug 970895 (and backed out in bug 973824).

Comment 3

[Mike Habicher [:mikeh] (high bugzilla latency)]

Oh, and it looks like the while bug 970895 made it into b2g-inbound, the back out hasn't (yet).

Comment 4

[pazos]

I'm able to reproduce this bug in all B2G branches that I've tested (v1.2, v1.3 & master). Today I've updated the build system and build the master branch, The device works ok but the camera bug is still there

Comment 5

[Mike Habicher [:mikeh] (high bugzilla latency)]

pazos, can you retry this on a build with the patch in bug 973790 in it?

Comment 6

[pazos]

tested with above patch but camera fails to record video too, the error is exactly the same. Is this bug only related to inari / zte open devices, or can be reproduced in other devices too??

Comment 7

[Mike Habicher [:mikeh] (high bugzilla latency)]

pazos, it definitely existed on other devices but was fixed (on helix and hamachi, e.g.) with the patch set that landed last night.

Comment 8

[Mike Habicher [:mikeh] (high bugzilla latency)]

Confirmed that with latest b2g-inbound/master build, video mode and recording work as expected. Trying a 1.3 build.

Comment 9

[Mike Habicher [:mikeh] (high bugzilla latency)]

Confirmed that with the latest aurora/v1.3 build, video mode and recording work as expected:

Gaia      f9a37c77efb4621a1f57e4695b497d18601fe134
Gecko     http://hg.mozilla.org/releases/mozilla-aurora/rev/3d9d920ca43b
BuildID   20140203004001
Version   28.0a2
ro.build.version.incremental=eng.cltbld.20140203.035851
ro.build.date=Mon Feb  3 04:19:55 EST 2014

Comment 10

[pazos]

Ok, I've tested again:

  - with blobs from 1.1.0B02: camera does NOT work
  - with blobs from 1.0.1B02: camera does work

Which blobs are you using? Can you confirm this bug on 1.1.0B02?

Comment 11

[Mike Habicher [:mikeh] (high bugzilla latency)]

(In reply to pazos from comment #10)
> 
> Which blobs are you using? Can you confirm this bug on 1.1.0B02?

How can I check my blob versions?

Comment 12

[pazos]

adb shell "ls -l /" 

some scripts are present in 1.1.0 but not in 1.0.1 like init.qcom.class_core.sh, init.qcom.class_main.sh or init.qcom.early_boot.sh.

Another simple way could be power on your phone "if you see a static fox image (or black screen) before the fox animation you're on 1.0.1, if you see the animation directly (after the splash screen with firefox logo) you're on 1.1.0

Comment 13

[Mike Habicher [:mikeh] (high bugzilla latency)]

19:22:20 ➜  ~  adb shell
root@android:/ # ls -l /
lrwxrwxrwx root     root              2014-02-20 11:47 Device -> /mnt/sdcard2
drwxr-xr-x root     root              2014-02-20 11:47 acct
drwxrwx--- system   cache             2014-02-20 11:51 cache
dr-x------ root     root              2014-02-20 11:47 config
lrwxrwxrwx root     root              2014-02-20 11:47 d -> /sys/kernel/debug
drwxrwx--x system   system            2014-02-20 11:47 data
-rw-r--r-- system   100           116 2013-02-06 15:59 default.prop
drwxr-xr-x root     root              2014-02-20 11:58 dev
lrwxrwxrwx root     root              2014-02-20 11:47 etc -> /system/etc
-rwxr-x--- system   100         98768 2013-02-06 15:59 init
-rw-r--r-- system   100           321 2013-02-11 12:49 init.b2g.rc
-rwxr-x--- system   100          2344 2013-02-06 15:59 init.goldfish.rc
-rwxr-x--- system   100         14083 2013-02-06 15:59 init.qcom.rc
-rwxr-x--- system   100         11014 2013-02-06 15:59 init.qcom.sh
-rwxr-x--- system   100         36721 2013-02-06 15:59 init.qcom.usb.rc
-rwxr-x--- system   100          4672 2013-02-15 13:44 init.qcom.usb.sh
-rw-r--r-- system   100         25387 2013-02-15 18:10 init.rc
-rwxr-x--- system   100         16570 2013-02-06 15:59 init.roamer2.rc
-rwxr-x--- system   100          2039 2013-02-06 15:59 init.target.rc
-rw-r--r-- system   100        614454 2013-02-08 15:18 logo.bmp
drwxrwxr-x root     system            2014-02-20 11:47 mnt
drwxrwx--x system   system            2013-12-10 11:13 persist
dr-xr-xr-x root     root              1969-12-31 19:00 proc
drwx------ root     root              2013-02-21 04:07 root
drwxr-x--- system   100               2013-02-06 15:59 sbin
lrwxrwxrwx root     root              2014-02-20 11:47 sdcard -> /mnt/sdcard
drwxr-xr-x root     root              2014-02-20 11:47 sys
drwxr-xr-x root     root              2014-02-20 08:36 system
-rw-r--r-- system   100           272 2013-02-06 15:59 ueventd.goldfish.rc
-rw-r--r-- system   100          8727 2013-02-06 15:59 ueventd.rc
lrwxrwxrwx root     root              2014-02-20 11:47 vendor -> /system/vendor

I also only see the static fox, so it looks like I'm running 1.0.1.

Comment 14

[pazos]

yes, the static fox is /logo.bmp. You're on 1.0 and camera works ok.

No longer works for me if I upgrade to 1.1: http://www.ztedevices.com/support/smart_phone/cba40ed6-d3ab-44c0-bdee-3a15803dc187.html?type=software (or 1.2: https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z) and build from here (delete backup-inari and pick up the blobs again).

Camera worked ok in zte releases

Comment 15

[heinrich_faust]

I have the same problem here, if I upgrade to 1.1 and build from there, the video camera doesn't work.

Comment 16

[Mike Habicher [:mikeh] (high bugzilla latency)]

I won't have time to look at this any time soon. If anyone else wants to take it up, go ahead.

Comment 17

[Mike Habicher [:mikeh] (high bugzilla latency)]

Are you still having video recording issues with Inari?

Comment 18

[jecomovi]

Comment on attachment 8377256 [details]
"DEBUG" logcat during an error

I think the audio fails fail video recording.

Comment 19

[BMO Automation]

Firefox OS is not being worked on