XPS 13 9360 Trackpad not working after boot or suspended state

Hello,

I'm running Ubuntu 16.04 with 4.4.0-57-generic and BIOS 1.2.3 (upgraded from 1.0.7). Since I got this laptop I've been experiencing different issues with the touchpad, from being randomly detected when booting up to my current state of being detected once the laptop temperature is warm enough (this is just my guess, but so far it's the best explanation I could think of)

When booting and not getting it working xinput just returns this:

Virtual core pointer id=2 [master pointer (3)]
   Virtual core XTEST pointer id=4 [slave pointer (2)]
   ELAN Touchscreen id=10 [slave pointer (2)]

On the other hand, when I get it working I get something like this:

Virtual core pointer id=2 [master pointer (3)]
   Virtual core XTEST pointer id=4 [slave pointer (2)]
   ELAN Touchscreen id=10 [slave pointer (2)]
   SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)]
   DLL075B:01 06CB:76AF Touchpad id=12 [slave pointer (2)]

Sometimes it shows SynPS/2, sometimes DLL075B and sometimes both.

Initially I would restart about 7-8 times until the touchpad was detected, but now that I found out this possible relationship with the temperature I just turn it on, wait for some minutes and then suspend-unsuspend or just restart and I've been successful in getting it to work. Needless to say, this is a bit annoying of a procedure to do every single time.

I tried almost everything I could think of. My current "patch" has been installing inputlib and modifying the default 90-libinput.conf file to have this:

Section "InputClass"
        Identifier "libinput touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
        Option "Tapping" "True"
        Option "DisableWhileTyping" "True"
EndSection

I initially disabled synaptics by modifying the entry in 51-synaptics-quirks.conf but later found that things would get worse (pointer wouldn't show no matter how many times i'd reboot) with this, so that file was left as is.

Any tip would be greatly appreciated. Could this be solved with a driver or BIOS update? If you need further data, logs, etc. please don't hesitate to let me know.