Android on older devices

by » Fri, 13 Mar 2009 00:19:21 GMT

Sponsored Links
 I happen to have android prototype device (the one in ;txt this

I'd like to know if it's possible to run the recent version of android
and if so, how can it be done?

If not, can I use older SDK to make a program to run on that


Android on older devices

by Jean-Baptiste Queru » Fri, 13 Mar 2009 00:33:57 GMT

 I wouldn't count on being able to run a recent Android on that device
(not enough RAM, no current kernel, wrong screen resolution, no

As for developing apps for that device, even if you could find the
right tools, you'd be developing against such an old pre-release that
it'd have little practical value. The emulator in the current SDK
behaves closer to a shipping consumer device than this device would.


Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further


Sponsored Links

Android on older devices

by mathiastck » Fri, 13 Mar 2009 19:30:19 GMT

 Really?  I had always hoped that device would come out eventually.
It's still being used as the QVGA-L emulator skin.

Trackballs are fun, but I prefer a D-Pad a lot of the time.  It's got
the Nokia E-Series form factor I like too.


Android on older devices

by Dianne Hackborn » Fri, 13 Mar 2009 20:02:33 GMT

 That particular hardware is ~3 years old.  It is obsolete, and there is
nobody supporting drivers or other software for it.  I wouldn't be surprised
if in the future there is a device with that form factor, but it won't be
that exact hardware.

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.


Other Threads

1. Android Unable To open initial Console

hi all,

i try to porting android to omap 3430, when i'm booting that's error like :

Warning : Unable to open an initial console
Kernel Panic - not syncing : attempted to kill init

it's my step :

#setenv booatargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw
rootdelay=2 mem=128M init=/init
#fatload mmc 0 80300000 uImage
#bootm 80300000

best Regards,
Aldyth M


2. Questions about adding an external shared library to Android image (donut)

I have determined (or so I hope) how to add a new shared library to
the external part of Android image:
1. Add a directory called "foobar", under <root>/external
2. In that folder put my source files
3. Create file
4. Update the file <root>/build/core/ and add my
library there, in the last section (titled "libraries for specific
apps..."), choosing a free memory area
5. Use the 'mm' or 'mmm' shell functions to build the library.

The output is (between dashed lines):
make: Entering directory `/media/disk-1/development/Donut/donut'
target thumb C: libfoobar <= external/foobar/src/foobar_01.c
target thumb C: libfoobar <= external/foobar/src/foobar_02.c
target SharedLib: libfoobar (out/target/product/generic/obj/
target Prelink: libfoobar (out/target/product/generic/symbols/system/
target Strip: libfoobar (out/target/product/generic/obj/lib/
Install: out/target/product/generic/system/lib/
make: Leaving directory `/media/disk-1/development/Donut/donut'

So far, so good.

My questions are:
1. Is the process above correct? If not, where did I go wrong?
2. Is this process documented and if so, where?
3. How do I prevent the library from being stripped?
4. Alternatively, can I tell the make process to preserve certain
symbols and strip all others?
5. If I want the foobar library to be built from objects and
libraries, located elsewhere, without any C compilations, how do I do
it by tweaking the file?



3. Kernel Stuck

4. Ongoing...

5. Anyone else notice that the "Top" apps in seem inaccurate?

6. Create Cool styled buttons

7. Send audio via mms