The new Range Rover Evoque offers a level of integration with a number of smartphones not seen in other vehicles.
Just need to add WiFi connectivity for their media unit and its the perfect solution!
It will be interesting to see how auto companies and car makers tap on the boundless potential of smartphone and connectivity integration into their vehicles. Many drivers will appreciate a more integrated approach to having some of the connectivity they enjoy on their phones in their cars, and will definitely be willing to pay for a car that offers such perks.
Jon - http://www.caravan-insurance-experts.co.uk/
Slight correction to the information on Terminal Mode. It was developed by Nokia in conjunction with CE4A but to allow development of the specification to be influenced by a larger audience a separate consortium is being setup - see TerminalMode.org. A full spec can also be downloaded from that site.
Terminal Mode will not work over BT SPP, there just is not enough bandwidth for decent framerates. The current spec uses IP over USB as this allows the phone to be charged and since Navigation is a key use case charging is important.
As well as BT A2DP, audio can also be sent over IP using RTP.
UPnP is used to allow the head unit to discover which apps the phone is making available to the HU and in this way the HU can make decisions as to which apps are allowed, something that is critical for the auto industry where the consequences of bad software are much more severe than if it were just a handset.
On one hand we have a car with very long development cycles and not much of a history of software updates. On the other we have cell phones / tablets which are on a very fast tech refresh cycle. I would rather have the car export controls to an external device than the other way around. Either that or create standard interfaces in the car which would allow user upgrades rather than forcing proprietary systems which require expensive dealer upgrades.
We did something related to this 18 months to 2 years ago. Essentially the challenge was to use a pre-touchecreen car fascia (buttons) as user input to a web browser based HMI on the facsia screen, backed by an incar PC. It was all about mapping button actions into gestures. We got it to work, eg Zoom in out, scroll up/down, left/right, page back and fwds etc all using the buttons. We also implemented a Windows Mobile device to generate those same gestures. All worked nicely.
Another approach with a Windows Mobile device would to be use the Soti application in the car PC to replicate the Mobile Phone on the fascia. The fascia controls (or touch gestures) then can drive the device.
It is absolutely great Idea to design some better user interface system for accessing the electronic information while driving effectively. Using terminal client will be a start of it, also bluetooth is insignificant for this purpose so it either requires some modification in the standard or design of some new protocol for in car use of electronics.
Drones are, in essence, flying autonomous vehicles. Pros and cons surrounding drones today might well foreshadow the debate over the development of self-driving cars. In the context of a strongly regulated aviation industry, "self-flying" drones pose a fresh challenge. How safe is it to fly drones in different environments? Should drones be required for visual line of sight – as are piloted airplanes? Join EE Times' Junko Yoshida as she moderates a panel of drone experts.