-
-
Thank you so much for all of this great information @Gordon. As well as your fantastic presence and assistance on the forums in general! This clarified a lot for me.
-
Here's the link: https://www.youtube.com/watch?v=BtEdM2w1VDM
It is from a year ago, so functionality has probably been updated since. Yes, I did see in the OSM settings you can choose from the direction of movement or compass. Just wanted some clarification from those who use the app. Thank you for the reply!
-
Thank you for the reply! It's never the exact same area and I've tried different size and had the 3bit checked or unchecked. I'll visit the ide and find out some more info in that env. I'll also attach the file as well. Thank you for the tips @user140377.
-
Thanks for the reply @Gordon! I did update to 2v20 when I was having issues connecting to gadgetbridge originally. It's had this same map behavior since I bought the device when I had to use a web browser to install applications before I could connect to gadgetbridge and upload from there. I've factory reset twice since then as well.
-
I have not been able to find proper documentation on how the Open Street Maps app on the Bangle interacts/functions with Android map apps like OSMand and Google Maps. Hoping some can clarify how they function together if at all.
Does OSMand~ on F-droid have the same gadgetbridge compatibility as OSMand+ on the playstore? I can't seem to find any clear answers. Curious because I obviously want directions to be able to pop-up on my bangle. I've seen conflicting info on the internet.
If I have a gadgetbridge compatible maps app like OSMand+ and set a destination, then open OSM on my bangle. Will a waypoint be created on OSM on my bangle? I don't see any other way to add a waypoint on the bangle app.
When I have a compatible map app will OSM on the bangle show the pop-up directions so that I only need to look at the bangle to know when to turn as well as my location?
Do I need the compass app? I saw a YouTuber who made a video on tracking bike routes with the OSM app on the Bangle.JS 2 say you need the compass app but i don't see that in the OSM docs.
Is there a way for OSM to automatically pull up once you set a destination on ur phone? Similar to the music controls app?
How do others use OSM on their bangle? Or is it at all usable for directions on ur wrist?
Settings recommendations for the best experience?
-
I have been unable to properly upload maps from Open Street Maps on the Bangle.JS 2. It allows me to upload the area I want, but when it open it on the bangle it only seems to have uploaded a slice of the area I selected. It always seems to be the same area/shape on the uploaded map as well? As if that's the maximum area it can show.
Troubleshooting:
- uninstall/reinstall OSM from the bangle multiple times
- reload/full reboot the bangle after it finishes uploading
- remove old map and try again multiple times with different sizes and settings
- let the bangle sit without opening OSM after it claims its finished uploading in case it's still uploading
Has anyone else experienced this issue?
- uninstall/reinstall OSM from the bangle multiple times
-
Success! I realized I'd entered the wrong MAC address when I downloaded GadgetBridge from F-droid and manually added the MAC in debug. I re-entered it, tried to connect and suddenly my Bangle.JS 2 popped up as an available device. It still kept the manually added device, but I just deleted it. So far so good!
RESOLUTION:
- Use the F-droid version of the Bangle.JS GadgetBridge.
- Make sure GadgetBridge is set to unrestricted battery access in GrapheneOS settings.
- In GadgetBridge go to debug and add the device manually.
Thank you to everyone who replied and assisted! I've never submitted an issue on any forum or community and had so much help with troubleshooting.
- Use the F-droid version of the Bangle.JS GadgetBridge.
-
I'm guessing that, like the Playstore app said. For some reason GadgetBridge does not see it as a valid bluetooth device. I did notice that my MAC looks different that others. The last for characters are all letters. They're also the same 4 characters that are used at my device identifier that are displayed in the top right corner of my bangle. I've noticed that all other MAC addresses have at least one number in the last 4 characters. In the Bangle.JS 2 startup guide it describes the unique identifier as "numbers". I don't know anything about how OS and Software determine's what a valid bluetooth MAC is, but it's just something I noticed. Maybe the way Gadgetbridge identifies valid bluetooth MAC addresses just doesn't align with my MAC. Just a guess, if somebody who worked on the Bangle fork of Gadgetbridge or knows anything about it could confirm or deny that guess.
-
-
-
unfortunately, gadgetbridge says it's not a valid MAC address
Edit: I deleted the Playstore Bangle.JS GadgetBridge and installed the F-droid version incase the OS is seeing it's connected to Google Play Services and isn't trusting it. When manually adding a debug device I don't get a "not valid bluetooth MAC address", but it still does not connect.
-
-
-
-
Thank you for the replies, I have tested a lot with the passkey setting. I just tested again a few times after reading your reply with the Bangle gadgetbridge app from the playstore. Still nothing. Previously I was getting some sort of background service error using the app from the Aurora store. I'm no longer getting that error, but still nothing.
Edit: I was mistaken I am actually still getting this error, here's a screeshot
-
Thank you for the replies, I've tried everything you described and the Bangle won't show up in the device discovery in the Bangle.js gadgetbride.
I've installed bangle gadgetbridge on my old galaxy s10e and it finds the device and pairs without issues. So it must be something in GrapheneOS. I don't know what it is, but if anyone has grapheneOS and has their Bangle connected please let me know if I need to enable some permission in the settings.
-
I commented this on a conversation marked completed so I wasn't sure if anyone would see it. I am reposting it.
Just got my Bangle.JS 2 a few days ago. I'm unable to pair the watch to my Pixel 7 with GrapheneOS.
OS and hardware:
GrapheneOS on Pixel 7
Ubuntu 23 on dell laptop
Asus USB-BT500 usb bluetooth adapterBehavior and troubleshooting:
Originally showed up as a device in GrapheneOS, and in Ubuntu on my laptop.
It would not allow me to pair and load apps in brave(as said in the docs), but it does allow me to pair and load apps in ungoogled-chromium without any issues as long as the proper chrome flags are enabled
After disconnecting from ubuntu I tried to pair with my pixel, originally it would show up and allow a pair, but not let me do anything with it, then it would show up as a pairable device, but not let me pair just does nothing when I tap on it. Now, sometimes it'll show up and sometimes it won't.
Gadgetbridge does not see it even when my bluetooth does
My work device, a macbook pro would not even see the device in bluetooth.
It pairs without issue on my old Galaxy S10e, but says it needs an app for the device
A lot of the time I have to quit settings, turn off bluetooth, open settings back up and turn it back on to see the device again in both Ubuntu and GrapheneOS
I have never had any issues with any bluetooth devices on Graphene, or Ubuntu with my usb bluetooth adapter.
I noticed at one point either on ubuntu or graphene when I selected my bangle the bluetooth symbol on the bangle would flash blue for a sec every time I selected the device to connect. I do not remember which device this was on and can't seem to reproduce it.
I've factory reset my bangle once.
I've tried using the gadgetbridge app from the playstore, aurora store, and F-droid
I've tried connecting on my profile with google play services enabled and my profile that has google play services not installedEdit: I am able to see it as a device consistently now by turning off Bluetooth and restarting the bangle, but still nothing happens when I select it for pairing in my Bluetooth settings.
Any help would be appreciated
-
Just got my Bangle.JS 2 yesterday. I'm having a similar issue, but I cannot even get my bangle to pair to my Pixel 7 with GrapheneOS. Reading this "solved" thread I'm not understanding what the resolution was.
OS and hardware:
- GrapheneOS on Pixel 7
- Ubuntu 23 on dell laptop
- Asus USB-BT500 usb bluetooth adapter
- Asus USB-BT500 usb bluetooth adapter
Behavior and troubleshooting:
- Originally showed up as a device in GrapheneOS, and in Ubuntu on my laptop.
- It would not allow me to pair and load apps in brave(as said in the docs), but it does allow me to pair and load apps in ungoogled-chromium without any issues as long as the proper chrome flags are enabled
- After disconnecting from ubuntu I tried to pair with my pixel, originally it would show up and allow a pair, but not let me do anything with it, then it would show up as a pairable device, but not let me pair just does nothing when I tap on it. Now, sometimes it'll show up and sometimes it won't.
- Gadgetbridge does not see it even when my bluetooth does
- My work device, a macbook pro would not even see the device in bluetooth.
- It pairs without issue on my old Galaxy S10e, but says it needs an app for the device
- A lot of the time I have to quit settings, turn off bluetooth, open settings back up and turn it back on to see the device again in both Ubuntu and GrapheneOS
- I have never had any issues with any bluetooth devices on Graphene, or Ubuntu with my usb bluetooth adapter.
- I noticed at one point either on ubuntu or graphene when I selected my bangle the bluetooth symbol on the bangle would flash blue for a sec every time I selected the device to connect. I do not remember which device this was on and can't seem to reproduce it.
- I've factory reset my bangle once.
- I've tried using the gadgetbridge app from the playstore, aurora store, and F-droid
- I've tried connecting on my profile with google play services enabled and my profile that has google play services not installed
Any help would be appreciated
- GrapheneOS on Pixel 7
Sorry for the late thanks, but it is in fact working at this point. Thanks for continuing to support this device @Gordon !