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

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...
3 comments
Read More »

Hardware Password Manager

[Updates 2025-01-20] The original blog post assumes that all passwords are stored in one password manager, and the password manager either unlocks everything or nothing (e.g. Keepass). After discussing with friends, I realized that if I use something like pass , and I use a hardware GPG token, I can actually store and sync all encrypted passwords to all devices, because I will only decrypt the passwords on demand, and the computer will not see the GPG private key. The compromise is that the computer will see the list of all password entries (e.g. accounts), as well as a few other issues . I've been using Keepass for many years. I don't use online password services because I cannot fully trust them. Besides, I may not always have Internet connection, which is why I also don't use a self-hosted service. Everything has been working fine, until I turn my paranoid knob to the max. Here's the thought experiment . The Imaginary Scenario Let's say I have 100 PCs for differe...
Post a Comment
Read More »

ESP32S3: Flash Encryption and Secure Boot

Flash encryption and secure boot are useful security features for ESP32S3 chip. While not perfect, they definitely make it harder to extract the secrets in the chip. However, it is tricky to enable both features at the same time. The topic is actually discussed in the official documentation: ESP32S3 Security Features Security Features Enablement Workflows Especially, the second one mentioned it is recommended to enable flash encryption before secure boot. But I still find the documentation confusing. In the end I was able to successfully enable both, here's my findings. My Understanding After my adventure, here's what I think could have worked. WARNING, this is untested. Follow  Security Features Enablement Workflows : Burn all the keys, as long as their purpose eFuses and read/write protections Burn other security eFuses, but DO NOT burn ENABLE_SECURITY_DOWNLOAD in the middle, which is mentined at the end of the instruction for both flash encryption and secure boot. Burn...
Post a Comment
Read More »