IT. Expert System.

Android Reference

UpdateLock


android.os

Class UpdateLock



  • public class UpdateLock
    extends Object
    Advisory wakelock-like mechanism by which processes that should not be interrupted for OTA/update purposes can so advise the OS. This is particularly relevant for headless or kiosk-like operation.
    • Field Summary

      Fields
      Modifier and Type Field and Description
      static String NOW_IS_CONVENIENT
      Boolean Intent extra on the UPDATE_LOCK_CHANGED sticky broadcast, indicating whether now is an appropriate time to interrupt device activity with an update operation.
      static String TIMESTAMP
      Long Intent extra on the UPDATE_LOCK_CHANGED sticky broadcast, marking the wall-clock time [in UTC] at which the broadcast was sent.
      static String UPDATE_LOCK_CHANGED
      Broadcast Intent action sent when the global update lock state changes, i.e.
    • Constructor Summary

      Constructors
      Constructor and Description
      UpdateLock(String tag)
      Construct an UpdateLock instance.
    • Field Detail

      • UPDATE_LOCK_CHANGED

        public static final String UPDATE_LOCK_CHANGED
        Broadcast Intent action sent when the global update lock state changes, i.e. when the first locker acquires an update lock, or when the last locker releases theirs. The broadcast is sticky but is sent only to registered receivers.
        See Also:
        Constant Field Values
      • NOW_IS_CONVENIENT

        public static final String NOW_IS_CONVENIENT
        Boolean Intent extra on the UPDATE_LOCK_CHANGED sticky broadcast, indicating whether now is an appropriate time to interrupt device activity with an update operation. True means that updates are okay right now; false indicates that perhaps later would be a better time.
        See Also:
        Constant Field Values
      • TIMESTAMP

        public static final String TIMESTAMP
        Long Intent extra on the UPDATE_LOCK_CHANGED sticky broadcast, marking the wall-clock time [in UTC] at which the broadcast was sent. Note that this is in the System.currentTimeMillis() time base, which may be non-monotonic especially around reboots.
        See Also:
        Constant Field Values
    • Constructor Detail

      • UpdateLock

        public UpdateLock(String tag)
        Construct an UpdateLock instance.
        Parameters:
        tag - An arbitrary string used to identify this lock instance in dump output.
    • Method Detail

      • setReferenceCounted

        public void setReferenceCounted(boolean isRefCounted)
        Change the refcount behavior of this update lock.
      • isHeld

        public boolean isHeld()
        Is this lock currently held?
      • acquire

        public void acquire()
        Acquire an update lock.
      • release

        public void release()
        Release this update lock.
      • finalize

        protected void finalize()
                         throws Throwable
        Description copied from class: Object
        Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

        Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

        If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

        Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

        Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.

        Overrides:
        finalize in class Object
        Throws:
        Throwable


Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

License.
All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 11820 / 248549937. Delta: 0.02793 с