Android is powered by the Linux kernel and the Dalvik (Java) Virtual Machine to support multi-tasking operations. This course covers how Android utilizes processes and threads, and will teach you about the numerous options available to developers for multi-tasking operations as well as how to leverage special platform capabilities.
At its core, Android is built to take advantage of multi-tasking operations, be it from separate applications or different operations within the same app. In addition to providing built in support for working with threads, Android provides a solid framework for inter-process communication and puts a twist on the way app processes are used. In this course you will learn about the way Android utilizes processes, how to take advantage of special app sharing features and explore the variety of ways in which threads can be used.
Larry Schiefer is the CTO and co-founder of HiQES, a mobile, embedded and application software development service company. He specializes in designing and developing device drivers, kernel software, BSP, and applications for Android, Linux, Windows, Windows Embedded, and various RTOS environments.
Android Processes and Threads (Sharing User IDs and Processes) Welcome to the Application Process and ID Sharing module of the Android Processes and Threads Pluralsight training course. My name is Larry Schiefer and in this module, we will be discussing a unique feature available in Android. The ability to have separate application packages, their user identity and a process. In our last module, we talked about how Android Processes are sandboxed with the unique user identity, a unique file system space, but at the same time are built to interact with each other, using a variety of IPC mechanisms. And at this point, you may be wondering, what if I need something different, something that this paradigm does not appear to support? I've special requirements for data and/or resource reuse between multiple apps of mine. Is there a way to do this in Android? Further, I have some related apps that share some common component or components, cross process work even with sharing memory rather than copying has a performance cost associated with it. Is there some way this can be made more efficient? In short, yes. These are both possible via existing functionality made available in the platform. This is the purpose of this module. Demonstrate the functionality built into the platform, which will allow multiple apps to share a user ID and possibly share a process.