melta101
melta101
DIIDevHeads IoT Integration Server
Created by melta101 on 1/13/2025 in #🔔-devheads-feed
New GUI editor by LVGL
LVGL, the Light and Versatile Graphics Library, has introduced its first-ever UI editor with version 0.1 Using this editor, developers can seamlessly drag, drop, and customize widgets like squareline. Few of the major features are Figma Plugin and an online preview via github pages, NOTE: it's a closed source software source: https://www.youtube.com/watch?v=gCxBAK9EByA
9 replies
DIIDevHeads IoT Integration Server
Created by melta101 on 1/12/2025 in #🔔-devheads-feed
open-source hacking PCB
2 replies
DIIDevHeads IoT Integration Server
Created by melta101 on 8/22/2024 in #📦-middleware-and-os
Problem Statement: All bi-directional Audio passthrough from device to controller
I’m working on a project that requires bi-directional audio transfer between a mobile device (iOS or Android) and a controller running Ubuntu 20.04 or macOS. I’ve explored two potential solutions but encountered issues with both: 1. Using oFono on Linux to Act as an HFP-AG: I attempted to use oFono to make the controller function as a Hands-Free Profile Audio Gateway (HFP-AG). However, I’ve found this approach to be unstable. Most of the time, the system automatically selects the A2DP profile, and I’m unable to manually choose the HFP-AG profile. 2. Bluetooth Device Connected via USB (UAC-Class) with HFP/HSP Profile: In this approach, the Bluetooth device is connected to the controller via USB audio, with the HFP/HSP profile connected to the mobile device. The idea is to route the incoming audio stream through USB audio and vice versa. I managed to implement the USB audio part successfully, but I’m stuck at creating the SCO link for the Bluetooth profile. Although the HFP profile is identified, establishing the SCO link is where I’m blocked. I’m seeking insights or alternative solutions to achieve stable bi-directional audio transfer. I’m open to exploring other technologies or approaches as long as it solves the problem statement
6 replies