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.

Hi everyone,

my Pinetab2 suddenly stopped working after around 4 weeks of minor usage.
The main symptom is, that the display stays complete black when trying to power on.

As Pine64's support is unfortunately not very helpful and pointed me to the community, i'd really appreciate your help.

I was able to get the following out from UART-console:

Hello everyone,

I have got problem with the USB 3.0 Type A

No information in dmesg or journalctl -f -u systemd-udevd about any devices in this USB port.

$lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
Bus 008 Device 002: ID 258a:001e HAILUCK CO.,LTD USB KEYBOARD 
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$lsusb -tv
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
ID 1d6b:0001 Linux Foundation 1.1 root hub
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
ID 258a:001e
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
ID 258a:001e
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
ID 1d6b:0001 Linux Foundation 1.1 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ID 05e3:0608 Genesys Logic, Inc. Hub
|__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=mt7601u, 480M
ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub


I do not know if this could be hardware issue, OS (Manjaro) or anything else?

Thank you for advice and suggestions.

PS: I've just noticed this post with similar, possibly the same issues https://forum.manjaro.org/t/usb-port-bre...sue/139653

Testing a new Operating System like Apache NuttX RTOS (or Linux) can get painfully tedious on a Single-Board Computer… Swapping, reflashing and rebooting a MicroSD Card, again and again and again! (Like how we tested NuttX on PinePhone)

Thankfully there’s a better way: Booting NuttX (or Linux) over the Local Network, with U-Boot Bootloader and TFTP!

Today we’ll configure TFTP Network Boot on Star64, the new 64-bit RISC-V SBC. (Powered by StarFive JH7110 SoC)


Star64 JH7110 RISC-V SBC: Boot from Network with U-Boot and TFTP

SOLD *** SOLD *** SOLD

Owned for about 3 weeks, in factory condition w/updates. In new condition.  Small scratch on screen is on screen protector (that's what it's for), not screen. I do not have the original box.

I have too many projects and this is just a victim of my needing to focus.

US only, please. Ships from Washington, DC area.

https://www.ebay.com/itm/225668004563


 -Charles

The R4 resistor in my pinecil has failed, when I insert a dc jack I can see a tiny spark in a tiny crack inside the resistor. Is this likely to take down anything else hardware wise, like the mosfet directly in front of it?

Hello,

today I tried to boot my PinePhone Pro, but it doesn't boot.
- Battery is charged (used external Charger, bought new battery)
- I can connect it to my PC and see the device in MASKROM mode
- no led or vibration is noticable

Trying to boot the phone connected with UART got me following lines.

Hello

when I try to install the Driver CH341SER from CH341SER_LINUX.ZIP - 南京沁恒微电子股份有限公司 (wch.cn) for the Ayufan linux build. I get this error Message during the compilation:

With a new PPP, I am on stock software (Manjaro-Plasma, I believe).
I have installed necessary packages for compiling megi's userland software for ppkb.
Too, I have compiled it, and added the system service as I explained (in the wrong sub-forum) here,
PinePhone Keyboard won't work. read_kb_reg(PPKB_SYS_CONFIG) needs what? - https://forum.pine64.org/showthread.php?tid=18476

My PPKB charges but won't type.
lsmod ends with
pinephone_keyboard
but has no instance of kb151.
With the PPP firmly seated in my PPKB (and charging, battery staying at 100%), I tried the command
build/ppkb-i2c-flasher --rom-in firmware/build/fw-user.bin write reset
and saw
ERROR: I2C_RDWR failed: No such device or address

I did
rmmod pinephone_keyboard
and repeated the above. I had the same result.

Installing i2c-tools
pacman -S i2c-tools
had no effect on the command above.

I did see the following.
i2cdetect -l
i2c-0 i2c      rk3x-i2c                        I2C adapter
i2c-1 i2c      rk3x-i2c                        I2C adapter
i2c-3 i2c      rk3x-i2c                        I2C adapter
i2c-4 i2c      rk3x-i2c                        I2C adapter
i2c-5 i2c      rk3x-i2c                        I2C adapter
i2c-9 i2c      i2c-4-mux (chan_id 0)          I2C adapter

I can not blacklist anything b/c
update-initramfs -u
bash: update-initramfs: command not found

I installed both
mkinitcpio
mkinitcpio-busybox
and still can not update-initramfs.

As a user posted here,
keyboard case charging but not typing - https://forum.pine64.org/showthread.php?tid=17464
with the PPP firmly seated in the PPKB and booted therein, I too found,
dmesg | grep keyboard
pinephone-keyboard 2-0015: Keyboard was not found on the I2C bus, maybe it's disconnected.

How do I get "such device or address", shown above?

As root, I did,
pacman -Syu
pacman -S git php sdcc make gcc
As a normal user I did,
git clone https://megous.com/git/pinephone-keyboard
cd pinephone-keyboard
make all

As root, I continued with
cp -a Downloads/pinephone-keyboard/build/* /usr/local/bin/
vi /etc/systemd/system/ppkb-i2c-inputd.service
and added,
[Unit]
Description=Pinephone Keyboard Service Daemon

[Service]
Type=simple
ExecStart=/usr/local/bin/ppkb-i2c-inputd

[Install]
WantedBy=multi-user.target

I had no need to blacklist kbd51
lsmod | grep kbd
gave nothing. I did see
pinephone_keyboard    16384  0
at the end of lsmod.
I enabled the new systemd service.
systemctl enable ppkb-i2c-inputd.service
Created symlink /etc/systemd/system/multi-user.target.wants/ppkb-i2c-inputd.service → /etc/systemd/system/ppkb-i2c-inputd.service.
The following did/showed nothing.
systemctl start ppkb-i2c-inputd
ps ax | grep ppkb
gave no match.
I rebooted and found the same results both above and below.

The following command (with the PPP out of and in the ppkb) generated a WARNING and an ERROR.
pkb-i2c-inputd
WARNING: I2C_RDWR failed (6)
ERROR: read_kb_reg(PPKB_SYS_CONFIG) failed: No such device or address

Having inserted the PPP into the ppkb, I found that charging works.
The keys do not work.
How may I obtain "such device or address"?