![]() If using a device without a PIN, one may need to manually trust the device before it can reconnect successfully. Enter device discovery mode with "scan on" command if device is not yet on the list.Įnter "pair MAC Address" to do the pairing (tab completion works).Enter "devices" to get the MAC Address of the device with which to pair.Turn the power to the controller on by entering "power on".Enter "help" to get a list of available commands. Start the bluetoothctl interactive command. If bluetooth-agent is not available, try bluetoothctl: ![]() Enter the pin you used with bluetooth-agent. This will force a connection from computer to phone, which should cause the phone to ask you to confirm the connection attempt by prompting for a PIN. Where is your phone's bluetooth address, as shown by hcitool scan (note that this will only work if the phone is discoverable, though the computer need not be). Start bluetoogh-agent as explained above, then run a command that will try to connect to the phone, e.g. Note: Instead of initiating the pairing process from the phone, you can also initiate it from the computer. Now enter the PIN you gave to bluetooth-agent, and pairing is completed. Select your computer once found the device should prompt you for a PIN. Then, as described above, choose something like the "setup", "connect" or "Bluetooth" menu on the device to be paired, and search for Bluetooth devices. Just start bluetooth-agent (as root), giving an arbitrary PIN, such as 4835: # bluetooth-agent 4835 If you do not want to or cannot use Gnome or KDE, you can also use bluetooth-agent or bluetoothctl for the pairing.īluetooth-agent is a part of package bluez, so it should already be available if Bluetooth has been configured on your system. Your phone sees that the PIN matches and shows it on its display. It asks for the PIN, enter the one you just made up. On your computer you will get a pop-up information balloon asking for the PIN, something like Pairing request from Phone (xx:xx:xx:xx:xx:xx) where Phone is the name of your phone and xx:xx:xx:xx:xx:xx is its MAC address.Īnother window will pop-up. The device will then ask for a PIN, you can make one up, (choose four digits, say 2309 ). On your device, select the Debian system. You should find your Debian system, called something like debian-0, where debian is the hostname of your Debian system. On the device you need to choose something like the "setup", "connect" or "Bluetooth" menu and then search for Bluetooth devices. On your Bluetooth device you can now try to pair. Log out of your desktop session and log back in - this is required for the pairing pop-up in the next step to appear correctly. To pair devices, you need a passkey-agent. This will however depend on the devices involved (on some devices this may be configurable). ![]() Afterwards, they will remember each other, and no exchange of PINs is necessary. Note that pairing is usually only required the first time two devices interact. If it's not running, start it.įor security reasons, Bluetooth devices will only talk to each other if they have been "introduced" first (a bit like in real life :-)). Make sure the Bluetooth daemon is running. Read /usr/share/doc/bluez/ to get some understanding of what's going on. ![]() Install Bluetooth support (package bluetooth) : use Bluetooth peripherals with your computer, such as a Bluetooth wireless mouse.use a mobile phone to give your computer mobile internet access.exchange data with devices, such as sending music or videos to/from your phone.Once you have setup Bluetooth, you can for example The steps described below are required before you can use the services Bluetooth offers. This documents describes what you need to do to use Bluetooth to communicate with other Bluetooth devices. We assume you have a Bluetooth adapter in your computer and a Bluetooth device (such as a mobile phone or PDA). Audio device issues (With pairing, quality, codec selection, etc.).I found one forum post mentioning that data in /var/lib/docker will be preserved, but I could not find any official docs stating that and it also seems strange considering the persistent storage guide above doesn't use this path or even mention that your data will be deleted. I can't find documentation on what is happening. However "docker-machine restart " clears out this custom data on the vm. I checked that this data is indeed stored on the boot2docker VM (created by docker-machine) and not on the container, so that it will persist. I've created a data volume container for storing persistent data. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |