I received my new Pinenote last week and have been slowly working my way through the docs and hitting some speed bumps.

The most bothersome so far is that the WiFi device does not show up after a wakeup from sleep. Its button doesn't even show up in the config menu (but
the bluetooth button remains present. Powering off, then turning it back on to boot brings WiFi back, but it is gone after the next suspend/resume.

I can't find any mention of this problem. Is anyone else seeing it?

Is there a fix? (Upgrading with apt did not help.)

Hi, everyone!

Today I had trouble with my upgrade of Mobian from bookwork to trixie with no call audio after the upgrade (and poor/inconsistent call audio before the upgrade). So I figured I'd try flashing some of the latest OS images.

I tried Ubuntu Touch for the first time, and I love the GUI--it is super-slick! But it did not register my SIM with the network, and thus I could not use it as a phone. At least Mobian trixie was able to register my SIM with the network (US Mobile "Dark Star" on AT&T network).

Ubuntu Touch does seem to see the modem, since it sees and reports the IMEI number correctly.

The website for Ubuntu Touch claims that it can make and receive calls on the PinePhone Pro, but I can't.

Has anyone figured out how to make Ubuntu Touch work properly (at least as far as they promise on their website, which includes calls and SMS texts but not some other features)?

Meanwhile, I'll try flashing some other OSes, but I'd love to get Ubuntu Touch working, primarily because of the GUI, but also because I use Ubuntu with touch support on my Starlabs StarLite Mk. V tablet as a daily driver. It would be really nice having a fairly uniform user experience across my devices.

Thanks in advance! Any tips/advice are welcome!

UPDATE: Weird--I just noticed that after booting to Ubuntu Touch on the microSD, it registered the SIM correctly. It seems like (but I haven't proven yet) that every time I boot from Ubuntu Touch on the internal eMMC it doesn't register the SIM correctly...

I will try re-imaging the eMMC, but after I flash a few other OSes to see how far along they're coming.

Hi there,
I am running mobian 12 on pinephone (not pro). I am connected to my local wifi. sshd is installed and active but I am not able to connect from another computer of my local network (ssh mobian@192.168.1.xx) :

I have this installed & running now. That sure took longer than I expected it to.

The Hardkernel 256GB emmc has some sort of an orange bump on the bottom, opposite the socket, that the Pine64 64GB emmc which it replaced did not.

There was a sticky pad on the PBP mainboard underneath the emmc to help keep it in place while it's being bumped around; I had to scrape it off with a spudger to get the 256 installed. The new emmc still doesn't sit quite level, it angles up slightly due to the bump; I hope it isn't going to come loose.

Using the Pine-branded emmc-to-USB adapter which I got from the Pine store several years ago, the 256 GB emmc consistently gave read errors whenever it was being accessed raw, which greatly slowed down operations like mounting & partitioning. It's not doing that in the emmc slot, and the 64 isn't doing that on the adapter. For example, this sort of command would trigger a read error if it wasn't read from cache, but reading from a filesystem would not:
$ sudo dd if=/dev/sda count=20480 | md5sum
The errors were recoverable and only showed up in dmesg & syslog, but made it slow.

I wanted to partition the new storage myself and rsync over my files, instead of reinstalling. Things I learned in the process:
- gpt's partition table & backup partition table occupy the first 64 and last 64 sectors of the main address space of the medium; thats why the skip=64 when writing bootloaders.
- The emmc boot partitions (mmcblk2boot0 and mmcblk2boot1) are NOT being used. The convention is to leave the first 30 MiB in the main address space unallocated so there's space for bootloaders and start the first partition at 62500 sectors; with alignment to 2048 sectors as parted recommends, the first partition starts at 32*2048 = 65536 sectors.
- Stock uboot can only boot from FAT filesystems. Using ext4 for your /boot partition makes the medium unbootable. I only tested that FAT16 works.
- If you want the root partition on lvm, as I did, you need to rebuild the initramfs with the lvm2 hook included (instructions) and specify the root fs as e.g. root=/dev/VG1/LV1. u-boot doesn't understand lvm by itself; the tools in the initramfs are needed to mount it.
- Boot order is supposed to be USB > SD > eMMC but with the particular boot loader versions I was using, the USB wouldn't boot at all without the internal emmc disabled. Failure to boot off the USB adapter doesn't necessarily mean it won't boot when slotted.
- The last revision of tow-boot before the maintainer bailed doesn't work on my PBP so it's u-boot only.

In principle, lvm should be a great fit for an all-solid state system like the PBP. Logically contiguous blocks on the medium aren't physically contiguous, so a partition table designed for rotating disks that forces you to keep partitions completely contiguous rather than just reasonably unfragmented, as allocation in extents is intended to do, doesn't make sense.

But what about in practice? I had a hard time finding any performance numbers for lvm other than "works for me", some synthetic benchmarks, and an ancient study using lvm1 which found that performance with small files was terrible.

Life on arm means compiling a lot. I don't want it to slow down big builds.

I've been benchmarking by building haveno's git repository, which is a convenient size. It goes from 260M to 5.1G over the course of a build, and takes about 7-10 minutes to do it. 98% Java code, build managed with Gradle.

Testing `make skip-tests` starting with all dependencies resolved & cached on disk, a gradle daemon running, parallel builds enabled & build caching off, and the linux disk cache freshly flushed, it took about 7m 20s to build on the old emmc without lvm, and 7m 3s on the new emmc with lvm2. Still to test is building on the new emmc in the non-lvm partition I left for comparison, and building from heavily fragmented logical volumes.

A pretty simple guide, Mobian Trixie is setup to use wireguard for VPNs.
It is pretty easy to add openVPN client services though.
first install two packages

I'm looking for the os for the original Pine A64 A64+ I have over and over downloaded the android 8.1 
I have also installed on my computer even going back to older systems Phoenix card win 32 disk manager and Etcher 
with 7 zip and i can not find an *.IMG for the life of me can some one please tell me what I'm doing wrong or give me a link to the correct software

Please and thank you

Hi,

Where I can download the Bulleyes version?. I updated to Bookworm and is not working, but with the Bulleyes version worked since day one.

Regards

I'm trying to get my pinebook pro up and running again. What's a good OS to put on it now? Can someone also recommend a video tutorial for how to put a new OS on the pinebook pro?

I'm running Void on my pbp, which currently is working fine, but during installation wifi didn't work, and `ip a` said that wlan0 didn't exist at all, and the privacy switches didn't help. The unbind/bind trick:

Running a PP Beta/kb/Manjaro/box86, life is fine in most categories. But chromium is glacial and links2 has developed issues bringing up news sites such as washingtonpost/reuters/etc (java complaints and so on).

Is there a very-modest browser that I'm missing? Graphics/video unimportant. I suppose links (vs links2) would be the fallback, but wouldn't mind something a little less stark.

Jake