Skype over bluetooth? (yes, I have googled!)

[H.S.]

Dotan Cohen wrote:

> 
> No change in playback volume.


So controlling the playback device of 'bluetooth' device does not change
the playback volume? That doesn't sound right (no pun intended). Just
verify that the input level (mic's) is not muted and is more than say 60%.


>>>
>> I think the command is taking the device name from your .asoundrc. What
>> happens if you move that file out of the way?
>>
>>
> 
> I will remove that file, reboot, and report back.
> 

I don't think you need to reboot. Why do you think you need to reboot? I
mean, did you read it anywhere in some documentation? I would be
interested to know.

When you have done the previous experiment without the .asoundrc, there
is one more thing I would like you to try.

Here is what I am doing at a Ubuntu machine. It has an M-audiophile card
listed as (using the 'arecord -l' command):
card 1: M2496 [M Audio Audiophile 24/96], device 0: ICE1712 multi
[ICE1712 multi]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I don't have a .asoundrc file. But I can successfully record using the
following command:
$ cat rec-at-job.txt
 arecord -D plug:hw:1 --duration=6300 --file-type raw  -f cd --nonblock
 ./`date +%Y%m%d-%H%M%S`.raw

(this just records the input in CD format to filename based on the time
the command is given).

The key point to note is the device: -D plug:hw:1

In your case, use the arecord command using the appropriate number in
the corresponding device name. See if you can still play an audio file
(using aplay) and if you can then record some sound from it (using
arecord).

Regars.

-- 

Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.