[MeeGo IVI] Calling all IVI architects/designers - navigation API proposal / draft

[Simon Bolek]

5. **Application framework definition and implementation of

navigation APIs extending (if needed) the existing QML location APIs to

support open source (i.e. Navit) and proprietary automotive navigation

applications.

I began to create api for navigation, look here
http://wiki.meego.com/In-vehicle/Roadmap/FeatureScope#Navigation

these 2 are still @work:
http://wiki.meego.com/In-vehicle/Roadmap/API#API_Functional_Groups_and_Functions
http://wiki.meego.com/In-vehicle/Roadmap/Navigation

Does this meet your expectations / requirements? Or should it evolve in a
different direction?

I am still looking into QML Location API, whether it has to be extended or
not.

cheers
simon:)

mit freundlichem Gruss / best regards / pozdrawiam / atentamente
Simon P. Bolek
------------------------------------------------------
Dipl. Inf. Simon P. Bolek
SAP Consultant
Business Mobile and IVI Solutions
Cell: [phone]
mailto: simon.bolek-B9s5scSTfCld/oRx+***@public.gmane.org
http://www.arcom-ivi.de/
XING: https://www.xing.com/profile/SimonP_Bolek
GULP: 84465

[Konopelko, Pavel (P.)]

Simon,

5. Application framework definition and

implementation of navigation APIs extending (if needed) the
existing QML location APIs to

support open source (i.e. Navit) and proprietary

automotive navigation applications.
I began to create api for navigation, look here
http://wiki.meego.com/In-vehicle/Roadmap/FeatureScope#Navigation
http://wiki.meego.com/In-vehicle/Roadmap/API#API_Functional_Gr
oups_and_Functions http://wiki.meego.com/In-vehicle/Roadmap/Navigation
Does this meet your expectations / requirements? Or should it
evolve in a different direction?

Are you proposing this API as a part of the 'Qt IVI' (i.e. access to
vehicle specific data and functionality) or rather as a separate
extension to Qt Mobility (e.g. the Location API or a new one)? The
location of the proposal on the Wiki suggests the former. However,
since navigation is a reasonable feature for other verticals as well,
the latter seems more reasonable to me.

Other than that, the API itself seems to go in the right direction.


Regards,
--Pavel Konopelko

I am still looking into QML Location API, whether it has to
be extended or not.
cheers
simon:)
mit freundlichem Gruss / best regards / pozdrawiam / atentamente Simon
P. Bolek ------------------------------------------------------ Dipl.
Inf. Simon P. Bolek SAP Consultant
Business Mobile and IVI Solutions
Cell: [phone] <tel:%2B49%20%28177%29%2067%2036%20556>
http://www.arcom-ivi.de/
XING: https://www.xing.com/profile/SimonP_Bolek
GULP: 84465

[Simon Bolek]

Pavel,

Are you proposing this API as a part of the 'Qt IVI' (i.e. access to

Post by Konopelko, Pavel (P.)
vehicle specific data and functionality) or rather as a separate
extension to Qt Mobility (e.g. the Location API or a new one)? The
location of the proposal on the Wiki suggests the former. However,
since navigation is a reasonable feature for other verticals as well,
the latter seems more reasonable to me.

Of course not a part of Automotive API itself. Is should, similar to
communication and multimedia, share Qt Mobility. At the moment it is just on
the same Wiki page. At the moment I am analyzing Location API to figure out
the best way of incorporating the proposed navigation API into Location API
(extend it / inherit from / new one / combination of these).


Other than that, the API itself seems to go in the right direction.

Good to hear, thanks.

best regards
Simon:)


mit freundlichem Gruss / best regards / pozdrawiam / atentamente
Simon P. Bolek
------------------------------------------------------
Dipl. Inf. Simon P. Bolek
SAP Consultant
Business Mobile and IVI Solutions
Cell: [phone]
mailto: simon.bolek-B9s5scSTfCld/oRx+***@public.gmane.org
http://www.arcom-ivi.de/
XING: https://www.xing.com/profile/SimonP_Bolek
GULP: 84465

Post by Konopelko, Pavel (P.)
Pavel,
Are you proposing this API as a part of the 'Qt IVI' (i.e. access to

Post by Konopelko, Pavel (P.)
vehicle specific data and functionality) or rather as a separate
extension to Qt Mobility (e.g. the Location API or a new one)? The
location of the proposal on the Wiki suggests the former. However,
since navigation is a reasonable feature for other verticals as well,
the latter seems more reasonable to me.

Of course not a part of Automotive API itself. Is should, similar to
communication and multimedia, share Qt Mobility. At the moment it is just on
the same Wiki page. At the moment I am analyzing Location API to figure out
the best way of incorporating the proposed navigation API into Location API
(extend it / inherit from / new one / combination of these).
Other than that, the API itself seems to go in the right direction.
Good to hear, thanks.
best regards
Simon:)
mit freundlichem Gruss / best regards / pozdrawiam / atentamente
Simon P. Bolek
------------------------------------------------------
Dipl. Inf. Simon P. Bolek
SAP Consultant
Business Mobile and IVI Solutions
Cell: [phone]
http://www.arcom-ivi.de/
XING: https://www.xing.com/profile/SimonP_Bolek
On Tue, Jul 12, 2011 at 4:24 PM, Konopelko, Pavel (P.) <

Post by Konopelko, Pavel (P.)
Simon,

5. Application framework definition and

implementation of navigation APIs extending (if needed) the
existing QML location APIs to

support open source (i.e. Navit) and proprietary

automotive navigation applications.
I began to create api for navigation, look here
http://wiki.meego.com/In-vehicle/Roadmap/FeatureScope#Navigation
http://wiki.meego.com/In-vehicle/Roadmap/API#API_Functional_Gr
oups_and_Functions http://wiki.meego.com/In-vehicle/Roadmap/Navigation
Does this meet your expectations / requirements? Or should it
evolve in a different direction?

Are you proposing this API as a part of the 'Qt IVI' (i.e. access to
vehicle specific data and functionality) or rather as a separate
extension to Qt Mobility (e.g. the Location API or a new one)? The
location of the proposal on the Wiki suggests the former. However,
since navigation is a reasonable feature for other verticals as well,
the latter seems more reasonable to me.
Other than that, the API itself seems to go in the right direction.
Regards,
--Pavel Konopelko

I am still looking into QML Location API, whether it has to
be extended or not.
cheers
simon:)
mit freundlichem Gruss / best regards / pozdrawiam / atentamente Simon
P. Bolek ------------------------------------------------------ Dipl.
Inf. Simon P. Bolek SAP Consultant
Business Mobile and IVI Solutions
Cell: [phone] <tel:%2B49%20%28177%29%2067%2036%20556>
http://www.arcom-ivi.de/
XING: https://www.xing.com/profile/SimonP_Bolek
GULP: 84465

[DK]

Hi, All



Does anyone know that why MIC recording is too low at OKI board



We were tentatively using below script via alsa recording just to see if
recording level is properly done.

arecord -D hw:0,0 -d 3 -f S16_LE -c 2 -r 44100 test.wav

However when we listen to ¡°test.wav¡± this volume is too low, so hardly
can not hear sound due to low amplitude.

I¡¯d like to know how to adjust volume in order to get enough volume

Please advise me so that we can get a enough volume at OKI board



Thanks, DK

[Clark, Joel]

It seems like there are still a few problems with the OKI board drivers. For example https://bugs.meego.com/show_bug.cgi?id=17137. You may need to ask OKI for help with this.

regards
Joel



From: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-bounces-VVXm0OgCXj2zQB+***@public.gmane.orggo.com] On Behalf Of DK
Sent: Thursday, July 14, 2011 1:20 AM
To: meego-ivi-***@public.gmane.org; meego-dev-bounces-***@public.gmane.org; meego-ivi-bounces-***@public.gmane.org
Subject: [MeeGo-ivi] [MeeGo IVI] Mic recording is too low at OKI board

Hi, All

Does anyone know that why MIC recording is too low at OKI board

We were tentatively using below script via alsa recording just to see if recording level is properly done.

arecord -D hw:0,0 -d 3 -f S16_LE -c 2 -r 44100 test.wav

However when we listen to "test.wav" this volume is too low, so hardly can not hear sound due to low amplitude.
I'd like to know how to adjust volume in order to get enough volume
Please advise me so that we can get a enough volume at OKI board

Thanks, DK

[O'carroll, David T]

Hi DK,

Have you tried changing the volume settings using alsamixer? Just type alsamixer in a terminal and it should open up a graphical volume control for audio I/O devices.

Hope this helps,
Dave

From: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-bounces-VVXm0OgCXj2zQB+***@public.gmane.orggo.com] On Behalf Of DK
Sent: Thursday, July 14, 2011 9:20 AM
To: meego-ivi-***@public.gmane.org; meego-dev-bounces-***@public.gmane.org; meego-ivi-bounces-***@public.gmane.org
Subject: [MeeGo-ivi] [MeeGo IVI] Mic recording is too low at OKI board

Hi, All

Does anyone know that why MIC recording is too low at OKI board

We were tentatively using below script via alsa recording just to see if recording level is properly done.

arecord -D hw:0,0 -d 3 -f S16_LE -c 2 -r 44100 test.wav

However when we listen to "test.wav" this volume is too low, so hardly can not hear sound due to low amplitude.
I'd like to know how to adjust volume in order to get enough volume
Please advise me so that we can get a enough volume at OKI board

Thanks, DK
--------------------------------------------------------------
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.

[DK]

Yes, we already did it, but even 100% MIC in volume setting, ther recorded
volume is too low, I think that this is OKI related driver problem itself



Thanks, DK



From: O'carroll, David T [mailto:david.t.o'carroll-***@public.gmane.org]
Sent: Thursday, July 14, 2011 6:50 PM
To: DK; meego-ivi-***@public.gmane.org; meego-dev-bounces-***@public.gmane.org; meego-ivi-
bounces-***@public.gmane.org
Subject: RE: [MeeGo-ivi] [MeeGo IVI] Mic recording is too low at OKI board



Hi DK,



Have you tried changing the volume settings using alsamixer? Just type
alsamixer in a terminal and it should open up a graphical volume control
for audio I/O devices.



Hope this helps,

Dave



From: meego-ivi-bounces-***@public.gmane.org [mailto:meego-ivi-
bounces-***@public.gmane.org] On Behalf Of DK
Sent: Thursday, July 14, 2011 9:20 AM
To: meego-ivi-***@public.gmane.org; meego-dev-bounces-***@public.gmane.org; meego-ivi-
bounces-***@public.gmane.org
Subject: [MeeGo-ivi] [MeeGo IVI] Mic recording is too low at OKI board



Hi, All



Does anyone know that why MIC recording is too low at OKI board



We were tentatively using below script via alsa recording just to see if
recording level is properly done.

arecord -D hw:0,0 -d 3 -f S16_LE -c 2 -r 44100 test.wav

However when we listen to ¡°test.wav¡± this volume is too low, so hardly
can not hear sound due to low amplitude.

I¡¯d like to know how to adjust volume in order to get enough volume

Please advise me so that we can get a enough volume at OKI board



Thanks, DK

--------------------------------------------------------------
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.