This poll is to determine how widespread the "No WiFi after resume" problem is among second batch PineNotes is. Also vote if you flashed the pinenote-debian-image to a first batch PineNote, but please say to in a post to this thread.

Symptoms are no WifI icon in the status bar, no WiFi button in the config menu (pop up by tapping upper left screen corner), and no wlan0 device in output from ip addr command.

Hello, since about a month or so I am not able to update with `apt` the PineNote (batch 2) because Debian Trixie moved some folders around according to wiki.debian.org/UsrMerge

Has anyone been able to connect over bluetooth to a PineNote from a linux laptop?

I have been able to get them to see each other and trust each other, but pairing attemps fail. I get asked to confirm a PIN and type yes, but it fails. Simple Pairing mode is enabled, so I don't know why a PIN is involved.

I'm trying to deal with the wifi card not showing after resume from sleep and connecting with the USB debug serial adapter isn't that good an alternative to ssh over wifi. I have zero experience with bluetooth and linux. All the online tutorials seem to be old and the commands don't work anymore.

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) :