Bluetooth is shut down, then started again, very often
I am using UbuntuStudio 18.10 on Asus S300CA.
In the past I had issues with Linux distros and bluetooth: the adapter was recognized but after some reboots it disappeared (and sometimes to appear again) because it was like not present on the hardware. Now I solved this issue by installing this particular distro, that in fact has not that issue, it's the first one to be useful to me as to bluetooth: the bluetooth is alsways recognized and shown on the menu bar at boot. But every some minutes the bluetooth disappears and after some seconds it appears again. If I am using the bluetooth mouse I get aware of that because it is not responding. It is very frustrating. Similar issue with the bluetooth headphones. I applied many suggested changes to settings, this is a very common issue, but no way. I would like to understand why it is so difficult to solve it. I mean it is a drastic disappearance, shut down of the bluetooth, why? If the blueman applet is opened I see that all devices disappear and it is greyed out. The icon disappears from the menu bar. How to check out which service is shutting down the bluetooth at regular time intervals. How to disable this useless action on my system? Thank you in advance |
Quote:
Quote:
This isn't a difficult problem to solve, and it's well documented. |
My bluetooth keeps disconnecting and reconnecting. Many times in day.
I changed my OS and now my system is: (ASUS S300CA laptop) Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-29-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3317U CPU @ 1.70GHz Memory: 3,7 GiB of RAM Here's some log from /var/log/syslog: Code:
Oct 2 13:23:09 pc kernel: [12566.632409] Bluetooth: hci0: corrupted ACL packet Is there a solution? I can run some script also if necessary. I found this script but it doesn't work for me (I do not know what it does or if it is safe, if you want to try it, use it only if you are aware of possible risks and consequences) Code:
# Prevents the Bluetooth USB card from getting reset which disconnects the mouse https://ubuntuforums.org/showthread....0#post12926730 the device id should be right, but I am not 100% sure because I found only this: Bus 001 Device 014: ID 13d3:3402 IMC Networks command bluetoothctl --version output bluetoothctl: 5.50 command hciconfig -a output hci0: Type: Primary Bus: USB BD Address: 6C:71:D9:50:6E:2C ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:339336 acl:16949 sco:0 events:101 errors:3 TX bytes:5375 acl:34 sco:0 commands:63 errors:0 Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'pc' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0x102 LMP Version: 4.0 (0x6) Subversion: 0x1 Manufacturer: Atheros Communications, Inc. (69) command rfkill list output 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 5: hci0: Bluetooth Soft blocked: no Hard blocked: no I am interested in finding the moment when it happens so I can detect it in a script and restart immediately. Thank you in advance |
Quote:
Quote:
Quote:
|
@TB0ne
You did neither understand what's written in July nor in October. The bluetooth is disconnected while I am using the mouse, so no idle state. I do not know how to say you more clearly not to answer my questions, as you are not very good at reading or thinking. You are wasted here. You'd better register an account on Quora so you can share your condition with scientists and the people. |
Quote:
Again, set the value stated; if you bothered to read the 'dangerous' script you posted, you'd see what it's doing, but you do not understand THAT script either. You have been given a solution (twice), but I don't think it can be explained simply enough for you to understand. Quote:
Quote:
|
@TB0ne
As I said, it's you not reading carefully. In the first post I have written: Quote:
If you have not a clever solution or a suggestion how to perform advanced troubleshooting please do not bother answering again, please. |
Quote:
Quote:
Quote:
You have NOT shown any efforts, told us what you've done/tried (again, as with most of your other threads), and continue to rehash the same thing, without providing any information or answering questions. |
I solved the problem with a workaround. I do not know if it is safe for the system, so use it only if you are aware of risks and consequences.
To have a stable bluetooth for mouse and headphone using I programmed crontab this way: 4,9,14,19,24,29,34,39,44,49,54,59 * * * * bluetoothctl power on I think it should work also with large time intervals, I am currently testing and experimenting it. Also it is necessary to run the above mentioned script. I think these two are the things that are making my bluetooth work. But I have to say that previously I blacklisted the bluetooth disconnection adding these two lines to a certain configuration file. Code:
HOOK_BLACKLIST="wireless" And I set the idle timeout value for bluetooth=0 (in /etc/bluetooth/input.conf if I remember). I do not know whether those two additions are necessary. I think it is enough to run the script and set the crontab recurring event. It is up to you how to set them permanently on your system, if you need it and it is safe. So the issue is not "solved" as to the knowledge of what is involved in the bluetooth disconnection event (maybe an hardware/firmware weakness of my laptop, in combination with Linux - every distro I have used for now). |
All times are GMT -5. The time now is 04:59 PM. |