Hello,
I bought a PINE64 PA642GB and flashed it with Armbian (Debian GNU/Linux 11 (bullseye)). I need the Pine64 for the BirdNET project https://github.com/mcguirepr89/BirdNET-Pi.

The Pine64 is so interesting precisely because the microphone input is also on the 3.5mm jack plug. Does this still have to be activated?

Many thanks for your help!

hello

I would really really really like to have a Linux cell phone.

I understand the pinephones are Beta right now.

What I am wondering, are there any PinePhones out there that have been gone over by hackers that are ready for use?

I am willing to pay extra for the extra finishing work.

I have limited experieince and limited time but a lot of enthusiazm for a phone for the people.  What I mean is a phone that is made for the people to use and NOT made to use people.

thank you.

Hello all,

I recently got the Quartz64-A board and I'm starting to feel a bit more experimental with it.  I don't have a lot of experience, but if I'm pointed towards some good docs and given some hints I can usually make some progress.  I have a scripting background with a very rudimentary programming understanding so I'd probably only be able to integrate other peoples work from other projects into this one vs writing something from scratch.

What I'm wondering, and this may need to go to the EDK II forums instead, is if it is possible to add the ethernet driver for uefi boot options and then to be able to use either PXE or iSCSI to get the board booting remotely?

What I've looked at so far, and only understand about 10% so far, are the following.  If there's better places or maybe more focused on the Quartz please let me know.  If you have any suggestions on how I'd need to go about learning more for this topic I'd appreciate it as well.

# Found that there are sections indicating something is called for both the ethernet driver and iscsi in the dsc for the quartz board
https://github.com/jaredmcneill/quartz64...artz64.dsc

# Starting to read through the Network driver requirements to understand how what's there may already be used
https://edk2-docs.gitbook.io/edk-ii-uefi...guidelines

# A link I've found but don't have the background to understand yet around iSCSI
https://github.com/tianocore/tianocore.g...C-Protocol

As others have pointed out in general (and I pointed out in regards to the PineTime), we need products to be more repairable, as well as sustainable (both being able to repair the devices, as well as have what to replace if need be), and this is a huge issue nowadays, though finally starting to be taken seriously (Framework, Fairphone, Puri.sm (to a degree), and some of Pine64's products come to mind).

Pine64, for the most part, does a great job on that front (the larger devices, such as the PinePhone, PineTab, PineNote, are built brilliantly) although there are some shortcomings, mainly with the smaller devices (the PineTime's construction hindering repairs, especially the soldered battery, however the Pinecil manages to avoid this and be a repairable device, that is also sustainable (more on that later)), and this does bode an ill-omen for things that are even harder to design with repairability in mind, like the PineBuds (even Fairphone failed to put a battery that is not soldered to the board, although they did manage to make opening the device relatively easy, when considering the challenges).

Puri.sm's Librem 5 development was (and still is) fraught with issues (mostly management issues), and despite not being as suited to be a daily driver as the PinePhone is, they got something right, and that is that there should be a way to easily replace the wireless components (not in the way they did, and less in regards to the specific component that thought about, that is more suited for a development unit in a lab), since despite the main issue there is the quality (Realtek is long known for their garbage quality and inefficient networking), the advantage of being able to replace the module, is that, if designed correctly, this could also alleviate the issues with broken antennae connectors (this will require a rethinking of how the modules exists, since the closest equivalent is M.2 1216, which only exists in soldered form in consumer-ready products, however even that form factor would be a step-up, although protocols other than PCIe should be considered for chipsets that cannot provide PCIe).

Regarding sustainability, I believe that Pine64 is working hard on that, and are on the right track, however we already have a situation where a Pine64 product is not sustainable, the PineTime (though this was probably because it was meant as more of an experiment, I have high hopes for a potential PineTime successor). The obvious examples of sustainability done right are Fairphone and (probably, we need more time for verification) Framework. I hope we see that level of sustainability, where replacement parts are available long after the device is no longer being sold (the Pinecil is already showing great promise in that area, and I believe, though not having the budget, I am not as knowledgeable about the state, of the PineBook and PinePhone and the other devices between those device classes, that something similar should be there as well.

are there  [testing] repos for atchlinuxarm on pinephone ?

 ezik

After I place a call (by clicking the call button in the contacts list or in the recent calls list) the display blanks.  The only way to get the display back so I can press the speaker button or access the dial pad seems to be to press the power button twice - the first time to lock the phone and the second to get the unlock screen.  Still, the display will sometimes blank again after a couple seconds.  Another aspect to this is that when I'm dialing the Calls screen has a white background with white buttons and after unlocking the Calls screen has a black background and black buttons.

Using up-to-date Mobian Bookworm but this behavior has been going on for quite a while.  Does anyone else see this?

This article explains how we read the BME280 Sensor (Temperature / Humidity / Air Pressure) with the new-ish Zig Programming Language and Apache NuttX RTOS on PineCone BL602...

Read NuttX Sensor Data with Zig

Sorry if this has been asked before but I have not followed pinephone development for a year or two.

I received the PPP today and updated pacman-mirrors followed by a full system upgrade via `pacman -Syyu'

During the update I get a Y/N prompt asking if I want to replace 'kwayland' with 'kwin' . I decided no as I thought this was a bug and the system was attempting to install the default plasma window manager (A big assumption I know, but a search at the time turned up nothing).

Following the update everything seems to be working fine (so far) with the exception of screen locking.

When attempting to wake the screen, instead of the lock-screen I get a text message I can not fully see due to it's size, something along the lines of " lock screen broken". Turning the screen off and back on presents me with a lock-screen that looks like a desktop and asking for a pin but no virtual keyboard is available to deliver user input.

Since I haven't been following development I don't know if the lock-screen misbehavior is 1) From my decision not to replace kwayland or 2) From the update or 3) a common bug everyone is dealing with.

Any insight  to help me get up to speed would be greatly appreciated.

HI
I have Rock64 v2. I ran debian 11 on it. It works.

How to turn on the sound on the headphones? On HDMI, sound and picture work.

alsa-utils is installed

speaker-test -c2 -D hw:0,0    --- headphones - it's quiet
speaker-test -c2 -D hw:1,0    --- HDMI is ok

Quote:root@rock64:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SPDIF [SPDIF], device 0: ff030000.spdif-dit-hifi dit-hifi-0 [ff030000.spdif-dit-hifi dit-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDMI], device 0: ff000000.i2s-i2s-hifi i2s-hifi-0 [ff000000.i2s-i2s-hifi i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I have an up to date PinePhone Pro with Siglo and my PineTime is running Infinitime 1.10.0. The watch shows an active Bluetooth connection but the watch is not receiving any notifications. Any idea how I can get notifications to work? Thanks.