Moving this thread to [hardware] from [community], as it's a hw-related technical problem. Eventually I will merge the similar thread from [support]-ml
All further discussion, status-reports etc will be supported by me solely here in [hw]-ml. Please don't continue the threads in the other both lists cheers jOERG
--- Begin Message ---Has there been any progress on the GSM interference issue (bug #883)? As I understand it, this is the current condition (please correct anything that is wrong): -only some people seem to have a problem with it -the buzzing is only heard by people on the other end -it is a hardware issue -it is being looked in to by the OpenMoko team -it is affected by how much power the FR is having to use to reach the tower (i.e. better signal strength -> less buzzing) Has anyone gotten a bluetooth headset (SCO type) to work with the 2007.2 distro for making calls? If so, how did you do it, and did it fix this interference issue? This issue is the only thing keeping me from using my FR as my primary phone. Josh _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---> Has anyone gotten a bluetooth headset (SCO type) to work with the 2007.2 > distro for making calls? nope. i asked a while ago since i understood that there's a direct connection between bt and the gsm chip for this purpose (no need for alsa and it's missing state-file), but never got a reply. bt audio seems the be rather orphaned -- the bluetoothsomething.state file for alsa is missing completely and even questions regarding the state of bt audio at all were not answered. > If so, how did you do it, and did it fix this > interference issue? the buzzing is canceled when the fr's mic is set to 0 -- so my expectation was by using a wireless headset to circumvent the issue (wired headset buzzes far louder than the fr itself). but see above ... _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: |> Has anyone gotten a bluetooth headset (SCO type) to work with the 2007.2 |> distro for making calls? | | nope. i asked a while ago since i understood that there's a direct | connection between bt and the gsm chip for this purpose (no need for alsa | and it's missing state-file), but never got a reply. | bt audio seems the be rather orphaned -- the bluetoothsomething.state file | for alsa is missing completely and even questions regarding the state of | bt audio at all were not answered. You'll need something like the Alsa state file to configure internal routing to make the connections. |> If so, how did you do it, and did it fix this |> interference issue? | | the buzzing is canceled when the fr's mic is set to 0 -- so my expectation | was by using a wireless headset to circumvent the issue (wired headset | buzzes far louder than the fr itself). but see above ... AFAIK in hardware this should be possible -- BT audio comes in on "VX" digital interface of WM8753 and there should be a path to get in and out of that to RXN/P pair and MONO1/2 pair. It's actually an interesting test to do it... AFAIK nobody proved that whatever makes the buzz (RF coupling or direct conduction from PSU rail for example) does not infect Vref on the Codec, in which case more paths than the mic might be infected as well because their reference is. So whether this is clean or not will be a clue. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiXNdQACgkQOjLpvpq7dMrMlgCfRlJjFDhieoesVrczBZY5ze/y TJEAniBGCWZfqCf6ejtS8Rjx2fxd6i3x =z2Vl -----END PGP SIGNATURE----- _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---On Monday August 04, 2008, Andy Green wrote: > AFAIK in hardware this should be possible -- BT audio comes in on "VX" > digital interface of WM8753 and there should be a path to get in and out > of that to RXN/P pair and MONO1/2 pair. So, I found this: http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem Now, I'm starting to understand what a lot of those setting in alsamixer mean. Does anyone know how much of the "ALSA Channels" diagram has changed for the FR? It seems there are 3 steps to getting a bluetooth headset to work for making calls. 1) connect the headset to the phone 2) route the audio correctly through the WM8753 so that it runs between the bluetooth device and the GSM. 3) configure the PCM coming from the WM8753 to be the right format for going to the bluetooth device. Directions for step 1 seem to be here: http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Headset_Audio Although, I'm not sure how the python script plays into things. Direction for step 2 seem to be on the audio subsystem page listed above using the asound.state file (http://opensource.wolfsonmicro.com/%7Egg/neo1973/gsmbluetooth.state) as a starting point. I guess step 3 is solved with the bluetooth_pcm.c file that is linked to on the same page. Unfortunately, I don't have much time to work on this. Hopefully, this will help someone else move things along. Josh _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---On Tuesday 05 August 2008, Josh Thompson wrote: > On Monday August 04, 2008, Andy Green wrote: > > AFAIK in hardware this should be possible -- BT audio comes in on "VX" > > digital interface of WM8753 and there should be a path to get in and out > > of that to RXN/P pair and MONO1/2 pair. > > So, I found this: > > http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem > > Now, I'm starting to understand what a lot of those setting in alsamixer > mean. Does anyone know how much of the "ALSA Channels" diagram has changed > for the FR? I drew up the "ALSA Channels" referring to the FR as I thought the audio subsystems were more or less identical. If there are differences then it should be moved to a different page, or the differences noted, but I don't have a Neo1973 so I can't check. _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---> You'll need something like the Alsa state file to configure internal > routing to make the connections. i tried the existing gta01 one, but it claimed some incompatibilites (besides the wrong naming in line 1) and did not help anything. > AFAIK in hardware this should be possible -- BT audio comes in on "VX" > digital interface of WM8753 and there should be a path to get in and out > of that to RXN/P pair and MONO1/2 pair. it's all bohemian villages to me as we in german say (i think, it's "hekuba" in shakespeare somewhere :-) > It's actually an interesting test to do it... AFAIK nobody proved that > whatever makes the buzz (RF coupling or direct conduction from PSU rail > for example) does not infect Vref on the Codec, in which case more paths > than the mic might be infected as well because their reference is. So > whether this is clean or not will be a clue. i am willing to test -- but how to make the fr play w/ the headset is absolutely beyond my understanding. i found alsa (and the whole audio stuff in fact) always pretty confusing and am happy if c&p helps me with any related problems ... _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---Josh Thompson wrote: > Has there been any progress on the GSM interference issue (bug #883)? As I > understand it, this is the current condition (please correct anything that is > wrong): > > -the buzzing is only heard by people on the other end I get buzzing at both ends of the call. > Has anyone gotten a bluetooth headset (SCO type) to work with the 2007.2 I was able to pair with a headset using the QTopia UI, however no audio came out, as I guess there is no alsa state file being applied. I have to say that after all this time it is surprising no one has been able to demonstrate a BT headset working, as this is a fundamental functionality for a phone in states that require handsfree whilst driving. -- Jim Morris, http://blog.wolfman.com _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---I'm also very concerned with the GSM buzzing. This post mentions that the issue was present in GTA01 and looks like it carried over to GTA02. http://lists.openmoko.org/pipermail/community/2008-January/012382.html The issue has been around for quite some time now. Can anyone from OM comment on the status or possibly any testing those of us who are experiencing the buzz can do to help investigate this issue? I'm spinning my wheels trying to debug and not sure where to go next. I realize it's most likely a complex bug with lots of variables but it would be great to get an idea of what information/testing/output would be most helpful to the hardware guys in determining the cause of the interference. --Andrew > Josh Thompson wrote: > >> Has there been any progress on the GSM interference issue (bug #883)? As I >> understand it, this is the current condition (please correct anything that is >> wrong): >> -the buzzing is only heard by people on the other end > > I get buzzing at both ends of the call. > > > Has anyone gotten a bluetooth headset (SCO type) to work with the > 2007.2 > > I was able to pair with a headset using the QTopia UI, however no audio came out, as I guess there > is no alsa state file being applied. I have to say that after all this time it is surprising no one > has been able to demonstrate a BT headset working, as this is a > fundamental functionality for a > phone in states that require handsfree whilst driving. > > > -- > Jim Morris, http://blog.wolfman.com > > _______________________________________________ > Openmoko community mailing list > [EMAIL PROTECTED] > http://lists.openmoko.org/mailman/listinfo/community > > _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---http://gadgets.boingboing.net/2008/08/02/kill-gsm-radio-buzz.html Maybe that could provide a less invasive means to getting rid of the problem? _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---> http://gadgets.boingboing.net/2008/08/02/kill-gsm-radio-buzz.html > Maybe that could provide a less invasive means to getting rid of the > problem? jOERG proposed using a ferrite bead on the wired headset a while ago in a german forum (freeyourphone.de or so). i am still trying to find one which is capable to be put on the included headset non-destructive (both the bead and the headset). ps: i was still under impression, the bead has to fit _around_ the cable -- the page says, it can be attached simple with tape as well. has someone a link explaining exactly what kind of voodoo that thing does? has it to have a hole? _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---On Tuesday 05 August 2008, arne anka wrote: > > http://gadgets.boingboing.net/2008/08/02/kill-gsm-radio-buzz.html > > Maybe that could provide a less invasive means to getting rid of the > > problem? > > jOERG proposed using a ferrite bead on the wired headset a while ago in a > german forum (freeyourphone.de or so). > i am still trying to find one which is capable to be put on the included > headset non-destructive (both the bead and the headset). > > ps: i was still under impression, the bead has to fit _around_ the cable > -- the page says, it can be attached simple with tape as well. > has someone a link explaining exactly what kind of voodoo that thing does? > has it to have a hole? The ferrite is increasing the common mode inductance of the cable because the ferrite has a better magnetic permeability than air. Taping the ferrite to the cable is a bit like a half turn on a ferrite rod. It will still affect the inductance, but not as much as if it went through a ferrite ring. _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---> The ferrite is increasing the common mode inductance of the cable > because the > ferrite has a better magnetic permeability than air. Taping the ferrite > to > the cable is a bit like a half turn on a ferrite rod. It will still > affect > the inductance, but not as much as if it went through a ferrite ring. anything to pay attention to in particular (size, color, taste or smell ;-) or just using one that fits? _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
--- Begin Message ---On Tuesday 05 August 2008, arne anka wrote: > > The ferrite is increasing the common mode inductance of the cable > > because the > > ferrite has a better magnetic permeability than air. Taping the ferrite > > to > > the cable is a bit like a half turn on a ferrite rod. It will still > > affect > > the inductance, but not as much as if it went through a ferrite ring. > > anything to pay attention to in particular (size, color, taste or smell > ;-) or just using one that fits? Given the less-than-scientific application, probably just one that fits ;-) My electronics experience doesn't go beyond audio frequencies though, so don't believe a word I say once it involves RF! _______________________________________________ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community
--- End Message ---
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ hardware mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/hardware
