I purchased the Manjaro Pinephone without going into a USCellular store first and low and behold, it didn't work when I tried about 5 months ago.  Are there any plans to expand to USCellular's network.  It is a midwest company that isn't huge by any means.

Is 20.12 the latest factory image (what I received on my new PBP shipment a few days ago)?

https://osdn.net/projects/manjaro-arm/st...sma/20.12/

I wish to restore my eMMC to be "as-shipped."

Thanks!
-Cal

So I followed this guide: [color=var(--newCommunityTheme-linkText)]https://forum.pine64.org/showthread.php?tid=10432 and applied the network fix to the Armbian image and wrote it to the SD card for one of the modules.[/color]
I tried booting it up afterwards (with only one module plugged in), and it's still not getting a DHCP lease from my router. Is this fix still appropriate? Do I need to change something else or define my DHCP information in advanced?
Any help would be greatly appreciated!

hello,

i'm trying to figure out how to transfer music files/folders to pinephone manjaro-arm and eventually also transferring file from pinephone to p.c. (windows and linux mint).

i've had no luck figuring out kde connect with linux mint. i found a post referring to devtools,

https://forum.pine64.org/showthread.php?...+pinephone

and i downloaded the devtools from the package manager and i still don't see pinephone on windows 7. am i missing something? would acquiring a sd card make a difference?

thanks.

Just got my PBP a few days ago. Booted fine but, I decided I wanted to play with things  . Installed Manjaro on a SD card and wiped the EMMC in my PBP.
Unfortunately it didn't boot so, I tried reinstalling Manjarno on the EMMC. This also did not work I also tried manjaro-arm-flasher to no avail.
eventually I ran updates on the Manjarno install on the SD and it told me I should update the boot loader, so I ran the recommended dd commands and now the SD doesn't boot . Just tried flashing my SD card from my desktop with:

Hi

There are some elements of the display behaviour on the pine power I dislike. Is the firmware opensource so that I can fix it, please?

Thanks

I was very impressed with my new Pinebook Pro for the entire day it ran after delivery, but the backlighting on the screen flickered and died, rendering my PBP unusable. (I can still barely see the Manjaro "M" logo on the splash screen during boot but, after that, I can't make out anything.

I have an RMA to return it for the Freemont CA service center, but I didn't encrypt my Manjaro installation so I'd like to to erase or re-flash the eMMC before returning it. I have some passwords saved in Firefox that I'd rather not ship off with the PBP. From what I recall about migrating Firefox passwords, they are stored in the clear, and with no whole drive encryption, my user password is insufficient protection.

Some may say I'm paranoid but there is an entire industry in India and the PRC that salvages disk drives from computer "recycling" bone yards to harvest personal data and passwords from them.

I have a Pinephone and dock but no Pinebook Pro dock. SSH connections are refused, because I never set it up on Manjaro.

Maybe forum members with greater knowledge of PBP than I can save me some time with suggestions or other ideas.

1. Boot via SD card to Jumpdrive. (Is there a Jumpdrive that runs on PBP?)
2. Image an OS with SSH enabled by default to an SD card and boot it. (Any suggested images?)
3. Try my Pinephone convergence dock for HDMI video out to my monitor. I know the dock is not designed for PBP, but perhaps the video out will work and I don't have a PBP USB-C video adapter.

I haven't looked into the serial port connection but it's probably a pretty big hassle to get setup.

Thanks!
-Cal

I have been owning a pinephone now for almost a year, but it still is something that lies around most of the time, while for any real world use, I regularly catch myself falling back to my android (LineageOS) device. I wonder how much is can be blamed on the current state of the software and how much on the quite modest hardware, the pinephone is equipped with. For instance: When I tap the geary icon, it takes around 30 seconds (estimated) for the window to show up and several minutes for it to finish checking the various IMAP accounts. K-9 on Android comples the same tasks in seconds, but also Geary on the desktop is much much faster. I suspect that on the Librem5 it also will be faster than on the Pinephone.

But maybe I simply haven't found the right setup yet to get an enjoyable experience out of the pinephone, so I thought I should do a mini survey among those who do use it as a real phone:

So these would be my questions, any answers and comment would be hugely appreciated:

1. Do you use the Pinephone as your daily driver?
   
2. If yes: What distribution do you use?
   
3. Which desktop environment/interface do you use?
   
4. Does the interface offer the basic functionality you need or is something missing?
   
5. Have you been able to add the missing functionality through third party applications or customisations?
   
6. Which customisations did you apply to make the pinephone meet your expectations towards a daily driver?
   

Hello everyone,

I wanted to install another distro to my Pinebook and wiped the EMMC, created a new partition and wrote the rootfs on it. After that I took a short break and when I came back, rebooted, totally forgetting, that I did not write the new uboot files.
When I tried to boot, it did not turn on, not even the LED. So I disabled the EMMC module with the hardware switch and booted to a manjaro image on the SD-card. I tried to enable it again after I booted to the SD-card and tried the commands on the wiki to detect the change (https://wiki.pine64.org/index.php/Pinebo...nformation).

Instead of working it gave me an error: "bash: echo: write error: No such device"

How can I get my Pinebook Pro to recognize my EMMC module again?

Thank you in advance.

I have been trying different distros on my Pinephone, and I love the layout and speed of Ubuntu Touch. However, whenever I turn the screen off, it will not wake up again (the screen flickers and then goes permanently black), and I have to hold the power-button for 10 seconds and boot it back up again. I haven't had any such problem on the other distros, so it clearly seems software-related.

This problem occurred on the latest 5/6 stable version downloaded from here: https://ci.ubports.com/job/rootfs/job/ro...stemimage/

Is this a known issue? Is there a workaround? 

Thanks!