Search results for:

my guess is that it will be some problem with one of the functions like cycling() etc.
I would suggest swapping out the functions to just print the string 'cycling' etc.
Also you might want to show the code you are using for the sub functions etc.

But also the screen draws power when it is redrawn, the larger the area redrawn the more power is required?

I'm watching with interest.

I think the concept is good. Could be a show_date Y/N value.

Not sure how it would work for things like Pastel, Daisy and other clocks that have a status bar that cycles round different displays of information.

With Daisy - my design principle was not to over complicate things.
Trying to draw rings like this usually ends up with something looking very aliased.
In order the get the crispness of the ring, it uses images for the different percentages 2,5,10,20..100.

There are improvement that could be made, but I'm currently a bit busy with work and other things.

I would not recommend anyone use the Active Pedometer at all now. It really ought be annexed. It was a very early attempt to fix the step counter, but the approach never worked. We fixed the step counter so that is reliable about 9 months ago now and it was well tested against AmazFit Bip and AmazFit GTS2. The link above shows 3 pedometers that work, they all read steps from the step event generated by the Firmware.

I used 'Lato Pedometer' mostly, here is a screenshot (top left).

Ooooo. Looks like the battery plot works in GadgetBridge now.

Try the new touch screen calibration app and see if that solves your issues with the buttons.

http://forum.espruino.com/conversations/­375618/#comment16518531

Ah ok. I thought you meant the original from 2011. I had 2, they lasted for years, but eventually became slow due to ram and bits of plastic dropped off. Still got about 8 years out of them.

Agree - looks like a chrome update.

I use a Chromebook all the time with Bangle - it does work.

It's the original Samsung Galaxy Chromebook

If it is that old it is possible that it is no longer taking OS updates and bug fixes.
There is a lifespan on how long Chromebook take updates for.
I'm using an ASUS C223N - about 2 years old.

This could be browser related. Crisp as anything on my Android phone, running Chrome. Fuzzy on my chromebook. Some images are still crisp. Eg pebble is fuzzy and pebbled is crisp. The difference is that the crisp image is much larger.

pebble image is 178x178 PNG file
pebbled image is 527x526 JPG file

the app icons on the loader all look a bit blurred.

Sure the app screenshot (ie the app mini screenshots on the right of the app cell) seem to have all gone fuzzy ?

See example marked up screenshot.
Sure these used to be sharper.

Well said.

However if you are moving about the heart rate bpm is not accurate.
https://github.com/espruino/BangleApps/i­ssues/1248

Bangle 1 and Bangle 2 use very different technologies for the screen. I cant remember the exact hardware terminology but I am sure others can explain it. In short Bangle 1 does flicker and Bangle 2 hardly ever. To reduce flicker on Bangle 1 only redraw the part of the screen that you need to. So if you had a clock that showed 3 square boxes with the digts for hour, minutes and seconds; then only update each when previousValue !== currentValue.

Or even better you could 'backup' the device to a zip file via the app loader

Will do. I didn't know there was a utility for this, but hve found it. Annoyingly I cant reproduce after removing a few apps.

Nice one !

Will I have to first update the operating system and then go through and upload each app I want to use?

Yes - but this is now a very simple, easy and reliable process.
You can do it all through the main App loader at:

https://banglejs.com/apps/

The firmware updater app is at:
https://banglejs.com/apps/?q=firmware

When you get your bangle it will be installed with the firmware it left the factory with (@Gordon's garage I image). This is 2vX and you can then update to 2v13 (the official stable release) or to 2v13.x which is one of the nightly builds (or known as cutting edge). I am currently running on 2v13.13. The nightly builds of the firmware are very stable and it is rare that a cutting edge build is broken and issues get fixed quickly so I'm never too worried about updating to the latest cutting edge build.

If I have to reset to factory at any time, do I have to then go through the apps
and re-install all of them again?

Yes a factory reset set of apps is stored somewhere in the firmware and when you do a factory reset the current storage is erased and the default apps rewritten to the storage.

You can mark apps as you favourites and it literally takes 1-2 minutes to reinstall your setup. The only thing you then have to do is change your settings to your preferred defaults. EG I always disable wake on twist and set the LCD brightness to 0.5 or less.

What is best practice. I'm looking forward into getting mine.

So I would suggest something like:

1. open you brand new Bangle
   
2. update the firmware
   
3. install some apps, play around with them, install some other apps and delete others.
   
4. mark some of the apps that are not the deafult apps as favourites.
   
5. do a factory reset through the IDE, type Bangle.factoryReset() when connect through the IDE in the left hand side of the IDE.
   
6. Now go back on the app loader, select Apps and click on the More option, you should see options to 'install favourites' or 'install deafults' etc.
   
   

Repeat.

Is the firmware open too? Can we look at it / participate in it's evolution?

Yes, it is built from. I have never built the whole thing, but it is possible.
It is written in C and supports the whole Espruino based product range.

https://github.com/hughbarney/Espruino

Not sure where is defined that the press of the button call for the launcher through

This is done by each App using the
https://banglejs.com/reference#l_Bangle_­setUI

It is possible to build a clock app that wont restart the launcher. If you set that clock as the default clock the only way out of that situation is to delete the app using the app launcher or the specific files through the IDE.

The behaviour of the launcher is controlled by the specific launcher app. You can choose from several different launchers.

As per screenshot.

Yes I do see that - but its only when you first open an existing note to edit it.

I think there is a case for not showing the cribsheet when you go to edit a note. If you are editing it is safe to assume you know you can tap the screen to get the cribsheet if you want it. Not sure if that is possible with the code. I guess the cribsheet would initially only be shown if length(notetext) == 0 OR you tap the screen ?

maybe make it draw it first in color and then when you tap make it draw in black and white?

That works.

@Sir_Indy - looking good. Shame about the centering issue. I've not used the layout at all yet.

I've updated to the latest version. I have noticed some behaviour with the hardware button, which may have been there in the previous version as well.

Set the timer running, then pause it with the blue button. Let the watch lock. Now press the hard button, the screen is unlocked, press the hard button again and the timer unpauses. But this isn't semetrical in that pressing the hardware button when running does not pause the count.

I think the action of the hard button should be to exit the app and return to the clock, with the timer left in whatever state it was set through play/pause button. Currently the only way to exit is to long press. Long press always feels a bit of last resort.

Love the app. Its one that will stay on my watch as its so easy to use.

I agree with @Alessandro. It is nice and self contained. Nice and easy to set a quick time up.
Also like the fact that you can exit the app and it keeps running in the background, open it up and the remaining count is shown counting down.

In terms of the UI design. The screen is a bit cluttered. EG I think the words 'timer' and 'time now' could be removed. The time now is actually very hard to read, it might be better in a large font and just centered under the main value. I think the start/stop touch button is a little narrow. My preferrence would be for the buton to be more like the one in Stopwatch Touch. Also I think on a black background a button in cyan looks nicer than dark blue. The dark blue would work better on the light theme rather than the cyan. Also you might consider using a play / pause icon on the button rather actual text.

out of interest what is an akku ?