Announcement

Collapse
No announcement yet.

Allwinner V316

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Allwinner V316

    Allwinner V316 Processor is made for Low-Cost “True” 4K 30 FPS Cameras .

    Allwinner V316 is a dual Arm Cortex-A7 processor for low-cost true 4K cameras support 4K UHD resolution at 60 fps encoded with H.264 or H.265.

  • #2
    Friends what do you think of this action camera? http://www.hdking8.com/hdking-real-4...mera_p449.html

    Comment


  • #3
    I'd like to see the review and photos of this cam with a LED flash.
    @ HDking8 and @ Alibaba

    click to see a larger picture
    Click image for larger versionName:	HTB1Nmn4SYvpK1RjSZFqq6AXUVXa3.jpg_.jpgViews:	0Size:	238.4 KBID:	14721

    Comment


    • #4
      Here is another online sell
      https://www.banggood.com/4K-60fps-Wi...r_warehouse=CN
      https://www.banggood.com/2-Inch-Touc...r_warehouse=CN

      Im really curious if its true, ive been looking some informatuion about v316 chip but only on this site can be found anything https://www.cnx-software.com

      Comment


      • #5
        http://www.hdking9.com/?mod=product&...=9&t=prodetail
        Chipset:Allwinner V316
        Sensor:Sony IMX386
        FOV:170 Degree lens
        Lens:2.0" LTPS LCD
        Video resolution:3840x2160 60fps (interpolation) / 3840x2160 30fps / 1920x1080 120fps /1280x720 240fps
        Photo Resolution:16M /13M /8M
        EIS:Support
        AppVKING 4K (support IOS and Android)
        Battery:1050mah 3.7V
        Storage:8~128G
        Waterproof:30m with waterproof case.

        Comment


        • #6
          Bought one of these:
          https://www.banggood.com/4K-60fps-Wi...r_warehouse=CN

          It is advertised as 4k60fps, but it seems the highest bitrate is achieved in 4k30fps so I guess that's its native resolution.
          I manages to get a backup of the firmware with a slightly modified V3(s) backup script. The naming of the mtdblocks is different.

          Firmware:
          https://j2n.nl/v316/backup.tgz

          Script:
          https://j2n.nl/v316/backup.sh

          /proc/cpuinfo
          https://j2n.nl/v316/cpu.txt

          The device info in the menu displays:
          - Product Model: V316
          - Software Version: V3.0
          - Update Time: 2019-05-28 10:28:46

          Comment


          • petesimon
            petesimon commented
            Editing a comment
            wow. thanks for sharing all that geeky info!

            I unsed unfex-refex scripts and tools. most system files successfully extracted from 2-system.img but i get "create_inode: could not create character device" when using 'unsquashfs.exe' in Windows 7.
            - get extracted files here https://my.pcloud.com/publink/show?c...Izvh4lImBfAE2y

            i can't get any info from script.bin or script.fex files. there is no 'build.prop' file and this Linux-based system appears to be a custom installation of a Linux kernel, proprietary libraries (maybe 'sdv' or 'sdvcam'), Android-Debug, MiniGui, and many userland tools and LUA scripts. the bulk of data is under the '/usr' directory inside 2-system.img . I found 5-slogo.img as the boot logo. I found /usr/share/minigui/res/images/shutdown.bmp could be the shutdown logo. Civetweb server might be running for data transfer via wireless network.

            Questions || info to find :
            1. What is the multimedia framework being used ... CedarX ? or another ?
            - http://linux-sunxi.org/Video_Engine
            2. is 'sdv' or 'sdvcam' binary also being using?
            3. What are the many LUA scripts for?
            4. What is the LCD model(s) in the camera?
            5. ... more ... ?

            You can try these scripts too.
            - modified v3 (not v316) script that was made for V5 cameras. https://my.pcloud.com/publink/show?code=mBq7
            - regular v3 script for Linux (Debian, Ubuntu, Mint, etc). https://www.dropbox.com/s/txrjqgu8nb...press.zip?dl=0

            here is some info i manually got by digging around inside 2-system.img
            Code:
            kernel version
               4.9.118
            touch screen
               yes, via libts-1.0.so.0.0.0 and ts.conf
            Sensor modules (drivers)
               imx278_mipi.ko, imx317_mipi.ko, imx386_mipi.ko
            Wifi:
               xradio
            Audio ?:
               nvp6134
            LCD:
               ? - see below -
            Gyro, Accelerometer:
               ? MPU-6050 Six-Axis
            Logos:
               WELCOME // BYE BYE
            .
            Let's try to determine the LCD model. Please run these commands and post the results here or upload the 'output.txt' file here. You may need to share the data via online cloud storage.
            Code:
            adb kill-server
            adb root
            adb remount
            adb shell busybox uname -a > output.txt
            adb shell busybox dmesg >> output.txt
            adb shell busybox lsmod >> output.txt
            adb shell ls -l /sys/class/drm/ >> output.txt
            adb kill-server
            .
            *Update: touch panel (maybe on top of actual LCD) is FT6236
            https://www.aliexpress.com/item/32794976481.html
            Last edited by petesimon; 08-16-2019, 07:10 AM.

          • petesimon
            petesimon commented
            Editing a comment
            Please share unprocessed mp4/mov video files from this camera via google-drive, dropbox or other cloud storage.

          • Dav
            Dav commented
            Editing a comment
            Hello petesimon! I am from Russia and speak English badly! Apologize. I took your full_img file.tex and full_img file.fex provided by "vzzbx". Both files contain ONLY one sensor for your camera and his . This is IMX386. I looked at the files with HEX editor in ANSI mode code. In the editor --> search --> ANSI--> the word "IMX". Similarly, I found information about the processor 2nd pieces:
            [email protected]
            cpu arm,cortex-a7
            [email protected]
            cpu arm,cortex-a7
            ... LCD model(s) in the camera? In this file Pro words LCD found:
            lcd-sdl.t1,tps65090.nxp,ptn3460.1.2.3
            https://www.alldatasheetru.com/view_...word=TPS65090A

            https://www.nxp.com/docs/en/data-sheet/PTN3460.pdf
            Touch
            LCD panel Controller
            focaltech,ft6236
            datasheet FT6236 .pdf
            https://yadi.sk/i/JxjpeUENpIdz5A
            and also there are such chips:
            mpu6050

            look
            https://i.ibb.co/yB00vrz/ft6236.jpg
            Last edited by Dav; 08-11-2019, 02:35 PM.

          • Dav
            Dav commented
            Editing a comment
            Hello vzzbx! The processor V316 has the h265 codec. Your camera can encode h265 codec?

          • vzzbx
            vzzbx commented
            Editing a comment
            Here is a link to some uncompressed footage of the camera:

            https://www.dropbox.com/s/hg7xdt86wf..._1382.mp4?dl=0

            I cannot find a setting for h265 encoding so it seems to be h264 only currently with this firmware version.

          • Dav
            Dav commented
            Editing a comment
            vzzbx! Thanks for the test. But it seems to me that the camera has a lot of noise (under the bridge arches).
            HDking camera with Sos V316 all can encode in h265

          • nutsey
            nutsey commented
            Editing a comment
            vzzbx is there an option to change AE metering type?

          • vzzbx
            vzzbx commented
            Editing a comment
            Dav: noticed the noise too. It also seems to record far to high brightness in overcast conditions like in the test footage. I tried this afternoon on Ev -3 and that seems to improve the situation a bit.

            nutsey: the following AE metering options are available: average, center, spot and matrix. I tried them and did not experience much of an improvement in overcast shots.

          • vzzbx
            vzzbx commented
            Editing a comment
            petesimon: never noticed your very first comment until now, sorry. Here is a link to the output of the commands you mentioned in your post.

            https://j2n.nl/v316/output.txt

            The whole show is running from two binaries: sdvcam and webapp. They seem to be using minigui indeed. The webapp binary reference to language resources from minigui. The startup script /etc/init.d/S01app does some copying and md5 summing of the sdvcam binary to the sd card. I don not really understand what it is doing there...


            There is a real chatty application log in /var/log/log/sdvcam.INFO going on. I uploaded one where I switch on the camera, record a movie for 3 seconds and then connect the USB to the PC.

            https://j2n.nl/v316/sdvcam.INFO
            Last edited by vzzbx; 08-12-2019, 08:50 PM.

          • petesimon
            petesimon commented
            Editing a comment
            @vzzbx
            thanks for sharing information. be sure to always click the arrow to expand and see all comments

            in your text logs, i see HDMI drivers and HDMI plugout events. Could the LCD be connected to the main board by HDMI cabling?

            I saw the ANMR0011.mp4 file name. Is the naming convention "ANMR0001", "ANMR0002", and so on?
            - i found similar video names in google - https://youtu.be/iVtoisUk49k

            the "adb shell ls -l /sys/class/drm/" command didn't work. let's try to list as many hardware devices as we can, 'n later we could probe into some devices. please do these commands when the camera is on and connected via USB, or via your tty console setup, and share the 'devices.txt' file. The default terminal config and default 'ls' behavior will try to show ANSI/vt100 color text. But it comes out goobligook in a Windows CMD prompt. So, let's disable color text output.
            Code:
            adb kill-server
            adb root
            adb remount
            adb shell ls --color=never -lR /sys >> devices.txt
            adb shell ls --color=never -lR /dev >> devices.txt
            adb shell ls --color=never -lR /proc >> devices.txt
            Thanks!
            Last edited by petesimon; 08-21-2019, 06:42 AM.

          • vzzbx
            vzzbx commented
            Editing a comment
            @petesimon: Yes, the ANMRxxxx.mp4 seems to be the filename pattern used by the camera. The initial file upload I shed through dropbox uses the IMG_xxxx.mp4 pattern, which is caused by my ipad. The file is not tainted however, the md5sums are exactly the same. It also create ANMRxxxx.thm and ANMRxxxx.sec which are a thumbnail file and a smaller preview video.
            The images follow the ANMPxxxx.jpg pattern.

            It does not seem to remember the last filename used. It is less braindead then its V3 predecessor that it seems to remember the date if you swap batteries.

            There is a HDMI output port, maybe you are confused by that. The LCD itself seems to be the same unit as the predecessors.

            Here is the devices.txt you asked for:

            https://j2n.nl/v316/devices.txt

          • vzzbx
            vzzbx commented
            Editing a comment
            I have updated the devices.txt for the ESC-code-challenged:

            https://j2n.nl/v316/devices.txt

            If you still see crap, remove browser cache.

        • #7
          One more Allwinner SoC (probably updated version of V316) - V536: https://www.alibaba.com/product-deta...211696077.html
          Last edited by nutsey; 08-12-2019, 01:47 PM.
          Donate here if you want to support my efforts and this site. Other options for gratefulness are also available on request.

          Email me if you have any offers, requests or ideas.

          Comment


          • #8
            Allwinner V316
            http://www.allwinnertech.com/index.p...&a=index&id=87

            Allwinner V57
            https://www.aliexpress.com/item/4000018712406.html
            Sensor:IMX278
            Last edited by Dav; 08-11-2019, 02:58 PM.

            Comment


            • nutsey
              nutsey commented
              Editing a comment
              Thanks! Have you seen any cams based on these new Allwinner SoCs with IMX317 sensor inside? And please don't post many links at once as forum spam filter can go mad
              Last edited by nutsey; 08-11-2019, 03:14 PM.

            • Dav
              Dav commented
              Editing a comment

            • nutsey
              nutsey commented
              Editing a comment
              Ок, спасибо!

            • Dav
              Dav commented
              Editing a comment
              nutsey ! Как Вы считаете , камера с v316 4k60fps (3800х1800, h264) лучше чем akaso v50 elite c 4k60 mjpeg?

            • nutsey
              nutsey commented
              Editing a comment
              Думаю, что большой разницы по качеству дневной съёмки между камерами на сенсорах IMX386 и IMX078 вы не увидете (при условии использования адекватной оптики в обоих случаях).

            • Dav
              Dav commented
              Editing a comment
              То что там микроны в размере пиксела не важны я понимаю. А вот в кодыке. различия наверное есть.
              http://4pda.ru/forum/index.php?showt...ost&p=84697927
              рем
              я чувствую что я эту (v316) камеру возьму.Она лучьше чем seabird по моему из-за hdmi, usb и почнго+цеа.

            • nutsey
              nutsey commented
              Editing a comment
              Прочитал по ссылке и думаю, кто это такой умный написал? А, ну да. Это я и был ))

              4к60 фейковый у обеих камер, так что я бы на это даже и не обращал внимания...

            • Dav
              Dav commented
              Editing a comment
              на глаз я не увижу растяжку на телике с 3800х1800 до 4к но вот перекодировать из mjpeg я замучаюсь.Помоему эта камера за 3000р стоит того чем 4к60 sj8pro за > 10000р
              Как считаете?

            • nutsey
              nutsey commented
              Editing a comment
              Нет там растяжки. Тупо 4К30 пишется с дублированием каждого второго кадра. И в 4К30 там баг, кстати, есть судя по прошивке выше... оно через 2.7К зачем-то прогоняется предварительно - мыло будет то ещё...

            • Dav
              Dav commented
              Editing a comment
              оно через 2.7К зачем-то прогоняется предварительно. может из-за стаба? Я для себя внешний стаб буду брать.

            • nutsey
              nutsey commented
              Editing a comment
              А я там стаба для режимов выше 1080p60 не наблюдаю.

            • Dav
              Dav commented
              Editing a comment
              я им (hdking и другим) написал вопросы о manual-е , кто-то но пришлёт. увидим.

          • #9
            The official answer from the manufacturer of the camera hdking with Soc V316. Cameras with SOC V316 have h265 codec

            http://hdking.en.alibaba.com/

            Comment


            • petesimon
              petesimon commented
              Editing a comment
              the hardware can do h265, but will the firmware actually utilize this feature and actually encode video as h265 in mp4 (or mov) files?

            • petesimon
              petesimon commented
              Editing a comment
              I ran the "binwalk" tool in Linux against each 0,1,2,3,4,5,6 img file (link is here) that vzzbx pulled from his camera. A sample output is shown below.
              Download the output logs here - https://my.pcloud.com/publink/show?c...C5n43Ju4g0qHCk

              0-uboot.img
              Code:
              DECIMAL       HEXADECIMAL     DESCRIPTION
              --------------------------------------------------------------------------------
              344332        0x5410C         SHA256 hash constants, little endian
              350810        0x55A5A         Unix path: /arch/arm/include/kernel/user_ta.h
              356444        0x5705C         Unix path: /arch/arm/mm/tee_mm.c
              357672        0x57528         Unix path: /arch/arm/pta/interrupt_tests.c
              362926        0x589AE         Unix path: /lib/libtomcrypt/src/tee_ltc_provider.c
              539436        0x83B2C         CRC32 polynomial table, little endian
              555560        0x87A28         Android bootimg, kernel size: 2037543936 bytes, kernel addr: 0x206F7420, ramdisk size: 1684104562 bytes, ramdisk addr: 0x72617020, product name: "ash read :offset %x, %d bytes %s"
              673636        0xA4764         YAFFS filesystem
              673660        0xA477C         YAFFS filesystem
              679944        0xA6008         YAFFS filesystem
              680016        0xA6050         YAFFS filesystem
              682320        0xA6950         YAFFS filesystem
              Last edited by petesimon; 08-12-2019, 06:38 PM.

          • #10
            Last night I opened the camera up to have a look inside. There is a working console on the tx and rx pins. It just logs you in with root without password. The main application log is also printed out to the console.

            Console works on 115200 baud.

            It would be nice if we could get it to boot from sd card instead of emmc...

            Comment


            • petesimon
              petesimon commented
              Editing a comment
              thx for photos. i copied your photos to an album here - https://imgur.com/a/GZ7fqoI

              what model/brand of USB to UART/TTL adapter device are you using?

            • vzzbx
              vzzbx commented
              Editing a comment
              @petesimon: the USB adapter is of my own design using a Holtek HT42B554 USB UART bridge.

          • #11
            The format of the H264 codec is written in the firmware. It is not possible to change the camera menu from "0" to "1"(H265). In the next firmware this will be done
            (hopefully).

            petesimon good job


            Last edited by Dav; 08-13-2019, 10:49 AM.

            Comment


            • petesimon
              petesimon commented
              Editing a comment
              Dav - Unpack '2-system.img' file. We could change 0 to 1 for h265 encoding in 'data\media_config.lua' and in 'usr\share\app\sdv\media_config.lua' file. And then repack the '2-system.img' file in Cygwin/Unix/Mac/Linux, but not in Windows because there is a problem. Most of all ... we need to determine how to flash load firmware to the camera.

              Notice that '1' setting corresponds to an encoding profile '1' in 'etc\cedarx.conf' file for h265. Also be aware that the text 'h265' and the text 'hevc' is found in 'usr\bin\sdvcam' binary file many times (by doing a case insensitive search).
              Code:
              -- -------------------------------------------------------------------------------
              -- Copyright (c), 2001-2016, Allwinner Tech  All rights reserved.
              -- -------------------------------------------------------------------------------
              -- file     media_config.lua
              -- brief    ${DESCRIPTION}
              -- author   id: 826
              -- version  v0.3
              -- date     2016-10-11
              
              media = {
                  camera = {
                      -- cam0
                      {
                          width = 1920,
                          height = 1080,
                          -- video encoder config
                          venc = {
                              -- encode format, 0-h264, 1-h265
                              format = 0,                                                          <-- HERE -->
                              -- encode type, 0-cbr, 1-vbr
                              type = 0,
              .
              Code:
              # file etc\cedarx.conf
              [vdecoder-1]
              comment = h265_vdecoder
              id = vdecoder.h265
              lib = libawh265.so
              init = CedarPluginVDInit
              .
              case insensitive search text in sdvcam
              Code:
              # for Unix/Mac/Linux                       # for Windows
              grep -a -i h265 usr/bin/sdvcam                      findstr /i h265 usr\bin\sdvcam
              Last edited by petesimon; 09-27-2019, 04:49 PM.

            • petesimon
              petesimon commented
              Editing a comment
              Dav and everyone - I read this page https://linux-sunxi.org/FEL . removed battery, and removed sd card first. and I tried the process of pressing buttons as written on that page.
              By holding a standard button. This is usually one of the standard tablet buttons, like the VOL+ key or something. The following seems to work:
              Press and hold the suspected or reported FEL key.
              Press and hold the power key for about 2 seconds.
              Release the power key, and press it at least 3 times immediately.
              Boot1 is initialized using this method.
              Actually, we can just do these steps. This is successful for me:
              1. remove battery, remove sd card
              2. press and hold UP button
              3. connect USB cable to camera and to computer, still holding UP button
              4. press and release the power/mode button 3 times
              and the usual USB device entry for recovery shows up in Windows Device Manager as "USB Device(VID_1f3a_PID_efe8)" or in Linux as "1f3a:efe8" when you run 'lsusb' tool.
              Last edited by petesimon; 09-27-2019, 12:38 AM.

          • #12
            vzzbx maybe h265 is not exhibited in all modes, the size of the image. For example GoPro 6-7 not in all sizes pictures of the has codec h265 --> https://gopro.com/help/articles/block/hevc

            Comment


            • vzzbx
              vzzbx commented
              Editing a comment
              I would imagine that the option would be greyed out then instead of hidden. There is an option called "distortion correction" which is greyed out in every resolution over 1080p60fps because the system is (propably) too slow to perform that tricks at higher resolutions. In the menu the option is then greyed out, but still visible. It would have been stupid to hide h265, because it is one of the selling points for crappy cameras like these. Let's not talk about the bullshit 4k 60fps recording mode...

              This firmware version seems very immature and lacking of features. The metering modes seem to do nothing. The recordings are by default far too bright, especially on overcast days. The photo modes are a joke, 2013 era smartphone pictures.

              Whether this is going to improve is really in the hands of the manufacturer.

              Why buy this camera? Personally it was the cheapest (semi-) native 4k30fps option currently on the market to strap onto my miniquads so I would shed the least amount of tears when I would inevitably crash this thing thing into a tree.
              If you insist in buying a true 4k30fps camera that does h265 encoding then buy something with an iCatch V50 chipset, much better. Still sorry I crash my Vikcam V50 into a lamppost...

              TLDR: Sorry for the rant, this version has no h265.

            • Dav
              Dav commented
              Editing a comment
              ...tnx

          • #13
            vzzbx Your camera's cheaper. nutsey Doubt that your camera has a true 4K. I want to ask you about the test chamber. It is necessary: 1-to take photos using the maximum resolution of the ruler (the school). 2 - Immediately switch to video mode and make the same video 4k30 and 4k60 file (ruler). try to put the camera down and not touch it. Stabilizer and other things off. And all this (photos and videos) to put on google drive or somewhere else. It would be good at the same time that there was a lot of light. You understand me?

            Comment


            • nutsey
              nutsey commented
              Editing a comment
              В наличии настоящего 4к у какой из моих камер речь?

            • Dav
              Dav commented
              Editing a comment
              https://www.goprawn.com/forum/allwin...5127#post15127
              ----------------
              Нет там растяжки. Тупо 4К30 пишется с дублированием каждого второго кадра. И в 4К30 там баг, кстати, есть судя по прошивке выше... оно через 2.7К зачем-то прогоняется предварительно - мыло будет то ещё...
              -------------
              Мне кажется это переводчик не правильно выразился. Не твоя камера а ЭТА!!

          • #14
            Thanks to all who are contributing. Here is a collection of raw files, info text and logs of the v316 firmware here from vzzbx

            Files: full_img.fex, and 0/1/2/4/5/6 img, and extracted data from 2-system.img - https://my.pcloud.com/publink/show?c...Izvh4lImBfAE2y

            dmesg log and list of devices dump - https://my.pcloud.com/publink/show?c...JPeqEdYXTUzEXy
            - "busybox dmesg" tends to work best inside cameras

            binwalk ran against all 0/1/2/3/4/5/6 img files - https://my.pcloud.com/publink/show?c...C5n43Ju4g0qHCk

            See more information in this thread, especially in post #6 here. Be sure to expand all comments for each post. 🤓

            Comment


            • GoPrawn
              GoPrawn commented
              Editing a comment
              "expand all comments"
              Thanks for the idea

            • petesimon
              petesimon commented
              Editing a comment
              We can find some nice information from text of some LUA scripts https://w.wiki/7kS . The LUA scripts are inside 2-system.img, in the /usr/share/app/sdv directory. Let's see...

              build_info.lua : text matches the date/time that vzzbx gave us.
              build_time = "2019-05-28 10:28:45"

              net_config.lua : text tells us defaults for network stuff, and tells us about some hardware.
              interface = "wlan0"
              mac = "78-D8-2B-66-D8-C8"
              ip = "192.168.1.8"
              wifi = {
              ssid = "PD2-IPC-test",
              pwd = "12345678",
              },
              softap = {
              ssid_prefix = "Sport-cameras",
              pwd = "1234567890",
              deviceinfo={
              producttype="V316",
              softwareversion="V3.0",
              updated="20190219",
              manufacturer="Sunchip",
              }
              privateinfo={
              chipid="V316",
              producttype="Dv-Tp",
              version="V3.0",
              lcd="st7789v",
              sensor="Imx386",
              customer="xdv",
              manufacturer="Sunchip",
              }

              device_info.lua : LCD screen res'
              screen = {
              width = 320,
              height = 240,
              }

              setting.lua : here is extra info
              device_info = "v316-sdv-v1.0rc2"
              Last edited by petesimon; 09-01-2019, 06:42 PM.

            • petesimon
              petesimon commented
              Editing a comment
              *Update - here are UNFEX REFEX FWINFO scripts to use in Windows. The scripts are designed to work with V316 (not V3) firmware - https://www.dropbox.com/s/12xljkf9pb..._V316.zip?dl=0

          • #15
            vzzbx Give a link to download the firmware of your camera. Your camera has a 4k60 . I bought https://www.aliexpress.com/item/4000029983758.html ahhh! I want to flash it with your firmware. Camera's still on the way..

            Comment


            • petesimon
              petesimon commented
              Editing a comment
              links are already provided above, in post #6. Expand all comments to see more detail...
              I don't have this camera. I don't know how to properly flash load it.
              how can we flash load FW without making a 'brick' ?
              Last edited by petesimon; 08-23-2019, 07:34 AM.

            • Dav
              Dav commented
              Editing a comment
              petesimon In the post (№6) backup is not firmware. On the box or in the user manual there is an http link to the brand or support

            • vzzbx
              vzzbx commented
              Editing a comment
              As petesimon said, the firmware is in my post and his backup links. There is no website link on the box and neither is there one in the manual. It is a generic unbranded camera probably made by Hdking8. Do not expect future updates.

              The only links on the box are QR-codes leading you to the app stores for either Android or IOS.

              @Dav: it will be interesting if you manage to pull a backup oof the firmware from your device and see whether the hardware is the same. Seems your housing is slightly different, more akin to the second Banggood offering (square buttons vs round). It could just be a cosmetic difference though.

              I tried putting the full_img.fex on my sd card and using the instructions for the V3s to update, but no luck until now.

              Off topic: it tends to overheat and become unstable if you connect the camera to the PC using USB cable. I was poking around using adb and got kicked out. It started to make fissing noises with the battery in. Without battery it gets hot too.

            • petesimon
              petesimon commented
              Editing a comment
              fizzy noises? maybe the battery cells are made of alka seltzer. yeah, it's much more effervescent then older V3 cams! haha

              I believe one camera is made or rebranded by Ausek and the other camera is HDKing. Check my FB post here - https://www.facebook.com/groups/allw...0897871010120/

              but seriously. how would we properly flash load FW into the camera without sending it to BSOD hell?
              Last edited by petesimon; 08-25-2019, 06:51 PM.

            • petesimon
              petesimon commented
              Editing a comment
              Dav - i got my V316 camera. did you get yours ?
              Last edited by petesimon; 09-26-2019, 05:27 AM.

            • Dav
              Dav commented
              Editing a comment
              petesimon
              Today received. SD Card still not came 64G. There is only 1G in the phone. Probably not enough to use your script. https://www.goprawn.com/forum/allwin...5572#post15572 . I have firmware version camera says 2019-03-28 17:20:21

            • petesimon
              petesimon commented
              Editing a comment
              Dav - good! congratulations! if you have 16gb Class 10 fast card or bigger card, then you can use that. A short 4k video is 400 mb or 500 mb. Other resolutions videos are smaller mb Please share your firmware data when you can.

              You purchased 64gb Sandisk Extreme Pro ? It's a very good card but too expensive (high $) for basic cameras. Samsung EVO Plus U3 (orange/white) works great in all cameras and costs less, here - aliexpress.com/item/33012988749.html .

              I use an OTG USB adapter cable and a SD card reader to quickly copy videos files to a phone, here - aliexpress.com/item/33046947209.html and here - aliexpress.com/item/33039671929.html . The DVKing wifi app is slow.
              Last edited by petesimon; 09-26-2019, 06:25 AM.
          Working...
          X