Home
last modified time | relevance | path

Searched refs:burn (Results 1 – 4 of 4) sorted by relevance

/frameworks/opt/bitmap/src/com/android/bitmap/util/
DInputStreamBuffer.java201 int burn = i - mFilled; in advanceTo() local
205 while (burn > 0) { in advanceTo()
206 final long burned = mInputStream.skip(burn); in advanceTo()
210 burn -= burned; in advanceTo()
227 mOffset = index - burn; in advanceTo()
/frameworks/opt/photoviewer/src/com/android/ex/photo/util/
DInputStreamBuffer.java201 int burn = i - mFilled; in advanceTo() local
205 while (burn > 0) { in advanceTo()
206 final long burned = mInputStream.skip(burn); in advanceTo()
210 burn -= burned; in advanceTo()
227 mOffset = index - burn; in advanceTo()
/frameworks/base/packages/SystemUI/docs/device-entry/
Ddoze.md5 …the UI should frequently shift its displayed contents in order to prevent burn-in. The recommended…
62 ## AOD burn-in and image retention
63 …e, AOD designs must take into consideration burn-in (leaving a permanent mark on the screen). Temp…
65 To prevent burn-in, it is recommended to often shift UI on the screen. [DozeUi][17] schedules a cal…
67 …SET'`) will update the burn-in translations of the views. For a general idea where burn-in may be …
/frameworks/base/packages/SystemUI/docs/
Dclock-plugins.md70 Clocks are high risk for battery consumption and screen burn-in because they modify the UI of AOD.
76 To prevent screen burn-in, clocks should not be composed of large solid blocks of color, and the
78 Software burn-in testing is a good starting point to assess the pixel shifting (clock movement)
85 difficult to define a threshold where burn-in will occur. It is, therefore, recommended to compare