Hello, I'm considering purchasing a PinePhone and I am interested in understanding the ethical aspects of its production. Could anyone provide information on whether Pine64 has ensured that materials used in the PinePhone are sourced without the involvement of forced labor or inhumane practices?

Hi.

Why that old not used 2G and 3G is still in phone?

Thanks for answers.

It seems the forum's last message was posted in 2023? Are the Linux Phone and the forum still continuing and active?

I noticed PINE64 Linux Phone two years ago, at time there seems many comments about hardware / software issues, such as connect to a keyboard, is that phone mature and fixed all issues? what is that phone latest hardware and software versions?

If the phone is still well developing, can it supports 4G VoLTE in Australia? Can it be accessed by ssh local wifi from another computer?

Thank very much

Kind regards

I need help recovering my old password to my other account. Same name minus the 2 at the end of it. I cant recieve the recovery emails and i tried multiple times.

Since my other account is unable to recieve recovery emails since somebody blocked it i had to create a new account and start over.

So what i wanted to ask or suggest is is it possible for somebody to create 2 versions of an os. What i mean by that is since android and ios do all this stuff that reserves battey life like shutting down processes and other stuff to drastically improve battery life, is there a developer willing to copy that same model to improve battery life but have 2 os versions where 1 has what we have now and the other has the clone of the android ios battery life but for the pine phone?

Good day!

I've been using Pinephone Pro as a daily driver for 7 months now. Mainly with Arch Linux Danctnix OS. Recently, I'm having problems with connecting to the wifi. It can scan available SSIDs but could not connect after a 90 second timeout.

I've tried manually connecting the wifi via nmcli, manually installing the firmware for brcmfmac from github repos and rebuilding the initramfs. But it doesn't seem to fix my problem.

I'm thinking whether this is a hardware problem (given that I charge it with a 5v:3000ma charger overnight) or a software problem (since I usually update with yay first then sudo pacman -Syu. The updates could've messed with the firmware.)

SInce I use the phone almost always for online activities, I can't use it and I usually reboot it often following the wifi connectivity error. While doing so, I read something in the splash screen at boot-time stating something along the lines of "Failed to read chip id 258" Hopefully anyone here could point me to a way to log or view the messages at the splash screen, or a more appropriate forum or discussion board to bring up my concern.

Help a bro out, links or advice would be greatly appreciated.

My pinephone pro came with sailfish and I believe U-boot ...
I've been trying to try different OS's from the wiki using sdcard.

Some work, some don't.
I assume a lot of the ones that don't work I need to install tow-boot.

My issue is...

I have the tow-boot spi on an sdcard.

I push in the re button and then the power button. (I have tried plugging in power via usb as well).
But, nothing happens. It never boots to the spi install screen.

Is there something I am doing wrong in this regard?

Also, if I ever do get tow-boot installed, how do I revert to a stock U-boot? I have not seen instructions for doing so with the reading I have done yet.

Any help is appreciated. I am just tired of iOS and android and tired of throwing away phones. I am hoping pine64 and its open nature can satiate my basic needs.

Hello! I am working on a project that requires nearly all of the GPIO pins on the rock64. 7 of the GPIO pins are unusable while the microSD card reader is in use. To fix this, I installed armbian onto a usb drive and am booting from it now instead. However, I am still unable to set the GPIO pins that were in use by the microSD card reader. My guess is that it is still active, even though it is not reading anything. I think I need to do something to disable it. Has anyone found a way to access these GPIO pins?

Hello, I'm new to RISC-V and would like to try a desktop board (no gaming needed).
I would like:

1. **Audio connection** for speakers (unless there's some wireless way I don't know about?)
1. **Bluetooth** for mouse or keyboard
1. **Display connections** x3, perhaps micro HDMI or USB-C (AOC 22B2H or similar)
1. **CPU**: RISC-V
1. **Graphics** integrated
1. **Mobo**: SBC
1. **NIC** x2 (run a VM router)
1. **Power**
1. **Ram**: 16-32GB preferred
1. **Storage**: NVMe PCIe, probably 32GB-256GB, nothing large like 1TB
1. **USB** x2 for spare stuff
1. **Wi-Fi** for Internet hotspot, mouse or keyboard

I've been following the discussions on the need for more hardware killswitches to enhance privacy and security. Inspired by the suggestions in this thread, I wanted to gather more insights and ideas from the community. basket random

1. What additional hardware components do you think should have killswitches to prevent potential privacy breaches?
2. Are there any specific use cases or scenarios where you believe these additional killswitches would be particularly beneficial?
3. Have you encountered any privacy concerns with existing hardware that could be mitigated with the implementation of killswitches?