Lem 12 PRO: random reboot, boot loops, crashing apps, extreme heat

Looks like “normal” is ~40 degrees for this watch. If I close everything and leave the watch for some time I can see ~35 in minimum.

Here dmesg log: https://controlc.com/32ea41fb

50°C-60°C is nothing unusual for this type of processor, they are made to operate in this temperature range.
It sounds more like a possible storage corruption issue, could you provide a logcat?

1 Like

Using an app called SysLog.
Here logcat:

--------- beginning of main
11-17 19:13:37.744 E/m.tortel.syslo( 4793): Not starting debugger since process cannot load the jdwp agent.
11-17 19:13:38.002 I/SurfaceFactory( 4793): [static] sSurfaceFactory = com.mediatek.view.impl.SurfaceFactoryImpl@6ff55d4
11-17 19:13:38.062 E/GraphicExt( 4793): Can't load libboost_ext_fwk
11-17 19:13:38.062 E/GraphicExt( 4793): GraphicExtModuleLoader::CreateGraphicExtInstance false
11-17 19:13:38.064 I/GPUD    ( 4793): @gpudInitialize: successfully initialized with GL, dbg=0 mmdump_dbg=0 mmpath_dbg=0
11-17 19:13:38.103 W/Gralloc3( 4793): mapper 3.x is not supported
11-17 19:13:38.105 E/ion     ( 4793): ioctl c0044901 failed with code -1: Invalid argument
11-17 19:14:01.287 E/GraphicExt( 4793): GraphicExtModuleLoader::CreateGraphicExtInstance false

Really need you to enable USB debugging and run adb from your computer.
Collect logs by using command “adb logcat”
It generates a LOT of information and you are better running it at a time when you are fairly sure that you will get reboots

For some reason I was thinking about hard drive temperatures since mine show in my taskbar on my computer. I’m sure member none is correct about the temperature range as I’m not familiar with ranges on these types in watches.
Sounds like one of three possibilities and I’m leaning toward hardware failure but it could also be related to the NVRAM being incorrectly flashed to change the IMEI or you have added some app that is causing this problem. If it still has the problem after a factory reset but no apps have been added other than what it came with then it sounds like the first two are the most likely culprits. One will likely require returning your watch for a replacement.

@pablo11 and @none this shows crashes for vivaldi and spotify: https://controlc.com/6e8f69ba

1 Like

Slack crash: https://controlc.com/adda943d

Play Store download loop: https://controlc.com/292ecdca

Skype crash: https://controlc.com/23f62628

Thanks, we are working on it

1 Like

Apkpure: https://controlc.com/9d173b49

One cycle of boot loop from on to off to on: https://we.tl/t-GFgvm4gfS2

Yeah I get it.
We are working on it as quickly as possible.
Thanks

1 Like

I believe this shows a different crash in skype: https://controlc.com/2f9413c2

Different but all related.

1 Like

Do you think this is a hardware failure or something we can not recover? Then I should set up things for replacement during the refund period. Otherwise, If you believe that the fix is doable for this watch in the future, I will keep it and keep trying to provide you useful feedback.

The question is what makes this watch so special to have those troubles while no one except me complains about these? This makes me think about the hardware.

Thanks for the logfiles.
There are many errors that indicates a storage corruption problem, but i’m not sure if this is a hardware or firmware issue.
Just to make sure this is not a firmware issue, could you install and test this Z32-LEM12pro-V03?

Also please note down when you notice any issue, if it’s already on the first boot or later when you install something from the play store for example.

1 Like

Skype crash in V03 firmware: https://controlc.com/3c7f65b2

Spotify V03 crash: https://controlc.com/de5c7f6e