Driver development in Android

by sudheerg » Tue, 08 Sep 2009 15:58:12 GMT

Sponsored Links
 Hi All,

I am newbie to android developement.
I previously worked on Wince driver development.

I want to start driver development for Android.

I have installed ubuntu, and got the git repository of Android, as per
the instructions given at the site ,
I am able to launch the emulator and also installed Eclipse.

However the notes published there indicate application development.
It will be easy for me to start, if someone can give some pointers to
start with the driver development for Android.




Driver development in Android

by sudhi » Thu, 17 Sep 2009 15:08:13 GMT

 Hi Sudheer,

You can download the goldfish (this is the emulator version) kernel
from the following link (click the snapshot tab to get the kernel
source into your desired path) ;a=tree;h=65bd5239eb2dba3024e5c3fd136a832b544c4783;hb=132305ed227e69bd7498c8a30d40a338a23a4afe

Make sure  to build the goldfish kernel separately.





Sponsored Links

Other Threads

1. Porting to a Phone that wont sync

I have a Verizon XV6700 PPC.  Its a great phone but has the hideous
white screen of death.  I can access the phone via mtty, but cannot
sync with it to repair the original OS (WM 5).  Can someone help me
put Android on this phone?


2. Memory management issues - stop crashing the party!

Ok, first I'm a longtime programmer, but a bit new to the world of
Java (so my apologies in advance).  I've done a bit of searching for
answers or similar questions, but haven't found exactly what I'm
looking for.

In my app, I'm allocating large arrays and experiencing some crashes,
so a few questions on memory management:

1.  Is memory saved in the Dalvik VM by using a short or byte vs. an
integer?  I've read some conflicting things on how this works.  i.e.
-- is the memory occupation as follows:

Byte = 8bits
Short = 16bits
Int = 32bits

2.  Garbage collection strategies.  Specifically, I'm allocating a
couple of large integer arrays in my main activity class.  My program
runs fine once.  When I press the HOME button, however, and then re-
launch the application it crashes when (re)allocating the arrays.

As a way around this, I've declared the large int arrays as "static".
This seems to prevent them from being re-allocated when the app goes
from background to foreground.  Not sure if this is the best strategy

However, getting past the int[] array HOME button crash, I get a crash
my second run through during some Bitmap activities.  I am doing a
bitmap.recycle() after they are used...but, should large bitmaps be
declared as static also?

How are people working with large arrays and bitmaps that may push the
limits of the VM heap on a single run through the application?

In my experience, pressing the HOME button does not cause garbage
collection of the arrays or bitmaps....yet relaunching the app
attempts to reallocate them both.

So, what's the best approach to dealing with things when you're nearly
at the memory limit -- to allow the app to gracefully go from

[It would be really great if Google could write an app note on this]


3. ListView turns black when focused/selected, although I already set cacheColorHint to transparent

4. ARM Architektur

5. Is there any UI can connect to SQLite database?

6. Widgets ( frequent updates )

7. why my 2nd App replaces the first one?