Steps to repo.
Launch Camera App from android and click a picture.
After clicking observe Camera app. closes and on logcat spew crash is observed.
Camera recording works fine.
Attaching logcat o/p from the crashes.
cheers,
mohit
@joanxie I debugged a little more and if I limit the resolution to 720p(see below) in the camera HAL, it no longer crashes.
uint32_t ispResNum = 0;
cheers,
mohit
@joanxie I don't have NXP imx8mn ddr4 device with me. I have moved to Android 11.0.0_2.6.0 (Linux 5.10.72 kernel) and observed the same crash. Please see camera_crash_Android_11.0.0_2.6.0.txt.
For me, the crash comes on the first try itself.
The camera name is already there in the log "isi-capture 32e20000.isi:cap_device: mxc_isi_capture_open: src name is ov5640 1-003c"
After the crash, I can still open the app and can see the preview, click the picture which results in the crash.
cheers,
mohit
After the crash, I can still open the app and can see the preview, click the picture which results in the crash.
>what crash do you mean? the camera is frozen? could you borrow a ddr4 board from local DFAE? the expert team couldn't reproduce this issue either, my test steps is:
1) open the camera app
2) click the picture to save picture more than 10 pictures
3) open all of the pictures to review one by one, the app or the display aren't frozen
when I take picture, I can get the message from display:
[ 123.046711][ T466] bypass csc
[ 123.049836][ T466] input fmt YUV4
[ 123.053257][ T466] output fmt YUYV
[ 129.277557][ T349] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400000 fc=4000000 cc=32 chg=a
[ 159.215704][ T466] bypass csc
[ 159.218786][ T466] input fmt YUV4
[ 159.222203][ T466] output fmt YUYV
[ 161.227841][ T1772] bypass csc
[ 161.230986][ T1772] input fmt YUV4
[ 161.234419][ T1772] output fmt YUYV
[ 162.575045][ T465] bypass csc
[ 162.578415][ T465] input fmt YUV4
[ 162.582228][ T465] output fmt YUYV
[ 164.511270][ T466] bypass csc
[ 164.514369][ T466] input fmt YUV4
[ 164.517800][ T466] output fmt YUYV
[ 165.375910][ T465] bypass csc
[ 165.379013][ T465] input fmt YUV4
[ 165.382456][ T465] output fmt YUYV
[ 167.279484][ T466] bypass csc
[ 167.282583][ T466] input fmt YUV4
[ 167.286014][ T466] output fmt YUYV
if you need further test on imx8mm board, pls let me know it, we need reproduce this on nxp imx8mm board
>>what crash do you mean?
I am not sure if you got the chance to look at the logs I attached earlier. I am pasting the some part of it here.
--------- beginning of crash
libc : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x6dfc1f9000 in tid 1796 (Thread-2), pid 1713 (android.camera2)
I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
I tombstoned: received crash request for pid 1796
I crash_dump64: performing dump of process 1713 (target tid = 1796)
: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
: Build fingerprint: 'Android/som_mx8mn/som_mx8mn:11/RQ3A.211001.001/eng.mohit.20220117.111624:userdebug/dev-keys'
: Revision: '0'
: ABI: 'arm64'
: Timestamp: 2022-01-17 21:06:26+0000
: pid: 1713, tid: 1796, name: Thread-2 >>> com.android.camera2 <<<
: uid: 10103
: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x6dfc1f9000
: x0 0000000076ae400c x1 0000006dfc1f8fb4 x2 000000000004b8b8 x3 0000000076ee3fc0
: x4 0000006dfc2448bc x5 0000000076f2f8c8 x6 7190e4201c50953c x7 f9d4633e700e82d0
: x8 e69ef5f449f5896f x9 0a3914222bc94bd9 x10 79f9410e68031fab x11 d562169c6c850ada
>>the camera is frozen?
App closes on its own after above crash, however I can re-open it and try to take the pic and it again results in the above mentioned behaviour.
Are you testing on imx8mm ? I have reported the issue on i. MX8M Nano.
imx8mm does __not__ have this issue when I tested it on Android 11.0.0_2.4.0 (kernel 5.10.52).
Also please note "if I limit the resolution to 720p(see below) in the camera HAL, it no longer crashes."
cheers,
mohit
how about the status now? the expert team couldn't reproduce this, if you still need help, pls answer these questions from expert team:
“Did the customer modify the code base at all around the cameras? Are they using a custom Android build? If so, can they share those code changes so we can reproduce the bug on our end? It will be much easier to debug if I can reproduce the issue here.
If not, I can try and send this to the rest of the video team to see if anyone has seen an error like this before.”
Yes, the issue is still present. As a work around I have capped the resolution to 720p. However, we still need a fix for it.
cheers,
mohit
if you still have issue, do you mind answering the below question from expert team?
“Did the customer modify the code base at all around the cameras? Are they using a custom Android build? If so, can they share those code changes so we can reproduce the bug on our end? It will be much easier to debug if I can reproduce the issue here.
If not, I can try and send this to the rest of the video team to see if anyone has seen an error like this before.”
sorry, this is my typo, I tested on imx8mn ddr4 board of course, I will forward your message to expert team and discussed with them, but I still suggest that you can test on nxp board if you could borrow this from local DFAE
Hi Joanxie,
We are using DDR4 based VAR-SOM-MX8M-NANO and the issue is 100% repro. with Android 11.0.0_2.4.0 (kernel 5.10.52) and works fine with Android 11.0.0_1.0.0 (kernel 5.4.47).
cheers,
mohit
I have downloaded the new android bsp from official website and flashed to my imx8mn ddr4 board again, I found my camera app is find with capturing picture, do you have nxp imx8mn ddr4 board to test? I couldn't reproduce this on my board right now,I launched the app and took picture more than 10 times, what camera do you use? I used ov5640, after you get the crash issue, could you open the app again?
my camera app has different issue on nxp imx8mn ddr4 board, we already escalated this issue to the internal team, pls wait for further debug
what board do you test? I have tested on my imx8mn lpdd4 board without issue, I open the camera app, and capture almost 10 pictures, and close the app or ctrl+c on the console, don't find any crash issues