NEW puppybt + bluez-tray + bluez5

Configuration wizards, scanners, remote desktop, etc.
Message
Author
gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#31 Post by gyro »

Pro wrote:sorry i dont now way for connect mouse via bluez5, may be you send me screen puppybt with recognized mouse and bluetoothctl info you_mac_moise
Thanks for the reply.
Unfortunately it's not a high priority for me at the moment, and I need to research bluetoothctl. So it may be a little while before I get back with more info.

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#32 Post by gyro »

Ok, I got puppybt to recognise, pair, and connect to my Logitech M337 bluetooth mouse. And the mouse works fine.
The difference is that I unpaired it from Windows 8, on the same machine, before I tried it on Puppy.

But when I reboot, I've got to manually run puppybt and connect to the mouse again.
How do I get it to automatically connect on reboot?

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#33 Post by gyro »

gyro wrote:But when I reboot, I've got to manually run puppybt and connect to the mouse again.
How do I get it to automatically connect on reboot?
Well I sorted this too.
I appended "AutoEnable=true" to /etc/bluetooth/main.conf.
And I made a symbolic link from /usr/bin/bluetooth.sh to /root/Startup/bluetooth.sh.

On reboot, I get a blue bluetooth icon in my tray, and my bluetooth mouse works.

gyro

Pro
Posts: 109
Joined: Fri 12 Feb 2010, 11:12

#34 Post by Pro »

Jwm not use xdg? I launch bluetooth.sh from /etc/xdg/autostart/ this way work for all standart desktop.

Thanks you, i change main.conf and enable option by default

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#35 Post by gyro »

Pro wrote:Jwm not use xdg? I launch bluetooth.sh from /etc/xdg/autostart/ this way work for all standart desktop
No, it does not, at least it doesn't in the Puppies I use, e.g. xenialpup, upupbb.
gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#36 Post by gyro »

After getting my bluetooth mouse to work, my wifi became very slow and flaky.
Apparently this is a known problem with some wifi drivers.
It is reported that the interference is caused by bluetooth and wifi competing for the 2.4GHz wireless.
Fortunately my local wifi acces point (router) provides a network in both 2.4GHz and 5GHz bands.
So I re-configured the laptop to connect to the 5GHz network, problem solved.

gyro

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#37 Post by perdido »

http://murga-linux.com/puppy/viewtopic. ... 90#1015390
Pro wrote:it's for bluez4 or bluez5?

I do something like this, maybe it will be useful for you
http://murga-linux.com/puppy/viewtopic.php?t=111331
This looks interesting, will report back.
Thank You

.

Pro
Posts: 109
Joined: Fri 12 Feb 2010, 11:12

#38 Post by Pro »

.

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#39 Post by perdido »

Thanks for your interest from the other thread. :)

Report back - no success
Computer Dell E6400 XFR
Bluetooth device(s)
0a5c:5800 Broadcomm BCM2046B1 USB Hub part of BCM2046 Bluetooth I always see this device every boot -{in output from lsusb}
413c:8187 Dell DW375 Bluetooth Module I only see this device when using some versions of bluez 4.xx -{in output from lsusb}
(these two devices are the integrated bluetooth, it is really only one component)

Using upupbb-18.05 bionic beaver (32-bit) Running as ~root
Installed the puppybt-5.7-bluez5.50-pr01.sfs
Installed the Devx
Installed ntf-0.9-any package

Launched puppybt
Got the following error
"Dbus "System" session not started'
check your Dbus launch script or service
"

Tried the following commands
-----
dbus-uuidgen --ensure
dbus-daemon --system
-----

Also tried editing puppybt line 14
first time commented out
second time tried changes suggested by gyro -
edited "puppybt" to change line 14 from
Code:
[ -e /run/dbus/system_bus_socket ]
to
Code:
[ -e /var/run/dbus/system_bus_socket ]

Ran bluetooth.sh
Killall found no processes to kill

Tried to launch puppybt again
Got the following error
"Error
Local bluetooth device not found
"
- --̶ ̶-̶L̶o̶o̶k̶s̶ ̶l̶i̶k̶e̶ ̶t̶h̶e̶ ̶D̶b̶u̶s̶ ̶s̶e̶s̶s̶i̶o̶n̶ ̶i̶s̶ ̶s̶t̶a̶r̶t̶e̶d̶ ̶n̶o̶w̶!̶-̶ ̶-̶ ̶- -
-------------------------------------------------------
I have never seen the 413c:8187 Dell DW375 bluetooth device listed in lsusb when trying any version of bluez 5.xx
I have seen the 413c:8187 Dell DW375 listed in lsusb when trying some versions of bluez 4.xx

There are problems with this bluetooth device, there are problem reports all over the internet.
https://linux-hardware.org/index.php?id=usb:413c-8187


.
Last edited by perdido on Thu 17 Jan 2019, 07:30, edited 1 time in total.

Pro
Posts: 109
Joined: Fri 12 Feb 2010, 11:12

#40 Post by Pro »

perdido wrote: -------------------------------------------------------
I have never seen the 413c:8187 Dell DW375 bluetooth device listed in lsusb when trying any version of bluez 5.xx
I have seen the 413c:8187 Dell DW375 listed in lsusb when trying some versions of bluez 4.xx
check lsmod or dmesg (btusb, bluetooth kernel module launched?)
lsusb not guarantee that the device works!

bluetooth.sh - script for autolaunch with xorg starts, run only puppybt for testing.
Check update puppybt from github, i not upload latest module because I need to solve the problem with simple pair device.

User avatar
perdido
Posts: 1528
Joined: Mon 09 Dec 2013, 16:29
Location: ¿Altair IV , Just north of Eeyore Junction.?

#41 Post by perdido »

Pro wrote:
perdido wrote: -------------------------------------------------------
I have never seen the 413c:8187 Dell DW375 bluetooth device listed in lsusb when trying any version of bluez 5.xx
I have seen the 413c:8187 Dell DW375 listed in lsusb when trying some versions of bluez 4.xx
check lsmod or dmesg (btusb, bluetooth kernel module launched?)
lsusb not guarantee that the device works!

bluetooth.sh - script for autolaunch with xorg starts, run only puppybt for testing.
Check update puppybt from github, i not upload latest module because I need to solve the problem with simple pair device.
Same software still loaded from yesterday
------------------------------------------------------------
dmesg shows no bluetooth
lsmod -shows no bluetooth driver (btusb module not loaded)
modprobe btusb - loads module ok
lsmod -now shows btusb module loaded
rfkill list bluetooth - not listed

dmesg now shows
Bluetooth: HCI device and connector manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usbcore: registered new interface driver btusb

Tried to run puppybt
Still get the error
"Error
Local bluetooth device not found"
Check update puppybt from github, i not upload latest module because I need to solve the problem with simple pair device.
I see no updated puppybt from github?

lsusb shows no Dell Wireless bluetooth device
My thought is this device needs to get initialized

Will post back after more checks
----------------------------------------------------------------------------
After more checks
Final report- I am not going to try to initialize my bluetooth with bluez 5.xx
I believe this is a hardware problem between bluez 5.xx and my bluetooth adapter.

Thanks for your help. If I get another bluetooth adapter I will be back!

.

Pro
Posts: 109
Joined: Fri 12 Feb 2010, 11:12

#42 Post by Pro »

perdido wrote: After more checks
Final report- I am not going to try to initialize my bluetooth with bluez 5.xx
I believe this is a hardware problem between bluez 5.xx and my bluetooth adapter.

Thanks for your help. If I get another bluetooth adapter I will be back!

.
NO, this is not bluez5 problem, you kernel not recognize and not load needed kernel modules. hci0 not created. Without this in dmesg, bluetoothd non work:

Code: Select all

Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
If hci0 not created - bluez5 (and bluez4 also) not work. Try launch bluetoothd from therminal, may be one lib not found...

my lsmod list loaded: btusb, btintel, btbcm, bluetooth, btrtl, bnep

kernel version 4.14.90

Post Reply