Most recent activity
-
- 23 comments
- 3,027 views
-
Just to check, did you enable "Heart rate monitoring" in the Wearables section of Sleep as Android, too?
I think that's the only extra step I took beyond what was mentioned before. I don't know why that's off by default; I almost overlooked it. It does look like it took maybe 20-50 minutes before the first reading in Sleep as Android; maybe there's a delay.
-
Setting the "DIY" smartwatch option was the only thing I missed; I mistakenly assumed the "Bangle.js" choice would've worked. No need to disable automatic nighttime DND, no need to reset Sleep as Android to defaults (thankfully due to over 2 years of sleep data gathered via phone). Heart rate monitoring works, too.
For my first night, the actigraph data does look.. different than just having my phone next to my pillow (notably, a lot less deep sleep time), but I'll need to try this for longer to get a feel for which might be more accurate.
Thanks again!
-
In case anyone missed this, Sleep as Android support will be available soon, courtesy of AnotherStranger (thank you!)…
- https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/3785 has been merged (not yet in a stable release)
- https://github.com/espruino/BangleApps/pull/3422 is available on the Bangle.js app site
- https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/3785 has been merged (not yet in a stable release)
-
Someone has stepped up to work on Sleep as Android support in Gadgetbridge!
https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/3188
It looks like they are focusing on the Mi Band (based on the PR branch name), but this could potentially be used as the foundation for Bangle.js 2 support, too.
-
AntennaPod does support notification channels, but I don't see a way to hide a specific notification channels in Gadgetbridge.
However, I now see that there is a way to filter on specific words in the notification, which I had not noticed and likely can work around this issue. (Ideally, Gadgetbridge itself would be fixed, but if that's too complicated I'd understand.)
-
- 9 comments
- 963 views
-
Noted! I didn't realize the watch could update Gadgetbridge's settings, that's rather handy. (I initially avoided this as I didn't want to have two separate collections of notification ignoring settings.)
And sure thing! I understand this is a high risk area to mess with, and I'll keep an eye out for any other apps that trigger this issue.
(I am surprised that the LineageOS system updater does not cause this given it frequently posts notification updates on download/installation progress. A quick glance at the source code doesn't find any
setLocalOnly()calls.) -
Sure thing! Your musings make sense. I haven't looked into Gadgetbridge's handling yet, but if I notice anything in potential future code-spelunkings, I'll let you know.
And, nah, I don't need AntennaPod notifications. It'd merely be nice to have, and I figured this might impact other folks too so I should report an issue. I had considered toggling the app off in Gadgetbridge then changing it to handle media notifications before the app blocklist; I'm glad to know the watch option handles similarly.
Overall, this is awesome! The Alarm ETA widget on Bangle.js is a nice way to see how much time I have left to sleep if I wake up early, too.
However, after some more nights to test, the Bangle.js actigraph data feels like it's less meaningful vs. my phone next to my pillow. So far, Sleep as Android has not detected deep sleep, always triggering the smart wake up alarm at the earliest start time.
My phone next to my pillow (2024-7-2):
Wearing Bangle.js 2 (2024-7-9):
I wonder if there's a difference in how Bangle.js 2 reports accelerometer data..?
At a glance, the
accelsendercode looks correct, as does the Gadgetbridge handling. If I understand correctly, Bangle.js 2 finds the maximum acceleration over a 1000 ms period (o.put("interval", 1000);), sends that to Gadgetbridge, which then finds the maximum acceleration over a 9999 ms period, sending it to Sleep as Android once it hits batch size.