Overall Manjaro has worked fairly well. I was able to get printing working and sort out getting most of the KDE-PIM packages working. It seems to me those issues should be sorted out and working out of the box.

I have not been able to get Akregator working. It freezes up when I go to fetch feeds. And if I am using it inside Kontact, it freezes up Kontact as well. I have searched the web in general for solutions and used the Arch Wiki as well without finding anything relating to this problem.

If anyone has any ideas on a solution to get Akregator working in Manjaro for the Pinebook Pro I would appreciate some assistance.

thank you
bill

I have a problem with the Rockpro64.
 
I have used a microSD with ARMBIAN like a OS (Kernel 4.4.213-rockchip64) , and the board work good.
But when I try to restart the os with the command reboot of Linux, the os shutdown but it doesn't boot.
 
I must necessarily turn  off and turn on  the electricity, but this is not possible remotely.



The board is connected to:
- an ATX power supply; 
- PCI-E controller whit 6-port (with n.3 hdd  + 1 ssd )
- RTC Battery CR2032

do you have any suggestions?

Hello community

I want use my Rock64 as TvHeadend.

What is the best image to do this?
I dont have experience with this.

I tried Libreelec, I seen to run unstable and slow, compared to my Odroid C2.
Android Images, I found only Android TV Images on download site, running Kodi even more slow.

So I stopped using the Rock64 for Kodi.

But I wrote that TvHeadend works well on Rock64.
I want to use it for IPTV and possible DVB S.

What is the most stable and fast Image to install/use TvHeadend?

Debian Stretch, Ubuntu or Libreelec?

I want to use it with Timeshift and recording on USB 3.0 HDD.
By the way, does the hardware allow transcoding?

I own a 64GB eMMC on a Rock64 v2.0

Thanks a lot for your help!!!

Tetterl

changes , When you swipe up , gives recent /missed , should make it easier when strapped to your dashboard

Using the latest BUSTER DEBIAN version available as of today, the LCD does not work. Only HDMI even after adding the line
pine64_lcd=on
in the proper file (/boot/armbianEnv.txt).
How can one make the LCD work with that OS?

There are lots of 1920x1200 MIPI LCD with CTP available on the market.
Their pinout can easily be connected to that of the ROCK64Pro MIPI connectors via a simple board that would connect the proper pins together so from a HW point of view it is pretty straightforward.
My question is would it work straight out of the box or is there a need to modify the kernel or some initialization files to get a specific MIPI LCD screen to display with the ROCK64Pro.
Any help guiding towards what should be done from a SW point of view would be greatly appreciated. Thank you!

Hi,
I was just curious to know whether eMMC chips not from PINE64 which are greater than 128 GB will work on the Pinebook Pro. 

Also, is there any way to dual boot 2 Linux distros (the default Debian and Manjaro) on the eMMC?

Anyone else have charging issues with SFOS on their BHs?  I'm running the latest SFOS image from a SD card.  The modem/phone/battery get VERY HOT when connected to various chargers.  So hot, the CPU shut down last night.  Tried using a Google Pixel charger, Amazon Kindle charger, OnePlus charger, both with Pine64 cable...  SFOS runs great on the BH, but this battery/charging issues is too much...  I have to pull the SD card w/SFOS and charge it while running UT off the eMMc.

Manjaro KDE. I was using sound converter to convert since wav to flac format. My pbp per light started flashing alternating red and green and now the system will not not at all into the nvme. I have to get data of off that nvme drive. Ideas?

So, I would like to use the pinephone to learn more about device driver kernel modules in linux and device nodes. My main goal would be to write a kernel module that I can load, to control an LED in user space but I know, that's a long way to go.  As you can see, there's going to be some very naive things I'm going to say, so please bear with me... I'd really like to know how this works!

I am fairly new to the subject and by now I was only developing firmware for STM32 devices and some software backend things, but no embedded linux at all. On a microcontroller I would look up on which GPIO pin the LED is connected, then search the programming manual for the registers that configure and controle the pin and write to those register addresses.

Still, I think I know at least SOME things about how the linux kernel works. Correct me if I'm wrong, but I suppose there is a kernel module which is basically executable machine code and does the "writing-to-register-addresses"-part? This module can be "loaded" in order to control a peripheral. The module then uses files (or nodes) to offer some sort of interface to applications in user space, in order to easily control the peripheral. These files are located either in /sys or /dev (I guess?). Is that kind of true so far? I already saw the files that can be used to turn an LED on or off in /sys/platform/leds/leds/.

If the above isn't too far off, I have many follow-up questions, but one after the other. 
It would be really kind if someone would like to take time and provide some inside knowledge and just help me find my way here!