-
I am running the firmware 2v15
I tried the github page version just now, it connected directly, I had an update for the calendar app, so I applied it, disconnected, then opened the IDE and tried to connect and just got the message "Connection Failed."
Because of the update the Bangle was on the "hold button to reload" screen, so I did it and retried connection. Same "Connection Failed." Result.
Then tried to disable/enable the bluetooth on the computer (Win 10 pro, up to date, Intel Wireless-AC 9560 integrated chip for wifi/bt 5.1), and it finally connected.
I will try again and update this post the next time the connection to github page/app store fail.
-
Hello,
Most of the time just the short press is enough to bring back to work everything. I maybe have to do a full reboot one out of ten time if the bluetooth still does not respond after.
It shouldn't affect the stability of the Bangle at all
Even if it was displayed it does not affect anything into the Bangle, I can still open the settings or any applications without any issue and it disapear until the next time.
so it's a bit odd about your issues connecting...
I would love to help more, I admit my usage of the Bangle is more of a wall clock most of the time and I almost never switch from the clock itself, with that and the message I imagined both could be linked.
For the state of today:
I did not touch it since my post 3 days ago, no MEMORY_BUSY message, I tried going to the espruino.github.io page to connect to the Bangle (from Chrome, up to date). It connect, the bluetooth widget become blue, and in the end the application fail at getting the app list.I tried two more times to be sure then while writting this post I remembered that the main site for the application was directly on banglejs.com and tried connecting from there instead and that worked directly. Got back to the github page version and that worked well too. That make me a little more confused since both site are relatively the same if I recall?
But it seem that everything on the Bangle side seem to work well, maybe the fail at the app list collection was what made me think that.
-
Hello,
Not sure if this post best fit here or on the github, but I noticed something lately.
I am not really somebody that use the watch for other things that the time and light up the screen when needed. And when I am at home I do not even wear it so it often stay week without being used much. On that not the battery lifespan is awesome, with my usage I often reach a full month without having to charge it!
Back to the problem, my default screen is running with the Anton Clock and the widgets lock, bluetooth and battery level (vertical). All up to date and in attachement.
I noticed that after a few days wihout use, if I try to connect to the watch to see if there are update available, it generaly fail to connect until I reload the screen on the Banglejs. often, but not all the time before I do that reload there is displayed at the bottom on the screen "memory busy", I would join a photo if that was currently the case but no "luck" this time, maybe in a few days if an update is asked.
My guess is that one of the 3 widgets or the clock is slowly eating memory while running, or just something in the firmware? I am not sure since I do not have the level of knowledge needed to understand the code of all of them. But maybe talking about it may point one of you in the direction?
-
Thanks Serj! It is interesting to know there is already something, even if it is not for public and for everybody.
I never used matrix @user140377, but that seem interesting, even more with the bridge!
The use is different @johan_m_o, github is mostly for bug report, PR and features suggestion, this forum double theses uses and add static discussions, history and research while the instant part of one of the platform suggested is more volatile and for instant feedback.If github is more of a documentation/knowledge base and the forum equivalent to a mailing list, IRC and associate is something similar to a club room where you talk about your current/next project, try to get feedback, testers for something still in progress, search a fix for a small function or just talk about your day. I see it as something a lot more casual globally. At least for me they all have the same goal, but not completly the same use
-
-
-
Hello,
The application seem to work well, integrate with the App Loader, have a (simple) setting page that allow to active or deactivate it's effect. But I am not sure how to do the PR to submit it, since I added it as a submodule on my side, if I subit it in this state it only suggest to add it in the same way.
Should I delete everything and just add the files manually before submiting it or is that format ok too?
-
Hello,
It is not perfect but seem to work well for me, if you want you can give it a try:
https://yarg-mirror.github.io/BangleApps/?q=calibrationI will try to update it until it is good enough to be submited for the official app loader
-
Hi,
In the end I assume it work well since I fail a lot less my input while trying it.
I put everything here, for now it work by putting the boot file on the Bangle and running the app from RAM then reload. It is a little dirty and use too many write, but was quick to finish for trying it and not letting the conversation hang too long.Since everything seem ok (?), I am now in the process of cleaning it, making it work completly then setting everything for it to work in the app loader if that may interest some people before it eventually become obsolete.
Edit: now working and ready to be tested here
-
Hey :)
As an example, from what I gather from my saussage fingers with the Bangle, when I touch the screen I am on average 12 pixel to the left and 14 pixel lower than were I aim. My goal is to correct this offset via an application.
I assume Bangle.on('touch', ...) is the main system used by everything, I missed the wanted option already to many times in the default setting menu to admit a number, so I was hoping to correct that and fix it with a myapp.boot.js file. In a way that seem to work since I got my debug text on every screen, but I am not sure any of the change I do inside the function do anything, even while setting extreme offset the expected result happened.
I guess it would be better to completly finish the application first then ask for advice if it is still not working. I will try to finish everything this week if that help
-
Thank you for these explanations!
With that and some more reading of the references and tutorial I think I almost have a first application to try and submit for touchscreen calibration!After reading the tutorial "Bangle.js Software Modification" I am currently searching how to override the function defining the event Bangle.touch, the one that set the button and xy variable that we can read.
I think it is linked at least partially to this in the firmware:
https://github.com/espruino/Espruino/blob/master/libs/banglejs/jswrap_bangle.c#L347
and https://github.com/espruino/Espruino/blob/master/libs/banglejs/jswrap_bangle.c#L1589
So I am not sure if there is really any control possible before that.up until now from the tutorial I tried adding a app.boot.js to set my own listener, and I guess that work everywhere like I intend to, but I am not sure if it will affect the other app if by example I change the value of x or y in my function, a few test showed that it is not the case. If you have any ideas?
For now the application for gathering the calibration data itself seem to work fine, tomorrow I will probably look how to save them and make a some settings and an icon. But after that I will stuck for some time I guess.
-
Hello! And in advance sorry, my questions will probably have a lot of repeat with past posts that I missed.
First, thank you for the great project! This is the first smartwatch that I encountered after looking for an open source (and fully programmable!) one to replace the existing which ask and send everything about our life somewhere we did not ask for. Plus the way it is working seem really interesting, I hope I will be able to contribute even a little to it's content.
I discovered about the Banglejs at the start of the week, ordered it the day after and received it today with a lot of reading about how to use it in between. But it being really fresh for me, I did not find all the answers I looked for. Si here I am with my questions!
1. the Bangle init sequence
From what I have gathered after playing it a little, clearing everything on the storage leave only the firmware starting, and this one give a default init screen with some infos and the bluetooth activated to allow communication with the web apps store/ide.If the bootloader is installed, the Banglejs will run the content of .boot0 then .bootcde at every restart. And it is apparently just the files, event without the bootloader app installed everything work with just them. Not sure where is defined that the press of the button call for the launcher through, is it hard coded in the firmware? Or is it a behavior we can change? Same question for the other way, will pressing the button from the laucher always will look for a clock to run/relauch the .boot files
If that is the case, the minimum files required for a full working watch would be the 2 .boot files, a launch.app.js and at least a clock app if mandatory or if not a "main" app to replace it I guess.
Is the firmware open too? Can we look at it / participate in it's evolution?
I think that is already a good list, thank you in advance for your answers!
A late update after already 2 month and the new firmware update.
I never saw the MEMORY_BUSY message since then, and for the connection same thing, it may have happened only once or twice for 12 ish connections.
I assume that 2v15 fixed a lot of what was happening from the start, that it did not reappear in 2v16, and that the main culprit for the connection is only windows and the bluetooth drivers.
Thanks for all your work! ❤