Part 1 of 3 in an general outlook array upon a Android platform. In this segment, Mike gives an general outlook of a complement architecture.
Androidology – Part 1 of 3 – Architecture Overview
Posted by admin on May 30, 2010, filed in Architecture Engineering and tagged Androidology, Architecture, Overview, Part. You can leave a response via the comment form below and follow any responses via the RSS feed.
This video was very useful… yes… useful… thank you Google…
PLEASE DON’T READ THIS you will die in seven days if you don’t post this comment on? at least 10 other videos in the next hour, if you do tomorow will be the best day of your life
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…
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.
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.
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.
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.
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.
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
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.
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.
So, we can build native apps on android ha? Who tell ya?
You could do that on every platform since the Comodore 64. That mean that every “pc” suck since we could do that (with source code), every mac suck, and every toaster with NetBSD suck, that the TI calculator suck…
So, I guest you’re post on a super nintendo with X-band… Shit we could build native application there to!!!
I think you’re wrong.
How do I make money off my application?
for real it’s based on Linux. WoW!!!
This gonna probably be one of the first and the largest Linux based system used by mass users.
OK
Gah, fanboys
fan of apple. are u kidding?
Android sucks because you can build a native apps.
they’re making history,
dex – ‘components’ – kernel.
with the dominating power of a google this will build a huge operatingsystem, not only for mobile gadgets
I can’t wait until fall when T-mobile offers there Android Tech. Phones, it will be the down fall of the iphone for sure, and you’ll be able to change out your own battery too!
I thought u’re annoyed so replied twice
obviously there was a posting error.
How many times u will tell this?
note the “handheld”