I have a workaround which works in my case, the problems seems to be that the field used as filter holds:
		<field name="filter_creation_date_from"
				placeholder="XPLOG_FILTER_CREATION_DATE_CREATION_DATE_FROM"
				type="calendar"
				submit="true"
				format="Y-m-d H:i:s"
				label="XPLOG_JSEARCH_CREATION_DATE"
				class="element-filter input-small"
				ui="chosen"/>
This is a date field in a form:
		<field name="creation_date"
				alias="creation_date"
				label="XPLOG_FIELD_CREATION_DATE"
				filter="USER_UTC"
				type="calendar"
				format="%Y-%m-%d %H:%M:%S"
				todaybutton="true"
				weeknumbers="false"
				filltable="true"
				singleheader="false"
				minyear="-100"
				maxyear="+50"
				timeformat="24"/>
notice the format="Y-m-d H:i:s", this differs from the field used in a form: format="%Y-%m-%d %H:%M:%S"
So what I did was fork the xml (below is the whole xml file, put in fork/model/form/yourtable.xml) and put the following code in it, to override the filter field:
<?xml version="1.0" encoding="utf-8"?>
<form>
	<fieldset name="default.filters" addfieldpath="/administrator/components/com_xplog/fork/models/fields">
		<field name="filter_creation_date_from"
				placeholder="XPLOG_FILTER_CREATION_DATE_CREATION_DATE_FROM"
				type="calendar"
				submit="true"
				format="%Y-%m-%d %H:%M:%S"
				label="XPLOG_JSEARCH_CREATION_DATE"
				class="element-filter input-small"
				ui="chosen"/>
	</fieldset>
</form>
And that fixes the issue in my case, but I think the cause is the incorrect generating of the filter fields in the xml