/frameworks/base/core/java/android/database/sqlite/ |
D | SQLiteSession.java | 345 Transaction transaction = obtainTransaction(transactionMode, transactionListener); in beginTransactionUnchecked() local 346 transaction.mParent = mTransactionStack; in beginTransactionUnchecked() 347 mTransactionStack = transaction; in beginTransactionUnchecked() 936 Transaction transaction = mTransactionPool; in obtainTransaction() local 937 if (transaction != null) { in obtainTransaction() 938 mTransactionPool = transaction.mParent; in obtainTransaction() 939 transaction.mParent = null; in obtainTransaction() 940 transaction.mMarkedSuccessful = false; in obtainTransaction() 941 transaction.mChildFailed = false; in obtainTransaction() 943 transaction = new Transaction(); in obtainTransaction() [all …]
|
/frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/reference/ |
D | ARM_DELIVERY.TXT | 1 The contents of this transaction was created by Hedley Francis 10 quoting transaction reference <97412>. 21 This transaction contains deliverables which are designated as being of 47 In addition to the data versions listed above, this transaction contains 54 files included in this transaction, together with their checksums.
|
/frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/arm_neon/ |
D | ARM_DELIVERY.TXT | 1 The contents of this transaction was created by Hedley Francis 10 quoting transaction reference <97414>. 21 This transaction contains deliverables which are designated as being of 47 In addition to the data versions listed above, this transaction contains 54 files included in this transaction, together with their checksums.
|
/frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/arm11/ |
D | ARM_DELIVERY.TXT | 1 The contents of this transaction was created by Hedley Francis 10 quoting transaction reference <97413>. 21 This transaction contains deliverables which are designated as being of 47 In addition to the data versions listed above, this transaction contains 54 files included in this transaction, together with their checksums.
|
/frameworks/base/docs/html/training/basics/fragments/ |
D | fragment-ui.jd | 66 <p>To perform a transaction such as add or 104 <p>You can perform multiple fragment transaction for the activity using the same {@link 164 <p class="note"><strong>Note:</strong> When you remove or replace a fragment and add the transaction 166 back to restore the fragment, it restarts. If you <em>do not</em> add the transaction to the back 178 FragmentTransaction transaction = getSupportFragmentManager().beginTransaction(); 181 // and add the transaction to the back stack so the user can navigate back 182 transaction.replace(R.id.fragment_container, newFragment); 183 transaction.addToBackStack(null); 185 // Commit the transaction 186 transaction.commit(); [all …]
|
D | communicating.jd | 158 FragmentTransaction transaction = getSupportFragmentManager().beginTransaction(); 161 // and add the transaction to the back stack so the user can navigate back 162 transaction.replace(R.id.fragment_container, newFragment); 163 transaction.addToBackStack(null); 165 // Commit the transaction 166 transaction.commit();
|
/frameworks/base/core/java/android/preference/ |
D | PreferenceActivity.java | 1126 FragmentTransaction transaction = getFragmentManager().beginTransaction(); in switchToHeaderInner() local 1127 transaction.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_FADE); in switchToHeaderInner() 1128 transaction.replace(com.android.internal.R.id.prefs, f); in switchToHeaderInner() 1129 transaction.commitAllowingStateLoss(); in switchToHeaderInner() 1216 FragmentTransaction transaction = getFragmentManager().beginTransaction(); in startPreferenceFragment() local 1217 transaction.replace(com.android.internal.R.id.prefs, fragment); in startPreferenceFragment() 1219 transaction.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_OPEN); in startPreferenceFragment() 1220 transaction.addToBackStack(BACK_STACK_PREFS); in startPreferenceFragment() 1222 transaction.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_FADE); in startPreferenceFragment() 1224 transaction.commitAllowingStateLoss(); in startPreferenceFragment() [all …]
|
/frameworks/base/voip/java/com/android/server/sip/ |
D | SipHelper.java | 339 ServerTransaction transaction = event.getServerTransaction(); in getServerTransaction() local 340 if (transaction == null) { in getServerTransaction() 344 return transaction; in getServerTransaction() 355 ServerTransaction transaction = getServerTransaction(event); in sendRinging() local 364 transaction.sendResponse(response); in sendRinging() 365 return transaction; in sendRinging() 521 public static String getCallId(Transaction transaction) { in getCallId() argument 522 return ((transaction != null) ? getCallId(transaction.getRequest()) in getCallId()
|
D | SipSessionGroup.java | 424 ISipSessionListener listener, ServerTransaction transaction, in createNewSession() argument 427 newSession.mServerTransaction = transaction; in createNewSession() 853 private String toString(Transaction transaction) { in toString() argument 854 if (transaction == null) return "null"; in toString() 855 Request request = transaction.getRequest(); in toString() 856 Dialog dialog = transaction.getDialog(); in toString() 859 cseq.getSeqNumber(), transaction.getState(), in toString()
|
/frameworks/base/docs/html/training/implementing-navigation/ |
D | temporal.jd | 48 // Add this transaction to the back stack and commit. 53 … pops the most recent transaction off the back stack and performs the reverse action (e.g., removi… 55 … the transaction. You should update your user interface after the fragment manager back stack chan…
|
/frameworks/base/docs/html/guide/google/play/billing/ |
D | billing_overview.jd | 44 product. The service then handles all of the checkout details for the transaction, including 45 requesting and validating the form of payment and processing the financial transaction. When the 74 …ed per user account" purchase type, Google Play permanently stores the transaction information for… 78 …transaction information stored on Google Play. This means that you cannot later query Google Play … 107 transaction history or perform various in-app billing security tasks, such as signature 149 detailed transaction information. The following section describes the basic request-response 184 an item in your application. Google Play then handles the financial transaction by displaying 189 a requested purchase is billed successfully or when a user cancels a transaction during 192 transaction information to retrieve.</p> 200 <p>This request retrieves a user's transaction status for <a [all …]
|
D | billing_integrate.jd | 60 integrity of the transaction messages that are sent by Google Play.</li> 190 <p>This enables the application to verify the signature of the transaction information that is 480 <li><code>GET_PURCHASE_INFORMATION</code>—retrieves transaction information for a purchase 482 <li><code>CONFIRM_NOTIFICATIONS</code>—acknowledges that you received the transaction 484 <li><code>RESTORE_TRANSACTIONS</code>—retrieves a user's transaction history for <a 668 <p>Next, when the requested transaction changes state (for example, the purchase is successfully 671 use to retrieve the transaction details for the <code>REQUEST_PURCHASE</code> request.</p> 680 message until you receive an <code>IN_APP_NOTIFY</code> message for the transaction. While the 681 transaction is pending, the Google Play checkout UI displays an "Authorizing purchase..." 683 this notification as your primary means of conveying transaction status to users. Instead, we [all …]
|
D | billing_reference.jd | 181 to verify the integrity of transaction responses form Google Play.</td> 200 transaction information for an order. You can use this key to send supplemental information with 218 an item in your application. Google Play then handles the financial transaction by displaying 223 occur when a purchase request is billed successfully or when a user cancels a transaction during 226 transaction information to retrieve.</p> 235 <p>This request retrieves a user's transaction status for managed purchases (see <a 238 retrieve a user's transaction status, which is usually only when your application is reinstalled 352 transaction information is contained in a JSON string. The JSON string is signed and the signature 397 <td>A unique order identifier for the transaction. This corresponds to the Google Wallet Order
|
D | index.jd | 57 familiar purchase flow (see figure 1). Also, the transaction fee for in-app 58 purchases is the same as the transaction fee for application purchases
|
D | billing_subscriptions.jd | 308 transaction fee for subscriptions, just as for other in-app purchases, is the 309 same as the transaction fee for application purchases (30%).</p> 312 Billing to handle the transaction and may not provide links to a purchase flow 407 can retrieve the purchase token and other transaction details by initiating a 524 transaction.. 614 <p>Your app can store the restored purchase state and other transaction details
|
D | billing_admin.jd | 401 is managed per user account, Google Play permanently stores the transaction information for each 420 <p>Items that are unmanaged do not have their transaction information stored on Google Play, 421 which means you cannot query Google Play to retrieve transaction information for items whose 422 purchase type is listed as unmanaged. You are responsible for managing the transaction information
|
/frameworks/support/v4/java/android/support/v4/app/ |
D | DialogFragment.java | 139 public int show(FragmentTransaction transaction, String tag) { in show() argument 142 transaction.add(this, tag); in show() 144 mBackStackId = transaction.commit(); in show()
|
/frameworks/base/core/java/android/app/ |
D | DialogFragment.java | 242 public int show(FragmentTransaction transaction, String tag) { in show() argument 245 transaction.add(this, tag); in show() 247 mBackStackId = transaction.commit(); in show()
|
/frameworks/base/docs/html/guide/components/ |
D | fragments.jd | 78 fragment transaction, you can also add it to a back stack that's managed by the 79 activity—each back stack entry in the activity is a record of the fragment transaction that 80 occurred. The back stack allows the user to reverse a fragment transaction (navigate backwards), 418 commit to the activity is called a transaction and you can perform one using APIs in {@link 419 android.app.FragmentTransaction}. You can also save each transaction to a back stack managed by the 431 <p>Each transaction is a set of changes that you want to perform at the same time. You can set 432 up all the changes you want to perform for a given transaction using methods such as {@link 434 and {@link android.app.FragmentTransaction#replace replace()}. Then, to apply the transaction 440 android.app.FragmentTransaction#addToBackStack addToBackStack()}, in order to add the transaction 448 // Create new fragment and transaction [all …]
|
/frameworks/base/services/java/com/android/server/pm/ |
D | Installer.java | 148 private synchronized String transaction(String cmd) { in transaction() method in Installer 183 String res = transaction(cmd); in execute() 353 String s = transaction(builder.toString()); in getSizeInfo()
|
/frameworks/base/docs/html/tools/testing/ |
D | what_to_test.jd | 37 current transaction. 49 transaction state, you should also test that the application updates itself to respond
|
/frameworks/native/libs/gui/ |
D | SurfaceComposerClient.cpp | 143 Vector<ComposerState> transaction; in closeGlobalTransactionImpl() local 149 transaction = mStates; in closeGlobalTransactionImpl() 161 sm->setTransactionState(transaction, orientation, flags); in closeGlobalTransactionImpl()
|
/frameworks/base/docs/html/distribute/googleplay/about/ |
D | monetizing.jd | 25 and complete the transaction.</p> 153 transaction.</p>
|
/frameworks/av/media/mtp/ |
D | MtpServer.cpp | 169 MtpTransactionID transaction = mRequest.getTransactionID(); in run() local 198 mData.setTransactionID(transaction); in run() 212 mResponse.setTransactionID(transaction); in run()
|
/frameworks/base/docs/html/guide/faq/ |
D | framework.jd | 45 separate pool of transaction threads in each process to dispatch all
|