Home
last modified time | relevance | path

Searched refs:migrate (Results 1 – 25 of 26) sorted by relevance

12

/frameworks/base/docs/html/sdk/installing/
Dmigrate.jd22 Android, so you should migrate to Android Studio to receive all the latest IDE updates.</p>
24 <p>To migrate existing Android projects, simply import them using Android Studio:</p>
Dinstalling-adt.jd21 for Android, so you should migrate to Android Studio to receive all the
23 see <a href="/sdk/installing/migrate.html">Migrating to Android
Dstudio-build.jd16 <li><a href="{@docRoot}sdk/installing/migrate.html">Migrating from Eclipse</a></li>
Dstudio-layout.jd13 <li><a href="{@docRoot}sdk/installing/migrate.html">
/frameworks/opt/telephony/src/java/com/android/internal/telephony/
DPhoneBase.java711 migrate(mHandoverRegistrants, from.mHandoverRegistrants); in migrateFrom()
712 migrate(mPreciseCallStateRegistrants, from.mPreciseCallStateRegistrants); in migrateFrom()
713 migrate(mNewRingingConnectionRegistrants, from.mNewRingingConnectionRegistrants); in migrateFrom()
714 migrate(mIncomingRingRegistrants, from.mIncomingRingRegistrants); in migrateFrom()
715 migrate(mDisconnectRegistrants, from.mDisconnectRegistrants); in migrateFrom()
716 migrate(mServiceStateRegistrants, from.mServiceStateRegistrants); in migrateFrom()
717 migrate(mMmiCompleteRegistrants, from.mMmiCompleteRegistrants); in migrateFrom()
718 migrate(mMmiRegistrants, from.mMmiRegistrants); in migrateFrom()
719 migrate(mUnknownConnectionRegistrants, from.mUnknownConnectionRegistrants); in migrateFrom()
720 migrate(mSuppServiceFailedRegistrants, from.mSuppServiceFailedRegistrants); in migrateFrom()
[all …]
/frameworks/base/docs/html/guide/practices/
Dindex.jd23 <p>As Ice Cream Sandwich rolls out to more devices, it's important that you begin to migrate
/frameworks/base/docs/html/guide/topics/ui/
Dindex.jd16 <p>As Ice Cream Sandwich rolls out to more devices, it’s important that you begin to migrate
Dmenus.jd64 provide a dedicated <em>Menu</em> button. With this change, Android apps should migrate away from a
84 don't have one), so you should migrate toward using the action bar to provide access to actions and
/frameworks/base/docs/html/google/gcm/
Dc2dm.jd11 <li>Learn how to migrate an app from C2DM to GCM.</li>
37 …. It describes the differences between GCM and C2DM, and explains how to migrate existing C2DM app…
/frameworks/opt/telephony/src/java/com/android/internal/telephony/sip/
DSipPhoneBase.java81 migrate(mRingbackRegistrants, from.mRingbackRegistrants); in migrateFrom()
/frameworks/opt/telephony/src/java/com/android/internal/telephony/imsphone/
DImsPhoneBase.java78 migrate(mRingbackRegistrants, ((ImsPhoneBase)from).mRingbackRegistrants); in migrateFrom()
/frameworks/base/docs/html/google/play/billing/
Dindex.jd17 …wn in January 2015. If your app is still using In-app Billing v2, please migrate to the v3 API as …
Dbilling_overview.jd165 earlier, you must migrate to <a href="{@docRoot}google/play/billing/api.html">In-app Billing Version
/frameworks/base/docs/html/sdk/
Dindex.jd314 <li><a href="{@docRoot}sdk/installing/migrate.html">Migrating to Android Studio</a></li>
435 for Android, so you should migrate to Android Studio to receive all the
437 see <a href="{@docRoot}sdk/installing/migrate.html">Migrating to Android
DRELEASENOTES.jd86 to make a few changes to your development environment to migrate to the new SDK.
93 to migrate the application to the new SDK, compile it using the platform
361 to make a few changes to your development environment to migrate to the new SDK.
368 to migrate the application to the new SDK, compile it using the platform
Dolder_releases.jd378 SDKs, you must migrate it to the Android 1.0 SDK (or later release) before you
/frameworks/base/docs/html/google/play/billing/v2/
Dbilling_reference.jd10 still using the Version 2 API, you must <strong>migrate to the Version 3 API
16 We strongly encourage and recommend you migrate your apps to use Version 3
Dbilling_subscriptions.jd10 still using the Version 2 API, you must <strong>migrate to the Version 3 API
16 We strongly encourage and recommend you migrate your apps to use Version 3
Dapi.jd10 still using the Version 2 API, you must <strong>migrate to the Version 3 API
16 We strongly encourage and recommend you migrate your apps to use Version 3
Dbilling_integrate.jd10 still using the Version 2 API, you must <strong>migrate to the Version 3 API
16 We strongly encourage and recommend you migrate your apps to use Version 3
/frameworks/base/docs/html/tools/help/
Dadt.jd42 for Android, so you should migrate to Android Studio to receive all the
44 see <a href="/sdk/installing/migrate.html">Migrating to Android
/frameworks/base/docs/html/guide/webapps/
Dmigrating.jd222 property is no longer supported and you should migrate to using standard solutions with
/frameworks/base/docs/html/google/auth/
Dapi-client.jd56 …ommon/GooglePlayServicesClient.html">{@code GooglePlayServicesClient}</a>, you should migrate to <a
/frameworks/base/docs/html/tools/sdk/
Declipse-adt.jd26 for Android, so you should migrate to Android Studio to receive all the
28 see <a href="/sdk/installing/migrate.html">Migrating to Android
376 Studio is the preferred way to migrate existing projects to Gradle.</li>
/frameworks/base/docs/html/training/articles/
Dsmp.jd1021 critical section. Put another way, you can migrate code “downward” across an
1233 migrate code into a “synchronized” block. One practical consequence: you must
1410 the code, but that won’t help, because it’s okay to migrate code upward &mdash;

12