title: Android app crashes at start with "E/dex2oat: Failed to create oat file" and "non-0 exit status"
body: <p>My app (still WIP) runs fine on different devices. But suddenly it refuses to start on Huawei Honor 7 (Android 6.0/EMUI 4.0.3). Logcat gives me the following:</p>
  <blockquote>
  <p>E/dex2oat: Failed to create oat file:<br />
  /data/dalvik-cache/arm64/data@app@myapp.mycomp.de.myapp-1@split_lib_slice_1_apk.apk@classes.dex:<br />
  Permission denied</p>
  </blockquote>
  <p>followed by</p>
  <blockquote>
  <p>07-12 19:23:49.223<br />
  11280-11280/myapp.mycomp.de.myapp W/art: Failed<br />
  execv(/system/bin/dex2oat --runtime-arg -classpath --runtime-arg<br />
  --debuggable --instruction-set=arm64 --instruction-set-features=smp,a53 --runtime-arg -Xrelocate --boot-image=/system/framework/boot.art --runtime-arg -Xms64m --runtime-arg -Xmx512m --instruction-set-variant=generic --instruction-set-features=default --dex-file=/data/app/myapp.mycomp.de.myapp-1/split_lib_slice_1_apk.apk<br />
  --oat-file=/data/dalvik-cache/arm64/data@app@myapp.mycomp.de.myapp-1@split_lib_slice_1_apk.apk@classes.dex)<br />
  because non-0 exit status</p>
  </blockquote>
  <p>This error occurs 9 times for <code>spli_lib_slice_N_apk.apk-parts</code> . I really have no idea, what it could be, especially since it run fine until today. I did no changes to the code. I also don't use any multidex, as far as I know.</p>
  <p>Any hint is appreciated, Thank you!</p>
  <p><strong>UPDATE JULY, 13TH 2017:</strong>
  I logged the app starts with a device on which it always works and I got the same &quot;errors&quot; as above. So it seems, that these messages may be normal... After this I had a look into the crash log of the faulty device and found the following lines shortly AFTER the errors I posted above:</p>
  <blockquote>
  <p>07-12 20:30:35.985 3209-3421/? I/logserver: extract_appname, forward search, appname=myapp.mycomp.de.myapp<br />
  07-12 20:30:35.985 3209-3421/? I/logserver: get_fault_appname, appname=myapp.mycomp.de.myapp<br />
  07-12 20:30:35.987 3209-3420/? I/logserver: handle_notify_event, send msg [submit:trigger=0,bugtype=2,modulename=myapp.mycomp.de.myapp,level=1,testtype=NORMAL,path=/data/log/unzip/PLK-L01_PLK-L01C432B390_0000000000_20170712203035_crash,mode=1;]<br />
  07-12 20:30:36.014 21797-21899/myapp.mycomp.de.myapp I/System: core_booster, getBoosterConfig = false<br />
  07-12 20:30:36.290 21797-21797/myapp.mycomp.de.myapp I/Process: Sending signal. PID: 21797 SIG: 9</p>
  </blockquote>
  <p>It seems the process gets killed by Sigkill 9, see also on SE here: <a href="https://stackoverflow.com/questions/11420963/app-dies-with-sending-signal-but-no-exception-or-other-info">App dies with &quot;Sending signal.&quot; but no exception or other info</a></p>
  <p>But again I have no idea what causes this. After this, I cleared the app data within androids app-preferences and suddenly the app starts again. The investigation will continue...</p>