Game:

Eclipse --- Defending the motherland (2016)

Duration: 0:00

44 views

1

Android is a widely used operating system for mobile devices and has a reputation for being one of the most secure mobile operating systems available. There are several reasons why Android can be considered a production-ready operating system for different types of embedded systems. Android has several built-in security features, such as encryption, app sandboxing, memory management, support for a complete chain of trust, implementation of a Trusted Execution Environment (TEE), and more. All these features came along over many years and updates in the Android Open Source Project (AOSP), and today, its maturity goes way beyond the great graphical user interface and user interaction that initially attracted many embedded developers. For this reason, Android is a truly excellent option for embedded systems such as IoT and edge devices. Indeed, Android is gaining traction among different industries, and today, its integration with existing open-source projects is an actual need to avoid reinventing the wheel. This premise applies, of course, to the Eclipse IoT ecosystem, which provides today great technologies for products and services. The Android framework is mainly written in Java, and it uses extensive Java Native Interface (JNI). Its SDK allows developers to write applications in Java and Kotlin. So, the question about using existing Eclipse Java project code or how to interact with Eclipse IoT cloud services from Android-based IoT devices is more than technical speculation. However, the Android virtual machine (DVK) is different from the standard JVM, and the native runtime ART differs from the traditional JVM runtime. This translates into the need for a different bytecode (DEX) with respect to the JVM. At a higher level, the DVK executable is an APK while the JVM is a JAR, and Android libraries are AAR and not a simple JAR. How do these differences, which have a lot of common foundations, impact adopting a specific non-Android code base? How do we approach differences at the build-build system level to finally have our artifacts compiled and assembled? In this session, we explore strategies and approaches we could adopt when we need to port the code base of an existing Eclipse project that fits our purposes. We start with an introduction to the Android Platform architecture to understand the foundation of the Operating System and the anatomy of an Android application. Moving forward, we look at the boundary conditions for successfully porting the Eclipse code. We analyze the structure and the dependencies of some popular Eclipse IoT projects that make sense to run on our embedded Android devices, such as Eclipse Paho, Eclipse Hara, and Eclipse Leshan.

Other Statistics