[Nexus 5 Original Android Development] dakore:
Just to confirm something I've been trying to solve for the last few months...

Does anyone have problem with Google Camera force close? I have following setup:

- using 16:9 sensor

- HDR enabled

- ART runtime

- ElementalX 1.0

Now whenever I try to disable HDR or switch to lens blur or any other mod, I got FC.

Logcat from clean stable 7.0:

E/AndroidRuntime( 5846): at com.android.internal.os.ZygoteInit$MethodAndA

rgsCaller.run(ZygoteInit.java:795)

E/AndroidRuntime( 5846): at com.android.internal.os.ZygoteInit.main(Zygot

eInit.java:611)

W/ActivityManager( 874): Force finishing activity com.google.android.GoogleCa

mera/com.android.camera.CameraLauncher

W/BackupManagerService( 874): dataChanged but no participant pkg='com.android.p

roviders.settings' uid=10072

W/ActivityManager( 874): Activity pause timeout for ActivityRecord{6580f4b0 u0

com.google.android.GoogleCamera/com.android.camera.CameraLauncher t85 f}

I/Timeline( 1319): Timeline: Activity_idle id: android.os.BinderProxy@6511ab50 t

ime:7576013

W/BackupManagerService( 874): dataChanged but no participant pkg='com.android.p

roviders.settings' uid=10072

D/BluetoothAdapter(20395): 1697065904: getState() : mService = null. Returning

STATE_OFF

I/Timeline( 874): Timeline: Activity_windows_visible id: ActivityRecord{6599e3c

0 u0 com.teslacoilsw.launcher/com.android.launcher2.Launcher t1} time:7576241

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8744096 Cur

Position: 36

W/GA-SERVICE( 1650): Thread[Thread-128,5,main]: Exception sending hit: HttpHostC

onnectException

W/GA-SERVICE( 1650): Thread[Thread-128,5,main]: Connection to https://ssl.google

-analytics.com refused

W/GA-SERVICE( 1650): Thread[Thread-128,5,main]: Empty hitIds passed to deleteHit

s.

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8861813 Cur

Position: 31

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 9032688 Cur

Position: 26

I/ActivityManager( 874): Process android.process.media (pid 3679) has died.

W/ActivityManager( 874): Scheduling restart of crashed service com.android.prov

iders.media/.MtpService in 1000ms

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8499525 Cur

Position: 21

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8324491 Cur

Position: 16

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8287380 Cur

Position: 11

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8246615 Cur

Position: 6

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8188296 Cur

Position: 1

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8103801 Cur

Position: 0

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 8159699 Cur

Position: 29

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 6130682 Cur

Position: 31

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 6315498 Cur

Position: 33

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 6273379 Cur

Position: 35

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 6251611 Cur

Position: 37

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 5686077 Cur

Position: 39

I/mm-camera( 226): af_util_cur_pos_after_lens_move: After move: FV: 4499215 Cur

Position: 31

I/mm-camera( 226): af_util_update_focus_status: AF Status already updated to ou

tput!Return!

I/mm-camera( 226): af_util_update_focus_status: AF Status already updated to ou

tput!Return!

W/art ( 211): Could not get current activity

I/ActivityManager( 874): Start proc android.process.media for service com.andro

id.providers.media/.MtpService: pid=5984 uid=10005 gids={50005, 1028, 1015, 1023

, 1024, 2001, 3003, 3007}

D/MtpService( 5984): updating state; isCurrentUser=true, mMtpLocked=false

D/MtpService( 5984): addStorageLocked 65537 /storage/emulated/0

D/MtpService( 5984): updating state; isCurrentUser=true, mMtpLocked=false

D/MtpService( 5984): starting MTP server in MTP mode

D/MtpService( 5984): addStorageLocked 65537 /storage/emulated/0

E/ANDR-PERF-LOCK( 1589): Failed to reset optimization for resource: 1 level: 12

When I switch to 4:3 sensor, everything works fine. On dalvik both sensor types work fine. Is this known (google?) bug or not? I'm using 16:9 sensor and ART all the time, and noticed this problem after stable 6.0.