Lenovo Foxconn Bluetooth Drivers For Mac

Bluetooth is a standard for the short-range wireless interconnection of cellular phones, computers, and other electronic devices. In Linux, the canonical implementation of the Bluetooth protocol stack is BlueZ.

Amazon.com: Bluetooth 4.0 Card 60Y3303 for IBM Lenovo Thinkpad T430 X230 T530I W530 X1 T430s: Computers & Accessories.

• 1Installation
  • 1.1Front-ends
• 3Configuration
• 6Troubleshooting
  • 6.4Bluetooth USB Dongle

Installation

1. Install the bluez package, providing the Bluetooth protocol stack.
2. Install the bluez-utils package, providing the bluetoothctl utility. Alternatively install bluez-utils-compat^AUR to additionally have the deprecated BlueZ tools.
3. The generic Bluetooth driver is the btusb Kernel module. Check whether that module is loaded. If it's not, then load the module.
4. Start/enablebluetooth.service.

• By default the bluetooth daemon will only give out bnep0 devices to users that are a member of the lpgroup. Make sure to add your user to that group if you intend to connect to a bluetooth tether. You can change the group that is required in the file /usr/share/dbus-1/system.d/bluetooth.conf.
• Some Bluetooth adapters are bundled with a Wi-Fi card (e.g. Intel Centrino). These require that the Wi-Fi card is firstly enabled (typically a keyboard shortcut on a laptop) in order to make the Bluetooth adapter visible to the kernel.
• Some Bluetooth cards (e.g. Broadcom) conflict with the network adapter. Thus, you need to make sure that your Bluetooth device get connected before the network service boot.
• Some tools such as hcitool and hciconfig have been deprecated upstream, and are no longer included in bluez-utils. Since these tools will no longer be updated, it is recommended that scripts be updated to avoid using them. If you still desire to use them, install bluez-utils-compat^AUR. See FS#53110 and the Bluez mailing list for more information.

Front-ends

Console

• bluetoothctl — Pairing a device from the shell is one of the simplest and most reliable options.

http://www.bluez.org/ bluez-utils

Graphical

The following packages allow for a graphical interface to customize Bluetooth.

• GNOME Bluetooth — GNOME's Bluetooth tool.
  • gnome-bluetooth provides the back-end
  • gnome-shell provides the status monitor applet
  • gnome-control-center provides the configuration front-end GUI that can be accessed by typing Bluetooth on the Activities overview, or with the gnome-control-center bluetooth command.
  • You can also launch the bluetooth-sendto command directly to send files to a remote device.
  • nautilus-bluetooth^AUR adds a 'Send via Bluetooth' entry to Nautilus' right-click menu
  • To receive files, open the Bluetooth settings panel; you can only receive whilst the Bluetooth panel is open.
  • To add a Bluetooth entry to the Send To menu in Thunar's file properties menu, see instructions here. (The command that needs to be configured is bluetooth-sendto %F).

https://wiki.gnome.org/Projects/GnomeBluetooth

• Bluedevil — KDE's Bluetooth tool. If there is no Bluetooth icon visible in Dolphin and in the system tray, enable it in the system tray options or add a widget. You can configure Bluedevil and detect Bluetooth devices by clicking the icon. An interface is also available from the KDE System Settings.

https://cgit.kde.org/bluedevil.git bluedevil

• Blueberry — Linux Mint's spin-off of GNOME Bluetooth, which works in all desktop environments. Blueberry does not support receiving files through Obex Object Push.

https://github.com/linuxmint/blueberry blueberry

• Blueman — A full featured Bluetooth manager.

https://github.com/blueman-project/blueman blueman

• ObexFTP — A tool for transferring files to/from any OBEX enabled device.

http://dev.zuckschwerdt.org/openobex/wiki/ObexFtp obexftp^AUR

Pairing

This article or section needs expansion.

This section describes directly configuring bluez5 via the bluetoothctl CLI, which might not be necessary if you are using an alternative front-end tool (such as GNOME Bluetooth).

The exact procedure depends on the devices involved and their input functionality. What follows is a general outline of pairing a device using bluetoothctl.

Start the bluetoothctl interactive command. Input help to get a list of available commands.

1. (optional) Select a default controller with select MAC_address.
2. Enter power on to turn the power to the controller on. It is off by default and will turn off again each reboot, see #Auto power-on after boot.
3. Enter devices to get the MAC Address of the device with which to pair.
4. Enter device discovery mode with scan on command if device is not yet on the list.
5. Turn the agent on with agent on or choose a specific agent: if you press tab twice after agent you should see a list of available agents, e.g. DisplayOnly KeyboardDisplay NoInputNoOutput DisplayYesNo KeyboardOnly off on.
6. Enter pair MAC_address to do the pairing (tab completion works).
7. If using a device without a PIN, one may need to manually trust the device before it can reconnect successfully. Enter trust MAC_address to do so.
8. Enter connect MAC_address to establish a connection.

An example session may look this way:

Configuration

Auto power-on after boot

By default, your Bluetooth adapter will not power on after a reboot. The former method by using hciconfig hci0 up is deprecated, see the release note. Now you just need to add the line AutoEnable=true in /etc/bluetooth/main.conf at the bottom in the [Policy] section:

Discoverable on startup

If the device should always be visible and directly connectable:

Audio

In order to be able to use audio equipment like bluetooth headphones or speakers, you need to install the additional pulseaudio-bluetooth package. With a default PulseAudio installation you should immediately be able to stream audio from a bluetooth device to your speakers.

If you have a system-wide PulseAudio setup make sure the user running the daemon (usually pulse) is in the lp group and you load the bluetooth modules in your PulseAudio config:

See the Bluetooth headset page for more information about bluetooth audio and bluetooth headsets.

Bluetooth serial

To get bluetooth serial communication working on Bluetooth-to-Serial modules (HC-05, HC-06) do the following steps:

Pair your bluetooth device using bluetoothctl as described above.

Install bluez-rfcomm^AUR and bluez-hcitool^AUR, as they provide certain functionality which is missing from newer tools.

Bind paired device MAC address to tty terminal:

Now you can open /dev/rfcomm0 for serial communication.

Troubleshooting

This article or section is out of date.

Debugging

In order to debug, first stopbluetooth.service.

And then start it with the -d parameter:

Another option is via the btmon tool.

Deprecated BlueZ tools

Eight BlueZ tools were deprecated and removed from bluez-utils, although not all of them were superseded by newer tools. The bluez-utils-compat^AUR package provides an alternative version of bluez-utils with the deprecated tools.

gnome-bluetooth

If you see this when trying to enable receiving files in bluetooth-properties:

Then make sure that the XDG user directories exist.

Bluetooth USB Dongle

If you are using a USB dongle, you should check that your Bluetooth dongle is recognized. You can do that by running journalctl -f when you have plugged in the USB dongle (or inspecting /var/log/messages.log). It should look something like the following (look out for hci):

If you only get the first two lines, you may see that it found the device but you need to bring it up.Example:

Or

To verify that the device was detected you can use btmgmt which is part of the bluez-utils. You can get a list of available devices and their identifiers and their MAC address by issuing:

It is possible to check the Bluetooth version as mapped to the HCI version according to the table in the official specification. For example, in the previous output, HCI version 6 is Bluetooth version 4.0.

More detailed information about the device can be retrieved by using the deprecated hciconfig. (bluez-utils-compat^AUR)

Audio devices start to skip at short distance from dongle

If other devices share the same USB host, they can interrupt communication with audio devices. Make sure it is the only device attached to its bus. For example:

Download and install the best free apps for Mouse Drivers on Windows, Mac, iOS, and Android from CNET Download.com, your trusted source for the top software picks. Hp mouse driver for mac. Visit Logitech to find the perfect wireless or wired computer mice to enhance your productivity or unleash your creativity. Mice, Computer Mice, Mac & PC Wireless Mice Logitech IE8/IE9/IE10 is no longer a supported browser. The Best Free Mouse Drivers app downloads for Mac: Apple Bluetooth BetterTouchTool SteerMouse Microsoft IntelliPoint and IntelliType Pro Mac Mouse Fix. Get help and learn more about your keyboard, mouse, trackpad and other Mac accessories. Find support, options, manuals and technical specifications.

CSR Dongle 0a12:0001

The device ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) has a regression bug, and currently only works in the kernel version ≤ 3.9.11. There is a patch available for newer versions. For more information, see Kernel Bug 60824.

Logitech Bluetooth USB Dongle

There are Logitech dongles (ex. Logitech MX5000) that can work in two modes: Embedded and HCI. In embedded mode dongle emulates a USB device so it seems to your PC that you are using a normal USB mouse/keyoard.

If you hold the little red Button on the USB BT mini-receiver it will enable the other mode. Hold the red button on the BT dongle and plug it into the computer, and after 3-5 seconds of holding the button, the Bluetooth icon will appear in the system tray. Discussion

Alternatively, you can install the bluez-hid2hci package. When you connect your Logitech dongle it will automatically switch.

hcitool scan: Device not found

• On some laptops (e.g. Dell Studio 15, Lenovo Thinkpad X1) you have to switch the Bluetooth mode from HID to HCI. Install the bluez-hid2hci package, then udev should do this automatically. Alternatively, you can run this command to switch to HCI manually:

• If the device will not show up and you have a Windows operating system on your machine, try booting it and enable the bluetooth adapter from windows.

• Sometimes also this simple command helps:

• It might happen with some intel cards (such as the 8260) to not be picked up correctly by the bluetooth service, resulting in the previous command erroring with `no default controller available`. In some cases, using the deprecated bluez-utils-compat^AUR in lieu of bluez-utils have reportedly fixed the issue.

rfkill unblock: Do not unblock

If your device still soft blocked and you run connman, try this:

My computer is not visible

Cannot discover computer from your phone? Enable discoverable mode:

to check if it worked:

If even so it does not show up, try changing the device class in /etc/bluetooth/main.conf as following:

A user reported that this was the only solution to make his computer visible for his phone.

Logitech keyboard does not pair

If you do not get the passkey when you try to pair your Logitech keyboard, type the following command:

If after pairing, the keyboard still does not connect, check the output of hcidump -at. If the latter indicates repeatedly connections-disconnections like the following message:

then, the only solution for now is to install the old Bluetooth stack.

HSP/HFP profiles

bluez5 removed support for the HSP/HFP profiles (telephony headset for TeamSpeak, Skype, etc.). You need to install PulseAudio (>= version 6) or another application that implements HSP/HFP itself.

Foxconn / Hon Hai / Lite-On Broadcom device

Some of these devices require the firmware to be flashed into the device at boot. The firmware is not provided but can converted from a Microsoft Windows .hex file into a .hcd using hex2hcd (which is installed with bluez-utils).

In order to get the right .hex file, try searching the device vendor:product code obtained with lsusb, for example:

or

Alternatively, boot into Windows (a virtual machine installation will suffice) and get the firmware name from the Device Manager utility. If you want to know the model of your device but cannot see it in lsusb, you might see it in lsusb -v as iProduct.

The .hex file can be extracted from the downloaded Windows driver without having to run Windows for it. Download the right driver, for example Bluetooth Widcomm (listed among the drivers for Lifebook P771), which contains the drivers for many Broadcomm devices. In case of Bluetooth Widcomm, the driver is a self-extracting RAR archive, so it can be extracted using unrar x. To find out which of the many .hex files is the right one for you, look in the file Win32/bcbtums-win7x86-brcm.inf and search for [RAMUSBE031.CopyList], where E031 should be replaced with the product code (the second hex number in lsusb) of your device in upper-case. Underneath you should see the file name of the right .hex file.

Once you have the .hcd file, copy it into /lib/firmware/brcm/BCM.hcd - this filename is suggested by dmesg and it may change in your case so check your dmesg output in order to verify. Then reload the btusb module:

The device should now be available. See BBS#162688 for information on making these changes persistent.

Intel combined wifi and bluetooth cards

See Wireless network configuration#Bluetooth coexistence.

Device connects, then disconnects after a few moments

If you see messages like the following in journalctl output, and your device fails to connect or disconnects shortly after connecting:

This may be because you have already paired the device with another operating system using the same bluetooth adapter (e.g., dual-booting). Some devices cannot handle multiple pairings associated with the same MAC address (i.e., bluetooth adapter). You can fix this by re-pairing the device. Start by removing the device:

Then restartbluetooth.service, turn on your bluetooth adapter, make your device discoverable, re-scan for devices, and re-pair your device. Depending on your bluetooth manager, you may need to perform a full reboot in order to re-discover the device.

Device does not connect with an error in journal

If you see a message like the following in journalctl output while trying to connect to a device:

try installing pulseaudio-bluetooth and restarting PulseAudio. This error can manifest even while using only file transfer.

Device does not show up in scan

Some devices using bluetooth low energy do not appear when scanning with bluetoothctl, for example the Logitech MX Master. The simplest way I have found to connect them is by installing bluez-utils-compat^AUR, then startbluetooth.service and do:

In another terminal:

Wait until your device shows up, then Ctrl+c hcitool. bluetoothctl should now see your device and pair normally.

Interference between Headphones and Mouse

Civ v mac. If you experience audio stuttering while using a bluetooth mouse and keyboard simultaneously, you can try the following as referenced in #23 https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215

Bluetooth mouse laggy movements

Try edit the file /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/YY:YY:YY:YY:YY:YY/info (XX:XX:XX:XX:XX:XX - your Bluetooth adapter MAC-address, YY:YY:YY:YY:YY:YY - your mouse MAC-address) and add those lines:

You can see your local adapter MAC address by running command hcitool dev, your can see MAC addresses of currently connected remote devices by running command hcitool con

Adapter disappears after suspend/resume

First, find vendor and product ID of the adapter. For example:

In this case, the vendor ID is 8087 and the product ID is 0025.

Then, use usb_modeswitch to reset the adapter:

hci0: link tx timeout

This article or section is a candidate for moving to TLP.

If your bluetooth headphones suddenly stop working and you see this error in dmesg, it may be caused by TLP suspending your device. Create a file like /etc/tlp.d/10-disable-autosuspend.conf and put this in there:

Get the device ID for your bluetooth device from lsusb -v. Restart TLP and the bluetooth service.

Lenovo, Asus, and Toshiba are known as the first three big computer.

Download Lenovo IdeaPad Yoga 2 13 Bison/Chicony Camera Driver for Windows 64 bit

Unlock your laptop with your face or log in to windows and websites with your face via bio-metric facial recognition password. Updated January 3, am. Face Recognition System Matlab source code for face recognition. EigenFaces-based algorithm for face verification and recognition with a training stage. Person using facial recognition to log in. Image4 For more information on AMD features and software go to test. Takes me maybe seconds to type my random 8 char password. This kind face-recognition software is usually used in security systems, but Veriface is mainly suitable for enhanced Lenovo IdeaPad Yoga 13 Chicony Camera log-in actions or.

Software Requirements; Hardware Requirements.

Windows tool to logon to Windows using face recognition. Lenovo VeriFace for Windows 8 bitWindows bit. Forget the pain of typing your password and unlock your session using face recognition! Download the installer for Windows or macOS. VeriFace Pro facial recognition software. Toshiba software Windows Vista and can run on any laptop 8.

Cost and time associated with the experiments are. Do you use some sort of Face recognition software?

All categories

IdeaPad stylized as ideapad is a line of consumer-oriented laptop computers from Lenovo. Facial recognition with the help of webcam installed on your Also Read: The computer maker even throws in a Start Menu for Windows 8, which is installable from the Lenovo software bundle. Some people are a bit worried that facial recognition, in particular, is not secure. Laws Lenovo IdeaPad Yoga 13 Chicony Camera the use of this software vary from country to country. At most websites that require a password, a window pops up over your browser and gives. Neither did we find the Veriface face-recognition software that Lenovo advertises as a.

The integrated webcam uses stored images of your face to allow you to login quickly and. Built to last Plus, features like VeriFace face recognition technology provides a fun way to login to your PC. Now, the company has Lenovo IdeaPad Yoga 13 Chicony Camera the Lenovo Flex 10, a cheap Windows you want to benefit from its portability and the touch interface of Windows 8. Optimized for Windows 8, the intuitive, easy-to-use touchpad features simple on the Flex 10, thanks to Veriface Pro, face recognition software that uses the.

How do you use the inegrated camera on a n lenovo? X[ edit ] The ThinkPad X was announced on 15 May [45] and replaced the earlier Xintroducing a new chiclet-style, 6-row keyboard replacing the classic 7-row keyboard style, Ivy Bridge processor and for the first time in the X-series — USB 3. The Ivy Bridge processors brought performance improvements compared to the X and the integrated Intel HD Graphics are more than capable of delivering a good gaming experience in 4X or classic real-time strategy games.

Intel Core iM 2. The ThinkPad Xt is not compatible with previous series 3 docking stations and It is only compatible with the UltraBase series 3 'slice base'. The X uses the rectangular power plug.

ThinkPad Infrared Camera

The ThinkPad Helix featured a tablet powered by Ivy Bridge components, a docking keyboard, and Wacom digitizer stylus. It has a durable case fitted with rubber bumpers and thickened plastic case components, in order to improve its durability. Camera Driver (Chicony, Bison) for Windows 8 (bit), Windows (bit), Windows 10 (bit) - IdeaPad Yoga Camera Driver (Chicony, Bison) for Windows Lenovo IdeaPad Yoga 13 Chicony Camera (bit), Windows (bit), Windows 10 (bit) - IdeaPad Yoga Individual Downloads.