[Other SmartWatches] perpe:
[MENTION=1938297]simple1i[/MENTION]

Who has reported problems with the newest firmware? Most people hasn't wrote on which firmware they are.

There are two hardware revisions of the inwatch-z, the older one without any special naming and the M2. The current firmware for frist one is v15, for the last one v4.

I own the M2 version, so I can only speak for this one.

I received it with firmware v3 like most other people. My v3 was not the original stock ROM, it arrived with a modified ROM. In this ROM multilanguage support was enabled, kinguser su binary and Play Store was installed and some chinese only app were uninstalled.

On the same day (or was it the day after?) my device received an OTA update, this update failed, because it wasn't stock. :-/

I flashed the original v3 for the M2, found on the chinese Inwatch-Z board and applied the OTA to v4. This means I haven't used the v3 for a long time. The v4 is very stable, I can't say anything bad about it. I'm quite happy with the watch. WiFi is too thirsty and eats too much battery. I don't use it regulary with a SIM, have did this only a few times. Most of the time I'm using it in companion mode with my phone or stand alone and offline. So far, it's very neat.

The v4 is only in chinese and english, but one can use MoreLocale 2 for multilanguage support. I'm from germany, having german as an addional language is fine, but restrict some buttons and views. English seems to be more compact, therefore useability on the small screen is better with it. I installed Xposed and also the App Settings modul, with it I can decide which app I would like to use in german and which ones in english.

The specs of the watch are good, nothing to say against it. I'm loving the transrefelctiv display. If you can live with Android 4.2 and if it is worth the money for you, then go and buy it. My watch was a gift and I like it, but I wouldn't pay 250$ or more for a device with 4.2. I don't think that it will get official updates to a newer Android version.It may get further updates, but only bugfixes.

Custom development has also restictions, the kernel source code isn't and won't be released. I wrote to Inwatch, but they ignored it. It has some MTK untypical hardware components, these are the LCD, the sensors mpu6500 and the memory. For the memory there are MTK drivers, but not for the MT6572, on this I'm working at the moment, without it there is no way to boot a custom kernel without kernel panic. MPU6500 is open source, but needs to be modified to fit for MTK CPU. For the lcd I may have found a driver, but can't test it, without working memory driver. Without kernel source and a newer kernel no newer Android version.

Recovery is also a little bit complicated. I have tried to compile TWRP, but it's always too big. Our recovery partiton is only 6MB, TWRP compiled within Omnirom is over 6.5MB big. I need a cut down, smaller kernel to build a smaller recovery -> kernel source is needed.

But for the recovery there is a solution, the Omate recovery is small enought (maybe because it's an older TWRP version), it can be repacked for the Inwatch-Z.

I was on vacation and haven't done much in that time.

Anyway, I can't say anything about the issues others have, especially if I don't know their hardware revision and firmware version. For my part, it's a good device with some little drawbacks, but nothing to worry.

Battery depands on your usage scenario. I can't recommend to use it in wifi mode, bluetooth tethering with a phone seems to be noticeable better, can last a few days. I can't say anything about cellular network, because haven't used it that way often. GPS is fine and if you are fast enough, I'm sure you can run a marathon with GPS on and display always on (but with backlight disabled). Anyhow I ran my marathon with display completly off and I had a little bit raiming battry for the rest of the day. ;)

With everything disabled and no usage it can run 6 days in standby, but who cares? No one buys a device to let it in standby mode ;)