03-06-2019, 03:41 AM
@kaymes
Interesting thread, especially with the stackoverflow post you found. I need to do my homework on this one.
BlueTooth in Linux today feels as sketchy to me as WiFi used to back in the kernel 2.x days. It's getting better but moOde (and all its competitors) are very dependent on developments outside the project.
Case in point: the clash between pulseaudio and bluez-alsa regarding what the A2DP spec says about RTP payload type. That problem's been known for several years. Looks like the fix was finally accepted into pulseaudio master just a month ago. We are in the midst of another such clash between the mpd developer and the bluez-alsa developer regarding their readings of the alsa specs. No progress yet on this one.
None of my Android devices have a BT pairing/connecting problem with moOde but they are all pure Google Android, e.g., Nexus tablets and phone. From time to time others have reported problems with old, third-party Android devices. AFAIK, Tim and others have not had problems with iOS devices.
For the record, what is the Android phone you are using? And what version of Android?
As an aside, I am curious about your problem with ssh, something I've never come across (assuming sshd is running and the appropriate port is open). I would have suggested it might be your router blocking client-to-client communication but you say the problem arises only when ssh invokes a pseudo-terminal. What makes you think it might be your WiFi or MTU? Have you tried a wired Ethernet connection to prove or disprove this conjecture?
Regards,
Kent
Interesting thread, especially with the stackoverflow post you found. I need to do my homework on this one.
BlueTooth in Linux today feels as sketchy to me as WiFi used to back in the kernel 2.x days. It's getting better but moOde (and all its competitors) are very dependent on developments outside the project.
Case in point: the clash between pulseaudio and bluez-alsa regarding what the A2DP spec says about RTP payload type. That problem's been known for several years. Looks like the fix was finally accepted into pulseaudio master just a month ago. We are in the midst of another such clash between the mpd developer and the bluez-alsa developer regarding their readings of the alsa specs. No progress yet on this one.
None of my Android devices have a BT pairing/connecting problem with moOde but they are all pure Google Android, e.g., Nexus tablets and phone. From time to time others have reported problems with old, third-party Android devices. AFAIK, Tim and others have not had problems with iOS devices.
For the record, what is the Android phone you are using? And what version of Android?
As an aside, I am curious about your problem with ssh, something I've never come across (assuming sshd is running and the appropriate port is open). I would have suggested it might be your router blocking client-to-client communication but you say the problem arises only when ssh invokes a pseudo-terminal. What makes you think it might be your WiFi or MTU? Have you tried a wired Ethernet connection to prove or disprove this conjecture?
Regards,
Kent
