Posts made by kl3m3n

@somasundaram-i Please try version 1.0.104, when it becomes available (you need to be in a beta tester program).

I would appreciate some feedback, when you test it.

Best regards,
Kl3m3n

@somasundaram-i Ok, thanks.

I have implemented local purchases caching (supported for Android 6 and above). The data is encrypted and persists through upgrades, but not re-installing the app.

I need to test this a bit more and then I will release the update.

Can you tell me if there is any notification (toast) message when GUI-O reverts back to DEMO version? Or just displays "Demo version" on the home screen?

Best regards,
Kl3m3n

@somasundaram-i Hi,

you don't need to clear the GUI-O app data, only Google Play Store data.
But still, this is a strange behavior.

Can you please tell me:

• Which Android version do you have?
• What is your Android device?
• Which Play Store version do you have?
• Are you using your device offline?
• GUI-O just reverts to DEMO once you start it up (randomly)?

Google Play Store should cache the purchase data - I think none of the users reported any errors regarding this. But now I am thinking about implementing offline (in-app) caching of purchase state.

Just waiting for your details, so that I can see if there is something else wrong with this.

Thanks.
Best regards,
Kl3m3n

@somasundaram-i
I am glad it works.

Did you perhaps leave the Beta testing recently as I've mentioned in one of the above posts?

I would still like to get to the bottom of this. Do you have another account on the same device?

Best regards,
Kl3m3n

@somasundaram-i
Do you by any chance know, which version were you using before the upgrade to 1.0.103?

@somasundaram-i Hi!

I am sorry for the inconvenience.

Can you please tell me, which GUI-O version do you have?

Can you try rebooting the device? If this doesn't work, can you clear the Google Play Store app cache? Navigate to Android Settings > Apps > Google Play Store > Clear data > Clear cache.

Also try re-installing the GUI-O app.

Can you try GUI-O on another device, using the same account?

Best regards,
Kl3m3n

@somasundaram-i Your were missing the position. When you create a widget, the position is mandatory. Please check the manual.

Best regards,
Kl3m3n

@somasundaram-i Hi,

I tried reproducing the issue on 1280x720 emulator and everything seems to work fine.

This image represents an image with non 1280x720 resolution, stretched to the entire available screen:

This image represents an image with 1280x720 resolution:

The GUI-O init command is:

|IM UID:im0 X:50 Y:50 W:100 H:100 IP:"<image>" SCM:1\r\n

Best regards,
Kl3m3n

@somasundaram-i

If you have the version 1.0.98 or below it should work ok.

Otherwise, you can wait foe version 1.0.103, which will be released in a day or two.

The version 1.0.98 is the latest production version. If your version is higher, you are enrolled as a beta tester. You can leave the beta testing via the Playstore GUI-O page (at the bottom). You then need to remove and reinstall the app. This way you will only get production versions when they are ready.

Best regards,
Kl3m3n

@somasundaram-i Hi,

can you please tell me, which app version you have?
I see this problem on the newer versions.

If you just rotate the screen with the "rotate" command, is GUI-O background (with the initialization button) extending over the entire screen or just a part of the screen?

Thanks.

Best regards,
Kl3m3n

@Sato Hi.

Try:

String text = "TXT:\"" + String(counter) + "\"\r\n";
String payload = String("@lb88 X:5 Y:47.5 SCI:0 VIS:1 FGC:#FF0000 ") + text;
mqttClient.publish(&In[0], payload.c_str());

Kl3m3n

@somasundaram-i Hi!

Why is your image placed at X:80 Y:-20?

Try placing it in at X:50 and Y:50.

I will try to simulate your conditions (1280x720 resolution) and test this.

I will get back to you, meanwhile please try placing the image at the center. Also you can try using other scale modes and see what happens.

Best regards,
Kl3m3n

@Sato Hi,

try setting the RTCR parameter to a low value, e.g. 0.1. This should give you updates with an interval of 10 seconds, which should be enough for you to disable the RTC. You can even go lower, up to 100 seconds.

Note that when creating the RTC, it will give you the time immediately and then with a specified interval.

Regards,
Kl3m3n

@Sato Hi!

Yes, the localisation can be a problem.
I will fix the RTC so it will return the day of the week as a number.

@Sato said in command that returns the date and time and the day of the week:

No, it not works, the date is wrong 2025/37/13, the time is correct

Can you please provide the initialization for RTCF for this?

Thanks.

Best regards,
Kl3m3n

@Sato Yes, you were missing the '|' character.

BR,
Kl3m3n

@Sato No problem!

@Sato Hi!

You can do this in the following way:

Set the format to:

"yyyy-MM-dd hh:mm:ss dddd"

The dddd part should give the days:
Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.

Create a lookup table to convert this into a number from 1 to 7.

P.S.: You can replace dddd with ddd, which will give you the short names for the days (e.g., Mon, Sun, ...).

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

@Sato I am glad to hear that!

Best regards,
Kl3m3n

Hi!

Ok, I understand!

@Sato said in On close with > clear some flags:

If Guio loses its internet connection, after a short time the Esp restarts and all the flags are cleared.

How does the ESP know to restart if GUI-O loses connection?