Search results for:

Add me to the list: a few weeks ago, after a firmware upgrade my Bangle started to be fast by about 600ppm.
Unfortunately I also didn't pay close attention so I can exactly pinpoint the version this started with. I typically update to cutting edge builds every 3 to 4 weeks or so...

I have had a similar break on one of my Bangle2 watches. It happened when I accidentally dropped the watch onto tile floor from about 1m height while no strap was on the watch. That caused the tab to take the whole force of the impact and break off. Given the unlucky impact angle I would not blame the watch for the failure, pretty much any plastic object would have been damaged by this.
I was able to glue it back on with some super glue and built the area around it up with epoxy resin. This repair has lasted for about a year or so now.
Given its inexpensive nature I am surprised how well the Bangle has held up in over two years of almost daily use.

This is all very exciting. Years ago (for the Bangle 1) I wrote an STL viewer that does some of the heavy lifting in C (viewstl in the app store). Back then I did all the math library function (mostly trig functions) in JS and passed the results into C (simple arithmetic fp ops worked fine, albeit not using the fpu).
I have a half-finished Space Shuttle lander game that uses 3d graphics. My approach was to fill arrays with polygon screen coordinates in C and then call graphics routines in JS, but your approach of accessing the screen buffer directly from native code seems better performance wise, Felipe. I might adopt that approach, thanks for figuring all this out, very impressive!

Tested again (after updating to version 0.28 of the Recorder app), it seems to work fine now. Not sure what the issue was previously.
Thanks for the help.

Thanks. Yes, Log GPS was checked.
The GPS coordinate columns are just empty in the downloaded CSVs.
I will investigate further on my end, maybe I really just got very unlucky with GPS locks. I just wanted to make sure this isn't some regression in the nightly builds or newer versions of the Recorder app.

Hi,
For about the last 3 weeks I have been unable to get the 'Recorder' app (version 0.27) to record any GPS waypoints, on at least about 10 occasions - this has worked fine previously.
Initially I assumed that I had no GPS fix (this has happened in the past), but for the last several experiments I have made it a point to get a good GPS fix first (confirmed via the GPSInfo app) and walking around outside under open skies for ~20 minutes.
I am running a nightly build firmware version 2v18.69 (and a slightly earlier builds over the last week) and was wondering if someone else had experienced similar issues, possibly due to a code regression somewhere (maybe related to GPS sharing via GB, which I explicitly turned off for the experiments above)?
I will try to instrument the Recorder code and keep a console open on the phone to see if I can gain some more insight.
Thanks,
Marko

Well, the STL Viewer and Mandel apps also use floats, although I haven't officially ported either to Bangle 2 (just running hacked versions privately). Don't have the watch near me at the moment, I will see how things break - I usually pass floats in flat arrays in and out of compiled C via pointers in my code, so I am not sure where the passing in registers comes in here...
I also freely concede that a more reliable HR monitor is much higher on most people's priority list than a 3D viewer on a watch... ;-)

Take a look at the source for the View STL app (Bangle 1 only atm) - I use this technique quite a bit in it.

Fanoush probably has a point here, regarding the temporary array getting cleaned up in garbage collection.
Instead I have used a global auxiliary Uint32Array large enough to be in a flat memory area for passing in additional parameters. Not very elegant but works...

I think I had a similar problem back then. I believe that E.getAddressOf will only return the address to a flat memory area if the Array is above a certain size. Try padding your Uint32Array with a few 0s at the end.

Thanks, I appreciate that.

Sadly my (previously working) Bangle 2 seems to have succumbed to the same issue - I can no longer connect to it via Bluetooth. In particular, it is no longer discoverable on any other device (tried 3 smart phones, a laptop and a desktop, all of which see my other 2 Bangles without issues; made sure it is programmable in settings, also performed a factor reset);
does not show up as Dfutarg in DFU mode, either; nor does the pinch trick mentioned above seem to have any effect. Curiously, this is the newest of 3 Bangle 2s I own (the first 2 were Kickstarters). It did not get wet (beyond wearing it regularly).
Any advise?

Hi,
I wrote a small proof-of-concept app a while ago that uses the textinput and ble_uart modules to implement a minimalist chat app. It is quite hackish as it literally executes JS on a nearby Bangle to print a message (this also highlights one of the security issues with a Bangle with BLE enabled in general). The range is quite limited, 2m doesn't sound too far off...

function send_text(a) {
  NRF.requestDevice({filters:[{ namePrefix: 'Bangle.js' }], timeout:3000}).then(function(device) {
    return require("ble_uart").connect(device);
  }).then(
    function(uart) {
uart.write("if(typeof(_oldg)!='undefined')g=_oldg;g.clear();E.showMessage('"+a+"');g.flip();Bangle.buzz(300);_oldg=g;g=Graphics.createArrayBuffer(8,8,1);\n").then(()=>{uart.disconnect(); load(); }, (error)=>{E.showAlert(error).then(()=>{load()});});
    },
    function(error) {
      E.showAlert(error).then(()=>{load()});
    });
}
require("textinput").input().then((a)=>send_text(a));

Great. I will give it a try.

Yes, this was with an XL map.

It seems that the current GPS position marker is offset from the correct position in OpenStreetMap, too.

Possibly a file system corruption, specifically of .boot0 or .bootcde ?
Can you connect to the web ide to get console output?

Excellent!
What exactly makes this a long distance transmission? The call to setTxPower or the specifics of the setAdvertising invocation?
If it is the former, the Show Nearby app does not seem to contain a call to setTxPower...

Sacrificing a little memory to align to 4 bit sounds like a good compromise.

Hi Gordon,
Scratch that, I just realized that the 'scroll' option already does this, sorry about the unnecessary post.
Marko

Hi Gordon,
Any chance an option could be added to E.showScroller that allows for setting the first index visible on screen (e.g. the scroller can open already scrolled half-way down)?
Thanks,
Marko

Excellent. You move fast, Gordon, thanks!

Yes, a scroll argument would be helpful indeed.

Thanks, that makes sense. I was looking for a way to programatically scroll a menu that has more items than fit on one screen. I guess there is no way to do this at them moment then?

I seem to remember that the object returned by E.showMenu offered a 'move' function. This is corroborated by the API documentation, yet in the latest firmware it seems to have gone missing. Is this an oversight or was it removed on purpose?