RE: HFP Audio is not getting routed to USB sound card
Hello, Can you tell me which hw and phone you are using? Are you also using usb headset? I can try this out with march release, if I know your setup more precisily... br, Jaska From: IVI [ivi-boun...@lists.tizen.org] on behalf of Kirankumar Mahajan [kirankumar.maha...@igate.com] Sent: Sunday, September 21, 2014 9:45 AM To: ivi@lists.tizen.org Subject: HFP Audio is not getting routed to USB sound card Hi, We are using Intel platform on which we are running March 2014 release. We are running our Phone Dialer application which similar to Lemolo and uses OFONO DBus interfaces to get telephony services. So after we successfully pair HFP enabled phone to our IVI system with Lemolo and with our application we are able to dial to a phone number. We receive the phone call on phone to which we are dialing but after accepting the call we are not able to hear any sound. Neither from IVI side or nor from the phone to which we dialed. We also crosschecked that the phone with which we are pairing supports HFP and it is, that is why we are able to make phone call. But the A2DP sound gets routed to USB sound card properly when we are using out IVI system as A2DP sink. I came across the following reported bugs, https://bugs.tizen.org/jira/browse/TIVI-2257 https://bugs.tizen.org/jira/browse/TIVI-2257 So did crosschecked whether we have correct firmware on our HW and it is, ibt-hw-37.7.10-fw-1.80.2.3.d.bseq which is the correct version which fixes the bug in FW. The case it that we did heard HFP audio 1-2 times but we don’t know how it worked that time. Basically we followed the same steps apart from trying out with our application and Lemolo. The steps we followed, 1) Start pulse audio as app user using #paplay song 2) Pair and connect HFP enabled phone over Bluetooth using #bluetoothctl 3) Check the HFP modem using #/usr/lib/ofono/test/list-modem 4) Enable modem using #/usr/lib/ofono/test/enable-modem /hfp/org/bluez/hci0/dev_xx_xx_xx_xx_xx_xx 5) Then checked the pulse audio sources and sinks after enabling the modem using commands #pactl list sources and #pactl list sinks 6) Then dialed to a phone number using command, #/usr/lib/ofono/test/dial-number /hfp/org/bluez/hci0/dev_xx_xx_xx_xx_xx_xx $number After this I receive the call but cannot hear HFP audio. So while call ongoing I tried to link sources with sinks using, #pactl load-module module-loopback source=bluez_source.xx_xx_xx_xx_xx_xx_xx sink=alsa-output.usb-C-Media_Electronics_Inc.x pactl load-module module-loopback sink=bluez_sink.xx_xx_xx_xx_xx_xx_xx source= alsa_input. usb-C-Media_Electronics_Inc.x After doing this I just hear a noise but not the actual HFP audio. Can anyone please give some pointers or any information how we can fix this issue? Regards, Kirankumar Mahajan Project Lead --- [cid:image002.jpg@01CFD595.C0640EE0]http://www.igate.com/ Level 0,1,2,5 6, Tower III, Cyber City, Magarpatta City, Hadapsar, Pune 411013 India Phone: +91 20 3984 2000 Extn 2684 I Cell: +91 860 510 0029 I www.igate.comhttp://www.igate.com/ [cid:image005.jpg@01CF6D3C.E6CF3BC0]https://twitter.com/iGATE_Corp[cid:image010.png@01CF6D3C.E6CF3BC0]http://linkd.in/1nvzJai[cid:image007.png@01CF6D3C.E6CF3BC0]http://on.fb.me/18eFm3a[cid:image016.png@01CF6D3C.C33BB850]http://www.youtube.com/igatechannel ~~Disclaimer~~~ Information contained and transmitted by this e-mail is confidential and proprietary to IGATE and its affiliates and is intended for use only by the recipient. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or mailad...@igate.commailto:mailad...@igate.com. IGATE does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of IGATE. IGATE is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While IGATE has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about IGATE please visit www.igate.comhttp://www.igate.com.
Does qt is mandatory for Tizen IVI ?
Hi all, Link to the PTF-227 Jira: * https://bugs.tizen.org/jira/browse/PTF-227 __ Currently qt is made mandatory by automotive-message-broker (hard coded into the spec file), and so it is forced into Tizen IVI build. This is not what I understand about the Tizen IVI definition. For me, Tizen must be able to be qt free. Here is my understanding about Tizen IVI definition: Is qt mandatory to Tizen IVI ? -No Is qt optional to Tizen IVI ? -Yes On Tizen.org, Tizen IVI provides qt ? -Yes (community effort) Currently The status of Tizen IVI is: Is qt mandatory to Tizen IVI ? - de facto qt has to be built. (due to hard wired dependency with amd) My pending patches allow to make qt fully optional. A global flag actives or de-actives qt built and any qt plugins (for amb) A Review in Progress for this issue. to allow a default value to Tizen IVI config project * https://review.tizen.org/gerrit/#/c/25140/ Coupled in this review: * https://review.tizen.org/gerrit/27877 Solve all issue. Futhermore, this patches will fix Yocto built were today qt is systematicly added to the build. Regards, Ronan ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Does qt is mandatory for Tizen IVI ?
On Mon, Sep 22, 2014 at 2:07 PM, ronan ronan.lemart...@open.eurogiciel.org wrote: Hi all, Link to the PTF-227 Jira: * https://bugs.tizen.org/jira/browse/PTF-227 __ Currently qt is made mandatory by automotive-message-broker (hard coded into the spec file), and so it is forced into Tizen IVI build. That's because https://review.tizen.org/gerrit/#/c/25140/ is still pending final decision on what the flag value should be. To be honest it's not completely obvious to me what is it you are proposing. We can have %define _with_qt5 1 as long as Qt is build in Tizen:IVI OBS. Are you proposing Qt should be deleted from the project? If we decide to remove Qt from Tizen:IVI, then the flag shall be %define _with_qt5 0 Thus, as long as QT libs are in the repo, AMB can enable it's Qt based plugins too. -- Mikko ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Does qt is mandatory for Tizen IVI ?
On Monday 22 September 2014 15:04:36 Ylinen, Mikko wrote: Thus, as long as QT libs are in the repo, AMB can enable it's Qt based plugins too. The build should always enable the Qt libs and the AMB plugins using Qt. The plugins should be packaged in a separate .rpm from the rest of AMB plugins. If some IVI customer does not want Qt installed, they won't install neither Qt nor the plugins. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Does qt is mandatory for Tizen IVI ?
Thiago, the problem is not to disable qt in the tizen.org but to allow the system to be consistent when a platform developer creates its own platform and rebuild his own Tizen without requiring qt With the current model anyone needs to rebuild qt even if not used. In particular in the Tizen-Meta when building with Yocto, it adds a serious extra time for building even if not used. Ronan's proposition is simply to allow by a configuration to request not to build qt if not required. It will have no effect on the the tizen.org build or images, but will allow to seriously optimise the build time when a local build of Tizen is required and qt not desired (in particular when using Yocto). Regards Dominig Le 22/09/2014 16:36, Thiago Macieira a écrit : On Monday 22 September 2014 15:04:36 Ylinen, Mikko wrote: Thus, as long as QT libs are in the repo, AMB can enable it's Qt based plugins too. The build should always enable the Qt libs and the AMB plugins using Qt. The plugins should be packaged in a separate .rpm from the rest of AMB plugins. If some IVI customer does not want Qt installed, they won't install neither Qt nor the plugins. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Does qt is mandatory for Tizen IVI ?
Le 22/09/2014 13:25, Counihan, Tom a écrit : . Quoting from the JIRA record: ◾Tizen IVI should be only HTML5 only. Today IVI official AppFW framework is HTML5. It is public knowledge that Native App are currently only supported by Mobile App and the extension to other Tizen profiles is not yet officially available. ◾qt5 (or just qt) should be optional for Tizen IVI. qt is not included in Tizen mandatory compliance list. We provide it as a a shared tool which is optional. Is the position taken on Qt consistent with the position to be taken on EFL? Bullet 1 would seem to imply yes, but a confirmation would be beneficial for clarity. Technically, Tizen FW has still some low level dependencies on EFL (in particular for the management of the main loop). At technical level those dependencies are quite easy to be removed what would enable to build a Tizen without EFL, as the Crosswalk WRT has no dependency on EFL. But as today that was not required. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Does qt is mandatory for Tizen IVI ?
On Mon, Sep 22, 2014 at 5:48 PM, Dominig ar Foll dominig.arf...@fridu.net wrote: Thiago, the problem is not to disable qt in the tizen.org but to allow the system to be consistent when a platform developer creates its own platform and rebuild his own Tizen without requiring qt With the current model anyone needs to rebuild qt even if not used. In particular in the Tizen-Meta when building with Yocto, it adds a serious extra time for building even if not used. Ronan's proposition is simply to allow by a configuration to request not to build qt if not required. This part is obvious. What's not is why the OBS config needs to be %define _with_qt5 0 even if the Qt libs are there. -- Mikko ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Does qt is mandatory for Tizen IVI ?
On Mon, Sep 22, 2014 at 8:02 AM, Ylinen, Mikko mikko.yli...@intel.com wrote: On Mon, Sep 22, 2014 at 5:48 PM, Dominig ar Foll dominig.arf...@fridu.net wrote: Thiago, the problem is not to disable qt in the tizen.org but to allow the system to be consistent when a platform developer creates its own platform and rebuild his own Tizen without requiring qt With the current model anyone needs to rebuild qt even if not used. In particular in the Tizen-Meta when building with Yocto, it adds a serious extra time for building even if not used. Ronan's proposition is simply to allow by a configuration to request not to build qt if not required. This part is obvious. What's not is why the OBS config needs to be %define _with_qt5 0 even if the Qt libs are there. If the Qt libs are there, we should %define _with_qt5 1 so that developers can use the AMB plugins that use Qt if they want (optional). If someone wants to build all tizen packages without Qt, they can %define _with_qt5 0. By default it should be ON because developers want/need those optional packages and shouldn't have to rebuild AMB to get them. So I'm with Mikko on this one. --Kevron -- Mikko ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
Re: Does qt is mandatory for Tizen IVI ?
Hi all, This part is obvious. What's not is why the OBS config needs to be %define _with_qt5 0 even if the Qt libs are there. If the Qt libs are there, we should %define _with_qt5 1 so that developers can use the AMB plugins that use Qt if they want (optional). If someone wants to build all tizen packages without Qt, they can %define _with_qt5 0. By default it should be ON because developers want/need those optional packages and shouldn't have to rebuild AMB to get them. So I'm with Mikko on this one. --Kevron -- Mikko Yes, I'm fully agreed with you too. _with_qt5 should be set to 1 This is why my review do that: * https://review.tizen.org/gerrit/#/c/25140/5/Tizen:IVI/_config Please can you read and check the review . * https://review.tizen.org/gerrit/#/c/25140/ Thanks Regards, Ronan ___ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
