Question is the title.

Thanks in advance!

So testing on multiple images (pmOS & debian) there is a new behavior showing up for me on my Pinephone where instead of the normal /dev/ttyUSB{1,2,3} showing up; instead now /dev/ttyS{0,2,3} shows up.

I can still see the modem is functional as I can `screen /dev/ttyS2 115200` and play around with `AT` commands; however modemmanager completely ignores /dev/ttyS* devices (there maybe a fix for mm by forcing it to use ttyS* and pointing it to the quectel plugin - but this shouldn't be needed...).

As well, booting up the factorytest image that the device shipped with and trying the modem test - it just shows "Waiting for modem" for a few minutes and then "Boot timeout".

The strange thing is this just started happening all of the sudden and things used to work fine and show up as ttyUSB* - only thing I can think of is maybe force shutting down messed something up (have a habit of just pulling battery out of phone to restart).

Anyone have an idea of how to debug/fix this?

After installing zram, my PBP still froze due to lack of memory, which required reboot.

So I installed Earlyoom, which kills the process it estimates abuse when memory is full.

Installation is very easy: just follow the download and compilation instructions.

You must install the git package to download and the base-devel meta-package to compile.

You can install go and cppcheck if you want to run the built-in self-tests. I don't know if it's usefull.

Earlyoom tries to guess what is the "right" process to kill. For me, this is always the youtube.com tab process of Chromium, which is a good decision because this page can use more than 1go (!) of memory. At the same time, it is not an important tab.

I also tested several memory limits before letting earlyoom go into action.

By default, earlyoom kills a process if available memory and free swap is less than 10%. I lowered this value to 2% for both without preventing earlyoom from working properly. For values less than 1%, the computer freezes before the intervention of earlyoom.

2% may be too low ( <=> 80 Mo for memory, 20 Mo for swap), but for now, earlyoom kill nasty process without problem with this value. If the computer freezes again, I will increase this value.

Thanks in advance for taking the time of reading this and possibly trying to help.

I recently got a 1 GB ROCK64, and I want to install DietPi on it. I have a 32 GB Class 10 micro SD card, a Realtek RTL8188EU Wi-FI USB dongle and a wireless keyboard + mouse combo, so up to this point I assume I'm properly equipped for the installation. The thing is I don't have any 1080p TVs or monitors (I live in Venezuela), but I do have an HDMI to VGA converter, which I'm planning to use with a 1280x1024 monitor. It also supports other resolutions, such as 800x600.

I already tried flashing the image to the micro SD card using Etcher, and the ROCK64 seems to boot up but no image appears on screen. I presume that it is booting up because the mouse turns on when I power the ROCK64.

Although I'm a Linux user, I'm completely new to the SBC world. Please, do keep that in mind.

I want to know how to change the resolution so I can proceed with the installation. I already tried Googling this issue, and even though there is comprehensive information on the subject, I couldn't find a specific solution for the ROCK64. I don't know which file I have to edit to change the resolution of the output.

I presume the issue is exclusively the output resolution, but I can't be sure. I hope someone more experienced can tell me what possibly could be wrong.

I have to add that all 3 lights of the board turn on and stay like that. I haven't tried leaving the board on for a while.

Disclaimer: I already posted this on the DietPi forum, but I haven't received an answer from them after a day. I figured that a ROCK64 forum was more likely to help me.

Has somebody an idea if it would be possible to solder-in some support for NFC?
(e.g.: so the watch could communicate with continuous glycaemia monitors like this, for which there is already opensource code available)

Does anyone have an idea of about how much the Pinebook Pro usb-c hub will cost? I know the blog update said it is still in its early stages, but a rough estimate would be really nice.

Hello,

I had an older version of Manjaro-ARM-Xfce on my emmc. Had no trouble installing it to the emmc thanks to the
emmc-installers I found @ Manjaro. Now I wanted to do a clean install of Manjaro-ARM-kde-plasma-pbpro-20.04. I tried the Write-to-eMMC-version of it,
but the Pinebook simply refused to boot after inserting the sd card. (The on light was green but the display empty for a considerable period before I gave up). I decided that I might as well go the direct way and flashed Manjaro-ARM-kde-plasma-pbpro-20.04.img on the eMMC with the eMMC-USB-Connector and dd. 

After starting the pinebook on led goes green, but the display remains empty. How do I go from here? Shouldnt reflashing the eMMC turn back the clock and give me a clean
system? Should I try another image and possible another tool than dd to write the image to the eMMC. How long should the initial boot last, meaning how long do I have to wait 
with Manjaro KDE Plasma until something appears on the screen for the first time. Is 20.04 considered stable?

Yours sincerely
Stefan

I've tried for a week now. I've followed the ubports install instructions on multiple sd cards and on the emmc using jumpdrive. Nothing works.
I get a ubuntu logo, some non working progress dots, a flickering screen. Sometimes I get to the setup app, it crashes before I can finish.


I had ubports running well on the emmc before the ota img was available, what's gone wrong?

Hello,

I've recently started playing with my BH pinephone. Unfortunately it seems my Volume up button is unresponsive at best.
Has anyone else had any similar experience?

It seems like the button is not making proper contact, however I am unsure on how to remove the back cover properly there seems to be more to it than just unscrewing the screws.

Any help is greatly appreciated.

OK, I charged the phone up for the first time and was able to turn it on and after a while it went dead.

Tried to recharge it but no indicator light to say its charging.

Any ideas?

Thanks.

Sent from my LYA-L09 using Tapatalk