Hello,

I recently got my PineBook and have managed to flash Tow-Boot on the SPI, flash manjaro on the eMMc and update the touchpad firmware.

I shut it down yesterday and had 50% battery left (at least) and today I started it up and the battery was at 0% so it powered off right after getting to the login screen.

This has happened every single day since I got the laptop.

All the LEDs turn off after shutting it down so it really looks like it is off while obviously it is not.

What can I do to solve this? Where do I even start?

Thank you very much for any help!

Tongman

I am running kernel 5,19 on mobian/Phosh but on starting megapixels from the command line I get the message;

"/usr/share/megapixels/config/pine64,pinephone-pro.ini not found.
Could not find any config file".

How do I get hold of the config file?

A thread with similar issue is closed.

postmarketOS is not charging the batteries at times; and the menu bar shows always charging, regardless if the device is plugged or not.
Also, the same result I can see from 'powersupply' package, always charging.

This issue happened with the newest stable release.  I have attempted replacing the battery with J7, and the same issue is there.

When PinePhone Pro is booted with Manjaro Plasma stable OS, the battery issues is not there, with both the PinePhone OEM battery, and the J7 battery.
With Manjaro Plasma stable OS, if I disconnect the phone from the charger, it shows so; and if I plug back the USB charging cable, the PinePhone Pro will charge, with no issue.

It is indifferently an issue with postmarketOS with charging the phone; or thinking it is being charged and connected (while it is not).

Issue is not with the hardware, it is with postmarketOS.

I have to boot up the Pinephone Pro with Manjaro Plasma OS to get the phone charging, and not depleting the battery, then switch back to postmarketOS. The loveliness of dual boot setup (SD card & eMMC).

Please, if any command I need to run, to supply more details, I am more than willing to do so.

Thank you

How to enter BIOS to change boot order from Hard disk to boot from USB
(to change distro to Endeavour, Mint or Fossapup64 in order to make Qemu work,
& cos I'm fed up with Manjaro wining about dependencies; too long time on each update or new program. Rolling release NO thanks!).

Helllo, looking at the new ROCK64 the spi flash chip is no longer included so my question is if it is possible to boot from an ssd connected via USB?

Plenty happens when we render graphics on PinePhone… Because PinePhone’s Display Hardware is so complex!

To understand the internals of PinePhone, let’s build a Display Driver that will talk directly to PinePhone’s Display Hardware. (“Bare Metal”)

We’ll do this with the Zig Programming Language, running on Apache NuttX RTOS...

NuttX RTOS for PinePhone: Render Graphics in Zig

I recently got a pinebook pro and have been playing around with distros to see what I like best. I found the existing instructions available for Fedora, but they didn't work for the 37 beta currently available. I had already installed Tow-Boot and that continued to work fine. Here's what I had to do:

1. Boot from Fedora 37 live image. I used USB, but SD should also work.
   
2. Run the 'Install to Disk' application
   
3. Choose the install destination. I reclaimed all space on the emmc and installed there.
   
4. There will be error boxes that pop up complaining about problems installing the boot loader. You can choose to continue with the installation.
   
5. Once the installer has finished and before rebooting, you need to add a boot loader entry. I did this manually by creating a boot loader entry file here:
   

   Quote:/mnt/sysimage/boot/loader/entries/fedora37.conf

   
   With these contents based on the kernel and initramfs images I had present in /mnt/sysimage/boot:
   

   Quote:title Fedora 37
   options $kernelopts
   linux /vmlinuz-5.19.7-300.fc37.aarch64
   initrd /initramfs-5.19.7-300.fc37.aarch64.img

1. Sound
   
2. Does not wake up from sleep after either closing the lid or pressing the power button.
   

Sorry, but I have no idea how to fix this.

If some kind person could guide me through it....?

Here is the result from journalctl when trying to place a call:

Just bought a new Pinephone (non pro) and I am trying to get it setup and working. Out of the box with Manjero I tried my SIM and it would not connect to cell service, IIIRC it would give constant GSM error and a timeout. I then updated Manjero, with the same result of not connecting to cell service.

So today I switched to Mobian, the latest weekly build (mobian-pinephone-phosh-20221113.img). But I still appear to still have an issue with registering on the cell network.

My SIM is Puretalk, I am in the US. And it works in my Android phone. I checked before ordering the phone and saw several posts where people said PureTalk works fine. One said just slap the SIM card in and voice is good, setup the APN and mobile data is good.

I have tried the following:

• Cycling through all of the network types 2g-4g, and disabling and re-enabling the mobile network.
  
• Switching the Network (selection) from Automatic to off, most of the time this results in "Timeout was reached" or GDBus.Error:org.freedesktop.libqmi...
  But after a several tires I usually get a list of carriers, and I select PureTalk.com. I can exit and go back in and it still shows PureTalk is selected. If I close the settings and re-open it it is back to Automatic.
• Multiple reboots, complete power off and battery removal
  
• Switching the modem hardware switch on and off.
  
• I am connected to WiFi and did update after installing.
  
• Tried disabling mobile data
  
• Tried a couple variations for APN (currently using PureTalk / RESELLER)
  
• Tried texting and calling. Texts to not send, calls just immediatly just say "call ended"
  
• SIM card has been in and out a few times, is installed correctly (since it sees my phone number)
  

I'm looking to use the Rock64 for emulation and media playback. I will be running RetroPie, Batocera, Recalbox, Lakka, or RetroArch. Which ever one runs the best, or is easiest to set up will be fine. I plan to install Kodi into which ever OS I go with. One of them even has Kodi preinstalled. The emulation capabilities of the Rock64 are just fine for my expectations but I'm curious about how well it handles HDR video and also passthrough audio with Atmos. I searched around to see what people had to say but most of the posts are from two years ago or more, and I know that development usually moves along pretty quickly so issues from two years ago may have been solved by now.

I will be playing media locally with Kodi. Files will be in h.265 10 bit with HDR and most will have Dolby Digital Plus with Atmos, some will be Dolby TrueHD with Atmos. Output will be via HDMI into a home theater receiver that fully supports the above audio codecs.

Does anybody have any recent experience with this type of setup? Any problems with either HDR or Atmos passthrough?