Hi, you could create a service with dummy implementation of the SurfaceFlinger's binder interface (used by the SurfaceComposerClient). You can disable the media player service, or replace StageFright path with the TestPlayer path in case you still going to have apps that may use the MediaPlayer API. You can gain some boot time by modifying the preloaded library list.
Br, Zoltan On Monday, 4 August 2014 19:00:06 UTC+2, Mauricio Cirelli wrote: > > Dear community, > > I am working on a very specific device which does not have a display nor > any kind of audio hardware. However, it does have GPS, Bluetooth, Wifi, > 3G, sensors and other peripherals. We would like to use the Android SDK to > develop apps for such a device, but we would like to disable multimedia and > user-input features. > > I would like to know if it is possible to have a working Android build > that does not run any multimedia or user-interface related features, such > as images, videos, audio or user-input (touch or keyboards). I have looked > into TINY ANDROID (https://wiki.linaro.org/Platform/Android/UseTinyAndroid), > but it is way too tiny.. It does not have zygote or system server, which > we need. > > Is it a matter of removing mediaservice and surfaceflinger from init.rc > or do I need to do further changes? We do need it to boot fast and start > running apps as soon as possible. I believe (please, correct me if I am > wrong) that removing such services, boot would complete faster and apps > listening to boot complete intent would start faster. > > Any help would be much appreciated. > > Thank you. > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
