Skip to content

Conversation

@scottleibrand
Copy link
Contributor

Fixes the newly added systemctl commands, whose start/restart bluetooth commands use an incorrect argument order, resulting in an inability for oref0-bluetoothup to automatically resolve bluetoothd issues.

@PedanticAvenger
Copy link
Contributor

Performing self-whipping.
ARgh

@scottleibrand
Copy link
Contributor Author

Can anyone post their results of testing this? Or do I need to just go ahead and merge it to dev for further testing there?

@rebecca-draben
Copy link
Contributor

Unfortunately, still having issues. BT connection dropped again today and did not reconnect. After about 50 minutes, power cycled my rig and then it reconnected on the next loop. Here are network logs from when it was not working.

At Mon Jul  1 13:47:03 EDT 2019 my wifi is not connected
At Mon Jul  1 13:47:03 EDT 2019 my local wifi IP is: unassigned
At Mon Jul  1 13:47:03 EDT 2019 my Bluetooth is connected to Galaxy S7 edge
At Mon Jul  1 13:47:03 EDT 2019 my local Bluetooth IP is: 192.168.44.121
At Mon Jul  1 13:47:03 EDT 2019 my public IP is: Bluetooth hci name does not match hostname: sweetbasal. Setting bluetooth hci name.
not found

At Mon Jul  1 13:47:09 EDT 2019 my wifi is not connected

Getting new wlan0 IP

No Internet access detected, attempting to connect BT to 20:2D:07:18:64:5E
Bluetooth hci name does not match hostname: sweetbasal. Setting bluetooth hci name.
Preference bt_offline enabled - already have a bt interface, not reconnecting it.
PING 192.168.44.1 (192.168.44.1) 56(84) bytes of data.

--- 192.168.44.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

bnep0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 58:a8:39:01:d7:40  txqueuelen 1000  (Ethernet)
        RX packets 59300  bytes 47758332 (45.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 82207  bytes 8493005 (8.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

--
wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether fc:db:b3:a6:98:17  txqueuelen 1000  (Ethernet)
        RX packets 566410  bytes 342229696 (326.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 244545  bytes 27987494 (26.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

No IP address assigned, cycling the bnep0 interface...done
Connected to Bluetooth with IP: unassigned

Offline hotspot not enabled in preferences.json
At Mon Jul  1 13:48:06 EDT 2019 my local hotspot is not running (and not enabled in preferences.json)
Cycling wlan0
Bluetooth hci name does not match hostname: sweetbasal. Setting bluetooth hci name.
Finished oref0-online at Mon Jul 1 13:48:30 EDT 2019.

@PedanticAvenger
Copy link
Contributor

The changes are working alright for me.
As to @WhatWouldHoneyBadgerDo issues, It looks like Bluetooth is just fine, the issue seems to be on the wifi side with it deciding things don't work. I wonder if this is potentially another dhclient.leases corruption issue.....

@rebecca-draben
Copy link
Contributor

Thanks @PedanticAvenger, I see what you are saying. I did see fewer problems yesterday than I did last week using the dev branch. And it seems to get farther with BT connection than it did using the dev branch. So this seems like a positive change.

@scottleibrand scottleibrand merged commit 3486d5e into dev Jul 2, 2019
@scottleibrand scottleibrand deleted the bluetoothup-syntax branch July 2, 2019 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants