diff options
| author | Lingfeng Yang <lfy@google.com> | 2016-04-27 09:12:25 -0700 |
|---|---|---|
| committer | Lingfeng Yang <lfy@google.com> | 2016-04-27 11:09:39 -0700 |
| commit | 996546fcf4058d98d9aceecb4086283e17ae6c9d (patch) | |
| tree | e90afac0a3f1b2a989412bdaa656b835d0eea93e /jni/feature_stab/db_vlvm/db_utilities_constants.h | |
| parent | 8e2f0e48cb3d2209f1cf818b6cf8c4bd95645783 (diff) | |
| download | LegacyCamera-996546fcf4058d98d9aceecb4086283e17ae6c9d.zip LegacyCamera-996546fcf4058d98d9aceecb4086283e17ae6c9d.tar.gz LegacyCamera-996546fcf4058d98d9aceecb4086283e17ae6c9d.tar.bz2 | |
Prevent camera app crashes on changing hw.camera.* settings
If the AVD's config.ini changes hw.camera.*, this is effectively,
connecting/disconnecting camera hardware, and the current
way in which camera settings are handled assumes
that the set of cameras never changes, which can lead to
the camera app crashing if the camera app was used successfuly
with one configuration of hw.camera.* and then
the AVD was restarted with a different configuration.
In particular, the crash happens if the number of cameras
has been reduced since the last run, and the camera app
is looking up a preferred camera ID that is not supported
by the new number of cameras.
bug: 28417929
BUG: https://code.google.com/p/android/issues/detail?id=206945
Change-Id: Ib0e26ae77d376f31f3cc281e386d3c67291c1edc
(cherry picked from commit 8f339abd9245577c348f5ba22322e8801c21faf8)
Diffstat (limited to 'jni/feature_stab/db_vlvm/db_utilities_constants.h')
0 files changed, 0 insertions, 0 deletions