Searched refs:debuggable (Results 1 – 25 of 27) sorted by relevance
12
/frameworks/base/docs/html/tools/ |
D | device.jd | 76 <li>Verify that your application is "debuggable" in your manifest or <em>build.gradle</em> file. 77 <p>In the build file, make sure the <em>debuggable</em> property in the <em>debug</em> build 83 debuggable true 87 <p>In the <code>AndroidManifest.xml</code> file, add <code>android:debuggable="true"</code> to 91 should usually <em>not</em> be debuggable).</p></li>
|
D | workflow.jd | 41 <p>During this phase you build your project into a debuggable <code>.apk</code> package that you
|
/frameworks/base/docs/html/tools/help/ |
D | monitor.jd | 42 in order for the device to be fully debuggable.</p>
|
/frameworks/base/docs/html/training/basics/firstapp/ |
D | index.jd | 27 project and run a debuggable version of the app. You'll also learn some fundamentals of Android app
|
/frameworks/opt/telephony/ |
D | README.txt | 47 On debuggable builds (userdebug, eng) you can change additional
|
/frameworks/base/docs/html-intl/intl/zh-cn/tools/publishing/ |
D | preparing.jd | 98 …<code><application></code> 代码中移除 <code>android:debuggable</code> 属性或将 <code>android:debuggab…
|
D | publishing_overview.jd | 52 …@docRoot}guide/topics/manifest/application-element.html#debug">android:debuggable</a> 属性,还应为 <code…
|
/frameworks/base/docs/html-intl/intl/ja/guide/publishing/ |
D | preparing.jd | 85 <li><code>android:debuggable="true"</code> 属性をマニフェストの <code><application></code> 要素から削除します。</…
|
/frameworks/base/docs/html/tools/building/ |
D | building-eclipse.jd | 83 <li>Ensure that your application is debuggable by setting the 84 <code>android:debuggable</code> attribute of the <code><application></code>
|
D | building-studio.jd | 229 <li>Ensure that your application is debuggable by setting the 230 <code>android:debuggable</code> attribute of the <code><application></code>
|
D | plugin-for-gradle.jd | 167 <li>build properties such as debuggable, ProGuard enabling, debug signing, version name 199 debuggable true
|
D | building-cmdline.jd | 46 …with a debug key based on the <code>debuggable true</code> setting in the module's gradle.build fi…
|
D | configuring-gradle.jd | 456 debuggable true
|
/frameworks/base/docs/html/tools/workflow/ |
D | index.jd | 44 <p>During this phase you build your project into a debuggable <code>.apk</code> package(s)
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | application-element.jd | 11 android:<a href="#debug">debuggable</a>=["true" | "false"] 58 {@code debuggable}, {@code enabled}, {@code description}, and 130 <dt><a name="debug"></a>{@code android:debuggable}</dt>
|
/frameworks/base/docs/html/tools/publishing/ |
D | preparing.jd | 185 <code>android:debuggable</code> attribute from the <code><application></code> tag in your 186 manifest file, or by setting the <code>android:debuggable</code> attribute to
|
D | publishing_overview.jd | 63 <a href="{@docRoot}guide/topics/manifest/application-element.html#debug">android:debuggable</a>
|
/frameworks/base/tools/aapt/ |
D | Command.cpp | 1158 int32_t debuggable = AaptXml::getResolvedIntegerAttribute(res, tree, in doDump() local 1165 if (debuggable != 0) { in doDump()
|
/frameworks/av/services/audioflinger/ |
D | AudioFlinger.cpp | 193 int debuggable = atoi(value); in AudioFlinger() local 195 if (debuggable) { in AudioFlinger()
|
/frameworks/base/docs/html/tools/debugging/ |
D | ddms.jd | 62 DDMS assigns port 8600 for the first debuggable VM, the next on 8601, and so on. When a debugger
|
D | debugging-studio.jd | 51 <p>To debug your app, Android Studio builds a debuggable version of your app, connects
|
/frameworks/base/docs/html/tools/sdk/ |
D | tools-notes.jd | 1679 <code>android:debuggable</code> attribute to the 1682 to be debug builds, so the tools insert <code>android:debuggable="true"</code>. 1685 <code>android:debuggable="true"</code> attribute, while <code>ant release</code> 1686 does not. If <code>android:debuggable="true"</code> is manually set, then
|
D | eclipse-adt.jd | 1944 <code>debuggable=true</code> was not set in the Android manifest.</li> 2012 <code>debuggable</code> attribute in the Android Manifest. 2013 <p>Incremental builds automatically insert <code>debuggable="true"</code>, but if you perform 2015 If you manually set <code>debuggable="true"</code> in the manifest file, then release builds will
|
/frameworks/base/docs/html/training/articles/ |
D | perf-jni.jd | 447 <p>You can also set the <code>android:debuggable</code> attribute in your application's manifest to
|
/frameworks/base/docs/html/tools/sdk/ndk/ |
D | index.jd | 476 <code>AndroidManifest.xml</code> containing <code>android:debuggable="true"</code>), 3229 builds of debuggable projects.</li> 3278 <li>Increased the build speed of debuggable applications when there is a very large number
|
12