Hi @lonerzzz,
I checked the described case, however, was unable to recreate the issue. I tested setting the minutes for the TimePicker via UI and code-behind and in both cases, the minutes were set correctly to zero. Check out the sample project here.

Your implementation provides one way to get it working, but someting about the implementation is currently brittle to the initialization. I have updated your code with a version 2. For me, the minutes are neither correct on startup nor when the button is pressed:

https://play.nativescript.org/?template=play-ng&id=3e8b92&v=2

I have subsequently determined that the time cannot be 12:00 AM. A zero is not allowed in the hour position either in certain cases:

https://play.nativescript.org/?template=play-ng&id=3e8b92&v=3

This seems to be a Nativescript core issue, as I just noticed it happens with Vue too.

If you run the example you'll see neither the minute nor the hour are set to 0. Every value other than 0 works. https://play.nativescript.org/?template=play-vue&id=Xz1XRK

Workaround: If you set it to new Number('0') it will work

@tsonevn Can you check if the Vue playground above works for you (the minute/hour should be showing 0 instead of the current minute/hour)?

If it is working for you it might be a device-specific problem. If it is not working it's a core issue and has nothing to do with nativescript-angular either, as this happens with all flavours.
For NS core there is already on open issue here: NativeScript/NativeScript#8941

This is still not working, the playground project provided here does not set the values to 0. In my case it is Nativescript Angular.

Closed via NativeScript/NativeScript#10460