@etravnik Hi!

Can you please tell me which connection mode you are using (Bluetooth, IoT...)? Can you provide a minimal example which reproduces the problem?

Best regards,
Kl3m3n

@Fehr

Try : Print "@Current_Chart CL:1"

Bernard

@enniom Hi!

#1 - I agree with your suggestion. In the next release, the numbers will be displayed outside the actual chart area, live you've suggested.

#2 - This is strange - in your video I see GUI-O is receiving invalid characters (ABV%).
After you quit the application with the command, you then open GUI-O from "recent apps" and what do you do next? Your video does not show this. Do you connect to the device manually or you use auto-connection feature to re-connect automatically?

Can you try quitting only when all Bluetooth transmissions are complete and Bluetooth is disconnected?

Best regards,
Kl3m3n

@AndrejK Thanks for sharing! This looks great! 👏

@Proto Hi!

Yes, you need a license for each Android device that uses a different Google account from the one used to purchase the license.

Licensing is based on the app, not on development. Specifically, the app does not track (and cannot enforce) which device is designated as the "development" device.

Best regards,
Kl3m3n

@RudiP Hi!

Thanks for reporting the issue. To help diagnose the problem, could you please provide a minimal example where this happens? Specifically, I’d like to see the widget initialization code that triggers the problem.

Also, what is the make and model of your Android device? If it’s an older or lower-end device, the issue might be related to limited system resources like RAM or GPU memory. Initializing complex widgets with a lot of data can sometimes cause delays or rendering issues on such devices.

Lastly, does the app crash or freeze, or is the screen just black but still responsive to touches?

Best regards,
Kl3m3n