• Content count

  • Joined

  • Last visited

About @lex

  • Rank
    Elite member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

131 profile views
  1. Theoretically you can take from 25 to 30 pictures per second (fps = frames per second) with picture size of 640x480, depending on sensor you use, OV5640 CMOS sensor or GC2035 CMOS sensor (OrangePi camea), YUV format. USB cameras are usually slower than this but has the advantage of delivering the pictures in JPG format, reducing cpu usage and bandwidth. Choosing the right one depends on your application requirements and price target. You can do a benchmark analysis using any v4l2 capture program, for CMOS sensor you can try this: https://github.com/avafinger/cap-v4l2 , it may also works for USB cameras with little change.
  2. That works, thanks.
  3. Whatever you can share, thanks! Looks like who Ziped that SDK ziped img, obj, temp files, etc... Sure a clean would reduce that to half. Mega is a pain for me, over quota every time.
  4. Please, full SDK would be better to get inside info, thank you! Later we wipe Android Just in time: @zador.blood.stained Unless you already built an image without full SDK and could share your inside info on how to build it.
  5. Can you upload the SDK to GoogleDrive?
  6. research

    Waiting for the IPX RF cable to arrive and see how it will boost the signal, 12dBi Omni wifi antenna, $6.75 (now $7.50) on AliExpress. Will try to reproduce same test and post here.
  7. preview

    Here is my take on this matter: Pine64 and BPI-M64 img does not boot on NanoPi A64 NanoPi A64 img boots on Pine64 and BPI-M64, but not without tons of errors Judging by the OPI Win Wifi/BT (AP6212) the best candidate to work out-of-the-box is BPI-M64 img. Better wait for the OPI Win Plus Plus (eMMC) and try mainline 4.10...
  8. research

    With power management off: ubuntu@bpi-m64:~$ sudo iwconfig wlan0 power off iwconfig: from board: other direction:
  9. research

    Results for bpi-m64, same condition: iwconfig: From the board: Other direction:
  10. research

    The results for nanoPi A64 - RTL8189es, 1 meter away, just the monitor between board and the wireless router/modem. tested against my ultra dual core pentium: *Update: no ehternet tune script this time! iwconfig: From the board: The other direction:
  11. research

    NanoPi A64 has RealTek 8189ETV so i have ported it to 3.10.104 to see how it would performs on the A64 arena. For the same distance, same antenna, no walls between i got the values below: bpi-m64 AP6212 with BT enabled: ~14 Mbits/sec nanopi a64 with RTL8189es: ~16 Mbits/sec Unfortunately i don't have Wifi on my Pin64+ to compare with, but i realized it is very hard to get the same values (average values) in different time of the day, for instance you get lower values during night. RTL8189ETV seems to have better signal strength and better performance ( ~ 15% faster ) however i have had a hard time to authenticate with some of my wifi router.
  12. I have to ask, how do i change my "avatar"?
  13. preview

    Thanks for the answer. What would be the boot order then? SD CARD, SPI-NOR, NAND and finally eMMC? Maybe a new BOOT0 would be needed?
  14. preview

    Can someone check if it is possible to attach RTC Backup Battery? What is the real use for this?
  15. Could you please make a short video of your running Squeezebox (with sound)? Looks like a very nice project. I am not an audiophile, is it easy to hear/see how much better ALSA is on vanilla kernel? I will be introduced to the 4.x in the following months, maybe if i get interested i can try to help on the ALSA thing (backport). Regarding DSD i came across this reading: http://www.mojo-audio.com/blog/dsd-vs-pcm-myth-vs-truth/