yashsingh1/xdaforums huggingface dataset:
[Other SmartWatches] simple1i:
Sam,

1.Will it work in Europe?

2. Will it be available in Europe?

3. Will it have a companion app?

4. What's the IP rating?

5. If the watch fails (not the users fault) for someone in Europe, who pays to return the watch to US? What's the after sales policy for non-US consumers?

6. Can you make spare parts available for consumer to buy, such as chargers?

7. How many years will the watch be supported for?

8. What is the SARS (Specific Absorption Rate) rating? Here's Samsung SARS info: http://www.samsung.com/sar/sarMain?site_cd=uk&prd_mdl_name=GT-I9100

Thanks.
[Other SmartWatches] inWatchUSA:
What about it broke? If I can fix it, I am happy to try. One of my first production samples that I ended up using hard for 6 months had the wake/power button break off the PCB. I have some decent tools and like to work on small stuff so I was able to resolder it. Any chance it is fixable?

---------- Post added at 10:39 PM ---------- Previous post was at 10:15 PM ----------

1.Will it work in Europe? YES

2. Will it be available in Europe? YES

3. Will it have a companion app? YES

4. What's the IP rating?

After Lokifish Marz' dunk test showed eventual hardware malfunction, it was clear that we needed to improve. We talked to our nanocoating factory and worked with them to up the level of protection provided by our superhydrophobic treatment. This was accomplished and will be applied to the samples that I will be receiving any day now.

After what I saw with the initial dunk test, I will withhold a claim of a specific IP rating until I can show it happening. I am not interested in inflated numbers and I KNOW none of you are. We will push this new coating to its limit and beyond. I hope it performs better than we initially did. In a way, we will find out its IP rating together, as I will post the test here when completed.

5. If the watch fails (not the users fault) for someone in Europe, who pays to return the watch to US? What's the after sales policy for non-US consumers?

There will be a standard 1 year warranty that protects against parts and workmanship failures within that time. we are still writing the policy but it will be quite similar to other devices of this kind. All logistics and shipping/replacement will be handled by the local sales outlets and the local distributer, the unit will not need to be sent to the US. I wish I could say more here but much of this is currently being ironed out. We are preparing to be available in the USA, South America, Europe and Russia in early 2015. How quickly we can do all that is unknown so I dont want to over promise and under deliver but that is the plan.

6. Can you make spare parts available for consumer to buy, such as chargers?

Yes, the fact that there are devices in the wild that use a proprietary charge clip that is not available for individual purchase is unacceptable. There will be charger clips, BLE earpieces and other swag available for purchase at time of US launch. In the meantime, PM me here if you are in need of a charge clip. I don't have any on hand but I will request a few be sent with the samples.

7. How many years will the watch be supported for?

What do you mean supported? We are not planning an end of life for Z, we want to keep supporting it as long as people want to keep using it.

8. What is the SARS (Specific Absorption Rate) rating? Here's Samsung SARS info: http://www.samsung.com/sar/sarMain?site_cd=uk&prd_mdl_name=GT-I9100

This is a great question and one that I want to have the answer ready for the next time I get asked. I will have a meeting with the team and make finding this out a priority. I will report back
[Other SmartWatches] ThePurpleK:
The watch just wouldn't start up, no matter how many times I charged it. I'm not opening it up because I might break it further. Chances are I'm probably going to have to buy from InWatch USA when it's released, which kinda sucks since I'll need to wait.
[Other SmartWatches] inWatchUSA:
I will PM you my address, if you send it to me I will open it up and see if I can fix it. If not, be patient and when we have our web store together, I will work with you and get you another unit. I bet I can fix it though, sounds like the same problem I had. :fingers-crossed:
[Other SmartWatches] simple1i:
What the earliest we can get our hands on the watch? Even if the software is not ready, as long as all the hardware and the hydro coating is done?

.. And as long as the software can be updated. [emoji6]
[Other SmartWatches] inWatchUSA:
It is the CE and FCC certification that we are waiting for right now. The software will be ready in time for release in the USA and, while I cannot be sure of any dates, I am expecting dealers to have samples mid January and at that same time, to have our web store on the website active. Pre-orders on the website should be possible around the first of the year.

As an aside however, I am hoping to get a large number of units (about 200) sent directly to me to distribute as soon as our factory run is complete. I will be sure that if a member of this forum wants a Z, they will get one AS SOON as it is possible to.
[Other SmartWatches] Parcaetron:
I'd just like to add another voice in favor of bone conduction. To me, it's the watch's biggest selling feature. I love the idea of being able to play a song just by raising my hand to my head, instead of having to fumble for headphones.
[Other SmartWatches] perpe:
[MENTION=5891605]inWatchUSA[/MENTION]

Do you plan to release the kernel source code? I searched for it everywhere, but without success. I'm sure, you guys know, that you have to release it.
[Other SmartWatches] ThePurpleK:
I second this. Releasing the source code will allow for greater support from developers in the future, which results in higher adoption of your product. Look at Omate Truesmart... they released a flimsy OS and didn't make /their/ watch's source code open source. The result? It's become a failure.

Keeping the developer community open will grant the watch a longer lifespan. :)
[Other SmartWatches] simple1i:
Unless things have changed recently ... Mediatek are anti open-source, they rarely share their source code.

Might be a battle to acquire it.
[Other SmartWatches] ThePurpleK:
Yup. It's a shame InWatch uses MediaTek. There's little pressure on them to comply with GPL. http://www.xda-developers.com/android/have-you-paid-your-linux-kernel-source-license-fee/
[Other SmartWatches] perpe:
No, that isn't right. The device manufacture is allowed to release the mediatek kernel source. Each manufacture gets with his Madiatek source tree a script to separate the kernel source from the Android source tree. Only the Mediatek Android source tree is closed and the manufactures are not allowed to release it, but the kernel source they can and have to release to fulfill the GPLv2.

Look at the BQ Github repo, they have released the kernel source of all their MTK devices. Look at wikogeek.com, there you can find the kernel sources for all the Wiko MTK devices. Alcatel has a repo on Sourceforge with the kernel sources of their devices.

The Mediatek kernel source is a mess, but most of them a compile and usable. I own different MTK devices and built some of the kernels, also with uncomplete source tree. I have sent more than one e.mail to Inwatch Z China with source code request, with the MTK script, too. They never answered :(
[Other SmartWatches] Apokriphos@gmail.com:
I just ordered a Inwatch Z and I am very interested in starting a thread in which we compile all that we know about Inwatch Z tweaks and modifications for English users.

Inwatch Z /w 4.4.2 Android has been reviewed on youtube, though it seems unavailable.

I saw that the v15 (4.2.2) Chinese firmware was linked a few pages back but both download links are invalid, even with a qq account. I also have watched a video on watch face editing for the Inwatch Z and heard mention in this thread of TWRP adjustments from the Omate Truesmart that could be adapted into a Recovery mode for the Inwatch Z. Lokifish made some adjustments to the brightness scaling on his watch which could be added as well.

A straightforward Rooting guide would also be useful.

Does anyone know if all of this is still available somewhere and/or interested in making a new thread to keep the information up to date?
[Other SmartWatches] simple1i:
Thanks for the rectification perpe.

I'm sure Sam will reply here and either release the source code or explain why InWatch Z can not.

Are some manufacturers afraid that if they release their kernel source then other copycats might clone their hardware and then used their released kernel code too?

... And use their name too?
[Other SmartWatches] inWatchUSA:
Even though it seems kind of far fetched, you are right on the money with that guess simple1i. Many manufacturers believe that with their source out there, other factories will spool up reasonable LOOKING copies with gutted hardware that still barely limps along. The user finds this version of "Z", hates the experience they have with it, the brand is then damaged in their eyes. Critical first impressions and all. As I said, seems far fetched. Still happens. Be that as it may.

To answer your question directly however, yes. inWatch will be releasing the source code for our 4.4 OS. It is still in closed beta so any review (can someone link it?) may not be 100% indicative of the final product. Cool that it is out there though! I cannot tell you how exciting/crazy/scary it feels to finally be nearing a US launch of Z! These final steps are critical too! OK, back to the source code and on to the event.

inWatch is in the first stages of planing a hackathon with UC Berkley students at their campus in Berkley, CA. When we were putting together the event, I brought up the prospect of non-students participating in the competition. They thought about it and have agreed that as long as there is one student on the team, it is acceptable. So that is quite exciting! It will allow young minds as well as interested pros to take a shot at writing something for Z and making a difference in the wearable space. Something even more exciting is that we are working on having the winning team flown to Mobile World Congress in Barcelona, Spain where they will take their idea to the next level! This could turn into something really incredible. I remind you that we are still planning and crafting this and it is a first for us. We want to have it happen sometime in Feb 2015 and are not officially announcing this for a while but I wanted to share this here because of obvious correlatives.

I hope this gives clarity to our position on source code. We still have the fears associated with opening our source to the world. There are still conversations being had as to how to do this correctly. But the benefits are clear. As can very easily be seen here, the people whom we want to use inWatch Z are asking for it. We will deliver.
[Other SmartWatches] Apokriphos:
Thank you very much for your reply Mr. Force. I am eager to see the start of your new campaign, and perhaps buy another watch for my girlfriend if my current one works out.

Since no one has answered my question yet, I figure I might as well ask it again here:

I recently purchased a used Inwatch Z with a slightly worn Rubber/Silicon Band.

From what I've heard:

Step 1). Clean with either Toothpaste or 1:3 diluted dishwashing soap, using hands. Be careful to avoid areas near and around embedded electronics.

Step 2). Dry, then apply Armor All, or other tire/plastic protectant.

From your experience with the Inwatch Z, do you have any suggestions on how to maintain/restore/clean it?
[Other SmartWatches] inWatchUSA:
Happy to help, glad you are enjoying Z so far. As far as maintenance, the above steps seem great. It kinda got me thinking because I have my white Z, the oldest one I have and it probably has some wear by now as well. I will try a few things and let you know what works best for me.
[Other SmartWatches] perpe:
This could be, but if they are so afraid then thy do better not using GPLv2 licensed code. GPLv2 means you have to release the source code. It isn't a choice, don't releasing it violates the licence agreement. Every Android device manufacture has agreed with this licence terms with his release of an Android devices. GPLv2 applies to the kernel, most parts of the Android source code is licensed with Apache License, Version 2.0. The Apache licence means you can keep your code closed, but this doesn't apply to the kernel. The kernel is still GPLv2. The conclusion is every manufacture have to release the source code for the kernel of their devices, but can keep the rest closed. (exception: the AOSP tree contains a lot of GPLv2 licensed parts within the external folder, if a manufacture changes code in one of this GPLv2 parts, he has to release the code for it, too)

Please, read also http://www.xda-developers.com/android/xda-developers-and-the-gpl/
[Other SmartWatches] Lokifish Marz:
Adam Outler an myself in dealing with MTK and source code- http://www.xda-developers.com/android/have-you-paid-your-linux-kernel-source-license-fee/

Combine that with the following which came directly from MTK at an ODM level: "We do release source code to our

licensee

customers without any problem. However, as the company policy, we won’t be able to release SW to un-licensee."

Further more, MTK locks ODMs/OEMs into an NDA and contract that limits what can be released. I have a copy of it somewhere (most likely on the computer the movers busted). The more you pay the more they will let you say/release. Due to this and Chinese ODMs adding further restrictions, was the key reason why my own smartwatch project has stalled.

In short, the Chinese market, MTK and unlicensed clones has made it very a "state secret"(ish) system. No MTK has promised to be more open, remains to be seen on a large scale, but that still leaves the rest of the industry in that part of the world to deal with. If it was not so, then a entry level quality smartwatch (think $100-200 level of real watch) would already be in prototype production phase right now.

So MTK uses GPL code, re-licences it, give source to major contracts and binaries to smaller contracts, wraps it all up in an NDA and calls it a day. ODMs/OEMs then add their hooks (further re-licencing and NDA addendums) to the line and calls it a day. After some examination of multiple smartwatches using the 6572, certain device specific flags show up on multiple devices across multiple manufacturers, which may be to MTK bulk coding and passing it off as "our secret". Problem is that none of the companies can talk to each other or are afraid violating NDAs by admitting that they have.

All this leaves companies trying to do the right thing holding the bag and having to quell GPL compliance requests while fighting with MTK.
[Other SmartWatches] StridAst:
I've been following the "z" for a while online. I'm quite interested in seeing where it goes. A suggestion to pass along to whoever. Try making a bluetooth bone conduction earpiece as a companion to this phone. Something that clips over one ear and rests against the skull behind your ear. Gets the advantages of the bone conduction speaker without needing to hold the phone against your head. Win win. Just my two cents. Oh, another +1 for an internal bone conduction speaker. Its what makes the Z stand out from the crowd. Still suggesting an external version on top of that

EDIT: To better explain what I mean. These standalone smartphone/watch devices really need a bluetooth headset to be useful as a phone. the problem is bluetooth headsets are a pain in the ass to put on every time you need to answer the phone, or call someone. bluetooth headsets are also a pain in the ass to leave in your ear, since you can't hear well out of that ear anymore, Bone conduction speakers have the advantage of working without covering your ears. So if some company were to design and make a bluetooth headset that works with bone conduction, comfortable enough to be worn for long periods at a time, but didn't cover the ears, then a person could simply leave the headset cliped onto the ear, and hopefully have the bulky battery components behind the ear. and out of sight. Then you could just answer the phone on your watch and talk away.

I've seen the Cynaps bone conduction hat that's out there. Something that you can wear without having to wear a hat would be nice. something that doesn't look too obtrusive would be nice.
[Other SmartWatches] Parcaetron:
So I finally coughed up the money and bought this watch! I'm super excited.

What should I do once I get it? Is there a list of "must have" apps somewhere? I guess, off-hand, what I'm looking for would be:

1. A way to use it as a speaker for my laptop and phone;

2. A notifications syncer for when I'm using the watch in tether mode;

3. A way to add additional watchfaces.

Or, of course, any other suggestions people might have.

Whee!
[Other SmartWatches] Apokriphos:
I am still messing with my Z, but overall it has been a great experience. I love this watch (so far) and am eagerly awaiting the US launch.

The first things I did:

Enable developer mode, USB debugging.

Rooted the Inwatch Z: I did this by downloading Kingo ROOT, and following onscreen prompts. Kingo Root will fail after running the initial reboot checks and downloading drivers, leaving you unable to root.

Simple Fix: Unplug your usb after drivers installed and watch is rebooting. Kingo ROOT will be displaying "waiting for device" at this point. Do not unplug beforehand obviously. Once you plug your usb back into your computer, it will recognize the Z and everything will go smoothly.

Download Chainfire's SuperSU.

Afterwards, download Xposed, and get GoogleOfflineVoice, Gravity Box, Light Adjustment (allows for up to 1% backlight), TouchPal (keyboard) and Play Store Fixes (for play store app availability).

Then, get SWApp Link (for using your watch as a companion), Shake (for arm twist waking), and Auto Dimmer (for late night time checking if you wear the Z in bed).

As far as Battery Management apps go I happen to like Battery Doctor, after altering its permissions a bit.

Things you asked about I haven't covered:

I dont have a sim card for my Z yet, so I haven't tried using it as a phone. Verizon.. However, when paired via SWApp link you can't use the internal speakers/mic to speak/listen obviously. I will have to try it when just bluetooth paired to see if this works.

Problems:

Battery Life.

The Z has great battery life, but I have noticed that sometimes the charging cycle doesn't "take" when docked. This means it says its charging, but when I take it off charger in an hour of no use I notice its nearly dead.

The charge state monitor when powered off (and charging) seems the most reliable, but even it has problems when charging (fast) when a short usb cord. Last night I had it charged at 50% powered off, unplugged it and went to bed, and in the morning when I plugged in to finish cycle it was at 100%. Pretty sure something's up. My typical battery life is great though, 2-3 days with just bluetooth pushes + all aforementioned apps running in background.

I just discovered Lokifish's trick of setting display to "always on". Going to play around with that and see how it impacts battery life further.

2nd Problem: Display DPI: I think this might be related to gravity box. After install I noticed my Keyboard and Battery Doctor app had a different layout. Battery Doctor wouldnt show the option to cleansweep, even with compatibility mode checked. Keyboard only showed half, covering same screen real estate. Will be playing with this further to determine cause unless someone else knows.

Enjoy your Z and let me know what you think of these suggestions.
[Other SmartWatches] Theo de Kok:
If I use that trick for setting display to 'always on' the battery is discharging very rapidly. Obviously not a very good choice for me.

I use a bluetooth mini keyboard with 5000mAh powerbank and it works great. A cheap device and very helpful.

I never noticed a problem with charging, powered off or not.
[Other SmartWatches] Apokriphos:
One thing I would like to find out is how to install a TWRP touch based recovery.

Anyone know?
[Other SmartWatches] Theo de Kok:
Maybe Sam has the answer. I e-mailed him this question too. Well not quite, I asked if this option could be added.
[Other SmartWatches] Parcaetron:
Does anyone else know how to factory reset this device? It arrived with some other guy's apps on it (I bought it second-hand), and the normal method, via Settings, doesn't work because the square screen cuts off the bottom of the "do you wish to proceed" screen.

My version has 4.4.2 on it, by the way. If anyone wants me to upload the firmware, give me instructions and I'd be happy to oblige.
[Other SmartWatches] Wii60:
I think I know the unfortunate answer to this, but when ATT shuts down its 2G network, will these cease to function on ATT? Or will the "As good as 3g" 2g radio still work?
[Other SmartWatches] Apokriphos:
RE: At&t 2G Network harvesting - Shutdown by end of 2017. 2G devices will no longer work on their network at that point.

Inwatch Z: Networking: GSM

Frequency 2G: GSM 850,900,1800,1900MHz

Data transfer: GPRS/HSPA/EDGE

It is possible the Inwatch Z will continue to work after the 2017 shutdown by switching to another provider. See list below:

You can use GSM unlocked phones with any GSM service providers when the phone supported network is compatible with the GSM service providers.

AT&T - GSM 850/1900, 3G 850/1900

T-mobile - GSM 1900, 3G 1700/1900

Straight Talk GSM only - depends on AT&T or T-mobile

other prepaid GSM carriers:

Lyca Mobile

Net10 Wireless

Red Pocket Mobile

Simple Mobile

Ultra Mobile

Hey Parcaetron,

I did the exact same as you, and am also pondering a reset - I will let you know if the same issue exists. My Z came with a recovery installed, though it is not touch based, and I am still using 4.2.2. I am certain there is a way to make backups once rooted, will post the process as I remember once home.

If anyone else more knowledgeable can help us out that would be great.

---------- Post added at 11:44 AM ---------- Previous post was at 11:35 AM ----------

Just to confirm, with 4.2.2 Installed, the reset button is clearly visible on the bottom edge of the screen. Some patient clicking activated it, but the back button canceled before any harm was done - so it works :). I believe I use 160 DPI (whatever default is). You should be able to change your default DPI for the settings app specifically by adjusting it in Xposed module "App Settings".

I had to change the DPI for Battery Doctor to 95 because (due to something I installed, I think) the option to clear running programs was cut off via a resolution change.

The same happened to my TouchPal. Default android keyboard still works fine. Will probably reset after tinkering a bit more if I cant find out whats wrong.
[Other SmartWatches] Apokriphos:
It seems you can create a Backup ROM without Recovery Installed solely through google play:

Download:

Busybox Free

Nandroid Browser

Online Nandroid Backup * ROOT

I think this method could also be used:

theandroidhow.com/2014/05/how-to-backup-restore-stock-rom-with-sp-flash.html