I don't think they go to sleep that fast, they just stop being
discoverable. The 30 year old engineer that designed them thought that
would be plenty of time. My pi kept going non-discoverable about 4 times
as I was sitting in front of it. This phone stays discoverable as long as
the Bluetooth s
On Saturday 26 September 2020 09:45:20 Alan Corey wrote:
> I moved the base to my earbuds downstairs and connected to this Pi.
> Some notes:
>
> Some of these things get cached, here B1 shows up twice at different
> addresses:
>
> devices
> Device CB:20:07:42:99:64 B1
> Device F3:66:48:29:CA:7D I
Gene Heskett wrote:
> But wouldn't that be only if the phones were going to be used on the pi?
> I made no attempt to pair them since that is not where the phones will
> be used when they arrive at the rest home 40 some one way miles away
> from that pi.
I must admit, I did not understand all you
Alan Corey wrote:
> My phone has lots of subdevices, I don't know how to connect to any of
> them yet either
what make/model is your phone, because I see you have OBEX FTP and I have
not seen this in recent phones?
Reco wrote:
> Proper Debian does not provide this package, and a certain popular
> GNU/Linux distribution for Raspberry Pi is an off-topic here.
may be we have to move to the raspberry-pi list, agreed, gut I think you
know Gene :)
Alan Corey wrote:
> bluetoothctl's info feature can be useful to see what states devices
> are in even if you're not pairing with them. Especially devices with
> few buttons.
>
> Yes there's a time limit because being discoverable is considered
> vulnerable.
Actually you can set up the discover
Dear list members,
On Sat, Sep 26, 2020 at 12:08:32PM -0400, Alan Corey wrote:
> My phone has lots of subdevices, I don't know how to connect to any of
> them yet either
Could you *please* move this enlightening discussion to debian-user, or,
preferrably, elsewhere?
First, there's nothin
On Saturday 26 September 2020 08:23:14 Alan Corey wrote:
> bluetoothctl's info feature can be useful to see what states devices
> are in even if you're not pairing with them. Especially devices with
> few buttons.
>
> Yes there's a time limit because being discoverable is considered
> vulnerable.
My phone has lots of subdevices, I don't know how to connect to any of
them yet either
info F8:CF:C5:00:F0:E2
Device F8:CF:C5:00:F0:E2 (public)
Name: MotoE2(4G-LTE)
Alias: MotoE2(4G-LTE)
Class: 0x005a020c
Icon: phone
Paired: yes
Trusted: yes
I moved the base to my earbuds downstairs and connected to this Pi. Some notes:
Some of these things get cached, here B1 shows up twice at different
addresses:
devices
Device CB:20:07:42:99:64 B1
Device F3:66:48:29:CA:7D IDTW211R
Device FE:46:6D:40:FC:43 B1
[CHG] Controller B8:27:EB:1F:69:7C Dis
bluetoothctl's info feature can be useful to see what states devices
are in even if you're not pairing with them. Especially devices with
few buttons.
Yes there's a time limit because being discoverable is considered vulnerable.
On 9/26/20, Gene Heskett wrote:
> On Saturday 26 September 2020 06
On Saturday 26 September 2020 06:48:11 Alan Corey wrote:
> Bring your devices closer together at least until you get them paired.
> BT doesn't have great range. There are covid tracing schemes which
> figure if you got within BT range you're in danger. 20 feet or so
> should be OK. Also heavy W
On Saturday 26 September 2020 04:22:31 deloptes wrote:
> Gene Heskett wrote:
> > Can anyone else contribute here?
>
> for the audio you may need the pulse bluetooth module package.
> pulseaudio-module-bluetooth
But wouldn't that be only if the phones were going to be used on the pi?
I ma
On Saturday 26 September 2020 04:15:10 deloptes wrote:
> Gene Heskett wrote:
> > Can anyone else contribute here?
>
> What specification of BT hardware does your keyboard implement?
It doesn't say in the booklet accompanying the keyboard. And I don't
recall seeing an FCC statement about it, whic
Bring your devices closer together at least until you get them paired. BT
doesn't have great range. There are covid tracing schemes which figure if
you got within BT range you're in danger. 20 feet or so should be OK. Also
heavy WiFi use disrupts it since they're both in the same frequency band.
Gene Heskett wrote:
> Can anyone else contribute here?
for the audio you may need the pulse bluetooth module package.
pulseaudio-module-bluetooth
Gene Heskett wrote:
> Can anyone else contribute here?
What specification of BT hardware does your keyboard implement?
The current linux version bluez5 seem to be working well with BT HW version
4, but not always with BT HW v2.
Perhaps post make and model.
Also do you have BT HID installed/confi
17 matches
Mail list logo
