Search results for:

@devsnd on github

Why @Gordon, thanks for your quick and thorough answer!

I'm afraid I didn't make myself clear. I already extensively use the feature you described.

What I can do now is this:
bangle -> app loader on phone -> web IDE remote -> Web IDE on laptop

What I'd like to do is:
bangle -> app loader on phone -> web IDE remote -> development app loader on laptop

So it would be great if the app loader could connect using the web IDE remote to the phone and therefore to the banglejs

It would be very convenient if I could connect the app loader to my bangle.js during development using a WebRTC connection. In this way I would never have to deconnect the watch from my phone and my phone remains the bridge for all development work for both web IDE and app loader.

I would also be willing to try to implement such a feature if someone could point me in the right direction.

Hey @ramzy23,

Your code is slow because of overdraw. Overdraw means that you paint the same pixel over and over again, no matter if it has already been painted before. Since you step through your circle at 0.1 degree increments, it gets really expensive to draw your circle even in the emulator. The real hardware watch would take a lot longer still.

I recommend looking at drawing algorithms using the implicit circle equation or the bresenham algorithm.

@bobrippling Made a change to the time variable in the public GitHub version of doztime a few months ago.

https://github.com/espruino/BangleApps/commit/1e49bb1e6338f91c78b8c2e819b8bf3a2fdddeda

Maybe you need to modify your secret version of the app to contain the same changes for it to work?

That's just a wild guess. Without any code to look at to reproduce the problem, it's going to be hard for the community to help you.

So if I understand correctly, you already have the weather setup correctly so that it shows up in the widget bar, but you want to see the weather as one of the circles in the circles watch face?

Did you try to tap on one of the circles and to swipe up/down/left/right to change the configuration? (This is how clockinfos are configurable in all watch faces that I know of)

Sometimes it's a bit hard to find the correct clockinfo since swiping left/right changes which clockinfo (e.g. weather/health etc) is used and swiping up/down changes which specific data point of the clockinfo should be used (e.g. temperature/humidity/etc)

I hope this is what you are looking for.

Also a big thank you from my side. The amount of mileage I get out of this little smartwatch is incredible. @Gordon and all the other contributors, you rock!

Maybe to add to that: even of you get bangle apps to work on another watch, you'll find out that many apps have been written for a specific watch (bangle 1 or 2 respectively) and that most apps just won't work nicely with another setup (e.g. rounded screens, more or less buttons, different screen resolution etc).

So getting the runtime to work is already a lot of work, but then getting the User-Level software to work is another herkulean effort.

But believe me, I also would love to have some more choice on the hardware side. Since you look for ruggedized, maybe my ruggedized cover[0] is something you'd like to have manufactured for you.

[0] https://forum.espruino.com/comments/17490753/

Hey @Beathoven, sorry for the long wait, here's the file. Tell me if this works for you (i used the free version of fusion 360 to make it), otherwise I can maybe export it in another format

Hey! Maybe this should be a bug report on github, but I have found that I could not connect to my Bangle.js2 using WebRTC in the WebIDE. I then saw in the logs that there was some error message about failing to connect to some UUID (the name of an old connection). I then modified the local storage in the browser running the WebIDE to contain the new UUID (shown on the phone). Then the connection worked again. I guess clearing the local storage alltogether would have worked too.

Anyway, I guess this is a bug of the WebIDE, that old saved webrtc bridge UUIDs in the local storage prevent the WebIDE from finding/connecting to new connections? Not entirely sure, but it surely made me scratch my head for a bit.

Car headlights are made of plastic, I would be very surprised if that would work.

Maybe a scratch remover for regular analog watches like poly watch would work?

@user159197 Here you go! I just had to make some parts of the model parameterizable and then it was easy to change the width of the wristband from 20mm to 22mm afterwards. This also includes the fix from my first try, with the slightly larger holes for the wristband mounting bar (using 1.25mm instead of 1mm holes), so I hope this works for you out of the box :)

@halemmerich, that looks really good! I'm starting to get pretty jealous of your 3 buttons and the usb-c port there. I hope airport security won't ask you to much about your watch next time you fly, though ;)

Hey @fanoush, do you have any plans to still work on the kospet magic 3? I was wondering if I should get one, so that I have something that I can tinker around with, without breaking my daily driver bangle.js... but if this is a dead end, I'd rather wait for another opportunity to get some cheap toys to play with

I tried it out and it actually feels faster than before, even without measuring. I guess we're just very close to jacob nielsons 100ms target (which is for web applications but remains a valid goal for UI development)[1]. That's also why a 10 or 20% improvement feels much more impactful than just linearly "10% faster"

@Gordon any chance you could provide "noflash" build with these optimizations? I'm wondering if running on the internal flash could do the last bit for responsiveness.

1: https://www.nngroup.com/articles/response-times-3-important-limits/

Ohh! You could also use setAdress on a banglejs right? Because switching between PC for development and android for daily use is always such a PITA. Maybe I'll find the time to create a small app for that 💡

Thanks for your continued work Gordon, it's much appreciated! I'll try it out once I get back from vacation.

Did I understand correctly that I need to reinstall all apps for them to be re-pretokenized?

Also another note on the internal-flash firmware: there used to be a problem with the compacting storage feature (compacting is like "defragmenting" or rather a "full vacuum" if you know what I mean).

Should you use the firmware, I recommend not installing your previous backup, but installing everything fresh so that there is as little lost space as possible. (Except if Gordon was able to track down this particular issue)

Hey, Just wanted to report back. Making the changes to the gadget bridge settings and also making sure that Gadget bridge is never killed to save battery did improve the Situation.

Thanks for the tips!

Thanks @fanoush, I had sticky tape on the middles ones, but the tape keeps disappearing.

So you're saying the the other pads are affected by the 3.3V pad and this is why the others are also disintegrating?

Maybe it's not clear on the photo, but the brownish part on the outer pads is actually the color of the PCB, meaning that the pads are almost gone. Could I add a tiny drop of solder there? Would that allow me to charge still?

Hey! I wear my bangle.js every day, also when doing sports etc... and I guess over time all the motion and bodily fluids and the charging cable are beginning to eat away the charging contacts. What could I do to restore them before the contacts are fully gone?

Thanks for the tips! I've activated Reconnect by BLE scan now, and I also made sure to exclude gadgetbridge from any energy-saving "feature" on my phone, I'll tell keep you posted if that improves the situation

Hey!

I've activated the "automatically reconnect" feature in gadgetbridge, but whenever the connection is severed, it never reconnects. For example if I move the watch out of range of the phone or if I turn off bluetooth intermittendly on the phone, the watch never reconnects automatically.

What can I do to improve this?

FYI: I'm using the nightly build of Bangle.js Gadgetbridge and also have a second device coupled, which I only use once per day (I use a colmi r02 for sleep tracking, but only wear it at night)

Interesting thought, maybe we could find out a ballpark number by just turning off BLE generally for a while throughout the day and compare that with power usage when BLE is activated. Your BLE "strobing" approach could then be at the midpoint of these two measurements, given that establishing a connection is not particularly expensive.

For example at night it might make sense to turn off BLE for longer periods of time to save on battery. The big question is if ble will use enough battery to be even noticeable when there is nothing being sent or received?

Gadget bridge has a function to redeliver messages after reconnecting, so on the software side this should work out; there are scenarios where turning BLE off would also not be good UX such as navigation, where the notification is important to be delivered fast... Also something to think about :)

Generally I like the idea to optimize battery life further, but first we need data to see if any effort could be worth it

I guess you didn't clone the submodules?

If so, you should be able to clone them still using the following commands:

git submodule init
git submodule update

See here for more info:
https://stackoverflow.com/questions/3796927/how-do-i-git-clone-a-repo-including-its-submodules

Oh yeah, that fixes it for me, thanks @halemmerich!