(Not necessarily the Galaxy S10 specific thing, but I didn't find any closer board for this. Set it so as I own S10e)
Wnenever you try to setup a new alarm by voice using Google Assistant ("Ok google set the alarm to 8 am") and you're already having 50 existing alarms (some sort of restriction so you can't have more than 50):
- the voice respond from Assistant would be "Done"
- in the pseudo-chat window where your speach is recognized and written down the green V mark appears reflecting the the action was completed successfully
- the popup floating system message from "Clock" app temporary appears on a screen that action cannot be completed
- no alarm is created
I was lucky enough and checked the screen of my phone before going to sleep, so I catch this small floating system message saying that I've reach the limit of 50 alarms (it appears for just a couple of seconds) on time and didn't oversleep the important event.
I treat it as a "Clock" app bug or interface bug of both "Clock" and "Google Assistant". Supposingly "Clock" app responses back to "Google Assistant" with some positive return even if it couldn't do the requested action, which makes "Google Assistant" to respond back to user that the requested action was done.
I contacted Samsung support team on Twitter official but they suggested me to raise this topic here.
Solved! Go to Solution.
Found solution by myself - there's some other Samsung user faced the similar issue (https://us.community.samsung.com/t5/Galaxy-S10/Google-Voice-not-setting-alarm/td-p/1379730) and the fix was to update Google app.
- buy some product from company A
- and company A covers that product with warranty
... you shouldn't give a s..t that product is made out of thousands components produced by companies B to Z. If something is wrong with product you just go to company A. Which I did.
Don't be too quick to judge.
Voice assistant is made by Google indeed, but god knows if Samsung applied their hands to it. Then the app with alarms, called "Clock". It's made by Samsung. At least this is what system says (it was preinstalled from Galaxy Store and on app page it says made by Samsung).
From UI side I see it like this (see screenshot). Google Assistant displays green V mark after it talked to "Clock" and said out loud "Your alarm was set". To me it looks like the issue is in the Samsung "Clock" app: instead of notifying back Google Assistant that the request it came with (to set the new alarm) wasn't fulfilled properly (similar to exit code <> 0 speaking of linux analogy) it reports back that everything went fine (exit code 0).
But I can only guess what happens under the hood based on my own software development experience.
Google assistant works perfectly fine with other apps and it can certainly detect and analyze their negative repsonses, when the requested action cannot be done. So I'm not sure if this bug is Google Assistant bug alone. To me it might be either "Clock" app bug or some tricky interface bug in conversation between Google Assistant and "Clock"
Sure. That was only a guess that Samsung might be also responsible for fine tuning other Android components. None of us knows that for sure if they do that or not. But what I'm speaking here is not about "Assistant" solely. It's about how "Clock" app iterracts with it.