If there is no UI I would also put ro.config.headless on the list.
For a few reasons I strongly favor config options over direct changes to
AOSP given the choice. Its worth the grep time to see if there is anything
you can do before editing that init.rc. For example you can use
"debug.sf.nobootanimation" instead of removing bootanim. I don't know
about anything for surfaceflinger though. Sorry I can't help out there.
On Wednesday, August 6, 2014 4:21:37 PM UTC-6, Mauricio Cirelli wrote:
>
> I will have a look into that!
>
> Searching for config.disable_media into this group I have found another
> thread which mentions some other interesting properties in
> frameworks/base/services/java/
> com/android/server/SystemServer.java, a quick grep yields:
>
> String factoryTestStr = SystemProperties.get("ro.factorytest");
> final boolean headless =
> "1".equals(SystemProperties.get("ro.config.headless", "0"));
> boolean disableStorage =
> SystemProperties.getBoolean("config.disable_storage", false);
> boolean disableMedia =
> SystemProperties.getBoolean("config.disable_media", false);
> boolean disableBluetooth =
> SystemProperties.getBoolean("config.disable_bluetooth", false);
> boolean disableTelephony =
> SystemProperties.getBoolean("config.disable_telephony", false);
> boolean disableLocation =
> SystemProperties.getBoolean("config.disable_location", false);
> boolean disableSystemUI =
> SystemProperties.getBoolean("config.disable_systemui", false);
> boolean disableNonCoreServices =
> SystemProperties.getBoolean("config.disable_noncore", false);
> boolean disableNetwork =
> SystemProperties.getBoolean("config.disable_network", false);
> :
> Having a look into SystemServer.java, I think disabling media, system UI,
> NonCoreServices (will it disable ADB, as it would disable USB Manager?)
> Also, I think I could remove media, surfaceflinger and bootanim services
> from init.rc would do the trick.
>
> What do you think?
>
> Thank you for your interest and time in our problem!
>
>
> On Wednesday, August 6, 2014 3:14:10 PM UTC-3, Stuart Small wrote:
>>
>> I would try the system property "config.disable_media"
>>
>> On Monday, August 4, 2014 11:00:06 AM UTC-6, 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.
