Audio works, but data does not. But chances are that this will chane.
LineageOS does not support Xperia 10 iii, seehttps://wiki.lineageos.org/devices/#sony
attah
4 May 2023 15:59
146
wosrediinanatour:
Audio works
…by virtue of having nothing to do with coming from the Android runtime.
Sailfish OS can do Bluetooth audio, that’s all that is at play here.
wosrediinanatour:
but data does not.
Bluetooth is not as simple as just being “audio” and “data”.
What makes you say that?
Because Jolla’s focus is on supporting Android apps.
2 Likes
I read the Jolla documentation and they were bigging up their Android support, so I assumed that would include Bluetooth. There was no mention that Android support did not include Bluetooth support .
This thread seems to already have been running for two years. Proper Bluetooth support may well be added at some point, but who knows when
2 Likes
Until some years the Bluetooth-Audio-Only-Support in Android-Support was enough for the most cases.
But with increasing Products that require Bluetooth-Auth and/or Connection (Public rent Scooter & Bicycle, Dashcams, DHL Packstation…etc) it becomes more and more important.
Waydroid doesn´t support it also, so the Problem might be the missing Link/Bridge between it.
If Jolla focus on their Cashcow Car-Dashboard-Support for Android-Apps maybe that functionality isn´t needed there, this is just my guess!
I hope i’m wrong with my opinion and we can profit from a further development in full BT-Support for Android-Apps and hopefully a stand-alone-solution for Android-Support in SFOS-Ports.
11 Likes
I remember someone wondered if it could be possible to have the bluetooth switched from Sailfish to the Android side. This would be enough for me even if it required a reboot as I rarely use bluetooth audio. It would make so many things possible that are impossible now…
8 Likes
rw007
27 May 2024 17:01
152
Bluetooth ist für mich sehr wichtig da ich mein gerät zum arbeiten brauche. wenn jolla/Sailfish nicht bald eine Möglichkeit bringt Bluetooth unter Android zu nutzen muss ich auf Android ausweichen.
es wäre auch sinnvoll wenn man in sailfish os z.b Bluetooth ausschalten könnte und das es dafür in Android aktiviert werden könnte. auf für Wlan wär es sinnvoller sailfish und Android zu trennen.
4 Likes
attah
27 May 2024 19:37
153
Translation server error.
1 Like
A lot of people are fed up with Jolla and are thinking to switch. Unfortunately, Android is not an option for many.
Deutsch: Viele Leute haben die Nase voll und denken darüber nach, zu wechseln. Leider ist Android für viele keine Option.
3 Likes
rw007
27 May 2024 20:29
155
I’ve been with Jolla since day one. I also had 2 Jolla phones, was absolutely thrilled, then the “Xperia X” came along, absolutely great, no problems, ran very stable and reliable. Problem Android 4.4 end
reminded me a lot of the reliable Nokia cell phones.
then since switching to the newer xperia, I had all xperia cell phones that are supported by sailfish. none of them ran really smoothly.
Always problems with reception, then problems with the voice quality, then the camera takes very slow recordings and sometimes even crashes.
and now the bluetooth android problem. weather app dead. here maps new version without language. MMS down RCS alternative is missing from sailfish. Battery consumption on Android phone ran for about 5 days on sailfish for 2 days. One advantage of sailfish is that the operation is fundamentally better in every app.
4 Likes
rw007
27 May 2024 20:30
156
I cant speak English. I come from Switzerland and can speak German quite well
1 Like
emva
27 May 2024 20:42
157
Here is a German thread:
Hier ist ein Deuches (I do not know the word for thread in german)
I started this Topic because of give user of SailfishOS who don´t speak English the chance to explain there problems her and get an solution.
Background: At the July 1, 2022 the last German SailfishOS community forum jollausers.de will be closed.
Have fun!
Ich habe dieses Thema gestartet, um SailfishOS-Nutzern, die kein Englisch sprechen, die Möglichkeit zu geben, ihre Probleme zu erklären und eine Lösung zu erhalten.
Hintergrund: Zum 1. Juli 2022 wird das letzte deutsche Community Forum Jol…
papa
3 July 2024 19:37
160
Sometimes Bluetooth is also necessary for setting up an PV inverter like https://emea.apsystems.com/diy/ez1/
This inverter also has a homeassistant integration, so I think this fits the SailfishOS-geek community here: APsystems - Home Assistant
Currently, I can not set up this integration because I only have my SailfishOS Xperia 10 III at hand., which is a pity…
2 Likes
attah
3 July 2024 19:40
161
Something requiring a proprietary app for setup is quite obviously a bad fit - regardless of Bluetooth.
8 Likes
The main problem is that the kernel is not handling the namespace for bt devices in the same way as for network devices.
As long as no kernel modification will be done no bt functions to alien dalvik will be possible.
opened 08:14AM - 02 May 17 UTC
closed 10:21PM - 23 May 17 UTC
I've provided as much information as I could to aid solving this problem.
# R… equired information
* Distribution: Ubuntu
* Distribution version: 17.04
* The output of "lxc info":
```
config:
core.https_address: '[::]:8443'
core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
api_status: stable
api_version: "1.0"
auth: trusted
public: false
environment:
addresses:
- 192.168.1.106:8443
architectures:
- x86_64
- i686
certificate: |
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
certificate_fingerprint: a8ef0eeedf4f705bc835f11b84d7d159f553ce4eda270490b853bb904bacb4c6
driver: lxc
driver_version: 2.0.7
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.10.0-20-generic
server: lxd
server_pid: 1135
server_version: "2.12"
storage: dir
storage_version: "1"
```
# Issue description
Unable to get USB based bluetooth device to function inside container.
# Steps to reproduce
- I created a container with Debian Jessie and made sure security.privileged was set to true.
- I got as listing of usb devices so that I could add them to the container.
```
lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 006: ID 05ac:8218 Apple, Inc. Bluetooth Host Controller
Bus 004 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 004 Device 002: ID 05ac:8242 Apple, Inc. Built-in IR Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
```
- Only two of these seemed relevant so I added them to the container.
```
lxc config device add homeass bthub usb vendorid=0a5c productid=4500
lxc config device add homeass bthost usb vendorid=05ac productid=8218
```
- For good measure, and because I wasn't having any success I added /dev/rfkill
```
lxc config device add homeass /dev/rfkill unix-char path=/dev/rfkill
```
With the bluetooth.service running outside the container I am able to get a list of devices and scan:
```
hcitool dev
Devices:
hci0 58:B0:35:82:D1:68
michal@macmini:~$ hcitool scan
Scanning ...
C4:D9:87:13:60:13 W0003KKSA53048
00:1B:AF:57:91:5A Stan's phone
```
- I made sure that the bluetooth.service was not running so that it could not interfere with anything inside the container.
```
sudo systemctl stop dbus-org.bluez
```
- I tried to start the bluetooth service inside the container but it failed immediately:
```
michal@homeass:~$ sudo systemctl start dbus-org.bluez
michal@homeass:~$ sudo systemctl status dbus-org.bluez
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
Active: failed (Result: exit-code) since Tue 2017-05-02 17:56:39 AEST; 3s ago
Docs: man:bluetoothd(8)
Process: 31805 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/FAILURE)
Main PID: 31805 (code=exited, status=1/FAILURE)
Status: "Starting up"
May 02 17:56:39 homeass bluetoothd[31805]: Bluetooth daemon 5.23
May 02 17:56:39 homeass systemd[1]: Started Bluetooth service.
May 02 17:56:39 homeass systemd[1]: bluetooth.service: main process exited, code=exited, status=1/FAILURE
May 02 17:56:39 homeass systemd[1]: Unit bluetooth.service entered failed state.
```
The contents of the systemd service file are as follows:
```
cat /etc/systemd/system/dbus-org.bluez.service
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/lib/bluetooth/bluetoothd
NotifyAccess=main
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service
```
# Information to attach
- [x] any relevant kernel output (dmesg)
```
sudo dmesg |egrep 'bt|Blue'
[ 4.005096] usb 4-6.3: Product: Bluetooth USB Host Controller
[ 6.015720] Bluetooth: Core ver 2.22
[ 6.015747] Bluetooth: HCI device and connection manager initialized
[ 6.015751] Bluetooth: HCI socket layer initialized
[ 6.015755] Bluetooth: L2CAP socket layer initialized
[ 6.015767] Bluetooth: SCO socket layer initialized
[ 6.044219] usbcore: registered new interface driver btusb
[ 6.165084] Bluetooth: hci0: BCM: chip id 19 build 0846
[ 6.167072] Bluetooth: hci0: BCM: product 05ac:8218
[ 6.185086] Bluetooth: hci0: Apple Bluetooth Device
[ 8790.262008] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8790.262009] Bluetooth: BNEP filters: protocol multicast
[ 8790.262014] Bluetooth: BNEP socket layer initialized
```
- [x] container log (lxc info NAME --show-log)
```
Name: homeass
Remote: unix:/var/lib/lxd/unix.socket
Architecture: x86_64
Created: 2017/05/01 04:49 UTC
Status: Running
Type: persistent
Profiles: default
Pid: 21355
Ips:
eth0: inet 192.168.1.107 vethB6CV8Q
eth0: inet6 fe80::216:3eff:fe13:dc22 vethB6CV8Q
lo: inet 127.0.0.1
lo: inet6 ::1
Resources:
Processes: 14
CPU usage:
CPU usage (in seconds): 308
Memory usage:
Memory (current): 225.04MB
Memory (peak): 245.22MB
Network usage:
lo:
Bytes received: 11.42kB
Bytes sent: 11.42kB
Packets received: 89
Packets sent: 89
eth0:
Bytes received: 122.31MB
Bytes sent: 2.71MB
Packets received: 558666
Packets sent: 9367
Log:
lxc 20170501100023.150 WARN lxc_start - start.c:signal_handler:322 - Invalid pid for SIGCHLD. Received pid 21347, expected pid 21355.
```
- [lxd.log.txt](https://github.com/lxc/lxd/files/969792/lxd.log.txt) main daemon log (/var/log/lxd.log)
- [client_with_debug.txt](https://github.com/lxc/lxd/files/969801/client_with_debug.txt)
Not sure how to run the daemon with --debug? Would this involve editing the systemd service file? If required please let me know and I will provide it.
Thank you in advance for any help. I am new to containers and lxd and I've been trying to work this out myself for days.
So all your discussions about this topic with jolla are useless until the kernel will be modified.
4 Likes
Agreed; there should literally be laws against that sort of thing.
2 Likes
not really. they can modify kernel themselves and build a lkm.
1 Like