Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,713
» Latest member: vicentewilson
» Forum threads: 16,264
» Forum posts: 117,212

Full Statistics

Latest Threads
what is the point?
Forum: General Discussion on PinePhone
Last Post: biketool
7 hours ago
» Replies: 6
» Views: 275
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
Yesterday, 07:38 AM
» Replies: 3
» Views: 11,849
Danctnix USB GPS for Pine...
Forum: PineTab Software
Last Post: biketool
Yesterday, 06:09 AM
» Replies: 0
» Views: 62
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: biketool
Yesterday, 03:39 AM
» Replies: 10
» Views: 6,783
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: realchunkyflea
11-27-2025, 05:01 PM
» Replies: 3
» Views: 316
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-27-2025, 04:23 PM
» Replies: 2
» Views: 104
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
11-27-2025, 10:30 AM
» Replies: 10
» Views: 15,931
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
11-26-2025, 02:45 PM
» Replies: 10
» Views: 16,861
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: j_s
11-26-2025, 11:33 AM
» Replies: 4
» Views: 314
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
11-26-2025, 01:42 AM
» Replies: 1
» Views: 199

 
  Lockup during update, force shut down and try again?
Posted by: tgz - 01-06-2021, 06:33 PM - Forum: Manjaro on PinePhone - Replies (5)

Hello, I purchased a used Manjaro Convergence Pinephone package that was allegedly only used for a couple of hours, unknown what occurred during that time. Tried to update first thing as I read that is very important, the phone kept locking up after a few minutes, I was forcing shut down with the power button. Long story short, fixed bad wi-fi at home (weak signal to very strong), finally was able to start an update.

So I just said yes to everything (wanted to get through it before another lock up), update went on for quite a bit, that is, this is the longest I had seen activity without lock up. However, the phone has now locked up without completing the update. Should I just force shut down with the power button and try to update again? Don't know what else, it is locked up anyway Smile
thanks
Edit: forgot to mention, the red light is flashing. Not sure if it was doing that in previous lockups.

update: I did force a shut down, keypad would then not show on terminal, tried shut down through normal button, for the first time I got a "something went wrong, log out try again". good!
update: met again with "(unable to lock database)", had found instructions earlier which had allowed previous update to begin. going to run it again:
sudo rm /var/lib/pacman/db.lck
then
sudo pacman -Syu

update: it looked like the update started again where it left off. I again said 'yes' to everything. After update there were many "file is corrupted, do you want to delete it", I said yes a bunch of times then get: "Errors occurred, no packages were upgraded." Going to try update again. The good news is... this is the longest the phone has been on without locking up!

update: ran update again, 255 "checking package integrity", looks like I'm back at the same place: invalid or corrupted package (pgp signature), do you want to delete it
Phone still has not locked up, good!

OK, so again "errors occurred, no packages were updated" How can I update? I did update mirrors before I started all this. Tried again, met with "unable to lock database". Should I be having to run sudo rm /var/lib/pacman/db.lck every time?


  Need a working copy of pacman.conf
Posted by: WaldoTheRanger - 01-06-2021, 10:56 AM - Forum: PinePhone Software - Replies (2)

Hello. Pretty simple issue.
I borked my own conf file, and I don't see any other place to get a new one.
I think I need pamac.conf as well.
so if someone could just upload those that would be awesome.


  Regarding S3 h.264 hardware encoder... using examples from OrangePi
Posted by: appoli - 01-06-2021, 04:04 AM - Forum: Development Discussion on PineCube - Replies (1)

Hi all,

Just registered for the forum, but I’ve dancing around the Pine-world for some time (even have an OG Pine64 SBC I got from the first Kickstarter laying around somewhere...). 

I saw that the Pinecil was released & while I don’t *need* another soldering iron I had always wanted to check out a TS80/100, but couldn’t justify the price (once I decided I needed something decent I got a Metcal SP-200 in very good condition for $70 + a couple tips. It’s no MX-5000, but gets the job done quite nicely for about as much as the aforementioned Chinese irons!). I dig a lot about the Pinecil & the low cost, USB-PD & other bits means I could find a use for it. So I figured I might as well consider all the Pine offerings if I am to buy some Pine kit and then I saw the PineCube & intrigued I became Smile

Long story short - the wiki says that currently ‘we don’t know how to use the hw encoder yet’. Doing a quick Google I saw that there are a couple GitHub projects making use of the S3 chips hw encoder (from an OrangePi) running Armbian & have basic examples that include using it to encode a live camera stream. 

I’ll probably scoop one regardless if for no other reason than to toy around with/possibly use as a 3D printer cam, but figured I’d throw this out there in the off chance that no one had checked the existing projects for something that might be a drop-in:

https://github.com/rosimildo/videoenc (There are others, this seemed to be one of the more recent ones). 

Thanks!


  Article: Control PineCone BL602 RGB LED with GPIO and PWM
Posted by: lupyuen - 01-06-2021, 03:35 AM - Forum: General - No Replies

Explore the BL602 GPIO and PWM Demo Firmware... And how they call the GPIO and PWM Hardware Abstraction Layer

Control PineCone BL602 RGB LED with GPIO and PWM


  Thoughts on 30 day hardware warranty?
Posted by: bartleby - 01-06-2021, 02:24 AM - Forum: General Discussion on PinePhone - Replies (10)

What are the community's thoughts about the 30 day hardware warranty on the Pinephone?  It's basically what's been holding me back from pulling the trigger on one.  In light of the recent news about the upcoming retail channel, I posted comments there and under the December update asking this question, and even tried to PM Lukasz but never heard back.  I was wondering if there were plans this year for a more traditional warranty than the 30 days.  I'm a Linux enthusiast so I feel right at home in the community (and not the retail channel), but, one's Linux or software expertise has nothing to do with the risk of developing a hardware problem after 30 days.  Perhaps is the concern not so great because the hardware is so inexpensive and the boards can be purchased and replaced?


  The camera does v4l2
Posted by: ab1jx - 01-05-2021, 08:13 PM - Forum: Linux on Pinebook Pro - Replies (2)

I haven't brought myself to install Cheese because it's Gnome.  But I have another USB webcam (which this is) and even in OpenBSD it can do v4l2 (Video For Linux 2).  I'm In Bullseye, I did
modprobe uvcvideo and lsusb shows (maybe it did before):
Bus 002 Device 003: ID 0c45:6321 Microdia HP Integrated Webcam

Installed a few v4l2 things, I don't really know what I'm doing.

Code:
v4l2-ctl --list-devices
rockchip,rk3399-vpu-enc (platform: hantro-vpu):
/dev/video0
/dev/video1
/dev/media0

rockchip-rga (platform:rga):
/dev/video4

USB Camera: USB Camera (usb-fe3c0000.usb-1.2):
/dev/video2
/dev/video3
/dev/media1

-------------
v4l2-ctl --all
Driver Info:
Driver name      : hantro-vpu
Card type        : rockchip,rk3399-vpu-enc
Bus info        : platform: hantro-vpu
Driver version  : 5.7.19
Capabilities    : 0x84204000
Video Memory-to-Memory Multiplanar
Streaming
Extended Pix Format
Device Capabilities
Device Caps      : 0x04204000
Video Memory-to-Memory Multiplanar
Streaming
Extended Pix Format
Media Driver Info:
Driver name      : hantro-vpu
Model            : hantro-vpu
Serial          :
Bus info        : platform: hantro-vpu
Media version    : 5.7.19
Hardware revision: 0x00000000 (0)
Driver version  : 5.7.19
Interface Info:
ID              : 0x0300000c
Type            : V4L Video
Entity Info:
ID              : 0x00000001 (1)
Name            : rockchip,rk3399-vpu-enc-source
Function        : V4L2 I/O
Pad 0x01000002  : 0: Source
  Link 0x02000008: to remote pad 0x1000004 of entity 'rockchip,rk3399-vpu-enc-proc': Data, Enabled, Immutable
Priority: 2
Format Video Capture Multiplanar:
Width/Height      : 96/32
Pixel Format      : 'JPEG' (JFIF JPEG)
Field            : None
Number of planes  : 1
Flags            :
Colorspace        : JPEG
Transfer Function : Default
YCbCr/HSV Encoding: Default
Quantization      : Default
Plane 0          :
  Bytes per Line : 0
  Size Image    : 6745
Format Video Output Multiplanar:
Width/Height      : 96/32
Pixel Format      : 'YM12' (Planar YUV 4:2:0 (N-C))
Field            : None
Number of planes  : 3
Flags            :
Colorspace        : JPEG
Transfer Function : Default
YCbCr/HSV Encoding: Default
Quantization      : Default
Plane 0          :
  Bytes per Line : 96
  Size Image    : 3072
Plane 1          :
  Bytes per Line : 48
  Size Image    : 768
Plane 2          :
  Bytes per Line : 48
  Size Image    : 768

JPEG Compression Controls

            compression_quality 0x009d0903 (int)    : min=5 max=100 step=1 default=50 value=50

And
Code:
v4l2-compliance -d /dev/video4 -s

v4l2-compliance SHA: not available
, 64 bits, 64-bit time_t

Compliance test for rockchip-rga device /dev/video4:

Driver Info:
Driver name      : rockchip-rga
Card type        : rockchip-rga
Bus info        : platform:rga
Driver version  : 5.7.19
Capabilities    : 0x84208000
Video Memory-to-Memory
Streaming
Extended Pix Format
Device Capabilities
Device Caps      : 0x04208000
Video Memory-to-Memory
Streaming
Extended Pix Format

Required ioctls:
test VIDIOC_QUERYCAP: OK

Allow for multiple opens:
test second /dev/video4 open: OK
test VIDIOC_QUERYCAP: OK
test VIDIOC_G/S_PRIORITY: OK
test for unlimited opens: OK

test invalid ioctls: OK
Debug ioctls:
test VIDIOC_DBG_G/S_REGISTER: OK (Not Supported)
test VIDIOC_LOG_STATUS: OK (Not Supported)

Input ioctls:
test VIDIOC_G/S_TUNER/ENUM_FREQ_BANDS: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_S_HW_FREQ_SEEK: OK (Not Supported)
test VIDIOC_ENUMAUDIO: OK (Not Supported)
test VIDIOC_G/S/ENUMINPUT: OK (Not Supported)
test VIDIOC_G/S_AUDIO: OK (Not Supported)
Inputs: 0 Audio Inputs: 0 Tuners: 0

Output ioctls:
test VIDIOC_G/S_MODULATOR: OK (Not Supported)
test VIDIOC_G/S_FREQUENCY: OK (Not Supported)
test VIDIOC_ENUMAUDOUT: OK (Not Supported)
test VIDIOC_G/S/ENUMOUTPUT: OK (Not Supported)
test VIDIOC_G/S_AUDOUT: OK (Not Supported)
Outputs: 0 Audio Outputs: 0 Modulators: 0

Input/Output configuration ioctls:
test VIDIOC_ENUM/G/S/QUERY_STD: OK (Not Supported)
test VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS: OK (Not Supported)
test VIDIOC_DV_TIMINGS_CAP: OK (Not Supported)
test VIDIOC_G/S_EDID: OK (Not Supported)

Control ioctls:
test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: OK
test VIDIOC_QUERYCTRL: OK
test VIDIOC_G/S_CTRL: OK
test VIDIOC_G/S/TRY_EXT_CTRLS: OK
test VIDIOC_(UN)SUBSCRIBE_EVENT/DQEVENT: OK
test VIDIOC_G/S_JPEGCOMP: OK (Not Supported)
Standard Controls: 5 Private Controls: 0

Format ioctls:
test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
test VIDIOC_G/S_PARM: OK (Not Supported)
test VIDIOC_G_FBUF: OK (Not Supported)
test VIDIOC_G_FMT: OK
test VIDIOC_TRY_FMT: OK
fail: v4l2-test-formats.cpp(836): fmt_cap.g_colorspace() != col
test VIDIOC_S_FMT: FAIL
test VIDIOC_G_SLICED_VBI_CAP: OK (Not Supported)
test Cropping: OK
test Composing: OK
test Scaling: OK

Codec ioctls:
test VIDIOC_(TRY_)ENCODER_CMD: OK (Not Supported)
test VIDIOC_G_ENC_INDEX: OK (Not Supported)
test VIDIOC_(TRY_)DECODER_CMD: OK (Not Supported)

Buffer ioctls:
test VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK
test VIDIOC_EXPBUF: OK
test Requests: OK (Not Supported)

Test input 0:

Streaming ioctls:
test read/write: OK (Not Supported)
test blocking wait: OK
fail: v4l2-test-buffers.cpp(256): g_field() == V4L2_FIELD_ANY
fail: v4l2-test-buffers.cpp(1278): buf.qbuf(node)
test MMAP (no poll): FAIL
fail: v4l2-test-buffers.cpp(256): g_field() == V4L2_FIELD_ANY
fail: v4l2-test-buffers.cpp(1278): buf.qbuf(node)
test MMAP (select): FAIL
fail: v4l2-test-buffers.cpp(256): g_field() == V4L2_FIELD_ANY
fail: v4l2-test-buffers.cpp(1278): buf.qbuf(node)
test MMAP (epoll): FAIL
test USERPTR (no poll): OK (Not Supported)
test USERPTR (select): OK (Not Supported)
test DMABUF: Cannot test, specify --expbuf-device

Total for rockchip-rga device /dev/video4: 52, Succeeded: 48, Failed: 4, Warnings: 0

So it's on /dev/video4 as a device name anyway.


  POW window switcher
Posted by: jack1 - 01-05-2021, 07:15 PM - Forum: General - No Replies

Pow is a minimal and lightweight window/application switcher that uses wmctrl. Made for X.
https://github.com/jackghg/Pow

Try also:
OnKey onscreen keyboard. https://github.com/jackghg/OnKey
smlock screen lock. https://github.com/jackghg/smlock


  webcam photo solid gray
Posted by: stozi - 01-05-2021, 05:35 PM - Forum: General Discussion on Pinebook Pro - No Replies

I installed Kamoso and Cheese. If I take a webcam photo with either I get a solid gray image, even though the preview works just fine.


  Pinephone mainboard v1.2 documentation update?
Posted by: scholbert - 01-05-2021, 07:49 AM - Forum: PinePhone Hardware - Replies (1)

Hi!

This thread may go out to the pine64 crew...
Maybe it would be possible to get an update on the mainboard placement documents.

Code:
PinePhone mainboard bottom placement v1.1 20191031.pdf
PinePhone mainboard top placement v1.1 20191031.pdf

There's still v1.1 available in the wiki, but it would be nice to get these documents referenced to the v1.2 boards.

Another thing to mention is, that it would be really nice to know about the exact position of the testpoints.
This might be helpful for debugging and low-level programming... or weird addons.

So far i made a list with the schematics as a reference.
v1.2 mainboard bottom:
Code:
in the middle nearby the mpu (U1, upper left):
T500 -> CPUS-UTX  (AR100 UART TX, disabled in crust, used as WL-PMU-EN)
T501 -> CPUS-URX  (AR100 UART RX, disabled in crust, used as WL-WAKE-AP)
T502 -> HDMI-CEC
T503 -> FEL  (pull low to enter FEL mode, USB-Boot)

next to ANX7688 (U1304):
T1300 -> ANX_CSDA
T1302 -> ANX_CSDL
T1502 -> GPIO0 (ANX7688

v1.2 mainboard top:
Code:
beneath J1101:
T1100 -> CTP-RST
T1101 -> CTP-INT
T1102 -> TWI0-SDA
T1103 -> TWI0-SCK
T1104 -> GPIO0-LDO (VCC-3V)

above J1200:
T1202 -> POWKEY
T1203 -> VOL-
T1204 -> VOL+

next to J1300:
T1 -> USB0-DP
T2 -> USB0-DM
T3 -> DCIN
T4 -> VBAT

in the middle nearby the modem (U1500):
T1503 -> HTXCN
T1504 -> HTXCP
T1505 -> HTX0N
T1506 -> HTX0P

T1600 -> 4K7_PD
T1601 -> USB_BOOT


The group of the HDMI signal pairs are just a guess, as we don't know the position yet.
The only reference i found in the wiki were the USB_BOOT (Modem) pins...

The craziest thing ever would be, if the board-files (e.g. gerber-data) could be shared...

Best regards,
scholbert


  Thermal Camera AMG8833 I2C
Posted by: Little_Johnny - 01-05-2021, 05:44 AM - Forum: General Discussion on PINE A64-LTS / SOPINE - No Replies

can the Thermal Camera module AMG883 be used with the pine64 LTS with Android 6.0, 
its sold by Adafruit for the Raspberry Pi, it connects to the Raspberry Pi via I2C
im still a noob when it comes to adding hardware and the programing side of things for the pine64

https://www.ebay.com.au/itm/AMG8833-IR-8...0005.m1851