Can Android Run on Time? Extending and Measuring the Android Platform's Timeliness

Yan, Yin; Gokul, Girish; Dantu, Karthik; Ko, Steven Y.; Ziarek, Lukasz; Vítek, Jan

doi:10.1145/3289257

Cited by 4 publications

(2 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As the current trend of developing main controllers based on embedded systems becomes a paradigm, there is an increasing demand for Android in industrial applications. Researchers have evaluated and proposed various solutions to enable its use as a platform for safety-critical and real-time applications [11][12][13][14][27][28][29]. In this section, we provide the complete development details of a real-time environment employing Xenomai as the dual-kernel approach of real-time Linux and the implementation of an open-source EtherCAT master for our own developed embedded platform, namely JECS-600ITX.…”

Section: Android-based Industrial Controller For Safety-critical Applmentioning

confidence: 99%

“…This provides a deterministic response of Android applications by replacing both the kernel and runtime with their respective real-time alternatives. RTDroid was tested mainly for real-time sound processing, and the measured sound latency performance is presented in their extended work [12]. However, its extendibility to industrial applications is moot as most industrial software tools and libraries are designed for the standard Linux kernel.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Safe and Policy Oriented Secure Android-Based Industrial Embedded Control System

Delgado

Park

Lee³

et al. 2020

Applied Sciences

View full text Add to dashboard Cite

Android is gaining popularity as the operating system of embedded systems and recent demands of its application on industrial control are steadily increasing. However, its feasibility is still in question due to two major drawbacks: safety and security. In particular, ensuring the safe operation of industrial control systems requires the system to be governed by stringent temporal constraints and should satisfy real-time requirements. In this sense, we explore the real-time characteristics of Xenomai to guarantee strict temporal deadlines, and provide a viable method integrating Android processes to real-time tasks. Security is another issue that affects safety due to the increased connectivity in industrial systems provoking a higher risk of cyber and hardware attacks. Herein, we adopted a hardware copy protection chip and enforced administrative security policies in the booting process and the Android application layer. These policies ensure that the developed system is protected from physical tampering and unwanted Android applications. The articulacy of the administrative policies is demonstrated through experiments. The developed embedded system is connected to an industrial EtherCAT motion device network exhibiting operability on an actual industrial application. Real-time performance was evaluated in terms of schedulability and responsiveness, which are critical in determining the safety and reliability of the control system.

show abstract

Section: Android-based Industrial Controller For Safety-critical Applmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Safe and Policy Oriented Secure Android-Based Industrial Embedded Control System

Delgado

Park

Lee³

et al. 2020

Applied Sciences

View full text Add to dashboard Cite

show abstract

Non-Blocking Synchronization Between Real-Time and Non-Real-Time Applications

2020

View full text Add to dashboard Cite

Real-time systems where applications with timing requirements coexist with applications without timing constraints are increasingly common. Furthermore, the processors used in desktops, smart phones or embedded devices are mostly multi-core, allowing the execution of applications in parallel. This article presents a set of non-blocking synchronization mechanisms to share data between real-time and non-real-time applications executing in different cores of a shared memory multi-core system. Four typical producer/consumer scenarios have been explored; a) shared data object with real-time reader, b) shared data object with real-time writer, c) shared queue with real-time writer, and d) shared queue with real-time reader. For these scenarios we have developed different non-blocking protocols where the execution of the real-time application is always prioritized over the execution of the non-real-time part. In this way, the real-time applications never have to repeat their operations and, consequently, their execution times are bounded. Furthermore, to reduce the overhead caused by the copies of the information used in the non-blocking algorithms, we have imposed the limitation of a single real-time reader or a single real-time writer in the algorithms developed. Finally, we have evaluated the response times of the developed protocols on a multi-core device with the Android operating system.INDEX TERMS Android, multi-core, non-blocking synchronization, real-time, wait-free.

show abstract

iAware: Interaction Aware Task Scheduling for Reducing Resource Contention in Mobile Systems

Zheng,

Li,

Xiong

et al. 2023

ACM Trans. Embed. Comput. Syst.

View full text Add to dashboard Cite

To ensure the user experience of mobile systems, the foreground application can be differentiated to minimize the impact of background applications. However, this article observes that system services in the kernel and framework layer, instead of background applications, are now the major resource competitors. Specifically, these service tasks tend to be quiet when people rarely interact with the foreground application and active when interactions become frequent, and this high overlap of busy times leads to contention for resources. This article proposes iAware, an interaction-aware task scheduling framework in mobile systems. The key insight is to make use of the previously ignored idle period and schedule service tasks to run at that period. iAware quantify the interaction characteristic based on the screen touch event, and successfully stagger the periods of frequent user interactions. With iAware, service tasks tend to run when few interactions occur, for example, when the device’s screen is turned off, instead of when the user is frequently interacting with it. iAware is implemented on real smartphones. Experimental results show that the user experience is significantly improved with iAware. Compared to the state-of-the-art, the application launching speed and frame rate are enhanced by 38.89% and 7.97% separately, with no more than 1% additional battery consumption.

show abstract

Can Android Run on Time? Extending and Measuring the Android Platform's Timeliness

Cited by 4 publications

References 30 publications

Safe and Policy Oriented Secure Android-Based Industrial Embedded Control System

Safe and Policy Oriented Secure Android-Based Industrial Embedded Control System

Non-Blocking Synchronization Between Real-Time and Non-Real-Time Applications

iAware: Interaction Aware Task Scheduling for Reducing Resource Contention in Mobile Systems

Contact Info

Product

Resources

About