[LG Watch Urbane] .cliffe.:
Immediately following the OTA update to Android Wear 2.0, my LG Urbane started turning itself off (or crashing? dead screen needs long button press to boot) every few minutes. I tried factory resets, and even before pairing with a phone, this still happens. After drawing a dead-end with LG and seller support (the watch is 1.5 years old in the UK, but there is only a 1 year manufacturer warranty, and the seller's policy is 1 year warranty despite EU regs), I ended up unlocking the bootloader and flashing various ROMs (such as [ROM][KERNEL] Ext4All by Skin1980 [M1D64S][Update 10.12.2016]), and formatting cache and userdata. Despite this, I have the same problem in every case... I tried adb logcat, but there are no useful messages, even when the crash happens (often after a screen dim).

Unhelpful logcat:

01-01 01:36:59.989 569 1037 I PowerManagerService: Nap time (uid 1000)...
01-01 01:36:59.989 569 605 I PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
01-01 01:36:59.990 569 605 I DreamManagerService: Entering dreamland.
01-01 01:36:59.990 569 605 I PowerManagerService: Dozing...
01-01 01:36:59.990 569 594 I DreamController: Starting dream: name=ComponentInfo{com.google.android.wearable.ambient/com.google.android.wearable.ambient.AmbientDream}, isTest=false, canDoze=true, userId=0
01-01 01:36:59.999 569 569 E InputMethodManagerService: Ignoring updateSystemUiLocked due to an invalid token. uid:1000 token:null
01-01 01:36:59.999 569 569 E InputMethodManagerService: Ignoring updateSystemUiLocked due to an invalid token. uid:1000 token:null
01-01 01:37:00.051 999 999 V DreamService[AmbientDream]: onBind() intent = Intent { act=android.service.dreams.DreamService flg=0x800000 cmp=com.google.android.wearable.ambient/.AmbientDream }
01-01 01:37:00.063 999 999 I AmbientService: Ambient Created
01-01 01:37:00.063 999 999 V DreamService[AmbientDream]: Calling onDreamingStarted()
01-01 01:37:00.063 999 999 I AmbientService: Ambient Starting
01-01 01:37:00.065 999 999 D WristGestureCtrl: Stopping detectors: GesturesEnabled-true gestureDetector-true ungazeEnabled-true ungaze-true
01-01 01:37:00.065 999 999 D DefaultUngazeDetector: stopping
01-01 01:37:00.144 569 605 V KeyguardServiceDelegate: onScreenTurnedOff()
01-01 01:37:00.152 569 602 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
01-01 01:37:00.156 186 186 D SurfaceFlinger: Set power mode=0, type=0 flinger=0xb8cbbdf0
01-01 01:37:00.168 999 1011 I AmbientService: Current ambient activity gets paused: AmbientActivity[component=ComponentInfo{com.google.android.wearable.app/com.google.android.clockwork.home.HomeActivity}, callbacks=@178d6dc, running=false, ambient=true]
01-01 01:37:00.169 999 1011 W AmbientService: we need an ambient activity, but nothing to use
01-01 01:37:00.184 200 2052 D audio_hw_primary: disable_audio_route: reset and update mixer path: audio-record
01-01 01:37:00.192 200 2052 D audio_hw_primary: disable_snd_device: snd_device(63: voice-rec-mic)
01-01 01:37:00.610 186 225 I qdhwcomposer: handle_blank_event: dpy:0 panel power state: 0
01-01 01:37:00.610 569 714 D SurfaceControl: Excessive delay in setPowerMode(): 458ms
01-01 01:37:00.615 569 605 D PowerHAL: IDLE_MODE(touch) -> 1
01-01 01:37:00.626 569 698 E WifiStateMachine: Fail to set up pno, want false now false
01-01 01:37:00.626 200 383 D audio_hw_primary: adev_set_parameters: enter: screen_state=off

The fact that this started after the OTA update points to software issue, but rolling back to earlier versions does not resolve the issue.

Any one have any ideas? Any advice would be welcome.