• Hi I'm benchmarking sensors and bluetooth throughputs on the BangleJS 2 right now, also working on a free multithreaded driver system that will unlock native android and IOS support on top of browsers in js, with the help of the Capacitor build library for mobile apps.

    Anyway I'm wondering why Bluetooth.write on the Bangle 2 device schedules in 128 byte chunks? Or at least that's what I am receiving on my end. I'm trying to simply pack 250 byte buffers which is more typical for eking out nRF52 performance. I tested my own nRF52 hardware in the same web streaming context and it was fine pumping the maximum packet size limit at 1M or 2M PHY into my browser system as browser and native mobile can do up to 512 MTU at either bluetooth 4 or 5 speeds (of course only 20 MTU on android web BLE but it's trash). Is there a simple function like setMTU in the espruino code that can change the packet size limiting on the Bluetooth.write call? I've had to dig pretty deep into the sources already for a number of other things but am not finding this one.

    I'll release a dummy app afterward to demonstrate the stack I have as it's pretty nice and minimal for cross platform dev. I'm doing a bunch of medical sensing related work so the Bangle 2 is a convenient placeholder/benchmark for a bunch of projects, keep up the good work.

About

Avatar for user158442 @user158442 started