Gadgetbridge is Android only?
Gadgetbridge is Android only?
I'm experiencing an issue using my G-Shock GB-6900B after recent phone change from Acer E700 with Android 4.4.2 to Motorola G7 Power with Android 9.
There is a significant change in behavior and I think this is connected directly with Android version.
This is step by step scenario:
1. When successfully connected to the G-shock+ app lock the phone so that screen is black.
2. Then manually disconnect watch by disabling BT on the watch.
3. Then manually re-enable BT on the watch (don't touch or unlock the phone).
4. Watch is not able to connect back. It has 100% reproducibility for me.
I check this also with LG V30 and Samsung Galaxy J7 (both with Android 9).
I also checked with Xiaomi with Android One - exact same behavior.
The exact same scenario works perfectly fine with my old phone with Android 4.4.2.
Issue is even more serious as on Android 9 I get random disconnections and then watch is not able to connect back.
I already contacted both Motorola and Casio support but neither could help me.
Is anyone here in possession of Casio GB-6900B and can check mentioned scenario to confirm this is a general issue?
PS. I tested also with Gadgetbridge (official apk) and Bluewatcher and the issue reproduces also with those apps.
I will be grateful for any advices and ideas. It's really annoying that the watch is working flawlessly with old Android version and is broken with latest one...
Is the same for me with the GB6900B and the Motorola G6 Plus with Android 9. There is no solution for that. Unfortunately, Casio does not support the G-Shock + App anymore.
Phone pairing I think runs counter to what G-Shockaz like about da G. Da G should be self-contained. Personally I'd love to see a thermocompensated HAQ movement non Bluetooth, non MB6, non GPS square. Casio should be able to achieve a digital engine with +- 1 spy accuracy.
Last edited by tomchicago; September 6th, 2019 at 05:54.
https://github.com/Freeyourgadget/Ga...idge/pull/1416) implemented works for me. If you want to give it a try, send me a PM. It works for me a on a Xiaomi Poco F1.
In the first case, there is nothing you can do about it, since the Bluetooth stack on the phone sends a disconnect packet and the watch never reconnects back. This is the behaviour I'm seeing with a Motorola G5 Plus.
So I am looking to get a GB-X6900B after trying 2 smartwatches and being unhappy with both. Am I crazy for wanting one? SMS notifications are important to me but it seems that technology is marched on since they put this watch out. It seems that the 3rd party app may work but would like to know for sure before getting another disappointment. Any real world experience?
So far I wasn't able to run it with any app available on Android 9.
The watch (Casio GB-6900B) is awesome. Just what I needed and I was really happy with it while using it with old phone.
Right now however it's less then a half the watch it was due to BT disconnecting and not being able to reconnect.
This is an answer I got from Casio support on 09.09.2019:
"Thank you for your advice to the several web sites.
We don't have any data regarding the update of the App G-Shock +. In case the App will be updated, this will be announced in our website.
In the meantime we will forward your comments to our Headquarter in Tokyo through our Customer's Voice report."
There was no update since 2017 so I honestly doubt it will happen.
I had some hopes for Gadgetbridge to fix this but MR from andyboeh seem to be stuck for almost a year.
So I would say if you want the watch for it's notifications Casio is not the right choice. Unless you want to endlessly wait for the issue to be fixed like I do ;)
If they released a GW-M5610 with the updated module, I would think about it.
I think I'm waiting on either an updated version of the GW-5000 with the blue tooth module, or a version of the GMW-B5000 with a resin bezel.
TL;DR: I cannot go any further because it works on all of the phones I own and can test with. Unofficial builds of Gadgetbridge can be provided on request via PM.
It works for me on both of the phones I own (Sony Xperia Z1 Compact with Android 8.1 and Xiaomi Pocophone F1 with Android 9), but:
The real problem is the way Casio implemented link loss. If the phone sends "disconnect", the Casio watch disables Bluetooth (and it doesn't turn on automatically). If the link is just "broken", the Casio watch is visible every now and then for a few seconds (like every minute for roughly 7 seconds). Some phones send a disconnect signal if they think the link is broken and hence the Casio watch disables Bluetooth. This happened on my older Motorola G5 Plus, but I don't own the phone anymore.
Unfortunately, this behavior is buried deep in either the Bluetooth stack (the would be "fixable" on the Android level) or (this is my theory) in the Bluetooth firmware. This is only fixable by the vendor of the Bluetooth module (Broadcom, Qualcomm ...).
The second problem (which could be overcome, but is limited by available testing devices) is catching the watch during the short period it is visible. My phones run LineageOS and this is, again, the only platform I can test on. Other manufacturers might have implemented this differently and thus it won't reconnect even if the watch is visible.
Testing the behavior:
If the link is broken and the man plugging the connectors in appears, then the watch is discoverable and the problem is likely fixable on an app level (i.e. Gadgetbridge).
If the link is broken and the man plugging the connectors in does not appear, then it is unfixable on an app level and would need to be fixed in the Bluetooth stack / Bluetooth firmware.
Additionally, BLE support in Android is a big mess. There are so many different cases and vendor-specific details to take care of that it is virtually impossible to support all phones.
As already mentioned, I can provide unofficial builds of Gadgetbridge with some BLE fixes applied until PR1416 is merged, but I do so only via private messages.
Last edited by andyboeh; October 30th, 2019 at 10:59.
There are currently 1 users browsing this thread. (0 members and 1 guests)