Bluetooth - Revision history

QuBe: Make "happy path" for installing mpris the first example. Also add missing code formatting

2026-02-23T08:09:26Z

Make "happy path" for installing mpris the first example. Also add missing code formatting

← Older revision		Revision as of 08:09, 23 February 2026
Line 53:		Line 53:
	To make these buttons usable with media players supporting the dbus-based [https://specifications.freedesktop.org/mpris-spec/latest/ MPRIS] standard,		To make these buttons usable with media players supporting the dbus-based [https://specifications.freedesktop.org/mpris-spec/latest/ MPRIS] standard,
	one can use <code>mpris-proxy</code> that is part of bluez package.		one can use <code>mpris-proxy</code> that is part of bluez package.
	~~The following snippet~~ can be used in [[Home Manager]] ~~to start this program as a daemon~~:		It can be used as a daemon in [[Home Manager]]:<syntaxhighlight lang="nix">
			services.mpris-proxy.enable = true;
			</syntaxhighlight>For versions preceding Home Manager 21.05, the following snippet can be used:

	<syntaxHighlight lang="nix">		<syntaxHighlight lang="nix">
Line 63:		Line 65:
	};		};
	</syntaxHighlight>		</syntaxHighlight>

	~~Or, starting with Home Manager 21.05, enable the <code>mpris-proxy</code> service.~~

	Some headsets (such as Sony's WH-1000XM series) also support AVRCP directly and as such <code>mpris-proxy</code> is not required for this functionality, as headset button presses will register as media key presses. If you are using a WM or a desktop environment which doesn't support media keys, you will have to set up keybindigs yourself; the keys are typically called <code>XF86AudioPlay</code>, <code>XF86AudioPause</code>, <code>XF86AudioNext</code>, and <code>XF86AudioPrev</code>. However, note that some functionality, such as "take off headphones to pause" on WH-1000XM4/5 requires two-way AVRCP communication to work properly, so `mpris-proxy` is still recommended if you wish to use it. It also may or may not help with Bluetooth multipoint.		Some headsets (such as Sony's WH-1000XM series) also support AVRCP directly and as such <code>mpris-proxy</code> is not required for this functionality, as headset button presses will register as media key presses. If you are using a WM or a desktop environment which doesn't support media keys, you will have to set up keybindigs yourself; the keys are typically called <code>XF86AudioPlay</code>, <code>XF86AudioPause</code>, <code>XF86AudioNext</code>, and <code>XF86AudioPrev</code>. However, note that some functionality, such as "take off headphones to pause" on WH-1000XM4/5 requires two-way AVRCP communication to work properly, so `mpris-proxy` is still recommended if you wish to use it. It also may or may not help with Bluetooth multipoint.

Bjn: Fix typo "overskirde" -> "overskride"

2026-01-08T21:56:24Z

Fix typo "overskirde" -> "overskride"

← Older revision		Revision as of 21:56, 8 January 2026
Line 10:		Line 10:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	services.blueman.enable = true;		services.blueman.enable = true;
	</syntaxhighlight>Another option for a GUI based Bluetooth management GUI can be [https://search.nixos.org/packages?channel=unstable&show=overskride&from=0&size=50&sort=relevance&type=packages&query=overskride ~~overskirde~~]		</syntaxhighlight>Another option for a GUI based Bluetooth management GUI can be [https://search.nixos.org/packages?channel=unstable&show=overskride&from=0&size=50&sort=relevance&type=packages&query=overskride overskride]

	Alternatively if you wish to use a TUI<ref>https://en.wikipedia.org/wiki/Text-based_user_interface</ref> then check out [https://github.com/bluetuith-org/bluetuith bluetuith] or [https://github.com/pythops/bluetui bluetui]		Alternatively if you wish to use a TUI<ref>https://en.wikipedia.org/wiki/Text-based_user_interface</ref> then check out [https://github.com/bluetuith-org/bluetuith bluetuith] or [https://github.com/pythops/bluetui bluetui]

Mathtician: /* Enabling A2DP Sink */ Added ellipses to match other code blocks

2025-11-02T03:45:14Z

Enabling A2DP Sink: Added ellipses to match other code blocks

← Older revision		Revision as of 03:45, 2 November 2025
Line 103:		Line 103:

	<syntaxhighlight lang="nix">{		<syntaxhighlight lang="nix">{
			...
	hardware.bluetooth.settings = {		hardware.bluetooth.settings = {
	General = {		General = {
Line 108:		Line 109:
	};		};
	};		};
			...
	}</syntaxhighlight>		}</syntaxhighlight>
	This configuration may be unnecessary and does not work with bluez5 (<tt>Unknown key Enable for group General</tt> ).		This configuration may be unnecessary and does not work with bluez5 (<tt>Unknown key Enable for group General</tt> ).

Qweered: better link

2025-09-11T16:35:36Z

better link

← Older revision		Revision as of 16:35, 11 September 2025
Line 12:		Line 12:
	</syntaxhighlight>Another option for a GUI based Bluetooth management GUI can be [https://search.nixos.org/packages?channel=unstable&show=overskride&from=0&size=50&sort=relevance&type=packages&query=overskride overskirde]		</syntaxhighlight>Another option for a GUI based Bluetooth management GUI can be [https://search.nixos.org/packages?channel=unstable&show=overskride&from=0&size=50&sort=relevance&type=packages&query=overskride overskirde]

	Alternatively if you wish to use a TUI<ref>https://en.wikipedia.org/wiki/Text-based_user_interface</ref> then check out [https://~~search.nixos~~.org/~~packages?channel=unstable&show=~~bluetuith~~&from=0&size=50&sort=relevance&type=packages&query=bluetui~~ bluetuith] or [https://github.com/pythops/bluetui bluetui]		Alternatively if you wish to use a TUI<ref>https://en.wikipedia.org/wiki/Text-based_user_interface</ref> then check out [https://github.com/bluetuith-org/bluetuith bluetuith] or [https://github.com/pythops/bluetui bluetui]

	===Pairing devices from the command line===		===Pairing devices from the command line===

Asymmetric: /* Enabling extra codecs */ use non-obsolete services.pulseaudio

2025-06-23T11:13:05Z

Enabling extra codecs: use non-obsolete services.pulseaudio

← Older revision		Revision as of 11:13, 23 June 2025
Line 88:		Line 88:

	To enable extra codecs add the following to <tt>/etc/nixos/configuration.nix</tt>:		To enable extra codecs add the following to <tt>/etc/nixos/configuration.nix</tt>:
	<~~syntaxHighlight~~ lang="nix">		<syntaxhighlight lang="nix">
	{		{
	...		...
	~~hardware~~.pulseaudio = {		services.pulseaudio = {
	enable = true;		enable = true;
	package = pkgs.pulseaudioFull;		package = pkgs.pulseaudioFull;
Line 97:		Line 97:
	...		...
	}		}
	</~~syntaxHighlight~~>		</syntaxhighlight>

	==== Enabling A2DP Sink ====		==== Enabling A2DP Sink ====
	Modern headsets will generally try to connect using the A2DP profile. To enable this for your bluetooth connection, add the following to <tt>/etc/nixos/configuration.nix</tt>		Modern headsets will generally try to connect using the A2DP profile. To enable this for your bluetooth connection, add the following to <tt>/etc/nixos/configuration.nix</tt>

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">{
	{
	hardware.bluetooth.settings = {		hardware.bluetooth.settings = {
	General = {		General = {
Line 109:		Line 108:
	};		};
	};		};
	}		}</syntaxhighlight>
	</syntaxhighlight>
	This configuration may be unnecessary and does not work with bluez5 (<tt>Unknown key Enable for group General</tt> ).		This configuration may be unnecessary and does not work with bluez5 (<tt>Unknown key Enable for group General</tt> ).

Onny: /* Pairing hearing aids using the ASHA protocol */

2025-05-25T19:08:21Z

Pairing hearing aids using the ASHA protocol

← Older revision		Revision as of 19:08, 25 May 2025
Line 152:		Line 152:

	Add following to your system config and apply it:		Add following to your system config and apply it:

	~~{{Note\|Parts of this instruction and module are not yet stable and will be available in the upcoming NixOS 25.04 release.}}~~

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
Line 180:		Line 178:

	Run the command <code>asha_pipewire_sink</code> and choose your hearing aids as audio sink in your sound mixer application, for example <code>pavucontrol</code>.		Run the command <code>asha_pipewire_sink</code> and choose your hearing aids as audio sink in your sound mixer application, for example <code>pavucontrol</code>.


	=== File Transfer from/to Mobile Device ===		=== File Transfer from/to Mobile Device ===

Balsoft at 12:11, 2 April 2025

2025-04-02T12:11:13Z

← Older revision		Revision as of 12:11, 2 April 2025
Line 50:		Line 50:

	=== Using Bluetooth headset buttons to control media player ===		=== Using Bluetooth headset buttons to control media player ===
	~~Some~~ bluetooth headsets have buttons for pause/play or to skip to the next track.		Many bluetooth headsets have buttons for pause/play or to skip to the next track.
	To make these buttons usable with media players supporting the dbus-based [https://specifications.freedesktop.org/mpris-spec/latest/ MPRIS] standard,		To make these buttons usable with media players supporting the dbus-based [https://specifications.freedesktop.org/mpris-spec/latest/ MPRIS] standard,
	one can use <code>mpris-proxy</code> that is part of bluez package.		one can use <code>mpris-proxy</code> that is part of bluez package.
Line 65:		Line 65:

	Or, starting with Home Manager 21.05, enable the <code>mpris-proxy</code> service.		Or, starting with Home Manager 21.05, enable the <code>mpris-proxy</code> service.

			Some headsets (such as Sony's WH-1000XM series) also support AVRCP directly and as such <code>mpris-proxy</code> is not required for this functionality, as headset button presses will register as media key presses. If you are using a WM or a desktop environment which doesn't support media keys, you will have to set up keybindigs yourself; the keys are typically called <code>XF86AudioPlay</code>, <code>XF86AudioPause</code>, <code>XF86AudioNext</code>, and <code>XF86AudioPrev</code>. However, note that some functionality, such as "take off headphones to pause" on WH-1000XM4/5 requires two-way AVRCP communication to work properly, so `mpris-proxy` is still recommended if you wish to use it. It also may or may not help with Bluetooth multipoint.

	==== System-Wide PulseAudio ====		==== System-Wide PulseAudio ====

Phanirithvij at 04:07, 13 March 2025

2025-03-13T04:07:35Z

← Older revision		Revision as of 04:07, 13 March 2025
Line 134:		Line 134:

	=== Showing battery charge of bluetooth devices ===		=== Showing battery charge of bluetooth devices ===
	If you want to see what charge your bluetooth devices have you have to enable experimental features, which might lead to bugs (according to [https://wiki.archlinux.org/title/Bluetooth_headset#Battery_level_reporting Arch Wiki). You can add the following to your config to enable experimental feature for bluetooth:		If you want to see what charge your bluetooth devices have you have to enable experimental features, which might lead to bugs (according to [https://wiki.archlinux.org/title/Bluetooth_headset#Battery_level_reporting Arch Wiki]). You can add the following to your config to enable experimental feature for bluetooth:
	<syntaxhighlight lang="nix">{		<syntaxhighlight lang="nix">{
	...		...

Blaggacao: /* File Transfer from/to Mobile Device */

2025-01-29T15:57:44Z

File Transfer from/to Mobile Device

← Older revision		Revision as of 15:57, 29 January 2025
Line 202:		Line 202:

	Caveat: When sending files to the phone, take into account that not all file extensions are accepted. Renaming the file before transfer did the trick.		Caveat: When sending files to the phone, take into account that not all file extensions are accepted. Renaming the file before transfer did the trick.

			<code>sudo journalctl -f -t obexd</code> be your friend.

	==Troubleshooting==		==Troubleshooting==

Blaggacao: /* File Transfer from/to Mobile Device */

2025-01-29T15:52:11Z

File Transfer from/to Mobile Device

← Older revision		Revision as of 15:52, 29 January 2025
Line 183:		Line 183:

	Use Case: When you're not using a desktop/window manager who supports accepting files the GUI (e.g. sway, etc)		Use Case: When you're not using a desktop/window manager who supports accepting files the GUI (e.g. sway, etc)

			<code>systemctl --user edit obex</code>

	<syntaxhighlight lang="ini">{		<syntaxhighlight lang="ini">{