- Sensors MTP Monitor Service: This service allows MTP sensors to communicate sensor data. If this service is stopped or disabled, MTP sensors will no longer function.
In other words, this service monitors MTP (Media Transfer Protocol) sensors (such as a cell phone with a GPS receiver) to communicate sensor data to programs.
As it is, there are lots of problems with existing GPS devices connected to Windows:
1. Most devices usea NMEA proprietary format to provide information, Windows Location Platform gives free open APIs standard
2. These devices are connected via COM so only one app can use location data at one time. Windows Location Platform enables concurrent access to several apps at the same time
3. Location-aware apps do not work without GPS. Windows Location Platform has support for different location sensors (read providers):
GPS
IP Geo Location
Wi Fi Triangulation
Cell Tower Triangulation
Any new kind of a location provider
And if you do not happen to have any of the above solutions, you can still use "Default Location Provider" which enables user to enter his location into one place where it will be then used by every app
This service is absent from build 6952!
- Windows Biometric Service: The Windows biometric service gives client applications the ability to capture, compare, manipulate, and store biometric data without gaining direct access to any biometric hardware or samples. The service is hosted in a privileged SVCHOST process.
There is a comma absent in that text. What the mean is that the Biometric Service itself will not gain direct access to the biometric hardware; it will simply connect the corresponding software to the hardware. The point is to try to unify the way biometric sensors are installed and interact with windows/the user.
- WWAN AutoConfig: This service manages mobile broadband (GSM & CDMA) data card/embedded module adapters and connections by auto-configuring the networks. It is strongly recommended that this service be kept running for best user experience of mobile broadband devices.
Once again, if the device manufacturers implement the correct Windows APIs and instructions for drivers requirements, this will be a vast improvement over the existing situation where the user experience is a new one each time a new mobile broadband device is connected. This service will also simplify the task of roaming from one mobile broadband network to another, much the same as roaming between wireless networks has been improved: the user does not need to launch a new application and perform several steps in order to connect the device to the internet, all the user will be required to do is specify which device to use and if necessary enter appropriate credentials (username and/or password)
No comments:
Post a Comment