-
Currently, you can only get the build APK if gordon invites you to the pre release "beta" of the app on the play store. As he stated above, he is
fighting with Google's review process at the moment
so if you wait a couple days, Google Play Store will be the way to go, even without the beta.
The latest latest cutting-edge build is also obtainable by cloning the repo from GitHub, opening it in Android Studio, and building it there for your device.
-
I am using Gotify-UP for push notifications.
Haha, another one who would like to have UnifiedPush integrated.
Or is there another fork / special version of Gadgetbridge for the bangle.js 2?
Gordon is developing a close fork, as he stated above. There wouldn't be fixes like call notifications in there though you wouldn't get in the normal app. The main reason behind the fork is to enable internet access.
-
-
-
Jup I know that, I flashed firmwares before the app store could do that ;P No DfuTarg shows up. Though the app has changed from nRF to https://play.google.com/store/apps/details?id=no.nordicsemi.android.dfu If the app still works for you guys, it might be that the bluetooth failed indeed.
-
it feels like we might as well have the current system of just letting Bangle.js itself do an HTTP request?
Yes, sure, that will be enough, especially for the beginning. If the notification generating process is not on a server, one can always use ntfy, with "just" http requests/websocket. What you can do with Bangle/the app though is to make sure it supports long polling/make that easy to access. It will be a bit more of a strain on the users data limit/phone battery ofc. I can always think about integrating the better version with Firebase, which should use less additional data/battery since your phone has already a connection to firebase.
-
-
if there were a way to integrate with an existing app (Tasker?) that does what you need already, I think that'd be preferable to just reimplementing everything
So I went down a rabbit hole. Apparently, the way push notification works is the same boring long polling implementation one would suspect. The idea is just that it would be very resource consuming if every apps implements their own long polling service, so one uses the google api. This means its all routed through their servers where just one connection needs to be made to. And then then android takes care of relying the new push from that api to the correct app.
If we dont want to (soley) use googles api, one can also apparently implement https://unifiedpush.org/developers/intro/, in tandem with a distributor like https://github.com/binwiederhier/ntfy#ntfysh--send-push-notifications-to-your-phone-or-desktop-via-putpost. Not sure if there is a big need of writing simpler over head code, looks to me like one guide would be enough. Once the API is implemented in the app of course.
-
Hi
Bluetooth icon blue or grey
Grey
The
-> Bluetooth
messageThats the one. Right under the icon and the firmware version and your name, you know, the startup screen.
how to reboot it.
Alright, lets clear this up. If I shut down with the Poweroff app, then press once on the button to start the watch, this is the behavior. If I follow the steps from https://www.espruino.com/Bangle.js2#resetting-without-loading-any-code correctly, you are right, it doesn't show up (I released the button too early sorry).
so I think it's most likely that one of your devices, somewhere, is automatically connecting to it
Easy to do, I turned off bluetooth at all devices which ever connected to it. Doing the normal shutdown/reboot, this still shows up. Doing the resetting without loading code, it again doesn't show up, but I can also not use the watch (obviously, since no code is loaded). So uhm, not sure if that helped?
-
-
-
Hello there,
I can not get my Bangle to connect to any devices. I tried the software reset without loading code, it shows the bluetooth launching and the mac address, but nothing else. I am hesitant to fully resetting the watch since I wanted to do a backup of the content there, which lead me trying to get a Bluetooth connection.
I have: Pixel 4a 5g, Android 13 as well as Pixel 2, Android (Lineage) 11, both with Gadgetbridge. And a Linux/Ubuntu PC with bluetooth dongle. The Pixel 4a and the PC both were able to connect to the watch X weeks prior, I only got out the Pixel 2 right now to see if it can connect to the watch.
Any specific step by steps I can follow to further debug this?
-
-
I think moving to Discussions would be fine. Having all the knowledge stored in this forum available there would be required though imo. If you actually spend time on this forum you could allocate to more development otherwise (not sure I get you here, you say "Right now the maintenance of this forum isn't a huge problem" as well as "The amount of time I waste dealing with company related admin is insane "?), I would do the move.
-
-
-
-
Might be related to my post, I can definitely confirm the 191 as max outmost coordinate.
http://forum.espruino.com/conversations/371220/#comment16336127
-
-
-
I can dive into Github Actions and set one up to run on each commit on the master branch to build an apk if you like that. If I remember correctly, as long as you have a Github account, you can see the actions tab, select the last action and download the apk then.