#2094 Casio gb5600aa (1st generation) - Device request

Open
opened 2 weeks ago by egor2t · 21 comments
egor2t commented 2 weeks ago
name about
Bug report Create a report to help us improve

Before reporting a bug, please confirm the following:

I got Gadgetbridge from:

If you got it from Google Play, please note that version is unofficial and not supported here; it's also often quite outdated. Please switch to one of the above versions if you can.

Your issue is:

If possible, please attach logs! that might help identifying the problem.
Long logs can be also included but make sure to tuck them into the details tag:

Click to see my log, which is a bit longer
Here go lines of that log.

Your wearable device is:

Casio gb5600aa (1st generation)

Your android version is: 10

Your Gadgetbridge version is: 0.48

New issues about already solved/documented topics could be closed without further comments. Same for too generic or incomplete reports.

--- name: Bug report about: Create a report to help us improve --- #### Before reporting a bug, please confirm the following: - [x] I have read the [wiki](https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki), and I didn't find a solution to my problem / an answer to my question. - [x] I have searched the [issues](https://codeberg.org/Freeyourgadget/Gadgetbridge/issues), and I didn't find a solution to my problem / an answer to my question. - [ ] If you upload an image or other content, please make sure you have read and understood the [Codeberg Terms of Use](https://codeberg.org/codeberg/org/src/branch/master/TermsOfUse.md) ### I got Gadgetbridge from: * [x] F-Droid * [ ] I built it myself from source code (specify tag / commit) If you got it from Google Play, please note [that version](https://github.com/TaaviE/Gadgetbridge) is unofficial and not supported here; it's also often quite outdated. Please switch to one of the above versions if you can. #### Your issue is: *If possible, please attach [logs](https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Log-Files)! that might help identifying the problem.* *Long logs can be also included but make sure to tuck them into the `details` tag:* <details> <summary>Click to see my log, which is a bit longer</summary> ``` Here go lines of that log. ``` </details> #### Your wearable device is: Casio gb5600aa (1st generation) #### Your android version is: 10 #### Your Gadgetbridge version is: 0.48 *New issues about already solved/documented topics could be closed without further comments. Same for too generic or incomplete reports.*
izzy added the
device request
label 2 weeks ago
izzy commented 2 weeks ago
Poster

As the log got sooo long (hahaha), may I point you to our wiki for some details?

Our devs need some more details than just the name of the device. They don't have all devices, cannot buy all of them – and even if there wasn't the monetary restrictions, not all devices can be obtained easily everywhere 😉

As the log got sooo long (hahaha), may I point you to our wiki for some details? * [Support for a new Device](https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Support-for-a-new-Device) (end users) * [Support for a new Device](https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Support-for-a-new-Device) (users with (some) development knowledge) Our devs need some more details than just the name of the device. They don't have all devices, cannot buy all of them – and even if there wasn't the monetary restrictions, not all devices can be obtained easily everywhere :wink:
Poster
Owner

@andyboeh

Do you know if this is similar to the casio devices you maintain?

@andyboeh Do you know if this is similar to the casio devices you maintain?
andyboeh commented 2 weeks ago
Poster

The GB-5600A should be fairly similar if not identical to the GB-5600B which is already supported. The DeviceCoordinator in the currently released version matches only for "CASIO" anyway, so it might just work.

That said, the 5600A is even older than the 5600B (I own two 5600B and one 6900B, but none of the A models) and getting that to a somewhat reliable level was quite a challenge. The BLE implementation on the watch is quite buggy and there are Android devices where a stable connection cannot be maintained (due to the way Casio implemented BLE reconnect).

@egor2t Please try to connect to your watch (don't forget to delete pairing data from the watch and the smartphone first!) and upload a log file. If it succeeds to connect, some features won't work correctly because it doesn't know about this model.

NB: As soon as #2088 is merged, the DeviceCoordinator looks for the exact model string, not just for "CASIO"! If we can get the 5600A connected/supported, we need to explicitly enable support for it. #2088 already contains an update to the README stating that the 5600B and GB-X6900B are also supported, not just the 6900B.

The GB-5600A should be fairly similar if not identical to the GB-5600B which is already supported. The DeviceCoordinator in the currently released version matches only for "CASIO" anyway, so it might just work. That said, the 5600A is even older than the 5600B (I own two 5600B and one 6900B, but none of the A models) and getting that to a somewhat reliable level was quite a challenge. The BLE implementation on the watch is quite buggy and there are Android devices where a stable connection cannot be maintained (due to the way Casio implemented BLE reconnect). @egor2t Please try to connect to your watch (don't forget to delete pairing data from the watch and the smartphone first!) and upload a log file. If it succeeds to connect, some features won't work correctly because it doesn't know about this model. NB: As soon as #2088 is merged, the DeviceCoordinator looks for the exact model string, not just for "CASIO"! If we can get the 5600A connected/supported, we need to explicitly enable support for it. #2088 already contains an update to the README stating that the 5600B and GB-X6900B are also supported, not just the 6900B.
egor2t commented 2 weeks ago
Poster

@andyboeh I tried. program can't find my watches. OF course all previous pairing were deleted.

@andyboeh I tried. program can't find my watches. OF course all previous pairing were deleted.
andyboeh commented 1 week ago
Poster

What's the BLE name of your watch, does it not start with "CASIO"?
Can you run a BLE scanner on your phone, find out the watch's name and the supported device services / characteristics?

What's the BLE name of your watch, does it not start with "CASIO"? Can you run a BLE scanner on your phone, find out the watch's name and the supported device services / characteristics?
egor2t commented 1 week ago
Poster

plz find in attachment but i m not sure that what you asked

plz find in attachment but i m not sure that what you asked
andyboeh commented 1 week ago
Poster

I'm sorry, I have no clue on what you just sent. Here a more detailed approach:

  1. Unpair everything
  2. Enable Bluetooth on your watch
  3. Enable Bluetooth on your phone and scan for devices. What device name is reported for your watch?

For the BLE services and characteristics: I usually use "nRF Connect", but any other BLE scanner should do the trick:

  1. Start the BLE scanning app
  2. Wait for your watch to appear - you might have to disable and re-enable bluetooth on the watch
  3. Connect to the watch and scan for services and characteristics
  4. Report the UUIDs of the discovered the services and characteristics

As an example, the services (and characteristics) should follow this pattern: 26ebXXXX-b012-49a8-b1f8-394fb2032b0f

XXXX is replaced by some specific hex digits. It's actually enough to know these missing digits.

I'm sorry, I have no clue on what you just sent. Here a more detailed approach: 1. Unpair everything 2. Enable Bluetooth on your watch 3. Enable Bluetooth on your phone and scan for devices. What device name is reported for your watch? For the BLE services and characteristics: I usually use "nRF Connect", but any other BLE scanner should do the trick: 1. Start the BLE scanning app 2. Wait for your watch to appear - you might have to disable and re-enable bluetooth on the watch 3. Connect to the watch and scan for services and characteristics 4. Report the UUIDs of the discovered the services and characteristics As an example, the services (and characteristics) should follow this pattern: 26ebXXXX-b012-49a8-b1f8-394fb2032b0f XXXX is replaced by some specific hex digits. It's actually enough to know these missing digits.
egor2t commented 1 week ago
Poster

26eb0008-b012-49a8-b1f8-394fb2032b0f

26eb0008-b012-49a8-b1f8-394fb2032b0f
egor2t commented 1 week ago
Poster

Used nRF connect

Used nRF connect
andyboeh commented 1 week ago
Poster

So it bears CASIO in the name and it has one of the required services. Is "26eb0007-b012-49a8-b1f8-394fb2032b0f" also among the list of available services? That's the only reason why it might not be detected.
Please open the tab in nRF Connect and expand the services in order to see them.

So it bears CASIO in the name and it has one of the required services. Is "26eb0007-b012-49a8-b1f8-394fb2032b0f" also among the list of available services? That's the only reason why it might not be detected. Please open the tab in nRF Connect and expand the services in order to see them.
egor2t commented 1 week ago
Poster

sorry, once agaon i m not sure, that is what you asked.

sorry, once agaon i m not sure, that is what you asked.
andyboeh commented 1 week ago
Poster

This is exactly what I was asking for :) I'll analyze it soon.

This is exactly what I was asking for :) I'll analyze it soon.
andyboeh commented 1 week ago
Poster

OK, basically, all required services and characteristics are there and the device name matches. However, on your screenshot I see the GShock app - could you try uninstalling (or, at least, force-stopping) it before you try pairing with Gadgetbridge?

And, as usual, please delete all pairing information from watch and phone before you try it.

OK, basically, all required services and characteristics are there and the device name matches. However, on your screenshot I see the GShock app - could you try uninstalling (or, at least, force-stopping) it before you try pairing with Gadgetbridge? And, as usual, please delete all pairing information from watch and phone before you try it.
egor2t commented 1 week ago
Poster

dshock+ used for connection to my watches. gadgetbridge was used with uninstalled gshock programm and deleted all pairs.

dshock+ used for connection to my watches. gadgetbridge was used with uninstalled gshock programm and deleted all pairs.
egor2t commented 1 week ago
Poster

This is exactly what I was asking for :) I'll analyze it soon.

thnq

> This is exactly what I was asking for :) I'll analyze it soon. thnq
andyboeh commented 1 week ago
Poster

From my point of view, there is no reason why it shouldn't be detected. Did you try to check "Disable new BLE scanning" and/or "CompanionDevice Pairing" in Gadgetbridge's settings? You could also try to uncheck "Ignore bonded devices".

If that doesn't help, please enable "Write log files", try to scan for the watch and send me or upload the log file. The log usually contains a list of all discovered BT/BLE devices.

From my point of view, there is no reason why it shouldn't be detected. Did you try to check "Disable new BLE scanning" and/or "CompanionDevice Pairing" in Gadgetbridge's settings? You could also try to uncheck "Ignore bonded devices". If that doesn't help, please enable "Write log files", try to scan for the watch and send me or upload the log file. The log usually contains a list of all discovered BT/BLE devices.
egor2t commented 1 week ago
Poster

what is procedure? I have uninstalled gshock + , deleted all pairs. Run latest gadgetbridge (0,49). Programm was detected my watches Bluetooth LE only. I have connected it , and nothing more....
Should I uninstall nRF coonect programm (in log of this programm only 'connected' and 'disconnected')

what is procedure? I have uninstalled gshock + , deleted all pairs. Run latest gadgetbridge (0,49). Programm was detected my watches Bluetooth LE only. I have connected it , and nothing more.... Should I uninstall nRF coonect programm (in log of this programm only 'connected' and 'disconnected')
egor2t commented 1 week ago
Poster

Programm tried to connect...
in the same time was written that already linked.

Programm tried to connect... in the same time was written that already linked.
andyboeh commented 1 week ago
Poster

Would you please provide a log file? We need the part where Gadgetbridge tries to connect to the watch.

See https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Log-Files

Would you please provide a log file? We need the part where Gadgetbridge tries to connect to the watch. See https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Log-Files
egor2t commented 1 week ago
Poster

sorry, I tried to do that but without result
Log file was not created

sorry, I tried to do that but without result Log file was not created
andyboeh commented 5 days ago
Poster

Can you at least get a Bluetooth HCI dump using the original GShock app? Please capture the pairing process when you connect to the watch. More Information

We can compare the init squence and try to figure out what's wrong afterwards.

Can you at least get a Bluetooth HCI dump using the original GShock app? Please capture the pairing process when you connect to the watch. [More Information](https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/BT-Protocol-Reverse-Engineering) We can compare the init squence and try to figure out what's wrong afterwards.
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.