Another article on the release.
When I spoke with the engineer behind the IVI Home screen interface he mentioned that it's really designed to be used with a dial or space navigator type interface. Also in speaking with one of the other IVI higher-ups for MeeGo, the HMI/UI design and implementation is really something that they'd love to see the community get involved with.
Former author of LinuxICE, nghost.
Current author of nobdy.
Another article on the release.
yes, exactly.
I have asked about the idea of contests etc, to really motivate developers to hop on and get involved. Also, I would like to add MeeGo as a platform to the auto app mart and have MeeGo IVI apps. Members of Genivi the group that has agreed to use this platform will surely find these interesting.
Another video of the IVI interface:
http://www.youtube.com/watch?v=JVL8I1B6uPs
Former author of LinuxICE, nghost.
Current author of nobdy.
I was after a simple dial controlled system years back but everyone was so obsessed with touch screens despite the brightness and glare problems being mainly down to them. A dial is much better suited to production cars as people only get a second or so to glance down at the screen so they can move the dial bit by bit and then select where as using a touch screen can require a much longer single instance to find and press the button - particularly on menus. For audio controls etc touch screen is easier but for OEM systems where the user was not involved in building it so may be unsure where things are you need to use a dial system.
hmmm, I was just wondering about the state of *nix in the car this evening.
This is what I'm looking for:
* start-up > FE (meaning FE is the system and the system is the FE)
* music, video, handsfree, gps, obdII (core items that I feel a FE should have from start)
* extras to add on
* skins
Is meego getting there or is Android getting there first?
I haven't seen any publicly available and sanctioned builds of android for the car... Especially not for x86. There's a lot of reasons why MeeGo was chosen by GenIVI over Android (which was chosen by an overwhelming majority of members). One big one is focus. Android claims to be governed by a "handset alliance" which focuses on, well, handsets. This is a problem for the automobile industry which isn't making a handset and don't there stuff to be treated as such. Other reasons they went with MeeGo over android probably include build infrastructure, multiple arch support things like boot and run speed.
Also, LinuxICE did all of what you wanted above, just no handsfree, which meego has. This 1.0 release of MeeGo IVI is still immature btw. It doesn't have a real vehicle-oriented media player and doesn't have anything for obd-II. These are two things that I'm hoping to contribute to MeeGo with the help of the community here and elsewhere. I've already started a clone of the handset media player with the intent to port it over to the car. I'm also hoping "nobdy" will find it's way into MeeGo to provide obd-II.
So overall I think we are pretty close. LinuxICE is a bit more mature at this point, but MeeGo could easily surpass it by the end of the year.
Former author of LinuxICE, nghost.
Current author of nobdy.
Bookmarks