The document discusses building Android Open Source Project (AOSP) software. It describes fetching source code using repo, configuring the build, and building and flashing images to an Android device. Key steps include initializing repo, syncing sources, setting environment variables, choosing a target from the lunch menu, and using make to build binaries, images and flash the device.
A deep dive into Android OpenSource Project(AOSP)Siji Sunny
A deep dive into Android openSource project presented at
International Centre for Free and Open Source Software (ICFOSS), Kerala's OpenSource Mobile Computing Conference
In order to understand HAL layers of Android Framework, having Linux device driver knowledge is important. Hence Day-2 of the workshop focuses on the same.
Embedded Android System Development - Part II talks about Hardware Abstraction Layer (HAL). HAL is an interfacing layer through which Android service can place a request to device. Uses functions provided by Linux system to service the request from android framework. A C/C++ layer with purely vendor specific implementation. Packaged into modules (.so) file & loaded by Android system at appropriate time
Android Things is the latest attempt from Google to connect the dots between the cloud and devices by introducing an OS that is exclusively built for IoT devices. Initially announced as project Brillo, Android Things helps developers to build devices faster and enable them integrate with cloud services. This presentation traces the architectural aspects of Android Things by connecting it back with Embedded Linux, Embedded Android and Brillo.
A deep dive into Android OpenSource Project(AOSP)Siji Sunny
A deep dive into Android openSource project presented at
International Centre for Free and Open Source Software (ICFOSS), Kerala's OpenSource Mobile Computing Conference
In order to understand HAL layers of Android Framework, having Linux device driver knowledge is important. Hence Day-2 of the workshop focuses on the same.
Embedded Android System Development - Part II talks about Hardware Abstraction Layer (HAL). HAL is an interfacing layer through which Android service can place a request to device. Uses functions provided by Linux system to service the request from android framework. A C/C++ layer with purely vendor specific implementation. Packaged into modules (.so) file & loaded by Android system at appropriate time
Android Things is the latest attempt from Google to connect the dots between the cloud and devices by introducing an OS that is exclusively built for IoT devices. Initially announced as project Brillo, Android Things helps developers to build devices faster and enable them integrate with cloud services. This presentation traces the architectural aspects of Android Things by connecting it back with Embedded Linux, Embedded Android and Brillo.
For new age touch-based embedded devices, Android is becoming a popular OS going beyond mobile phones. With its roots from Embedded Linux, Android framework offers benefits in terms of rich libraries, open-source and multi-device support. Emertxe’s hands-on Embedded Android Training Course is designed to customize, build and deploy custom Embedded OS on ARM target. Rich set of projects will make your learning complete.
I have tried to present maximum detail on android booting sequence in a very abstract way. I hope it would be useful. If you find any correction needed please mention it on comments. Happy Coding :)
Connecting Android apps to Android Auto, Ford Sync and other OEM SDKs. Presentation explores the different options available in the world of Driveables.
Implementing generic JNI hardware control for Kotlin based app on AOSPCheng Wig
With the popularity of Android phones, along with the success in the consumer field, the industrial Android platform is getting more and more popular in Europe.
An industrial grade Android OS usually requires hardware control such as GPIO, I2C, PWM, etc., however device vendors implement these functions in different ways, some may even compromise Android security function. In this session, the presenter will introduce how to implement packaged JNI API from common libraries of Linux OS for hardware controlling for Kotlin based app while fully matching the security architecture of Android OS through AOSP 12 BSP and Android-Studio IDE.
Device Tree Overlay implementation on AOSP 9.0Cheng Wig
With the popularity of Android phones, along with the success in the consumer field, the industrial Android platform is also becoming more and more popular in Europe.
In this session, the presenter will share his experience of integrating AOSP 9.0 on multiple industrial grade platform with various hardware specifications, as well as demonstrate a real case of using the latest dtbo.img architecture to achieve separating the hardware specifications from the software definitions. With this additional abstract layer, the maintenance costs and upgrade complexity will be dramatically improved while fully matching the security architecture of AOSP.
There is a surge in number of sensors / devices that are getting connected under the umbrella of Internet-Of-Things (IoT). These devices need to be integrated into the Android system and accessed via applications, which is covered in the course. Our Android system development course curriculum over weekends with practicals ensures you learn all critical components to get started.
In dieser Session werfen wir einen Blick auf die Android Platform jenseits der Dalvik VM. Wir entdecken den Android Source Code und erklären wo sich interessante Beispiele und Referenzen für App-Entwickler sowie nützliche Tools verbergen. Ein High-Level Überblick über die Platform-Architektur und das Platform-Build-System runden die Session ab.
For new age touch-based embedded devices, Android is becoming a popular OS going beyond mobile phones. With its roots from Embedded Linux, Android framework offers benefits in terms of rich libraries, open-source and multi-device support. Emertxe’s hands-on Embedded Android Training Course is designed to customize, build and deploy custom Embedded OS on ARM target. Rich set of projects will make your learning complete.
I have tried to present maximum detail on android booting sequence in a very abstract way. I hope it would be useful. If you find any correction needed please mention it on comments. Happy Coding :)
Connecting Android apps to Android Auto, Ford Sync and other OEM SDKs. Presentation explores the different options available in the world of Driveables.
Implementing generic JNI hardware control for Kotlin based app on AOSPCheng Wig
With the popularity of Android phones, along with the success in the consumer field, the industrial Android platform is getting more and more popular in Europe.
An industrial grade Android OS usually requires hardware control such as GPIO, I2C, PWM, etc., however device vendors implement these functions in different ways, some may even compromise Android security function. In this session, the presenter will introduce how to implement packaged JNI API from common libraries of Linux OS for hardware controlling for Kotlin based app while fully matching the security architecture of Android OS through AOSP 12 BSP and Android-Studio IDE.
Device Tree Overlay implementation on AOSP 9.0Cheng Wig
With the popularity of Android phones, along with the success in the consumer field, the industrial Android platform is also becoming more and more popular in Europe.
In this session, the presenter will share his experience of integrating AOSP 9.0 on multiple industrial grade platform with various hardware specifications, as well as demonstrate a real case of using the latest dtbo.img architecture to achieve separating the hardware specifications from the software definitions. With this additional abstract layer, the maintenance costs and upgrade complexity will be dramatically improved while fully matching the security architecture of AOSP.
There is a surge in number of sensors / devices that are getting connected under the umbrella of Internet-Of-Things (IoT). These devices need to be integrated into the Android system and accessed via applications, which is covered in the course. Our Android system development course curriculum over weekends with practicals ensures you learn all critical components to get started.
In dieser Session werfen wir einen Blick auf die Android Platform jenseits der Dalvik VM. Wir entdecken den Android Source Code und erklären wo sich interessante Beispiele und Referenzen für App-Entwickler sowie nützliche Tools verbergen. Ein High-Level Überblick über die Platform-Architektur und das Platform-Build-System runden die Session ab.
An Overview of the IHK/McKernel Multi-kernel Operating SystemLinaro
By Balazs Gerofi, RIKEN Advanced Institute For Computational Science
RIKEN Advanced Institute for Computation Science is in charge of leading the development of Japan's next generation flagship supercomputer, the successor of the K. Part of this effort is to design and develop a system software stack that suits the needs of future extreme scale computing. In this talk, we focus on operating system (OS) requirements for HPC and discuss IHK/McKernel, a multi-kernel based operating system framework. IHK/McKernel runs Linux with a light-weight kernel (LWK) side-by-side on compute nodes with the primary motivation of providing scalable, consistent performance for large scale HPC simulations, but at the same time to retain a fully Linux compatible execution environment. We provide an overview of the project and discuss the status of its support for ARM architecture.
Balazs Gerofi Bio
Research Scientist at RIKEN Advanced Institute For Computational Science.
Email
bgerofi@riken.jp
For more info on The Linaro High Performance Computing (HPC) visit https://www.linaro.org/sig/hpc/
Alfresco Environment Validation and "Day Zero" ConfigurationAlfresco Software
This session will commence with the environmental checks that should be performed prior to the installation of Alfresco, and then describe the "day zero" configuration changes that should be made to ensure that the installed Alfresco instance is optimally configured.
Android Embedded - Smart Hubs als Schaltzentrale des IoTinovex GmbH
Viele IoT-Anwendungen fordern eine grafische Benutzerschnittstelle, um mit uns zu kommunizieren. Dies kann auf ganz klassischen Wegen wie Webseiten oder Apps erfolgen. Hardwarenahe Anwendungen fordern aber meist auch ein speziell abgestimmtes Human-Machine-Interface (HMI), zum Beispiel im Auto oder im Smart Home. Diese zentrale HMI-Hardware übernimmt häufig auch zentrale steuernde Aufgaben und integriert sich mit verschiedensten Protokollen und Komponenten. Setzt man Android auf einem Single Board Computer (SBC) in Verbindung mit einem Display- und Touchsensor ein, hat man eine ideale Kombination für diese Herausforderung. Wir zeigen, wie sich Android in das IoT eingliedert und welche Vorteile diese Lösung bietet.
Speaker: Dominik Helleberg, inovex
.NET Conf 2019 Tel-Aviv Israel
There are cases where bugs are discovered only after the product is shipped and used by the end-users. The main reason for these bugs that appear only in the production environment is the use of real user scenarios with real user data. Production debugging is about solving customer-facing issues that aren't easily reproducible in the development or testing environments. When it comes to a cloud-hosted application, production debugging becomes even harder. The code is running on multiple hosts, a business flow can span many services. A remote debugging session with the cloud is dangerous and may introduce side effects to the currently running software, such as performance degradation, interruption of service, and data correctness issues.
In this lecture, we will see how we can remote debug our cloud staging environment, and how we can use Visual Studio Snapshot debugger to set Snapshots and Log points in our production environment.
To get even more insights, the audience will see a revolutionary tool and approach for a collaborative production debugging – OzCode Debugging as a Service (DaaS), where the DevOps and the Dev team can solve production problems together!
You will learn:
1. The difficulties of debugging a modern cloud-hosted application
2. Methods and tools for capturing the state and debugging cloud-hosted services
[Hands-on 필수 준비 사항] 쇼핑몰 예제를 통한 Microservice 개발/배포 실습 - 황주필 부장 / 강인호 부장, 한국오라클Oracle Korea
클라우드 시대의 개발자 네트워킹의 장, Oracle Developer Meetup 그 네번째 모임의 핸즈온 실습을 위한 필수 준비 사항 슬라이드입니다.
: Polyglot 환경의 Microservice로 구성된 쇼핑몰 예제를 이용하여, Microservice의 개발과 운영에 대해 직접 체험할 수 있는 세션입니다. 서비스 개선 요구사항에 맞춰 서비스를 개발/변경해 보고, Kubernetes + istio 환경에 배포하는 실습을 진행합니다.
* 본 세션은 ‘입문자/초급자' 에게 적합한 세션입니다.
(1) Pick up one Android phone and discover its internals
(2) Learn how to select the "weapons" to fight with
Android system facilities
(3) Skipping Java parts, we focus on the native area:
dynamic linking, processes, debugger, memory
layout, IPC, and interactions with frameworks.
(4) It is not comprehensive to familarize Android. The
goal is to utilize Android platforms, which are the
popular and powerful development devices to us.
The slides from my Deployment Tactics talk at the ThinkVitamin Code Management online conference (http://thinkvitamin.com/online-conferences/code-manage-deploy/).
15. # source ./build/envsetup.sh
// include all existing vendorsetup.sh in ./device
// and define cmds
...
- lunch: lunch <product_name>-<build_variant>
- croot: Changes directory to the top of the tree.
- m: Makes from the top of the tree.
- mm* : Builds all of the modules in the current/suplied directory, with,
/without their dependencies.
- cgrep: Greps on all local C/C++ files.
- jgrep: Greps on all local Java files.
- resgrep: Greps on all local res/*.xml files.
- sepgrep: Greps on all loacal sepolicy files
...
PREPARE TO BUILD
Set env
16. PREPARE TO
BUILD
Prepare ingredient
vendorsetup.sh
Lunch entry point
in device/manufacturer/device
TYPE = eng | userdebug | release
AndroidProducts.mk
The first makefile
add_lunch_combo TARGETNAME-TYPE
PRODUCT_MAKEFILES = TARGETNAME.mk
38. AOSP PUZZLE
Were are missing blobs?
Download them from Google/Sony/...
https://developers.google.com/android/nexus/drivers
http://developer.sonymobile.com/knowledge-base/open-source/
Or get them from official working image
Distributed blobs are sometimes buggy
39. AOSP PUZZLE
Were are missing blobs?
Copy in /vendor + include in build system
inherited in device.mk
NEW : in vendor partition for some devices
42. The
Gapps
issue
NOT Open source
- gapps not distributed for everybody
- aosp apps != gapps
- Google Mobile Services are getting fat
AOSP PUZZLE
Base apps looks bad!
43. ANDROID CERTIFICATION
Google approve this build
API &
function
(auto)
CTS
software &
hardware
requirerments
CDD
API &
function
(manual)
CTS
verifier
final tests
Google
44. SUMMARY
What did he said?
# repo init ...
# repo sync
# [get binaries]
# source ./build/envsetup.sh
# lunch
# make -j42
# [unlock bootloader]
# fastboot flashall
46. COPYRIGHTS
#
# Copyright (C) 2013 The Android Open-Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
The following copyright have been stripped from all the
examples :