Carsten Haitzler <ras...@rasterman.com> ezt írta (időpont: 2022. jan. 20., Cs, 12:12): > > On Thu, 20 Jan 2022 11:13:36 +0100 "ezerot...@gmail.com" <ezerot...@gmail.com> > said: > > > Hi, > > > > My .e-log.log has tons of log messages from l2ping. I've the 'power' > > checkbox switched off, yet new messages appear every 6 seconds. Is > > this intentional? How should this l2ping work? > > that's e pining a device you set to a lock device most likely. they need to be > pinged to see if they are there (to do it reliably). i guess it still pings > when > powered off (and well the ping fails of course...). i think it may have also > pinged if you enabled force connect - i have since removed that option as it > doesn't seem needed. > > i can indeed stop the pings if the bt adapter is unpowered that the bt device > is attached to.
Yes, that would be nice. I'm not sure if l2ping is the problem but sometimes my headphone does not connect, until I unload the bluez5 module. When the problem happens this is what I see in bluetoothctl: [CHG] Controller 68:54:5A:A9:F2:6C Powered: yes [CHG] Device 38:18:4C:1A:35:20 Connected: yes [CHG] Device 38:18:4C:1A:35:20 Connected: no [CHG] Device 38:18:4C:1A:35:20 Connected: yes [CHG] Device 38:18:4C:1A:35:20 Connected: no [CHG] Device 38:18:4C:1A:35:20 Connected: yes [CHG] Device 38:18:4C:1A:35:20 Connected: no [CHG] Device 38:18:4C:1A:35:20 Connected: yes [CHG] Device 38:18:4C:1A:35:20 Connected: no [CHG] Device 38:18:4C:1A:35:20 Connected: yes [CHG] Device 38:18:4C:1A:35:20 Connected: no [CHG] Device 38:18:4C:1A:35:20 Connected: yes [CHG] Device 38:18:4C:1A:35:20 Connected: no The yes/no states change every few seconds. After unloading the module and powering on the adapter the headset connects without problems. This is what I have in .e-log.log: =================== unlock: 0/0 === _devices_eval... === dev: 38:18:4C:1A:35:20|38:18:4C:1A:35:20 [WH-1000XM3] === 38:18:4C:1A:35:20 need_ping=0 conn=1 ping_ok=0 =================== unlock: 0/0 E_SYSTEM_ERR: l2ping: Size 16 echo for [38:18:4C:1A:35:20] does not match 44 === _devices_eval... === dev: 38:18:4C:1A:35:20|38:18:4C:1A:35:20 [WH-1000XM3] === 38:18:4C:1A:35:20 force con, not conn, ping ok=0 === 38:18:4C:1A:35:20 need_ping=1 conn=0 ping_ok=0 @@@ run new ping 38:18:4C:1A:35:20 5000 @@@ new ping in 6,000 Should I try to update to the module version which no longer has the force connection stuff? > > Is it possible to add support for switching the 'power' checkbox by > > middle clicking on the bluetooth icon in the shelf? And maybe changing > > the icon to see whether bluetooth is enabled/disabled? > > there isn't a middle click for power - you can have multiple bt adapters and > each can be rfkilled/powered separately (they are the same for e - an > unpowered device will be rf blocked and powered will be unblocked as bluez > refuses to touch any rfkill state and so you can easily have a perfectly > powered bt adapter that refuses to work because its rf kill blocked by default > on boot). Okay, I see. It could still make sense when there is only 1 adapter in the host? Laszlo _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
