Hello!

I'm experimenting on running sway on PineTab2. My idea would be to use it together with the keyboard attached and sometime detach to read or doing stuff that are not keyboard heavy.

I managed to rotate the screen to landscape mode manually by running:
$ swaymsg output DSI-1 transform 90

This is fine, except that if I try to use the touchscreen it seems like the touch gestures "didn't rotate" together with the screen, i.e., I need to swipe left and right in order to scroll up and down when I'm reading a text.

Does anyone know what might be causing this? What is the KDE WM doing besides just rotating the output to match the gestures?

Hello, I used arch with FDE in the past with this script https://github.com/dreemurrs-embedded/ar...-installer
I used to work fine, but I tested a few months ago and could not install anymore, is it working again now?
Another question, how is the support of tow-boot in arch+pinephone?

Just installed. Has internet, but no audio. Did full update. Restarted. No audio through headphones or the internal speaker. What do?

Was curious if there's anyway to reflash the chip inside the pinephone? Even if it's stock, I would like to go through the process of reflashing this chip. Even better if there are updates from sunxi.

I saw this: https://forum.pine64.org/showthread.php?...4+firmware

Which points to here:

https://linux-sunxi.org/Pine64#Boot_sequence
https://linux-sunxi.org/BROM#A64

So I'm assuming I can use FEL somehow?

Where do I download the firmware hopefully with a hash to check integrity and what's the process to reflash it?

And a question about Pinephone PRO. It has SPI flash? Does that mean there is no BROM in the allwinner chip? Or is the same, and just boots from SPI instead of emmc?

Thank you.

Hi everyone,

I want to be able to run kali off of the pinebook pro as needed via the SD card. I followed the Pinebook Pro installation instructions here: https://www.kali.org/docs/arm/pinebook/

* Download and validate the kali linux image
* flash the kali-linux-2023.2-pinebook-pro-arm64.img file to the SD card (note, no errors or issues took place on flashing the SD card)
* insert the SD card to the pinebook pro
* start the machine

From here, I'll see what appears to be the boot process loading which is a wall of text. Note that I saw several "FAILED" "Failed to start ssh.service - OpenBSD SecureShell error, etc.

kali-pinebook-pro login: 
password:

After the booting process stops, I am dropped into a CLI login screen. I attempt to use the kali login defaults e.g. username: kali and password kali which shows as invalid. Does anyone have the default login and password or can we determine if I did something horribly wrong?



Thank you!

Iv'e got my pine tab 2 to boot once again and the only thing it says is [    0.000000] clk: failed to reparent gpll to clk_rtc32k_frac: -22 it repeats this line 1 more time and below both lines I get a flashing cursor  does anybody out there know what it means? and what do I need to do to get it run again? please thisis driving me nuts pine64 insists that the community will help please!

Hi
As a new raspberry->pine64 I'm lost in all model options and I find it confusing.
I think a comparison sheet would/table would bring benefit to all buyers to see which on is the most modern which on lack what.

For QUARTZ64 Model-B I found info it can handle 3-pin li-po charging with temp. sensing.

The page for Model-B does not mention it.
So does it mean it's gone in model B?

It's a bit of a hike to get to the end of compiling and installing, but once done, box86/WINE performs admirably on the PP Community phone/physical keyboard.

In xfce (though not in Manjaro Phosh, oddly), LibreOffice has laggy typing, but Word 97, despite its 20-second start-up, has none, and once the program is up, it's as robust as anything on the PP. All its features function and it works with the phone's suspend.

HanDBase, my favorite cross-platform database app, also does its job.

I installed an NVMe drive into my Pinebook Pro. I booted into Majaro from a MicroSD card, blew away the "ROOT_MNJRO" partition from the eMMC drive, and then use the Manjaro flash utility to flash Manjaro Arm for Pinebook to the NVMe drive. On reboot, I completed the setup, rebooted, and then there's no wifi, no audio, connecting my USB ethernet dongle doesn't get recognized, even the power button doesn't work. *UPDATE* The power button does work now.** If I flash this image to the eMMC drive, everything works fine. The same image works fine from the microSD card. For some reason, only when I flash the image to NVMe do I lose all of the functionality of the Pinebook Pro, though I can open a terminal and folders. Hoping someone here can point me in the right direction.

I've been trying to write a Python application for the Pinephone that needs access to the camera.

1. My first iteration was using python-opencv, but that doesn't work out of the box.
The simple first two lines:
```
import cv2
cap = cv2.VideoCapture(0)
```
produce the following error:
```
[ WARN:0@18.736] global ./modules/videoio/src/cap_gstreamer.cpp (2401) handleMessage OpenCV | GStreamer warning: Embedded video playback halted; module v4l2src0 reported: Device '/dev/video0' is not a capture device.
[ WARN:0@18.739] global ./modules/videoio/src/cap_gstreamer.cpp (1356) open OpenCV | GStreamer warning: unable to start pipeline
[ WARN:0@18.740] global ./modules/videoio/src/cap_gstreamer.cpp (862) isPipelinePlaying OpenCV | GStreamer warning: GStreamer: pipeline have not been created
[ WARN:0@18.758] global ./modules/videoio/src/cap_v4l.cpp (902) open VIDEOIO(V4L2:/dev/video0): can't open camera by index

```
There is some discussion about this problem in a manjaro forum: https://forum.manjaro.org/t/access-pinep...encv/94593
but there are no conclusive solutions.

I have two possible work-around to this issue:

2. I could build a python library reusing "megapixels" code (https://gitlab.com/postmarketOS/megapixels). By the way, there is a very interesting description of the pinephone camera interface in the README in that repository.

3. Or I could call an external command from my python executable that gets me the actual camera data, for example `ffmpeg` similarly to this blog post: https://blog.brixit.nl/camera-on-the-pinephone/

In my opinion, solution 3 is ugly and probably under-performant, while 2 seems overkill.
There should be a simple way to read the camera data natively from Python.

If anyone can give me a solution or a hint, I would really appreciate it.