All Activity

This stream auto-updates     

  1. Past hour
  2. What's the difference if I need to manually configure the port where the IR receiver has been soldered. Later I'll try H3droid. I'm not sure what it is that it's easier to confiure up a separate pin Clapper algorithm analyzes the envelope of the audio signal. And my system based on the neural network and HMM with the Viterbi algorithm recognizes individual phonemes and letters in the word. The difference between an ant and an elephant )) And there is no understanding in any system. There is simply a memory in which the dictionary is kept and a possible suitable answer and choice
  3. For CEC support, better stick with this OpenElec ports - IR is working fine there too, you can find some info here - How to get IR working (NEC protocol). Bad news is, i personally was unable to get HDMI CEC working with OpiOne, or OpiPlus2e (the boards i had). It was working for seconds, or not working at all. The only board i manage to make it working stable (and use it every day till now) is Orange Pi PC. IR with OpiPlus2e was working fine, the last time i tried, but for OpiOne, you don't have IR receiver soldered, so you have to soldered yourself (if you can ) - Orange Pi One - adding USB, analog audio out, TV out, mic and IR receive. Basically it's possible to activate HDMI CEC in Armbian, as module and install libcec, i tested myself back in days. Maybe it's applicable for H3Droid too, which is Android based on Armbian, as far, as i know and there should be h/w acceleration Kodi. But how you will integrate CEC with Kodi after this, i have no idea. Opi One is not good for what you want to archive, by my opinion. The best use case you can have from it, that will save you some headaches, is to buy some usb mini keyboard with tuch and use it with OS of your choice - Armbian with MPV/SMPlayer/SMTube, OpenElec, H3Droid (probably the best choice for your needs).
  4. Today
  5. Completely forgot this stock androids on eMMC... It's not that uncommon.. There's a reason why we push people to the usb-ttl. Even if it's not solved everything yet, you see now what's going on during boot.
  6. NanoPi Duo (plus Mini Shield)

    I received a NanoPi Duo today. Since I did not order the shield I set up for Wifi. A preliminary network performance test using speedtest-cli shows about 18 MBit/s with the on-board antenna, and 20 MBit/s with an OPiZ-Antenna (ca. 1,5 m from AP). Though not impressive, this is significantly better the OPiZ WLAN performance - despite the identical driver(and close to the numbers reported by @TarableCode). Nice little board, though ...
  7. That's a buyed false board issue, not software issue. IR remote is supported by H3droid. It might be interesting to test android on your OPi one first, to evaluate if it's worth to buy another H3 board with a appropriate IR solution (and maybe with a bit more ram). The clapper recognizes claps and it was made in the 90'.. Doesn't mean, he 'understands' something. Ok, we may have different opinions what voice recognition means. But doesn't matter, this is out of your basic requirements yet.
  8. Orange pi zero random hangs

    Yes, you are correct. To soon. I remove them.
  9. Orange pi zero random hangs

    I wouldn't make a "stable" mainline build yet. Without DVFS and thermal throttling it will be as "stable" as this:
  10. android did not try. What is the use of me from any OS if there is no IR control panel support ...
  11. At me recognition of separate words on the microcontroller it is made with 16кб RAM ... 14кб from which it is borrowed under the buffer for capture of a word ... Power even Orange Pi One, is Something extremely large and sufficient for me... ))
  12. Orange pi zero random hangs

    Check most recent preview build. This will be next stable. In general, make sure you have good power supply and cables. Wifi rather don't use since it has a very bad chip and driver.
  13. Orange Pi One bootlooping with current armbian

    ... and (hopefully) fixed: a717f1a Funny how the problematic code here is identical to the "bad" example here.
  14. Boot process changed. Start with a new image and don't' update. I hope you understand that we don't care to provide any stability for testing images? They work or not. The file is one path up. Copy it there.
  15. ARMBIAN for Amlogic S905 and S905X

    I haven't tested these utilities on core 4.x I hope you are using a 64 bit system and installed the 32 bit multilib ? To all Update test image 4.14.0-rc1-next-20170922.
  16. Hello guys, I need my device to load armbian , autologin and run my application fullscreen. Can you give me a hint, please, what I should add into customization scripts ? Thanks
  17. I used the Armbian test image. I did apt-get upgrade I changed eth0 to static IP. But now, I started it up and eth0 green light won't stay on. Can't ping it or SSH. I connected a USB PL-2303HX from my PC to the NanoPi Neo2 (first time for me ever connecting to a Linux computer's serial console) With no configuration at all I got this output in minicom. U-Boot SPL 2017.09-armbian (Sep 17 2017 - 03:48:48) DRAM: 4096 MiB Trying to boot from MMC1 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 02:45:22, Sep 17 2017 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 Looks like U-Boot can't find the kernel or whatever? Okay I removed the 5v wire from the USB serial adapter so I can rather power the board via microUSB 2A adapter than weak USB port power. I unplugged and replugged the 2A microUSB but it didn't help. With the microUSB unplugged the PCB's green LED still glowed faintly somehow powered from GND and tx/rx. rneese suggested I unplug and replug everything. I did and now it booted up and I can see it on the console. It's saying no ethernet found and it looks like a console so I'll give it a go. U-Boot 2017.09-armbian (Sep 17 2017 - 03:48:48 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO 2 DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 38518 bytes read in 134 ms (280.3 KiB/s) Unknown command 'bmp' - try 'help' switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3362 bytes read in 179 ms (17.6 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 116 bytes read in 149 ms (0 Bytes/s) ** File not found /boot/dtb/allwinner/allwinner/sun50i-h5-nanopi-neo2.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 4179 bytes read in 362 ms (10.7 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 5001834 bytes read in 452 ms (10.6 MiB/s) 12285960 bytes read in 868 ms (13.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 5001770 Bytes = 4.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... starting USB... No controllers found USB is stopped. Please issue 'usb start' first. starting USB... No controllers found No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found starting USB... No controllers found No ethernet found. No ethernet found. => => ls ls - list files in a directory (default /) Usage: ls <interface> [<dev[:part]> [directory]] - List files in directory 'directory' of partition 'part' on device type 'interface' instance 'dev'. => su Unknown command 'su' - try 'help' => help ? - alias for 'help' base - print or set address offset bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootefi - Boots an EFI payload from memory bootelf - Boot from an ELF image in memory booti - boot arm64 Linux Image image from memory bootm - boot application image from memory bootp - boot image via network using BOOTP/TFTP protocol bootvx - Boot vxWorks from an ELF image cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation dhcp - boot image via network using DHCP/TFTP protocol dm - Driver model low level access echo - echo args to console editenv - edit environment variable env - environment handling commands exit - exit script ext2load- load binary file from a Ext2 filesystem ext2ls - list files in a directory (default /) ext4load- load binary file from a Ext4 filesystem ext4ls - list files in a directory (default /) ext4size- determine a file's size false - do nothing, unsuccessfully fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) fatsize - determine a file's size fatwrite- write file into a dos filesystem fdt - flattened device tree utility commands fstype - Look up a filesystem type go - start application at address 'addr' gpio - query and control gpio pins help - print command description/usage iminfo - print header information for application image imxtract- extract a part of a multi-image itest - return true/false on integer compare lcdputs - print string on video framebuffer load - load binary file from a filesystem loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loadx - load binary file over serial line (xmodem mode) loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range ls - list files in a directory (default /) md - memory display mdio - MDIO utility commands mii - MII utility commands mm - memory modify (auto-incrementing address) mmc - MMC sub system mmcinfo - display MMC info mw - memory write (fill) nfs - boot image via network using NFS protocol nm - memory modify (constant address) part - disk partition related commands ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables pxe - commands to get and boot from pxe files reset - Perform RESET of the CPU run - run commands in an environment variable save - save file to a filesystem saveenv - save environment variables to persistent storage setcurs - set cursor position within screen setenv - set environment variables setexpr - set environment variable as the result of eval expression showvar - print local hushshell variables size - determine a file's size sleep - delay execution for some time source - run script from memory sysboot - command to get and boot from syslinux files test - minimal test like /bin/sh tftpboot- boot image via network using TFTP protocol true - do nothing, successfully usb - USB sub-system usbboot - boot from USB device version - print monitor, compiler and linker version
  18. VLC Issue

    What about with stock mplayer? Does it work OK?
  19. Orange Pi One bootlooping with current armbian

    ... and we have some rather strange results: this: fdt set /soc/${tmp_spi_path}/spiflash spi-max-frequency "<${param_spinor_max_freq}>" is broken after this commit:;a=commit;h=7cbc12415dad707b94d755311126059e5cdc65e3
  20. Looking for board for nas

    I can't agree more. I'll definitely try this and report back. If this small problem can be fixed, then there's suddenly good use for it.
  21. Armbian build farm

    Personally I prefer to purchase something that I can use in a later machine if possible - but this all depends on how you look at it. If the board is going to be busy doing a lot of work, then some cheaper but not-so-capable modules might be a better overall purchase, but I'll leave that up to you to decide. I've been there a couple of times. It's even worse when a product vanishes completely. Eg. you don't find 2.5" PATA drives everywhere anymore (they're still on eBay). Almost can't purchase them in Denmark from the stores (well you can, but they cost 3 times a SATA drive and there is only one to choose between).
  22. Speech recognition in terms of 'understanding' not just recording wouldn't be possible with an orange. The reason why all these services (alexa, siri etc.) are so powerful is their huge back end. I think a minimum requirement for some 'basic' machine learning would be a OpenCl capable GPU with software support. Without 'experimental' builds a lot of this projects would be really boring.. Things have to be developed and tested before you can call them 'stable'. In a 'commercial' product, this is (hopefully) done before release whereas in opensource projects this is mostly done before and users can test things before they are sure everything runs smoothly. Welcome to the real world.. Whereas on x86 architecture you've (more or less) one player dominating the whole market, this differs much on arm (e.g. Allwinner, Broadcom, Qualcomm, Rockchip, Samsung etc.). Their main goal is to provide 'support' for android devices in those days. SBCs are IMO just a niche market to sell some extra boards. If you compare H3 devices from xunlong, you get them in a price range between 10 (OPi one) up to 50$ (OPi plus 2). Beside ram and eMMC you need some other reasons why people should buy one or the other board.. To my knowledge, all these linux based OSes on H3 are spare time projects. Without them, you would stay with a 3.4.39 kernel provided by Allwinners BSP 'without any support'. Most/all development happens neither by board makers or SoC makers as soon as they rolled out the SoC. Support of a SoC from 2014 isn't of interest for them. For the price of a OPiOne you get here a BigMac with fries and a coke... You'll have more fun with the OPiOne (in case of your expectations of course more frustration since it doesn't fullfill your needs). I recommend to do the 'homework' before buying it. I buyed a OPi 2g-IoT once expecting that it will have a decent software support soon, just to realize that experienced developers weren't willing to work on it and I'm not able to do it (lack of knowledge). Just cause I'm interested, did you test the android?
  23. VLC Issue

    Hello guys, I am having problems with vlc, the video is running out of proportion and it is all over the interface, ie, even minimizing vlc the video is still being shown, I tried to change the codecs but I did not have a satisfactory result, because only the VDPAU works without lags Help me please, sorry for bad English.
  24. @spicedreams Fixed in sources.
  25. Pinebook install to eMMC?

    mmc-utils is already present in Stretch, and we could probably build it for older releases too, but can't give any ETA due to some HW related issues.
  26. Pinebook install to eMMC?

    @Igor and @zador.blood.stained: I thought about bundling mmc utility from mmc-utils package already but did not found a debian package. Building from source results in these times (Clearfog Pro): time (git clone ; cd mmc-utils ; make -j$(grep -c processor /proc/cpuinfo) ) ... real 0m4.989s user 0m7.035s sys 0m0.413s Size of the binary is below 300K. Any chance to bundle this somehow with an Armbian package so I could include output from it in a future armbianmonitor -U (capital U) version?
  27. Quick Pinebook Preview / Review

    Well, I don't know if adjusting these 3 values in the way they are set now everywhere was much by intention and not just by accident. By looking at a lot of similar values (like CPU frequency steps, DVFS OPP or DRAM clockspeeds) in the meantime I came to conclusion that whoever defines them in the first place can do almost what he wants (numbers not being questioned) while later it needs an insane amount of discussions/efforts to change such numbers again. After thinking somewhat about it given the PSU's 3A limitation and people probably attaching even a host powered USB disk to their Pinebooks having pmu_runtime_chgcur set that high seems questionable to me. These were the values we started with: pmu_runtime_chgcur = <0x1c2>; pmu_suspend_chgcur = <0x5dc>; pmu_shutdown_chgcur = <0x5dc>; And that's where we're now: pmu_runtime_chgcur = <0x708>; pmu_suspend_chgcur = <0x5dc>; pmu_shutdown_chgcur = <0x5dc>; (only change: increasing charge current on a running system from 450mA to 1800mA while not touching the other values).
  1. Load more activity