The short lowdown on the ZGPAX S5: it is a full-blown Android smartphone with quite a bit of CPU power packed inside a watch form factor. Although usable as a mere ‘smartwatch’ when jumping through some hoops, it is intended as a standalone device and can be quite successful at that, when taking the time to configure it and work around the most obvious flaws.
However, some important issues lead me to not recommend this watch phone to the general public that wants to buy something that ‘just works’ out-of-the-box. Amongst these issues are poor battery life, lack of quality assurance that might result in random defects on the particular unit you will receive from the reseller, as well as some fundamental flaws in the touch screen and radio subsystems. For people with more patience and the willingness to do some hacking however, it is well worth its reasonable price tag and a good sign that wearable tech could have a bright future.
A few months after doing this review, I tested the similar IKWear IK8 which proved to be a much better designed product with very similar hardware, so you may also want to check out my review of it. I no longer use the S5, my main watch phone is now the Abardeen F80 which I obviously also reviewed.
Recently I wrote a lengthy article about smartwatches and smartphones. For clarity, I consider a ‘smartwatch’ the kind of device that only serves as a companion device to a nearby smartphone. What I call a ‘watch phone’ on the other hand, is a fully autonomous device. The article explains why I believe the concept of a device that is only useful when tethered to a nearby phone, is flawed. For me it would be a step back, because I have been using true watch phones since mid-2008.
My last watch phone, the MQ668, proved to be of poor build quality and started showing worrisome cracks everywhere, so I decided to replace it. I was also pretty frustrated by all its bugs in both hardware and software, which I had managed to fix only partially. Last but not least, I was also getting tired of its ancient operating system, limiting functionality to that of cell phones from the first years of this millennium. A strict requirement for my new watch phone was therefore that it must run Android.
Considering the available Android-based watch phones (i.e. devices that can make calls and access the internet autonomously), the offerings are still quite limited at this time. There is the Z1, which is bulky and runs an old Android release. There is the Neptune Pine, which is great feature-wise (especially because it is detachable), but it is way too large for being a watch, and at the time of this writing, still not shipped to customers. The remaining models are all very similar in form factor and specifications: one of them is the Omate TrueSmart, which has been plagued by a few disappointing setbacks like lack of Play store support, and some other issues that left a sour taste with the backers of its Kickstarter campaign. Another one is the Pearl Simvalley AW-414.go, similar to the Omate.
The Chinese have also been busy of course, and have released watch phones very similar to the Omate and AW-414.go. As usual, their pricing is pretty competitive, but if you have read my long watch phone rant, you know why. Still, one particular model caught my eye for various reasons, and in the end I decided to have a go at it. The model is the ZGPAX S5. Having learnt from my experiences with the TW810 (see MQ668 review), I ordered directly from a Chinese reseller. I asked not to try anything fancy with customs declarations, and just provide correct forms. In the end I paid a total of about €150, of which a good 30% were customs taxes, but I received the gadget quickly and without hassle.
Contrary to your average smartwatch, the ZGPAX S5 is a full-fledged smartphone in a very tiny form factor. It has:
The dimensions are almost identical to the MQ668: about 60×40×14mm, making it very wearable under clothing.
The S5 runs Android 4.0.4 with Play store access. It comes with a custom launcher that is tied together with a clock screensaver. Whenever the display turns off, the phone will show the clock face when woken up again.
In the box, next to the phone there is a microUSB cable and USB mains charger, a headset that plugs into the microUSB port, and a short instruction manual. The FM radio only works with the headset, because it needs it as an antenna.
There are no volume buttons, most apps with audio (including the phone) offer an on-screen volume control when holding down the ‘back’ key. Custom apps like Pie Control can also be used to invoke a volume control.
It is hard to stress how much of an improvement this is over the previous generation of Chinese watch phones. If I would have to give a multiplication factor of how much more useful an Android-based device like this is, compared to the average MT6225-based phone with its primitive Mediatek Nucleus operating system, I would say the factor is 1000, give or take. The mere fact that any Android app compatible with the tiny screen resolution can be installed and that I could write my own apps, makes this watch phone almost infinitely more useful.
swastikain a manual, though.
Issues that I managed to solve through a hack or tweak are marked with a [Hacked] or [Tweaked] link to their corresponding fix in the hacks section.
In this section I summarise the tweaks and hacks I did to tailor my S5 to my needs. Like I said before, the good thing about the S5 is that there is a community around it that shares their experiences, see for instance the XDA forums and Joe's Tech Review.
The S5 comes with what appears to be a screen protector, but it barely sticks. I recommend using pre-made protectors for the iPod Nano 6th generation, which are a perfect fit. As an alternative, any larger protector can be cut to a size of about 36×36 mm.
Engineer mode can be activated by dialling *#*#3646633#*#*, or through an app like MobileUncle MTK Tools. Only use this if you know what you are doing!
For what it's worth, digging through the system files reveals that the ZGPAX S5 uses a MMA7660 accelerometer, and the touch display controller is an FT5206.
As with the MQ668, I made the S5 more practical as a telephone by fitting a 24mm deployment clasp instead of the tang buckle. This allows to take the watch off the wrist in just a few seconds, instead of either being forced to answer calls by talking to your wrist, or having the other party wait until you have fumbled open the tang buckle.
The other big obstacle for the S5 to be a practical telephone is the buzzing sound on outgoing audio. Both the cause and the fix are the same as with the MQ668: the microphone is too close to the GSM antenna. When the cell signal is weak, the antenna will transmit at maximum power and cause audible interference on the microphone signal. The microphone wires are wrapped inside electrostatic shielding, but this is insufficient. I tried to add more shielding, but it had no effect. The fact that the wires run parallel to the antenna seems to be the main problem. I tried a few configurations, but eventually I had to ensure that the mic wires went away from the antenna as quickly as possible, at a 90° angle. Just as with the MQ668, I relocated the microphone to the other side where there happened to be just enough room, and I drilled an air hole. I had to use 0.2 mm enamel wiring because anything else was too thick to route under the shielding, without affecting the tight fit of the battery. The main concern I had, was that the mic is now placed even closer to the loudspeaker than it already was, and there could be risk of feedback. There is indeed a short whistling sound at the start of a call, but it goes away immediately. Therefore the fix works perfectly, but it is obviously not something the average consumer would dare to attempt.
The short battery life can be mitigated in two ways. The first obvious one is to buy a larger battery: 700mAh batteries are available. They are 2mm thicker than the standard battery, meaning the total thickness of the phone becomes 16mm which is still OK. Dubious new airline regulations state that LiPo batteries may only be shipped inside their original product, so it is best to order extra batteries together with the S5 itself. Chinese resellers know the problem however, as well as creative ways to work around it (I won't go into details, but they managed to ship me some batteries while neither lying nor specifying on the envelope that it contained batteries).
The second remedy for battery life is also pretty obvious: avoid consuming much energy. Do not run power-hungry apps and disable useless animations where possible. A big power hog is WiFi: only enable it when you need it (there are some apps that can do this for you), this also helps to prevent it from locking up. Likewise, if you are not using the S5 as a phone that needs to be online all the time, enable airplane mode unless you need a data connection. This can easily double the battery life. The display does not consume enormous amounts of power thanks to its small size, yet it is recommended to set it to the lowest brightness and shortest timeout you are comfortable with.
The CPU in the S5 seems prone to getting stuck in a high-power mode, causing the phone to heat up for no apparent reason even when idle (and obviously consuming a lot of power). People on the XDA forums recommend setting the CPU governor to ‘ondemand’ instead of the default ‘hybrid’ to avoid this. I recommend the following approach: first, use an app like No-Frills CPU Control to set the default governor to 250MHz/500MHz ondemand, or even 250MHz powersave if you dare. Also set the I/O scheduler to deadline. Next, use Per-App Modes to fine-tune CPU performance for specific apps. I have made a list of the profiles and app assignments that I use.
To install apps that can manipulate the CPU governor, as well as for pretty much every other hack I report here, the phone must be rooted. Framaroot is reported to work, but it did not work on my S5. I used Cydia Impactor instead.
Once the phone has been rooted, the next step is to create a Nandroid backup so you can restore it in case you have badly messed up. I recommend Rashr to install either TWRP or CWM. Follow the instructions from the ‘Recovery’ section on the XDA forum post. I made a tweaked version of the TWRP ui.zip interface file [Download, 72kB]. Drop it in
/sdcard/TWRP/theme/. You may still need a magnifying glass to see what you're doing, but the interface elements are better arranged.
Forget about typing text with the standard keyboard, or the custom ‘iFlytek’ keyboard that is preinstalled: the keys are unpractically small. I recommend installing Slidy Press, which is a half-size keyboard with much larger keys. The most common letters are typed by tapping the keys, while the less common secondary keys are accessed by sliding over the keys. To avoid a bug with the backspace key, always slide left on the ‘u’ key to type a ‘p’.
If you find the Slidy Press keyboard difficult to read, I have made a tweaked version with a big bold font: [Download, 75kB, currently based on 1.3 version]. Uninstall the Play store version before installing this APK manually. Disclaimer: I give no warranties for this modified app whatsoever and it must not be redistributed.
The Qwerty5 keyboard extends on the concept of Slidy Press by squeezing three keys into one, which makes it more compact. Unfortunately it cannot be installed from within the Play Store: you need to obtain the APK in another way (e.g. install it on another phone) and sideload it. Another alternative that is reported to work well is the Swype keyboard. All these alternative keyboards take some time getting used to, but are certainly worth it.
I kind of like the simplicity of the stock launcher, so instead of installing a custom one, I hacked it to better fit my needs. You can download this customised launcher here [936kB]. To install, use a root explorer app to overwrite the existing /system/app/SzkctLauncher.app (obviously, make a backup of the original). Ensure permissions and owner are set correctly (
rw-r--r--, root:root), and reboot. Only do this if you have a backup and know how to unbrick your phone. I give no warranties whatsoever! These are the included fixes:
Some apps are unusable because parts fall outside the small screen (one example is the settings menu in Per-App Modes). To work around this, install the XPosed framework as explained in the XDA forums. Next, install the App Settings plugin (a few reboots are required to activate everything). In App Settings, create a profile for the problematic apps. To fit more stuff on the screen, set the DPI to a value lower than the default for the ZGPAX S5, which is 120 DPI. Likewise, you can enlarge the interface by using a DPI above 120. You can also tweak the font size to compensate for the rescaled interface.
A few examples: for Per-App Modes I recommend a DPI of 100 with a font scale of 110. For the Camera app, set DPI to 125 and font scale to 96: this moves the snapshot button down, making it much easier to hit.
To get the most out of the notoriously fickle Mediatek GPS that plagues all phones with this chipset, you should first of all install an app like FasterGPS and select an NTP server as close to your location as possible. Next, you need to enable some options of the GPS system that are disabled by default. You can do this in System Settings, but I recommend using Engineer mode when doing it for the first time. Go to ‘LocationBasedService’ and enable A-GPS, and EPO. You could try using the auto-download EPO feature, but it almost never works as of lately because the server that hosts the file can no longer handle the load. You should use an app that updates the file instead. My own EPO Updater is very simple, lightweight, and is especially suitable for the small screen of the S5. It should suffice to do all this once, except the EPO update should be performed once every month.
I recommend installing the app ‘GPS Status & Toolbox’, and running it whenever you plan to use the GPS, such that it can update your A-GPS data and ‘warm up’ the GPS. Configure the app to keep the screen awake. Under clear skies, the GPS should get a fix (satellites marked in green) within less than two minutes. Taking the phone off your wrist seems to help to speed up obtaining a GPS fix. Sometimes the S5 may end up in a state where it fails to obtain a fix no matter what. If this happens, try deleting the /data/misc/mtkgps.dat file and rebooting the phone to reset its state.
Mind that the GPS is inherently bug-ridden on all phones with this chipset. It is quite typical for the GPS to get in a messed-up state after it has lost its satellite fix due to e.g. driving under a bridge. The only remedy in such case is turning the GPS off and on again, after which it will typically regain its fix within seconds.
The preinstalled Google Calendar cannot sync with online accounts because GoogleCalendarSyncAdapter.apk is missing. You can either get the right version of that APK (look for “YourZgapps XS 4.0.4”), drop it in /system/app/ and install it from there, or disable the preinstalled app and install the Calendar app from the Play store.
The microUSB port is not protected, but little rubber plugs are available that can be inserted to keep dust from getting inside.
This is definitely the best watch phone I have had so far (until I got the IKWear IK8), but it still is not quite ‘there’. The overall impression is that of a typical Chinese product, hastily brought to market before being properly tested and finished. The good thing about it, is that it runs Android and is therefore much easier to tweak than the closed platform of the older watch phones. However, it has some hardware defects that cannot be fixed in software.
In my opinion, the following problems need to be fixed before a device like this could have any success with the general public:
The bottom line is that I would not recommend the ZGPAX S5 to anyone except the hardcore watch phone enthusiast. The IKWear IK8 is a much better choice if you want similar hardware for a similar price, in a better designed end-product. Last but not least, the Abardeen F80 is detachable, has twice the amount of RAM and a much better touchscreen, and runs a more recent Android version. The Omate TrueSmart and Pearl/SimValley watch phones might score a little better on the quality front, but they also suffer from awful battery life and the general lack of Android support for such tiny screens. The Pine looks promising but is way too large as a watch. Nevertheless, they all give me good hopes that we are coming closer to a truly usable watch phone.