• Lite-on Laptops Amazon
• Liteon Laptops & Desktops Drivers

Shop for Shop Laptops By Brand in Laptops. Buy products such as ASUS C423 14' Celeron 4GB/64GB Chromebook, 14' HD Nano-Edge Display, Intel Celeron N3350, 4GB DDR4, 64GB eMMC, Chrome OS, C423NA-WB04 (Google Classroom Ready) at Walmart and save. In order to satisfy the increasing number of gaming notebooks we have outsourced the best high-end laptops weighing less than 2.5 kg (5.5 lbs) with a maximum thickness of 2 cm (0.8 inches) as well.

Lite-On Technology Corporation

Type	Public
TWSE: 2301
Industry	Consumer Electronics
Founded	1975; 46 years ago
Headquarters	,
Raymond Soong (Chairman), David Lin (CEO)
Products	Computer components, consumer electronics
Revenue	NT$ 16.7 Billion

1. My Lite-On Laptop SDW-431S stopped recognizing ANY discs but installation ones. Any suggestions?
2. Jan 15, 2021 Some Xiaomi devices get quite popular due to their stunning features and compelling pricing. Xiaomi Mi Watch is such a useful device featuring 1.39-inch AMOLED display, six high-precision sensors.
3. Lite-On (also known as LiteOn and LiteON) is a Taiwanese Company that primarily manufactures consumer electronics, including LEDs, semiconductors, computer chassis, monitors, motherboards, optical disc drives, and other electronic components.

Lite-On (also known as LiteOn and LiteON) is a Taiwanese Company that primarily manufactures consumer electronics, including LEDs, semiconductors, computer chassis, monitors, motherboards, optical disc drives, and other electronic components. The Lite-On group also consists of some non-electronic companies like a finance arm and a cultural company.

History[edit]

Lite-On was started in 1975 by several Taiwanese Texas Instruments ex-employees. The original line of business was optical products (LEDs). They then branched out into computer power supplies by starting the Power Conversion Division. Other divisions were soon to follow.

In 1983 Lite-On Electronics issued initial public offering as the first technology company listed on the Taiwan Stock Exchange with Stock Code 2301.^[1]In 2003 Lite-ON appoint Dragon Group as their sole distributor in Indonesia.In 2006 Lite-On IT Corporation acquired BenQ Corporation's Optical Disk Drive Business to become one of the top 3 ODD manufacturers in the world.^[1]

In March 2007, Lite-On IT Corporation formed a joint venture with Koninklijke Philips Electronics N.V. for their optical disc drive division as Philips & Lite-On Digital Solutions Corporation (PLDS).^[2][3]

Kioxia (formerly Toshiba Memory) announced on August 30, 2019, that it signed a definitive agreement to acquire Lite-On's SSD business for US$165 million. The transaction closed in 2020.^[4][5]

References[edit]

1. ^ ^abhttp://www.liteon.com/Page.aspx?id=99541f27-4f04-478d-a39b-4d064ce98a74
2. ^'Lite-On IT Corporation and Philips to join hands in Optical Storage market'. Retrieved 20 March 2017.
3. ^'Philips & Lite-On Digital Solutions Corp'. Retrieved 20 March 2017.
4. ^Duckett, Chris (2 September 2019). 'Toshiba Memory picks up Lite-On SSD business in $165 million deal'. ZDNet. Retrieved 20 November 2019.
5. ^'Kioxia to Complete Acquisition of LITE-ON Technology's SSD Business'. June 30, 2020. Retrieved July 2, 2020.

External links[edit]

Wikimedia Commons has media related to Lite-On Technology.

• Official website

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.

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.

Note:

• 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 gets 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://invent.kde.org/plasma/bluedevil || 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:

Dual boot pairing

To pair devices on dual boot setups you need to change the pairing keys manually on your Linux install, so that they match in both systems.

Setup

To do this, first pair your device on your Arch Linux install. Then reboot into the other OS and pair the device. Now you need to extract the pairing keys, but first switch off the bluetooth devices to prevent any connection attempts.

For Windows

Reboot into Arch. Install chntpw. Mount your windows system drive.

Inside the chntpw environment, run

Then get your Bluetooth adapter's MAC address and enter its folder

Do the same for your paired devices

example output

Now get your device's key through hex

example output

The 'XX's are the pairing key. Make note of which keys map to which MAC addresses.

For macOS

Boot into macOS, then open a terminal.

• If you are on Sierra or older, run

• If you are on High Sierra or newer, run

Copy the bt_keys.txt file to a drive that can be read from Arch Linux. Reboot into Arch Linux.

Finishing up

Now that you have the keys change user to root, then continue with:

Here you will find folders for each paired bluetooth device. For each device you want to pair with Arch and your dual boot, do the following:

Edit the info file and change the key under [LinkKey]. E.g.:

Note: For older versions of macOS (High Sierra and older) you will have to reverse the key like so:

98 54 2f aa bb cc dd ee ff gg hh ii jj kk ll mm becomes MM LL KK JJ GG FF EE DD CC BB AA 2F 54 98.

This reversal is not necessary for newer versions of macOS.

Then restartbluetooth.service and pulseaudio (with pulseaudio -k && pulseaudio --start).

You should be able to connect to your device now.

Configuration

Auto power-on after boot

By default, the Bluetooth adapter does not power on after a reboot, you need to add the line AutoEnable=true in the configuration file /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

You will typically need to take an additional step to integrate the audio server with bluetooth. This is detailed in the below sections.

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

PulseAudio

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:

PipeWire

Lite-on Laptops Amazon

PipeWire as of v0.3.19 enables its Bluetooth support by default, see bluetooth.

ALSA

First, ensure that your bluetooth audio device is correctly paired and connected to the system.

Then, install bluez-alsa-git^AUR, start (and enable) the bluealsa service, and add your user to the audio group.

Run the following command to check if everything is working as intended (replace XX:XX:XX:XX:XX:XX and FILE.wav below):

Finally, add the following lines to your ~/.asoundrc:

You can now use the bluealsa device to reach your bluetooth audio device. Volume management is conducted normally via alsamixer with the option -D bluealsa.

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.

Deprecated tool	Most likely replacement
gatttool	btgatt-client, D-Bus Gatt API
hciattach	btattach
hciconfig	btmgmt (and bluetoothctl?)
hcidump	btmon (and btsnoop)
hcitool	missing, D-Bus Device API available
rfcomm	missing, implement with D-Bus Profile1 API?
ciptool
sdptool	missing, functionality seems to be scattered over different D-Bus objects: Profile, Advertising, and the UUIDs arrays in device and adapter.

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:

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

Liteon Laptops & Desktops Drivers

• 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:

bluetoothctl: No default controller available

This error may happen if the device is blocked by rfkill.

It might also happen with some intel cards (such as the 8260) to not be picked up correctly by the bluetooth service. In some cases, using the deprecated bluez-utils-compat^AUR in lieu of bluez-utils have reportedly fixed the issue.

This might also be caused by power saving measures, in which case adding the kernel parameterbtusb.enable_autosuspend=n is a potential solution. See also Red Hat Bugzilla – Bug 1573562.

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.

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 adapters). Follow instructions on #Dual boot pairing for solving this issue.

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

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:

Problems with all BLE devices on kernel 5.9+

Starting with v5.9, the kernel Bluetooth stack tries to use link-layer privacy on BLE connections. If the device works after pairing but does not survive a reboot or suspend, it is probably because of this.

To workaround [1] this issue, open /var/lib/bluetooth/<adapter mac>/<device mac>/info, remove the following lines, and restart bluetooth.service:

See the relevant discussion on the Arch forum.