summaryrefslogtreecommitdiffstats
path: root/init/Android.mk
diff options
context:
space:
mode:
authorDavid 'Digit' Turner <digit@google.com>2011-09-16 00:19:40 +0200
committerDavid 'Digit' Turner <digit@google.com>2011-09-16 00:25:16 +0200
commita503456526359767ffb383a06835308f62172dde (patch)
tree560b1c0352080dd766863669f1d508bbd19b659d /init/Android.mk
parent243123fb41d7d2981116bd5d11ba168b127d68e9 (diff)
downloadsystem_core-a503456526359767ffb383a06835308f62172dde.zip
system_core-a503456526359767ffb383a06835308f62172dde.tar.gz
system_core-a503456526359767ffb383a06835308f62172dde.tar.bz2
emulator: Move qemu-props to core service
The qemu-props program is launched at boot to read a series of system property assignments from the emulator and apply them. This is necessary to deal with the dynamic nature of the emulated platform (e.g. the screen density which depends on the skin and cannot be hard-coded in the platform image). This patch ensures that qemu-props is started before any other service that may read one of these properties (e.g. surface flinger). This is done by encapsulating the program into a 'core' service. Core services are all stared before regular ones. Before the patch, qemu-props was started manually inside a script that is called from a late emulator-specific boot service (goldfish-setup). The problem was that sometimes qemu-props was run too late. This resulted in random flakiness, especially when running on a low-end host machine. Fix for bug 2161189 (and probably a few others) Change-Id: I2933a25dcb5fecbb1fc238f157264e621b8f295b
Diffstat (limited to 'init/Android.mk')
0 files changed, 0 insertions, 0 deletions