Just curious: Did anyone already ran Geekbench on the latest Android 7.0 build with longsleep kernel?

I just ask since when we started tweaking cpufreq / dvfs scaling back in March it was pretty obvious that 'performance' of any demanding task lasting longer than 60 seconds depends on heat dissipation (hardware issue: enclosure vs. none, heatsink vs. none, heavy loads as cpuburn-a53 required already heatsink + fan) and on ths / throttling settings (software issue: killing CPU cores vs. reducing frequencies, providing more cpufreq steps vs. less and so on).

When looking through scores made for Android 5.1 (all with Allwinner's boring and outdated 3.10.65 kernel and most probably ths / cooler_table settings from hell) it looks like different environmental conditions have been 'benchmarked' (especially enclosure vs. none): https://browser.primatelabs.com/v4/cpu/s...q=PINE+A64

Is Geekbench smart enough to take throttling into account? Or at least reporting/monitoring (changes of) /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq?

Hello all,

Love it.  

I've not used vi  seriously since the 1990's, and as a modal editor, I managed to remember enough to quit.  :q!  My current editor of preference is sublime text, which is awesome!, but not on the basic boot images found here, let alone for arm instruction sets.

My long time editor is emacs, cause it does lots, and the key bindings work for Cisco kit too, and lots of other systems.  Missing.

My go to ultra light weight editor is pico, taken from the pine email program (yeah, any one using pine yet, on pine???), and it provides plenty of what's needed for basic system editing.  But that's not here either.

Copying from my netbook does no good, cause the binaries are all x86_64, and pine64 is AArch64.  

So, I am looking for these as precompiled binaries, and failing that, I'll have to cross compile on the netbook.  Or I could refresh myself on vi, but...yeah... that's gonna happen.

I'll post my solution once I've found it.

David

Hello anybody,

I've ordered one Pine A64+ on Sep 4th, but until today there isn't any change on the shipment status. It is still on "Your package is being prepared to ship"

Is this normal? Today we have Sep 19th! On my two emails I got no reply, but they charged my VISA card after the order directly. This isn't nice...

Could somebody be so nice to check this? My order number is #8165400.

thanks in advance,
Christian

So today, after waiting what seems forever, finally arrives my Z-Wave (US) Module and PINE64 Enclosure.  Originally I backed the PINE A64+ IoT Package (2GB), and finally got my board in early July, and mid-Sept I got the rest of my order.  I was backer 13,893.

So imagine my excitement thinking I could finally, after waiting almost a year, play with OpenHAB and finally set up, after waiting 6+ months, the Z-Wave gear that I had recently bought (deadbolts, thermostat, motion sensors, etc -- ~$500 in Z-Wave gear).  

Here is my thought progression..

What I received:
http://imgur.com/dPDR92l.jpg

Logic says they go together like this:
http://imgur.com/jI5ISAC.jpg

This is how it fits on the PINE64 board, right?

http://imgur.com/tBR7Xtg.jpg

Cool, now let's put the FINISHED board into my fancy new case:
http://imgur.com/mBd4ivP.jpg

Wait...will the top fit on?  This module sticks up pretty high..
http://imgur.com/qnF4MVW.jpg

Hmm...yeah, that's not going to work:
http://imgur.com/5f4smvq.jpg


So please, help me.  Did I install this incorrectly?  Without seeing any instructions I can only assume I did this all correctly.

Beyond that, are my assumptions correct that the latest Pine OpenHAB build is still 20160415?  That means that the new Z-Wave module isn't even supported?  Maybe I should just trash this Z-Wave module (that doesn't even appear to fit) and use my Z-Stick with Home Assistant or something...

I like to think I've been pretty patient with all this, but I'm starting to get upset by this whole adventure.  I thought by now I would have a plug-and-play OpenHAB box with Z-Wave, Wifi, and Bluetooth support.  The Pine board is pretty nice and runs great with DietPi, and this case seems very solid and would fit nicely on the shelf on my server rack.  But I guess I'll have to put up with a big Z-stick sticking out of it.  Hmm, maybe I'll just ditch this whole project and put the PINE in my storage tote next to my Pi B+ and my oDroid XU4 and put the Z-Stick in a rack-mount piece of gear.  Bleh, what a mess.

im building a pineapple with one of my pines. well why not. i figured i would post my instructions. this is adapted from an install script i wrote for reaver a few months back.

remember that any of these tools must be used on networks that you own or have permission to use.
some of these tools on here can interfere with computers/devices on a network.
i will not be held responsible for killing your router, causing nuclear winter, you going to prison or your neighbour bashing the shit out of you for using all of his internet and costing him a small fortune.
i will also not answer questions on how to use the software included. everything has a "--help" or man page for usage. if you still dont know what your are doing then this is not the guide for you.

THIS IS ONLY FOR THOSE WHO KNOW WHAT THEY ARE DOING



my setup.
pine a64+ 2GB board + 64GB SD card. metasploit alone takes up 10gigs.
pine64 wifi module. used for connecting to personal wireless hotspot provided by my mobile device. dont plug this in just yet. we dont want this called wlan0 or wlan1
2 x external wireless network cards with reasonable antennas. most of the wireless tools out there only really attack the 2.4GHz band so the cards should be single band.




first download the latest debian longsleep base image.

burn SD card and boot your pine.



start by changing the default password

Quote:root@pine64:/home/debian# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Quote:firmware-atheros - Binary firmware for Atheros wireless cards

Quote:wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

Quote:root@pine64:/home/debian# iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

dummy0    no wireless extensions.

sit0      no wireless extensions.

lo        no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:on

root@pine64:/home/debian# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Quote:debian@pine64:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
debian@pine64:~$ sudo iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

dummy0    no wireless extensions.

rename7   IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:on

wlan2     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

sit0      no wireless extensions.

lo        no wireless extensions.

wlan1     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Quote:debian@pine64:~$ sudo iwconfig
wlan3     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

dummy0    no wireless extensions.

wlan2     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

sit0      no wireless extensions.

lo        no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
          Retry  long limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:on

Quote:auto wlan2
iface wlan2 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Quote:network={
ssid="YOUR_NETWORK_NAME"
psk="YOUR_NETWORK_PASSWORD"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
}

I want to rotate the video, I used the sunxi transform module. But I found that the sunxi transform module is very slow, I rotate a 640x360 yuv420 video buffer, the performance is 10fps! It's too slow to do any thing. What the sunxi transform use for? If I need to rotate 4k video @ 30fps, how can I do that?

Hi there,

I am running 2GB version on Android. This was initially working at great speed.

Now I'm experiencing problems streaming online content (using catch up TV apps) as well as things from NAS on local network using Kodi. Streaming videos buffer really slow over wifi and wired ethernet connection. Seems to be a problem with the Pine64 rather than network issue.

Can anyone point me to a way to get some logs for more specific help here?

Cheers

All-

Looking to integrate the Enocean USB 300U radio on Android to use their IoT kit.  Before we start working I wanted to check that no one else is/has already successfully integrated the FTDI drivers on the Android image?

Thanks!

I received a Nexdock which is basically a display and a bluetooth keybord. The idea is that with Nexdock you can turn your Pine64 into a laptop.
https://www.indiegogo.com/projects/nexdo.../2028259#/

I'm running RemixOS 2.0 on my Pine64 2GB but I can't change the output resolution of the Pine64 to 1366x768.
1366x718 is the native resolution of the Nexdock.
Nexdock works together with Pine64, but all text is hard to read because of the wrong display setting.

Any solution or Remix OS update to fix this issue?

Thanks, Bart

This mini tutorial is meant for those people providing Android or RemixOS 'DD images'. The DD images currently provided have been created wrong (too large for many SD cards out there). Fortunately it's easy to do it better. Since we're talking here about SBC why not stop wasting time on both creator's and user's side, using an SBC in USB gadget mode, create images with appropriate size and speed up things?

The whole process would work with any Pine64/Pine64+ too but since AFAIK no OS image is around that uses a correctly configured kernel enabling the necessary g_mass_storage module and since a small patch might be necessary to get this working with BSP kernel (can't test right now since ran out of Pine64) we discuss this with H3 devices instead (H3 is A64's little sibling). Ingredients:

• Any H3 device from this list: http://www.armbian.com/download/
  
• A short USB-to-Micro-USB cable (or type A to type A when choosing the Beelink X2 or Pine64 later)
  
• An Armbian image for the device in question using legacy kernel since we need USB OTG support
  
• A 120 GB disk to store the images with 7.8, 15.8, 31.8 and 63.8 GB size (or a 250 disk when both Android and RemixOS images should be stored on the same disk)