Hi all,

Put together my new PBP (running Manjaro / XFCE, u-boot is 2022.04-4), NVME-adapter and an Intel 660p 1TB SSD. Drive turned up, partitioning and formatting went fine, started copying data - and suddenly the drive vanished. Was running out of battery (maybe that caused the drive to vanish?), fiddled around some days, connected the original power adapter, drive turned up again.

The second time I wasn't that lucky. Copied data, turned the PBP off - and after starting it again, the drive didn't turn up anymore. Basically I have the same problem as described here . But the solution mentioned (flashing a certain boot loader into SPI), doesn't work for me. As the thread is already 2 years old - has anyone run into this problem recently?

`lspci` lists the controller:

• Several different power supplies.
  
• Fiddling around and reconnecting the drive, adapter board and cable.
  
• Booting from SD-card: Some thread mentioned it would help, but got the same behaviour as described above.
  
• Adding `nvme_core.default_ps_max_latency_us=0` to `/boot/extlinux/extlinux.conf` - no change (see this thread )
  
• Ensuring max_link_speed is 1 in device tree.
  
• Putting the SSD into a USB-adapter - turned up, no problems (on my PBP).
  
• Searching the net. The issue turns up with other notebooks and discs too - but never a proper solution is described.
  

• Are there any new insights into this issue?
  
• Is the Intel 660p really working flawlessly for everyone else but me?
  
• If you ran into these problems with a recent PBP / OS (2022) - what worked for you?
  
• Any information I could provide to solve this?
  

Hello

My very first Pinephone became almost unusable a few days ago, some parts of the touchscreen no longer worked, I had to use a second Pinephone left as is, bought 2 years ago with Manjaro ARM KDE (Plasma Mobile) installed by default.

At first, I quickly realized that the battery couldn't be recharged. I tried to recharge it for hours but I had to use the battery of my first Pinephone to be able to power it on anew.

Secondly, I had no mobile data whereas my mobile operator is the biggest one in France and I was very surprised because I had mobile data support two years earlier with Manjaro and Phosh. I could call but the dialer was broken, I often had to reboot to make it work anew, I couldn't press keys during calls for audiotel systems (i.e "Press zero to choose this option" etc). The SMS barely worked, there was a problem of refresh, I had to restart Spacebar to see them. When I was receiving a call, sometimes it didn't ring, I only saw the dialog with "Accept" and "Decline" buttons. It was impossible to select a language for the system, I was stuck with American English (which is obviously not my mother tongue).

Thirdly, I tried to perform the system upgrade by using the GUI but after hours, the tasks remained stuck at 50% and then it complained about a corrupted package. Retrying gave the same result.

Fourthly, I tried to do it in command line with pacman, it started well but I got a black screen with a message talking about a broken session manager that became unreadable after a rotation of the screen. When rebooting, I just saw the KDE logo and it didn't go any further.

As it's Sunday, I can't buy a microSD card, nobody can contact me. The only suggested solution consists in buying one, which I will do tomorrow in order to install Tow-Boot and probably install a working Linux distribution. If anybody has a better suggestion in the meantime, it will be very welcome.

By the way, it's better than nothing, the first time I used a Pinephone, it was unable to boot whereas this second Pinephone was able to do a very few things.

Quote:[alarm@pinephone ~]$ sudo pacman -S vim
[sudo] password for alarm:
resolving dependencies...
looking for conflicting packages...

Packages (2) vim-runtime-9.0.0000-1  vim-9.0.0000-1

Total Download Size:    8.01 MiB
Total Installed Size:  37.94 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
vim-runtime-9.0.0000-1-aarch64.pkg.tar.xz failed to download
Total (1/2)            8.0 MiB  8.05 MiB/s 00:01 [######################] 100%
error: failed retrieving file 'vim-runtime-9.0.0000-1-aarch64.pkg.tar.xz' from mirror.archlinuxarm.org : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

Hello

Bought new Pinebook Pro, while updating I logged out and crashed login window theme software, I type the password and then it logs me in then logs me out back to login window, so to reinstall Manjaro I burned Manjaro on SD card and booted from that successfully. Manjaro installed itself on another partiton on SD card rather than eMMC, I then followed some tutorial and used a command to install Manjaroo in eMMC while running from SD card, Now I boot into uboot, some text shows up and now it wont boot from from neither SD card like it used to be able to, and not from USB drive. I used Balena etcher on ubuntu to burn the images on SD card and USB drive but both are not booting.

What shall I do to install Manajaroo in eMMC? I used to be able to boot from SD card using  Manjaro-ARM-kde-plasma-pbpro-22.12.img but not anymore. Now it just loads uboot and then goes to black screen forever.

Thanks in advance.

I have a PineBook14 forgotten in a cabinet, which could work quite well, but is actually unusable because of broken case. Screwset fixing screen hinges to the bottom case are all broken, so it is very hard to open it and keep in position.

I would really like to restore it in some way. Few years ago I asked to the support if it is possible to get the spare, but it was't. Now I asked to the sales, and I am waiting for an answer.

Anyone with the same problem have found an alternative solution?

PS: I am quite happy of this device, even if, with hindsight, I would have been taken the 11 version! If anyone have one to sell, I would evaluate this choice.

I've been playing with flashing different versions of the PinePhone OSes and noticed that when I use versions updated in the last few months, the charge level displayed on the battery icon is now incorrect. I've seen this on both Mobian and PostmarketOS with Plasma mobile and Phosh.

More specifically, on my PinePhone it displays a quarter of the battery percentage it used to show.

I haven't found much discussion of this (though there was this: https://forum.pine64.org/showthread.php?tid=17056). Who else is seeing this?

In frustration, I took a look at the code and Phosh just pulls the charge level from upowerd for the "display" device which seems to be the right way to do it.

So, I went looking at the documentation and then the source code for the UPower daemon. Sure enough, the way the battery percentage is calculated was changed in July this year:

https://gitlab.freedesktop.org/upower/up...4d_236_242

Apache NuttX RTOS for PinePhone now supports Allwinner A64 Display Engine!

We’re one step closer to completing our NuttX Display Driver for PinePhone.

Let’s find out how our NuttX Display Driver will call A64 Display Engine to render graphics on PinePhone’s LCD Display…

NuttX RTOS for PinePhone: Display Engine

The sailfishos port for pinephone, pinetab and pinephonepro is now updated to the latest sfos release 4.4.0.72. Current state: calls now work and wake device from deep sleep, but call audio is poor at the moment....everything else works except the following:
Not working - camera (waiting for development of libcamera);
Wifi disconnects after sleep, it needs to be toggled off and back on. The indicator shows it as still connected but if you check under Settings>Developer Tools you can see the WLAN IP address field is empty.

There is a new wiki for documentation: https://github.com/sailfish-on-dontbeevi...ation/wiki

The flash-it script works for emmc and sdcards. The option "raw" to write an image on your pc is still broken.

Waydroid works but is very sluggish and a battery guzzler. In theory it needs 6GB ram so especially on original PP it's always going to be slow.
Update edit: after a period of about 3hrs the screen now longer wakes and the only option is to force shutdown (power button for 5 seconds) and reboot.

Hello,

got my hands on a Pinetab lately. Since UT is hardly usable I want to flash another OS.

I read through the threads here and since most of the relvant posts are quite old I like to ask what OS works as of the end of 2022?

Any news about tow boot?

Thanks in advance!

I recently was unable to update Manjaro with xfce on my Pinebook.  The Wiki says Manjaro is no longer supporting the Pinebook.  The Wiki says that Ambian is still supporting it, but I can't find that at Ambian's website, though the site does list the Pinebook Pro.  Is my Pinebook now useless with no suitable OS?  

-v