How to add a EFI bootloader to android

by gowtham gowda » Sat, 11 Apr 2009 11:49:09 GMT


Sponsored Links
 I want to use a EFI bootloader to start android on an intel atom
board. Can someone help me with this?
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. NOOBIE : PLEASE HELP

Hye All,


I am Computer Science Grad student at Clemson University. My research
is going to be based on Android for the next 2 semesters to come.

I need some tips and ideas as to what I can start working on which
could be achieved in 1 year.

I have a lot of random ideas in my mind. I thought I could seek some
pro-help.

Thanks.

Regards,
Sid

--~--~---------~--~----~------------~-------~--~----~

2. Will Android support and update feature?

Obviously in conjunction with the announced Android Marketplace, there
should be a uniform system to update apps through the marketplace, but
that's not what I'm asking about here.

What I want to know is if there are plans to support updating Android
to later versions as new features and APIs are crafted.

I think this is the single most important feature for Android. If the
first phones don't have a simple and easy way to upgrade, then it
doesn't matter how many great features are added into Android later,
you will always have these old phones with ancient features not
capable of running your program. I really hope Android will update
from the beginning. Then Apps simply have hardware requirements (needs
GPS, compass etc) and a single minimum android version requirement,
and any Android phone with the right hardware can be updated if need
be. This takes the sting off all the recent dropped feature
announcements. It becomes OK because we know they'll be available in
later versions of Android and if updating is easy enough, all the
phones will be up to date.

I think, as a developer, what scares me the most isn't a 1.0 Android
release that is missing the Bluetooth functions that were critical to
the app I was writing, it's the fact that the Android platform may
never have 100% support for them. Launching a new mobile phone
platform is a difficult task which is why it doesn't upset or shock me
much that Android is losing many of its promised features. But it will
be a real disappointment if Android apps have to list which Android
phones they will run on because the lack of Updating.

I think getting the entire phone right on 1.0 is impossible.
But if every Android phone released can be updated to the latest
software it will happen for sure.

I follow the Windows Mobile team blog where the phones curiously have
a Windows Update system setting, that doesn't seem to actually get
used. They also have an explanation for why, essentially, Windows
Mobile doesn't update. The iPhone doesn't seem to be prevented from
receiving regular, easy to install system updates as the WM engineers
seem to imply is impossible.

If Android gets pushed around by the carriers on various issues, I
think the one it should push back the most on is a system update that
comes from Android directly to ensure the base platform on all
handsets can be kept current. Of course it may prove tricky to update
the base underneath an handset provider's custom home screen etc.
Which is why I'm worried Android won't be able to update. The moment
Android says "well it's too hard, there'll be too many different
devices, we can't do an Android update. But hey! don't worry handset
providers will be able to push their own updates to the phone" is the
moment Android phones will never be up to date and bug free.

The handset manufacturers have no incentive to release updates for
their phones. Perhaps a few flagship phones get an update here or
there, but the majority receive no updates. There's just no money in
it for them. And what do you have now in Windows Mobile? If I told you
I had a Windows Mobile phone, and an application written for "Windows
Mobile" (and I don't say what version of either, picking just one at
random). The chances the app will run on the device without issues is
very low.

I just can't stress how important I think this is. There is only once
chance to release this on the very first phones. After they ship
without the capability to update, that's it. I really think even if a
bullish approach needs to be taken, it's the better route. Say an
Android version 1.1 comes out, handset manufacturers have 90 (or some
# agreed to by the OHA) days to take the update and include any
updates to their own software layer to make it fit with the new
android update. Then when owners of these phones update, they get the
Android update and the manufacturers update. If these days elapse and
no update is provided, or if the handset manufacturer elects to not
submit anything for their handset. The android phones can get the
update anyways even if it breaks compatibility with whatever handset
manufacturer bloatware came with the phone.

What does everyone else think? I just am willing to accept missing
features if I know all the phones will be able to get them later on
down the road, and I don't have to tell people they have to have an
Android phone with software version 1.1.56 build 6 or better to run my
app.
--~--~---------~--~----~------------~-------~--~----~

3. Unimplemented intents in Notepad tutorial

4. run emulator on eclipse

5. difference between start a service and a thread

6. Video playback in Android emulator

7. Androidology.com