WindowManager will have the knowledge about headlamp, stop/run, parking brake and light status because WindowManager informs the application about the switching timing of the day/night graphics and the switching timing of the restriction by car running.
WindowManager gets the knowledge from low-can-service.

If the applications want to switch the day/night graphics, the applications have to get the knowledge from low-can-service and etc..
It is the one of options for the applications to use WindowManager to get the knowledge.

When the applicatioins register callback handler for getting the events to WindowManager, then the applications can get the knowledge.
Therefore we think it is the one of advantage that WindowManager has the knowledge.

[Add events]

• headlamp ON/OFF
• car stop/run
• parking brake ON/OFF
• lightstatus brake ON/OFF

These event signal format are here:
ON-EVENT windowmanager/<EVENT_NAME>:

{ "event":"windowmanager\/<EVENT_NAME>", "jtype":"afb-event" }

<EVENT_NAME> is as follows:

• headlampOff
• headlampOn
• parkingBrakeOff
• parkingBrakeOn
• lightstatusBrakeOff
• lightstatusBrakeOn
• carStop
• carRun

[Add API]
getCarInfo() can get the car information as follows:

• parking brake state : true/false
• lightstatus brake : true/false
• accelerator pedal position : 0-127.5
• car state : "stop"/"run"