After today's update

Continued Issues
Settings: date/time issue continues - now you cant change the date/time from Jan 10, 2116 20:34
Lolly Pop:head phone issue continues - still doesnt play through the head phone but through the speakers
Software: continues not to display available software and it was not aware of today's update until sudo pacman -Syyu was ran

New issue
Global issue:The X in an minimized app upper right hand corner is missing and there is no intuitive way close an opened app

New app
Disks: - displays partition info although it report SD 32GB and I dont have one present (Maybe I am reading it wrong)

Image Viewer: First impression is it that is working a little more "smoother"

Still well done and I am looking forward to contribute one day!!

I booted into a microSD-borne Manjaro on my PinebookPro and used Manjaro's `manjaro-arm-flasher` to permanentize that distribution. In that process, however, I chose the wrong image `rock64` rather than `pbpro` and as a result ended up with a PinebookPro that is not even able to boot from the microSD any longer.

In a first attemtp at remediing this situation I have switched off the eMMC on the main bord - now booting from the microSD is possible. The wiki says the eMMC is hot-pluggable, so I hoped when switching it back on when the system is up and running, I could just reflash it and be fine.

BUT: when toggling the eMMC's hardware switch on the running system, the blockdevice does NOT (re)appear accessible for the `manjaro-arm-flasher` utility.
My next step is trying to have journalctl -f running while toggling the eMMC to have a better feedback of what may be going wrong ...

Can anyone help me out with this situation?

Hello,

I'd like to contribute to https://wiki.pine64.org/wiki/PinePhone_APN_Settings (or ask someone to do it if that is not possible). Should I just register or what the process is?

I've contacted @Luke via PM but I think he's too busy or receives too many PMs.

Also I'd like to encourage everyone to do the same as well, we all will benefit from this.

With my newly received 3GB device flashed to Mobian 11/13 image, it seems the battery will not charge beyond 50%. Furthermore the Powersupply app does not report charging when plugged in, although Settings->Power does. 

I will revert to Manjaro tomorrow to make sure it’s not a hardware issue with my device.

As I've learned here, PinePhone is running a Linux OS. Though I keen on Pinephones still there are some Android apps I love to used such as Youtube Vanced (Not Google's official app and also not available in the Play store). Is there any chance to use such apps on Pinephone like we emulators to run Android apps on PCs?

Does anybody know if there is a default password for Manjaro pinephone? One of my friends received his Manjaro pinephone and no password to unlock the locked screen after boot.

Hi all,

I received my PinePhone CE 3gb today and was eager to get started tinkering with the device. I expected getting started would be a bit bumpy but nothing as bad as what I encountered:

Basically the device crashes to a black screen after more than a few seconds of use. Sometimes I have enough time to enter my pin, though usually not. I thought maybe it was something with battery (nope), something to do with whether a port splitter was plugged in and HDMI was in use (nope), or with my Wi-Fi (nope), or with Manjaro (also no). I've flashed Manjaro-ARM-phosh-pinephone-beta2-20201119, Manjaro-ARM-plasma-mobile-dev-pinephone-alpha7-200818, and mobian-pinephone-phosh-20201113 and they all do the same thing.

The only OS that seems to run for more than a few minutes is Jumpdrive 0.6, and *possibly* the stock manjaro that shipped on the device. I would like to re-load that version on just to be sure but I can't figure out what build it was actually running.

In any case I found a thread on these forums (here: https://forum.pine64.org/showthread.php?tid=9832) that seems to indicate the issue may be related to RAM clock speeds being too high. The problems people describe there match what I am experiencing.

I would like to apply these patches but I cannot get the device running long enough to feel comfortable deploying them!

Looking for advice on how to proceed, because right now about all this phone is good for right now is being a bulky 32gb USB drive. Should I seek out the last known-good build and run on that for the time being? Is my device busted? Should I sit tight for a while and check back in a month?

To be clear, I can't even get the device up long enough to claim an IP address over its ethernet link, and even if I did the whole thing crashes in a few minutes! (And worse, the included USB port splitter doesn't lock into place, so even slight movements unplug it!)

Is there something I can do with Jumpdrive over telnet to fix this?

Thank you in advance, and I apologize if I'm noobing up the place

Tom

I first booted up my new pinephone only to be greeted by a lock screen I plan to swap to mobian but I wanted to muck about be manjaro first.

I've tried pins like 0000 1234 12345 but they didn't work

It appears the default partitions Manjaro creates on the eMMC are not aligned.  This is really bad for performance!  Here's how to check this and fix it without re-installing or erasing eMMC.  You do need a boot from a bootable sdcard to do the final step.

First, check the alignment:

Quote:$ sudo sfdisk -l /dev/mmcblk2

Disk /dev/mmcblk2: 58.24 GiB, 62537072640 bytes, 122142720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x87129214

Device         Boot  Start       End   Sectors   Size Id Type
/dev/mmcblk2p1       62500    500000    437501 213.6M  c W95 FAT32 (LBA) 
/dev/mmcblk2p2      500001 122142719 121642719    58G 83 Linux

Quote:$ mkfs.vfat -v -n BOOT_MNJRO -C new-root.img $(( (437501 - 289) / 2 ))

mkfs.fat 4.1 (2017-01-24)
new-root.img has 64 heads and 32 sectors per track,
hidden sectors 0x0000;
logical sector size is 512,
using 0xf8 media descriptor, with 437212 sectors;
drive number 0x80;
filesystem has 2 16-bit FATs and 8 sectors per cluster.
FAT size is 216 sectors, and provides 54592 clusters.
There are 8 reserved sectors.
Root directory contains 512 slots and uses 32 sectors.
Volume ID is 7d933d98, volume label BOOT_MNJRO .

Quote:$ sudo mount -o loop new-root.img /mnt

# Check that the filesystems are mounted as expected and the new one is empty.
$ df /boot /mnt
Filesystem     1K-blocks  Used Available Use% Mounted on
/dev/mmcblk2p1    218512 40296    178216  19% /boot
/dev/loop0        218368     0    218368   0% /mnt

# Copy all the files
$ sudo cp -a /boot/. /mnt

# Check fs is filled as expected
# It wouldn't hurt to ls -l /mnt too
$ df /boot /mnt
Filesystem     1K-blocks  Used Available Use% Mounted on
/dev/mmcblk2p1    218512 40296    178216  19% /boot
/dev/loop0        218368 40296    178072  19% /mnt

Quote:$ sudo umount /dev/mmcblk2p1

$ sudo umount /mnt

# This is the command that writes the partition.  Be sure you have mmcblk2p1 here!
$ sudo dd if=new-root.img of=/dev/mmcblk2p1

Quote:
$ echo ",-289" | sudo sfdisk --no-reread -N 1 /dev/mmcblk2

Disk /dev/mmcblk2: 58.24 GiB, 62537072640 bytes, 122142720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x87129214

Old situation:

Device         Boot  Start       End   Sectors   Size Id Type
/dev/mmcblk2p1       62500    500000    437501 213.6M  c W95 FAT32 (LBA)
/dev/mmcblk2p2      500001 122142719 121642719    58G 83 Linux

/dev/mmcblk2p1:
New situation:
Disklabel type: dos
Disk identifier: 0x87129214

Device         Boot  Start       End   Sectors   Size Id Type
/dev/mmcblk2p1       62500    499711    437212 213.5M  c W95 FAT32 (LBA)
/dev/mmcblk2p2      500001 122142719 121642719    58G 83 Linux

The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8).
Syncing disks.

As part of my quest for a Pop!_OS experience on a PBP, (see this tweet for a snapshot), I wanted to install Pop Shell tiling Gnome extension. I found there were a couple extra steps to get it working on PBP. Once it works, it's freaking awesome.

This should work with any Gnome image, especially Ubuntu based. 

Personally, I started with Armbian and then installed Gnome. if you want to know how to do that, see my answer to Best Gnome Distro for PBP? thread. 

Install dependencies: