I've been thinking of buying a Pinephone for quite a while now, but I don't really know if it's really the perfect phone for me, or if there's better.
I just want a phone for basic calling and messaging and also to goof around with a pocket terminal while staying open, and for relatively cheap.
For now I'm thinking of a Pinephone(Pro) with the keyboard shell.

Thanks.

Hi there,

TL;DR: S/PDIF output is choppy, unclear whether hardware or software issue, any insights appreciated.

I got a ROCKPro64 running Debian stable (with the kernel pulled in from backports). I modified the devicetree to enable SPDIF, by disabling the other two i2s blocks and enabling the SPDIF blocks. I also re-routed the SPDIF signal to the Pi2 GPIO header (using the alternate pin which was already provisioned in the devicetree), because I didn't have a compatible 2mm pin socket available, and delivery times were in the order of months for those. I am connecting via a hand-soldered coax cable to the amp. I tried different cables and adapters to rule out the cabling as a source of problem.

S/PDIF output works in principle, but there are issues. In particular, the amplifier will irregularly fail to recognize the signal for a short moment (it has indicator lights for S/PDIF PCM which turn off briefly), like some kind of synchronization loss. This causes a gap in the audio.

After looking at the amplifier schematics (it is a Denon AVR-1910 and the service manual can be found on the internet), I realized that the signal is tied to GND using a 75 ohm resistor, which would result in significant peak current being sourced from the RK3399 GPIO. To mitigate that, I added a 2N7000 N-FET as driver, powered from the 5V rail with a 75 ohm resistor. This results in 33mA of peak current, I suppose, which should be fine for the 5V rail (any USB device may need more than that).

That way, I hope to have ruled out any cabling/power issues on the transmission line.

I am currently running nothing except mpd on the box. I tried with pulseaudio inbetween mpd and ALSA, but that did not fix the issues (although I *think* it reduced the issues somewhat, not 100% sure).

The rate of issues seems to correlate with the kind of content played back. 44.1 kHz 16 bit content seems to work better than 48 kHz 24 bit content. 96 kHz 24 bit content is completely unplayable (all you can hear are irregular pops on the output, somewhat like light drizzle rain on a metal roof). mpd is not saturating the CPU; it is between 5% and 30%, depending on the ALSA buffer and period time configuration. (With a buffer_time of 0.5s and a period_time of 1ms, I can get 96 kHz content to play somewhat, but with many, many gaps). There's also no significant iowait going on. Swap is turned off.

I took out my oscilloscope and looked at the signal on the wire and I noticed that most of the time (not always, but that may be my scope failing to trigger properly) when a gap occurs, the S/PDIF signal is interrupted. The smallest gap I saw was 22 microseconds. However, ALSA does *not* report a buffer underrun (via the EPIPE error code) to the application. (I also saw some significant ringing at the rising edges of my simplistic driver, which I removed with a 100pF capacitor in parallel to GND, but that did not change the issue.)

I am a bit at a loss at where to look at next. With ALSA not reporting an underrun, I'm not sure if this is a hardware or a software issue.

I saw someone else report a similar problem, but I can't find it anymore in the forums (the search is broken for me).

I'm not sure what to look at next. I'm not 100% sure this is a hardware problem, it may also be in the Linux kernel or whatnot. Feel free to move this thread if appropriate. I am trying to reproduce the issue with speaker-test currently, but so far I wasn't able to (unless when tweaking the buffer sizes well below any sensible threshold, at which point -EPIPE *is* returned from ALSA, suggesting that that then is another issue). Because of this, I decided to post this in the Linux subforum instead of the hardware one.

I appreciate any kind of input and I'm more than happy to provide scope traces, config files, schematics or anything else which may be useful in debugging this. Because I'm at this point rather clueless where to even start, I decided against uploading a swath of data, but don't hesitate to ask.

kind regards & thank you for reading,
jssfr

Hi guys, I have a cuestion

Do somebody know if the Odroid's eMMC are compatible with Pinebook? For example this:

https://www.raspipc.es/index.php?ver=tie...ducto=1333

Thank you!

Hello pinephone community !

I'm glad to own a pinephone pro ... but I need help

It seems that me eMMC installation is corrupted.
So I can only boot from sd card.

As https://wiki.pine64.org/wiki/PinePhone_P...o_the_eMMC says, eMMC should appear when my phone is boot on linux and plug in usb, but I see nothing with lsblk.

The wiki only says "the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot".

What can I do to apply the bypass to a shorter time during boot ?

Cheers
Valère

I got my pinephone a few days ago, I turned it on to check it was working, used the browser for a little bit and then turned the screen off. Since then the screen has been black. (But it is lighting up very slightly I think) I've tried flashing a few different OS's with jumpdrive (arch-arm with phosh and manjaro-arm with phosh.) and the screen stays black. I think the actual OS's are working because jumpdrive clearly works (Lets me see and flash to the eMMC from my pc) I just can't see anything on the screen. I also installed tow-boots installer on an sd and put it in the phone, but the screen merely flashes blue after turning it on and then goes dark again. That's everything I've tried, any suggestions would be appreciated.

for the android users

Android 12L for quartz64-a and quartzpro64

working
magisk installed
hdmi (4k ,hdr,hlg,dobly vison)

wifi
bluetooth
cec
lan
npu

for the Quartzpro64
https://drive.google.com/file/d/1zttd-9b...sp=sharing

for the Quartz64-a
https://drive.google.com/file/d/1Xg1dJOR...sp=sharing

to make a google account
add the redfin module with magisk

https://drive.google.com/file/d/16ThYgxH...sp=sharing

have fun

Hi everybody,

I've a problem with the Rockpro64.

With the Port USB-C is possibile to tranfer video data?

I tried to connected an HUB (to the USB-C port of the Rockpro), this HUB contain 3 port USB and 1 port HDMI, i connect the 2 USB on the HUB Mouse and Keyboard and they function correcty, but if i connected the HDMI to the i can't see the video on the screen. But if i connected the HDMI directly on the Rockpro, i can see the video on the screen.

So, Why it doesn't work with USB C?

Thanks,

Daniele

hello i received today my pinephone.i use many years manjaro on my laptop.how i install packages on pinephone ? is there a pamac for pinephone? how i can install anbox on pinephone because i want to use whatsup and viber is there a documentation to read for all these ?

Hi all,
my brand new pinetime is stuck at the "infinitime logo" after 2-3 days.
I've used gadgetbrige to flash the 1.9.0 firmware as soon as the watch arrived. Everything was fine for about 2 days. After that the "inititime" logo appeared and i got stuck there. I've discharged the watch, read some help request so i went in the blue recovery and then in the red one and got it flashed again. Seemed fine for about a day and then "infinitime logo" again.
Tried to flash it again with 1.9.0 or anything but nothing worked. Rebooted phone, tried gadgetbrige, nrf connect, different boot (green, blue and red) but i can't associate the watch with gadgetbrige anymore (no entry there so no flash) and with nrf connect i get a "starting DFU, disconnecting" with nothing done apparently (uploading the firmware usually require about a minute).
Any idea on how i can recover from here?

Thanks!

I would like to boot my Pro from a MicroSD card and backup the eMMC. Once booted from MicroSD, I want to enter the CLI and run the `dd` command or whatever (obviously, this should not be done on the live system booted from eMMC).

What kind of image should I flash onto the MicroSD card? Will any of the images for OS installation do, or are they only good for actual installation and not for live trial/recovery purposes?

UPDATE:

PostmarketOS regular image works very well for this purpose (need to install Tow-Boot to the SPI first).

I also tried to simply use the Tow-Boot's USB Mass Storage mode to directly access eMMC from laptop, and it initially seemingly worked, but the phone would arbitrarily reboot itself during the backup process.