Search results for:

I' sorry guys, Gadgetbridge doesn't stop responding anymore. So the issue was somehow fixed (probably because I was resetting bangleJS and Gadgetbridge). I still have 0.73.0-banglejs installed. So I can't reproduce the issue which also means I can't tell you, if it is fixed in that update.

Sorry for that.
But of course: Thanks a lot for your efforts! I really like my bangle and the support from this forum!

Oh, sure, I'll wait then :)

Hi guys,

sorry for my late reply, email notification on updates to this thread were delivered to my spam folder so I didn't see them write away.

I'm not sure if I was able to follow you all along. I see the question about my Android device: it's a Google Pixel 5 with Android 13 (Kernel version 4.19.261-g768ca1b2052f-ab... as of March 16th).
I also activated 'Allow high MTU' and kept hitting "wait" when Android's message of ANR was displayed until logcat stopped more or less.

Then I cleared logcat, turned off my bandle js and stopped Gadgetbrige app from within the app (Burger menu bottom entry). Logcat was quiet. I started my BangleJS (saw a message in logcat appearing), then started Gadgetbridge and then connected. I copy pasted it to an new Gist: https://gist.github.com/graphcon/3abe2d6f83c2ffe95c21a7013f8ae15b
I feat, it doesn't start from when I started my bangle as there might be a limit of displayed messages. Not sure if I can expand this. Please tell me, if it isn't enough, I will then look into it.

I then kept hitting "wait" when ANR message appeared, but it doesn't seem to change anything.
There were no private messages/notifications while recording this logcat.

Also, I don't have any calendar apps on my bangle, does it always pull my events?
I use Circles Clock https://github.com/espruino/BangleApps/tree/master/apps/circlesclock

I did the same again (turn off bangle, stop gadgetbridge, ...). My bangle showed some messages at the bottom like "fifo full". It's still running and logcat shows a lot of "writing to characteristic" messages. But I received some personal messages so I can't provide you the logcat this time.

Hi forum,

this morning I received an update on Gadgetbridge. I connected it to my BangleJS2 (kickstarter, Firmware 2v17) and it crashed. I tried multiple times, but it always crashed. I restarted my bangle (long press button) but still same issue.

So I connected it to Android Studio and filtered its output to "gadg". I opened Gadgebridge and it wasn't connected. I waited a few seconds and connected it. After some time, Android said it crashed and I had the option to wait or clode Gadgetbridge. I hit wait. This message came up again, this time I hit close.

This is this logcat output:
https://gist.github.com/graphcon/ba077e16278e3c112fc0be1830eec96d

This is the ANR part:
ANR in com.espruino.gadgetbridge.banglejs
PID: 15614
Reason: executing service com.espruino.gadgetbridge.banglejs/nodomain.freeyourgadget.gadgetbridge.service.DeviceCommunicationService
ErrorId: 3d41d4dd-f870-4f0c-ae22-d83a58b21c0f
Frozen: false
Load: 1.91 / 1.38 / 1.67
----- Output from /proc/pressure/memory -----
some avg10=0.07 avg60=0.65 avg300=0.45 total=2037021908
full avg10=0.03 avg60=0.37 avg300=0.22 total=1061692332
----- End output from /proc/pressure/memory -----

CPU usage from 8047ms to 20103ms later (2023-05-19 09:21:59.563 to 2023-05-19 09:22:11.619):
39% 2995/com.google.android.bluetooth: 24% user + 14% kernel / faults: 5330 minor 40 major
27% 15614/com.espruino.gadgetbridge.banglejs: 18% user + 9.4% kernel / faults: 24066 minor
17% 1639/adbd: 8.2% user + 9.5% kernel / faults: 3589 minor
16% 1972/system_server: 11% user + 4.7% kernel / faults: 3701 minor
15% 16392/com.zhiliaoapp.musically: 10% user + 5.7% kernel / faults: 17904 minor 166 major
10% 592/logd: 3% user + 7.2% kernel / faults: 1013 minor 11 major
0.3% 1585/media.swcodec: 0.1% user + 0.1% kernel / faults: 25153 minor 209 major
7.7% 4405/com.google.android.as: 4.7% user + 3% kernel / faults: 21673 minor 1139 major
6.5% 1201/android.hardware.bluetooth@1.0-service-qti: 2.4% user + 4% kernel
6.2% 22823/logcat: 2% user + 4.2% kernel
5.5% 2759/cds_ol_rx_threa: 0% user + 5.5% kernel
3.8% 2787/com.android.systemui: 3% user + 0.8% kernel / faults: 7433 minor 132 major
3.1% 22717/kworker/u16:18-LPASS_CNTL: 0% user + 3.1% kernel
2.2% 32446/com.google.android.gms.persistent: 1.5% user + 0.6% kernel / faults: 3080 minor 120 major
2% 1264/media.hwcodec: 1.1% user + 0.9% kernel
1.9% 20562/kworker/u16:14-events_unbound: 0% user + 1.9% kernel
0.8% 20501/kworker/u16:2-events_unbound: 0% user + 0.8% kernel
1.4% 20563/kworker/u16:15-events_unbound: 0% user + 1.4% kernel
1.4% 22716/kworker/u16:17-WCNSS_DATA: 0% user + 1.4% kernel
0.9% 3149/com.android.phone: 0.7% user + 0.2% kernel / faults: 847 minor 397 major
0.1% 4502/com.android.nfc: 0% user + 0% kernel / faults: 1817 minor 548 major
0.9% 9230/com.google.android.apps.turbo: 0.9% user + 0% kernel / faults: 2925 minor 232 major
0% 1554/media.extractor: 0% user + 0% kernel / faults: 3505 minor 67 major
0.9% 3011/com.android.hbmsvmanager: 0.6% user + 0.2% kernel / faults: 1507 minor 445 major
0.8% 5376/com.whatsapp: 0.4% user + 0.3% kernel / faults: 567 minor 53 major
0.4% 31705/com.facebook.katana: 0.1% user + 0.2% kernel / faults: 405 minor 279 major
0.7% 1252/vendor.google.wifi_ext@1.0-service-vendor: 0.4% user + 0.3% kernel / faults: 181 minor 2 major
0% 1559/media.codec: 0% user + 0% kernel / faults: 1976 minor 52 major
0.4% 3041/.qtidataservices: 0.2% user + 0.1% kernel / faults: 1139 minor 353 major
0.4% 4568/com.google.android.connectivitythermalpowermanager: 0.2% user + 0.1% kernel / faults: 593 minor 571 major
0% 4582/com.qualcomm.qti.services.secureui:sui_service: 0% user + 0% kernel / faults: 769 minor 590 major
0.6% 1246/rlsservice: 0% user + 0.5% kernel
0.6% 2893/com.android.networkstack.process: 0.5% user + 0% kernel / faults: 741 minor 143 major
0% 3029/.dataservices: 0% user + 0% kernel / faults: 576 minor 529 major
0.3% 3045/com.google.android.grilservice: 0.2% user + 0% kernel / faults: 608 minor 377 major
0% 3069/org.codeaurora.ims: 0% user + 0% kernel / faults: 665 minor 486 major
0% 4533/com.android.ims.rcsservice: 0% user + 0% kernel / faults: 597 minor 499 major
0.6% 18089/kworker/u16:0-kverityd: 0% user + 0.6% kernel
0.5% 11/rcu_preempt: 0% user + 0.5% kernel
0.5% 130/kswapd0: 0% user + 0.5% kernel
0% 3044/com.qti.phone: 0% user + 0% kernel / faults: 579 minor 525 major
0.5% 3109/com.qualcomm.qti.devicestatisticsservice: 0.4% user + 0% kernel / faults: 568 minor 521 major
0% 3121/com.google.android.apps.cbrsnetworkmonitor: 0% user + 0% kernel / faults: 560 minor 506 major

Can you tell me how to fix this?

I use Gadgetbridge in German. For me, when I tap the gear at my BangleJS, there is no "allow 3rd party apps to change settings" or its translation. But I activated (translated by me): "Text as bitmap", "Allow internet access" and "Allow intents"
Using Gadgetbridge version 0.71.2a-banglejs

Thanks a lot guys! This seems to be a topic that I should investigate some time. But it involves Gadgetbridge and BangleJS and that makes it complex.
Thanks

Hi guys,

I searched this forum but didn't find what I was looking for:
Usually, when I do sports, I don't have my phone with me but my banglejs.
When I look at the statistics, especially the heart rate, there is a smooth line between when I left my phone and when I came back. It looks like heart rate only gets transferred to the phone, when it is connected (in the screenshot: not connected between 1740 and 1920).

Is there a way to save this "Offline" HRM data and collect it, when banglejs and phone connect? Is this planned?

I found the app Health Tracking, perhaps this data can be used?

I didn't know about this and my banglejs 2 also doesn't connect. I'm happy to test and support the integration.

Ok sorry. I didn't find any posts about Fonts, probably because I searched for "emojis". Thank you for your reply!

Is there a way to display those emojis as font? How can I support that?

Yeah... thanks.
I realized, the reason why it didn't charge wasn't the cable, it was the USB charger that wasn't connected to socket *facepalm

I see, there is a whole thread about corrosion and cleaning the connectors http://forum.espruino.com/conversations/370766/

By it, I understand the broken connector is "only" for data and not charging. So perhaps it's my cable.

Short notice: I updated my Pixel 5 to Android 13 yesterday and had no issues.

I had to clean those connections to charge my bangle once again. I think, I broke it. :( Is that connecter with hole the actually required? Or is just my cable broken? :(
The optical sensor is above those connectors in the photo

Works like a charm! 🥳
I had to adapt to the fact that my email notification on my laptop comes before if feel it on my arm but that's something I will learn ;)

Great, thanks!
I had a few problems with connecting to my bangle but restarting watch and my phone helped. Now I will test this new version 👍

Hi there,

perhaps this is a dumb question, but would it probably be possible to make my bangleJS2 vibrate when a message is actually displayed?

So, currently, my bangle vibrates, I look at it and see my watchface. The I see a "Loading..." popup and then I see a message. Of course, this all happens in like 1-3 seconds. But still, people around me find it inconvenient, when I look at my watch for "that long". Also for me, when I'm riding my bike, it's inconvenient, perhaps even dangerous.

Of course, the workaround is to know, that it might take a few seconds and only then look at the watch. But still, I wanted to ask if the watch could only vibrate when it knows the message is displayed.

Yours
Graphity

I would also be interested in how I can make my bangle.js 2 vibrate until I accept a call

Ok, so I have installed bangle.js version of Gadgetbridge (0.67.1b-banglejs) and bangleJ firmware version 2v14. I didn't receive call notifications.

I checked Gadgetbrige's permissions and it was missing phone and caller list permissions (not sure about the english names of permissions, it's "Telefon" and "Anrufliste" in German). I added them and now I see a notification when my phone is ringing 🎉🎉

Is there a way to make this notification vibrate until I accept the call?

This is really frustrating. Why does it take two months until Gadgetbridge makes a new release? Didn't "they" make one every month or every few weeks last year? Who may I offer my help to speed things up?

Soooo... did this somehow break the GB release process? I'm really waiting for this fix and GB's last release was more than a month ago

I have the same issue. Is this a gadgetbridge issue or bangle?

Hi all,

thank you all for your replies. I executed compact via Web IDE and had no problems with. It went through and I would say my BangleJS2 is faster now 🎉
I recorded a video showing it speeded up. Thanks!

I also made a video executing compact but since there was no problem, I didn't upload it. If you want it anyway (about 100MB) I can upload that one, too.

One feedback about executing compact from WebIDE though: I didn't know if it was stuck or if it even started. I didn't have visual feedback on my Bangle nor a message "Compacting started" or so. Would be great to have that.

Yours
Graphity

Hi all,

I know, BangleJS2 is work in progress and I use it every day. I definitely enjoy the working notifications and vibration.
But at one time it got a lot slower. I guess it was, when I upgraded firmware to 2v11, but I'm not sure.
I attached a video that shows entering menu and leaving it from/to circles clock. Of course, circles clock may also be the reason for the watch being slow.

I just wanted to ask, if:

1. the watch is slow now and I have to cope with it or
   
2. if that's just my watch and there's something I can do to speed it up again
   
   

So, does someone else have a slow BangleJS2?

Hi there,

I'm not sure if it's good to put this in this thread, but I was afraid to open a new one. If no one answers, I will open a new one :)

I just wanted to ask, if bangle can recognize "shaking". The Pebble once had an app that displayed messages and you were able to "shake them off" your wrist. I would like this behavior in the messages app and would try to implement it myself. But I'm new to bangle and anything with accelerometer, so I wanted to ask if recognizing "shaking" is already available.
I read about "gestures" but that seemed too sophisticated for what I have in mind.