Donut to Eclair

by Porting beginner » Sat, 21 Nov 2009 05:40:46 GMT

Sponsored Links

Is there any detail on what changes/new feature required from kernel and
driver when migrating to eclair from donut ?

Is that mandatory have to some feature/modification in kernel ( i.e fb
driver ) to make eclair works along with kernel which is currently working
for donut.  kernel 2.6.27 + donut (already working) , same kernel 2.6.27 +
eclair ? . Just to brint-up to eclair home screen, don't care about other
features which is working on donut i.e audio, video etc.



Other Threads

1. how to invalidate a single row in ListView with EfficientAdapter?

My application has a ListView that uses an EfficientAdapter (i.e.,
APIDemos/Views/Lists/List 14) to display a list of custom views (a
TextView with some line drawing on the left of each row and a checkbox
on the right of each row).

In the ListView's onItemClick listener, the checkbox changes state
(checked or unchecked) if the whole ListView is invalidated with
mListView.invalidateViews().  However when I try invalidating just the
changed row by calling v.invalidate() or mListView.invalidate(l,t,r,b)
in the following code, the EfficientAdapter's getView() for the
changed row doesn't get called.

    public void onItemClick(AdapterView<?> av, View v, int position,
long id) {
//      mListView.invalidateViews();  // this correctly updates the
checkbox state
//      v.invalidate(); // this doesn't
        mListView.invalidate(v.getLeft(), v.getTop(), v.getRight(),
v.getBottom()); // nor does this
        Log.d("onItemClick", "invalidate l,t,r,b: " + v.getLeft() +
                        ", " + v.getTop() +
                        ", " + v.getRight() +
                        ", " + v.getBottom());

What should onItemClick() call to invalidate just the checked/
unchecked row?

In a possibly related question, why does APIDemos/Views/Lists/List 11.
Multiple Choice List redraw all rows (seen by enabling Dev Tools/
Development Settings/Show Screen Updates) whenever any checkbox is


2. IMAGE_CAPTURE Intent and changing phone orientation

Hi all,

I think finally I am able to to replicate my issue of the camera
intent restarting mysteriously (not always) after an image capture,
where the intent never seems to finalize and call the code specified
in onAcitvityResult function.

As it turns out after starting the IMAGE_CAPTURE intent if you change
the orientation of the phone simply by turning it sideways the camera
intent restarts instead of calling onAcvitityResult after a successful
capture and user clicking "OK" or "Done".

Has anyone else seen this behavior ? Is there a work around to this ?


3. Automatic font size adjustment?

4. Apps not showing in market after factory reset with Froyo.

5. how to connect android phone to pc using adb

6. Minta link froyo untuk yang sudah r00t

7. Anybody run Chrometophone in Android 2.2 Emulator successfully