Hello,

I hope I'm right here. I experience a weird behaviour for some time now with my KDE Community Edition PinePhone:

As long as I touch the screen, the brightness goes to normal. As soon as I lift my finger, the screen dims down to minimum immediatly.
The problem does not appear, as long as the phone is charging. But if it is not connected to the charger, the Pinephone is unusable like this. Shortly everything was ok, maybe this has come from a recent update.

What could be the reason? System is up to date...

Not every time, but sometimes when trying to power the phone off, an error appears and I get a mouse pointer. But the screen is too dark to read the error message (even with flashlight). The phone stays in this state until powering it of the hard way.

I found this thread which might provide a solution. But I'd prefer not to touch system files.
Did anybody experience this and solved it?

I have had lots of issues trying to get Mobian to work and I am confused by my most recent problem.  Maybe one of you have resolved this issue.

Background: I could not get the latest installer (mobian-installer-pinetab-phosh-alpha5.img.gz) or the latest build (mobian-pinetab-phosh-20210314.img.gz) to work by flashing the eMMC using JumpDrive 0.7 with bmap or dd.  I tried both encrypted and unencrypted with the installer.  The installer finished, but both choices resulted in a system that did not boot.  With the latest build, it would resize, and then go to black.  Reboots would flash the Mobian logo and then be black.  I started flashing older builds using the same process with success.  I do not have the serial cable to investigate the black screen issue further.

Now I am having trouble updating the old builds (mobian-pinetab-phosh-20201215.img.gz) to the latest version.  If I use the Software app and try to update, I run into the "Gnome Software (gnome-software) unable to download updates" issue listed on the troubleshooting section of the Mobian wiki [1].

The wiki suggests running these commands using King's Cross app:

Read the blog entry by @JF002 discussing the release of InifiniTime 1.0 for the PineTime.

Read now

Hi all,

I received my pinepower desktop earlier this week, and seems to be working fine when just used for charging devices.

However, when using the pinepower to supply power to a Raspberry Pi 4 (or even to a Lattepanda Alpha) through the type-C port, I'm seeing that the output power just drops then returns randomly, resulting in the SBCs to reboot, and that even multiple times per day. 

Initially I thought this was because of me plugging and unplugging the usb cable to charge my pinephone on the quickcharge port, but apparently, after leaving the pinepower desktop on overnight, I figured that the SBCs had rebooted multiple times!

It is strange to see this behaviour, and I would like to know if anyone else is experiencing this issue.

I'm aware the device is promoted as a charger, but I would like to know if this is considered normal.

Thanks!

PS: Feel free to move this message to a different thread if needed, because apparently there is no dedicated forum for the PinePower desktop to this day.

Hello there,

I have a Rock64 4GB Board, powered by POE and running Ubuntu 18.04.5 LTS (by Ayufan), Booting from microSD, no eMMC installed.
With fresh installations everything works great (i mean bare OS and no other applications), My intention of buying this board is to move away from RPi3B
for my Home Assistant system. I believe Rock64 is much more powerful CPU and extra RAM can provide a better environment.

However after migrating my working Home Assistant from RPi-3B to Rock64, Rock-64 started crashing immediately after boot with kernel panic.

I was able to take a short video to read what's going on with system and below are few lines which hets printed on console at panic.
Note that I have a oversized fan constantly blowing air on Rock64 and Heatsink is also installed on CPU.

Any help to resolve this issue will be appreciated..  ( I believe this is not too unstable system and can at least handle load what RPi-3B was doing past 2 years)


---- ERROR LOGS ---
INFO: task systems:885 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Kernel panic - not syncing: hung_task: blocked tasks
----
----  few more lines here with exception stack... 
----
Kernel Offset: disabled
Memory Limit: none

rockchip-thermal ff250000:tsadc: channel 0: temprature(48 C)
THERMAL REGS:
<SOME ADDRESSES IN BINARY>
Rebooting in 10 seconds

Hi all,
  I try to boot over the network (PXE boot) and follow the tutorial https://forum.pine64.org/showthread.php?tid=6814 with the Armbian image. After some hours to understand at the end that iptables was blocking the tftp connection I was able to boot but I cannot login : it is stuck when I enter the login or new password.
Do you have an idea of how to solve this issue ? root mount error ? NFS problem ?

LMM

Hello!

I'm looking into buying a pinetime, but there are a few features I would need:
- Ability to sync time with a degoogled Android phone or a Linux desktop os 
- Alarms
- Count down timer
- Ability to write/install custom apps

Do infinitime and the 1.0 release include this?

Thanks!

hello
i would like get vpn or tor working. is there a way for an average user to do that?

Hi all. I am trying to find a Rasberry clone to drastically 
modify but remain backwards compatable with the RPi.
My planned redesigns are cutting edge .
My final goal is a slim and cool looking VR / AR harness
that is light and comfy to wear day2day, but still robust and water 
resilient, so I'm looking at RK35xx based SBCs that claim
  an open hardware layout and wiring /connectivity architecture.

Radxa seams to slowly start up their community,
but Pine64 is ready and up and running.

Is there a chance that the Quartz64 physical wiring
 layout layers  will be published? or that someone 
at Pine64 can authorize me to receive such files?
Sincere regards:

Daniel +972

Hello,

I am trying to use the RaspBee ZigBee Module with my P64-LTS and wanted to connect it to uart3 / uart4 on the Euelr bus and power it with the 5V/GND pins on the Euler header. I power my P64 LTS via the 3.5mm Barrel Power and I also connect the official 7"LCD via the DSI connector

The pinout of the module

I wired the module with cables as follows:

Module    Euler

pin  8      pin 24 (uart3 tx)
pin 10     pin 23 (uart3 rx)
pin  2      pin  8 (5V)
pin  6      pin  6 (GND)

As sonn as I plug the power the board produces a "whining noise" and is not booting. The LCD is complete white and the small green LED is flickering and not very bright. As long as I use external 5V supply for the Module and disconnect it from 5V/GND on the Euler bus the board boots normally and I can access the module via the uart.