Libby is a e-book reader that in the US you can checkout copyrighted books from public libraries.

Libbys instructions for install are:
https://snapcraft.io/install/libbylinux/debian

sudo apt update
sudo apt install snapd
sudo snap install snapd
sudo snap install libbylinux

This fails missing squashfs:
error: system does not fully support snapd: cannot mount squashfs image using
      "squashfs": ----- mount: /tmp/syscheck-mountpoint-3961583142: unknown
      filesystem type 'squashfs'.

      dmesg(1) may have more information after failed mount system call.


Debian has squashfs packages which I installed:
squashfs-mount
squashfs-tools
squashfs-tools-ng
squashfuse

cat /proc/filesystems does NOT have squashfs meaning the kernel doesnt have the driver loaded.
It's not in /lib|lib64/modules so my guess its not compiled nor profiled by the packages above.

apt update/upgrade yielded:
******************************************************************************
*
* The base-files package cannot be installed because
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.
*
* This is an unexpected situation. Cannot proceed with the upgrade.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
******************************************************************************


dpkg: error processing archive /var/cache/apt/archives/base-files_13.6_arm64.deb (--unpack):
new base-files package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/base-files_13.6_arm64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)


(as always devs, if you're trying to do something...tell me what.  I dont use --unpack a lot.  unsure why it failed)
root@pinenote:~# dpkg --unpack /var/cache/apt/archives/base-files_13.6_arm64.deb
yielded
* The base-files package cannot be installed because
* /lib64 is a symbolic link and not pointing at usr/lib64 exactly.

Time to play with other presents.
(libby makes PineNote a user product.  XournalPP does, liferae does, ...  It's close but still lots of hacking.)

Hello everyone. I think I ran into an infinite loop with my device. I believe I installed towboot on my pro device (i have a normal pinephone too) years ago. It seems to be broken. When I turn it on I get a steady red light (good, it has power), then a yellow steady light, then red blinking lights (very bad). If I turn it on and into usb debugging/flashing mode by holding down the volume up button down while the phone boots up, I get red, blue, into yellow and red flashing lights. Luckily, I can still boot into jumpdrive and expose the eMMC.. it seems this is not the right way to flash images to this device however. This is an old pinephone pro, one that came out after the explorers edition. It doesn't have an RE button that you hold down to boot off the sd card first.
My question is: how can i reflash towboot to the phone either using telnet or jumdrive? the usb debug mode, as I've said, seems to be corrupted because towboot seems to be corrupted. If it's a matter of not being able to boot off the sd card into the towboot installation wizard because the phone is so old, does anyone know which contact pins i need to short out to boot off the sd card instead? I researched and could not find that information out.
Thank you in advance

What are people using? Just a clear piece of tape over the backside of the SIM adapter to catch it from dropping in any further? Or is there another adapter with a transparent portion?

This is I think the second SIM tray that has died on me.

Hi, everyone!

biketool got me thinking about this: is there a LINUX utility that can do the following:

a) log battery level over time (datalogger functionality for graphing)
b) log which processes or hardware modules (especially the modem) are consuming what power, in milliwatts
c) show power-related settings, especially those that might alter the power consumption

The primary objectives are:

1) to allow the PINE64 community to objectively compare their own experiences for the purpose of sharing settings, tips, tricks, and diagnoses to maximize battery life. There are too many variables to consider when comparing battery life, such as screen brightness, modem clock speed, settings, usage patterns, cell signal strength. With a datalogger we could see, for instance, that someone who complains about awful battery life might have a specific setting that's set wrong, or that someone else with awful battery life has a process that keeps waking the phone up, or that someone with fantastic battery life runs their screen brightness at the dimmest setting all the time, etc.

2) to improve LINUX distros' power optimization for the PinePhone and PinePhone Pro over time


PowerTOP can do b) and c), but I don't think it can do a) without having a serial-attached external datalogger.

It's probable that PINE64 has some kind of internal tool that profiles power/battery consumption as they design their hardware. If that exists and we can use it, that would be great.

If not, which 3rd party open-source LINUX tools are closest to fulfilling the objectives?

I'll search online, but if anyone knows already what tools to use, please share here. Thanks!

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