summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramStore.java
diff options
context:
space:
mode:
authorMasanori Ogino <ogino.masanori@sharp.co.jp>2012-05-07 16:44:48 +0900
committerMasanori Ogino <ogino.masanori@sharp.co.jp>2012-05-07 16:44:48 +0900
commit2d91007e051f8fe90238c26a3509c76ea56a992b (patch)
tree5351076282518029c580df88fab53694a87b799e /rs/java/android/renderscript/ProgramStore.java
parenta10cc893f7e1f21783ea60c50a49401181611027 (diff)
Avoid adding FORWARD_LOCK flag to an updated system app
Consider the following case: 1. An app exists in /system/app or /vendor/app. (i.e, it's a system app) 2. If the app would be updated as a forward-lock app by downloading from market(google play), then it would be installed in /data/app-private. 3. Moreover, if it would be updated by the whole system image (i.e, FOTA or something like that), then the app would be applied a FORWARD_LOCK flag. The app SHOULD NOT have a FORWARD_LCOK flag. Because the resource path of such app does not refer to the proper resources to access. Change-Id: I0750f69a93a3115f4201029796b598507de3555f
Diffstat (limited to 'rs/java/android/renderscript/ProgramStore.java')
0 files changed, 0 insertions, 0 deletions