I think it is related to the Bluetooth driver and/or marvel bluetooth adapter itself. I mostly use the new Surface Pro connected to power but I still get random issues (NOT shut downs) with the Microsoft Arc Touch mouse (not the new one, the previous version)
where the centre scroll just stops working. I will see events listed saying the Bluetooth driver has malfunctioned and has been unloaded. I have also been using the SP4 Signature Edition keyboard with the new Pro and that seemed to cause it issues but they
seem to have settled down.
Random sleep in tablet mode only happened in the first few days and I put that down to all the app and os updates that were going on in the background. Since then it has happened only two or three times but maybe it isn't happening because (a) I am using
plugged in and (b) I rarely select 'tablet mode' even when I use it as a tablet without keyboard and mouse. And I never let it adjust brightness automatically.
However, in the Notification panel my Brightness button has stopped functioning - anyone else have this? Just started today. Clicking that button does nothing instead of cycling through the brightness levels. Will have to reboot and see if that fixes that
issue.
I like the new SP enough I think I'm keeping it (have another week to decide) but that is largely because I have the MS Complete and will have two years warranty.
That said it may be something else software update related as well as my Surface Pro 4 (i5, 8GB, 256GB) which has performed absolutely flawlessly for a year has just started to act weirdly in tablet mode. When I wake it after it has been hibernating over
night the screen is getting interference type lines in the top inch of the screen. The screen will then adjust the lighting way up, way down, and finally cycle into acceptable visual range. The screen then ends up normal and beautiful like it always was. The
only Bluetooth device I am using with it is the SP4 pen. I moved the keyboard and arc touch to the new one until I can get the updated versions down here in Australia.
I wonder if the second problem has to do with the Night Light function which dims the screen... it seems to have started around the time I activated that. Could be coincidence.