Instabilities when returning from idle mode and delay when detecting Intel bluetooth [8087:07da] peripherals

[Edson T. Marques]

I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I return to my desk I go back to using my notebook that went into idle mode. In addition, I realize that when turning on the computer and entering the Ubuntu login interface, there is a relevant delay before the bluetooth peripherals (mouse and keyboard) are detected. The time difference is very relevant compared to what happened at Eoan.
Whenever I leave the idle mode, the mouse pointer became slow, with unstable and heavy movements. The keyboard also has erratic and strange functioning.
I have an old sony vaio notebook and use a wireless keyboard and mouse communicating directly with the notebook's bluetooth without the need for adapters (dongle). The Mouse is an original sony vaio that I bought with the notebook, the keyboard, unlike, was recently purchased.
For now the workaround solution I've been applying is to turn bluetooth off and on again, through the gnome configuration panel. In fact, whenever I do this, there is again a long delay before the peripherals are detected. I need to keep moving the mouse for about 10 to 20 seconds for detection to occur. I need to type on the keyboard many times until detection occurs.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-bluetooth 3.34.1-1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 08:46:37 2020
InstallationDate: Installed on 2020-01-28 (86 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: etm 2253 F.... pulseaudio
 /dev/snd/pcmC0D0p: etm 2253 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-01-28 (86 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
MachineType: Sony Corporation SVS151290X
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-26-generic N/A
 linux-backports-modules-5.4.0-26-generic N/A
 linux-firmware 1.187
Tags: focal
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare sudo tty uuidd video voice
_MarkForUpload: True
dmi.bios.date: 03/13/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1021C8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS151290X:pvrC60BKPK7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVS151290X
dmi.product.sku: 54520726
dmi.product.version: C60BKPK7
dmi.sys.vendor: Sony Corporation

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1874713

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[Edson T. Marques (edsontmarques)]

apport information

[You-Sheng Yang (vicamo)]

Does blacklisting the power saving option in tlp work for you?

Open the tlp configuration file using the terminal: gksu gedit /etc/default/tlp and search the line containing: USB_BLACKLIST= Then edit this line and enter the ID of the bluetooth device, e.g. USB_BLACKLIST="8087:07da"

[Edson T. Marques (edsontmarques)]

It seems that the cause is tlp. I made adjustments to the suggested line (thanks You-Sheng Yang) and got some improvement in the detection time of the mouse and keyboard (the keyboard is still slow but less worse). I will monitor what happens when I return from idle mode.

[Edson T. Marques (edsontmarques)]

Unfortunately the problem has not been completely solved, if I can put it that way.
First (before) of all, I had already installed the Slimboot Battery 3 (an application for controlling battery consumption that uses tlp). So I used its configuration interfaces to define the USB blacklist and I also disabled the "Bluetooth device deactivation" ... after that I noticed that the reconnection time of the peripherals decreased a little ... However the return of the idle mode continued keeping erratic mouse behavior.
So I uninstalled Slimboot and then removed all remnants of it manually, only the TLP was maintained, with the suggested configuration changes (I installed TLPGUI to check it out) ... Well, in the end, even so the problems continued.
Finally I decided to remove all the TLP, TLPGUI and all its configuration traces, restarted the computer and, as in other times, continued the slight improvement of the keyboard and mouse connection time (in the login interface), but in the execution of the system, when returning from idle mode, mouse pointer continues to have a problem, slow and heavy locomotion, keyboard taking time to reconnect and failing in the first seconds after connection.
For now I keep turning off and on again the bluetooth to return to normal.
As the changes I made affected the initial behavior, I think the problem may be related, in fact, to the TLP. Perhaps a new installation of ubuntu can guarantee that this will resolve itself ... but I can't do that right now.