Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,094
» Latest member: minseow22
» Forum threads: 16,358
» Forum posts: 117,524

Full Statistics

Latest Threads
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 124
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 85
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,553
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
06-27-2026, 02:43 PM
» Replies: 13
» Views: 18,697
Android Gaming Image
Forum: Game Station Emulation
Last Post: Jacobgilbert
06-26-2026, 07:06 AM
» Replies: 52
» Views: 110,897
rAudio for Rock64 V2/Pine...
Forum: Linux on Rock64
Last Post: shinzuka
06-25-2026, 03:16 PM
» Replies: 11
» Views: 1,860
Big thanks for the docume...
Forum: General Discussion on Pinebook Pro
Last Post: alchemist
06-25-2026, 12:58 PM
» Replies: 0
» Views: 184
Mobian MMS/SMS text probl...
Forum: Mobian on PinePhone
Last Post: mehdy
06-23-2026, 06:53 AM
» Replies: 16
» Views: 34,463
OpenTTD game - Error: no ...
Forum: Mobian on PinePhone
Last Post: Mary_Davis
06-23-2026, 01:12 AM
» Replies: 3
» Views: 5,583
Libby - ebook reader that...
Forum: PineNote Software
Last Post: Mary_Davis
06-23-2026, 01:04 AM
» Replies: 5
» Views: 3,900

 
  Mac doesn't detect USB connection with PineA64+ 1GB using LCD touchscreen
Posted by: magna_shogun - 08-28-2017, 03:52 AM - Forum: Android on Pine A64(+) - No Replies

Hi, I hope someone will be able to help me. I've been trying to make it work for days.

My goal is to use the Pine64 with Android and the touchscreen to debug a game using Unity Remote. 
The board is PineA64+ 1GB, the touchscreen is the one from the Pine64 store (https://www.pine64.org/?product=7-lcd-to...reen-panel), the SD card is the 32GB card from the store (https://www.pine64.org/?product=32gb-microsd), and the Android is the 6.0.1 for LCD (http://wiki.pine64.org/index.php/Pine_A6...0170209.5D).
My computer OS is macOS Sierra (10.12.6).
 
I've installed the Android SDK using Android Studio (version 23.0.3 of the build-tools, since I use Android 6.0.1). When I use 'adb devices' to list the devices, it is not listed. But when I go to System Information to check if it's even detected, under Hardware > USB, nothing appears. So it seems that is not that 'adb' doesn't recognize the device, but the USB connection doesn't appear to be there; the computer doesn't detect it.

USB debugging is on, I've tried changing the USB mode between MTP and PTP, I've tried different USB ports from my laptop (if I connect my phone, Android too, it works in both), I've tried different USB cables, I've tried the different USB ports in the board (using Linux the USB ports work well, so I assume is something with Android, and not the board).

Could anyone help me? Should I use Android 5.1.1? Do I need to change some configuration, or install some app?

Thank you and best regards.


  Broken yellow Ethernet light?
Posted by: jl_678 - 08-27-2017, 03:11 PM - Forum: Linux on Rock64 - Replies (1)

Hi,

I am exploring my Rock64 and everything is currently going well.  It happily boots up and the Ethernet connection works perfectly.

The one thing that is odd is that only the green light on the Ethernet connection is lit.  It flashes periodically and I definitely have connectivity so things are working.  It is odd because almost every Ethernet connection that I have seen in the past have a solid green light to show the connection and a flashing yellow one to show traffic.  I do see that the Ethernet connector has a yellow light, but it is not lit.  Is this normal?

Thank you!


  Screen backlight accidentally zero %
Posted by: boubik - 08-27-2017, 12:55 PM - Forum: Linux on Pinebook - Replies (5)

Hi from Czech Republic, i am satisfied with my Pinebook 14", running original Linux MATE, however as I was changing slide bar of the screen brightness via touchpad, as i think there is no hardware shortcut like "Fn+something", i accidentally moved it to zero % and then manually switched off the Pinebook via long hold of the power button, so the screen is now after every log-in totally dark. I can run up Guest session, but once I log into my account, it becomes dark. External HDMI does not run (i never tested before, just tried now and TV says no signal). I know i can run up Terminal via shortcut CTRL+ALT+T, however what next then, step by step pls.? I tried to play with "xbacklight" advise in Guest session and also my account, but i am not sure i am doing the steps in correct synchronizations (blind typing, lack of Guest password knowledge, lack of knowledge if xbacklight is installed or not, etc.). Thx to experts to let me know fast!


  AOSP Build Steps Using github.com/ayufan-rock64/android-7.1
Posted by: birender.s - 08-27-2017, 08:19 AM - Forum: General Discussion on ROCK64 - Replies (15)

Please provide step-by-step method to build 
rock64_20170809_stock_android_7.1.2_sdboot.img
Using source code provided @
https://github.com/rock64-linux
https://github.com/rockchip-linux
https://source.android.com/
https://android.googlesource.com/

Major task is to merge rock64-linux code with full ASOP and build it for Rock64

Regards.


Thumbs Up solved: ROCK64 Stereo Audio POT-Board anyone having success getting sound?
Posted by: RockyBoulder - 08-27-2017, 06:49 AM - Forum: Rock64 Hardware and Accessories - Replies (7)

Hello everyone,

Last Monday I received my Rock64 including the ES9023 Audio POT-Board. Till now I don't have any success getting audio out of this board. aplay -l lists 3 cards. Card 1 is i2s device. I tried speaker-test, aplay  and mpd but and don't get any sound or error.

For example: 

Code:
speaker-test -c2 -D hw:1,0

claims to play noise but nothing is heard. Audio-Pot board is connected to a small Class-D amplifier with speakers. I am using ayufan's debian stretch minimal image. 


Did anyone got any sound out of the Audio-POT-Board? If yes: Which image/settings where used?

Thanx for your help.


Lightbulb Lang. Japanese
Posted by: Jews Jap - 08-27-2017, 05:55 AM - Forum: Linux on Rock64 - Replies (2)

When installing LanguageSupport of xenial-mate-rock64-0.4.17-85-arm64.img, fcitx-tool-gtk is missing.
Also, fcitx-mozc does not exist in the package.
fcitx-anthy is working normally.


  Eth0 dhcp issues
Posted by: LTronic - 08-27-2017, 03:10 AM - Forum: Linux on Rock64 - Replies (5)

Hello,

Pretty often at boot time my eth0 does not get an DHCP address assigned.
I have to play with

sudo dhclient
sudo ifconfig eth0 down
sudo ifconfig eth0 up

between 2 and 5 times to finally get network configuration from DHCP server.

Is it a known issue on Linux (happens on most images I have tested) ?
I have seen a similar thread on Android.

Well at least since latest ayufan fixes (0.5.1 images) we always get the same MAC address Smile


  Writeup About Pinebook
Posted by: dahni - 08-27-2017, 01:49 AM - Forum: General Discussion on Pinebook - Replies (4)

Hi everyone, just thought i'd share this article:
http://dt.iki.fi/pinebook/
i have outlined the whole process from getting the pinebook to having it work satisfactorily.
i really recommend the two distros i tried: Q4OS and armbian.


  Xenial Mate: Screensaver Preview & LibreOffice Slideshow problems
Posted by: moravecz - 08-26-2017, 09:59 PM - Forum: Linux on Rock64 - Replies (2)

Using Xenial Mate on Rock64 4GB, I have consistent problems with the Control Center Screensaver and the LibreOffice Impress Slideshow. 

In the Control Center Screensaver whenever I press the Preview button, the system locks up. The mouse cursor moves around, but both keyboard and mouse are not able to do anything.

In LibreOffice Impress, when I try to run a Slideshow (F5), the Slideshow is not seen, but the system appears to be locked up. The mouse cursor moves, but you cannot do anything on the desktop. However, if you press the Esc key, then LibreOffice Impress returns to normal mode. It seems like it tried to launch the Slideshow, but the Slideshow never appears.  Note that the LibreOffice Impress Slideshow function worked correctly and reliably in the Debian image Build 20170809. So there is something unique about the CXenial Mate image. 

Any suggestions would be very much appreciated.


Information How to Setup Serial Console Cable Over the Rock64 SBC
Posted by: MarkHaysHarris777 - 08-26-2017, 08:22 PM - Forum: Rock64 Hardware and Accessories - Replies (10)

Greetings,

The purpose of this photo blog is to provide a tutorial on setting up a serial console over the Rock64 ( or any other SBC ) from the Pinebook ( or any other notebook ) !


Materials & Preparation

You will need a usb extension cable ( two 1m cables will do ) and the CH340g usb to serial ttl bridge adapter carried by the Pine store.  Also you will need to have three  6"  F-F  jumper wires;  the ch340g is placed in short proximity to the Rock64 board and is attached to the Rock64 via the three F-F 6" jumper wires to the PI-2 bus, pins ( 6, 8, 10 ) covered later.  The usb extension cable(s) then run from the ch340g adapter to the notebook computer;  in this case the Pinebook.  You will also need to make sure you have serial terminal software installed ( I recommend the old standby minicom ).  We'll talk about that later as well.

Theory and Pinebook caveats

The theory is fairly straight-forward;  the Rock64 has a uart serial console port on the PI-2 bus pins (6, 8, 10) which allows another computer ( Pinebook ) to connect from usb port via the serial console adapter ( ch340g ).  

With the terminal software running , and all connections correct , you will be able to see the console messages from the Rock64 when the SBC boots, on the serial console terminal.  You can debug boot-up messages, also shutdown messages, as well logon to the Rock64 from the serial console after boot-up. 

         

The Pinebook usb ports are not identical.  For one thing the correct port ( pic on right ) is on a usb hub, and is designed to be used as a console.  The "incorrect" port to use ( pic on the left ) should not be used as a console.  Failure to heed the warning to use only the correct port ( the right-hand usb port ) will cause you endless frustration, grumpiness, and probably hair loss.  

Procedure

Make the Connections to the CH340g

                   

The pic at the left shows the connections on the CH340g;  the pic at the right shows the connections at the Rock64 SBC.  I like to Scotch tape the CH340g to the table top in close proximity to the Rock64;  so that the 6" F-F jumper wires can easily be connected.  The Tx, Rx, and gnd are in reference to the Rock64 SBC.  You will notice that the Rock64 Tx is connected to the CH340g Rx, and the Rock64 Rx is connected to the CH340g Tx.  The ground from the Rock64 is connected to the ground on the CH340g.  

                Rx-->Tx,   Tx-->Rx,    ground--ground

Notice that the gold jumper on the CH340g is set to select 3v3 logic level for the adapter.  This is critical.  Failure to observe this will irrevocably damage your Rock64 !  (words to the wise) 

The red LED on the CH340g is a power indicator;  there are other green LED(s) by the connectors which flicker during comms.  

Do not plug in the green Rx wire at this time;  this is the transmit (Tx) line from the CH340g and usually carries 3v3 even in idle which will "back feed" or bleed current into the Rock64 often keeping it from booting up !  We will wait to plug in the Rx line until after the boot-up and when we have a logon prompt on the console.

Plug in the usb cable extension into the CH340g;  this will run over to the Pinebook ( or other notebook ).

Plug in the USB Cable on the Pinebook and Start the Terminal Software 

Plug the other end of the usb extension cable into the Pinebook right-hand usb port ( note that the left-hand usb port is not suitable as a console port ).  Open a terminal on the Pinebook.  This terminal will become the serial console.  For now issue the following command to verify that the Pinebook can "see" the  CH340g serial adapter:

          dmesg  |tail  -n  10

You should see a line that says, " usb ch341-uart converter now attached to ttyUSBx ".  Pay attention to the ttyUSBx!  This will probably be ttyUSB0,  but it may be another value;  this is the device that you will enter when you start the minicom terminal emulation software for serial comms with the Rock64.

Start the console terminal emulation software ( minicom ) with the following command sequence:

          sudo  minicom  -s  -D  /dev/ttyUSB0  -b  1500000  --color=on

The  -s  flag will open the configuration menu when minicom initiates;  select "Serial Port Setup" and press enter.  On the serial port setup dialogue check your defaults ( 1500000 8N1  /dev/ttyUSB0 ) and make sure that hardware and software flow control are both NO;  then press the enter key.

Select  'Exit'  from the menu, and press the enter key;  the terminal emulation software will be running.

Note:   If your device ( found with dmesg ) was not /dev/ttyUSB0 then use your device in the minicom initialization command sequence !

Boot the Rock64 SBC

Apply power to the Rock64 SBC board and almost immediately the Rock64 boot-up messages will begin scrolling down the serial console terminal emulation software running on the Pinebook.  Congratulations! --  you have setup a serial console over your Rock64, using your Pinebook !   ... nice job.

When the logon prompt appears on the serial console then plug the green Rx line from the Rock64 into the CH340g Tx pin, and then logon to the Rock64 from the serial console on the Pinebook.  To shutdown the Rock64 enter:

                 sudo halt

You will be able to see the shutdown messages as well ! 


             


The pic above is the serial console running on my Pinebook over my production Rock64 running xenial-mate 0.4.16 #83.  You will notice the RED status bar at the bottom of the terminal.  You will not see this unless you grab the bottom edge of your terminal with your mouse and pull the bottom of the terminal down ONE line  ( 80x25 ). 

Shy