After tacking a few pictures, camera in my Meizu MX4 Ubuntu Edition
locks up, i.e. Camera App displays black screen, and if I try to
restart it, it says that this app does not have permission to access
camera. Rebooting the device helps, but only for a few more snaps.
It seems to happen randomly, sometimes only after a second photo, and
sometimes after 10th or so. It seems to be linked to locking the
device when the camera is on, or maybe switching to other apps, or a
combination of these behaviours, but I'm not sure.
I can reproduce this behaviour with some effort, so I took a look at
dmesg output on the phone, but I'm not sure I see antyhing
incriminating. The log seems to be the same for "healthy" photo and
for "broken" one, both containing a fair number of error messages
[mt-i2c]ERROR,454: id=0,addr: 54, transfer error
[mt-i2c]ERROR,460: I2C_ACKERR
[CAM_CAL] I2C send read address failed!!
[CAM_CAL]I2C read liteon e2prom failed!!
The only thing I have is that I see a lot more mt-i2c errors after
bugged photo:
[ 496.276011] [LC898212XD] LC898212XD_Release - Start
[ 496.276018] [LC898212XD] LC898212XD_Release - End
[ 496.334223] [ion_dbg] warning: free_list_size=0xc862000
[ 496.347719] [ion_dbg] warning: free_list_size=0xc862000
[ 496.559796] [mt-i2c]ERROR,454: id=0,addr: 54, transfer error
[ 496.559832] [mt-i2c]ERROR,460: I2C_ACKERR
[ 496.560223] [mt-i2c]ERROR,454: id=0,addr: 54, transfer error
[ 496.560241] [mt-i2c]ERROR,460: I2C_ACKERR
[ 496.705554] [mt-i2c]ERROR,454: id=0,addr: 37, transfer error
[ 496.705591] [mt-i2c]ERROR,460: I2C_ACKERR
[ 496.705686] [mt-i2c]ERROR,454: id=0,addr: 37, transfer error
What other diagnostic can I gather before submitting a bug?
--
