Unable to bond with Miband 1s and Android 6.0 #349

Closed
by foutchi opened 5 years ago · 42 comments
foutchi commented 5 years ago (Migrated from github.com)
Owner

Hi,

I've been trying to use your app since about 2 weeks. More than often, the band isn't even detected and when it's detected, I'm unable to bond.

I've read a lot of the other issue but everything I've tried yet is not working.

I've even tried to downgrade the firmware of my Miband without success.
nRF control master see the band, is able to connect to it but unable to bond.

Hi, I've been trying to use your app since about 2 weeks. More than often, the band isn't even detected and when it's detected, I'm unable to bond. I've read a lot of the other issue but everything I've tried yet is not working. I've even tried to downgrade the firmware of my Miband without success. nRF control master see the band, is able to connect to it but unable to bond.
Owner

See #330, you cannot run MiFit and Gadgetbridge in parallel. You have to deactivate or uninstall MiFit because it effectively prevents Gadgetbridge from functioning.

See #330, you cannot run MiFit and Gadgetbridge in parallel. You have to deactivate or uninstall MiFit because it effectively prevents Gadgetbridge from functioning.
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

i've already read it and close / uninstalled Mi fit ... No other bluetooth app are running and still not able to connect... i'm not a noob btw i've look into the forum for 2 weeks already.
Here what' i've done to help you understand my situation with your app.

  • Clear bluetooth cache
  • forget all bluetooth devices
    -Uninstall all bluetooth related apps
    -Reinstall GB
  • try to pair with band = unsuccessful.
    -download Mifit connect perfectly
  • Uninstall Mi fit / GB
    -Flash phone to factory Default
    -re-download GB
    -Try to connect = not working unable to bond
    -Reinstall all from scratch

Now, It's still not able to connect.
-GB see the band,
-It ask me to enter my info (i've entered them)
-GB never bond with Miband (after more than 10 mins.)

i've already read it and close / uninstalled Mi fit ... No other bluetooth app are running and still not able to connect... i'm not a noob btw i've look into the forum for 2 weeks already. Here what' i've done to help you understand my situation with your app. - Clear bluetooth cache - forget all bluetooth devices -Uninstall all bluetooth related apps -Reinstall GB - try to pair with band = unsuccessful. -download Mifit connect perfectly - Uninstall Mi fit / GB -Flash phone to factory Default -re-download GB -Try to connect = not working unable to bond -Reinstall all from scratch Now, It's still not able to connect. -GB see the band, -It ask me to enter my info (i've entered them) -GB never bond with Miband (after more than 10 mins.)
Owner

Closing Mi Fit seems to not help, probably because there's still some kind of background service running. Uninstalling should definitely cure this, though.

So when it tries to bond, the band never blinks, right? What happens if you abort and press the back button? Do you see your band as entry in the list, then? If so, what happens when you tap the entry? It should connect to the band and, if necessary, initiate the pairing.

If you do not see the band in the list (after cancelling the unsuccessful bonding), then the bluetooth-level pairing did not work. Is your band visible in the standard bluetooth pairing dialog? Marked as paired or not?

If all is negative, can you provide a log as documented in our wiki?

Closing Mi Fit seems to not help, probably because there's still some kind of background service running. Uninstalling should definitely cure this, though. So when it tries to bond, the band never blinks, right? What happens if you abort and press the back button? Do you see your band as entry in the list, then? If so, what happens when you tap the entry? It should connect to the band and, if necessary, initiate the pairing. If you do not see the band in the list (after cancelling the unsuccessful bonding), then the bluetooth-level pairing did not work. Is your band visible in the standard bluetooth pairing dialog? Marked as paired or not? If all is negative, can you provide a log as documented in our wiki?
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

Hi, Sorry for the delay... I was on a fishing trip so no internet.

There we go:
1, I've uninstalled the Mifit app, forget the all the bluetooth devices and clear bluetooth cache.
2. Yes, exactly, The band is recognize but never blink or vibe. When I go back, I see the band is detected and it's say that it's creating the bond with the band but without success.
3. The band is visible from bluetooth settings, but i'm unable to "pair" it like a bluetooth headset for example.

mili_log.txt

Hi, Sorry for the delay... I was on a fishing trip so no internet. There we go: 1, I've uninstalled the Mifit app, forget the all the bluetooth devices and clear bluetooth cache. 2. Yes, exactly, The band is recognize but never blink or vibe. When I go back, I see the band is detected and it's say that it's creating the bond with the band but without success. 3. The band is visible from bluetooth settings, but i'm unable to "pair" it like a bluetooth headset for example. [mili_log.txt](https://github.com/Freeyourgadget/Gadgetbridge/files/344554/mili_log.txt)
robin13 commented 5 years ago (Migrated from github.com)
Owner

Have you updated the Mi 1S to the latest firmware with the Mi Fit App?

Have you updated the Mi 1S to the latest firmware with the Mi Fit App?
Owner

Thanks for the log, but this is the Mifit log, not the Gadgetbridge log :-) Please have a look at our wiki how to enable and access the Gadgetbridge log.

Other than that, if you're band is listed in gadgetbridge's default screen, you can simply tap the entry to connect to it. In cafe it needs authentication with the band, the band will start to blink and then you will have to tap it. All this without Mifit interfering, of course.

Thanks for the log, but this is the Mifit log, not the Gadgetbridge log :-) Please have a look at our wiki how to enable and access the Gadgetbridge log. Other than that, if you're band is listed in gadgetbridge's default screen, you can simply tap the entry to connect to it. In cafe it needs authentication with the band, the band will start to blink and then you will have to tap it. All this without Mifit interfering, of course.
Owner

PS: hope you caught some good fish :-)

PS: hope you caught some good fish :-)
rd999 commented 5 years ago (Migrated from github.com)
Owner

Hi everyone.
I've same problem like foutchi described 3 comments above. I can connect with MiFit and pair it. After I unpair in MiFit, clear MiFit cache, remove MiFit and restart the phone I can still not pair with GB. Band is found and visible in GB but it does not pair. It is also visible in Bluetooth device list of Android. Band version is 4.16.3.7 HR 1.3.76.18, should be newest version IMHO.
I also entered the MAC manually and tried to get GB working again but that hasn't worked too.
Also tried to clear cache of GB and removed / reinstalled it.
Would provide a log file but after switched log files on I only get a 0 byte one without content.
Currently using newest GB version 0.11.0.

Hi everyone. I've same problem like foutchi described 3 comments above. I can connect with MiFit and pair it. After I unpair in MiFit, clear MiFit cache, remove MiFit and restart the phone I can still not pair with GB. Band is found and visible in GB but it does not pair. It is also visible in Bluetooth device list of Android. Band version is 4.16.3.7 HR 1.3.76.18, should be newest version IMHO. I also entered the MAC manually and tried to get GB working again but that hasn't worked too. Also tried to clear cache of GB and removed / reinstalled it. Would provide a log file but after switched log files on I only get a 0 byte one without content. Currently using newest GB version 0.11.0.
robin13 commented 5 years ago (Migrated from github.com)
Owner

I have 4.16.4.22 and found that the phone had to be closer to the band for
pairing than for sync afterwards. Try lying band right next to phone.

On Tue, 5 Jul 2016, 21:12 rd999, notifications@github.com wrote:

Hi everyone.
I've same problem like foutchi described 3 comments above. I can connect
with MiFit and pair it. After I unpair in MiFit, clear MiFit cache, remove
MiFit and restart the phone I can still not pair with GB. Band is found and
visible in GB but it does not pair. It is also visible in Bluetooth device
list of Android. Band version is 4.16.3.7 HR 1.3.76.18, should be newest
version IMHO.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Freeyourgadget/Gadgetbridge/issues/349#issuecomment-230573865,
or mute the thread
https://github.com/notifications/unsubscribe/AAKo0-MdiwehcfOV0un-fEfJfCGkOM35ks5qSqyngaJpZM4JCGIe
.

I have 4.16.4.22 and found that the phone had to be closer to the band for pairing than for sync afterwards. Try lying band right next to phone. On Tue, 5 Jul 2016, 21:12 rd999, notifications@github.com wrote: > Hi everyone. > I've same problem like foutchi described 3 comments above. I can connect > with MiFit and pair it. After I unpair in MiFit, clear MiFit cache, remove > MiFit and restart the phone I can still not pair with GB. Band is found and > visible in GB but it does not pair. It is also visible in Bluetooth device > list of Android. Band version is 4.16.3.7 HR 1.3.76.18, should be newest > version IMHO. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > https://github.com/Freeyourgadget/Gadgetbridge/issues/349#issuecomment-230573865, > or mute the thread > https://github.com/notifications/unsubscribe/AAKo0-MdiwehcfOV0un-fEfJfCGkOM35ks5qSqyngaJpZM4JCGIe > .
Owner

First, if you remove Mi Fit, there's no need to to clear its cache. It should also not be necessary to unpair the band in Mi Fit. Just removing or deactivating Mi Fit should be sufficient to keep it from interfering with Gadgetbridge.

The Pairing activity in Gadgetbridge really only performs a Bluetooth level pairing with the Mi Band (so called bonding). The rest is just giving the user a hint to perform the application level pairing by taping the band when it blinks.

Once the band is paired on Bluetooth level (which can also be done in the Android Bluetooth Pairing activity), every time you (try to) connect to your band, it will perform the application level pairing, if needed.

So, if your band is paired on Bluetooth level, most things should be fine and Gadgetbridge should already display the band.

If coming from Mi Fit, connecting to the band by tapping the item should perform the application level pairing, because the user information is most probably a little different.

I'm interesting in two things:

  • does the Bluetooth pairing work or fail?
  • does the application level pairing fail?

If you have log files of failing attempts, I'd love to see them.

First, if you remove Mi Fit, there's no need to to clear its cache. It should also not be necessary to unpair the band in Mi Fit. Just removing or deactivating Mi Fit should be sufficient to keep it from interfering with Gadgetbridge. The Pairing activity in Gadgetbridge really only performs a Bluetooth level pairing with the Mi Band (so called bonding). The rest is just giving the user a hint to perform the application level pairing by taping the band when it blinks. Once the band is paired on Bluetooth level (which can also be done in the Android Bluetooth Pairing activity), every time you (try to) connect to your band, it will perform the application level pairing, if needed. So, if your band is paired on Bluetooth level, most things should be fine and Gadgetbridge should already display the band. If coming from Mi Fit, connecting to the band by tapping the item should perform the application level pairing, because the user information is most probably a little different. I'm interesting in two things: - does the Bluetooth pairing work or fail? - does the application level pairing fail? If you have log files of failing attempts, I'd love to see them.
Owner

BTW, the next version should provide a bit more log output and have better device recognition that is not based on a mac address filter anymore.

And finally: if the discovery activity does not show your device, try a few times. Mi Band consumes very little battery and apparently advertises itself not so often.

BTW, the next version should provide a bit more log output and have better device recognition that is not based on a mac address filter anymore. And finally: if the discovery activity does not show your device, try a few times. Mi Band consumes very little battery and apparently advertises itself not so often.
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

Hi all,
@robin13 -Yes I have the latest firmware (on the first band)
- The band is on the wrist of the hand that hold the phone.. I don't think that I can be closer physically than that ;).
Thank you very much for the input.
@cpfeiffer

  1. 1st band has stopped working alltogether i'm doing the fridge test.
  2. I've already asked for an exchange with the dealer who sold me the first band and I've received it today.
  3. I've never pair it with anything yet.
  4. I've enabled the developper option in settings and tried to find the log. Even after rebooting it's empty.
  5. Now the app is trying to create a bond with the band. Without succcess.
  6. It's impossible to see the band in bluetooth phone settings.
Hi all, @robin13 -Yes I have the latest firmware (on the first band) - The band is on the wrist of the hand that hold the phone.. I don't think that I can be closer physically than that ;). Thank you very much for the input. @cpfeiffer 1. 1st band has stopped working alltogether i'm doing the fridge test. 2. I've already asked for an exchange with the dealer who sold me the first band and I've received it today. 3. I've never pair it with anything yet. 4. I've enabled the developper option in settings and tried to find the log. Even after rebooting it's empty. 5. Now the app is trying to create a bond with the band. Without succcess. 6. It's impossible to see the band in bluetooth phone settings.
rd999 commented 5 years ago (Migrated from github.com)
Owner

Many thanks for the quick response from so many people. I'm very glad that the community is vital for GB

@robin13: I had the MiBand1s aprox 15 centimeter away from phone. Same distance with MiFit where it worked. Both phone and band statically laying on the desk. I don't think this distance is a problem.

@cpfeiffer: About your questions:

  • does the Bluetooth pairing work or fail?
    I see the MiBand1s in Android's list of Bluetooth devices but cannot pair neither with Android nor with GB.
  • does the application level pairing fail?
    Pairing with MiFit is working perfectly. I tried it many times in last view weeks.

I'd love to send you the log files. I already sent some in the past but in this case it is like foutchi describes: The log file is created and I see it in GhostCommander but it is 0 bytes large means empty.

I will try next GB version. Would also try a developer version if someone provides me one. I want to support this great project even if I nearly have time for something like this because of my family.

Many thanks for the quick response from so many people. I'm very glad that the community is vital for GB @robin13: I had the MiBand1s aprox 15 centimeter away from phone. Same distance with MiFit where it worked. Both phone and band statically laying on the desk. I don't think this distance is a problem. @cpfeiffer: About your questions: - does the Bluetooth pairing work or fail? I see the MiBand1s in Android's list of Bluetooth devices but cannot pair neither with Android nor with GB. - does the application level pairing fail? Pairing with MiFit is working perfectly. I tried it many times in last view weeks. I'd love to send you the log files. I already sent some in the past but in this case it is like foutchi describes: The log file is created and I see it in GhostCommander but it is 0 bytes large means empty. I will try next GB version. Would also try a developer version if someone provides me one. I want to support this great project even if I nearly have time for something like this because of my family.
Owner

@foutchi The log will be filled once you start connecting to your band. However, @rd999 also appears to have problems with logs. @ashimokawa has a theory that it might be a permission problem. I.e. that the log file is actually correct, but you lack the permission to access the file. He experienced the same on a device with dual boot (CM + Omnirom).

We will fix logging (once more) in a different way.

If you don't see the band, even in bluetooth settings, I'm not sure what we could do. Is it charged? Does it display on another phone?

@foutchi The log will be filled once you start connecting to your band. However, @rd999 also appears to have problems with logs. @ashimokawa has a theory that it might be a permission problem. I.e. that the log file is actually correct, but you lack the permission to access the file. He experienced the same on a device with dual boot (CM + Omnirom). We will fix logging (once more) in a different way. If you don't see the band, even in bluetooth settings, I'm not sure what we could do. Is it charged? Does it display on another phone?
Owner

@rd999 I'd love to find out why you can't pair the device, but it will take a bit of time. Right now I have no idea why it might fail to pair in GB and Android, but work in Mi Fit.

Even if Gadgetbridge's logging does not work for you, you might create a bluetooth snoop (enable it in android's development settings). Two different logs, once where Mi Fit successfully bonds and one from Gadgetbridge would help tremendously.

@rd999 I'd love to find out why you can't pair the device, but it will take a bit of time. Right now I have no idea why it might fail to pair in GB and Android, but work in Mi Fit. Even if Gadgetbridge's logging does not work for you, you might create a bluetooth snoop (enable it in android's development settings). Two different logs, once where Mi Fit successfully bonds and one from Gadgetbridge would help tremendously.
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

@cpfeiffer Sorry about that, for an unexplicable reason after rebooting the phone the band appears. In any ways, I will wait after the update for the loggin issue and I will send you the log.

We'll see what happen then. I don't want it to update the firmware yet, so I will wait to pair it un MiFit.

@cpfeiffer Sorry about that, for an unexplicable reason after rebooting the phone the band appears. In any ways, I will wait after the update for the loggin issue and I will send you the log. We'll see what happen then. I don't want it to update the firmware yet, so I will wait to pair it un MiFit.
rd999 commented 5 years ago (Migrated from github.com)
Owner

I don't know why but now / today I still see an empty log file BUT besides some information in a log-zip:

21:13:43.925 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.0
21:13:46.756 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed
21:13:46.758 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false
21:13:47.692 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created
21:13:47.692 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:13:47.698 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:13:48.687 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT
21:13:48.692 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery
21:13:54.636 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery
21:13:54.722 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:33:A9:A3
21:16:47.894 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:16:47.895 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:16:49.278 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed
21:16:49.279 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false
21:16:58.886 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created
21:16:58.888 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:16:58.897 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:17:00.392 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT
21:17:00.399 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery
21:17:12.314 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:17:12.315 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:17:19.730 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT
21:17:19.733 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery
21:17:25.182 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery
21:17:25.298 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:33:A9:A3
21:18:00.407 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery
21:18:16.339 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:18:16.339 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:18:17.703 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed
21:18:17.704 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false
21:18:25.102 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created
21:18:25.106 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:18:25.113 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:18:26.494 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT
21:18:26.498 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery
21:18:27.871 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery
21:18:27.972 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:33:A9:A3
21:19:16.926 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:19:16.929 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:19:18.175 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed
21:19:18.176 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false
21:31:31.707 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created
21:31:31.708 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:31:31.723 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:31:33.041 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT
21:31:33.045 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery
21:31:36.313 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
21:31:36.314 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
21:32:34.006 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery
21:52:35.707 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed
21:52:35.708 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false

I don't know why but now / today I still see an empty log file BUT besides some information in a log-zip: 21:13:43.925 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.0 21:13:46.756 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed 21:13:46.758 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false 21:13:47.692 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created 21:13:47.692 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:13:47.698 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:13:48.687 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT 21:13:48.692 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery 21:13:54.636 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery 21:13:54.722 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:33:A9:A3 21:16:47.894 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:16:47.895 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:16:49.278 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed 21:16:49.279 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false 21:16:58.886 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created 21:16:58.888 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:16:58.897 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:17:00.392 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT 21:17:00.399 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery 21:17:12.314 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:17:12.315 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:17:19.730 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT 21:17:19.733 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery 21:17:25.182 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery 21:17:25.298 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:33:A9:A3 21:18:00.407 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery 21:18:16.339 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:18:16.339 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:18:17.703 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed 21:18:17.704 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false 21:18:25.102 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created 21:18:25.106 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:18:25.113 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:18:26.494 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT 21:18:26.498 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery 21:18:27.871 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery 21:18:27.972 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:33:A9:A3 21:19:16.926 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:19:16.929 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:19:18.175 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed 21:19:18.176 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false 21:31:31.707 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created 21:31:31.708 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:31:31.723 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:31:33.041 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT 21:31:33.045 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery 21:31:36.313 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 21:31:36.314 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 21:32:34.006 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery 21:52:35.707 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed 21:52:35.708 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false
Seb-3 commented 5 years ago (Migrated from github.com)
Owner

Hi guys,
I have exactly the same Problem as described by foutchi.

  • I can see the 1S in Bluetooth Setting but am unable to connect
  • I can see the 1S in GB but am unable to bond
  • It did work with MiFit (even if it was a big hustle)
  • I did reset Bluetooth Cache and uninstalled MiFit before trying to bond within GB

I can send you also the logs and maybe debug - am new in this area but keen to learn ;)

at last: really appreciate that you built the app!

BR,
Seb

Hi guys, I have exactly the same Problem as described by foutchi. - I can see the 1S in Bluetooth Setting but am unable to connect - I can see the 1S in GB but am unable to bond - It did work with MiFit (even if it was a big hustle) - I did reset Bluetooth Cache and uninstalled MiFit before trying to bond within GB I can send you also the logs and maybe debug - am new in this area but keen to learn ;) at last: really appreciate that you built the app! BR, Seb
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

Hi guys, Still unable to got a log from GB therefore I can give you one from MIband paired and working. Maybe that could help @cpfeiffer
mili_log_20160707074217.txt

Hi guys, Still unable to got a log from GB therefore I can give you one from MIband paired and working. Maybe that could help @cpfeiffer [mili_log_20160707074217.txt](https://github.com/Freeyourgadget/Gadgetbridge/files/352099/mili_log_20160707074217.txt)
Owner

@foutchi Thanks for the log -- I'm afraid it won't help to discover why it's not working with Gadgetbridge. I will still have a look at it.

However @rd999 posted an interesting log. It contains a very unusual thing: our service that does all the communication with the bands is being destroyed all the time. We do restart it, but it's destroyed shortly after, so no wonder that this won't work.

At the moment I have no idea why this would happen, I've never seen something like this.

I also don't know if this is the same cause for all the mentioned connection problems, but it might very well be.

It might give a clue if you could try connecting with Gadgetbridge on a different device that had no Mi Fit installed before. And maybe we should start gathering some information the used

  • mobile device (e.g. Samsung Galaxy S4)
  • OS vendor (e.g. Cyanogenmod)
  • OS version (e.g. 5.1)
  • whether other bluetooth devices are used/connected, and if so, which
  • whether some "rogue" system programs are installed, like virus scanners or the like
@foutchi Thanks for the log -- I'm afraid it won't help to discover why it's _not_ working with Gadgetbridge. I will still have a look at it. However @rd999 posted an interesting log. It contains a very unusual thing: our service that does all the communication with the bands is being destroyed all the time. We do restart it, but it's destroyed shortly after, so no wonder that this won't work. At the moment I have _no idea_ why this would happen, I've never seen something like this. I also don't know if this is the same cause for all the mentioned connection problems, but it might very well be. It might give a clue if you could try connecting with Gadgetbridge on a different device that had no Mi Fit installed before. And maybe we should start gathering some information the used - mobile device (e.g. Samsung Galaxy S4) - OS vendor (e.g. Cyanogenmod) - OS version (e.g. 5.1) - whether other bluetooth devices are used/connected, and if so, which - whether some "rogue" system programs are installed, like virus scanners or the like
Owner

@Seb-3 welcome to the club :-) Yes, logs and help with debugging this is most appreciated.
Please, use the newest version from f-droid (0.11.1 as of now).

Thanks!

@Seb-3 welcome to the club :-) Yes, logs and help with debugging this is most appreciated. Please, use the newest version from f-droid (0.11.1 as of now). Thanks!
Owner

@foutchi and others who have problems accessing the log files: three things:

  1. while Gadgetbridge is running, the log files are still being written, so maybe your OS prevents reading the files that are currently "open for writing". Usually this is not a problem, but apparently it is a problem for some people.

  2. when there is enough log output, or a day has passed by, the log file is rotated, so the currently log file is closed and zipped and a new one is being created. So even if you cannot access the current log, you should be able to read yesterday's and earlier zipped logs.

  3. we'll change logging once more to accomodate for this problem.

@foutchi and others who have problems accessing the log files: three things: 1) while Gadgetbridge is running, the log files are still being written, so maybe your OS prevents reading the files that are currently "open for writing". Usually this is not a problem, but apparently it is a problem for some people. 2) when there is enough log output, or a day has passed by, the log file is rotated, so the currently log file is closed and zipped and a new one is being created. So even if you cannot access the current log, you should be able to read yesterday's and earlier zipped logs. 3) we'll change logging _once more_ to accomodate for this problem.
Owner

Another wild guess: could you check the permissions that you granted or not granted to Gadgetbridge? Maybe we lack a permission on your systems and get killed due to that.

Another wild guess: could you check the permissions that you granted or not granted to Gadgetbridge? Maybe we lack a permission on your systems and get killed due to that.
Seb-3 commented 5 years ago (Migrated from github.com)
Owner

Checked. All permissions granted already. No log file is written for me as well... current version is 0.10.0 I will upgrade tomorrow...

Checked. All permissions granted already. No log file is written for me as well... current version is 0.10.0 I will upgrade tomorrow...
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

@cpfeiffer

LG g4
original OS (really thinking about flashing it to CM to test. afraid of voiding warranty.)
6.0.1
No other bluetooth devices are connected or have been connected since the factory reset. (yes. i've been so far with this.)
No virus scanner or app like this is installed.
All permission are granted.
The version 11.1 is not available through f-droid yet. Can't try it.

Still no logs.

I've tried ALL miband apps on the play store (only to see) and surprisingly I have the same problem with another app (gliderun) But it's the only one else that I have this problem with.

The app Miband notification and fitness is able to connect With Mifit and without mifit installed.

Cheers.

@cpfeiffer LG g4 original OS (really thinking about flashing it to CM to test. afraid of voiding warranty.) 6.0.1 No other bluetooth devices are connected or have been connected since the factory reset. (yes. i've been so far with this.) No virus scanner or app like this is installed. All permission are granted. The version 11.1 is not available through f-droid yet. Can't try it. Still no logs. I've tried ALL miband apps on the play store (only to see) and surprisingly I have the same problem with another app (gliderun) But it's the only one else that I have this problem with. The app Miband notification and fitness is able to connect With Mifit and without mifit installed. Cheers.
Owner

0.11.1 is available on f-droid (you can download it from the website if your store does not list it yet).

0.11.1 is available on f-droid (you can download it from the website if your store does not list it yet).
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

Hi. I didn't though about the website since i'm mainly on my cell.

I've installed it and If i go through the windows explorer to grab the log it's still a 0kb. BUT If i look at it from my phone I can see it's 15.9kb so there is something in it. I've copied it in another folder in my phone and now I can transfer it to the computer and add it here.

I wish it can help you to understand the situation.

17:05:06.200 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.1
17:05:32.952 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created
17:05:32.954 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
17:05:32.966 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
17:05:34.232 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT
17:05:34.244 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery
17:05:49.686 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery
17:05:49.765 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:7A:37:39
17:06:15.728 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery
17:06:15.806 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:7A:37:39
17:07:26.717 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:07:26.720 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:11:43.512 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:11:43.513 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:11:43.541 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:11:43.544 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:11:43.696 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:11:43.698 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:11:43.715 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:11:43.716 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:12:02.009 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:12:02.009 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:12:02.053 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:12:02.054 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:12:02.138 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:12:02.140 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:12:02.153 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:12:02.154 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:12:02.187 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:12:02.188 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:12:02.201 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:12:02.203 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:12:02.759 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:12:02.760 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:16:33.907 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:16:33.909 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:16:33.936 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:16:33.936 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:16:34.026 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:16:34.029 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:16:34.052 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:16:34.053 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:16:34.137 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:16:34.138 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:16:34.159 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:16:34.160 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:20:54.248 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:20:54.250 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:20:54.300 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:20:54.303 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:20:54.449 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:20:54.451 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:20:54.468 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:20:54.469 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:24:33.798 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:24:33.801 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:24:33.840 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:24:33.842 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:24:33.948 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:24:33.951 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:24:34.016 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:24:34.017 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:24:34.044 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:24:34.047 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:24:34.062 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:24:34.063 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:27:58.720 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:27:58.725 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:27:58.752 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:27:58.753 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:27:58.888 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:27:58.888 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:27:58.922 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:27:58.924 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:27:58.938 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:27:58.938 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.035 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.037 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.072 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.074 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.195 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.196 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.220 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.222 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.244 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.245 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.269 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.271 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.600 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.602 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:28:15.621 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:28:15.622 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:32:30.954 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:32:30.956 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:32:30.992 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:32:30.994 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:32:31.058 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:32:31.058 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:32:31.074 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:32:31.074 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:32:31.351 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:32:31.351 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:32:31.361 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:32:31.367 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:32:31.464 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:32:31.465 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:37:04.091 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:37:04.093 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:37:04.109 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:37:04.109 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
17:37:04.256 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
17:37:04.257 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate

Hi. I didn't though about the website since i'm mainly on my cell. I've installed it and If i go through the windows explorer to grab the log it's still a 0kb. BUT If i look at it from my phone I can see it's 15.9kb so there is something in it. I've copied it in another folder in my phone and now I can transfer it to the computer and add it here. I wish it can help you to understand the situation. 17:05:06.200 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.1 17:05:32.952 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created 17:05:32.954 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 17:05:32.966 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 17:05:34.232 [main] INFO n.f.g.a.DiscoveryActivity - Starting discovery: SCANNING_BT 17:05:34.244 [main] INFO n.f.g.a.DiscoveryActivity - Starting BT Discovery 17:05:49.686 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery 17:05:49.765 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:7A:37:39 17:06:15.728 [main] INFO n.f.g.a.DiscoveryActivity - Stopping discovery 17:06:15.806 [main] INFO n.f.g.u.GB - Creating bond withC8:0F:10:7A:37:39 17:07:26.717 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:07:26.720 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:11:43.512 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:11:43.513 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:11:43.541 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:11:43.544 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:11:43.696 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:11:43.698 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:11:43.715 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:11:43.716 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:12:02.009 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:12:02.009 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:12:02.053 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:12:02.054 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:12:02.138 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:12:02.140 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:12:02.153 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:12:02.154 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:12:02.187 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:12:02.188 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:12:02.201 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:12:02.203 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:12:02.759 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:12:02.760 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:16:33.907 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:16:33.909 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:16:33.936 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:16:33.936 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:16:34.026 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:16:34.029 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:16:34.052 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:16:34.053 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:16:34.137 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:16:34.138 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:16:34.159 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:16:34.160 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:20:54.248 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:20:54.250 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:20:54.300 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:20:54.303 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:20:54.449 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:20:54.451 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:20:54.468 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:20:54.469 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:24:33.798 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:24:33.801 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:24:33.840 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:24:33.842 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:24:33.948 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:24:33.951 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:24:34.016 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:24:34.017 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:24:34.044 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:24:34.047 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:24:34.062 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:24:34.063 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:27:58.720 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:27:58.725 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:27:58.752 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:27:58.753 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:27:58.888 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:27:58.888 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:27:58.922 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:27:58.924 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:27:58.938 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:27:58.938 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.035 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.037 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.072 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.074 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.195 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.196 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.220 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.222 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.244 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.245 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.269 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.271 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.600 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.602 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:28:15.621 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:28:15.622 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:32:30.954 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:32:30.956 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:32:30.992 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:32:30.994 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:32:31.058 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:32:31.058 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:32:31.074 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:32:31.074 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:32:31.351 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:32:31.351 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:32:31.361 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:32:31.367 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:32:31.464 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:32:31.465 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:37:04.091 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:37:04.093 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:37:04.109 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:37:04.109 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate 17:37:04.256 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 17:37:04.257 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicstate
Owner

@foutchi Thanks for the log! It tells us that the device doesn't pair, it simply does not respond positively to our request. I've added even more logging -- this should explicitly tell us that the bonding failed. I don't know why, though.

So, can you try one thing: can you enter your Mi's mac address into the "Development MI Mac Address" field in the MI Band Preferences?

This should make your band visible in Gadgetbridge's main activity, even though it is not paired. Then try to connect to it. I'm interested in what happens then (please provide the log, if you can).

Good luck!

@foutchi Thanks for the log! It tells us that the device doesn't pair, it simply does not respond positively to our request. I've added even more logging -- this should explicitly tell us that the bonding failed. I don't know why, though. So, can you try one thing: can you enter your Mi's mac address into the "Development MI Mac Address" field in the MI Band Preferences? This should make your band visible in Gadgetbridge's main activity, even though it is not paired. Then try to connect to it. I'm interested in what happens then (please provide the log, if you can). Good luck!
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

Hi, There what i've have for log with the Miband Mac address in the specified place.

18:27:54.407 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.1
18:30:38.500 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
18:30:38.508 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
18:33:33.588 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
18:33:33.609 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
18:33:35.817 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
18:33:35.844 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
18:33:35.845 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
18:33:35.867 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
18:33:35.871 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:33:36.230 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
18:33:36.231 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
18:33:36.233 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
18:33:36.233 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
18:33:36.235 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
18:33:36.241 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S)
18:33:36.241 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:33:37.132 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
18:33:37.132 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
18:33:37.140 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
18:33:37.141 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
18:33:37.142 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
18:33:37.225 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:33:37 GMT)
18:33:37.226 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
18:33:37.227 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:33:37: Transaction task: Initializing device with 21 actions
18:33:37.232 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: SetDeviceStateAction to INITIALIZING
18:33:37.234 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:33:37.234 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
18:33:37.237 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
18:33:37.312 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
18:33:37.313 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
18:33:37.407 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
18:33:37.409 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
18:33:37.553 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
18:33:37.554 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:33
18:33:37.556 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
18:33:37.800 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
18:33:37.801 [Binder_4] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
18:33:40.921 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
18:33:40.922 [Binder_3] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
18:33:40.923 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
18:33:40.924 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
18:33:40.925 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
18:33:40.926 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:33:40.927 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:33:40.927 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:33:40.933 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
18:33:40.941 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:33:40.954 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:33:48.237 [main] INFO n.f.g.e.AlarmReceiver - won't send sunrise and sunset events (disabled in preferences)
18:34:45.170 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
18:34:45.171 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:34:45.172 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
18:34:45.172 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
18:34:45.174 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
18:34:45.175 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
18:34:45.181 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
18:34:45.181 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:34:45.985 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
18:34:45.995 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
18:34:45.996 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
18:34:45.996 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
18:34:45.997 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S)
18:34:46.004 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:34:45.998 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
18:34:47.308 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
18:34:47.309 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
18:34:47.310 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
18:34:47.310 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
18:34:47.311 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
18:34:47.315 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:34:47 GMT)
18:34:47.317 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
18:34:47.318 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:34:47: Transaction task: Initializing device with 21 actions
18:34:47.319 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: SetDeviceStateAction to INITIALIZING
18:34:47.320 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
18:34:47.322 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:34:47.322 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
18:34:47.363 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
18:34:47.364 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
18:34:47.472 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
18:34:47.475 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
18:34:47.620 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
18:34:47.622 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:34
18:34:47.625 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
18:34:47.859 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
18:34:47.860 [Binder_4] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
18:34:51.009 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
18:34:51.010 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
18:34:51.010 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
18:34:51.010 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
18:34:51.010 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
18:34:51.011 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:34:51.011 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:34:51.012 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
18:34:51.012 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:34:51.028 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:34:51.044 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:03.732 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
18:35:03.733 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
18:35:03.747 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:04.576 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
18:35:04.577 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:35:04.579 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
18:35:04.579 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
18:35:04.579 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
18:35:04.581 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
18:35:04.585 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
18:35:04.585 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:05.778 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
18:35:05.779 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
18:35:05.780 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
18:35:05.782 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
18:35:05.781 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S)
18:35:05.783 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:05.784 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
18:35:06.219 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
18:35:06.220 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:06.909 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
18:35:06.909 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
18:35:06.909 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
18:35:06.909 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
18:35:06.909 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
18:35:06.911 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:35:06 GMT)
18:35:06.912 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
18:35:06.913 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:35:06: Transaction task: Initializing device with 21 actions
18:35:06.914 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: SetDeviceStateAction to INITIALIZING
18:35:06.918 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:06.920 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
18:35:06.922 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
18:35:06.953 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
18:35:06.954 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
18:35:06.956 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
18:35:06.958 [Binder_4] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
18:35:07.068 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
18:35:07.072 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
18:35:07.217 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
18:35:07.218 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:35
18:35:07.219 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
18:35:07.500 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
18:35:07.500 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
18:35:10.632 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
18:35:10.633 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
18:35:10.634 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
18:35:10.634 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
18:35:10.635 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
18:35:10.635 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:35:10.635 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:35:10.635 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:10.635 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
18:35:10.639 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:35:10.651 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:14.997 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
18:35:14.997 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:35:14.998 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
18:35:14.999 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
18:35:15.001 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
18:35:15.002 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
18:35:15.010 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
18:35:15.012 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:15.670 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
18:35:15.671 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
18:35:15.671 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
18:35:15.671 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
18:35:15.678 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S)
18:35:15.679 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:15.678 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
18:35:16.949 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
18:35:16.949 [Binder_4] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
18:35:16.949 [Binder_4] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
18:35:16.949 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
18:35:16.949 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
18:35:16.950 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:35:16 GMT)
18:35:16.951 [Binder_4] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
18:35:16.952 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:35:16: Transaction task: Initializing device with 21 actions
18:35:16.953 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: SetDeviceStateAction to INITIALIZING
18:35:16.957 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:16.957 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
18:35:16.959 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
18:35:16.984 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
18:35:16.985 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
18:35:16.994 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
18:35:16.995 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
18:35:17.050 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
18:35:17.051 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
18:35:17.210 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
18:35:17.212 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:35
18:35:17.214 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
18:35:17.479 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
18:35:17.480 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
18:35:20.557 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
18:35:20.558 [Binder_3] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
18:35:20.559 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
18:35:20.560 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
18:35:20.561 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
18:35:20.562 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:35:20.571 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:35:20.571 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:20.576 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
18:35:20.588 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
18:35:20.590 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:25.852 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
18:35:25.853 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
18:35:25.855 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
18:35:25.855 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
18:35:25.861 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
18:35:25.862 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
18:35:25.876 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
18:35:25.878 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:26.556 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
18:35:26.558 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
18:35:26.559 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
18:35:26.559 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
18:35:26.567 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
18:35:26.573 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S)
18:35:26.574 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:27.809 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
18:35:27.810 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
18:35:27.810 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
18:35:27.810 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
18:35:27.810 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
18:35:27.813 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:35:27 GMT)
18:35:27.814 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
18:35:27.816 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:35:27: Transaction task: Initializing device with 21 actions
18:35:27.825 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: SetDeviceStateAction to INITIALIZING
18:35:27.826 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
18:35:27.826 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
18:35:27.829 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
18:35:27.895 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
18:35:27.897 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
18:35:28.000 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
18:35:28.001 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb

I've tried about 10 time to connect without success. I've tried to tap the band Even if it didn't vibrate or flash..

Hi, There what i've have for log with the Miband Mac address in the specified place. 18:27:54.407 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.1 18:30:38.500 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 18:30:38.508 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 18:33:33.588 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 18:33:33.609 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 18:33:35.817 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 18:33:35.844 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 18:33:35.845 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 18:33:35.867 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 18:33:35.871 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:33:36.230 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 18:33:36.231 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 18:33:36.233 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 18:33:36.233 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 18:33:36.235 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 18:33:36.241 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S) 18:33:36.241 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:33:37.132 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 18:33:37.132 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 18:33:37.140 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 18:33:37.141 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 18:33:37.142 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 18:33:37.225 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:33:37 GMT) 18:33:37.226 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 18:33:37.227 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:33:37: Transaction task: Initializing device with 21 actions 18:33:37.232 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: SetDeviceStateAction to INITIALIZING 18:33:37.234 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:33:37.234 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 18:33:37.237 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 18:33:37.312 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 18:33:37.313 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 18:33:37.407 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 18:33:37.409 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 18:33:37.553 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 18:33:37.554 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:33 18:33:37.556 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:33: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 18:33:37.800 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 18:33:37.801 [Binder_4] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 18:33:40.921 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 18:33:40.922 [Binder_3] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 18:33:40.923 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 18:33:40.924 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 18:33:40.925 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 18:33:40.926 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:33:40.927 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:33:40.927 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:33:40.933 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 18:33:40.941 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:33:40.954 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:33:48.237 [main] INFO n.f.g.e.AlarmReceiver - won't send sunrise and sunset events (disabled in preferences) 18:34:45.170 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 18:34:45.171 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:34:45.172 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 18:34:45.172 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated. 18:34:45.174 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 18:34:45.175 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 18:34:45.181 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 18:34:45.181 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:34:45.985 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 18:34:45.995 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 18:34:45.996 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 18:34:45.996 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 18:34:45.997 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S) 18:34:46.004 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:34:45.998 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 18:34:47.308 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 18:34:47.309 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 18:34:47.310 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 18:34:47.310 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 18:34:47.311 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 18:34:47.315 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:34:47 GMT) 18:34:47.317 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 18:34:47.318 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:34:47: Transaction task: Initializing device with 21 actions 18:34:47.319 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: SetDeviceStateAction to INITIALIZING 18:34:47.320 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 18:34:47.322 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:34:47.322 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 18:34:47.363 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 18:34:47.364 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 18:34:47.472 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 18:34:47.475 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 18:34:47.620 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 18:34:47.622 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:34 18:34:47.625 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:34: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 18:34:47.859 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 18:34:47.860 [Binder_4] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 18:34:51.009 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 18:34:51.010 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 18:34:51.010 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 18:34:51.010 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 18:34:51.010 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 18:34:51.011 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:34:51.011 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:34:51.012 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 18:34:51.012 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:34:51.028 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:34:51.044 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:03.732 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 18:35:03.733 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 18:35:03.747 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:04.576 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 18:35:04.577 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:35:04.579 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 18:35:04.579 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 18:35:04.579 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated. 18:35:04.581 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 18:35:04.585 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 18:35:04.585 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:05.778 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 18:35:05.779 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 18:35:05.780 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 18:35:05.782 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 18:35:05.781 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S) 18:35:05.783 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:05.784 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 18:35:06.219 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 18:35:06.220 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:06.909 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 18:35:06.909 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 18:35:06.909 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 18:35:06.909 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 18:35:06.909 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 18:35:06.911 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:35:06 GMT) 18:35:06.912 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 18:35:06.913 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:35:06: Transaction task: Initializing device with 21 actions 18:35:06.914 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: SetDeviceStateAction to INITIALIZING 18:35:06.918 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:06.920 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 18:35:06.922 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 18:35:06.953 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 18:35:06.954 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 18:35:06.956 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 18:35:06.958 [Binder_4] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 18:35:07.068 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 18:35:07.072 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 18:35:07.217 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 18:35:07.218 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:35 18:35:07.219 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 18:35:07.500 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 18:35:07.500 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 18:35:10.632 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 18:35:10.633 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 18:35:10.634 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 18:35:10.634 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 18:35:10.635 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 18:35:10.635 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:35:10.635 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:35:10.635 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:10.635 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 18:35:10.639 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:35:10.651 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:14.997 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 18:35:14.997 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:35:14.998 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 18:35:14.999 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated. 18:35:15.001 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 18:35:15.002 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 18:35:15.010 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 18:35:15.012 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:15.670 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 18:35:15.671 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 18:35:15.671 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 18:35:15.671 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 18:35:15.678 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S) 18:35:15.679 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:15.678 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 18:35:16.949 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 18:35:16.949 [Binder_4] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 18:35:16.949 [Binder_4] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 18:35:16.949 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 18:35:16.949 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 18:35:16.950 [Binder_4] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:35:16 GMT) 18:35:16.951 [Binder_4] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 18:35:16.952 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:35:16: Transaction task: Initializing device with 21 actions 18:35:16.953 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: SetDeviceStateAction to INITIALIZING 18:35:16.957 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:16.957 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 18:35:16.959 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 18:35:16.984 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 18:35:16.985 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 18:35:16.994 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 18:35:16.995 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 18:35:17.050 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 18:35:17.051 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 18:35:17.210 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 18:35:17.212 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: July 10, 18:35 18:35:17.214 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 18:35:17.479 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 18:35:17.480 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 18:35:20.557 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 18:35:20.558 [Binder_3] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 18:35:20.559 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 18:35:20.560 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 18:35:20.561 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 18:35:20.562 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:35:20.571 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:35:20.571 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:20.576 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 18:35:20.588 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 18:35:20.590 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:25.852 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 18:35:25.853 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 18:35:25.855 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 18:35:25.855 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated. 18:35:25.861 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 18:35:25.862 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 18:35:25.876 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 18:35:25.878 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:26.556 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 18:35:26.558 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 18:35:26.559 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 18:35:26.559 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 18:35:26.567 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 18:35:26.573 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:36:0E:8A(MI1S) 18:35:26.574 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:27.809 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 18:35:27.810 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 18:35:27.810 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 18:35:27.810 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 18:35:27.810 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 18:35:27.813 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: July 10 (10 Jul 2016 22:35:27 GMT) 18:35:27.814 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 18:35:27.816 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - about to add: 18:35:27: Transaction task: Initializing device with 21 actions 18:35:27.825 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: SetDeviceStateAction to INITIALIZING 18:35:27.826 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 18:35:27.826 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 18:35:27.829 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 18:35:27.895 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 18:35:27.897 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 18:35:28.000 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 18:35:28.001 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: July 10, 18:35: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb I've tried about 10 time to connect without success. I've tried to tap the band Even if it didn't vibrate or flash..
Owner

Thanks, this most probably confirms the pairing problems. You can successfully connect to the band, and even read its data, but as soon as you do something more serious, you get disconnected with status 22 (which does not really say what it means, but I guess it's the missing pairing.

Now, what we could do is:

  1. test this after MiFit successfully paired the devices, after deactivating/uninstalling MiFit. I'm afraid that the band will remove the pairing, but it might be worth a try.

  2. I will update to the same firmware version that you have and see if I can still connect to my band afterwards

  3. It may be worthwhile do capture a lowlevel bluetooth snoop (trace) with Mi Fit to see if they perform a different pairing now (with a hardcoded pin, for example).

Thanks, this most probably confirms the pairing problems. You can successfully connect to the band, and even read its data, but as soon as you do something more serious, you get disconnected with status 22 (which does not really say what it means, but I guess it's the missing pairing. Now, what we could do is: 1) test this after MiFit successfully paired the devices, after deactivating/uninstalling MiFit. I'm afraid that the band will remove the pairing, but it might be worth a try. 2) I will update to the same firmware version that you have and see if I can still connect to my band afterwards 3) It may be worthwhile do capture a lowlevel bluetooth snoop (trace) with Mi Fit to see if they perform a different pairing now (with a hardcoded pin, for example).
Owner

@foutchi
It looks like this is a firmware problem. I updated to 4.16.4.22, the same version that you have. Right after that, connection works fine for me. But after unpairing the device, I can't discover it anymore. More experiments will follow...

@foutchi It looks like this is a firmware problem. I updated to 4.16.4.22, the same version that you have. Right after that, connection works fine for me. But after unpairing the device, I can't discover it anymore. More experiments will follow...
Owner

OK, I'll retract that. Even though it takes a few attempts to find the device, it does get discovered, I can successfully pair it and connect to it. So all is fine with the firmware, at least with my OnePlus One.

OK, I'll retract that. Even though it takes a few attempts to find the device, it does get discovered, I can successfully pair it and connect to it. So all is fine with the firmware, at least with my OnePlus One.
Seb-3 commented 5 years ago (Migrated from github.com)
Owner

Sorry guys, I'm unable to generate a Log file :(
Any hints why? I restarted the App, restarted the Phone but the files doesn't get generated... (and yes, the Logging Option is "on" ;) )

Nevertheless I will try the BT snoop as well and give you the results.

Sorry guys, I'm unable to generate a Log file :( Any hints why? I restarted the App, restarted the Phone but the files doesn't get generated... (and yes, the Logging Option is "on" ;) ) Nevertheless I will try the BT snoop as well and give you the results.
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

@Seb-3 I don't know if my procedure is right but what i've said is: downloaded the latest file on f-droid (on a computer/website) install it and reboot the phone. Enable loggin, then, start trying to connect. After a while, press the back button until you see the first screen, tap the 3 dots and select "quit"

I needed to copy the log from the original location to another folder in my phone (like "download" in this occurence.) Then from a computer copy it again directly on the PC. from there i've been able to open the log (never been able to paste it directly here because the site won't support .log files.) When it's opened, I've just had to copy the log from the .txt editor. I with it will help.

@cpfeiffer Would "nRF Master Control Panel (BLE)" with nRF logger help ?

@Seb-3 I don't know if my procedure is right but what i've said is: downloaded the latest file on f-droid (on a computer/website) install it and reboot the phone. Enable loggin, then, start trying to connect. After a while, press the back button until you see the first screen, tap the 3 dots and select "quit" I needed to copy the log from the original location to another folder in my phone (like "download" in this occurence.) Then from a computer copy it again directly on the PC. from there i've been able to open the log (never been able to paste it directly here because the site won't support .log files.) When it's opened, I've just had to copy the log from the .txt editor. I with it will help. @cpfeiffer Would "nRF Master Control Panel (BLE)" with nRF logger help ?
foutchi commented 5 years ago (Migrated from github.com)
Poster
Owner

I have this problem with 2 apps only.
I'll try to see if I can extract a log from the only app that works without being paired with Mifit first. (Miband notify & fitness.)
log.txt

I wish it'll help.

And I need to pair it manually with the mac adress to work. (If not connected to Mifit before.)

I have this problem with 2 apps only. I'll try to see if I can extract a log from the only app that works without being paired with Mifit first. (Miband notify & fitness.) [log.txt](https://github.com/Freeyourgadget/Gadgetbridge/files/359293/log.txt) I wish it'll help. And I need to pair it manually with the mac adress to work. (If not connected to Mifit before.)
Seb-3 commented 5 years ago (Migrated from github.com)
Owner

Found it... ^^

22:36:38.776 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created
22:36:38.777 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
22:36:38.787 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
22:36:44.958 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
22:36:44.960 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
22:36:44.961 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
22:36:45.005 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
22:36:45.022 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:36:45.041 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
22:36:46.916 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
22:36:46.916 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
22:36:46.916 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
22:36:46.917 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
22:36:46.932 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:36:47.848 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
22:36:47.849 [Binder_5] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
22:36:47.849 [Binder_5] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
22:36:47.851 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
22:36:47.852 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
22:36:47.858 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:36:47 GMT)
22:36:47.859 [Binder_5] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
22:36:47.860 [Binder_5] DEBUG n.f.g.s.b.BtLEQueue - about to add: 22:36:47: Transaction task: Initializing device with 21 actions
22:36:47.862 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: SetDeviceStateAction to INITIALIZING
22:36:47.862 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
22:36:47.863 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
22:36:47.891 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:36:47.951 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
22:36:47.952 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
22:36:48.049 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
22:36:48.049 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
22:36:48.196 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
22:36:48.196 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:36
22:36:48.197 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
22:36:48.404 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
22:36:48.404 [Binder_1] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
22:36:51.530 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
22:36:51.531 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
22:36:51.532 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
22:36:51.533 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
22:36:51.533 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
22:36:51.534 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:36:51.534 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
22:36:51.534 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
22:36:51.539 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:36:51.557 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:36:51.580 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:36:55.111 [main] INFO n.f.g.e.AlarmReceiver - won't send sunrise and sunset events (disabled in preferences)
22:37:00.340 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
22:37:00.340 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
22:37:00.364 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:37:01.929 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
22:37:01.930 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
22:37:01.931 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
22:37:01.932 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
22:37:01.934 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
22:37:01.935 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
22:37:01.986 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
22:37:01.988 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:37:02.404 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
22:37:02.405 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
22:37:02.406 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
22:37:02.407 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:37:02.411 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
22:37:03.600 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
22:37:03.601 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
22:37:03.602 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
22:37:03.603 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
22:37:03.604 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
22:37:03.608 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:37:03 GMT)
22:37:03.612 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
22:37:03.615 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 22:37:03: Transaction task: Initializing device with 21 actions
22:37:03.617 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:37: SetDeviceStateAction to INITIALIZING
22:37:03.618 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:37: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
22:37:03.619 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:37:50.724 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.1
22:59:26.499 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created
22:59:26.500 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
22:59:26.508 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
22:59:27.830 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
22:59:27.846 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
22:59:27.847 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
22:59:27.903 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
22:59:27.943 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:28.000 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo
22:59:28.152 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
22:59:28.159 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
22:59:28.160 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
22:59:28.161 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
22:59:28.168 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:5A:71:63(MI1S)
22:59:28.173 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
22:59:28.293 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:29.310 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
22:59:29.311 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
22:59:29.330 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
22:59:29.333 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
22:59:29.335 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
22:59:29.373 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:59:29 GMT)
22:59:29.375 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
22:59:29.377 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 10:59:29 PM: Transaction task: Initializing device with 21 actions
22:59:29.383 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: SetDeviceStateAction to INITIALIZING
22:59:29.385 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
22:59:29.393 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
22:59:29.429 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:29.458 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
22:59:29.460 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
22:59:29.553 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
22:59:29.556 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
22:59:29.698 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
22:59:29.700 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:59
22:59:29.701 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
22:59:29.957 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
22:59:29.959 [Binder_1] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
22:59:33.071 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
22:59:33.072 [Binder_2] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
22:59:33.073 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
22:59:33.074 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
22:59:33.075 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
22:59:33.076 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:59:33.077 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
22:59:33.078 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
22:59:33.171 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:59:33.263 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:33.311 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:36.257 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
22:59:36.258 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
22:59:36.259 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
22:59:36.259 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
22:59:36.261 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
22:59:36.261 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
22:59:36.312 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
22:59:36.368 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:36.791 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
22:59:36.802 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
22:59:36.802 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
22:59:36.803 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
22:59:36.814 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:5A:71:63(MI1S)
22:59:36.815 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
22:59:36.931 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:37.711 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
22:59:37.712 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
22:59:37.713 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
22:59:37.714 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
22:59:37.715 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
22:59:37.718 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:59:37 GMT)
22:59:37.720 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
22:59:37.722 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - about to add: 10:59:37 PM: Transaction task: Initializing device with 21 actions
22:59:37.725 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: SetDeviceStateAction to INITIALIZING
22:59:37.726 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
22:59:37.732 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
22:59:37.795 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
22:59:37.797 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
22:59:37.816 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:37.893 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
22:59:37.895 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
22:59:38.040 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
22:59:38.043 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:59
22:59:38.045 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
22:59:38.259 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
22:59:38.261 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
22:59:41.320 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
22:59:41.321 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
22:59:41.321 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
22:59:41.322 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
22:59:41.322 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
22:59:41.323 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:59:41.324 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
22:59:41.324 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
22:59:41.379 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:59:41.486 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:41.566 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:42.924 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect
22:59:42.925 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
22:59:42.926 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
22:59:42.926 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
22:59:42.928 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI
22:59:42.928 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started.
22:59:42.978 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING
22:59:43.024 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:43.382 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt
22:59:43.398 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success)
22:59:43.399 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server.
22:59:43.399 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED
22:59:43.410 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:5A:71:63(MI1S)
22:59:43.410 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true
22:59:43.543 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:44.319 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device...
22:59:44.320 [Binder_2] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info!
22:59:44.321 [Binder_2] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info!
22:59:44.322 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location...
22:59:44.323 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal...
22:59:44.327 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:59:44 GMT)
22:59:44.329 [Binder_2] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info!
22:59:44.331 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - about to add: 10:59:44 PM: Transaction task: Initializing device with 21 actions
22:59:44.334 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: SetDeviceStateAction to INITIALIZING
22:59:44.335 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb
22:59:44.339 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION
22:59:44.416 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success)
22:59:44.418 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb
22:59:44.437 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:44.512 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success)
22:59:44.514 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb
22:59:44.660 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success)
22:59:44.663 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:59
22:59:44.665 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb
22:59:44.918 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8
22:59:44.919 [Binder_3] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8
22:59:47.927 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22)
22:59:47.928 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22
22:59:47.929 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server.
22:59:47.930 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22
22:59:47.931 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null
22:59:47.932 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:59:47.934 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
22:59:47.935 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device
22:59:48.007 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED
22:59:48.119 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:48.179 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
22:59:59.335 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start
22:59:59.336 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo
22:59:59.375 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true
23:00:01.256 [main] INFO n.f.g.e.AlarmReceiver - won't send sunrise and sunset events (disabled in preferences)
23:00:01.626 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed
23:00:01.627 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false
23:00:01.644 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect()
23:00:01.644 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted
23:00:01.645 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.

Found it... ^^ 22:36:38.776 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created 22:36:38.777 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 22:36:38.787 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 22:36:44.958 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 22:36:44.960 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 22:36:44.961 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 22:36:45.005 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 22:36:45.022 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:36:45.041 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 22:36:46.916 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 22:36:46.916 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 22:36:46.916 [Binder_4] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 22:36:46.917 [Binder_4] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 22:36:46.932 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:36:47.848 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 22:36:47.849 [Binder_5] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 22:36:47.849 [Binder_5] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 22:36:47.851 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 22:36:47.852 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 22:36:47.858 [Binder_5] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:36:47 GMT) 22:36:47.859 [Binder_5] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 22:36:47.860 [Binder_5] DEBUG n.f.g.s.b.BtLEQueue - about to add: 22:36:47: Transaction task: Initializing device with 21 actions 22:36:47.862 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: SetDeviceStateAction to INITIALIZING 22:36:47.862 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 22:36:47.863 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 22:36:47.891 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:36:47.951 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 22:36:47.952 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 22:36:48.049 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 22:36:48.049 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 22:36:48.196 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 22:36:48.196 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:36 22:36:48.197 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:36: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 22:36:48.404 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 22:36:48.404 [Binder_1] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 22:36:51.530 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 22:36:51.531 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 22:36:51.532 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 22:36:51.533 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 22:36:51.533 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 22:36:51.534 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:36:51.534 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 22:36:51.534 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 22:36:51.539 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:36:51.557 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:36:51.580 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:36:55.111 [main] INFO n.f.g.e.AlarmReceiver - won't send sunrise and sunset events (disabled in preferences) 22:37:00.340 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 22:37:00.340 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 22:37:00.364 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:37:01.929 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 22:37:01.930 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 22:37:01.931 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 22:37:01.932 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated. 22:37:01.934 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 22:37:01.935 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 22:37:01.986 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 22:37:01.988 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:37:02.404 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 22:37:02.405 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 22:37:02.406 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 22:37:02.407 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:37:02.411 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 22:37:03.600 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 22:37:03.601 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 22:37:03.602 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 22:37:03.603 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 22:37:03.604 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 22:37:03.608 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:37:03 GMT) 22:37:03.612 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 22:37:03.615 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 22:37:03: Transaction task: Initializing device with 21 actions 22:37:03.617 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:37: SetDeviceStateAction to INITIALIZING 22:37:03.618 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:37: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 22:37:03.619 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:37:50.724 [main] INFO n.f.g.Logging - Gadgetbridge version: 0.11.1 22:59:26.499 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being created 22:59:26.500 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 22:59:26.508 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 22:59:27.830 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 22:59:27.846 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 22:59:27.847 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 22:59:27.903 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 22:59:27.943 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:28.000 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.setmusicinfo 22:59:28.152 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 22:59:28.159 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 22:59:28.160 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 22:59:28.161 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 22:59:28.168 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:5A:71:63(MI1S) 22:59:28.173 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 22:59:28.293 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:29.310 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 22:59:29.311 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 22:59:29.330 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 22:59:29.333 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 22:59:29.335 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 22:59:29.373 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:59:29 GMT) 22:59:29.375 [Binder_3] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 22:59:29.377 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - about to add: 10:59:29 PM: Transaction task: Initializing device with 21 actions 22:59:29.383 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: SetDeviceStateAction to INITIALIZING 22:59:29.385 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 22:59:29.393 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 22:59:29.429 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:29.458 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 22:59:29.460 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 22:59:29.553 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 22:59:29.556 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 22:59:29.698 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 22:59:29.700 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:59 22:59:29.701 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 22:59:29.957 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 22:59:29.959 [Binder_1] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 22:59:33.071 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 22:59:33.072 [Binder_2] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 22:59:33.073 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 22:59:33.074 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 22:59:33.075 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 22:59:33.076 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:59:33.077 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 22:59:33.078 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 22:59:33.171 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:59:33.263 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:33.311 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:36.257 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 22:59:36.258 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 22:59:36.259 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 22:59:36.259 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated. 22:59:36.261 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 22:59:36.261 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 22:59:36.312 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 22:59:36.368 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:36.791 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 22:59:36.802 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 22:59:36.802 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 22:59:36.803 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 22:59:36.814 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:5A:71:63(MI1S) 22:59:36.815 [Binder_2] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 22:59:36.931 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:37.711 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 22:59:37.712 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 22:59:37.713 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 22:59:37.714 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 22:59:37.715 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 22:59:37.718 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:59:37 GMT) 22:59:37.720 [Binder_1] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 22:59:37.722 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - about to add: 10:59:37 PM: Transaction task: Initializing device with 21 actions 22:59:37.725 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: SetDeviceStateAction to INITIALIZING 22:59:37.726 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 22:59:37.732 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 22:59:37.795 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 22:59:37.797 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 22:59:37.816 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:37.893 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 22:59:37.895 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 22:59:38.040 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 22:59:38.043 [Binder_1] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:59 22:59:38.045 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 22:59:38.259 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 22:59:38.261 [Binder_2] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 22:59:41.320 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 22:59:41.321 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 22:59:41.321 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 22:59:41.322 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 22:59:41.322 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 22:59:41.323 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:59:41.324 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 22:59:41.324 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 22:59:41.379 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:59:41.486 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:41.566 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:42.924 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.connect 22:59:42.925 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 22:59:42.926 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 22:59:42.926 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated. 22:59:42.928 [main] INFO n.f.g.s.b.BtLEQueue - Attempting to connect to MI 22:59:42.928 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Queue Dispatch Thread started. 22:59:42.978 [main] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTING 22:59:43.024 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:43.382 [main] INFO n.f.g.e.BluetoothConnectReceiver - got connection attempt 22:59:43.398 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 2 (success) 22:59:43.399 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Connected to GATT server. 22:59:43.399 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: CONNECTED 22:59:43.410 [main] INFO n.f.g.e.BluetoothConnectReceiver - won't connect to C8:0F:10:5A:71:63(MI1S) 22:59:43.410 [Binder_3] INFO n.f.g.s.b.BtLEQueue - Attempting to start service discovery:true 22:59:43.543 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:44.319 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Attempting to pair MI device... 22:59:44.320 [Binder_2] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Device Info! 22:59:44.321 [Binder_2] DEBUG n.f.g.s.d.m.MiBandSupport - Writing User Info! 22:59:44.322 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set wear location... 22:59:44.323 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Attempting to set Fitness Goal... 22:59:44.327 [Binder_2] INFO n.f.g.s.d.m.MiBandSupport - Sending current time to Mi Band: 10. Juli (10 Jul 2016 20:59:44 GMT) 22:59:44.329 [Binder_2] DEBUG n.f.g.s.d.m.MiBandSupport - Requesting Battery Info! 22:59:44.331 [Binder_2] DEBUG n.f.g.s.b.BtLEQueue - about to add: 10:59:44 PM: Transaction task: Initializing device with 21 actions 22:59:44.334 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: SetDeviceStateAction to INITIALIZING 22:59:44.335 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: NotifyAction on characteristic: 0000ff03-0000-1000-8000-00805f9b34fb 22:59:44.339 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.TransactionBuilder - use NOTIFICATION 22:59:44.416 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - descriptor write: 00002902-0000-1000-8000-00805f9b34fb (success) 22:59:44.418 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff09-0000-1000-8000-00805f9b34fb 22:59:44.437 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:44.512 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - characteristic write: 0000ff09-0000-1000-8000-00805f9b34fb (success) 22:59:44.514 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: ReadAction on characteristic: 0000ff0a-0000-1000-8000-00805f9b34fb 22:59:44.660 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic read: 0000ff0a-0000-1000-8000-00805f9b34fb (success) 22:59:44.663 [Binder_3] INFO n.f.g.s.d.m.MiBandSupport - Got Mi Band Date: 10. Juli, 22:59 22:59:44.665 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - About to run action: 10. Juli, 22:59: WriteAction on characteristic: 0000ff0f-0000-1000-8000-00805f9b34fb 22:59:44.918 [Binder_3] DEBUG n.f.g.s.b.BtLEQueue - characteristic changed: 0000ff03-0000-1000-8000-00805f9b34fb value: 0x8 22:59:44.919 [Binder_3] WARN n.f.g.s.d.m.MiBandSupport - DATA: 0x 8 22:59:47.927 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - connection state change, newState: 0 (failed: 22) 22:59:47.928 [Binder_1] WARN n.f.g.s.b.BtLEQueue - connection state event with error status 22 22:59:47.929 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnected from GATT server. 22:59:47.930 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - handleDisconnected: 22 22:59:47.931 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - internal gatt callback set to null 22:59:47.932 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:59:47.934 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 22:59:47.935 [Binder_1] INFO n.f.g.s.b.BtLEQueue - Disconnecting BtLEQueue from GATT device 22:59:48.007 [Binder_1] DEBUG n.f.g.s.b.BtLEQueue - new device connection state: NOT_CONNECTED 22:59:48.119 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:48.179 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 22:59:59.335 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.start 22:59:59.336 [main] DEBUG n.f.g.s.DeviceCommunicationService - Service startcommand: nodomain.freeyourgadget.gadgetbridge.devices.action.request_deviceinfo 22:59:59.375 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: true 23:00:01.256 [main] INFO n.f.g.e.AlarmReceiver - won't send sunrise and sunset events (disabled in preferences) 23:00:01.626 [main] DEBUG n.f.g.s.DeviceCommunicationService - DeviceCommunicationService is being destroyed 23:00:01.627 [main] INFO n.f.g.s.DeviceCommunicationService - Setting broadcast receivers to: false 23:00:01.644 [main] DEBUG n.f.g.s.b.BtLEQueue - disconnect() 23:00:01.644 [GadgetBridge GATT Dispatcher] DEBUG n.f.g.s.b.BtLEQueue - Thread interrupted 23:00:01.645 [GadgetBridge GATT Dispatcher] INFO n.f.g.s.b.BtLEQueue - Queue Dispatch Thread terminated.
Owner

Thanks for the log! The good thing is, that you both have the same problem (disconnect with status 22). So if we get to fix it, it will probably be fixed for both of you :-)

Thanks for the log! The good thing is, that you both have the same problem (disconnect with status 22). So if we get to fix it, it will probably be fixed for both of you :-)
Owner

I have a fix for you. I can now connect without the band being paired. We still try to pair the device because that's the right thing IMHO, but if it fails, we still try to connect to the band, which should not fail anymore.

I couldn'te completely test the the code that attempts to initiate the connection when pairing fails, because for me, pairing never fails. IF it does fail, you can connect to the device from the default Gadgetbridge screen. If you band is not listed there, enter your band's mac address into Preferences -> Mi Band Preferences -> Mi Band MAC Address

This is not perfect yet, but the biggest problem should be solved now. Please report back (0.11.2 is tagged, should be available on f-droid, soon).

I have a fix for you. I can now connect without the band being paired. We still try to pair the device because that's the right thing IMHO, but if it fails, we still try to connect to the band, which should not fail anymore. I couldn'te completely test the the code that attempts to initiate the connection when pairing fails, because for me, pairing never fails. IF it does fail, you can connect to the device from the default Gadgetbridge screen. If you band is not listed there, enter your band's mac address into Preferences -> Mi Band Preferences -> Mi Band MAC Address This is not perfect yet, but the biggest problem should be solved now. Please report back (0.11.2 is tagged, should be available on f-droid, soon).
tincore commented 5 years ago (Migrated from github.com)
Owner

Well done! That should work

Well done! That should work
Seb-3 commented 5 years ago (Migrated from github.com)
Owner

@cpfeiffer Thank you so much, it worked right away with the update!
I will try the app now a few days and see if I can contribute further :)

@cpfeiffer Thank you so much, it worked right away with the update! I will try the app now a few days and see if I can contribute further :)
Owner

Excellent, thanks for testing so quickly!

Excellent, thanks for testing so quickly!
rd999 commented 5 years ago (Migrated from github.com)
Owner

It worked for me too. With GB 0.11.2 I can now pair/connect again, by entering the MAC manually in Settings page.
Many thanks for the great support. GB is great.

It worked for me too. With GB 0.11.2 I can now pair/connect again, by entering the MAC manually in Settings page. Many thanks for the great support. GB is great.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.