Smartthings Running on Wink Relay

Thank you. So even though you installed your modified version before the update and then disabled Winkupdate, it still updated the app?

Hello, here is Josh’s approche to integrating the Wink Relay to ST, it works pretty well

1 Like

This will let you control the Wink relay from within ST app, right?
What about controlling ST from within the Wink relay. once you install the ST app in the relay, it will log you out every hour. You original workaround from Synthesis is not working for me. Any other options?

1 Like

Correct this lets you control the Wink Relay from ST. For my set up I’m using ActionTile to control ST from the Wink Relay

There is no other free option to be able to control St from the relay without being logged out anymore?

I have the SharpTools Android app installed on my Wink Relay to control SmartThings.

You could also use webCoRE to configure the button press events from the Wink Relay to trigger actions in SmartThings (via my STWinkRelay integration).

Or if you prefer a web interface, you could use the web interface at

Tile UI / Card UI
image image

1 Like

Hey, I made a step by step video of modding it for adding apps after a factory restore or out of the box. One can then KingRoot if they want to kill off the Wink relay part of it if needed for other use like ST. Otherwise it functions very well to toggle between either Google Now or Total Launcher, plus you retain the original buttons if you are going to use it with Wink. Check it out, hope it helps as I know a few people have asked for it?

Step by Step Wink Relay MOD Video


ActiON Dashboard was the last free webcontrol app released, is not complete like smart tiles , but works fine with buttons, search in the web

I saw in this link that we were able to install fully kiosk on android 4.3. I downloaded the link on the Wink Relay but he did not want to open. Does someone have an idea.

Made another video using some steps from here (Thanks!) that shows rooting and getting the Google Play Store working on the Wink Relay. Give it a view as it goes step by step for the visual leaners like me :smile:


I found a new way to control the wink button. We can use the wink in its original state or root. We have a wink account and an Artik Cloud account. In artik cloud we add the wink account with its credentials. it will automatically add all the buttons of all the winks you have. Then in Smartthings apps, go to the Marketplace / SmartApps and in Samsung Home you will find Artik Cloud. Register your credentials and SmartThings will automatically create a button for each wink button you add in Artik Cloud. It will work instantly on the side of smartthings but if you manually press the refreshing is done automatically at hourly. But there is the possibility, by IFTTT, of launching a refresh of the state of all the wink buttons. every time you press any button on the wink


If you want to start the ActionTiles link automatically. Download this app that I made. Place the google shortcut in the upper left corner. The application will wait for the Wink menu to start. will go back to the home menu and make a click in the upper left corner. In my application choose the number of seconds before it returns you to the home menu. and the number of minutes before the wink restarts if it no longer detects an internet connection. Capitalization is important in the link, open it with Chrome and the download will start automatically.


Stuck with the Wink Relay spash screen hanging. Assuming I need to get a serial -> usb cable. Can anyone point me in the right direction to one? Amazon or otherwise.

I was able to gather the edison file from an above post. I could not find a cohesive walk through on repair. Did I miss or does anyone have one they can share?


Managed to find my device into a bootloop. Setup Jtag and am getting this. Can anyone point me in the right direction?

Card did not respond to voltage select!
mmc2(part 0) is current device

MMC read: dev # 2, block # 2048, count 9728 ... Card did not respond to voltage select!
MMC: block number 0x2e00 exceeds max(0x0)
0 blocks read: ERROR
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Card did not respond to voltage select!
mmc2 init failed
kernel   @ 10808000 (4825656)
ramdisk  @ 11800000 (238581)
kernel cmdline:
        use boot.img command line:
        console=ttymxc0,115200 init=/init video=mxcfb0:dev=lcd,mxcfb_dataimage_lcd,if=RGB666 video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale no_console_suspend=1

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 3.0.35 (vagrant@precise64) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #97 SMP PREEMPT Thu May 11 15:35:31 UTC 2017
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writealloc
CPU identified as i.MX6DL/SOLO, silicon rev 1.2
PERCPU: Embedded 7 pages/cpu @c131e000 s6592 r8192 d13888 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 208128
Kernel command line: console=ttymxc0,115200 init=/init video=mxcfb0:dev=lcd,mxcfb_dataimage_lcd,if=RGB666 video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale no_console_suspend=1
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 379MB 378MB 64MB = 821MB total
Memory: 820432k/820432k available, 228144k reserved, 441344K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xfbe00000 - 0xffe00000   (  64 MB)
    vmalloc : 0xd9800000 - 0xf2000000   ( 392 MB)
    lowmem  : 0xc0000000 - 0xd9000000   ( 400 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0044000   ( 240 kB)
      .text : 0xc0044000 - 0xc08f6d0c   (8908 kB)
      .data : 0xc08f8000 - 0xc0984190   ( 561 kB)
       .bss : 0xc09841b4 - 0xc0b14848   (1602 kB)
Preemptible hierarchical RCU implementation.
MXC GPIO hardware
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
Set periph_clk's parent to pll2_pfd_400M!
MXC_Early serial console at MMIO 0x2020000 (options '115200')
bootconsole [ttymxc0] enabled
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
CPU1: Booted secondary processor
Brought up 2 CPUs
SMP: Total of 2 processors activated (3162.11 BogoMIPS).
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
ram_console: got buffer at 3ff00000, size 100000
ram_console: found existing buffer, size 20145, start 20145
console [ram-1] enabled
brcm_wlan_init: start
hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
hw-breakpoint: maximum watchpoint size is 4 bytes.
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32050000, Cache size: 524288 B
bio: create slab <bio-0> at 0
mxs-dma mxs-dma-apbh: initialized
print_constraints: SPKVDD: 4200 mV
print_constraints: vmmc: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
spi_imx imx6q-ecspi.0: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
mc_pfuze 1-0008: ID: 0,Full lay: 2 ,Metal lay: 1
mc_pfuze 1-0008: FAB: 0 ,FIN: 0
print_constraints: PFUZE100_SW1A: 300 <--> 1875 mV at 1300 mV
print_constraints: PFUZE100_SW1B: 300 <--> 1875 mV at 300 mV
print_constraints: PFUZE100_SW1C: 300 <--> 1875 mV at 1300 mV
print_constraints: PFUZE100_SW2: 800 <--> 3950 mV at 3300 mV
print_constraints: PFUZE100_SW3A: 400 <--> 1975 mV at 1500 mV
print_constraints: PFUZE100_SW3B: 400 <--> 1975 mV at 1500 mV
print_constraints: PFUZE100_SW4: 800 <--> 3950 mV at 3150 mV
print_constraints: PFUZE100_SWBST: 5000 <--> 5150 mV at 5000 mV
print_constraints: PFUZE100_VSNVS: 1200 <--> 3000 mV at 1800 mV
print_constraints: PFUZE100_VREFDDR: at 750 mV
print_constraints: PFUZE100_VGEN1: 800 <--> 1550 mV at 1500 mV
print_constraints: PFUZE100_VGEN2: 800 <--> 1550 mV at 1500 mV
print_constraints: PFUZE100_VGEN3: 1800 <--> 3300 mV at 2500 mV
print_constraints: PFUZE100_VGEN4: 1800 <--> 3300 mV at 1800 mV
print_constraints: PFUZE100_VGEN5: 1800 <--> 3300 mV at 2800 mV
print_constraints: PFUZE100_VGEN6: 1800 <--> 3300 mV at 3300 mV
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
i2c-core: driver [max17135] using legacy suspend method
i2c-core: driver [max17135] using legacy resume method
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 232K
PMU: registered new PMU device of type 0
Static Power Management for Freescale i.MX6
wait mode is enabled for i.MX6
cpaddr = d9820000 suspend_iram_base=d989c000
PM driver module loaded
IMX usb wakeup probe
the wakeup pdata is 0xd45f2ee0
add wake up source irq 75
IMX usb wakeup probe
the wakeup pdata is 0xd440f320
mxc_bt_rfkill driver success loaded
rfkill: BT RF going to : on
cpu regulator mode:ldo_bypass
_regulator_get: get() with no identifier
mx6_cpu_regulator_init: failed to get pu regulator
i.MXC CPU frequency driver
highmem bounce pool size: 64 pages
ashmem: initialized
NTFS driver 2.1.30 [Flags: R/O].
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.16)
msgmni has been set to 740
NET: Registered protocol family 38
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver lcd
mxc_sdc_fb mxc_sdc_fb.1: Can't get fb option for mxcfb1!
LCD SPI Request GPIO 58 OK!!
LCD SPI Request GPIO 55 OK!!
LCD SPI Request GPIO 56 OK!!
------------[ cut here ]------------
WARNING: at arch/arm/plat-mxc/clock.c:63 clk_disable+0x44/0x8c()
clock enable/disable mismatch! clk  ipu1_clk
Modules linked in:
[<c0051fc4>] (unwind_backtrace+0x0/0x138) from [<c008af90>] (warn_slowpath_common+0x4c/0x64)
[<c008af90>] (warn_slowpath_common+0x4c/0x64) from [<c008b03c>] (warn_slowpath_fmt+0x30/0x40)
[<c008b03c>] (warn_slowpath_fmt+0x30/0x40) from [<c006c738>] (clk_disable+0x44/0x8c)
[<c006c738>] (clk_disable+0x44/0x8c) from [<c02de938>] (mxcfb_set_par+0x69c/0x834)
[<c02de938>] (mxcfb_set_par+0x69c/0x834) from [<c02d0888>] (fb_set_var+0x124/0x290)
[<c02d0888>] (fb_set_var+0x124/0x290) from [<c02e187c>] (lcd_init_fb+0x54/0x70)
[<c02e187c>] (lcd_init_fb+0x54/0x70) from [<c0682050>] (lcd_plat_probe+0x304/0x364)
[<c0682050>] (lcd_plat_probe+0x304/0x364) from [<c0309410>] (platform_drv_probe+0x18/0x1c)
[<c0309410>] (platform_drv_probe+0x18/0x1c) from [<c0308058>] (driver_probe_device+0xb0/0x290)
[<c0308058>] (driver_probe_device+0xb0/0x290) from [<c03082c4>] (__driver_attach+0x8c/0x90)
[<c03082c4>] (__driver_attach+0x8c/0x90) from [<c03070ac>] (bus_for_each_dev+0x5c/0x88)
[<c03070ac>] (bus_for_each_dev+0x5c/0x88) from [<c0307944>] (bus_add_driver+0x188/0x268)
[<c0307944>] (bus_add_driver+0x188/0x268) from [<c0308794>] (driver_register+0x78/0x13c)
[<c0308794>] (driver_register+0x78/0x13c) from [<c0044640>] (do_one_initcall+0xfc/0x164)
[<c0044640>] (do_one_initcall+0xfc/0x164) from [<c00089a8>] (kernel_init+0x9c/0x140)
[<c00089a8>] (kernel_init+0x9c/0x140) from [<c004b408>] (kernel_thread_exit+0x0/0x8)
---[ end trace 199f8b1c5287134b ]---
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
console [ttymxc0] enabled, bootconsole disabled
console [ttymxc0] enabled, bootconsole disabled
brd: module loaded
loop: module loaded
m25p80 spi0.0: unrecognized JEDEC id ffffff
GPMI NAND driver registered. (IMX)
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPTP driver version 0.8.5
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <>
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 72
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
USB Serial support registered for Qualcomm USB modem
usbcore: registered new interface driver qcserial
ARC USBOTG Device Controller driver (1 August 2005)
android_usb gadget: Mass Storage Function, version: 2009/09/11
android_usb gadget: Number of LUNs=1
 lun0: LUN: removable file: (no medium)
Gadget Android: controller 'fsl-usb2-udc' not recognized
android_usb gadget: android_usb ready
Suspend udc for OTG auto detect
USB Host suspend begins
will suspend roothub and its children
ehci_fsl_bus_suspend begins, DR -- bypassed
host suspend ends
USB Gadget resume begins
fsl_udc_resume, Wait for wakeup thread finishes
dr_controller_run: udc enter low power mode
USB Gadget resume ends
fsl-usb2-udc: bind to driver android_usb
mousedev: PS/2 mouse device common for all mice
[himax] himax_ts_init
himax_add_i2c_device : i2c_bus=1; slave_address=0x4a; i2c_name=himax-tsHimax IC package 8528 D
Himax himax_read_flash addr_start = 622 , local_start_addr = 155 , local_length = 3 , local_end_addr = 157 , local_addr = 2
Himax cmd[0]=30,cmd[1]=0,cmd[2]=11,cmd[3]=17
Himax cmd[0]=32,cmd[1]=19,cmd[2]=2,cmd[3]=0
Himax himax_read_flash addr_start = 626 , local_start_addr = 156 , local_length = 6 , local_end_addr = 159 , local_addr = 2
USB Gadget resume begins
fsl_udc_resume, Wait for wakeup thread finishes
Himax cmd[0]=32,cmd[1]=19,cmd[2]=2,cmd[3]=0
Himax cmd[0]=1,cmd[1]=224,cmd[2]=3,cmd[3]=32
Himax cmd[0]=0,cmd[1]=0,cmd[2]=0,cmd[3]=0
Himax himax_read_flash addr_start = 512 , local_start_addr = 128 , local_length = 6 , local_end_addr = 130 , local_addr = 0
Himax cmd[0]=95,cmd[1]=0,cmd[2]=0,cmd[3]=16
Himax cmd[0]=0,cmd[1]=0,cmd[2]=100,cmd[3]=14
input: himax-touchscreen as /devices/virtual/input/input0
[himax]himax_ts_register_interrupt request_irq ok
[HIMAX TP ERROR]himax_ts_probe: handle missed interrupt
[HIMAX PORTING ERROR] interrupt gpio 107 request fail.
i2c-core: driver [himax-ts] using legacy suspend method
i2c-core: driver [himax-ts] using legacy resume method
i2c-core: driver [isl29023] using legacy suspend method
i2c-core: driver [isl29023] using legacy resume method
si114x 2-005a: si114x_probe: Probing si114x..
si114x 2-005a: _check_part_id: Detected SI1143 part_id:43
si114x 2-005a: _i2c_read_mult Retried read count:0
[HIMAX TP MSG] checksum fail : check_sum_cal: 0x00
si114x 2-005a: _read_response Command id:1
input: si114x_als_ir as /devices/platform/imx-i2c.2/i2c-2/2-005a/input/input1
input: si114x_als_vis as /devices/platform/imx-i2c.2/i2c-2/2-005a/input/input2
input: si114x_ps as /devices/platform/imx-i2c.2/i2c-2/2-005a/input/input3
si114x 2-005a: _read_response Command id:2
si114x 2-005a: _read_response Command id:3
si114x 2-005a: _read_response Command id:4
si114x 2-005a: _read_response Command id:5
si114x 2-005a: _read_response Command id:6
si114x 2-005a: _read_response Command id:7
si114x 2-005a: _read_response Command id:8
si114x 2-005a: _read_response Command id:9
si114x 2-005a: _read_response Command id:10
using rtc device, snvs_rtc, for alarms
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.1.0)
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised:
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.3] using ADMA
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using ADMA
mmc2: SDHCI controller on platform [sdhci-esdhc-imx.1] using ADMA
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
VPU initialized
mxc_asrc registered
Galcore version
revserved_memory_account:viv_gpu registerd
Thermal calibration data is 0x59050e5f
Thermal sensor with ratio = 185
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 256K log 'log_main'
logger: created 256K log 'log_events'
logger: created 256K log 'log_radio'
logger: created 256K log 'log_system'
usbcore: registered new interface driver snd-usb-audio
mmc0: new high speed DDR MMC card at address 0001
mmcblk0: mmc0:0001 SEM04G 3.68 GiB
mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
 mmcblk0: p1 p2 p3 < p5 p6 p7 p8 > p4
 mmcblk0boot1: unknown partition table
 mmcblk0boot0: unknown partition table
wm8962 0-001a: customer id 0 revision D
input: WM8962 Beep Generator as /devices/platform/imx-i2c.0/i2c-0/0-001a/input/input4
asoc: wm8962 <-> imx-ssi.1 mapping ok
input: wm8962-audio DMIC as /devices/platform/soc-audio.5/sound/card0/input5
input: wm8962-audio Headphone Jack as /devices/platform/soc-audio.5/sound/card0/input6
ALSA device list:
  #0: wm8962-audio
oprofile: using arm/armv7-ca9
GACT probability NOT on
Mirror/redirect action on
u32 classifier
    Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (12822 buckets, 51288 max)
ctnetlink v0.93: registering with nfnetlink.
NF_TPROXY: Transparent proxy support initialized, version 4.1.0
ehci_fsl_bus_suspend begins, Host 1 -- bypassed
NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
xt_time: kernel timezone is -0000
IPv4 over IPv4 tunneling driver
GRE over IPv4 demultiplexor driver
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 10
Mobile IPv6
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
L2TP core driver, V2.0
PPPoL2TP kernel driver, V2.0
L2TP IP encapsulation support (L2TPv3)
L2TP netlink interface
L2TP ethernet pseudowire support (L2TPv3)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'WEP'
lib80211_crypt: registered algorithm 'CCMP'
lib80211_crypt: registered algorithm 'TKIP'
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
DVFS driver module loaded
regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on
regulator_init_complete: PFUZE100_VGEN3: incomplete constraints, leaving on
regulator_init_complete: PFUZE100_VGEN2: incomplete constraints, leaving on
regulator_init_complete: PFUZE100_VGEN1: incomplete constraints, leaving on
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:09:00 UTC (540)
Freeing init memory: 240K
init: untracked pid 2312 exited
init: cannot find '/system/bin/ingsvcd', disabling 'ing'
android_usb: already disabled
root@edison_dvt:/ # init: untracked pid 2320 exited
init: untracked pid 2385 exited
EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p5): re-mounted. Opts: (null)
EXT4-fs (mmcblk0p5): re-mounted. Opts: (null)
PM: Syncing filesystems ...

U-Boot 2009.08-00171-gb9851cb-dirty (Oct 17 2014 - 14:39:59)

CPU: Freescale i.MX6 family TO1.2 at 792 MHz
Thermal sensor with ratio = 185
Temperature:   47 C, calibration data 0x59050e5f
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 99000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
nfc clock     : 24000000Hz
Board: i.MX6DL/Solo-SABRESD: unknown-board Board: 0x61012 [POR ]
Boot Device: MMC
I2C:   ready
DRAM:   1 GB
*** Warning - bad CRC or MMC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   got MAC address from IIM: 00:00:00:00:00:00
Hit any key to stop autoboot:  0

TLDR: My Relay got corrupted. I think the new(ish) version of Chrome or Google App did it. Anyone else see something similar?

My original Wink Relay which I set up early last year somehow got corrupted. I was able to restore it from the factory wipe/restore and it ran again for a week or so but same thing happened (would freeze or hang on boot). After restoring it another couple of times, eventually I was not able to get Android up and running anymore (hangs in boot; I can bring up the factory menu and do a wipe or wipe/restore which then hangs again on subsequent reboot).

I assumed it had some kind of hardware problem so I used my $29 Black Friday special spare Relay as a replacement; setting it up like the first one (non-rooted; installed Firefox, Chrome, StartupManager free, APKPure app, etc.) Used it mainly just to run ActionTiles on Chrome-- not through Firefox, though it was installed as well); also installed the Google app (which accepts voice input), just to play with it. The version of Chrome which APKPure installed was 65.0.3325.109 which I had run for a while on my previous Relay as well before it failed. This is a much more recent version of Chrome than I was using initially (prior to last fall or so, the only version that seemed to run on Android 4.3 was one of the earliest builds that was on APKpure. Back then, my attempts to install a more recent one would fail with an ‘incompatible on this device’ message. I thought it was interesting that the APKPure app was able to automatically (and apparently successfully) by default offer up and install the more recent build.

So fast forward a few weeks, and my new Relay has now begun acting like the previous one-- hanging, requiring a wipe cache/factory reset to get it going again for a week or so, then hanging again. Ultimately it wouldn’t even completely startup-- it hung as soon as the Chrome browser appeared. I tried unsuccessfully to get into StartupManager to deselect Chrome before it could start but was unable to do so.

It then occurs to me that a Wink Relay I had set up for a buddy months ago has been running perfectly for the last six months. I set it up the same way as mine but I did not install the most recent version of Chrome, nor the Google app; in fact I think I left it running ActionTiles on Firefox. (One other difference with my install; I use Bluetooth and the Amazon Music app so i can pipe music to my receiver’s speakers. That may prove to be a key difference but right now I’m suspecting Chrome because it was the app on the screen when the Relay hung).

So I fully wiped/reset the factory image on the Relay and this time did not install Chrome at all, or any Google app. I did my normal mode of installation, which is to only allow the first initial Wink update after login (to get into the Wink App to set options and get the proximity sensor going) and never accept any subsequent Wink updates. I’ve found if you do this, the Wink app never pops up into the foreground (I have no Wink hardware but do use Alexa voice control via Wink so I can have voice control of the built-in switches). So far so good; the Wink Relay has stayed operational for a few days now.

I’ve read a few posts from people that have had their Relays stuck in boot loops; just wondering if anyone has noticed a correlation with that and the installation of a recent Chrome build or Google app.

1 Like

I have google chrome installed on two wink relays (I’m not sure which version) but I only installed the Google app on one of them, and I have been having issues with that particular one. You might be right about the Google app messing with the Relays. At this point it will just randomly freeze, restart and anything installed/changed before it freezes just disappears, trying factory reset doesn’t work anymore

Hi I have a new version wink-projectone-release.apk You can modify it ?

Anyone have the compatible version of the fully browser? I haven’t been able to find one that works with the wink relay

Did anyone figure out how to unbrick their wink relay? Mine is stuck with the “signature verification failed” as well. Im going crazy over here trying to figure out how exactly to fix it. I called wink and they were no help at all and refused to send me a new one as I no longer have my receipt. (But they told me they can verify that it was brand new and never attached to any other account?). Extremely disappointed as the relay is exactly what I have wanted. Any pointers would be great! Also is there ANY way to connect to the relay without a USB cable? I have read from a few posts that people were connecting via wifi? @Synthesis don’t know if you have any pointers?

I set my Wink Relays to the side for now. Working through some major issues at work with a promotion I’m a bit unsure about (the reasons behind it, not receiving or accepting it), and some personal health issues that had me in the hospital recently. I’ll get back on this in the near future.