Jan-Simon Möller | 1 Feb 12:01 2011

Re: Question re: Navit

Hi Ian,

issue is fixed now in Trunk. Please retry your kickstart file.

Best regards,
Jan-Simon

Am Donnerstag, 27. Januar 2011, 14:23:55 schrieb Bennett, Ian (Jet; ADITG/SWG):
> Hello,
> 
> My name is Ian Bennett.  I am new to the Meego-IVI mailing list. I work
> for ADIT GmbH in Germany as SW integrator, with the task of contributing
> to the BIT Team of the GENIVI consortium.
> I am trying to get navit running under Meego IVI on the Beagle Board
> (ARM chip vC4).  I cannot get navit started at the moment because of a
> missing library: libebook-1.2.so.9.  It is not present on the Meego
> site: http://download.meego.com/live/Trunk:/IVI/Trunk/armv7l/. Can
> anyone from Meego tell me where to get the library as an ARM binary for
> the Beagle Board from?
> 
> Many Thanks
> 
> Best regards
> 
> Ian Bennett
> 
> Advanced Driver Information Technology GmbH
> Software Group (ADITG/SWG)
> Robert-Bosch-Str. 200
> 31139 Hildesheim
(Continue reading)

Re: Question re: Navit

Hi Jan-Simon,

Thanks very much for fixing this :-)

Best regards

Ian Bennett
Software Group (ADITG/SWG)

Tel. +49 5121 49 6971

-----Original Message-----
From: Jan-Simon Möller [mailto:jsmoeller@...] 
Sent: Dienstag, 1. Februar 2011 12:02
To: meego-ivi@...
Cc: Bennett, Ian (Jet; ADITG/SWG); Keppke, Sven (Auronik; ADITG/SWG); Pfohl, Andreas (c4c; ADITG/SWG);
Demus, Peter (Brunel; ADITG/SWG); Khaliq, Abdul (ADITG/SWG); Maleyka, Simon (ADITG/SWG)
Subject: Re: [MeeGo-ivi] Question re: Navit

Hi Ian,

issue is fixed now in Trunk. Please retry your kickstart file.

Best regards,
Jan-Simon

Am Donnerstag, 27. Januar 2011, 14:23:55 schrieb Bennett, Ian (Jet; ADITG/SWG):
> Hello,
> 
> My name is Ian Bennett.  I am new to the Meego-IVI mailing list. I 
(Continue reading)

Komatovic, Marjan | 2 Feb 13:33 2011
Picon

Re: Audio-Visual zones in the car

Hi Rudi,

 

I shared details on how to set-up manually Pulse Audio for rear zone in: http://wiki.meego.com/In-vehicle/IVI_topic_areas, check for ”PA hands-on” section. As mentioned, this is manual setup, therefore a static one that always dedicates streams to particular audio zone.

 

In regards to your question, this is something that can’t be done statically. We need to have some policy framework that would sit on top of Pulse Audio and use its stream control capability. For example, the “proximity” application would compete for resources (speakers) with other applications based on priority. Assuming highest priority, policy framework would allow “proximity” application to use resources while either stopping, pausing other applications or just corking audio streams at source/sink side. To my best knowledge, that kind of policy handling capability already resides in Resource Management component: http://wiki.meego.com/images/Meego-policy-framework-developer-guide.pdf

 

Best regards,

Marjan

 

 

 

 

 

From: rudolf.streif-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [mailto:rudolf.streif-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] On Behalf Of Rudolf Streif
Sent: Tuesday, January 25, 2011 8:03 PM
To: Komatovic, Marjan
Cc: meego-ivi-VVXm0OgCXj10cC2WI2GV6A@public.gmane.org
Subject: Re: [MeeGo-ivi] Audio-Visual zones in the car

 

Hi Marjan,

 

Thank for sharing your great demo and the video. It clearly demonstrates the policies on what application can be used by what user depending on the context.

 

For the ones who are not that familiar with configuring pulseaudio would you be able to share the steps on how to set it up? That would be good "tribal" knowledge to share on the MeeGo Wiki branching off http://wiki.meego.com/In-vehicle.

 

What about an application that uses front and rear speakers in the car such as the audible feedback from the ultrasonic proximity sensors in the bumpers? This application routes a beeping sound to the front left, front right, rear left, rear right speakers dependent on what sensor detects an obstacle in the path of travel. The frequency of the sound is also different for front and rear and the intervals between the beeps shorten with closeness until it is a continuous sound if the distance is less than a foot for example. Technically, that application should get immediate control over the entire audio system and have zone that covers the entire vehicle and all other audio needs to be muted or at least lowered in volume. Do you think that can be done with pulseaudio configuration too? Or would that actually require code enhancement?

 

Thank you,

Rudi

On Tue, Jan 25, 2011 at 4:32 AM, Komatovic, Marjan <marjan.komatovic-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

Hi guys,

 

I was working lately on setting zones in the car and I hope that my experience can be of some benefit to Meego community.

 

The simplest form of zone division within the car environment would be:

-Zone 1: front for driver

-Zone 2: rear for passenger(s)

 

My agenda was to use basic Meego 1.1 release on Russellvile platform and explore how far would one get with just a basic configuration changes – no new packets and no code change. With this in mind I achieved simple setup that demonstrates audio and application zone dedication.

 

Audio:

-Navit audio streaming to front speakers. Speakers are attached to standard Line-Out from main automotive connector.

-Movie player audio streaming to rear headphones. These are USB headphones attached to one of 4 USB connectors.

NOTE: Audio routing was achieved manually by changing PulseAudio settings through “pacmd” tool.

You just have pair your source to desired sink.

 

Application dedication to zones. For time being both windows (front and rear zone) have the same menu. Application launch are restricted by the zone origin:

-Navit can be started only within front zone to be displayed on front

-Movie player can be started only within rear zone to be displayed on rear

-attempt to open application from non-dedicated zone will raise warning.

 

Video of the setup is shared on YouTube:

 

http://www.youtube.com/watch?v=v5TTCr3yolg

 

Best regards,

Marjan

 

--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.


_______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi-VVXm0OgCXj10cC2WI2GV6A@public.gmane.org
http://lists.meego.com/listinfo/meego-ivi



--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi@...
http://lists.meego.com/listinfo/meego-ivi
Marco Ballesio | 3 Feb 12:11 2011
Picon

Fwd: Audio-Visual zones in the car

Oh I forgot MeeGo mailing lists are somewhat "special".. Thanks Marjan
for the notice, forwarding the right way to the list..

---------- Forwarded message ----------
From: Marco Ballesio <gibrovacco@...>
Date: Wed, Feb 2, 2011 at 11:24 PM
Subject: Re: [MeeGo-ivi] Audio-Visual zones in the car
To: "Komatovic, Marjan" <marjan.komatovic@...>

Hi all,

jumping into this interesting thread even though it somewhat is not my area.

First of all, my opinion about the open question Marjan has posted in
the wiki (copied/pasted here):

"Where is IIR and/or FIR filtering best handled - GStreamer or Pulse?
GStreamer has some implementations, is that the most appropriate
place?"

The answer is "well, it depends" ;). GStreamer already comes with
plenty of filters and effects for audio ("Audio effects" aka audiofx
plugin), here you go for some references:

http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-plugin-audiofx.html

No filters of that kind exist (so far) in pulseaudio but, in case you
want to make applications agnostic for such a filtering, you'll have
to do it in the sound server, maybe implementing your own "effects"
module.

some more coins worth 5 cents below..

On Wed, Feb 2, 2011 at 2:33 PM, Komatovic, Marjan
<marjan.komatovic@...> wrote:
..snip..
>
> In regards to your question, this is something that can’t be done
> statically. We need to have some policy framework that would sit on top of
> Pulse Audio and use its stream control capability. For example, the
> “proximity” application would compete for resources (speakers) with other
> applications based on priority.

Isn't it possible to have them playing at the same time? For instance,
should the player be paused while the proximity sensor beeps on a
speaker?

> Assuming highest priority, policy framework
> would allow “proximity” application to use resources while either stopping,
> pausing other applications or just corking audio streams at source/sink
> side. To my best knowledge, that kind of policy handling capability already
> resides in Resource Management component:
> http://wiki.meego.com/images/Meego-policy-framework-developer-guide.pdf

this document is for the application developers' bookshelf, and does
not reveal too much about how to actually write an enforcement point.

In the following, keep the slides of my presentation under the eyes
(http://conference2010.meego.com/session/policy-framework-flexible-way-orchestrate-multiple-functionalities-meego-devices).

The pieces of code you might be interested into are here:

http://meego.gitorious.org/maemo-multimedia/pulseaudio-policy-enforcement

the xpolicy.conf file under the "examples" folder is an example
configuration to feed the enforcement point beast with. You'll find
there a set of elements with the "groups", "group", "device" and
"stream" tag, each of those exposing some attributes (for instance,
"cork_stream").

To understand a little more about the meaning of the tags within [..]
you'll have to switch to the policy ruleset, which instructs the
engine to decide as we wish to. This other piece is here:

http://meego.gitorious.org/maemo-multimedia/policy-settings-basic

This is a restricted set of rules for the decision point. For instance, here:

http://meego.gitorious.org/maemo-multimedia/policy-settings-basic/blobs/master/basic/policy/audio_groups.pl

you can find a declarative list of example groups and group types
(compare them with the ones in the enforcement point configuration to
understand what they're for).

Now, let's go back to xpolicy.conf and its attributes. They're
unfortunately undocumented but it's easy to guess what they do by
their name. For instance cork_stream means that applications
pertaining to the given group can be corked if needed. In case of
doubt.. use the source (and the mailing list), Luke!

Maybe I'm running too long with the email (and I recognize what I'm
writing is just an appetizer), but the last question I'd like to give
some clues about is "and how is it decided when to cork an application
group?".

Two files in the resource policy settings are of major interest for
the rule of corking we've analyzed so far:

basic/policy/policy.dres: it's the dependency resolver configuration
file. As in a Makefile (well, the syntax is not exactly as in a
Makefile, but almost the same), it declares which dependencies must be
satisfied when a given fact has changed in the store. Let's jump to
the following target:

audio_cork: $resource_owner
 $audio_cork[group] |= prolog(set_corks)

It means that when something has changed in an entry of the
resource_owner variable (see at the beginning of the file to know more
about its simple structure) it triggers the audio_cork target, which
calls the prolog rule "set_corks" and updates the state of the
audio_cork variable (again, see at the beginning of the file).

basic/policy/audio_cork.pl: here are the prolog rules executed from
the audio_cork target. The file is pretty simple, but it's in Prolog
and related to concepts and functions also defined in the dependency
resolver itself, available at:

http://meego.gitorious.org/maemo-multimedia/dres

As a leap of faith, believe me that those functions are modifying
appropriately the entries in the audio_cork variable ;). For more
details, a little more knowledge about declarative languages is needed
(not that much to be honest).

As a note of interest, the action of corking a stream modifies (as
already said) the audio_cork target, which in turn triggers the
targets "audio_actions" and "all". Well, if you go and check the code
it's easy to guess that the first one will eventually trigger a dbus
message towards the enforcement point. How? It's specified into a
Resource Policy Framework/ohm plugin (guess which one) you can
retrieve from here:

http://meego.gitorious.org/maemo-multimedia/ohm-plugins-misc

Sorry for the long email, but hopefully it gives some basic hints on
how to start hacking. Maybe we could make a wiki out of it..

Regards

Meegeo IVI multimedia question

Hi all,

I am hoping to use the Meego IVI RFS applications:

Meegosound
Meegovideo
Meegopictures

In a demo of the Meego IVI / GENIVI Apollo release here at ADIT.  At present the mouse is not visible once these apps. are started.  I have the following questions:

1) Is there any way to configure them so that the mouse is visible?
2) If not, then what are the key-strokes which I can use to operate these apps?
3) In general, is there any source of user documentation for these apps?

Many thanks in advance and Best regards

Ian Bennett

Advanced Driver Information Technology GmbH
Software Group (ADITG/SWG)
Robert-Bosch-Str. 200
31139 Hildesheim
Germany

Tel. +49 5121 49 6971
Fax +49 5121 49 6999

ibennett-Tbglbhd2jqSoSS7kgVBzIA@public.gmane.org

ADIT is a joint venture company of Robert Bosch GmbH/Robert Bosch Car Multimedia GmbH and DENSO Corporation
Sitz: Hildesheim, Registergericht: Amtsgericht Hildesheim HRB 3438
Geschaeftsfuehrung: Wilhelm Grabow, Katsuyoshi Maeda

_______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi@...
http://lists.meego.com/listinfo/meego-ivi
Clark, Joel | 4 Feb 00:31 2011
Picon

Re: Meegeo IVI multimedia question

These apps are considered “Sample/demo” quality apps in the MeeGo 1.1 IVI release.   We borrowed them unmodified from the MeeGo handset images.  So you can find a few notes on them here: http://meego.com/downloads/releases/1.1/meego-v1.1-handset

Discussion of how to use MeeGo Handset code may be found here: http://forum.meego.com/forumdisplay.php?f=7

These apps all use the MeeGoTouchFramework.  You can find discussion of this framework here: http://lists.meego.com/pipermail/meego-touch-dev/

 

We plan to replace these apps in MeeGo IVI with similar apps based on QML before the MeeGo 1.2 release in April.

 

regards

Joel

 

 

From: meego-ivi-bounces <at> lists.meego.com [mailto:meego-ivi-bounces-VVXm0OgCXj10cC2WI2GV6A@public.gmane.org] On Behalf Of Bennett, Ian (Jet; ADITG/SWG)
Sent: Thursday, February 03, 2011 7:57 AM
To: meego-ivi-VVXm0OgCXj10cC2WI2GV6A@public.gmane.org
Cc: Keppke, Sven (Auronik; ADITG/SWG); Pfohl, Andreas (c4c; ADITG/SWG); Demus, Peter (Brunel; ADITG/SWG); Khaliq, Abdul (ADITG/SWG); Maleyka, Simon (ADITG/SWG)
Subject: [MeeGo-ivi] Meegeo IVI multimedia question

 

Hi all,

I am hoping to use the Meego IVI RFS applications:

Meegosound
Meegovideo
Meegopictures

In a demo of the Meego IVI / GENIVI Apollo release here at ADIT.  At present the mouse is not visible once these apps. are started.  I have the following questions:

1) Is there any way to configure them so that the mouse is visible?
2) If not, then what are the key-strokes which I can use to operate these apps?
3) In general, is there any source of user documentation for these apps?

Many thanks in advance and Best regards

Ian Bennett

Advanced Driver Information Technology GmbH
Software Group (ADITG/SWG)
Robert-Bosch-Str. 200

31139 Hildesheim
Germany

Tel. +49 5121 49 6971
Fax +49 5121 49 6999
ibennett-Tbglbhd2jqSoSS7kgVBzIA@public.gmane.org

ADIT is a joint venture company of Robert Bosch GmbH/Robert Bosch Car Multimedia GmbH and DENSO Corporation
Sitz: Hildesheim, Registergericht: Amtsgericht Hildesheim HRB 3438
Geschaeftsfuehrung: Wilhelm Grabow, Katsuyoshi Maeda

_______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi@...
http://lists.meego.com/listinfo/meego-ivi
Nasa | 10 Feb 01:10 2011
Picon
Picon

Terminal Mode

Hi Gang,

I noted that terminal mode has been added to the packages.  Does anyone know how to use it?  The --help tag isn't
very helpful...  I have an original Droid from motorola -- which I would love to give this a go with.

Nasa
Hoffmann, Joel A | 10 Feb 01:17 2011
Picon

Re: Terminal Mode

Hi Nasa,

I don't think your Moto Droid will have the TM server software, but there is a developer kit you can buy which
includes a pre-release Nokia phone that does.  Look at
http://www.terminalmode.org/en/developer/developer-offering for details.

Joel Andrew Hoffmann 

Intel Strategic Market Development Manager
Automotive Solutions Division
Joel.A.Hoffmann@...
(248) 345-7947

-----Original Message-----
From: meego-ivi-bounces@...
[mailto:meego-ivi-bounces@...] On Behalf Of Nasa
Sent: Wednesday, February 09, 2011 7:11 PM
To: meego-ivi@...
Subject: [MeeGo-ivi] Terminal Mode

Hi Gang,

I noted that terminal mode has been added to the packages.  Does anyone know how to use it?  The --help tag isn't
very helpful...  I have an original Droid from motorola -- which I would love to give this a go with.

Nasa

_______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi@...
http://lists.meego.com/listinfo/meego-ivi
Rudolf Streif | 10 Feb 01:20 2011

Re: Terminal Mode

Hi Nasa,


It requires a phone with a terminal mode server. There are none currently that are commercially available. Nokia offers a prototype kit with a phone (http://www.nokia.com/terminalmode). You will have to sign up for the developer program.

Best regards,
Rudi

On Wed, Feb 9, 2011 at 4:10 PM, Nasa <nasa01-Wuw85uim5zDR7s880joybQ@public.gmane.org> wrote:
Hi Gang,

I noted that terminal mode has been added to the packages.  Does anyone know how to use it?  The --help tag isn't very helpful...  I have an original Droid from motorola -- which I would love to give this a go with.

Nasa

_______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi-VVXm0OgCXj10cC2WI2GV6A@public.gmane.org
http://lists.meego.com/listinfo/meego-ivi




_______________________________________________
MeeGo-ivi mailing list
MeeGo-ivi@...
http://lists.meego.com/listinfo/meego-ivi
Nasa | 10 Feb 01:46 2011
Picon
Picon

Re: Terminal Mode

Thanks Rudi,

Will look in to it...

Nasa
----- "Rudolf Streif" <rudolf.streif@...> wrote:

> Hi Nasa,
> 
> 
> It requires a phone with a terminal mode server. There are none
> currently that are commercially available. Nokia offers a prototype
> kit with a phone ( http://www.nokia.com/terminalmode ). You will have
> to sign up for the developer program.
> 
> 
> Best regards,
> Rudi
> 
> 
> On Wed, Feb 9, 2011 at 4:10 PM, Nasa < nasa01@... > wrote:
> 
> 
> Hi Gang,
> 
> I noted that terminal mode has been added to the packages. Does anyone
> know how to use it? The --help tag isn't very helpful... I have an
> original Droid from motorola -- which I would love to give this a go
> with.
> 
> Nasa
> 
> _______________________________________________
> MeeGo-ivi mailing list
> MeeGo-ivi@...
> http://lists.meego.com/listinfo/meego-ivi

Gmane