init.<architecture>.rc

by Stefan » Wed, 09 Feb 2011 22:34:03 GMT


Sponsored Links
 I'm not sure, maybe it's a dumb question, but anyway:

When I want to start Android, and I use the images from the
sdk I have to adjust the init.rc file. But what happens with the
init.goldfish.rc file which is in the same directory?

Shall I delete it and make my own init.<architecture>.rc file?

If yes, what shall I write into this file?

Regards,

Stefan

-- 



Re: init.<architecture>.rc

by Joerie de Gram » Thu, 10 Feb 2011 00:52:17 GMT


 Hi,




It's evaluated for the goldfish (emulator) board. It's not
architecture, but board specific. On bootup it attempts to run
init.<boardname>.rc, where boardname is the kernel supplied board
name, lowercase (and if it contains spaces, up to the first space).

Anything to be performed at init, specific to your board.

Joerie

-- 


Sponsored Links


Re: init.<architecture>.rc

by Stefan » Fri, 11 Feb 2011 17:19:40 GMT


 > It's not architecture, but board specific.

So, I have to delete the goldfish-init and write my board specific
file.

What do I have to write into e.g. init.myOwnBoard.rc if I "only"
want to start Android as I can see it running on the emulator?

Do I have to edit the normal init.rc too for this?

Would you be so kind and give me an example for a running init.XXX.rc-
File?

-- 



Re: Re: init.<architecture>.rc

by David Turner » Fri, 11 Feb 2011 21:58:32 GMT


 




board-specific initialization.
It could defining new services, mounting partitions, defining system
properties, whatever.

Apart from that, consider it an extension of init.rc

It really depends on the customization you have done.


board-specific.

I.e. if you modify the platform in significant ways, you would modify
init.rc to reflect that.
You could then use the same platform to build various product configurations
(each corresponding to a different board), and put their own customizations
in init.<board1>.rc, init.<board2>.rc, etc...

Of course, if all you do is developing a single product/board, you can just
modifiy init.rc instead.


Would you be so kind and give me an example for a running init.XXX.rc-

-- 



Other Threads

1. Home screen widget - weird size of int[] appWidgetIds

Hi all,

I've been developing my home screen widget for a week or two now and during
last few days I encountered an interesting error. First about my widget, I'm
handling my own broadcast messages in onReceive method, looks like this:

public void onReceive(Context context, Intent intent) {
super.onReceive(context, intent);
/* handling of my intents follows */
}

I don't really use onUpdate method since I'm updating widget content on
demand, so I finally put this into the onUpdate method (I was trying to
debug the code):

public void onUpdate(Context context, AppWidgetManager appWidgetManager,
int[] appWidgetIds){
Log.d("number of ids",new Integer(appWidgetIds.length).toString());
}

Provider's XML looks like this:

<appwidget-provider
xmlns:android="http://schemas.android.com/apk/res/android"
android:minWidth="318dp"
android:minHeight="78dp"
android:initialLayout="@layout/widget"
 android:configure="blah.WidgetConfigurationActivity"
updatePeriodMillis="0"
</appwidget-provider>

(I have some interesting question(s) about the width and height fields, but
that's another case.)
And to clear the other thins, the only moment I send an Intent from my main
application to the widget is on user demand (user clicks some button). Now
about the error - when I deploy the application to the emulator from
Eclipse, my onUpdate method gets called with appWidgetIds with length about
119 (has been 120 lately). If I understand this correctly, that would mean
my widget provider should handle more than 100 widget instances even when
there are none? I don't remember changing anything that could affect this
(and I don't really know what even could). Anyone got some thoughts or
proposals about this?

I'm actually wondering why is the onUpdate method getting called on
application deploy too (it shouldn't imho, at least I don't see any real
reason). I've tried to solve that for a day or two, but I wasn't able to
make any improvements. I came up with some possible workarounds, but I don't
really feel good about them.

Thanks a lot for all your replies.
Filip Havlicek

-- 

2. Widget which has arrow button to show up and down

Hi Everyone,

I am using a button to hide some edit text boxes and to display them,
that means if I press a button 4 edit text boxex will scroll down and
again if I press it that 4 edit text boxes scrolled down will scroll
up and not visible, my problem is there any widget which has arrow
button on that such that it can show scroll up and scroll down, Please
any one help me.

Thanks & Regards

-- 

3. touch vs. drag

4. not getting current location

5. S5PV210 S5PC110 Android Tree Downloadin

6. Hero performance reported as slow

7. runtime error on softkeyboard using LatinIME.git example