When I go to the available networks page in settings, all I get is 

current operator: none

When I scan for more I get the error:

Scanning networks failed: Cannot scan networks: not enabled yet

I am able to temporarily receive texts if I run the command "sudo mmcli -m any -e", but after a while I go back to having "no carrier", and for this duration data does not work either, and the settings option for adjusting the APN is not highlighter, so I am unable to change it.  

If there's anymore information I can post to help resolve this issue, please let me know.

I've flashed Mobian to the emmc and ran into the "low disk space on file system root"- issue. I already have removed unnecessary software, emptied tradh etc.......
I know this is still or has been a question discussed on this forum.

But there seem to be differentt ways of a solution.
Which one would you recommend?
Or is it depending of the chosen image?

Hi this is Palak Sharma
I am an Engineering Student.
I am planning to develop a website for final year project. Lots of programming languages I am learning here. My strength is in Python programming language as it is very easy to learn and coding. One of my friend suggest me that before start developing I should learn about Pseudocode which will help me to make rough idea for doing programming and similarly help in web development.
I had never heard about term Pseudocode. I am full confused now, Is Pseudocode really does matter or will help in web development.
Waiting for some positive responses.
Thanks

Programming the GPIO Hardware on PinePhone looks complicated… But it’s not that different from microcontrollers! (Like PineTime Smartwatch and PineCone BL602)

Today we shall learn…
1. How to blink the LEDs on PinePhone
2. What’s the Allwinner A64 Port Controller
3. What’s inside the Linux Device Tree
4. How we configure and flip the GPIOs
5. How to do this in C and BASIC

We shall experiment with PinePhone’s GPIO Hardware by booting Apache NuttX RTOS on PinePhone.

Why boot NuttX RTOS on PinePhone? Why not Linux?

NuttX RTOS is a super-tiny, Linux-like operating system that gives us “Unlocked Access” to all PinePhone Hardware. Thus it’s easier to directly manipulate the Hardware Registers on PinePhone.

(Like with peek and poke in BASIC)

Will it mess up the Linux installed on PinePhone?

We shall boot NuttX safely with a microSD Card, we won’t touch the Linux Distro on PinePhone. 

Let’s dive in and find out how we blinked the PinePhone LEDs…

NuttX RTOS for PinePhone: Blinking the LEDs

my bluetooth headphones works great with pinebook pro, but when i connect my jack headphones audio is Quieter, without bass and with very low quality
installed OS is manjaro, i haven't tested yet other OS

I have a number of RockPro64 4Gb boards, and some days ago, after powering down the cluster one of the devices is no longer booting. I have tested it with another MicroSD and is not working either. Both MicoSD cards are booting properly on another RockPro64 device.

I have tried powering down, pressing the power button for many seconds (many times), pressing reset and pressing power button after, pressing both power and reset buttons, but no solution at all.

I see some link in the ethernet switch, that is blinking for some seconds and then turning off. Some other times it just keeps blinking for a long period of time until I press reset or power buttons, then it stops blinking definitely.

I wonder if you could give me an advice on how to solve this issue.

TL;DR: Click the link to get Waydroid with hardware acceleration or if you're interested in building an image from source for development purposes.

Guide lives here: Waydroid for PinePhone Pro

Waydroid is a popular Android emulation environment for Linux that uses a lightweight container to run apps. Though a release based on LineageOS 17.1 is available on many package repositories, it doesn't meet everyone's needs. The official 17.1 release doesn't support graphics hardware acceleration on the RK3399 (i.e. PinePhone Pro), which is important for usability. Additionally, the official instructions do not provide everything developers need to build a working daily-driver-ready image from the latest sources, which they may want in order to test features and fixes that they plan to upstream on their personal phones. This guide attempts to help users who want hardware acceleration but don't have it on 17.1 (e.g., PinePhone Pro users) and developers who want to test new features and fixes on their daily drivers.

I have 3 pinephones, running manjero, and mobian all 3 phones the external speaker has died, where can I get replacement speakers that can handle what the pinephone puts out. There is some kind of design flaw, or parts problem with the speaker. Rest of the phone works and bluetooth is getting better. But without external speaker can't use any alarm functions, constantly miss calls.

Since I, or maybe Mobian, or maybe both of us, fubar'd my package dependencies beyond repair a few weeks ago, I've been eagerly awaiting a new weekly.  Finally dropped very early this morning, so I downloaded, decompressed and wrote the image to a known good SD card.  The bad news is that the PP fails to  recognize it, instead booting to PMOS on the EMMC.  

I've re-burned the it several times from two different laptops, using Gnome Disks and  Balena Etcher, but no joy.  The only difference I see is that the Ext4 bootfs partition says "EFI". 

I've  never had problems with Mobian on SD... I'm stumped.  Any ideas?

I have a Rock64 4GB board which I would like to turn into a FreedomBox server.

Since the Rock64 boards are no longer sold with SPI flash, I am trying
to build U-Boot to flash onto the eMMC module. I am following the instructions
for building here:

https://u-boot.readthedocs.io/en/latest/...kchip.html

However, when I get to here: