Most recent activity
-
Is it possible to get the double touch signal working from the
typeon.("touch") ? I can't seem to get it working.I see on search others with same touch controller also have issues with the double touch.
0xBI want to find as many unique ways of input as possible so as to prevent using button, I don't like pressing the button that much.
So i need mb multi-touch (2 fingers at once?). long press and double touch.
-
I think it would be nice to have an app on the app loader which allows paste code into it, and it packages it into an app with meta etc, so like a quick app wizard.
In case you want to create an app that does incredibly little, but still want it to function as an 'app', so other apps see it as an app.
Does this already exist? couldn't find it. I would use such an app often.
So, it uploads the code you paste in there, on to your Bangle an an app, not as a file. Its incredibly simple but very useful in my opinion.
It could also have an option to upload it as a boot app too, for people who are not familiar with concept of .boot.js files loading in every app.
Guess i am super lazy, and don't enjoy writing much meta data, I prefer default options and want a fast auto-app wizard type thing.
-
https://github.com/espruino/Espruino/commit/5be8869ae36b7d9fe955e1b1071b9f8a58a038cf
v21.124
This is the culprit, but I have no idea why, it doesn't seem like it should be the culprit. -
I can confirm it my tests:
Testing latest firmware: 2v22 17:26:55 - synced. 19:48:30 5 seconds drift. 5 seconds over 2 hour 22 mins =================================== 2v21 19:53:50 - synced. 23:24 In sync 0.5 seconds -
Some notes from a.i response and web-search:
The DC internal resistance of a lithium-ion battery increases with the
increase of the depth of discharge (DOD). Within the discharge range
of 10% to 80%, the internal resistance remains relatively constant.
The internal resistance increases significantly at deeper discharge
depths.Cold temperature increases the internal resistance on all batteries
Chemical Processes: The chemical processes within the battery become less efficient as it discharges. This inefficiency leads to a more rapid decline in voltage as the battery approaches depletion.
Increased Internal Resistance: Batteries also have internal
resistance, which impedes the flow of current. This resistance
typically increases as the voltage falls. With higher resistance, more
energy is wasted as heat, further reducing the available power to your
device and accelerating the voltage drop.As the battery discharges, the movement of lithium ions within the cell decreases, leading to higher resistance.
I think as to whether the graph is normal or not, depends highly on what apps you have installed. And as to whether that is normal gadgetbridge type usage/behaviour. The curve on the left where you had it sitting does look pretty. But also it could be that usage means that the Display is turning on/off , so power draw would fluctuate a lot with that type of usage, or other peripherals like gps eg. Other obvious thing is ensuring wake on tap is not active, known to wake too often.
I think your graph on right just represents typical usage of a device. But you'd have to do more digging to be sure, there are some apps on the appstore that monitor power usage/current by seeing which peripherals are active.
And a best test scenario would be with as little as possible installed as Gordon mentioned, a clean base.
-
Programming/testing other Bluetooth devices using things like the 'Espruino Programmer' device
Can you elaborate what this is?
-
Reinstall bootloader from appstore, it uses .boot0 file.
Now make your app use
.boot1instead of.boot0The info file is only for making a normal app that is listed by the app loader app. You might need your app as a
clock, and also as a.boot1file. An app being a clock just means that it is loaded by the bootloader(.boot0 AND .bootcde) App, by default.Depending on how your device is reset/loaded, it won't always execute the
.bootcdewhich is the clockLoader. But sometime it will. That is why I suggest a.boot1and anormal app clockwhich are identical code. This could be a workaround for you. Ofc there can be other ways to solve this too.But this method might cause your code to load twice, in the normal case. So we have to think about it a bit more. Probably you would delete the file :
.bootcdeif you are relying on.boot1file as a clock loader instead.EDIT: I just realized there is a
.bootrstfile that overrides.bootcdebehaviour, AND runs upon reset too. So instead of deleting.bootcde, and instead of writing to.boot1, you could try writing to.bootrst. Then when you want to revert back to normal behaviour , delete the.bootrstfile. Now the Bootloader app's.boot0will load and then.bootrst(Your App) will load.Conslusion: Write your app to
.bootrst, the bootloader app(.boot0) should not try to load a clock now. Bear in mind as above has said, all this tinkering can be risky for bricking the device (If you lose access to DFU screen). If you do still have access to DFU screen, you should be fine.
Yes it is tapping fast in quick succession.
I am just stating that I also need multi touch, does bangle support that? is the controller capable of multi touch ?
But since double touch is simply 2 touch in quick succession and we have double tap implemented already, I feel like a in-built double touch based on similar concept could be nice for us.