First of all thanks for the response @Irene2_ASUS
. Greatly appreciated - not all manufacturers provide responses.
Firmware version is that one (current latest).
Bluetooth itself is working fine. I have several BT devices that I use pretty much daily basis and they work fine:
When I use car the phone connects and disconnects to MPOW. Sometimes using other car and there it connects to car's BT system without issues.
Every now and then I'm using BT ear plugs (MPOW5) and they work quite OK except couple of strange things:
After pairing them the right hand plug was the one that performed the connection with phone so I was able to use only one for phone calls. Two for music.
Something happened and I had issues with connection thus had to re-pair them. After that it's the left plug that performs the connection thus I cannot use single plug anymore for phone calls. I can manually connect to right plug and then it works but on longer automatically. Annoying thing. Need to check that one day again.
The other thing is that sometimes (seldom) there are "cracks" in the sound. It's not fully correct term either but something like that. Connections stops for a while and then resumes with cracks in both occasions. Phone is at close proximity (at pocket). Didn't have anything like this with previous phone.
Occasionally I'm using Charge 2+ and no issues
Seldom connecting with OBD2 adapter and no issues
I'd say it's fair to say that BT itself works pretty well. Once I've had an issue where I had connection issues that got only fixed by rebooting phone.
I'm pretty sure that this sync issue is related to power saving or something similar. I've been using Dynamic mode but now changed to High performance to see if it has any impact. Started PolarFlow app again and noticed that last sync was sometime yesterday between afternoon and evening. Manually synced and BT connected fine, data was synced etc. Why the app had been stopped from running? This is major annoyance since app is needed to feed notifications to the wrist tracker. Not only annoyance but I cannot trust that notifications come through.
Made those tests regarding vibration and proximity. Both work. Fine? I cannot say but work. At least proximity sensor's usage has significant room for improvement to be able to use phone on ear and not cause accidental button presses.
I was probably not clear enough with the notification snoozing. When a notification comes it would be very nice to snooze it by 5min. Several people have requested this from MS for Outlook (calendar notifications) but MS has not responded anything. Alarm clock is one thing and it has it's own. If there would be generic, well functioning, snooze functionality for notifications it would be great. Android's default snooze is at the shortest 15min which is the default I am (as well as many others) are using as a default reminder (notification) before meeting starts. This can be modified via ADB but I'd prefer not do it that way. The best would be that Asus provides setting for this to adjust it according to user needs. The snooze implementation is also very tricky to use. Very easily (at least I am) one swipes the notification too much right and it vanishes away completely.
I really hope you can fix these issues quickly. I like the phone itself because of it's size, performance etc. but these issues are driving me to sell it and get something else - which will be physically bigger in size because of lack of alternatives in compact size.