Hi all,

I thought I would start a thread to help me decide whether to purchase a Rockpro64 or wait for the upcoming Hardrock64. I started a thread in the Rockpro64 section of the forum to decide whether I was asking a little to much of the SBC to host all the services , I would like and after a bit of discussion away from the forum, I think the Rockchip RK3399 SOC with Mali T860 MP4 GPU will more than meet my needs .

That being said I cant decide between the 2 devices which hold this chip and GPU, essentially the main objective is to have OpenMediaVault run as the main contender on the board with the other services in docker.

The rockpro64 with NAS case , PCI-e to Dual SATA-II Interface Card and 2 SSD's more than suits this need, but with the smaller form factor of the Hardrock64 and the minimal  difference in speed over usb 3.0 to sata cable,  compared to the PCI-e card is really enticing .

The Hardrock64 would provide me with a smaller form factor overall which is brilliant but the lack of a case and fan setup steers me back towards the Rockpro64 setup .

So I turn to the wisdom and opinions of the community to help me win the battle between the 2 contenders .

thanks in advance

Hello,
 
    I want to interface rockpro64 with external sensors with I2C, UART, SPI   and blinking led using GPIO pins, is there any liberay or example programs. I have installed Armbian_20.05.4 OS.

Regards,
Madhu K S

I read somewhere here that someone had ordered and received their Pinebook Pro with a larger eMMC.  Is it possible to do this?  I would like the 128Gb eMMC, but can't justify buying one separate and then ending up with a spare 64Gb one that I don't need.

Hi folks,

It is quite common for Android phones to share mobile broadband connection via wifi/bluetooth/usb to you can browse internet in other devices that doesn't have mobile broadband capabilities (aka tethering).

Has anyone tried to make tethering work with the pinephone? I guess the most difficult part would be to set the wireless interface in 'master' mode to be able to run hostapd or something similar... (IDK if the chipset supports master mode)

Thoughts?

Thanks!

# I am working on a new installation of Armbian for Rock64, and have been having an inordinate amount of trouble
# I was working and struggling mightily with getting full disk-encryption on the device.
# I now have another, more low-level problem: connecting to the internet.
# I don't know what is causing it, but suspect a random number generator required for ethernet may have stopped functioning.

===================================================================================================

# I verified the image I am using is the same one available at this time from:
$ wget https://dl.armbian.com/rock64/Buster_current
$ if [[ `md5sum file_i_used.img | cut -d ' ' -f1` == `md5sum Armbian_20.05.2_Rock64_buster_current_5.4.43.img | cut -d ' ' -f1` ]]; then
    echo MATCH;
    else echo DIFFERENT;
fi
| -> MATCH

# It's md5 checksum:
$ md5sum Armbian_20.05.2_Rock64_buster_current_5.4.43.img | cut -d ' ' -f1
| -> e0202e3887c8784d456eeab6f6ab2b11

===================================================================================================

# I discovered the internet connection problem quickly upon trying:
$ sudo apt install (package names)
| -> Could not resolve 'deb.debian.org'
| -> (With lots of other probably-irrelevant information)

# My first thought is to test network connections with ping:
$ ping 9.9.9.9
| -> connect: Network is unreachable
$ ping 192.168.1.254
| -> connect: Network is unreachable

# systemctl --state=failed reveals that haveged.service failed.
# grepping for the reason yields:
$ systemctl --state=failed | grep haveged.service
| -> haveged.service loaded failed failed Entropy daemon using the HAVEGE algorithm

# Checking journald, grepping for the relevant info I found:
$ sudo journalctl -xe | grep ip-config
| -> (...junk information removed...) device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
| -> (...junk information removed...) device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')

# I also check /var/log/syslog
# grepping for haveged yields:
$ sudo cat /var/log/syslog | grep haveged
| -> (...junk information...) "haveged[776]: haveged: Couldn't initialize HAVEGE rng 9"
| -> (...junk information...) "haveged[776]: haveged starting up"
| -> (...junk information...) "systemd[1]: haveged.service: Main process exited, code=exited, status=1/FAILURE"
| -> (...junk information...) "systemd[1]: haveged.service: Failed with result 'exit-code'."

===================================================================================================

# My next thought is to check the interfaces
# eth0 appears to be up:
$ sudo ifconfig
| -> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
| ->    RX packets 1 bytes 118 (118.9 B)
| ->    TX packets 245 bytes 42062 (41.0 KiB)
# Why not try to stop and restart it?
$ sudo ifdown eth0
| -> ifdown: unknown interface eth0
# It's still there:
$ sudo ifconfig
| -> (eth0 still listed)

# Can I stop and restart the loopback interface?
# I can:
$ sudo ifdown lo
| -> echo $? -> 0
$ sudo ifconfig
| -> (lo not listed)
$ sudo ifup lo
| -> echo $? -> 0
$ sudo ifconfig
| -> (lo listed)

# I add the following lines to both the /etc/network/interfaces and /etc/network/interfaces.default files,
# but nothing changed. This appears to be a pretty basic configuration So I don't know why:
"auto eth0"
"  allow-hotplug eth0"
"  iface eth0 inet dhcp"

===================================================================================================

# Something else new that caught my eye is that the board's red LED is blinking in a rhythm suggestive of the human heartbeat.
# I found this page regarding the LED, but that's all, and there's not much indication of what they really mean:
# https://forum.pine64.org/showthread.php?tid=5847

# I definitely don't have any heartbeat sensors attached, and I tried writing the same image to an SD card with the same results:
$ cat /sys/devices/platform/leds/leds/{standby,power}/trigger | egrep -o '\[\w+?\]'
| -> [heartbeat]
| -> [mmc0]

# The led indicating an ethernet cable is blinking normally
# I poked around using commands like the following to try and find ethernet-related LEDs but found nothing suggestive of ethernet:
$ find /sys/devices/platform/leds -type f
| -> nothing interesting
$ find /sys/firmware/devicetree/base/leds -type f
| -> nothing interesting

===================================================================================================

# Upon searching duckduckgo some more I find little that appears relevant
# This was one of the few things that looked promising:
# https://raspberrypi.stackexchange.com/qu...face#14107

# So I check the routing table:
$ sudo route -n
| -> Destination    Gateway    Genmask    Flags Metric Ref      Use Iface
| (None listed)

# Attempt to add default gateway manually:
$ sudo route add default gw 192.168.1.254
| -> SIOCADDRT: Network is unreachable

# what would raise error exit code 7?
$ echo $?
| -> 7

# Check routing table again -- nothing changed, still empty:
$ sudo route -n
| -> Destination    Gateway    Genmask    Flags Metric Ref      Use Iface
| (None listed)

===================================================================================================

I will post more updates as I continue to work on this problem.
Can anyone help?

What was the reason behind the increase in PineTab cost (Initially the standalone tablet was supposed to be $79.00 + $20 for the optional keyboard)?  or is this just a temporary increase for the Early Adopter shipment?

Also in the future could there be a lower cost PineTab (with NO battery) for an AC adapter powered tablet/kiosk application?  Would this also help lower cost of shipping and be orderable/shippable with other items?

-Lennie

Even though I received my PinePhone Braveheart months ago (albeit not using it as my daily driver), I just noticed that there are actually 2 screen protectors layered. The top one should be removed because it gets scratched very fast. Hence I thought the screen protector was of poor quality where as it does not seem to be actually. This info could be made clearer somewhere (in the box and/or in the store ?).

Just received my PINEPHONE - “Community Edition: UBports" Limited Edition Linux SmartPhone today and have a few questions.

What is the procedure to update the operating system? (see below)

I removed the plastic that covers the connections of the battery during shipment then booted up the phone.

I played around with the phone got the WiFi setup and connected.

Noticed the camera does not work just starts to a black screen, is there a fix for this, my first thought was to update the phone

The app store thing also never loads.


Thanks in advance.

Since I have a Braveheart v1.1 phone and can't used it due to known issues of excessive power drain (even when turned off), I created an Electron application using React to display a clock and my electrical provider's rate.  The app checks the electrical provider's rate every 5 minutes and when the cents/kilowatt hr is over 6.0, the screen turns red from green.

I will most likely ship the phone off to my father when I can get the USB CC and power drain components fixed.  This depends on Pine hooking up a person to solder/desolder the respective fixes.  Until then, it has become a mini screen on my entertainment center.

ps. don't judge my mess


https://drive.google.com/file/d/1uE_v0sR...sp=sharing

Hello,

today I got my Pinephone64. Unfortunately, the SD card cannot be used. It is recognized but is not automatically mounted. The camera is also unusable. I think this is due to the incorrectly integrated SD card. The SD card is displayed under External Drives. I can only format it or remove it safely. An error appears during formatting: "Format Error. There was an error when formatting the device". I can also mount the SD card in the terminal and access the files. Only it is not automatically integrated. I could solve this problem by integrating them into the terminal. However, the camera remains unusable. The trigger button is greyed out.
Does anyone have the same experience? What can I do to make the camera usable?

The device is not really usable for me.

Thanks in advance
Pavel