Announcing IoT push notifications
-
@kl3m3n said in Announcing IoT push notifications:
@sato
I have been running the push notification service for approx. 10h (Android 7, Samsung Galaxy S6), without any problems sending the notification every 30 seconds. Everything still works ok. So, I am convinced that the service works ok. I will try it on my Xiaomi device also (Android 11) for prolonged duration, but I also don't see any problems here...Regarding Whatsapp - OEMs (e.g., Samsung) probably keep some list of whitelisted applications that the OS is not allowed to kill, so there is definitely some difference here.
This is (in my opininon) one of the few drawbacks of Android systems (comapring to Apple devices) - due to open sourceness, the OEMs can do what they want, often breaking some core functionalities.
Regarding your second question - when creating a device, specify the optional user name. This is then sent in the usr: parameter. So:
Quick pair -> IoT devices -> add a new device -> specify device and user name.BR,
kl3m3nRunning Xiaomi Mi 9 Lite for 5h, push notification every 30 s, everything works ok.
BR,
kl3m3n -
Hi Kl3m3n,
Since 10 hours ago I have re-enabled Push Notifications every 5 minutes. I disabled all possible battery management. It now works with my Samsung Android 11. Sometimes after receiving a Push Notification the GUI-O freezes, can't open, shows Gui-o black screen. Then I go to settings - Apps - choose GUI-O and confirm the "Force to close". After that, it works again and I don't need to restart the phone.
Another question, how many notifications can it show. Currently, when you get a new Notification, always delete the last one.I know I ask a lot of questions, sorry
Best regards -
Hi kl3m3n,
My Sansung M22 updated the firmware to Android 12
Gui-O is still working, but Push notifications are not.
All the settings remained the same, that is, Android12 did not
changed anything, all the battery management options and others remain as they were before the update.
There is a warning about Gui-O where it says that the developer of the App should make corrections so that it works with this new version.
Attached I send the alert image.
-
@sato could you please send the output of adb logcat?
First enable USB debugging:
-
On the Android device, open the settings. Tap Developer Settings. The developer settings are hidden by default. If the developer settings are not included in the settings menu of the device:
-
Depending on whether the device is a phone or a pad, scroll down and tap About phone or About Pad.
-
Scroll down again and tap Build Number seven times.
-
In the Developer settings window, check USB-Debugging.
You need to install the SDK platform tools from:
https://developer.android.com/studio/releases/platform-tools.htmlThen open the terminal / shell and navigate to platform-tools directory and run:
adb logcatPlease send the terminal output to info.guio.app[at]gmail.com (replacing at with @).
I would really appreciate this.
BR,
kl3m3n -
-
-
@sato Thank you.
Regarding the notifications, I have debugged the error using Android 12 emulator. This seems to be working now.
There were also some other errors targeting Android 12 (regarding Bluetooth), due to some API changes, which I handled inappropriately.
I have also added the device name to the IoT message from the GUI-O app.
I need to test the functionality and then I will release a fix...
Thank you for your help.
BR,
kl3m3n -
-
@sato v1.0.6 available.
FYI: I also plan to add a notification log that stores multiple messages. I would rather not include Firebase. It will ruin the concept of IoT broker. You can setup your own IoT broker and the notifications functionality will "follow". No need for my interaction, configuration, etc. If I involve Firebase, this will not be the case...
BR,
kl3m3n -
@kl3m3n ,
Thanks for the effort, the Push Notif. already works on my Android 12. The device name works good.
Saving multiple messages, is also a great feature.So far, it's working on my Samsung Android 12. I've had to force close Gui-O a few times because it stopped opening. There was also a problem after update to 1.0.6.1, the Application UUID as changed.
I will update later on my other Samsung Android 10, to see if it will also change.Best Regards
-
@sato said in Announcing IoT push notifications:
@kl3m3n ,
Thanks for the effort, the Push Notif. already works on my Android 12. The device name works good.
Saving multiple messages, is also a great feature.So far, it's working on my Samsung Android 12. I've had to force close Gui-O a few times because it stopped opening. There was also a problem after update to 1.0.6.1, the Application UUID as changed.
I will update later on my other Samsung Android 10, to see if it will also change.Best Regards
Can you please explain the circumstances when the GUI-O stopped opening. Can you create a log of this situation? Also, please try GUI-O v1.0.7.
It is very strange that the applicationUUID changed. This would mean that other settings should change also. Are you certain, you did not uninstall the app?
BR,
kl3m3n -
Hello @kl3m3n,
I didn't uninstall the App, I just updated it through the Play Store, have now 1.0.7.1 and when I tested the Push notification didn't work, then I noticed that the Application UUID had changed.
Yesterday, a few times, when receiving a Push, I pressed the notification and Gui-O did not react, I tried after that, opening normally and also did not open, then I had to go to Settings-Applications and select Gui-O and then force close, after that, it worked again.
I am out of office, but at the end of the day, I will update the other Samsung Android 10, I didn't get a chance yesterday.
After the update I will give Feedback if there was Applic UUID changed.Regards
-
Have updated to 1.0.7.1 the Samsung Android 10 and it no changed the Application UUID
Good!Don't know why my cellphone Android 12 have changed the UUID on update
Next version update i will look if it happens againRegards