Most recent activity
-
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! -
-
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/circlesclockI 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/ba077e16278e3c112fc0be1830eec96dThis 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 majorCan you tell me how to fix this?
-
-
-
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 was interested in smart watches since Pebble's debut. I supported BangleJS 1 but then moved to Nubia, which was a real bummer. Now I'm looking forward to enjoy BangleJS 2