Androidology - Part 1 of 3 - Architecture Overview

Back


Part 1 of 3 in an overview series on the Android platform. In this segment, Mike gives an overview of the system architecture.

Channel: Science & Technology
Uploaded: November 11, 2007 at 8:58 pm
Author: Google

Length: 00:12:41
Rating: 4.70
Views: 183278

Tags: android mobile development

Embed Code:


Video Comments:
doctorcortex (November 27, 2008 at 7:21 am)
DONT READ!

in 1964 13 year old Elisa Johnson was raped and murdered in North Carolina, her body was found with multiple stab wounds, and now that you've read this, every night she will come to your house and hang from your closet with glowing red eyes, the only way to stop this is to post this to 10 other videos. SORRY I DIDNT WANT HER IN MY ROOM :S makr as spam.. tbh i just dont want her there...
babylon2233 (October 17, 2008 at 10:04 am)
So, we can build native apps on android ha? Who tell ya?
therrydicule (October 17, 2008 at 4:55 pm)
Yes, we can... It's a bit more complicated then on Windows or a normal "unix", due to some technicalities, but we can do that.

Who tell me? A, common: When you know how it's work a bit, you know that.
babylon2233 (October 22, 2008 at 3:35 am)
I think you mean writing a native linux application. So, you're wrong because Android is Linux + Dalvik + ... ~ Dalvik itself is a linux software and not an android apps.Every sing Android apps will always written in java unless Google modify the architecture of Android. I know how Android works. And I wonder if you even know what Android is all about.
therrydicule (October 22, 2008 at 3:34 pm)
I take android as a full operating system that include a kernel and some abi and api. Not just a kernel, with is linux anyways...

Since we could write native application for linux, we could for android with some modification...
I said we could write some native application for the OS, but I did not specified the level of abstraction and neither if we should add some API and libraries... For me, that technicalities. Because if I talk about this, a lot of 2guy" will not understand what I mean ;)
babylon2233 (October 23, 2008 at 2:13 am)
Basically, when you want to write a linux software what you need is libc. But you can't use that java classes to use with your native application. Let say you want to write an openGL apps, you will need the related library. That library is not available with android. What android have is just a libc. That's clear. Because android is jvm on top of linux which mean if you write native apps that somehow run on android it is not an android apps but instead a linux apps.
babylon2233 (October 23, 2008 at 2:14 am)
Then you might want to tell me the technicalities that you mean. If you don't mind just explain about those API and abstraction level. I hope you get it right.
therrydicule (October 23, 2008 at 4:54 pm)
Ok: For short, I been specific to android.

Over the hardware and "bios" you have a monolithic kernel call linux. Alone, the kernel only some management, drive the hardware, work some file system.

To work, they add some libraries, then api and over all this you run application.

You could add extra-libraries&api&application in this order.

It's a kind of hacking ;) You need a cross-compiler,a debuger, to modified the G.U.I.
But little portabilities for this "new" specific application.
babylon2233 (October 24, 2008 at 7:21 am)
So, the conclusion:

Android apps will always Java/JVM-based. That's clear because all android apps run on the Dalvik(which is a JVM). Unless you want to modify the system. For your info, libary isn't necessary as you can simply write a linux/BSD/blabla application by only using system calls. Library just making your work easier.
therrydicule (October 24, 2008 at 12:00 pm)
I know that, I just feel is hard for nothing to use system calls... Specially when portabilities need. But is possible, you are right.
What I just mean it is possible, with some modification. But it don't mean programmer have to: Java is great when goodly use.