Wyze Cam - Usable with Blue Iris?

(see post 60, on page 2.)
Now if i see the cam local ip in my Asus Wireless router that means the id and pass enter in config/wpa_supplicant are correct?

As i am looking at the "key_mgmt=WPA-PSK" and my network has this:

2802k5d.jpg


As for the camera logs with the openip firmware this is what i have:

Network info:

Information:
Interfaces:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.1.153 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3832 errors:0 dropped:224 overruns:0 frame:0
TX packets:1363 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:696988 (680.6 KiB) TX bytes:220400 (215.2 KiB)
wlan0 IEEE 802.11bgn ESSID:"WIFI NAME" Nickname:""
Mode:Managed Frequency:2.457 GHz Access Point: XX:XX:XX:XX:XX:XX
Bit Rate:72.2 Mb/s Sensitivity:0/0
Retry:eek:ff RTS thr:eek:ff Fragment thr:eek:ff
Encryption key:****-****-****-****-****-****-****-**** Security mode:eek:pen
Power Management:eek:ff
Link Quality=91/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Routes:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default router.asus.com 0.0.0.0 UG 0 0 0 wlan0
192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0
DNS:
nameserver 192.168.1.1 # wlan0
Contents of logcat
D/IMP-ISP ( 211): ~~~~~~ IMP_ISP_Open[120] ~~~~~~~
E/IMP-ISP ( 211): VIDIOC_REGISTER_SENSOR(jxf22) error!

Contents of dmesg

Code: 
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.14 (root@ubuntu) (gcc version 4.7.2 (Ingenic r2.3.3 2016.12) ) #21 PREEMPT Thu Oct 19 11:38:16 CST 2017
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 RESET ERROR PC:BB100105
[    0.000000] CPU0 revision is: 00d00101 (Ingenic Xburst)
[    0.000000] FPU revision is: 00b70000
[    0.000000] cgu_get_rate, parent = 860160000, rate = 0, m = 0, n = 0, reg val = 0x000020ff
[    0.000000] CCLK:860MHz L2CLK:430Mhz H0CLK:200MHz H2CLK:200Mhz PCLK:100Mhz
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 00535000 @ 00010000 (usable)
[    0.000000]  memory: 0003b000 @ 00545000 (usable after init)
[    0.000000] User-defined physical RAM map:
[    0.000000]  memory: 06800000 @ 00000000 (usable)
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x067fffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x067fffff]
[    0.000000] On node 0 totalpages: 26624
[    0.000000] free_area_init_node: node 0, pgdat 80541cb0, node_mem_map 81000000
[    0.000000]   Normal zone: 208 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 26624 pages, LIFO batch:7
[    0.000000] Primary instruction cache 32kB, 8-way, VIPT, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 8-way, VIPT, no aliases, linesize 32 bytes
[    0.000000] pls check processor_id[0x00d00101],sc_jz not support!
[    0.000000] MIPS secondary cache 128kB, 8-way, linesize 32 bytes.
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 26416
[    0.000000] Kernel command line: console=ttyS1,115200n8 mem=104M@0x0 ispmem=8M@0x6800000 rmem=16M@0x7000000 init=/linuxrc rootfstype=squashfs root=/dev/mtdblock2 rw mtdparts=jz_sfc:256k(boot),2048k(kernel),3392k(root),640k(driver),4736k(appfs),2048k(backupk),640k(backupd),2048k(backupa),256k(config),256k(para),-(flag)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 99300k/106496k available (4024k kernel code, 7196k reserved, 1304k data, 236k init, 0k highmem)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:418
[    0.000000] clockevents_config_and_register success.
[    0.000024] Calibrating delay loop... 858.52 BogoMIPS (lpj=4292608)
[    0.087753] pid_max: default: 32768 minimum: 301
[    0.092737] Mount-cache hash table entries: 512
[    0.097840] Initializing cgroup subsys debug
[    0.102101] Initializing cgroup subsys freezer
[    0.109176] regulator-dummy: no parameters
[    0.113464] NET: Registered protocol family 16
[    0.135468] bio: create slab  at 0
[    0.141796] jz-dma jz-dma: JZ SoC DMA initialized
[    0.147055] SCSI subsystem initialized
[    0.150987] usbcore: registered new interface driver usbfs
[    0.156560] usbcore: registered new interface driver hub
[    0.161994] usbcore: registered new device driver usb
[    0.167294] i2c-gpio i2c-gpio.1: using pins 57 (SDA) and 58 (SCL)
[    0.173504]  (null): set:249  hold:250 dev=100000000 h=500 l=500
[    0.179652] media: Linux media interface: v0.10
[    0.184204] Linux video capture interface: v2.00
[    0.191010] Switching to clocksource jz_clocksource
[    0.195965] cfg80211: Calling CRDA to update world regulatory domain
[    0.203041] jz-dwc2 jz-dwc2: cgu clk gate get error
[    0.207977] jz-dwc2 jz-dwc2: regulator vbus get error
[    0.213062] DWC IN OTG MODE
[    0.366312] sft id =========================off
[    0.370929] dwc2 dwc2: Keep PHY ON
[    0.374322] dwc2 dwc2: Using Buffer DMA mode
[    0.578465] dwc2 dwc2: Core Release: 3.00a
[    0.582588] dwc2 dwc2: DesignWare USB2.0 High-Speed Host Controller
[    0.588918] dwc2 dwc2: new USB bus registered, assigned bus number 1
[    0.596306] hub 1-0:1.0: USB hub found
[    0.600047] hub 1-0:1.0: 1 port detected
[    0.604208] dwc2 dwc2: DWC2 Host Initialized
[    0.608704] NET: Registered protocol family 2
[    0.613684] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[    0.620710] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.627190] TCP: Hash tables configured (established 1024 bind 1024)
[    0.633644] TCP: reno registered
[    0.636842] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.642797] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.649398] NET: Registered protocol family 1
[    0.654113] RPC: Registered named UNIX socket transport module.
[    0.660046] RPC: Registered udp transport module.
[    0.664882] RPC: Registered tcp transport module.
[    0.669582] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.676624] freq_udelay_jiffys[0].max_num = 10
[    0.681051] cpufreq     udelay     loops_per_jiffy 
[    0.685515] dwc2 dwc2: ID PIN CHANGED!
[    0.689295] init DWC as A_HOST
[    0.692400] 12000    59885    59885 
[    0.695621] 24000    119771    119771 
[    0.699063] 60000    299428    299428 
[    0.702619] 120000    598857    598857 
[    0.706075] 200000    998095    998095 
[    0.709607] 300000    1497142    1497142 
[    0.713421] 600000    2994285    2994285 
[    0.717053] 792000    3952457    3952457 
[    0.720761] 1008000    5030400    5030400 
[    0.724581] 1200000    5988571    5988571 
[    0.733955] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.740797] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.747397] msgmni has been set to 193
[    0.752627] io scheduler noop registered
[    0.756563] io scheduler cfq registered (default)
[    0.763240] jz-uart.1: ttyS1 at MMIO 0x10031000 (irq = 58) is a uart1
[    0.771430] console [ttyS1] enabled, bootconsole disabled
[    0.786647] brd: module loaded
[    0.791907] loop: module loaded
[    0.796185] zram: Created 2 device(s) ...
[    0.800423] logger: created 256K log 'log_main'
[    0.805835] jz SADC driver registeres over!
[    0.811148] jz TCU driver register completed
[    0.816243] the id code = 1c7018, the flash name is GD25LQ128C
[    0.822296] #####unsupport ID is 1c7018 if the id not be 0x00,the flash can be ok,but the quad mode may be not support!!!!!
[    1.033828] JZ SFC Controller for SFC channel 0 driver register
[    1.039995] 11 cmdlinepart partitions found on MTD device jz_sfc
[    1.046236] Creating 11 MTD partitions on "jz_sfc":
[    1.051296] 0x000000000000-0x000000040000 : "boot"
[    1.056845] 0x000000040000-0x000000240000 : "kernel"
[    1.062561] 0x000000240000-0x000000590000 : "root"
[    1.068063] 0x000000590000-0x000000630000 : "driver"
[    1.073814] 0x000000630000-0x000000ad0000 : "appfs"
[    1.079405] 0x000000ad0000-0x000000cd0000 : "backupk"
[    1.085240] 0x000000cd0000-0x000000d70000 : "backupd"
[    1.091025] 0x000000d70000-0x000000f70000 : "backupa"
[    1.096869] 0x000000f70000-0x000000fb0000 : "config"
[    1.102672] 0x000000fb0000-0x000000ff0000 : "para"
[    1.108216] 0x000000ff0000-0x000001000000 : "flag"
[    1.113761] SPI NOR MTD LOAD OK
[    1.117086] tun: Universal TUN/TAP device driver, 1.6
[    1.122320] tun: (C) 1999-2004 Max Krasnyansky
[    1.128904] usbcore: registered new interface driver zd1201
[    1.134755] usbcore: registered new interface driver r8152
[    1.140526] usbcore: registered new interface driver usb-storage
[    1.146898] usbcore: registered new interface driver usbserial
[    1.153018] usbcore: registered new interface driver usbserial_generic
[    1.159813] usbserial: USB Serial support registered for generic
[    1.166093] usbcore: registered new interface driver ch341
[    1.171819] usbserial: USB Serial support registered for ch341-uart
[    1.178373] usbcore: registered new interface driver cp210x
[    1.184195] usbserial: USB Serial support registered for cp210x
[    1.190373] usbcore: registered new interface driver pl2303
[    1.196196] usbserial: USB Serial support registered for pl2303
[    1.703388] i8042: i8042 controller selftest timeout
[    1.709024] jzmmc_v1.2 jzmmc_v1.2.0: vmmc regulator missing
[    1.752528] jzmmc_v1.2 jzmmc_v1.2.0: register success!
[    1.757920] jzmmc_v1.2 jzmmc_v1.2.1: vmmc regulator missing
[    1.795393] dwc2 dwc2:  ++OTG Interrupt: A-Device Timeout Change++
[    1.803450] jzmmc_v1.2 jzmmc_v1.2.1: register success!
[    1.808928] hidraw: raw HID events driver (C) Jiri Kosina
[    1.814815] usbcore: registered new interface driver usbhid
[    1.820591] usbhid: USB HID core driver
[    1.824678] Netfilter messages via NETLINK v0.30.
[    1.829610] nf_conntrack version 0.5.0 (1551 buckets, 6204 max)
[    1.836366] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.841981] TCP: cubic registered
[    1.845467] NET: Registered protocol family 17
[    1.851083] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    1.858324] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.870341] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    1.878148] Freeing unused kernel memory: 236K (80545000 - 80580000)
[    3.902414] jzmmc_v1.2 jzmmc_v1.2.0: card inserted, state=0
[    5.022336] wait stable.[246][cgu_msc0]
[    5.026439] mmc0: new high speed SDHC card at address 0d78
[    5.034813] mmcblk0: mmc0:0d78 SD04G 3.75 GiB
[    5.042567]  mmcblk0: p1
[    5.728875] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    6.884899] register all isp device successfully!
[    6.894343] @@@@ tx-isp-probe ok @@@@@
[    6.965515] exFAT: Version 1.2.9
[    6.977249] motor_probe743
[    7.014949] jz_codec_register: probe() successful!
[    7.021902] cgu_set_rate, parent = 860160000, rate = 2048000, n = 420, reg val = 0x000021a4
[    7.021922] cgu_enable,cgu_i2s reg val = 0x200021a4
[    7.362815] dma dma0chan24: Channel 24 have been requested.(phy id 7,type 0x06 desc a50b3000)
[    7.372072] dma dma0chan25: Channel 25 have been requested.(phy id 6,type 0x06 desc a4f4f000)
[    7.398028] jz_pwm_probe[198] d_name = tcu_chn0
[    7.413032] request pwm channel 0 successfully
[    7.421944] pwm-jz pwm-jz: jz_pwm_probe register ok !
[    7.782468] RTL871X: module init start
[    7.786365] RTL871X: rtl8189ftv v4.3.24.7_21113.20170208.nova.1.02
[    7.794689] RTL871X: build time: Jan 24 2018 14:43:26
[    7.799936] wlan power on
[    7.822831] RTL871X: module init ret=0
[    7.868409] mmc1: card claims to support voltages below the defined range. These will be ignored.
[    7.901715] mmc1: new SDIO card at address 0001
[    7.917712] RTL871X: ++++++++rtw_drv_init: vendor=0x024c device=0xf179 class=0x07
[    7.979518] RTL871X: HW EFUSE
[    7.992482] RTL871X: hal_com_config_channel_plan chplan:0x20
[    8.182002] RTL871X: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
[    8.212747] RTL871X: rtw_ndev_init(wlan0) if1 mac_addr=c8:02:8f:f8:65:ac
[   11.367081] RTL871X: rtw_set_802_11_connect(wlan0)  fw_state=0x00000008
[   11.462492] RTL871X: start auth
[   11.469142] RTL871X: auth success, start assoc
[   11.477530] RTL871X: assoc success
[   11.485443] RTL871X: recv eapol packet
[   11.498546] RTL871X: send eapol packet
[   11.511232] RTL871X: recv eapol packet
[   11.515902] RTL871X: send eapol packet
[   11.522611] RTL871X: set pairwise key camid:4, addr:ac:9e:17:49:23:88, kid:0, type:AES
[   11.534416] RTL871X: set group key camid:5, addr:ac:9e:17:49:23:88, kid:1, type:AES
[   15.572344] set sensor gpio as PA-low-10bit
[   15.578974] probe ok ------->jxf22
[   15.605043] -----jxf22_detect: 432 ret = 0, v = 0x0f
[   15.605460] -----jxf22_detect: 440 ret = 0, v = 0x23
[   15.605473] jxf22 0-0040: chip found @ 0x40 (i2c0) is not an jxf22 chip.
[   15.621141] do_page_fault() #2: sending SIGSEGV to v4l2rtspserver- for invalid read access from
[   15.621141] 00000000 (epc == 004c2cf8, ra == 0045b454)

Any idea what may cause the no video?
Thanks for advice.
P.
 
Last edited:
Got it to work in BI, just for testing only camera, curios George :)
Now looks that the night vision has a pinkish color,hmm...

14uyyq1.jpg
 
In the event someone comes across this thread as I did and is struggling with the fact that the custom firmware breaks the automated night mode I used the following solution. I have a batch file that sends three curl commands:

morning.bat
curl -u dafang:ismart12 http://192.168.1.420/cgi-bin/action.cgi?cmd=auto_night_mode_stop
curl -u dafang:ismart12 http://192.168.1.420/cgi-bin/api.cgi?action=ir_led_off
curl -u dafang:ismart12 http://192.168.1.420/cgi-bin/api.cgi?action=ir_cut_off

night.bat
curl -u dafang:ismart12 http://192.168.1.420/cgi-bin/action.cgi?cmd=auto_night_mode_stop
curl -u dafang:ismart12 http://192.168.1.420/cgi-bin/api.cgi?action=ir_led_on
curl -u dafang:ismart12 http://192.168.1.420/cgi-bin/api.cgi?action=ir_cut_on

If you've changed the username and password then you'd change the dafang:ismart12 (I've shown the default username/password here for reference) and you'll also need to customize the ip address. This obviously assumes that you have curl installed on your system. I just have Windows run the batch files in the morning/evening but you could also schedule BlueIris to do it as a scheduled PTZ command.

For reference, the first turns auto night mode off. I have it run every time because if the camera resets it turns it back on. If you don't do this the camera will turn the led back off on its own. The second turns the ir leds on/off and the third turns the ir filter on/off. If anyone has a better way to do this or suggestions on how to improve this solution I'd love to hear them.
 
  • Like
Reactions: aesterling
Just an update from my testing. The Wi-Fi in the custom open firmware is not as good as the Wi-Fi in the default proprietary firmware. Because I have these cameras installed outside, and they go through brick walls, they don’t have enough bandwidth to do proper streaming video. What I have done is configured blue Iris to connect to the JPEG stream once per second. They also get strange color glitches every few seconds. However, in the current set up, I have had them running this way for a few months with no more tweaking, and they have been mostly hassle free. Unless I can tweak these to operate better, I would not buy them again, unless I could get them with a wired ethernet connection. I have three of them.
 
LBJ said:
These things are $15 shipped today on AMZN. I agree they are junk, but I ordered one so I can learn about how to update it to the open source firmware / software etc.
My expectations are low, and I won't use it for any mission critical tasks.

My guess is they are closing them out since they are so cheap, but I may be wrong.
Click to expand...

And I got ripped off. Order never arrived and I had to get a refund from Amazon. What a total scam. Dozens of similar complaints with the seller I used.

I've moved on to better cameras. Not going to bother.
 
Last edited:
MatthewNinety said:
Just an update from my testing. The Wi-Fi in the custom open firmware is not as good as the Wi-Fi in the default proprietary firmware. Because I have these cameras installed outside, and they go through brick walls, they don’t have enough bandwidth to do proper streaming video. What I have done is configured blue Iris to connect to the JPEG stream once per second. They also get strange color glitches every few seconds. However, in the current set up, I have had them running this way for a few months with no more tweaking, and they have been mostly hassle free. Unless I can tweak these to operate better, I would not buy them again, unless I could get them with a wired ethernet connection. I have three of them.
Click to expand...
How did you do that in BI?

Sent from my SM-G955U using Tapatalk
 
HI There,

I came a cross a youtube video yesterday showing that Wyze have released a Beta version of Firmware that will allow RTSP streams without the need for the custom firmware hack. Which in theory means we could add them too Blue Iris.

I tried one of these about 6 months ago with the Dafang hack and the quality was horrible compared to my 4 Amcrest cameras. My father-in-law has 3 of the Wyzecam V2's and a Wyze Cam Pan. With the original firmware the quality of the streams is actually quite good.

Has anyone tried this new firmware from Wyze? Maybe I'll have to try and convince my father-in-law let me try one of his cameras lol
 
Richdem said:
HI There,

I came a cross a youtube video yesterday showing that Wyze have released a Beta version of Firmware that will allow RTSP streams without the need for the custom firmware hack. Which in theory means we could add them too Blue Iris.

I tried one of these about 6 months ago with the Dafang hack and the quality was horrible compared to my 4 Amcrest cameras. My father-in-law has 3 of the Wyzecam V2's and a Wyze Cam Pan. With the original firmware the quality of the streams is actually quite good.

Has anyone tried this new firmware from Wyze? Maybe I'll have to try and convince my father-in-law let me try one of his cameras lol
Click to expand...
yeah the quality is fine too issue that I've had with wife cams and blue iris is the concert dropout because the Wi-Fi simply isn't good

Sent from my SM-G955U using Tapatalk
 
Richdem said:
HI There,

I came a cross a youtube video yesterday showing that Wyze have released a Beta version of Firmware that will allow RTSP streams without the need for the custom firmware hack. Which in theory means we could add them too Blue Iris.

I tried one of these about 6 months ago with the Dafang hack and the quality was horrible compared to my 4 Amcrest cameras. My father-in-law has 3 of the Wyzecam V2's and a Wyze Cam Pan. With the original firmware the quality of the streams is actually quite good.

Has anyone tried this new firmware from Wyze? Maybe I'll have to try and convince my father-in-law let me try one of his cameras lol
Click to expand...

Just tried this. Works slightly better than custom firmware (No strange colors, decent image quality, wifi isn't weaker), but for some reason there are frequent connectivity drops right now. Not quite stable just yet. Similar to what other people are describing here:

Having trouble with RTSP firmware
 
Benak said:
There is a link here:

Wyze Cam RTSP

Works with v2 only or Pan - I have v2 and will attempt to get this in operation with BI tonight.
Click to expand...

I wasn't able to get the beta firmware to flash last night after screwing with the camera for 45 minutes +/-

Has anyone else had issues flashing this firmware? I'll probably try again on the weekend.

Currently have firmware rev 4.19.4.48 installed. I've seen some rumbling on other forums about this being sensitive to micro SD card size, formatted to FAT32, etc. Does anyone have any specific knowledge or experience with this?
 
Benak said:
I wasn't able to get the beta firmware to flash last night after screwing with the camera for 45 minutes +/-

Has anyone else had issues flashing this firmware? I'll probably try again on the weekend.

Currently have firmware rev 4.19.4.48 installed. I've seen some rumbling on other forums about this being sensitive to micro SD card size, formatted to FAT32, etc. Does anyone have any specific knowledge or experience with this?
Click to expand...
This is what I did

Put the files on the SD card insert the SD card in run the setup when the camera reboots and starts flashing yellow remove the SD card run setup again and then insert the SD card and it should work.

Sent from my SM-G955U using Tapatalk
 
Bboy486 said:
This is what I did

Put the files on the SD card insert the SD card in run the setup when the camera reboots and starts flashing yellow remove the SD card run setup again and then insert the SD card and it should work.

Sent from my SM-G955U using Tapatalk
Click to expand...

Thanks for the feedback bboy. The way I read the instructions was that you needed to have the camera paired/synced in the Wyze app before attempting to flash the new beta firmware. I think you're saying you paired the camera in the Wyze app at the same time as flashing the new firmware? I'll give that a shot.
 
Benak said:
Thanks for the feedback bboy. The way I read the instructions was that you needed to have the camera paired/synced in the Wyze app before attempting to flash the new beta firmware. I think you're saying you paired the camera in the Wyze app at the same time as flashing the new firmware? I'll give that a shot.
Click to expand...
Sort of. I followed the instructions but when I rebooted the led just flashed yellow. I then removed the SD card. Re-booted and paired in the app and put the sd card back and it was running the beta

Sent from my SM-G955U using Tapatalk
 
You must log in or register to reply here.
Top Bottom