Search results for:

I am aware of 'Widget Editor' app and it works perfectly but probably many users are not aware of the existence of the app.

I think for new users the best is to have the functionality available by default.

I noticed that some times an app (a clock/watch) executed by the emulator is not the same that I uploaded to storage and tested on a previous time but an older one.

Curiously when i upload a new file to storage during all the session it really seems properly overwritten. For example I can leave the app and execute again from launcher or storage and always it is executing the updated code.

Have you experience it? Ideas besides clearing the cache/storage?

What about allowing the widget configuration from the apploader page?

As solutions I can imagine:

• Modifying through regexp following line of code before uploading
  WIDGETS["wdclkbttm"]={area:"br",...

• Implementing on default bangle system code/function from Widget Editor

unfortunately i feel that it is a a too complicated task for me :|

Anyway I suppose this middle button function is not that important for bangle.js2 users and bangle.sj1 users can test on the real device.

I haven't used the banglejs2, but for more than a year I am using the bangle.js1 as a daily driver.

Yes, before that, it was just a gadget/toy for experiments, but at the moment I found the watch very stable, batt last many days, good apps are continuously improving, and even some of them are useful for my life.

Hardware can't be improved but bjs2 fw/software maybe requires more polish.

I had other smartwatches before from garmin or smartthings with better look and plastics but I prefer the bangle ecosystem.

Bangle.js 1 display can't be read back from - getPixel always returns 0 in Bangle 1

Why? is it related to BJS1 lower specs?
BTW getpixel works fine on BJS2

You should be able to just press right in the middle of the screen to activate both?

@Gordon Yes, in a real bangle.js touching on the middle area1+area2 is associated to the simulated area 3.
However, in using the simulator the cursor must be touching in a specific point of the screen.
For better simulation of a action with a finger, i think the pointer should have a diameter of ¿2 o3 cms?

no errors in console. What fW do U have ? Maybe it is related with the use of Certain widgets, but I tested before and after removing most of them

When it happened I had fw 2v16, even I though that issue could be related to any the version of app but it was't.

Anyway, since yesterday i don't have the issue, as after clicking on " install default apps" the watch start working and i reinstalled apps again without problems.

th app is on apploader https://github.com/espruino/BangleApps/t­ree/master/apps/miclock2
BTW i hace to update the 1st post becasue i added little more info and also the format was broken

You should be able to just press right in the middle of the screen to activate both?
The cursor of a computer press on small and specific area ,
For example the app "testuserinput"should shows "touch3" when you press in the middle but it can't be done from the emulator

Maybe the cursor for emulator should simulate a finger ;)

I am not very experienced using the emulator, so maybe it is just a matter of lack of experience.

At the moment I am facing different behaviour between both espruino interpreters,

1. The "mixedclock2" app works fine on emulator but fails on a bangle.js1.
   See the issue drawing graphs

2. The "toucher" launcher, can't open some apps "mixedclock2 or setting"
   ....on bangle.js1 can be open with BTN2 or middle area touch
   ....on Emulator BTN2 doesn't open the app (probably something fail without an error output), and the touch can't tested (see next point)

.....Curiously both apps work fine on emulator when they are executed from the storage but also same apps can be open properly using the default "launch" launcher.

1. touch area 3 (lef+right)
   I can't figure how to press in both areas "simultaneously" from the emulator screen.
   i.e toucher launcher use this area to open apps
   (I suppose the touch action can be emulated from the IDE commandline)
   
   
   
   
   
   

Recently i was updating apps from GB Apploader, though i was receiving a messages "...JSON malformed.." i keep updating and some apps were updated but one never completed the process.

Later i began seeing debug messages on watch screen, and graphs overwritten with a wrong position

Now the watch is broken, after checking storage, bootloader and settings are not installed.

It assume that during the update process they were uninstalled but installation step failed. (as i was doing from the phone I didn't realize)

If i try to install "bootloader" i get following message

FW addr 0x0001a168 fail
Status 0
Uncaught Error: File already written with different data
at line 1 col 1426
...xlPDAuMimrO2cucw=="),0,4945);;p(24);B­luetooth.println("OK")..
FW addr 0x0001a168 fail
Status 0
Uncaught Error: File already written with different data
at line 1 col 881
...tvu1lplpud0soA==")),0,18826);;p(5);Bl­uetooth.println("OK")...

but installing other apps also fail

FW addr 0x0001a168 fail
Status 0
Uncaught Error: File already written with different data
at line 1 col 1424
...xib29zdHw0NSxpbg=="),0,2620);;p(16);B­luetooth.println("OK")...

Any alternative to earease.all and reinstall basic/default apps?
I see that "install default apps" implies a removal for all apps. (i don't mind but i was not expecting it)

The duplicated thread with better pics (smaller size) has been the removed one.

Anyway it was a false alarm, but that's true that i expected the same size and horizontal/vertical centered independently of length of the string.

On the other hand, what is the expect app to display in bangle.js for a debug notification?
Currently it shows "Bangle.js gadgetbridge" or the fake app selected from the debug dropdown list, a even i would propose a 3rd option "Debug: %app%" so "Debug: Whatsapp"

But also it is not a real life problem, so it is just a curiosity :D

Yes, this is a known issue. Mozilla refuse to implement Web Bluetooth
in their browser.

Sad but true

*Status:
RESOLVED WONTFIX*

https://bugzilla.mozilla.org/show_bug.cg­i?id=674737

Mozilla's Position:.... Like WebUSB there is significant uncertainty regarding how well prepared devices are to receive requests from arbitrary sites. The generic nature of the API means that this risk is difficult to manage. The Web Bluetooth CG has opted to only rely on user consent, which we believe is not sufficient protection. This proposal also uses a blocklist, which will require constant and active maintenance so that vulnerable devices aren't exploited. This model is unsustainable and presents a significant risk to users and their devices.

I don't know if there is a reason to display notification from GB Debug in a different way than those from real apps.
At the moment when notifications come from Debug:

• font size is always the same (big) independently of the number of lines
  
• header is shown different
  
• text can go out of the content area and overlay widget areas
  
  

See the photos with multi line messages
photo1. a test from Debug
photo2. a real notification (it is not recent, so maybe the text distribution has been improved)

I deliberately avoided feedback in the app loader

I agree with a separating feedback from the installing function, but maybe having a link to the github filtered result.

By "feedback" i was referring more to personal opinions or functional analysis, focused more in end-users than in issues/technical feedback as bugs or feature demands focused on developers.

In fact i just realized that my example (reviews page of firefox addon) lacks of a version number field (btw google play reviews lacks of it too), and imo it is must to have info.

Through fields and filters I am sure that Github can manage this review info :)

so maybe after that one is gone completely?

I think keeping support for old models like bangle.js1 is not bad at all for the project neither for users of new models. As it forces to apply better coding practises, help detecting the lack of abstraction between the code and the hardware.
It would be amazing having the official espruino and most apps working in some of the watches that jeffmer made to work with its espruino fork.

Yes, the different display sizes are a challenge, but I am sure there is a solution for it :)

Using Favorite is good way to avoid risks or a trial&error installing process with its associated time consuming.

I missed the "favorite" filter when I was new with bangle.js. Now I find interesting the "New" filter and give a chance to new apps.

To be even more perfect I just miss a page for feedback (considering privacy), so users can give opinion and even tips. (inspiration from Firefox addons page)

I see that this OWM weather is not defined as compatible with bangle.js 1. Isn't it? or it just has not been tested

Not the answer to you question but
I managed to have weather working on the "advanced casio clock" with the API key of openweathermap.org and syncing from its own web app.

The syncing method is not ideal, but it can be re-coded ;)

Thanks to this question I've realized that espruino has a fork of "gadgetbridge" with additional functions. ;)

Thanks, great support:)
The problem is solved, yesterday i was able to install from the android phone all the apps that failed before.
And Messages is working fine.

Regarding a potential misbehave from Messages, it can be very likely as the ide output when opening the app is:

Uncaught Error: Unknown UI mode
 at line 43 col 38
    throw new Error("Unknown UI mode");
                                     ^
in function called from line 1 col 682 in messages.app.js
...s[s]);}this.selectedButton=s;});uiSet­=true;}}if(options.back&&!uiSet...
                                      ^
at line 1 col 682 in messages.app.js
...s[s]);}this.selectedButton=s;});uiSet­=true;}}if(options.back&&!uiSet...
                                      ^
in function "Layout" called from line 28 col 2472 in messages.app.js
...pe:"h",fillx:1,c:buttons}]});g.clearR­ect(Bangle.appRect);lay...
                              ^
in function "showMessage" called from line 29 col 531 in messages.app.js
...owMessage(newMessages[0].id);if(optio­ns.openMusic&&MESSAGES.so...
                                ^
in function "checkMessages" called from line 34 col 368 in messages.app.js
...ewMusic&&settings.openMusic});

There was a bug also. At the end of the run, I stopped the run app and... The recorder app was still on "on", stopping the run app didn't trigger "off" in the recorder. I had to go into settings/recorder to actually stop the recorder.

I suffered recently this bug in bangle.js1, not only a record continua after stop but also after kill/exit Run it was recoding.

I think the goals defined for "run" are out of the capacity of bangle.js1 specs.
Is it possible to develop "Run" in modular way, so some functions can be optional; it can be good also for experimental features.

I mean setting the dashboard interface is cool but most people will no customize, and low specs hw like bangle.js1 prefers the lack of gold plating :D

for the version 3, i would like:

• physical buttons; 3 or 4 ,
  
• good readability under the sun
  
• seamless compatibility with software for previous models. (note)
  
  

(note) compatible software must be designed before the model exist, so i think espruino (i know that there are already some functions that allow that) and devs should use more generic functions that can be easily "translated" to different hw interfaces by any model maybe the software