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?




Re: init.<architecture>.rc

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


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.



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

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-


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.


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. developing on a physical device

Hi all,
         I have a android based device on which I am trying to run a
simple hello world application, but I don't see the device listed
using : adb devices.

My setup is Eclipse 3.5, ADT 0.9.5, Android SDK 1.6, Debian 5.0.5
(lenny) with SMP kernel.

I have already tried the various options listed on

The usb debugging is enabled on the device and I have already tried
setting up /etc/udev/rules.d/51-android.rules with the following

SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"

dmesg shows the following output:

[155544.908038] usb 7-2: new high speed USB device using ehci_hcd and
address 8
[155545.057192] usb 7-2: New USB device found, idVendor=0955,
[155545.057194] usb 7-2: New USB device strings: Mfr=1, Product=2,
[155545.057196] usb 7-2: Product: ADB Composite Device
[155545.057198] usb 7-2: Manufacturer: NVIDIA Corporation
[155545.057199] usb 7-2: SerialNumber: 0123456789ABCDEF
[155545.057280] usb 7-2: configuration #1 chosen from 1 choice
[155545.074121] scsi10 : SCSI emulation for USB Mass Storage devices
[155545.074328] usb-storage: device found at 8
[155545.074329] usb-storage: waiting for device to settle before
[155560.072610] usb-storage: device scan complete
[155560.073098] scsi 10:0:0:0: Direct-Access     <NULL>
<NULL>           0000 PQ: 0 ANSI: 2
[155560.073455] sd 10:0:0:0: Attached scsi generic sg2 type 0
[155560.082069] sd 10:0:0:0: [sdb] Attached SCSI removable disk

Has anyone tried running an android application with Debian Lenny
host? Please suggest if I need to make any changes to my setup.

Thanks in advance,


2. Emulator on Linux 10 times slower than on Windows

Hi there,

I know that many people are complaining about slow emulator
performance, and mostly it can't be helped because of slow hardware
and the fact that emulators somehow have to be slow by definition
because of the way they work. But something really puzzles me:

I'm using a dual boot configuration with Windows XP and Ubuntu 9.04.
On XP, the emualtor is somehow slower than a real G1 device, but it's
completely ok.

But on Ubuntu, the emulator is unusable slow. Note that other programs
run just fine under my ubuntu. I have no exact measurements, but I
think the emulator about 10 times slower than on Windows. Installing a
small app takes more than 2 minutes, starting an app sometimes takes
over 2 minutes, returning to the home screen takes up to 40 seconds,
and there is not a single click I can do that takes less than 2
seconds to trigger some kind of reaction. I get around 2 fps at most,
no matter what I do.

Both systems (of course) use the same hardware, and on both I'm using
SDK 1.6 with a 1.5 AVD without google additions, and the very same app
that I'm developing.

I used to have a very old Graphics card that I had to access through
plain old VESA drivers on both XP and Ubuntu.
Now I'm on a new hardware which uses a proper driver to access the
graphics hardware, but the emulator on Ubuntu is still as slow as
before, so I think this is not the bottleneck.

Also, I noticed that under heavy usage of the emulator, the usage of
my real CPU never went above 30%.

Is there any explanation for this slowness on Ubuntu? Or even a way to
further investigate where the bottleneck might be?


3. Android build in email client

4. G1 dream android 1.5 , where is telnetd

5. how to get header in Listview without scrolling

6. Custom menu items

7. Knowing when a scroll/fling is done.