All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: ofono@ofono.org
Subject: Re: Method "Register" with signature "oay" doesn't exist
Date: Sun, 15 May 2016 15:08:19 +0200	[thread overview]
Message-ID: <573874C3.4010001@gmail.com> (raw)
In-Reply-To: <57387336.5070809@chini.tk>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

Il 15/05/2016 15:01, Georg Chini ha scritto:
> To me it still looks like this is an issue with your dbus access 
> rights. Everything else
> looks fine - even the loopback modules are loaded but don't receive / 
> send any audio.

I would try to run all services as normal user, but it is different than 
your experience.
Your dbus policies are different than mine?

> Something else I noticed: It looks like you can't get high priority 
> and also no timer based
> scheduling for pulseaudio. This means that your audio quality will 
> probably be really bad.

It is. I've already asked to the pulseaudio guys how to improve the 
audio quality, but currently I'm still here.

> Also there are lots of other errors in the PA log. It seems that there 
> is still something
> broken in your build. Or is that due to the embedded system?

PA itself works fine with paplay and parecord. The problems rise only 
when I try to use bluetooth audio.
For example the a2dp "works" (apart the poor quality) but every time the 
stream is suspended the bluez source is released and I need to 
disconnect and reconnect again the phone to hear the audio another time.

This isn't the expected behavior, but nobody knows why this happens!

I'm fighting against these problems for over 10 days... I need to find a 
solution!
Because Buildroot compiles all packets from the sources it MUST be just 
a matter of configuration.



  reply	other threads:[~2016-05-15 13:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 10:37 Method "Register" with signature "oay" doesn't exist Marco Trapanese
2016-05-12 14:09 ` Denis Kenzior
2016-05-12 14:36   ` Marco Trapanese
2016-05-12 14:55     ` Denis Kenzior
2016-05-12 15:05       ` Marco Trapanese
2016-05-12 16:11         ` Denis Kenzior
2016-05-12 16:31           ` Marco Trapanese
2016-05-14 20:43             ` Stephan Schmolke
2016-05-15  5:46               ` Marco Trapanese
2016-05-15 10:32                 ` Georg Chini
2016-05-15 10:36                   ` Marco Trapanese
2016-05-15 10:39                     ` Georg Chini
2016-05-15 10:58                       ` Marco Trapanese
2016-05-15 11:15                         ` Georg Chini
2016-05-15 11:27                           ` Marco Trapanese
2016-05-15 11:29                             ` Marco Trapanese
2016-05-15 11:43                             ` Georg Chini
2016-05-15 12:09                               ` Marco Trapanese
2016-05-15 12:15                                 ` Georg Chini
2016-05-15 12:30                                   ` Marco Trapanese
2016-05-15 13:01                                     ` Georg Chini
2016-05-15 13:08                                       ` Marco Trapanese [this message]
2016-05-15 13:24                                         ` Georg Chini
2016-05-15 17:38                                           ` Marco Trapanese
2016-05-12 16:32           ` Marco Trapanese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=573874C3.4010001@gmail.com \
    --to=marcotrapanese@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.