Thanks Daniel. Rolling back to kernel 4.4.0-87-generic #110-Ubuntu SMP
seemed to fix the problem. Upgrading to 4.4.0-91 also seemed to cause
other problems: My system started overheating, eventually slowed to a
crawl (i.e., over a matter of minutes after each reboot slowed to the
point of being u
Public bug reported:
Bluetooth connection to Bose Soundlink II have been fine for years.
Applied a few new updates in the last day or two --- system was
generally up to date, I don't often wait more than a week or so --- and
now I can no longer connect. Removed the device and re-paired just
fine,
@Daniel van Vugt (vanvugt): Thanks for your assistance!
I am not Mary Sherman, and I'm continuing to experience this problem,
even with the PPA and after rebooting.
I didn't subscribe to this bug, I didn't even know about it. I report
bug 1691556 and you marked it a duplicate of this one.
As I
The problem appears to be with setting up the input sink, which I
couldn't care less about. If any knows of a way for bluez / pulseaudio
to force a device to just connect as an output-only device (e.g., normal
bluetooth speaker), I think I'd be fine, as I have no problems with
numerous other bluet
@hife and @Mary Sherman (spot9019): Thanks for the speedy replies!
@hife: Thanks for describing your workaround in greater detail.
I've already tried the a2dp.py script, it doesn't fix the problem for
me. I just downloaded again the latest version and
@hife and @Mary Sherman (spot9019):
You both indicate that the latest pulse-testing ppa fixes the problem
for you.
Can you both indicate whether you are running Unity as the desktop or
KDE or perhaps some other?
I still have suspicions that there may be a permissions issue that is
specific to Un
I must unfortunately report that that the recently reported fix does not
work for me. Ubuntu 16.04 LTS connecting to Amazon Echo. Pulseaudio
1:8.0-0ubuntu3.3~xenial1, which is the latest presently available from
ppa:ubuntu-audio-dev/pulse-testing as of today.
The problem appears to result in the
Additionally, this issue also appeared along the line with Ubuntu+KDE
and apparently was easily resolved, as described in ubuntuforums.org,
[link](https://ubuntuforums.org/showthread.php?t=2318966). Quoting
another ubuntuforums.org post (also KDE),
[link](https://askubuntu.com/questions/763539/blu
I should also note that on the askubuntu.com site, I speculate that it
may just be some permission issue deep down somewhere, and why.
** Description changed:
- Pairing and coupling to Amazon Echo works, but sound is heard.
+ Pairing and coupling to Amazon Echo works, but no sound is heard.
Public bug reported:
Pairing and coupling to Amazon Echo works, but no sound is heard.
I believe the issue is related to the fact that Amazon Echo is paired as
a handset (i.e., speaker + microphone) rather than just as a speaker. I
believe the critical error is found in a dmesg line such as:
Fe
10 matches
Mail list logo
