Search results for:

I actually had the same error when updating from 2v24.x to 2v25 (My DFU is 2v12) via apploader.
Reflashing again with the nrf toolbox also let me to the bank0 invalid error. Luckily a 2nd flashing with nrf toolbox was successful. So maybe just try again?

Wouldn't a seperate widget for stopwatch touch be more useful?

I can't even run the version 0.14 on my Bangle.js 1. I get low memory error. I say we just remove it from the supported list for this app.

Can you please try this: https://forum.espruino.com/comments/16645817/

If you have the SPL06 we might be able to reset the sensor without a full discharge:
https://forum.espruino.com/conversations/381706/#comment16770729

On Linux you can "simply" restart the bluetooth service. The discussion about that is here: https://github.com/espruino/BangleApps/issues/349

Did "GPS Auto Time" see a GPS fix? The "auto time" letters should turn green if so. So you need to run an app which enables GPS to receive a fix, e.g. speedo or gps recorder.

GPS auto time itself does not enable GPS because it would drain the battery really fast.

Well all acc-sensors I have seen so far do return the earth acceleration when not moving. Also they are usually not accurate enough to measure any other acceleration that is a lot smaller then 1G.

If you want to know the acceleration of your car I would try the GPS. You should be able to get enough satellites in your car.

These are usually the raw values. Try to subtract 9.81 from the acceleration vector.

I once needed a small widget to send the acceleration data over BLE as json. I have attached the files. You should be able to use it as a sample.

There's the 'GPS Time' app that makes it easy - or you could just hold BTN1+BTN3 to reboot and it'll pull it in then...

I will just code a widget then. It will update the Bangle time from GPS every time it has a valid fix.

I mean automatically, without any manual intervention. e.g. when using the gps recorder the clock does set the time without me having to press any additional buttons.

Btw is there a way to automatically set the time as soon as the watch gets a gps fix?

Looks like there is no two-way-binding between both. I guess the wrapping needs to be done in E.showMenu(). But you do know that you can easily set the time from gps or from the "About"-Tab in the app loader?

Wow, you are fast, thanks.

Hi,

when an application gets updated we can get the changes from its corresponding changelog.

But what about new apps? Is there a list somewhere?
If not, it probably can be automatically generated with git? e.g. Date of first commit on its folder, assuming that date of first commit and date of merge to master are not far apart. Probably a bash script like this:

for appfolder in apps/*/; do echo "$(git log --follow --format=%ai $appfolder) $appfolder" | tail -n 1 ; done | sort -r

I like the flexible setting, I commented it in the github report.

Thanks, I'm going to test it.

Yes it will avoid that problem, with the downside that sometimes my bt host does not pick up the change of the hid descriptor.
Let me check again if these were isolated incidents because I had the descriptor wrong or reproducible.

For me it is a bug, but I do not know the bt spec well enough to declare it as one.

-

Given that this is my issue I have seen it ;)

Setting only one device in the descriptor is not enough. All apps would need change to not include the first report id byte.

Update: I got it working by hacking my bluez to not add this extra zero, but this is only a workaround. I posted the question on the linux-bluetooth mailing list, but so far no one seems to be interested, so this issue will probably persist for quite a while.

The additional zero is inserted in bluez hog-lib.c in the "if (hog->has_report_id)"-block . Unfortunately "report->id" is zero at this time.

I have sent:

[2,0,0,0x52,0,0,0,0,0]

(basically the same as Linux displays, just without the leading zero)

At least now I understand why hidkbd.app.js sends 9 bytes instead of 8: Since there are now two collections instead of only one as in ble_hid­_keyboard.js the report id (2 for keyboard) needs to be prefixed. Unfortunately Linux still seem to think it is 0:

drivers/hid/hid-core.c: undefined report_id 0 received

What Linux receives is:

cat /sys/kernel/debug/hid/0005:0000:0000.0003/events
report (size 10) (numbered) = 00 02 00 00 52 00 00 00 00 00

..10 bytes

Found a parser:
https://eleccelerator.com/usbdescreqparser/

0x05, 0x01, // Usage Page (Generic Desktop Ctrls)
0x09, 0x06, // Usage (Keyboard)
0xA1, 0x01, // Collection (Application)
0x85, 0x02, // Report ID (2)
0x05, 0x07, // Usage Page (Kbrd/Keypad)
0x19, 0xE0, // Usage Minimum (0xE0)
0x29, 0xE7, // Usage Maximum (0xE7)
0x15, 0x00, // Logical Minimum (0)
0x25, 0x01, // Logical Maximum (1)
0x75, 0x01, // Report Size (1)
0x95, 0x08, // Report Count (8)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x95, 0x01, // Report Count (1)
0x75, 0x08, // Report Size (8)
0x81, 0x01, // Input (Const,Array,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x95, 0x05, // Report Count (5)
0x75, 0x01, // Report Size (1)
0x05, 0x08, // Usage Page (LEDs)
0x19, 0x01, // Usage Minimum (Num Lock)
0x29, 0x05, // Usage Maximum (Kana)
0x91, 0x02, // Output (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile)
0x95, 0x01, // Report Count (1)
0x75, 0x03, // Report Size (3)
0x91, 0x01, // Output (Const,Array,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile)
0x95, 0x06, // Report Count (6)
0x75, 0x08, // Report Size (8)
0x15, 0x00, // Logical Minimum (0)
0x25, 0x73, // Logical Maximum (115)
0x05, 0x07, // Usage Page (Kbrd/Keypad)
0x19, 0x00, // Usage Minimum (0x00)
0x29, 0x73, // Usage Maximum (0x73)
0x81, 0x00, // Input (Data,Array,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0x05, // Usage (0x05)
0x15, 0x00, // Logical Minimum (0)
0x26, 0xFF, 0x00, // Logical Maximum (255)
0x75, 0x08, // Report Size (8)
0x95, 0x02, // Report Count (2)
0xB1, 0x02, // Feature (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position,Non-volatile)
0xC0, // End Collection
0x05, 0x0C, // Usage Page (Consumer)
0x09, 0x01, // Usage (Consumer Control)
0xA1, 0x01, // Collection (Application)
0x85, 0x01, // Report ID (1)
0x15, 0x00, // Logical Minimum (0)
0x25, 0x01, // Logical Maximum (1)
0x75, 0x01, // Report Size (1)
0x95, 0x01, // Report Count (1)
0x09, 0xB5, // Usage (Scan Next Track)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0xB6, // Usage (Scan Previous Track)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0xB7, // Usage (Stop)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0xB8, // Usage (Eject)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0xCD, // Usage (Play/Pause)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0xE2, // Usage (Mute)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0xE9, // Usage (Volume Increment)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x09, 0xEA, // Usage (Volume Decrement)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0xC0, // End Collection
// 127 bytes

I don't think this is true now. HID just needs to be enabled when you pair it with your device

Well I'm new to this, but when exactly is boot0.js executed, when I pair with another device or a single time on start?

The code in boot0.js is basically:

var s = require('Storage').readJSON('setting.json',1)||{};
if (s.HID) { // Human interface device
    Bangle.HID = "(...)";
    NRF.setServices({}, {uart:true, hid:Bangle.HID});
}

so when HID is not enabled in settings while starting and boot0.js is only executed on start the NRF.setServices() never happens, correct?