Tizen Developers

I am making a native watch application based on this guide, and got it set up and running (on a real Gear S3 Frontier running Tizen 4.0.0.4, not an emulator). I've placed some dlog_print calls to debug an issue I'm having and... none of my dlogs appear.

Currently, my code looks like this (everything else is exactly as the template makes it):

update_watch(appdata_s *ad, watch_time_h watch_time, int ambient)
{
    char watch_text[TEXT_BUF_SIZE];
	int hour24, minute, second;

	if (watch_time == NULL)
		return;

	watch_time_get_hour24(watch_time, &hour24);
	watch_time_get_minute(watch_time, &minute);
	watch_time_get_second(watch_time, &second);
	if (!ambient) {
		snprintf(watch_text, TEXT_BUF_SIZE, "<align=center>Hello Watch<br/>%02d:%02d:%02d</align>",
			hour24, minute, second);
	} else {
		snprintf(watch_text, TEXT_BUF_SIZE, "<align=center>Hello Watch<br/>%02d:%02d</align>",
			hour24, minute);
	}

	// debugging dlog... remove this later
	int ret = dlog_print(DLOG_FATAL, "USR_TAG", "test dlog boooooooooooooooooooooooooooooooooooooooo!!!");

	switch (ret) {
		case DLOG_ERROR_NONE:
		snprintf(watch_text, TEXT_BUF_SIZE, "<align=center>NO ERROR<br/><font_size=50>%02d:%02d</font_size></align>",
				hour24, minute);
		break;
		case DLOG_ERROR_NOT_PERMITTED:
			snprintf(watch_text, TEXT_BUF_SIZE, "<align=center>NOT PERMITTED<br/><font_size=50>%02d:%02d</font_size></align>",
					hour24, minute);
			break;
		case DLOG_ERROR_INVALID_PARAMETER:
			snprintf(watch_text, TEXT_BUF_SIZE, "<align=center>INVALID PARAMETER<br/><font_size=50>%02d:%02d</font_size></align>",
					hour24, minute);
			break;
		default:
			snprintf(watch_text, TEXT_BUF_SIZE, "<align=center>ERROR: %d<br/>%s<br/><font_size=50>%02d:%02d</font_size></align>",
					ret, get_error_message(ret), hour24, minute);
			break;
	}
	// end of debugging dlog

	elm_object_text_set(ad->label, watch_text);
}

I expect my log to be spammed with the USR_TAG log entries, it doesn't appear there at all. However, the return value isn't an error - it's a positive number (64 right now, was 19 when the message was shorter), indicating success.

The log is spammed full of other kinds of log entries, but mine aren't in there. (I've looked manually as well as using the filters)

Any idea what's going on?