Search results for:

Gordon, thank you for all the support, this really isn't "selbstverständlich". You're realizing a bold idea (JS on a watch, amazing) and then you're sharing it with likeminded folks (Kickstarter + Manufacturer + Logistics ++++, n-times-amazing), and then you're providing support.
Checking your email now, in case my Bangle is seriously broken I'll just order a new one.
~momo

Hi @Gordon, flattened the Battery & plugged it in - Nothing happened directly but after pressing & holding the button (I think that's normal) the watch booted. The scrolling issue unfortunately persists.

Executed your code, now waiting for the battery to flatten. The battery already was empty once since this behavior started, but just naturally, no flattening.

The first time I noticed this behavior was indeed after the bootloader + firmware update, it could be that it started shortly before and I didn't notice because I didn't access the menu, but it still is weird.

Hardware-wise, the Bangle was treated extremely well, no water contact, never even fell down.

UPDATE #2

Heres some logs from the above snippet, hope it gives more insight:

Simple Single Touch

drag { "x": 94, "y": 71, "b": 1, "dx": 0,
  "dy": 0 }
drag { "x": 94, "y": 71, "b": 0, "dx": 0,
  "dy": 0 }
touch { "x": 94, "y": 71, "type": 0 }

Drag Left to Right

drag { "x": 1, "y": 93, "b": 1, "dx": 0,
  "dy": 0 }
drag { "x": 1, "y": 191, "b": 1, "dx": 0,
  "dy": 98 }
drag { "x": 2, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 3, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 4, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 5, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 6, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 7, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 8, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 9, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 11, "y": 191, "b": 1, "dx": 2,
  "dy": 0 }
drag { "x": 12, "y": 191, "b": 1, "dx": 1,
  "dy": 0 }
drag { "x": 13, "y": 191, "b": 1, "dx": 1,

Drag Top to Bottom

drag { "x": 89, "y": 55, "b": 1, "dx": 0,
  "dy": 0 }
drag { "x": 89, "y": 191, "b": 1, "dx": 0,
  "dy": 136 }
touch { "x": 89, "y": 191, "type": 2 }
drag { "x": 89, "y": 191, "b": 0, "dx": 0,
  "dy": 0 }

UPDATE
I've tried the code that @myownself linked above and put it into RAM: Touches seem to work, left-to-right and right-to-left drag seems to work (although the y value doesn't change even if I alter the finger position) BUT dragging up & down does not work! When dragging up or down on the screen there's only one drag event registered followed by a touch?!

Super annoying issue, but I'm really curious how this can happen :D
~momo

Thanks for your answers! The issue is really insane.

@myownself yes, touch seems to work - just scrolling doesn't properly. In the main menu, e.g. I can't scroll up or down at all. If I open settings (which works as it's the first menu item and auto-selected) then there is some scrolling happening, but it's completely random (doesn't necessarily scroll when I drag my finger, randomly fires touch events while dragging the finger).

@Gordon I have the Bangle.js 2 from your Kickstarter campaign. Long-pressing the button (until the ====== bar is complete) does reboot the watch but doesn't fix the problem.

~momo

Dear Community,

Since the update to firmware 2v12 (using the firmware updater, including a bootloader update), my touchscreen doesn't work anymore. I can't e.g. scroll in the standard menu (which basically bricks the watch for me).
I tried rebooting, uninstalling all apps, reinstalling the 2v11 firmware, nothing helped. Any suggestions?

Thank you so much
~momo

And as I don't want to open another thread but also couldn't find good references: Are there some general tips on how to optimize the performance while programming for the Bangle.js 2? In my game I'm drawing a bunch of shapes - quite rapidly.

Hi all, I noticed that under heavy load, the touch event gets fired appropriately, however the xy coordinates are sometimes wrong (to be precise: they are a duplicate of the previous touch event).

Trying out this code

Bangle.on('touch', function(button, xy) {
  console.log("coords are", xy);
});

setInterval(() => {
  g.clear();
  for (let i = 0; i < 40; i ++) {
    g.fillRect(0,0,50,50);
  }
}, 50);

and then quickly touching the screen, alternating between the upper edge and lower edge, does register the correct amount of events, however a quick top, bottom, top tap results in this console log

coords are { "x": 103, "y": 9, "type": 0 }
coords are { "x": 117, "y": 8, "type": 0 }
coords are { "x": 117, "y": 8, "type": 0 }

It doesn't reproduce every single time, however it happens often. Any idea how this could be fixed?

Thank you
~momo

Btw did a little test myself with

Bangle.on('touch', (button, xy) => {
  console.log("coords are", xy);
});

and after spamming the touchscreen edges with my finger it looks like

x ∈ [1,191]
y ∈ [0,191]

Awesome input! @Poolitzer I didn't see your thread, otherwise I would've added it there. It's definitely interesting what @HilmarSt added as well, because 191-8 = 188-5 = 183 (!= 176 but at least the same for both coordinates)

I think this is best fixed in the underlying system, shall I create a github issue or so? For now I'll hardcode the 8..191 & 5..188 then!

Hi all,

I'm currently working on a smooth snake game for the lovely bangle watch, and with most games, precise controls are key! I'm using the onTouch event to change the Snake's direction, but it felt weird, and then after debugging I found out that the maximum x value I can receive in the onTouch event is not 176 (as you might expect due to the screen resolution) but 191.

Now I wonder what is the actual resolution of the touchscreen, and is there a function to fetch it dynamically (so I can develop the game device-agnostic)?

Thank you so much! Happy to join the community!
~momo