Abstract: Returning a runtime type loaded from an archive in a module system is disclosed. Operations include (a) identifying, by a class loader implemented in a runtime environment, an archived runtime type loaded into an archive from a module source; (b) identifying a particular package associated with the archived runtime type; (c) determining that the particular package is defined to a runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates; and (d) returning directly or indirectly, by the class loader, a runtime type loaded based on the archived runtime type from the archive.

Abstract: Returning a runtime type loaded from an archive in a module system is disclosed. Operations include (a) identifying, by a class loader implemented in a runtime environment, an archived runtime type loaded into an archive from a module source; (b) identifying a particular package associated with the archived runtime type; (c) determining that the particular package is defined to a runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates; and (d) returning directly or indirectly, by the class loader, a runtime type loaded based on the archived runtime type from the archive.

Abstract: Operations include (a) receiving a request to verify a first runtime type loaded based on a first runtime type reference; (b) identifying verification metadata comprising a stored assignable relationship between a second runtime type reference and a third runtime type reference; (c) determining whether an actual assignable relationship between a second runtime type and a third runtime type adheres to the stored assignable relationship between the second runtime type reference and the third runtime type reference; and (d) responsive at least to determining that the actual assignable relationship adheres to the stored assignable relationship, determining that the first runtime type is verified based on the verification metadata.

Abstract: Returning a runtime type loaded from an archive in a module system is disclosed. Operations include (a) identifying, by a class loader implemented in a runtime environment, an archived runtime type loaded into an archive from a module source; (b) identifying a particular package associated with the archived runtime type; (c) determining that the particular package is defined to a runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates; and (d) returning directly or indirectly, by the class loader, a runtime type loaded based on the archived runtime type from the archive.

Abstract: Operations include (a) receiving a request to verify a first runtime type loaded based on a first runtime type reference; (b) identifying verification metadata comprising a stored assignable relationship between a second runtime type reference and a third runtime type reference; (c) determining whether an actual assignable relationship between a second runtime type and a third runtime type adheres to the stored assignable relationship between the second runtime type reference and the third runtime type reference; and (d) responsive at least to determining that the actual assignable relationship adheres to the stored assignable relationship, determining that the first runtime type is verified based on the verification metadata.

Abstract: Operations include (a) receiving a request to verify a first runtime type loaded based on a first runtime type reference; (b) identifying verification metadata comprising a stored assignable relationship between a second runtime type reference and a third runtime type reference; (c) determining whether an actual assignable relationship between a second runtime type and a third runtime type adheres to the stored assignable relationship between the second runtime type reference and the third runtime type reference; and (d) responsive at least to determining that the actual assignable relationship adheres to the stored assignable relationship, determining that the first runtime type is verified based on the verification metadata.

Abstract: Returning a runtime type loaded from an archive in a module system is disclosed. Operations include (a) identifying, by a class loader implemented in a runtime environment, an archived runtime type loaded into an archive from a module source; (b) identifying a particular package associated with the archived runtime type; (c) determining that the particular package is defined to a runtime module that is defined to (i) the class loader or (ii) any class loader in the class loader hierarchy to which the class loader delegates; and (d) returning directly or indirectly, by the class loader, a runtime type loaded based on the archived runtime type from the archive.

Abstract: Operations include (a) receiving a request to verify a first runtime type loaded based on a first runtime type reference; (b) identifying verification metadata comprising a stored assignable relationship between a second runtime type reference and a third runtime type reference; (c) determining whether an actual assignable relationship between a second runtime type and a third runtime type adheres to the stored assignable relationship between the second runtime type reference and the third runtime type reference; and (d) responsive at least to determining that the actual assignable relationship adheres to the stored assignable relationship, determining that the first runtime type is verified based on the verification metadata.

Abstract: An apparatus and method for providing a user interface are provided. The method includes determining a status of the mobile terminal, and rendering a user interface using one of the software mode and the hardware mode based on the status of the mobile terminal. Accordingly, because a hardware mode provides a high quality user interface but requires more power as compared to the software mode, the mobile terminal is able to reduce power consumption by automatically switching to the software mode based on the status of the mobile terminal.

Abstract: A method, a non-transitory computer readable medium having instructions recorded therein for performing the method, and processing device for rendering an animation for a screen. The method includes rendering a frame of animation of a screen, attaching a Move Surfaces at BufferSwap (MSBS) command to at least one surface to be aligned with the frame of animation, swapping the buffer of the frame of animation, updating at least one of a size and a location of the at least one surface having an attached MSBS command, and composing a scene including the contents of the at least one surface of which the at least one of the size and the location has been updated.

Abstract: A method and device for adaptively determining processes to kill when a low memory situation is detected, and for adaptively determining processes to pre-launch, are disclosed. The method for determining processes to kill includes tracking statistics of application launching behaviors, predicting application behaviors under certain system states in accordance with the tracked statistics, detecting a certain system state, and, if the certain system state is detected, adaptively selecting an application loaded in a cache memory to kill in accordance with the predicted behaviors.

Abstract: A method, a non-transitory computer readable medium having instructions recorded therein for performing the method, and processing device for rendering an animation for a screen. The method includes rendering a frame of animation of a screen, attaching a Move Surfaces at BufferSwap (MSBS) command to at least one surface to be aligned with the frame of animation, swapping the buffer of the frame of animation, updating at least one of a size and a location of the at least one surface having an attached MSBS command, and composing a scene including the contents of the at least one surface of which the at least one of the size and the location has been updated.

Abstract: An apparatus and method for providing a user interface are provided. The method includes determining a status of the mobile terminal, and rendering a user interface using one of the software mode and the hardware mode based on the status of the mobile terminal. Accordingly, because a hardware mode provides a high quality user interface but requires more power as compared to the software mode, the mobile terminal is able to reduce power consumption by automatically switching to the software mode based on the status of the mobile terminal.

Abstract: Apparatus, methods and computer program products are disclosed to improve allocation of physical memory in a memory limited device when the amount of unallocated memory approaches a threshold. In this situation the disclosed technology will identify memory pages that have substantially the same content, identify the process-contexts that map to the identified memory pages, remap these process-contexts to one of the identical memory pages, recycle all of the other identical memory pages to increase the amount of unallocated memory, and conditions the process-contexts to appropriately trap accesses to the mapped page.