Specifications

Windows Embedded Automotive 7 Deep Dive: Phone Core and Media Core 36
Class
Code in wParam
CMS Errors (phone response included)
0x00002000
Standard error values, as defined in the GSM
specification, are appended to the wParam value.
HFP Port Failures
0x00004000
Sync Manager and Phonebook
Windows Embedded Automotive 7 provides users with the ability to access their phone’s
contact information through the UI. This gives users a safe and fast way of accessing their
phone’s contact list to make calls, as well as providing OEMs a way to display contact
information based on caller ID information.
Prior to Microsoft Auto 4.0, the HFP Service contained all of the phonebook download
components, and the HFP API controlled the download initiation and messaging. In the legacy
model, the HFP Service downloaded the phonebook using PBAP, SyncML, and then AT
commands. Phonebooks were stored in a structure written to a persistent file in flash memory
and read into memory as a cache.
In Automotive 7, Microsoft separated the phonebook download components into individual
elements but maintained full-backwards compatibility. Each profile now has its own header in
autocomp\sdk\inc, including a Sync Manager header. This architecture change provides
significant advantages to developers using Automotive 7. During the design of the new
architecture, Microsoft ensured that code paths from their shipping, field-tested, and hardened
call handling and phonebook downloading compatibility code was preserved in the new
architecture.
Windows Embedded Automotive 7 supports the following mechanisms for downloading
phonebook data from supported phones:
• PBAP 1.1
• SyncML 1.1.2
• Phonebook-related AT commands
• OPP 1.1
• SYNCH 1.0 (Note that by default, this is disabled for phonebook and used for
downloading calendar items only.)
• OBEX