Apply suggestions from code review

Co-authored-by: Tobias Gesellchen <tobias@gesellix.de>
This commit is contained in:
Tim Vahlbrock
2026-05-10 12:58:00 +02:00
committed by Tobias Gesellchen
co-authored by Tobias Gesellchen
parent 1d9264437d
commit e008bb6a2b
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -10,7 +10,7 @@ AfterTouch usually normally migrates the SoundTouch devices very noninvasive, by
### AfterTouch Availability
Some devices will expose the AfterTouch port, some won't. We currently suspect that the newer generation devices (those with Bluetooth) will expose the port, while the older ones won't. We're still investigating how to expose AfterTouch on all devices.
Some devices will expose the AfterTouch port, some won't. We currently (May 2026) suspect that the newer generation devices (those with Bluetooth) will expose the port, while the older ones won't. We're still investigating how to expose AfterTouch on all devices.
If your device doesn't expose the port, you can still use the on-device installer, but you'll need to run AfterTouch on each one of your speakers individually and may only access AfterTouch via ssh port forwarding. This will also make OAuth authentication a little more tricky, but should also work via SSH port forwarding.
+1 -1
View File
@@ -1,6 +1,6 @@
#!/bin/sh
### BEGIN INIT INFO
# Provides: soundtouch-service
# Provides: aftertouch-service
# Required-Start: $network $local_fs
# Required-Stop: $network $local_fs
# Default-Start: 2 3 4 5