According to some requirements from OEM/Tiers ( e.g., SPEC-4 ), we need to detect, handle, and acton on hot & cold-plug devices at run-time.

Here are some of missing functionalities and features we are looking for:
1-Run by default so It can recover the last GUI app and its' last state.
2-Discover "Cold-plug" and "Hot-plug" devices (e.g multi-media, connectivity devices) at runtime and take functional/security action over them (e.g block/mount the device, launch/recover corresponding app/service) based on a group of static (OEM strict/permanent) or dynamic (changeable at run-time) policies.
3-The service should be notified/get the last state of running App and "recoverable" services (e.g connectivity services) including their states.
4-Provide multi-user query/subscription API mechanism to expose the device's notifications/state-changes with their useful properties for other AGL apps/services.
5- Provide some verbs with the required security to take some actions on the device ( dynamic policies ).
6- Any more? ... Please comment!

These functionalities should be unique and not redundant across the AGL eco-system and compatible with the AGL runtime and security model so OEM/Tiers can customize policies and required securities.
These group of features can be centralized in a service which can be named "agl-service-ddm" ("Device Detection Manager" )(from SPEC-4) or any other sensible name (depends on the service final functionalities) or can be delegated to different AGL runtime/security components (Architectural decision).