Google I/O 2008 - Inside the Android Application Framework
Why Stack Overflow recommends it
Stack Overflow users link it when explaining how Android works under the hood, such as the UI thread event loop, inflater and context, and how apps are started, and they note it is a legacy talk that still gives useful historical context.
Recommended by 4 people across 4 different months, 2012 to 2021.
What it is
A Google I/O 2008 session in which Dan Morrill of Google walks through the internals of the Android application framework. It covers how the framework is put together, including the event loop built on Looper and Message Queue, and how applications run on top of it.
Cited in 1 Wikipedia article, including Apk (file format).
What people said
Strong rec Behnam · 2014-03 · Stack Overflow · on “How to use findViewById in custom class? (Android)”
No you don't need to extend Activity. Whatever you are doing, just stop for a minute. Because you need to learn a few lessons on Android Application Framework, which contains details that you need in this specific case: Inflater Service and Context . You can search and there are plenty of resources on Android Developer [LINK] website. Looks like you are at the beginning of the road, and to be frank, the best place to start is watching Inside Android Application Framework [this video] on Google IO 2008. Go and devour that video. I wish I had seen it before beginning Android application development.
Recommends user827992 · 2012-07 · Stack Overflow · on “Java project won't compile to a JAR correctly for Android”
@JoeSimpson I want to help, but you are keeping to go farward in the wrong direction, you have an application that does not works and you are still convinced, have a look at this [this video] if a talk from an engineer from the Android team does not convince you i don't know what can.
Recommends kamituel · 2013-07 · Stack Overflow · on “How do android's Event Listeners work?”
Internally, Android is running an event loop to handle UI events. For a nice diagram, see a third slide of this presentation [LINK] . This thread is being used to dispatch system calls to the UI elements: The system does not create a separate thread for each instance of a component. All components that run in the same process are instantiated in the UI thread, and system calls to each component are dispatched from that thread. (source: Processes and Threads [LINK] ) Have a look at a Inside the Android Application Framework video [this video] from Google I/O 2008. It has the nice explanation of the event loop (consisting of Looper and Message Queue). The interesting stuff starts at around 26m into
Recommends Morrison Chang · 2021-03 · Stack Overflow · on “Which component passes the events and intents to our application if not zygote?”
Legacy videos but provides historical context for when Android started: Google I/O 2008 - Inside the Android Application Framework [this video] and Google I/O 2008 - Anatomy and Physiology of an Android [LINK] . New stuff like ART can be found in more recent Google IO videos and [LINK]
Cites axis · 2012-10 · Stack Overflow · on “Other VM than Dalvik possible for Android Applications”
Yes, you can even add a support for C# in theory, meaning that you can add a CLR/CLI support, or whatever language or VM you like. All the Android components are really modular and the entire OS is customizable, the problem is that this requires a lot of money, time, know-how and most-likely, patent-trolling. click me for a youtube reply [this video] this is from an official talk about Android.