Skip to main content

linux 连接 蓝牙 手机

参考：http://blog.flyingdream.net.cn/2007/%E5%9C%A8-ubuntu-linux-%E4%B8%8B%E5%88%A9%E7%94%A8%E8%93%9D%E7%89%99%E9%80%9A%E8%BF%87-gprs-%E6%97%A0%E7%BA%BF%E4%B8%8A%E7%BD%91/
http://www.chinalinuxpub.com/read.php?wid=1490

测试环境， ubuntu 7.10 + motorola A768i

网上搜这个能搜到很多， 大致是装上很多以bluez-开头和包含bluetooth的包（我差不多都装了), 之后启动bluetooh服务，以及运行gnome-obex-server(Applications->Accessories->Bluetooth File Sharing). 然后就能自动找到手机了（可能也需要修改hcid.conf，见下）， 传文件是点右键， Send to, 里面有个Bluetooh的选项。

今天一直在搞rfcomm, 本来是试图连上蓝牙局域网的，但是一直没成功，到现在有点成果。记录如下。

注意：
要用到的命令：hcitool, hciconfig, sdptool, rfcomm, 最好都看一下文档。
另外每次修改配之后注意重启bluetooth服务：/etc/init.d/bluetooth restart
很多命令需要管理员权限，以下省略sudo

步骤：
1.修改/etc/bluetooth/hcid.conf, 关键是如下两行
security auto;
passkey "1234";
第一行很重要， 我一开始设的user，手机怎么都连不上电脑
第二行是手机连电脑时需要输入的验证码

2.hcitool scan 得到手机的地址

3.sdptool browse <地址> 得到手机服务列表
我这里这条命令结果为空,
我用的是spdtool search --bdaddr <地址>
常用的service有
DUN 拨号
LAN
HS headset
OPUSH obex push

得到列表后注意看Protocal Descriptor List里“RFCOMM”一行及下一行，
找到Channel: x, 记住这个x

4.编辑 /etc/bluetooth/rfcomm.conf,
rfcomm0 {
bind yes;
device <地址>;
channel ;
comment “your comment here”;
}

之后/dev/rfcomm0就是这个channel的连接了
如果rfcomm0已经使用，那么直接改rfcomm.conf里的设备名

引文里提到用kermit可以通过/dev/rfcomm0实现与手机通信， 我这里没成功
另一引文里提到可以用/dev/rfcomm0通过手机上网， 我没有试

现在我这里主要就是能够手机电脑互传文件， 互相bond而已，很多功能还有待研究
Labels:

Comments

Post a Comment

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...
Post a Comment
Read More »

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »