📜 ⬆️ ⬇️

Chinese Chaofon AN1 Smart Watch

Box

Hello, lovers of Chinese and not very gadgets. I’m sure many people are fed up with this endless stream of faceless tablets, especially, for example, companies like Google are pressing the price and quality bars with their Nexus, making the acquisition of the next Chinese tablet know-how a dubious idea.
I guarantee - this tablet review will not. While everyone is looking forward to a new wave of wearable gadgets, namely “smart watches” from Apple, Motorola, LG and others, the Chinese did not pull for a long time and urgently released their version of smart watches, the sample of which fell into my hands.

Meet, 100% know-it-yourself watch phone - SmartWatch AN1.
Spoiler: at the end of the review, he will hack.

Story


If you have ever done a review of something on a Habré, then be sure that sooner or later you will be knocked on the good Chinese and will offer you to tell Habr about this or that gadget, and the choice of something hoo wide: apart from tablets, It is known that there are no useful items for their IT specialists in their depressed warehouses. And to review the Chinese tablets, especially in Habré, is an ignoble matter, starting in 2012.
But this time, the fartanul: a cute girl invited me to look at their smart watches and, if interested, make a review. Of course, because the topic of wearable gadgets I care about for a long time, but here such a case fell out to evaluate the Chinese approach. April 23 sent via Singapore, May 19 in our mail, quite quickly. Most photos are clickable.
')
Parcel
Figure 1. Well they filled out the declaration. I hope the content
the cherished box will pull on more than an MP4 player for $ 0.06.

Kit and features


With the characteristics of a strange situation: on the sites of shops, on the box, and in fact, the characteristics are different.
OSAndroid 4.0.4, on the box and in the firmware is 4.1.1
CPU1GHz, Single Core, MT6515 ARMv7, graphics: OpenGL ES 1.1, PowerVR SGX 531, AnTuTu score: 5855
Memory512M RAM, 4GB NAND (a markup such that is available around 512M - in half on / system and / data)
Screen2 ", 320x240, capacitive TFT (5 points)
ConnectionGSM, EDGE, GPS, FM, Bluetooth 3.0, WiFi b / g / n ( MT6628 chip)
Slots and PortsmicroUSB, microSD, SIM
Dimensions60 x 41 x 15, 72g with battery (900mAh, Lithium, 3.7V)
Specification on the box
Box fake spec

Build.prop dump
# begin build properties # autogenerated by buildinfo.sh ro.build.id=IMM76D ro.build.display.id=ALPS.ICS2.MP.V1.18 ro.build.version.incremental=eng.lt.1395940871 ro.custom.build.version=1395940871 ro.build.version.sdk=15 ro.build.version.codename=REL ro.build.version.release=4.1.1 ro.build.date=Fri Mar 28 01:23:10 CST 2014 ro.build.date.utc=1395940990 ro.build.type=user ro.build.user=lt ro.build.host=ubuntu ro.build.tags=test-keys ro.product.model=AN1 ro.product.brand=XINGHAN ro.product.name=F9-2S ro.product.device=F9-2S ro.product.board=XINGHAN ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=XH_F9 ro.product.locale.language=zhr ro.product.locale.region=CN ro.wifi.channels= ro.board.platform= # ro.build.product is obsolete; use ro.product.device ro.build.product=F9-2S # Do not try to parse ro.build.description or .fingerprint ro.build.description=fise15_ics2-user 4.0.4 IMM76D eng.lt.1395940871 test-keys ro.build.fingerprint=alps/fise15_ics2/fise15_ics2:4.0.4/IMM76D/1395940871:user/test-keys ro.build.flavor= ro.build.characteristics=default persist.sys.timezone=Asia/Shanghai # end build properties # begin mediatek build properties ro.mediatek.version.release=ALPS.ICS2.MP.V1.18 ro.mediatek.platform=MT6575 ro.mediatek.chip_ver=S01 ro.mediatek.version.branch=ALPS.ICS2.MP # end mediatek build properties # # system.prop for generic sdk # rild.libpath=/system/lib/mtk-ril.so rild.libargs=-d /dev/ttyC0 # MTK, Infinity, 20090720 { wifi.interface=wlan0 # MTK, Infinity, 20090720 } # MTK, mtk03034, 20101210 { ro.mediatek.wlan.wsc=1 # MTK, mtk03034 20101210} # MTK, mtk03034, 20110318 { ro.mediatek.wlan.p2p=1 # MTK, mtk03034 20110318} # MTK, mtk03034, 20101213 { mediatek.wlan.ctia=0 # MTK, mtk03034 20101213} # MTK, TeChien { ro.media.enc.hprof.file.format=3gp ro.media.enc.hprof.codec.vid=m4v ro.media.enc.hprof.vid.width=720 ro.media.enc.hprof.vid.height=480 ro.media.enc.hprof.vid.fps=30 ro.media.enc.hprof.vid.bps=3400000 ro.media.enc.hprof.codec.aud=amrnb ro.media.enc.hprof.aud.bps=12200 ro.media.enc.hprof.aud.ch=1 ro.media.enc.hprof.aud.hz=8000 ro.media.enc.mprof.file.format=3gp ro.media.enc.mprof.codec.vid=m4v ro.media.enc.mprof.vid.width=352 ro.media.enc.mprof.vid.height=288 ro.media.enc.mprof.vid.fps=30 ro.media.enc.mprof.vid.bps=990000 ro.media.enc.mprof.codec.aud=amrnb ro.media.enc.mprof.aud.bps=12200 ro.media.enc.mprof.aud.ch=1 ro.media.enc.mprof.aud.hz=8000 ro.media.enc.lprof.file.format=3gp ro.media.enc.lprof.codec.vid=h263 ro.media.enc.lprof.vid.width=176 ro.media.enc.lprof.vid.height=144 ro.media.enc.lprof.vid.fps=30 ro.media.enc.lprof.vid.bps=384000 ro.media.enc.lprof.codec.aud=amrnb ro.media.enc.lprof.aud.bps=12200 ro.media.enc.lprof.aud.ch=1 ro.media.enc.lprof.aud.hz=8000 # MTK, TeChien } # wifi.tethering.interface=ap0 # ro.opengles.version=131072 wifi.direct.interface=p2p0 dalvik.vm.heapgrowthlimit=64m dalvik.vm.heapsize=128m # Encrypt phone function ro.crypto.tmpfs_options=mode=0771,uid=1000,gid=1000 ro.crypto.fs_type=ext4 ro.crypto.fs_real_blkdev=/emmc@usrdata ro.crypto.fs_mnt_point=/data ro.crypto.fs_options=noauto_da_alloc ro.crypto.fs_flags=0x00000406 # audio ro.camera.sound.forced=0 ro.audio.silent=0 # USB Config Type ro.sys.usb.storage.type=mtp,mass_storage # USB MTP WHQL ro.sys.usb.mtp.whql.enable=0 # Power off opt in IPO sys.ipo.pwrdncap=2 ro.sys.usb.storage.type=mtp,mass_storage # # ADDITIONAL_BUILD_PROPERTIES # fmradio.driver.chip=3 ril.external.md=1 ro.sf.hwrotation=0 ril.current.share_modem=1 launcherplus.allappsgrid=2d launcher2.allappsgrid=3d_20 curlockscreen=2 ro.mediatek.gemini_support=false drm.service.enabled=true fmradio.driver.enable=1 mediatek.wlan.chip=MT6628 mediatek.wlan.module.postfix=_mt6628 dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt ro.config.notification_sound=OnTheHunt.ogg ro.config.alarm_alert=Alarm_Classic.ogg ro.config.ringtone=Backroad.ogg net.bt.name=Android dalvik.vm.stack-trace-file=/data/anr/traces.txt 

NAND specification
image

NAND markup
 [PART] blksz: 2048B [PART] [0x0000000000000000-0x000000000003FFFF] "PRELOADER" (128 blocks) [PART] [0x0000000000040000-0x00000000000FFFFF] "DSP_BL" (384 blocks) [PART] [0x0000000000100000-0x00000000003FFFFF] "NVRAM" (1536 blocks) [PART] [0x0000000000400000-0x000000000041FFFF] "SECCNFG" (64 blocks) [PART] [0x0000000000420000-0x000000000047FFFF] "UBOOT" (192 blocks) [PART] [0x0000000000480000-0x000000000097FFFF] "BOOTIMG" (2560 blocks) [PART] [0x0000000000980000-0x0000000000E7FFFF] "RECOVERY" (2560 blocks) [PART] [0x0000000000E80000-0x0000000000F9FFFF] "SECSTATIC" (576 blocks) [PART] [0x0000000000FA0000-0x0000000000FFFFFF] "MISC" (192 blocks) [PART] [0x0000000001000000-0x00000000012FFFFF] "LOGO" (1536 blocks) [PART] [0x0000000001300000-0x000000000139FFFF] "EXPDB" (320 blocks) [PART] [0x00000000013A0000-0x000000000FE9FFFF] "ANDSYSIMG" (120320 blocks) [PART] [0x000000000FEA0000-0x0000000011C9FFFF] "CACHE" (15360 blocks) [PART] [0x0000000011CA0000-0x0000000011C9FFFF] "USER" (0 blocks) 

For reference: the MT6515 processor is an absolute counterpart of the MT6575 , the only difference is in the absence of 3G from the 6515. The MT6575 came out in 2011, and hit the market by early 2012. The AN1 operating system is listed everywhere as Android 4.1.1, even in firmware, but in fact There is Android 4.0.4 ICS, which was released in 2012 the same year.

The device comes in 5 different colors: black, white, pink, gold and white, gold and black. As you can see, my chances of getting a review device of normal color were 20%. On the other hand, the chances of getting exactly pink are the same, so I am eternally grateful for the gold. Swag!

image
Figure 1. In the summer, the hand literally boils beneath them.
awolf:
gut nafig it to you at all
just do not say what was going to use as a clock
they can kill

xlab:
This is a clock, how to use it.
Do not chop the wood
though wait a minute ...

Package Manual
Figure 2-3. The standard contents of the box: subject, headphones, wire, power supply, instruction in broken English.

Cap Cap2
Figure 4-5. Vol + button, back button, plastic usb cap, speaker, you can see the hole for the camera

The lid for usb consists of hard plastic, immediately began to move away and became completely useless - had to be removed. The strap is made of silicone rubber, it tightens well (if desired, you can put a harness).

Buttons 2 Battery
Figure 6-7. Home button, power button on the other side of the case. The battery is removed very easily, under it there are slots for microSD and SIM cards.

There is no audio jack, the microUSB headphones were included, and they also act as an antenna for FM radio. The best application is to cut off half, and use the remaining piece of wire as an antenna, while the radio will work through the speaker.

103 Nikolay
Figure 8-9. Wearable on the wrist music box conditional Uncle Vasya.

Display CWM
Figure 10-11. The TFT screen barely drags, but everything is clearly visible. Best of all, of course, at night.

The screen behaves like any other one from the TFT family - it inverts colors at different angles, it is badly seen in the sun, there is grit, light spots. About TTX I do not know. The backlight cannot be adjusted.

image
Figure 12. SWAAAAG!

Price and Availability


I have no coupons and ref-links for you, and the price, in my opinion, biting - 4300 rub. You can buy this model in TinyDeal (there are other models of normal colors in the same place, there is even a discount on black). On DealExtreme, the wrong characteristics are shown from the box and the photos on the watch are mixed up and down, so I won't give you any links there. Let them learn to study their goods.

Software and firmware


As I wrote above, Android 4.0.4 is on the device. This is easy to check: first, you can look at the build.prop dump (under the characteristics table) and find the build identifier ALPS.ICS2.MP.V1.18 , secondly, you can poke several times on the line with 4.1.1 in the settings and to catch easter eggs from 4.0.x:

abouteaster
Figure 13-14. About Phone.

The firmware is practically AOSP, with minor modifications in the direction of reducing weight and usability on the screen 2. "Standard android - no more, no less. Then there will be only selected screenshots.

lockhome
Figure 14-15. Lock screen and desktop (set the clock MIUI ).

apps1apps2apps3
Figure 16-18. 3 screens of embedded applications. In addition to SuperSU.

From the embedded applications, the following can be noted:


listussd
Figure 19-20. I definitely like the look and feel of the dialer.

incomingoutgoing
Figure 21-22. Incoming and outgoing call.

cameraMXtimer
Figure 23-24. CameraMX with paid filters (in-app purchases). Some kind of stopwatch (with a banner).

smscontacts
Figure 25-26. Messages and contacts.

emailmail
Figure 26-27. Post application. By the way, you can be used quite seriously - it is very convenient to check messages.

browsertabs
Figure 28-29. Browser. Despite the screen size, the touchscreen performs its function extremely well.

The browser works smoothly, the canvas is scaled without brakes, the video opens right on the page or in a separate application, a short demonstration in the video below.



Reviewer is not related to the video.

gallerymusic
Figure 30-31. Gallery and music. The music application works correctly even with .m4a from iTunes.

There is no built-in Google Play, apparently in order to save space and to get rid of google-probes. Installing GApps manually is possible, but please note that the android version is 4.0.4 and the SDK is 15. There is not enough space on the / system partition, it should be set selectively. I'm not a fan of google services in my watch , so I decided that I would manage with the forum w3bsit3-dns.com and Yandex.Store.

storestatus
Figure 32-33. Yandex.Store, correctly working on 2 ". The status of installed applications (as usual).

pdfmaps
Figure 34-35. Reading PDF (with normal performance, but at 2 "320x240 is a perversion). Maps.

agpsgps
Figure 35-36. There is support for A-GPS. The GPS test went smoothly - the satellites were quickly found, although I was inside the room near the window.

As for playing video, here MK6575 obviously does not pull. A sample resolution of 720x304 came with noticeable lags in a standard video player, VLC and MX Player (with active HW Decoding). Therefore, if you need to watch a movie on the clock, you must first convert it to the screen resolution (320x240). Only it should be noted that with active use of CPU / GPU resources, the battery lasts about 2-3 hours.

powerimage
Figure 37-38. Battery consumption in standby mode (left overnight). CPU / GPU benchmark in AnTuTu.

Bit of phreaking


Before you make lewdness with the firmware and carcass of the chasofone, you should get NAND dumps while the device is still alive. First of all, you need to ruin the system, if you have not done it yet - I personally ruined it as soon as I took it out of the box. Framaroot copes with its task.

imagerequest
Figure 39-40. SuperSU is installed, the access request is working.

Now you should use the kitchen Mtk Droid Tools , created by our compatriot.

mtktools
Use the Backup (1) option to copy blocks from all NAND partitions. Option (2) will repack the downloaded blocks into the format perceived by the SP Flash Tool. Option (3) automatically generates and flashes CWM recovery . The button for entering recovery mode is VolUp, you just need to hold it when the device is turned on and until CWM appears.

The boot process of the entire MTK family, and mt6575 in particular, proceeds as follows: preloader -> uboot -> kernel. Accordingly, the preloader does the initial initialization, reads the NAND markup, and jumps to the uboot address. Depending on the reason for switching on (normal, plug in cable, ...), uboot continues loading or not. Preloader is responsible for drawing the charge indication and the logo, while the uboot decides what to do.

Preloader is also responsible for NAND firmware using the SP Flash Tool utility, which is used, roughly speaking, by the Chinese in the factory. In older models of Mediatek, the firmware was produced through the UART, but in our case everything happens quickly and via USB.
SP Flash Tool Interface
image

To flash NAND parts, turn off the device, click “Download” and connect the cable. When the cable is connected, the Preloader is detected by the program and the process begins. All parts automatically cling from a scatter file generated in MTK Droid Tools ( MT6575_Android_scatter.txt ). However, the description of the NAND markup must fully coincide with the actual markup on the device. In case of a mismatch, the program will safely notify about the error and write to the log what exactly did not match.
Current NAND markup for Smart Watch AN1 (taken from the UART log)
 part PRELOADER size 0 40000 part DSP_BL size 40000 C0000 part __NODL_NVRAM size 100000 300000 part __NODL_SECCFG size 400000 20000 part UBOOT size 420000 60000 part BOOTIMG size 480000 500000 part RECOVERY size 980000 500000 part SEC_RO size E80000 120000 part __NODL_MISC size FA0000 60000 part LOGO size 1000000 300000 part __NODL_EXPDB size 1300000 A0000 part ANDROID size 13A0000 EB00000 part __NODL_CACHE size FEA0000 1E00000 part USRDATA size 11CA0000 D920000 

Thus, if there are backups and the preloader is still alive, the device is unkillable. In the case of a preloader, the mt65xx has a special meta-mode , until it had to be checked (fortunately), but this mode is called by either a) pinching VolUp when connecting a usb cable, or b) closing a special test pin to the ground.

And then I could not resist.

f9-s2
+ partial photo of the back side (there is nothing interesting there).

The cheaper the device is made, the easier it is to disassemble it. The case was fastened with 8 identical cross screws, after unscrewing it, it broke up by itself (itself). Inside, as it turned out, the traditional hot melt glue or some kind of yellow electrical tape is not used. The entire periphery is neatly laid out on the shelves and pressed against the top of the case. On the same side of A are all the pins of interest to us. First, judging by a similar example for the mk6577 , the meta-mode activating pin is located on the right in the corner and is labeled as KCOLO . Secondly, there are pins tx4 , rx4 , tx1 , rx1 , one of them is clearly responsible for the UART. At random, it turned out that tx1 and rx1 in the lower right corner.

uart wiring surgery

The battery can be cut with a knife and then the wires from the UART will be removed without interfering with the battery. Now to this NEXT on the hand even more questions from others.

Kernel boot line The minicom needs to be configured to baudrate 921600. My pl2303 seems to cope with quartz. After loading, you can communicate with uart tx / rx via / dev / ttyMT0 and nothing will interfere with this.

This conclusion has helped in understanding the processes mk65xx and in the future will be very useful when debugging custom / uboot kernel assemblies, if it is not too lazy.

Further hacking can be done in amateur mode (setting and customizing the firmware until the device is morally obsolete) or in guru mode - try to glue the existing sources into one puzzle and build AOSP 4.1+ for example. By the way, the source code for the SoC mk65xx is publicly available. Various companies post the source codes of the firmware, observing the GPL, but at the same time they manage to merge certain confidential parts belonging to Mediatek. Repositories on GitHub are point-deleted by the DMCA, but on w3bsit3-dns.com there are immortal archives: http://w3bsit3-dns.com.ru/forum/index.php?showtopic=535287 . Our compatriots are distinguished by special enthusiasm towards mt65xx, for example, luckasfb , honorary forum user w3bsit3-dns.com and an amateur who collect custom firmware for the mt65xx family from leaked sources. I will soon check the situation for MT6575 a little deeper, since Android 4.1 will allow using the new Google Search with the recognition of Russian speech and, in particular, the matchless assistant Dusya right on the watch on his arm.

Results


The brand and the manufacturer could not be found, in the tags and prints flashes XINGHAN, nothing good could be found. Like the model - F9-2S. The device was made in the period October 2013 - March 2014, went on sale in April 2014. The overall quality is notable for exceptional savings on everything. Platform and OS - end of 2011.
All this is like some kind of experiment of small circulation and with a large price. Even with attempts to deceive the ordinary buyer. : <

On the other hand, lovers of gigahertz cores and megabytes of RAM will forgive me, these characteristics are not first-priority. The system works noticeably quickly (better than on some phones that I used to touch), the browser scrolls smoothly, Wi-Fi speed is normal (I have up to 15MBit / s on the network), the battery lasts for viewing the time all day. In any case, watch videos or read books on a wristwatch - it can damage the elbow of the left hand.

And finally, the main component for me is the hacking ability of the device. On the smart watch scale, the Smart Watch AN1 deserve a solid 8/10 , where 0 on the scale is Geeksphone Peak (I did a review exactly a year ago, by the way), and 10 on the scale is SoC Allwinner A10 and everything connected with it.

It sounds stupid, but I'm afraid of hours. They are ticking. And penetrate the brain.
—Dennis Lehane. Shutter Island.

Source: https://habr.com/ru/post/225359/


All Articles