Lines Matching full:code
24 (use <code>adb shell dalvikvm -help</code> to get a summary), but
30 with <code>setprop</code>,
35 effect</strong> (<code>adb shell stop; adb shell start</code>). This is because the
39 <p>You may not be able to set <code>dalvik.*</code> properties or restart
41 <code>adb root</code> or run the <code>su</code> command from the device
44 will tell you if the <code>setprop</code> took.
47 add a line to <code>/data/local.prop</code> that looks like:
51 partition is wiped. (Hint: create a <code>local.prop</code>
52 on your workstation, then <code>adb push local.prop /data</code>. Or,
54 <code>adb shell "echo name = value >> /data/local.prop"</code> -- note
60 <p>JNI, the Java Native Interface, provides a way for code written in the
62 interact with native (C/C++) code. The extended JNI checks will cause
67 enabled with the <code>-Xcheck:jni</code> command-line argument. The
68 first is <code>ro.kernel.android.checkjni</code>. This is set by the
70 the Android emulator unless the <code>-nojni</code> flag is provided on the
75 property, <code>dalvik.vm.checkjni</code>, is also checked. The value
76 of this overrides the value from <code>ro.kernel.android.checkjni</code>.
78 <p>If neither property is defined, or <code>dalvik.vm.checkjni</code>
79 is set to <code>false</code>, the <code>-Xcheck:jni</code> flag is
86 property. The value set for <code>dalvik.vm.jniopts</code> will
87 be passed in as the <code>-Xjniopts</code> argument. For example:
94 By default they are off, but the <code>dalvik.vm.enableassertions</code>
95 property provides a way to set the value for a <code>-ea</code> argument.
106 It is not possible to specify more than one <code>-ea</code> entry, and there
107 is no way to specify a <code>-da</code> entry. There is presently no
108 equivalent for <code>-esa</code>/<code>-dsa</code>.
115 runtime performance. Both of these are done by the <code>dexopt</code>
117 device, <code>dexopt</code> may be run the first time a DEX file is used
123 <code>-Xverify</code> and <code>-Xdexopt</code>. The Android framework
124 configures these based on the <code>dalvik.vm.dexopt-flags</code>
129 then the framework will pass <code>-Xverify:all -Xdexopt:verified</code>
132 <p>You could also set <code>dalvik.vm.dexopt-flags</code> to <code>v=n</code>
133 to have the framework pass <code>-Xverify:none -Xdexopt:verified</code>
134 to disable verification. (We could pass in <code>-Xdexopt:all</code> to
136 code, since classes that fail verification may well be skipped by the
138 <code>dexopt</code>, and unverified code will be loaded and executed.
140 <p>Enabling verification will make the <code>dexopt</code> command
154 stop and restart the runtime (<code>adb shell stop; adb shell start</code>).
157 <code>dalvik.vm.verify-bytecode</code> property, but that has been
158 superceded by <code>dalvik.vm.dexopt-flags</code>.)</p>
173 with the same flag. (Check the output of <code>dalvikvm -help</code> to
177 extended form of the <code>-Xint</code> argument. The value of this
178 argument can be set through the <code>dalvik.vm.execution-mode</code>
200 <code>android:vmSafeMode="true"</code> in the <code>application</code>
201 tag in <code>AndroidManifest.xml</code>. This can be useful if you
209 (Ctrl-\ or <code>kill -3</code>), it dumps stack traces for all threads.
212 <p>The <code>dalvik.vm.stack-trace-file</code> property allows you to
216 is passed into the VM via the <code>-Xstacktracefile</code> argument.
234 <code>-Xcheckdexsum</code> argument. When set, the checksums on all DEX
238 creation if the <code>dalvik.vm.check-dex-sum</code> property is enabled.
246 <code>/data/local.prop</code>.
249 <code>dexdump</code> tool always verifies DEX checksums, and can be used
266 example, to experiment with different values for <code>-Xmx</code> even
