title: AOSP building: replace my own keys with default test-keys
body: <p>I am building AOSP and I want to sign the build with my own key. There is some official doc about this process <a href="https://source.android.com/devices/tech/ota/sign_builds" rel="nofollow noreferrer">here</a>.</p>
  
  <p>But I wonder if I can simply turn around all of that process and instead do this things:</p>
  
  <ol>
  <li>Delete default android test-keys which are located at <code>build/target/product/security</code></li>
  <li>put my keys (which are generated using official instructions at <a href="https://source.android.com/devices/tech/ota/sign_builds#manually-generating-keys" rel="nofollow noreferrer">here</a>) in that folder with same names. (Assume one key for all of shared,media,...)</li>
  </ol>
  
  <p>But this approach does not work. After burning the image, system apps (SystemUI, settings,..) will stop and continuously show the ANR dialog. I know this happens if system signature does not match with these apps's signature... but why?</p>
  
  <p>Another question: Is using same key as <code>shared.pk8</code> , <code>media.pk8</code>, <code>testkey.pk8</code> , ... causes any problem?</p>
  
  <p>Thanks</p>