I want to set up a serial connection from raspberry pi 2 bus but don't know what the device would be called in regards to /dev/tty*. It is wired correctly but because the raspberry pi is different to pine64 system the tutorial stopped there.

Hello
I am trying to run Tvheadend over Ubuntu 16.04 LTS (GNU/Linux 3.10.102-3-pine64-longsleep aarch64)
with dongle Bus 001 Device 002: ID 0572:c688 Conexant Systems (Rockwell), Inc. Geniatech T230 DVB-T2 TV Stick
I couldn't make the compile of tvheadend so i have used a prepared .deb file and the service is working just fine. the thing is that the DVB dongle is not recognised on the Tvheadend.


some1 can help?

Hi

Many of the threads here on the forums, when talking about burning operating system images mention the use of Win32DiskImager. But there is a better alternative called Etcher.

It's user-friendly, open source, cross-platform, and most importantly, it verifies that a burn has been completed successfully.

You can download it here.

Hello, 

My end goal is to use this with a plex media client connected to my TV and audio receiver via HDMI and get surround sound.

I have tested Android 5.1 which as far as I know is not capable of surround sound, I assumed that it would because my nexus player running the same software did support surround sound, I was wrong. I thought that perhaps the nexus was running Android TV OS, so that could be the issue. I have tested Android TV, that also does not produce surround sound, only stero sound via my receiver.

My question is, is there any software (remix, Linux) that can supports surround sound via HDMI? If so, is it possible to run plex from that OS?


Not sure why the nexus player is capable of playing surround sound but this is not, from what I understand it is more complicated than them sharing similair OS.


If anyone could point me in any direction it would be appreciated. I checked the forums in each OS but couldn't find anything to confirm this works.

Hi all. The Pine64 Debian Xfce image does not detect my LCD monitor resolution correctly. For some reason it is using 1280 x 760 or such. The correct resolution is 1920 x 1080. The Pine64 Ubuntu mate image does not suffer from this problem - It works at the correct resolution. My OpenSuse Desktop also uses this monitor at 1920 x 1080.  Any ideas on how to address this?

Tested on a Pine64+ 1GB running Debian 8 “jessie” (3.10.102-3) using the official WIFI 802.11BGN/BLUETOOTH 4.0 Module.

What's it all about? These were the steps I followed to be able to view the text output of a bluetooth-enabled USB power meter, and most of these steps apply to getting bluetooth working at all if it isn't already configured in your chosen image. If it is already enabled, you can probably jump straight to step 5. Regardless, steps 1-5 should get your bluetooth working and a device paired with your pine64, but what you do after that if you don't want the text output (ie. you instead want a bluetooth mouse, audio) like I did I wouldn't know! ;)


Step 1: Make sure you have the bluetooth stack and utilities installed! If you want to all make sure you have  all of the stuff this guide uses in one hit, you can add "rfkill git screen minicom" to the list of stuff to install.
sudo apt-get install bluez


Step 2: Get the firmware binaries for the BT from https://github.com/lwfinger/rtl8723bs_bt

This repo contains the programs and firmware to operate the Bluetooth section of the RTL8723BS. This basically loads the firmware into the module, which makes it a bluetooth module! if you don't have git, install it by running "sudo apt-get install git".

Quote:git clone https://github.com/lwfinger/rtl8723bs_bt.git

Quote:sudo ./start_bt.sh

Quote:sudo rfkill list

Quote:0: sunxi-bt: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

Quote:sudo rfkill unblock 3

Quote:Devices:
hci0 34:C3:D2:71:BE:ED

Quote:power on
agent on
default-agent

Quote:[NEW] Controller 34:C3:D2:71:BE:ED pine64 [default]
[NEW] Device 00:BA:55:56:D8:7E SPP-CA
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful

Quote:sudo rfcomm bind hci0 00:BA:55:56:D8:7E

Quote:sudo screen /dev/rfcomm0 9600

Quote:sudo minicom -D /dev/rfcomm0 -b 9600

Quote:052496,005516
052496,005420

• https://github.com/lwfinger/rtl8723bs_bt – info on compiling and installing the BT firmware
  
• http://forum.pine64.org/showthread.php?t...1#pid19891 – post by another Pine64 user, Arjun, detailing how to use bluetoothctl
  
• http://forum.pine64.org/showthread.php?tid=1392 – posts by xalius and Faye on getting the BT firmware loaded and unblocked.
  
• Bashing my head against a screen for an afternoon and finally winning! :D
  

Coming soon on Linux...



Currently, it only lasted for 5 to 6 seconds before my Pine powers down (i guess it is due to not enough power) , which means i can't test it out to see if it's truly working or not.

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