@Tutrix any alternative? Thanks
-
Hey Flic community!
I just released TapShorts on the App Store — it's an iOS app purpose-built to connect your Flic 2 buttons to iOS Shortcuts.
Why I built this: I wanted a dead-simple, dedicated app for triggering iOS Shortcuts with my Flic 2. I wanted something laser-focused on the Shortcuts integration with a clean UI and curated templates.
What it does:
Connect your Flic 2 via Bluetooth Assign any iOS Shortcut to single press, double press, or long press 20+ pre-built shortcut templates across 5 categories (productivity, media, communication, smart home, accessibility) Background execution support Clean SwiftUI interfaceMy favorite use case — learning on the go:
I clip a Flic button to my jacket or bike handlebars while listening to a podcast or audiobook. When I hear a word or concept I don't understand, I single press the button to open AI voice mode, ask my question, learn something new — then double press to continue my podcast/audiobook. No fumbling with my phone, no stopping my run. It's like having a "curiosity button" that lets you learn in the moment without breaking your flow.Other use cases:
Desk: focus timer, music control, DND toggle Bedside: lights, alarm, good night routine Car: send ETA, play playlist, hands-free calling Kitchen: cooking timers, shopping list, recipe podcasts Accessibility: emergency SOS, call caregiver, medication loggingFree tier: 1 button, single-press shortcuts
Pro ($1.99/mo): double press + long press actionsWould love feedback from fellow Flic users. What shortcuts are you running with your buttons?
Download: https://apps.apple.com/si/app/tapshorts/id6758866017
-
Hi all,
I'm using AccelerometerStreamingConfig on a Flic Duo button (Android SDK) with outputDataRate = 1, which the javadoc says maps to 1.6Hz per the LIS2DW12 datasheet, table 29. But when I measure the actual data arriving over BLE, it consistently comes in at about double that rate — and the burst size is also about 4x bigger than the samplesPerBurst value I requested.
Measured examples:
samplesPerBurst = 8 requested → I receive bursts of 32 samples, about every 10.2s samplesPerBurst = 2 requested → I receive bursts of 8 samples, about every 2.55sBoth cases work out to ~3.14 samples/second delivered — exactly double 1.6Hz, regardless of the requested burst size.
I tried toggling lowNoise (true/false) and got identical results either way, so that doesn't seem to be the cause.
Is this expected behavior? Is there some other parameter (lowPowerMode, mode, bandwidthFilter?) that affects the actual delivery rate independently of outputDataRate, or is there a known firmware reason the button delivers roughly double the configured rate? Any insight would be appreciated.Thanks!
-
-