[Other SmartWatches] monocharismatic:
I was given a present of a Mi Smart Band clone for X-mas which died (M4). My hotel points were gonna expire so I decided to spend some points on a smart watch to keep the account active. The watch in question is a supersonicinc[dot]com[slash]SC-68SW. Once I received the watch I had a hell of a time trying to install an app to work with it. The one mentioned in the manual wouldn't come up in Google Play store and the QR code on the watch wouldn't focus enough on the phone to register. I eventually figured out how to use BT Notifier and another app to finally have the watch get interfaced. But I just didn't like it. Doesn't look better than the Mi Band clone on the outside and the interface either. However, in the process I managed to learn a few things about Chinese clone smart watches. I figured this one runs Nucleus OS and is likely a clone of a RWatch M28, but called Marriott and told them I don't want it rather than try to dink around with it. They said keep it. So I did. Recently I decided to give another watch a try mainly because it has a camera built-in, takes SD card and a SIM card. It is a SuperSonic one as well, but I will make a separate post about that one as it is more complicated and I am not super impressed with it in the end either and may have to send it back. So I decided to at least try to document some things about these watches, so that someone on the forum here can identify what they are and perhaps provide additional information that will help someone.

First off, SuperSonic SC-68SW is a Mediatek based device (MT6261DA) which is a suspicious giveaway about Nucleus OS and being an RWatch clone.

I'll try to post some photos of the insides of the watch, but I may need some help to get that accomplished from someone here on the forum. The PCB has test points for SDA and SCL, so it maybe possible to get into it via I2C because I don't seem to be able to do it via USB with the watch either turned off or on.

Here is what I get with it turned off:

[ 4904.934339] usb 1-2: new full-speed USB device number 5 using xhci_hcd

[ 4905.073008] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00

[ 4905.073017] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

[ 4905.123658] cdc_acm 1-2:1.1: ttyACM0: USB ACM device

[ 4905.125660] usbcore: registered new interface driver cdc_acm

[ 4905.125664] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

[ 4905.172680] usbcore: registered new interface driver usbserial_generic

[ 4905.172715] usbserial: USB Serial support registered for generic

[ 4905.212374] usbcore: registered new interface driver option

[ 4905.212395] usbserial: USB Serial support registered for GSM modem (1-port)

[ 4907.714459] usb 1-2: USB disconnect, device number 5

[ 4911.045348] usb 1-2: new full-speed USB device number 6 using xhci_hcd

[ 4911.212446] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0002, bcdDevice= 1.00

[ 4911.212455] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4

[ 4911.212459] usb 1-2: Product: U8

[ 4911.212462] usb 1-2: Manufacturer: U8

[ 4911.212465] usb 1-2: SerialNumber: fffffffffffffff

[ 4911.217978] usb-storage 1-2:1.0: USB Mass Storage device detected

[ 4911.218282] scsi host2: usb-storage 1-2:1.0

[ 4912.239217] scsi 2:0:0:0: Direct-Access MEDIATEK FLASH DISK PQ: 0 ANSI: 0 CCS

[ 4912.239542] sd 2:0:0:0: Attached scsi generic sg2 type 0

[ 4912.255159] sd 2:0:0:0: [sdc] Attached SCSI removable disk

-- also note that I had to turn usb_modeswitching.conf off to get it to show a disk device

[sdc]

in kernel log (in addition to a modem), but in reality there isn't one, so I wasn't able to dd any data off of the watch that way.

With the watch turned on with usb_modeswitch.conf on it shows up like this:

[ 5304.200340] usb 1-2: new full-speed USB device number 10 using xhci_hcd

[ 5304.364675] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00

[ 5304.364700] usb 1-2: New USB device strings: Mfr=3, Product=4, SerialNumber=0

[ 5304.364704] usb 1-2: Product: U8

[ 5304.364707] usb 1-2: Manufacturer: U8

[ 5304.374194] option 1-2:1.0: GSM modem (1-port) converter detected

[ 5304.374357] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1

[ 5304.377155] cdc_acm: probe of 1-2:1.1 failed with error -16

-- just the modem, no drive device! Kinda the opposite effect... Hm...

lsusb shows this when turned on:

Bus 001 Device 010: ID 0e8d:0003 MediaTek Inc. MT6227 phone

-- and if you want more details then here there are:

Bus 001 Device 010: ID 0e8d:0003 MediaTek Inc. MT6227 phone

Device Descriptor:

bLength 18

bDescriptorType 1

bcdUSB 2.00

bDeviceClass 2 Communications

bDeviceSubClass 0

bDeviceProtocol 0

bMaxPacketSize0 8

idVendor 0x0e8d MediaTek Inc.

idProduct 0x0003 MT6227 phone

bcdDevice 1.00

iManufacturer 3 U8

iProduct 4 U8

iSerial 0

bNumConfigurations 3

Configuration Descriptor:

bLength 9

bDescriptorType 2

wTotalLength 67

bNumInterfaces 2

bConfigurationValue 1

iConfiguration 0

bmAttributes 0x80

(Bus Powered)

MaxPower 500mA

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 0

bAlternateSetting 0

bNumEndpoints 2

bInterfaceClass 10 CDC Data

bInterfaceSubClass 0

bInterfaceProtocol 0

iInterface 1 COM(data_if)

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x81 EP 1 IN

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x01 EP 1 OUT

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 1

bAlternateSetting 0

bNumEndpoints 1

bInterfaceClass 2 Communications

bInterfaceSubClass 2 Abstract (modem)

bInterfaceProtocol 1 AT-commands (v.25ter)

iInterface 2 COM(comm_if)

CDC Header:

bcdCDC 1.10

CDC ACM:

bmCapabilities 0x0f

connection notifications

sends break

line coding and serial state

get/set/clear comm features

CDC Union:

bMasterInterface 1

bSlaveInterface 0

CDC Call Management:

bmCapabilities 0x03

call management

use DataInterface

bDataInterface 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x84 EP 4 IN

bmAttributes 3

Transfer Type Interrupt

Synch Type None

Usage Type Data

wMaxPacketSize 0x0010 1x 16 bytes

bInterval 3

Configuration Descriptor:

bLength 9

bDescriptorType 2

wTotalLength 67

bNumInterfaces 2

bConfigurationValue 2

iConfiguration 0

bmAttributes 0x80

(Bus Powered)

MaxPower 98mA

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 0

bAlternateSetting 0

bNumEndpoints 2

bInterfaceClass 10 CDC Data

bInterfaceSubClass 0

bInterfaceProtocol 0

iInterface 1 COM(data_if)

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x81 EP 1 IN

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x01 EP 1 OUT

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 1

bAlternateSetting 0

bNumEndpoints 1

bInterfaceClass 2 Communications

bInterfaceSubClass 2 Abstract (modem)

bInterfaceProtocol 1 AT-commands (v.25ter)

iInterface 2 COM(comm_if)

CDC Header:

bcdCDC 1.10

CDC ACM:

bmCapabilities 0x0f

connection notifications

sends break

line coding and serial state

get/set/clear comm features

CDC Union:

bMasterInterface 1

bSlaveInterface 0

CDC Call Management:

bmCapabilities 0x03

call management

use DataInterface

bDataInterface 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x84 EP 4 IN

bmAttributes 3

Transfer Type Interrupt

Synch Type None

Usage Type Data

wMaxPacketSize 0x0010 1x 16 bytes

bInterval 3

Configuration Descriptor:

bLength 9

bDescriptorType 2

wTotalLength 67

bNumInterfaces 2

bConfigurationValue 3

iConfiguration 0

bmAttributes 0xc0

Self Powered

MaxPower 0mA

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 0

bAlternateSetting 0

bNumEndpoints 2

bInterfaceClass 10 CDC Data

bInterfaceSubClass 0

bInterfaceProtocol 0

iInterface 1 COM(data_if)

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x81 EP 1 IN

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x01 EP 1 OUT

bmAttributes 2

Transfer Type Bulk

Synch Type None

Usage Type Data

wMaxPacketSize 0x0040 1x 64 bytes

bInterval 0

Interface Descriptor:

bLength 9

bDescriptorType 4

bInterfaceNumber 1

bAlternateSetting 0

bNumEndpoints 1

bInterfaceClass 2 Communications

bInterfaceSubClass 2 Abstract (modem)

bInterfaceProtocol 1 AT-commands (v.25ter)

iInterface 2 COM(comm_if)

CDC Header:

bcdCDC 1.10

CDC ACM:

bmCapabilities 0x0f

connection notifications

sends break

line coding and serial state

get/set/clear comm features

CDC Union:

bMasterInterface 1

bSlaveInterface 0

CDC Call Management:

bmCapabilities 0x03

call management

use DataInterface

bDataInterface 0

Endpoint Descriptor:

bLength 7

bDescriptorType 5

bEndpointAddress 0x84 EP 4 IN

bmAttributes 3

Transfer Type Interrupt

Synch Type None

Usage Type Data

wMaxPacketSize 0x0010 1x 16 bytes

bInterval 3

Device Status: 0x0000

(Bus Powered)

lsbusb shows nothing when the phone is powered off.

I am gonna try to attach some pictures, let's hope they come through. Nope, it doesn't let me add links. [slash][slash]photos[dot]app[dot]goo[dot]gl[slash]YbH3LAjTB2x6u3xq9