Error : applying many patches

by Celeste82 » Fri, 25 Sep 2009 01:21:23 GMT

Sponsored Links

I am trying to patch Android with Armadeus patches.

I use the script "" in amdeus-3.1/buildroot/toolchain/

I executed this command :

$ script     Kernel_to_patch    folder_of_Armadeus_patches

$ARMADEUS/buildroot/toolchain/ $ANDROID_SOURCE/kernel
$ARMADEUS/buildroot/target/device/armadeus/linux/kernel-patches/ \*.patch{,.gz,.bz2}

I have this message error :
Applying 015-armadeus-logo-add_armadeus-project_tux.patch using
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|Index: linux-
|--- linux-    2009-03-24
00:12:14.000000000 +0100
|+++ linux-    2009-06-04
09:54:16.000000000 +0200
File to patch:
Skip this patch?

Can you help me ?

Thank you very much



Other Threads

1. SDP Support

I believe packet video support SDP for streaming video. However I do
not see any default application registering for SDP content.
Does anybody know why?
Is there a plan from Google to add this into default video player in
future releases?


2. Having some trouble handling focus between a TabView and my own custom widget

Hi all,

I am having some trouble defining how focus should move through my
app.  I have a Tab Layout which I set up following the android

In my first tab, I have created a custom widget that acts as a sub-tab
menu.  It is a RelativeLayout with two buttons laid out horizontally.
I am handling focus events on my custom widget so that I can determine
which of the two buttons should be focused as the user navigates up
and down in my app.  Underneath the sub-tab menu is a list.

I created a custom xml file for my custom widget and the
RelativeLayout I defined there is marked focusable and
focusableInTouchMode.  When I navigate up from the list, my
RelativeLayout's focusListener is notified as I would have expected
and I can determine which of the two buttons should be focused.  This
works great!  However, when I go back up to the tab layout and then
navigate down again, my RelativeLayout doesn't get focus.  Instead,
focus jumps directly to the 1st button in my custom widget, which is
not correct.

Does anyone know why this would be happening?  I have tried a few
things to fix this but nothing seems to work.  One thing I tried is
configuring the "nextFocusDownId" on my 1st tab by calling:


When I do this, I notice in DDMS that there is a log statement saying
"couldn't find next focus view specified by user for id 2131230742".

Is this because the collect_subtab_view id is defined in a different
xml file than my tabhost?  How can I correctly set the



3. Views example on 1024x600 AVD -- Froyo

4. Does AsyncQueryHandler / AsyncTask really runs asynchronously?

5. Smack in Android

6. Widget button dies

7. Android and Java Reflection to call a higher API level function/abstract class