Now that the MNT Reform Next laptop with RK3588 came out I became a bit interested in ARM laptops on the market again.

I found a few ARM laptops with RK3588 processor emerging that give an indication what a Pinebook Next (or however it would be called) could look like. 

Of course the Pinebook Pro still works fine for the purpose it was good for when it came out, like writing, light development, browsing, some games. I love mine and don't really need a new one. But it can be nice to speculate.

I guess the RockchipRK3588 would be a natural fit for the next Pinebook and there is some nice progress with Linux support.
https://www.collabora.com/news-and-blog/...ps-rk3588/

In this performance test the RK3588 compares very favorably compared to the RK3399 of the PBP:
https://www.cnx-software.com/2021/12/16/...geekbench/

It looks like price at this time would be about double of the Pinebook Pro.

Here are a few links of laptops that I have found. I don't know any of these and would be cautious of actually buying one:
https://www.crowdsupply.com/shenzhen-tia...patibility
https://www.alibaba.com/product-detail/C...82500.html
https://www.obsidian.works/shop/p/open-s...am-android

Last but not least the MNT Reform Next. This one has for sure the best software support. But it's also a different price point.
https://www.crowdsupply.com/mnt/mnt-reform-next

Overall I think the PBP would need only a light update. The connections are all right.
The display is absolutely super (for me) and I would be happy to have just the same. 
The trackpad has a nice feel to it, but the software support could be better and it could be more precise.
It would be nice it there were better open source driver support for keyboard and trackpad.

I am now daily driving my PinePhonePro for well over a year, but there is one issue that still annoys me:

The PinePhone pro uses Battery fuel gauging as implemented in the RK818 Chip.
Fuel gauging works ok when using one battery. Battery full and empty indications match the battery voltages within a couple of percentage points.

But the daily driving the PPP with only one battery is hard.
When using multiple batteries, however, the fuel gauging becomes really annoying, as the phone will show the percentage of the last (empty) battery until it shuts off.
After a couple of reboots, the fuel gauging seems to reset itself, but rebooting the PPP several times takes time and does not seem like an ideal solution.

Is there a possibility to reset the fuel gauge calibration on eg. each reboot to avoid unintended shutdowns after battery swapping?

This poll is to determine how widespread the problem is with the PineNote USB not working as an USB client or host. (Charging works and serial port dongle work.) If you are voting regarding a first batch (pre 2024) PineNote, please make a post saying so to this thread and whether you are running the pinenote-debian-image supplied on the 2nd batch PineNotes.

Symptoms are that the lsusb command gives no results, sudo /usr/bin/dmesg | tail shows nothing new after plugging in a hub, flash drive,or other USB device, and sudo /usr/bin/dmesg | tail on a linux computer shows nothing new after connecting the computer and PineNote by USB.

Also /sys/bus/usb/devices is empty on the PineNote.

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!