Collectives™ on Stack Overflow
Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about Collectives
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about Teams
Want to improve this question?
Update the question so it focuses on one problem only by
editing this post
.
Closed
8 years ago
.
WakeLock is a mechanism to keep the device on, as written
here
and
here
It is used for example when you need to do things even when the device seems to be asleep, like downloading files from the internet.
Wakelocks should never be used unless you really need them. The reason is that they consume more battery, and if you have a bug that won't release them when needed, your app will keep consuming the battery of the device. There are even apps to detect such problematic apps (like "wakelock detector") .
Also, a small tip for people who just wish to let the screen stay on (as long as the app is shown): you don't need (and you shouldn't need) the wakeLock permission. Instead, you should just set "
android:keepScreenOn="true"
" on the layout of the current activity. More about this is talked about on the lecture
"Coding for Life -- Battery Life, That Is"
(presentation
here
)
–
You can use a wakelock for keeping the screen turned on - you can see an example in
this code
.
If you want more information, you have to specify your question.
–
–
–
A wake lock is a mechanism to indicate that your application needs to have the device stay on.
Any application using a
WakeLock
must request the
android.permission.WAKE_LOCK
permission in an
<uses-permission>
element of the application's manifest. Obtain a wake lock by calling
newWakeLock(int, String)
.