New post
0

PC Viewer v1.18 crashing consistently (5 sec of DR750S-2CH-E playback followed by crash)

I just installed my new DR750S-2CH-E cameras.
I'm using the PC Viewer v1.18 on HP Z800 Worstation, Win 10Pro 64-bit.
The program crashes consistently after about 5sec of playing back my DR750S-2CH-E footage.

My footage is set in Firmware to 'Sports' mode, with 60fps FHD front and 30fps FHD Rear.
The quality selected in Firmware is 'ighest (Sports)'.

I tried the following, none of which fixes the problem :

- Run the program in 'Administrator Mode'
- Changed program 'Compatibility Mode' to various earlier Windows versions.
- Copied files from micro SD card to an internal SSD drive and attempted playback from there.

Further observations :

- The card was formatted in the camera

- I get about 5 seconds of playback _only_ when the player plays back from a folder which contains _both_ Front and Rear camera files.

- When separating the front and rear camera files, and pointing the player to a folder containing just Front or just Rear camera files the behaviour is even worse : there's only 1 sec of playback _sometimes_ and no playback at all (blank screen) on other occasions, followed by a crash.

- I tried to clicking on the 'Screen Mode Settings' button on the bottom of video viewer but it does nothing before and/or after starting playback for the first time.

- Weirdly, when in 'Settings -> Firmware -> Sensitivity -> Advanced Settings' I can select and play any Front or Rear cam video, whilst the Gyro graphs are playing along with no problems. Of course this is no substitute for the viewer and curious nevertheless. You go figure ...

This is a disappointing start to my relationship with BlackVue :(

Please advise on things I can do/try to remedy the situation.

Thanks.

========

BlackVue PC Viewer v1.18
DR750S-2CH-E firmware v1.005
I can't attach my system info here, apparently, but can email it to you on request.

 

28 comments

  • 0
    Avatar
    Smithb

    I'm getting crashing in 1.18 too. I'm thinking of going back to 1.17. I'm running a 650S-2CH, so it's probably not related to the footage itself.

  • 0
    Avatar
    Martin Ograbek

    Reverting the PC player to v1.16 has brought back the ability to turn off the option 'use video accelerator' in the program settings.
    That option has been removed from v1.18 with the 'video accelerator' apparently left permanently on, leading to instant crashes.

    Although the program crashes are gone when running v1.16 with the 'use video accelerator' option disabled, the playback randomly slows down to a crawl :(

    That's poor software engineering, BlackVue !

    Also : on the subject of reverting to previous software versions in case of trouble :

    BlackVue aren't helpful here and make it frustratingly hard to do.

    There's no online library of software revisions, like other caring and sensible companies do, and tech support over email takes more than a week to receive a response.

    I needed both camera firmware and the PC player downgrades and the only place on the planet I was able to find them was on an obscure Russian tech forum.

    Ridiculous, but at least that way I've sorted all my problems myself days before the tech support got back to me.

    Boo !

  • 0
    Avatar
    Smithb

    Yeah, I now archive the Zips for all old versions for that very reason.

    The other irritant is if you just run an old Setup, it'll go through without any error indication, but not actually replace the files. Since it's difficult to see the version you're running from inside the app, that could get confusing. You need to uninstall and then reinstall.

    Did Tech Support ever actually get back to you on this? Any confirmation of plans to fix?

    I think the slow playback is because it's not buffering as much of the file, and if the file reading is a bit slow it'll lag. I'm doing playback from a hard drive I archive all videos to, and it gets horribly fragmented (plus it's not an especially fast drive to begin with), and I can hear it hunting as it's reading the file A defrag fixes that (for a while), and eventually I'll swap in a faster drive (maybe even an SSD).

  • 0
    Avatar
    famcorlettheinze

    Pretty similar situation here. Brand new DR750S-2CH (v1.005), and after running DR650GW-2CH without problems for over a year, viewer (v1.18) front and rear camera views not in sync, playback judders and keeps slowing down and now it's started crashing after a few seconds. Very disappointed that Blackvue don't even acknowledge that the problem exists and that they’re working on a resolution.

     

     

  • 0
    Avatar
    Noman

    Dear Customers

    Please accept our sincere apologies for the inconvenience.

    Can you please tell us your computer specifications: OS, Processor, RAM and GPU for our engineers to analyse what's causing the error on the specific computers?

    Due to the new viewer being made compatible to run 4K video files, it might require more processing power causing the playback to be slow or resulting in a crash. 

    Also, if you have already contacted our customer support department, please let us know your ticket numbers so that we can check it coherently and come up with a

    possible  resolution.

    Thank you for your patience and understanding.

  • 0
    Avatar
    famcorlettheinze

    Hi Noman, see below the system I'm running. I don't think it's short on processing power. I'm away from home at the present and was going to reload all the Blackvue software at the weekend and give it another try. Note: I'm using original Blackvue microSD cards 128GB and 64GB

    OS: Windows 10 (up to date)

    CPU: Intel Core i7-8700K (3.70GHz / 12MB)

    RAM: HyperX Fury DDR4 16GB (4x4GB) 2400MHz

    GPU: Nvidia GeForce GTX 1050 Ti 4GT LP

    The frustraion for me is that I'm alo gettng similar symptoms,with the exception of the crash, on the other computer we have. This unit has worked fine on all previous revisions of the software with both the DR750S-2CH and the DR650GW-2CH from my wifes auto.

    OS: Windows 10 (upto date)

    CPU: IntlCore i7-870 (2.93GHz / 8MB)

    RAM: DDR4 (4x1GB)

    GPU: Nvidia GeForce GT 640

     Very Best Regards,

    RON

  • 0
    Avatar
    Smithb

    I haven't logged a ticket. System is an Intel i7 processor, 16GB RAM running Windows 10 Fall Creators. GPU is an nVidia GeForce GTX 1050 driving three 1080p monitors. I am not attempting to view 4k videos. The dashcam itself is a 650S. All my video files have been offloaded to a local hard drive.

    I will attempt to log a ticket with more data, plus my contact info. I'm a software developer myself, so I could run Debug builds or whatever if that's helpful.

  • 0
    Avatar
    Noman

    Dear Customers
    In able for us to further determine the crashing issue, please send us the Blackvue folder on your computer. 
    (Documents--> Blackvue)

    You may send setup ini, trace cld and trace sd for us to further analyze it.

    Thank you. 

  • 0
    Avatar
    famcorlettheinze

    Hi Folks, quick update now I've been able to get in front of the computer. I downloaded the latest software PC Viewer v1.19 and it has resolved all the problems I was experiencing on the i7-870 rig. Not too sure if it was the v1.18 software that was causing the problem but sine the reload an a restart it's now sorted.

    I also found that the GTX 1050 GPU on the other set-up was not running as it should and I have gone back to the vendor for a replacement. With the GPU removed it still exhibits the same symptoms as befoe, so the idea that the 4K video files might be too heavy for the motherboard GPU seems logical. Will update you when I get the replacement GPU installed. When I'm back at the computer I'll pull the trace files before I install the GPU or I upgrade this one to v1.19

  • 0
    Avatar
    Smithb

    1.19 crashes for me same as before. I'll be e-mailing the requested files to cs@ in a short while, but they're short:

    setup.ini:
    [setup]
    filepath=B:\Blackvue\VE3BSM\Record
    accelerator=0

    trace_cld.txt:
    [CCldMapDlg::HttpRes(588)] gps failed message[12017]

    trace_sd.txt:
    [CDrawWnd::Decode(231)] Video Decoding receive Failed. B:\Blackvue\VE3BSM\Record\20180507_220813_NF.mp4
    ... multiples of these, all identical except the file name, and 8 copies of the same file name in a row (retrying?)

    I'm not playing 4k files at all, so that's not going to be a factor, at least directly. The more likely scenario is the video player library (ffmpeg?) was upgraded for 4k support, and that library has a problem (not specific to 4k).

  • 0
    Avatar
    famcorlettheinze

    Okay the replacement New GPU (Nvidia GTX 1050 Ti) installed and still getting the crash. Replaced the viewer with version 1.17 and everything is working fine (no crash) but still miss timing between front and rear images.

    However after some more fiddling around with files and software and found the most stable set-up was as follows:

    Camera DR750S-2CH v1.005 Set to: FHD@60+FHD@30(sports)

    Enhanced Night Vision = On (Parking Mode Only)

    MSD-64

    Viewer v1.15

    Now all working as should.

    Note: doesn't make any difference to results if the data is read direct from the Micro SD card via card reader, or if data is read via the Blackvue Micro SD adaptor through a USB, or if the data is downloaded to the (C:) drive and read direct from there.

  • 0
    Avatar
    John Chase

    I am experiencing the same problems as above. Video seeks, starts to run then Blackvue Viewer 1.19 crashes. I have tried reading the HVEC 265 from the SD card and the hard drive.

    The files with play in both Windows "Movie & TV" and "Photo". I have recorded some files in 264, but have yet to try them with Blackvue Viewer 1.19.

    Everything is fully upgraded including the latest Windows 10 1803 and video drivers for NVidia GTX 1080 Founders Edition x 2.

    Diagnostic information follows:

    OS Name Microsoft Windows 10 Home
    Version 10.0.17134 Build 17134
    OS Manufacturer Microsoft Corporation
    System Manufacturer ASUS
    System Model All Series
    System Type x64-based PC
    System SKU All
    Processor Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz, 3601 Mhz, 6 Core(s), 12 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. 1802, 9/5/2017
    SMBIOS Version 3.0
    Embedded Controller Version 255.255
    BIOS Mode Legacy
    BaseBoard Manufacturer ASUSTeK COMPUTER INC.
    BaseBoard Model Not Available
    BaseBoard Name Base Board
    Platform Role Desktop
    Secure Boot State Unsupported
    PCR7 Configuration Binding Not Possible
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume1
    Locale United States
    Hardware Abstraction Layer Version = "10.0.17134.1"
    Installed Physical Memory (RAM) 128 GB
    Total Physical Memory 128 GB
    Available Physical Memory 121 GB
    Total Virtual Memory 147 GB
    Available Virtual Memory 136 GB
    Page File Space 19.0 GB
    Page File C:\pagefile.sys
    Kernel DMA Protection Off
    Virtualization-based security Not enabled
    Hyper-V - VM Monitor Mode Extensions Yes
    Hyper-V - Second Level Address Translation Extensions Yes
    Hyper-V - Virtualization Enabled in Firmware No
    Hyper-V - Data Execution Protection Yes

    Video Codecs:

    c:\windows\system32\cfhd.dll CineForm Inc. CineForm HD VFW Codec OK C:\WINDOWS\system32\CFHD.DLL 9.2.1.690 1.27 MB (1,334,784 bytes) 12/2/2016 02:54
    c:\windows\system32\iyuv_32.dll Microsoft Corporation OK C:\WINDOWS\system32\IYUV_32.DLL 10.0.17134.1 52.50 KB (53,760 bytes) 4/11/2018 17:34
    c:\windows\system32\msrle32.dll Microsoft Corporation OK C:\WINDOWS\system32\MSRLE32.DLL 10.0.17134.1 17.50 KB (17,920 bytes) 4/11/2018 17:34
    c:\windows\system32\msvidc32.dll Microsoft Corporation OK C:\WINDOWS\system32\MSVIDC32.DLL 10.0.17134.1 38.50 KB (39,424 bytes) 4/11/2018 17:34
    c:\windows\system32\msyuv.dll Microsoft Corporation OK C:\WINDOWS\system32\MSYUV.DLL 10.0.17134.1 27.50 KB (28,160 bytes) 4/11/2018 17:34
    c:\windows\system32\tsbyuv.dll Microsoft Corporation OK C:\WINDOWS\system32\TSBYUV.DLL 10.0.17134.1 16.50 KB (16,896 bytes) 4/11/2018 17:34

    Video:

    Name NVIDIA GeForce GTX 1080
    PNP Device ID PCI\VEN_10DE&DEV_1B80&SUBSYS_119E10DE&REV_A1\4&FC7F53B&0&0018
    Adapter Type GeForce GTX 1080, NVIDIA compatible
    Adapter Description NVIDIA GeForce GTX 1080
    Adapter RAM (1,048,576) bytes
    Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll
    Driver Version 23.21.13.8859
    INF File oem52.inf (Section136 section)
    Color Planes Not Available
    Color Table Entries 4294967296
    Resolution 3840 x 2160 x 59 hertz
    Bits/Pixel 32
    Memory Address 0xFA000000-0xFB0FFFFF
    Memory Address 0xC0000000-0xD1FFFFFF
    Memory Address 0xD0000000-0xD1FFFFFF
    I/O Port 0x0000E000-0x0000EFFF
    IRQ Channel IRQ 40
    I/O Port 0x000003B0-0x000003BB
    I/O Port 0x000003C0-0x000003DF
    Memory Address 0xA0000-0xBFFFF
    Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvlddmkm.sys (23.21.13.8859, 16.24 MB (17,025,992 bytes), 12/9/2017 16:07)

    Name NVIDIA GeForce GTX 1080
    PNP Device ID PCI\VEN_10DE&DEV_1B80&SUBSYS_119E10DE&REV_A1\4&16866DE7&0&0010
    Adapter Type GeForce GTX 1080, NVIDIA compatible
    Adapter Description NVIDIA GeForce GTX 1080
    Adapter RAM (1,048,576) bytes
    Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll
    Driver Version 23.21.13.8859
    INF File oem52.inf (Section136 section)
    Color Planes Not Available
    Color Table Entries 4294967296
    Resolution 3840 x 2160 x 59 hertz
    Bits/Pixel 32
    Memory Address 0xF8000000-0xF8FFFFFF
    Memory Address 0xA0000000-0xAFFFFFFF
    Memory Address 0xB0000000-0xB1FFFFFF
    IRQ Channel IRQ 32
    Driver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvlddmkm.sys (23.21.13.8859, 16.24 MB (17,025,992 bytes), 12/9/2017 16:07)

    Blackvue setup.ini

    [setup]
    speedunit=1
    filepath=E:\Recordings\2018 05 26

    trace_cld.txt

    [WHttpProc(115)] WinHttpSendRequest Error(12017)
    [CCldMapDlg::HttpRes(587)] gps failed message[12017]
    [CCldMapDlg::HttpRes(587)] gps failed message[12017]
    [WHttpProc(115)] WinHttpSendRequest Error(12017)
    [CCldMapDlg::HttpRes(587)] gps failed message[12017]

    trace_sd.txt

    [CDrawWnd::Decode(231)] Video Decoding receive Failed. E:\Recordings\2018 05 26\20180526_155114_NF.mp4
    [CDrawWnd::Decode(231)] Video Decoding receive Failed. E:\Recordings\2018 05 26\20180526_155114_NF.mp4
    [CDrawWnd::Decode(231)] Video Decoding receive Failed. E:\Recordings\2018 05 26\20180526_155114_NF.mp4
    [CDrawWnd::Decode(231)] Video Decoding receive Failed. E:\Recordings\2018 05 26\20180526_155114_NF.mp4

    I hope that helps...I am willing to run beta for you. I want to get this issue resolved.

    Thank you!

  • 0
    Avatar
    John Chase

    Some additional troubleshooting information.

    I switched to the cloud player which allowed me to play one video segment from my hard drive. Unlike the viewer the front and back do not play at the same time.

    However, after one segment is played if I try to play another segment the viewer (1.19) crashes.

    I suspect there is a problem with playing more than one video at a time with the viewer. Obviously from the system information above I should have no problem playing multiple videos at the same time. In fact using MS Photo I have played both the front and back videos simultaneously.

    I also learned that NVidia has had the hardware capacity for HEVC 265 since GTX 960.

    I again include the trace_cld.txt content. The trace_sd.txt is emply. The Blackvue setup.ini has not changed.

    [WHttpProc(115)] WinHttpSendRequest Error(12017)
    [CCldMapDlg::HttpRes(587)] gps failed message[12017]
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4
    [CDispWnd::Decode(622)] Video Decoding Failed. E:/Recordings/2018 05 26 b/20180526_181753_NF.mp4

    Let me know how I can be of assistance solving this problem.

     

  • 0
    Avatar
    Noman

    Dear Customers

    We thank you for your patience. 

    Our research team has developed a new beta version which might be a fix to crash issue. First of all please delete already installed viewer from your computer and download and install the new version from the following link and see if it solves the crashing issue.

    https://drive.google.com/drive/folders/1wA-5VhQbOpRyQDnFUCOWn0wRLJJSUjQK?usp=sharing 

    Thank you 

  • 0
    Avatar
    Smithb

    Good news, I've put this new build through its paces, and it's much better. I've viewed long stretches of recordings with the previous crashing problem not occurring.

    I did find a couple of files that do crash the Viewer. But I'm pretty sure this isn't related to the previous problem because, unlike before, I can consistently crash on the same files every time (previously it was random). I've isolated a couple of the files (that play fine in VLC) and I'll report this and send those files separately.

    But as far as the crash problem discussed in this thread, I think you nailed it.

    Brad.

  • 0
    Avatar
    Smithb

    Drat. Still crashing. But differently now. I don't get any unhandled exception errors like before. The app just "goes away". Always right at the beginning of playing a clip. But it's not consistent. Sometimes it'll work for a while, sometimes barf on the very first clip. :-(

    And, again, I have debugging tools here. I can reproduce, I can debug. A bit of trust from the development team and I could probably have pointed to the exact line of code months ago. :-)

  • 0
    Avatar
    famcorlettheinze

     

    Hi Noman, tried loading the beta version and I’m still getting the crash of the program after a few seconds. Cleaned the program from the computer and starting at version 1.14 tried each version until the system started failing again. Got up to version 1.18 and started getting the shutdown once more. Did a clean installation of version 1.17 and all seems okay. Note: if I select “use video accelerator” in the viewer settings I once again experience the crash with version 1.17. If I deselect the video accelerator option everything runs fine.

     

    I hope this helps.

     

    Best Regards,

     

    RON

     

  • 0
    Avatar
    Noman

    Dear Customers

     Please try the following and see if the viewer still crashes.

    IF you are using a two channel camera, please turn off the rear video (refer to the attached screenshot) and just play the front video.

    Please let us know if the viewer still crashes or not so that we can find out what is the error and fix it.

     

    Thank you 

  • 0
    Avatar
    Smithb

    So you may be on to something. I ran for over half an hour (at 4x speed) with only the front camera selected, with no crash. I also ran for a while with only the rear camera selected, with no crash. Reset to both cameras, and crashed within 10 minutes.

    Brad.

  • 0
    Avatar
    David

    My version v1.20 won't stay open long enough for me to disable picture-in-picture/dual view display.  I try and deselect but the application crashes before it registers the mode change request.

    Very frustrating.

  • 0
    Avatar
    Noman

    Dear Customers

    Please try to download and  install the below test version of new Windows viewer and see if it fixes the issue.

    https://drive.google.com/drive/folders/0Bx0Zv57VYSRAVHd5cEwxU2tlNE0   

    Thank you 

  • 0
    Avatar
    Smithb

    I've done a couple of sessions of playing hours of recordings, acceleration enabled, Front & Rear enabled, 4x speed, both long stretched and random file selection, and no crashes at all. I think you finally nailed it. :-)

    Brad.

  • 0
    Avatar
    famcorlettheinze

    Hi Noman, tried downloading the (https://drive.google.com/drive/folders/0Bx0Zv57VYSRAVHd5cEwxU2tlNE0 ) fix and keep getting the Error 400 (not found)!! message.

    Best Regards,

    RON

  • 0
    Avatar
    Smithb

    The link got a couple of extra characters added to the end. Try https://drive.google.com/drive/folders/0Bx0Zv57VYSRAVHd5cEwxU2tlNE0

    (delete the %C2%AO from the end of the original link)

  • 0
    Avatar
    famcorlettheinze

    Okay Smithb I managed to download the file. Thanks for the help.

    I've been running this version for a few hours now and all seems okay on both of the systems I have here. No more crashes now and all seems pretty stable. However there is still a sync issue between the front and rear camera. Sometimes, not always, there is a half second difference between the two video streams. I can live with that as I'm only using the app to quickly review and sort the data from the microSD card before downloading the files for editing on another program.

  • 0
    Avatar
    famcorlettheinze

    Just an update on the current situation. Downloaded both firmware 1.011-DR750S-2CH-E and the Viewer, Version2.01x64 yesterday. I must say it's rock solid and everything is working great. I'm also sure that the playback picture quality from both front and rear cameras has improved greatly. This also goes for the firmware 2.008-DR650GW-2CH-EN

    Noman, tell the programmers they got it sorted this time. Great Job. Thanks.

  • 0
    Avatar
    Martin Ograbek

    To the contrary here.

    BlackVue client software continues to be an utter waste of my time and an embarrassment to the company.

    v2.01 player crashes after merely moving the playhead when playing back a single file (say, front cam) or initiating the playback of a second piece of video.
    Specifically - it just bombs off the screen with no notifications.

    I can't speak for v1.011 firmware as yet.
    After installing it and updating the Android viewer app to v2.77 I now cannot access the camera over WiFi.
    Specifically - I can connect the phone to the camera's SSID but when choosing "BlackVue Wi-Fi" app option the viewer consistently says "Failed to connect Wi-Fi" (see attached image).

    As a result - I can't easily access v1.011 firmware's settings from the car.

    To add insult to injury - a free Play Store app called "Viewer for BlackVue" connects to the camera instantly and plays back videos - no problem.
    I can't access/set up firmware options with it, though (which is fair enough - it does not promise to do anything but video viewing).
    Nevertheless - "Viewer for BlackVue" is useful at confirming that native BlackVue app sucks at its own game.

    All that is tragic, really.

    BlackVue :

    You need to hire a couple of Windows and Android engineers who actually know what they're doing (hint - give the job to the creator of "Viewer for BlackVue", please).
    Your current client software team are as inept at writing working code as they are efficient at destroying your reputation.



  • 0
    Avatar
    Noman

    Dear Martin

    Our apologies for the inconvenience.

    For the inaccessibility of dashcam over direct Wifi issue, can you please tell us what phone are you using? In some Android phones this issue occurs if the LTE/DAta is turned on. Please apply the troubleshooting procedure mentioned in the article below and see if it fixes the issue.

    https://helpcenter.blackvue.com/hc/en-us/articles/222462808-My-smartphone-doesn-t-connect-to-dashcam-s-Wi-fi-how-to-fix-it- 

    Let us know if the issue persits.

    Thank you

Please sign in to leave a comment.