Re: [alsa-devel] No sound from usb on Motorola C350 cellphone
With an old copy of motorola driver, the usb sound device was recognized by windows XP, with mixer elements only for the playback. I was not able to record from it, playing give no errors, but no sound either
With the last copy of driver from motorola developer devsite, on XP a whole new "Motorola Device" is created, with the audio interface listed on it in the usb control panel, but no audio device is available for normal usage.
Needs more info, tests?
On Nov 12, 2007 2:50 PM, Alexander E. Patrakov patrakov@gmail.com wrote:
Giovanni Maruzzelli wrote:
Maybe there is a way to not using soundcards, that would be *so* much better: I found that Motorola c350 phones after receiving an AT+MODE=8 command via USB, make available an usb sound device.
Confirmed with my Motorola C350 cellphone. It appears to accept S16_LE, MU_LAW and A_LAW formats, 8 kHz sample rate, but actually records no data and plays no sounds (even if a cal is in progress).
One question: what playback and recording functionality is available on this cellphone under Windows?
-- Alexander E. Patrakov
Giovanni Maruzzelli wrote:
Needs more info, tests?
If you can make the audio functionality work under Windows 2000 or XP with the new (non-standard) driver, snoopy logs will be interesting. Snoopy is available from http://www.wingmanteam.com/usbsnoopy/ or (different version) http://sourceforge.net/projects/usbsnoop/
Hi All;
I think this is a totally fascinating thing and i hope it will be possible to make it work.....
onto the specifics
On Mon, 12 Nov 2007 19:14:06 +0500 "Alexander E. Patrakov" patrakov@gmail.com wrote:
Giovanni Maruzzelli wrote:
Needs more info, tests?
If you can make the audio functionality work under Windows 2000 or XP with the new (non-standard) driver, snoopy logs will be interesting. Snoopy is available from http://www.wingmanteam.com/usbsnoopy/ or (different version) http://sourceforge.net/projects/usbsnoop/
i am not staring at the USB code right now (it's on a different box), but i would think that one of the first things that you might need to uncover is the USB device string. It may be offered up as part of the device probe when it's attached (check in dmesg) or you may find it in a registry or .inf file on the windows file system after you install the drivers.
if it's a class compliant device, then it may just work once alsa get's taught about it (dont hold me to that, i am not looking at code)
however, as one of you alluded to, there may be an AT command that needs to get tickled to turn it on.
the other annoying thing to consider is that it may actually be probe and connected, but you havent yet figured out how to turn up the volume :-( (yes, that happens)
i'll be really curious about this, so please continue to share with the list....
tnx!
johnu
Johnu,
device string, and all the "usual" kind of detailed informations are in the files contained by the compressed archive you can download at: http://www.celliax.org/c350_usb_sound.tgz (lsusb -vv before and after, stream0, etc etc).
maybe there is need for a quirk in snd_usb_audio ?
the problem is that the device appear to works, but do not captures or plays samples.
On Nov 12, 2007 7:39 PM, John Utz john.utz@dmx.com wrote:
Hi All;
I think this is a totally fascinating thing and i hope it will be possible to make it work.....
onto the specifics
On Mon, 12 Nov 2007 19:14:06 +0500 "Alexander E. Patrakov" patrakov@gmail.com wrote:
Giovanni Maruzzelli wrote:
Needs more info, tests?
If you can make the audio functionality work under Windows 2000 or XP with the new (non-standard) driver, snoopy logs will be interesting. Snoopy is available from http://www.wingmanteam.com/usbsnoopy/ or (different version) http://sourceforge.net/projects/usbsnoop/
i am not staring at the USB code right now (it's on a different box), but i would think that one of the first things that you might need to uncover is the USB device string. It may be offered up as part of the device probe when it's attached (check in dmesg) or you may find it in a registry or .inf file on the windows file system after you install the drivers.
if it's a class compliant device, then it may just work once alsa get's taught about it (dont hold me to that, i am not looking at code)
however, as one of you alluded to, there may be an AT command that needs to get tickled to turn it on.
the other annoying thing to consider is that it may actually be probe and connected, but you havent yet figured out how to turn up the volume :-( (yes, that happens)
i'll be really curious about this, so please continue to share with the list....
tnx!
johnu
Giovanni,
I agree with John, this sounds very interesting; I have been looking to do something at least remotely related to this, but standalone (though perhaps I've misunderstood the purpose of your software completely). I've been searching for a way to use a host PC as a handsfree/speakerphone for my v3/v3x via bluetooth. The closest I've come is the software at: http://wall4.soft.uni-linz.ac.at/_wiki/tiki-index.php?page=ProjectBluezHands...
...but I only once got it to partly work with my V3 (very little audio, and all broken up) and no audio at all with my V3x. It seems the links to the tarballs are dead though so if anyone wants them I think I can find them somewhere on my computer.
I have tried sending the 'AT+MODE=8' command to my phone and it indeed does trigger a change in the USB state: it disconnects and attempts to reconnect, but fails.
Also I don't mean to flood the list with something that might be considered offtopic so unless someone feels any of what I've said is relevant this will be my first and last post.
Cheers, Jesse Burt
On Mon, 2007-11-12 at 10:39 -0800, John Utz wrote:
Hi All;
I think this is a totally fascinating thing and i hope it will be possible to make it work.....
onto the specifics
On Mon, 12 Nov 2007 19:14:06 +0500 "Alexander E. Patrakov" patrakov@gmail.com wrote:
Giovanni Maruzzelli wrote:
Needs more info, tests?
If you can make the audio functionality work under Windows 2000 or XP with the new (non-standard) driver, snoopy logs will be interesting. Snoopy is available from http://www.wingmanteam.com/usbsnoopy/ or (different version) http://sourceforge.net/projects/usbsnoop/
i am not staring at the USB code right now (it's on a different box), but i would think that one of the first things that you might need to uncover is the USB device string. It may be offered up as part of the device probe when it's attached (check in dmesg) or you may find it in a registry or .inf file on the windows file system after you install the drivers.
if it's a class compliant device, then it may just work once alsa get's taught about it (dont hold me to that, i am not looking at code)
however, as one of you alluded to, there may be an AT command that needs to get tickled to turn it on.
the other annoying thing to consider is that it may actually be probe and connected, but you havent yet figured out how to turn up the volume :-( (yes, that happens)
i'll be really curious about this, so please continue to share with the list....
tnx!
johnu
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
participants (4)
-
Alexander E. Patrakov -
Giovanni Maruzzelli -
Jesse Burt -
John Utz