Device: Soundcore P30i / R50i NC (A3959)
App: OpenSCQ30 v2.12.0 GUI on Windows 11
The buds periodically send an inbound packet that has no registered handler. It's logged and ignored — no functional problem that I've noticed, but flagging it in case the command is worth mapping for this model.
WARN openscq30_lib::devices::soundcore::common::packet_manager: no handler found for inbound packet: Packet { command: Command([11, 2]), body: [1, 156, 17, 106, 60, 199, 64] }
WARN openscq30_lib::devices::soundcore::common::packet_manager: no handler found for inbound packet: Packet { command: Command([11, 2]), body: [0] }
WARN openscq30_lib::devices::soundcore::common::packet_manager: no handler found for inbound packet: Packet { command: Command([11, 2]), body: [1, 156, 17, 106, 60, 199, 64] }
WARN openscq30_lib::devices::soundcore::common::packet_manager: no handler found for inbound packet: Packet { command: Command([11, 2]), body: [0] }
4 occurrences over ~7 minutes while connected via the GUI; arrived spontaneously, not correlated with any action taken in the app. The alternating [0] / [1, ...] pattern made me wonder if it's a two-message pair or an on/off state push.
Happy to capture more packet dumps if useful.
Device: Soundcore P30i / R50i NC (A3959)
App: OpenSCQ30 v2.12.0 GUI on Windows 11
The buds periodically send an inbound packet that has no registered handler. It's logged and ignored — no functional problem that I've noticed, but flagging it in case the command is worth mapping for this model.
4 occurrences over ~7 minutes while connected via the GUI; arrived spontaneously, not correlated with any action taken in the app. The alternating
[0]/[1, ...]pattern made me wonder if it's a two-message pair or an on/off state push.Happy to capture more packet dumps if useful.