-
my point was that asking questions about an Espruino device should not require a GitHub account (now managed by Microsoft and almost certainly not GDPR compliant...)
Fully agree.
Of course everyone who published an app on the Espruino GitHub repository already has a GitHub account. And that may also be the majority of the current forum users.
But people who bought e.g. a Bangle.js 2 for privacy reasons (it doesn't share data with third parties) may not want to create a GitHub account. And they may also avoid the current forum due to the use of Google Analytics and therefore not give feedback in this thread.
It would be great to have a forum where privacy-conscious people are welcome, too.
-
-
-
-
I had that idea, too :)
It is possible to do that with the Pattern Launcher.
I did that but it only worked until the Bangle hang (maybe an infinite loop). The Bluetooth connection didn't work anymore in that state, and without the button it was not possible to restart the watch and make it work again. So the battery discharged and now the Bangle is unusable. -
@Gordon Did you see my PMs?
Also another question: my Bangle turned off after the battery was discharged. I was hoping it would turn on again when connecting it to the charger but it didn't. Is this expected? -
Just for info - this is the configuration that is working for me (after disabling the internal bluetooth adapter as described in the link I posted above):
- x86_64 computer bought 2013
- up-to-date Debian Bullseye with kernel 5.10
- Chromium (I wouldn't use Chrome either)
- a cheap bluetooth adapter that is working out of the box with the Debian main repositories.
- x86_64 computer bought 2013
-
-
Hi,
similar story here. I ordered a bluetooth dongle because the internal bluetooth worked for my Bangle only when put close to my computer and it didn't work for the Puck at all.The dongle worked at first after I blocked the internal bluetooth with
rfkill
. But only until the next reboot of the computer. Since thenrfkill
didn't help anymore.Deactivating the internal bluetooth adapter is what finally worked for me. Since then bluetooth is working for both my Bangle and my Puck.
-
-
-
-
-
-
-
But it would probably help if the top-level < Back option was labelled < Exit instead.
Good idea, that would help a bit.
But it wouldn't solve the main problem I'm having with the menus (app launcher as well as settings): Often when I want to scroll up or down a random menu / app is opened instead. And when I want to actually tap to open a menu it scrolls instead. So often it goes like this:- Open the app launcher
- Try to scroll to the app / settings menu to open it
- After some scrolling a random app / menu item is opened
- Trying to go back - but instead of going one step back it goes back to the clock => Repeat from step 1.
- Alternatively tapping back goes indeed one step back but jumps to
the top of the menu. => Continue with step 3.
This can be quite frustrating.
But maybe this is just me being clumsy.
And maybe I'll just end up writing my own menus. The possibility of doing this is one of the reasons I like my Bangle so much (despite its limitations) :) - Open the app launcher
-
I like it. But for now I would prefer a menu without so many submenus for the following reasons:
The menu doesn't remember the currently selected item so when going to a submenu and then back it jumps to the top of the item list. This makes it difficult to find the right submenu. For example when looking for the Quiet Mode settings I would assume it's in the system settings but it is not there. Going back jumps to the top of the list so I would have to scroll down again to find it in the Notifications submenu.
When tapping the Back button too often it goes back to the app instead of the app launcher. From the app launcher it would be easy to open the settings again. But having to go from the app to the settings again because you accidentally hit the Back button too often can be annoying.
I wonder if these two issues can be resolved? IMO it would also improve usability quite a bit.
-
You were lucky then.
It is usually not recommended to use rice:
https://de.ifixit.com/Wiki/Don%27t_Put_Your_Device_in_Rice._Here%27s_Why... -
Sorry to read this. I have a Pebble that isn't waterproof anymore. After I noticed some water in it I turned it off and let it dry for a week or so. Then I turned it on and it is working well again since then.
I wish you good luck that it is the same with your Bangle and it starts working again after it is fully dried out. -
It took me some time to get the Bangle.js 2 to connect to my devices. Here is what I did (maybe these are a few more things to try if your watch cannot connect):
To connect the Bangle.js 2 to my Desktop computer (with Debian Bullseye) I followed the steps in the documentation (https://www.espruino.com/Web+Bluetooth+On+Linux) but the watch didn't show up as an option to connect to. In the end the solution was simple: Put the watch next to the computer (within a range of a few cm) and it shows up and everything works.
Next I tried Web Bluetooth with an Android device. It didn't work at first. The device only showed up after connecting the watch once via the Bluetooth system settings and then removing it again. Since then it works well.
-
People who avoid this forum will most probably not see this thread.
The people I know of think different about this. Microsoft collects a lot of data from a lot of users. E.g. with each Windows version they collect more data from their users. The question is: Do we want to support such a company by using their platforms? Not everyone wants this and burner accounts don't help in this case.
I think I understand the reasons for using GitHub discussions but I am nevertheless a bit sad about this move.