Home
last modified time | relevance | path

Searched refs:why (Results 1 – 25 of 66) sorted by relevance

123

/frameworks/base/packages/SystemUI/src/com/android/systemui/doze/
DDozeLog.java142 public static void traceScreenOff(int why) { in traceScreenOff() argument
144 log("screenOff why=" + why); in traceScreenOff()
254 public void onFinishedGoingToSleep(int why) {
255 traceScreenOff(why);
/frameworks/base/packages/Keyguard/src/com/android/keyguard/
DKeyguardUpdateMonitorCallback.java159 public void onStartedGoingToSleep(int why) { } in onStartedGoingToSleep() argument
167 public void onFinishedGoingToSleep(int why) { } in onFinishedGoingToSleep() argument
DKeyguardMessageArea.java64 public void onFinishedGoingToSleep(int why) {
DKeyguardStatusView.java74 public void onFinishedGoingToSleep(int why) {
DKeyguardUpdateMonitor.java1697 public void dispatchStartedGoingToSleep(int why) { in dispatchStartedGoingToSleep() argument
1698 mHandler.sendMessage(mHandler.obtainMessage(MSG_STARTED_GOING_TO_SLEEP, why, 0)); in dispatchStartedGoingToSleep()
1701 public void dispatchFinishedGoingToSleep(int why) { in dispatchFinishedGoingToSleep() argument
1705 mHandler.sendMessage(mHandler.obtainMessage(MSG_FINISHED_GOING_TO_SLEEP, why, 0)); in dispatchFinishedGoingToSleep()
DCarrierText.java61 public void onFinishedGoingToSleep(int why) {
/frameworks/base/services/core/java/com/android/server/policy/keyguard/
DKeyguardServiceDelegate.java309 public void onStartedGoingToSleep(int why) { in onStartedGoingToSleep() argument
311 mKeyguardService.onStartedGoingToSleep(why); in onStartedGoingToSleep()
313 mKeyguardState.offReason = why; in onStartedGoingToSleep()
317 public void onFinishedGoingToSleep(int why, boolean cameraGestureTriggered) { in onFinishedGoingToSleep() argument
319 mKeyguardService.onFinishedGoingToSleep(why, cameraGestureTriggered); in onFinishedGoingToSleep()
/frameworks/base/services/core/java/com/android/server/power/
DNotifier.java417 final int why = translateOffReason(mInteractiveChangeReason); in handleEarlyInteractiveChange() local
421 mPolicy.startedGoingToSleep(why); in handleEarlyInteractiveChange()
457 final int why = translateOffReason(mInteractiveChangeReason); in handleLateInteractiveChange() local
461 EventLog.writeEvent(EventLogTags.POWER_SCREEN_STATE, 0, why, 0, 0); in handleLateInteractiveChange()
462 mPolicy.finishedGoingToSleep(why); in handleLateInteractiveChange()
/frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/phone/
DFingerprintUnlockController.java234 public void onStartedGoingToSleep(int why) { in onStartedGoingToSleep() argument
239 public void onFinishedGoingToSleep(int why) { in onFinishedGoingToSleep() argument
/frameworks/base/docs/html/training/articles/
Duser-data-permissions.jd86 request, be clear about what you’re accessing, and why, so users can make
121 more important to provide detailed explanation to the user as to why you’re
134 explanation of why you need the permission for your app to work properly. You
306 unless there is a clear user-facing reason why the app needs those permissions.
314 <p>You should inform your users about what you’re accessing and why. Research shows
316 why the app needs them. A user study showed that:</p>
338 <p>...when people know why an app is using something as sensitive as their location &mdash;
349 you're using, and why. For example:
372 know why you need the most sensitive permissions.
Dwear-permissions.jd89 <p>Your app requests permissions in context when it’s clear why the
172 <p>Your app should request permissions when it’s clear why they are needed in order to perform a
195 action, if it’s unclear why your app needs access to the requested permission
214 alt="When the need for the permission arises, the app explains why the permission is necessary."
246 alt="When requesting a permission on launch, the app can explain why it needs the permission."
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyguard/
DKeyguardViewMediator.java728 public void onStartedGoingToSleep(int why) { in onStartedGoingToSleep() argument
729 if (DEBUG) Log.d(TAG, "onStartedGoingToSleep(" + why + ")"); in onStartedGoingToSleep()
756 } else if ((why == WindowManagerPolicy.OFF_BECAUSE_OF_TIMEOUT && timeout > 0) in onStartedGoingToSleep()
757 || (why == WindowManagerPolicy.OFF_BECAUSE_OF_USER && !lockImmediately)) { in onStartedGoingToSleep()
768 KeyguardUpdateMonitor.getInstance(mContext).dispatchStartedGoingToSleep(why); in onStartedGoingToSleep()
772 public void onFinishedGoingToSleep(int why, boolean cameraGestureTriggered) { in onFinishedGoingToSleep() argument
773 if (DEBUG) Log.d(TAG, "onFinishedGoingToSleep(" + why + ")"); in onFinishedGoingToSleep()
811 KeyguardUpdateMonitor.getInstance(mContext).dispatchFinishedGoingToSleep(why); in onFinishedGoingToSleep()
/frameworks/base/core/java/android/view/
DWindowManagerPolicy.java1042 public void startedGoingToSleep(int why); in startedGoingToSleep() argument
1050 public void finishedGoingToSleep(int why); in finishedGoingToSleep() argument
/frameworks/base/docs/html/training/permissions/
Drequesting.jd153 <h3 id="explain">Explain why the app needs permissions</h3>
167 In some circumstances, you might want to help the user understand why your
170 the camera, but the user might not understand why the app wants access to the
181 permission request, that probably shows that the user doesn't understand why
257 requestPermissions()}, as described in <a href="#explain">Explain why the app
342 action. For example, your app might show a dialog explaining why it could not
Dbest-practices.jd167 why. In some cases, the user may find that puzzling. It's a good idea to
168 explain to the user why your app wants the permissions before calling
176 contain location information, and would be puzzled why their photography app
/frameworks/opt/net/wifi/tests/wifitests/
DREADME.md37 If you are trying to debug why tests are not doing what you expected, you can add android log
/frameworks/base/docs/html/guide/topics/resources/
Dmultilingual-support.jd101 The following examples explain why these practices improve performance and
142 why you should store French strings in {@code fr} rather than {@code fr_FR}
/frameworks/base/docs/html/training/graphics/opengl/
Dindex.jd60 <dd>Learn how to define shapes and why you need to know about faces and winding.</dd>
/frameworks/base/docs/html/about/versions/marshmallow/
Dandroid-6.0-testing.jd49 well as better context for understanding why the app is requesting a specific permission. Users
109 refactoring or compartmentalizing that flow to eliminate the dependency or make it clear why the
/frameworks/base/docs/html/work/
Ddevice-management-policy.jd119 to users why the application is requesting to be a device administrator, by specifying the
139 // explain to user why the application is requesting to be a device
/frameworks/base/docs/html/training/monitoring-device-state/
Dconnectivity-monitoring.jd36 download, why both waking the device to schedule the update at all?</p>
/frameworks/base/docs/html/training/displaying-bitmaps/
Dindex.jd48 <p>There are a number of reasons why loading bitmaps in your Android application is tricky:</p>
/frameworks/base/docs/html/guide/practices/app-design/
Dseamlessness.jd105 call) it's a pretty safe bet he did it on purpose. That's why you should avoid
199 <p>That's why you should always code your applications to minimize network
235 radio; that's why it's important to write your applications to do as little
/frameworks/base/docs/html/guide/practices/
Dseamlessness.jd106 call) it's a pretty safe bet he did it on purpose. That's why you should avoid
200 <p>That's why you should always code your applications to minimize network
236 radio; that's why it's important to write your applications to do as little
/frameworks/base/docs/html/distribute/analyze/
Dgoogle-services.jd44 Users are different, so why force them all to have the same experience? Using

123