Has anyone noticed battery issues with UBPorts?  

I received my PinePhone and tried out UBPorts.  I did upgrade and update and played around a bit.  The phone was charged to 100%.  I locked the screen and went to bed.  In the morning the battery was completely dead. 

It appears the OS didn't go to sleep or something was running heavily enough to completely drain battery.

Does anyone have clear, specific instructions on how to install the updated uboot in manjaro? I tried to follow these instructions in the /boot file in manjaro:
flash_uboot() {
  echo "A new U-Boot version needs to be flashed onto your install drive. Please use lsblk to determine your drive, before proceeding."
    echo "You can do this by running:"
    echo "# dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc"
    echo "# dd if=/boot/u-boot.itb of=/dev/mmcblkX seek=16384 conv=notrunc"
}

## arg 1:  the new package version
post_install() {
  flash_uboot
}

## arg 1:  the new package version
## arg 2:  the old package version
post_upgrade() {
  flash_uboot
}
but....the second dd command failed (never gave any visible output) and I temporarily bricked my PBP . I don't particularly want to repeat that experience EVER again, so I don't want to try it again until someone else gives it a good look over. Confusingly, I found these instructions printed in the terminal while doing pacman -Syyu:

(213/215) upgrading uboot-pinebookpro                [############################] 100%
warning: /boot/boot.scr installed as /boot/boot.scr.pacnew
warning: /boot/boot.txt installed as /boot/boot.txt.pacnew
A new U-Boot version needs to be flashed onto /dev/mmcblkX.
You can do this later by running:
# dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc
# dd if=/boot/uboot.img of=/dev/mmcblkX seek=16384 conv=notrunc
# dd if=/boot/trust.img of=/dev/mmcblkX seek=24576 conv=notrunc
(214/215) upgrading xorg-server-common       

Thoughts/ideas??
P.S. I am running Manjaro from my emmc and did check to make sure I flashed the correct drive (the emmc)

Has anyone been able to build a Kali Linux image with the build script? I have tried very hard on both the pinebook pro and another laptop to run it, and I have run into a few obstacles: first, when I run it on the PBP on Manjaro, the ./build-deps.sh script fails because the script uses apt-get. Then, when I switched to Ubuntu Mate, I discovered that the PBP's cross-compiler does not seem to be compatible with arm (apt-get can't find the package). Finally, I switched to another (intel cpu) laptop running elementary os, installed the compiler, and ran the ./build-deps.sh script without issues. But when I tried to run:

If you accidentally soft brick your PBP there is special mode implemented called maskrom mode. In this mode the device is accessible as regular USB device and can be accessed using rkdevelop tools. Especially to rewrite SPI flash or to erase it.

According to Rockchip documentation it should be accessible following below procedure:

1. Press and hold recovery button.
2. Short press reset.
3. Release recovery button after about 3 seconds.

Unfortunately it is not always the case. I had a clear SPI from factory and had to do this procedure trillion times to eventually get into maskrom mode. There is another person who had the same problems.

The nature of this problem is not clear. There are two suspicions:

- the button is not working correctly or is just prone to failures.
- the problem occurs only when the SPI was previously flashed.

One way or the other the button works shorting two pins in an SPI device. But in some cases it just does nothing. So if you experience such problem there is a way to overcome it. You can short the two pins by yourself.

Procedure:

1. Unscrew bottom cover.
2. Remove the metal shield surrounding main CPU - it is held in place by a tape and micro clamps on pcb.
3. Disconnect all (!!!) boot devices (emmc, sdcard, usb).
4. Locate SPI flash (number 29 on picture).


  PBPL_S.jpg (Size: 442.41 KB / Downloads: 7454)

5. Connect pbp with USB-C - USB-A cable to another computer (pbp on USB-C side).
6. Turn on pbp, short pins CLK and VSS and press reset. It should get your pbp into maskrom mode.


  spi.png (Size: 1.84 KB / Downloads: 1100)


On another computer:

1. Compile rkdeveloptools --> https://github.com/rockchip-linux/rkdeveloptool

2. Create a file filled with zeros:

It's probably me being a total noob, but i fail to use the flashing script:




Is writing mmcblk0 wrong?

We're pleased that you guys are excited and sharing pictures of your phone. However, it is advisable to keep the caseback ON when sharing photographs of the phone, since a number of potentially sensitive numbers (notably IMEI) are etched on the metal cover of the modem.

If you are keen to show others the internals of the phone, then feel free to share this image. It looks identical to the inside of your phone.

If you already shared pictures with the cover off, don't worry about it; consider this a precautions post.

Hey, having a bit of an issue. I got Sailfish installed and up to a point where the screen is locked and there are arrows pointing out from the sides implying I should swipe. But nothing happens with swipe sideways. The swipe up and down works as expected. Anyone know what's going on?

Thank you all for getting a PinePhone BH. With the release of this early adopters version of the PinePhone we've also taken the opportunity to try out a new shipping method. There are a a number of upsides and drawbacks to this shipping method - which I've listed in the January community update - but shipping cost is probably the most notable positive.

So, then, I (and likely other end-users) would like to find out how many of you were asked to pay import tax on your PinePhone? In the comments feel free to include other relevant info such as country, amount paid, etc.
Thanks

Sailfish is one of the oses i'd like to try out, but it's also the only one I can't get to boot properly.
The flash-it script reported success, the device starts to boot, the sailfish logo appears then it goes to a blank screen and the led comes on. looks kind of pink. I've left it in this state for several minutes but no change. 
All other images I've tried have worked fine on the phone, including using the same sd card. any clues? what am I missing?

Edit: That's a bit scary, nothing else would boot on the pinephone until I did a reset (long hold vol down plus power). back to normal now but something's really wrong with sailfish.

Warning: As far as I am aware, so far, this flash process has had about a 16% failure rate. It is difficult to restore your machine with a bad SPI flash. Please proceed at your own risk, and probably best not to try at all if you don't have experience or the time it takes to recover your machine. 

Necessary Items:
 - a screwdriver
 - USB Type-A to USB-C cable
 - Another Computer with a USB-A 3.0 port (I used a Macbook Pro with a type-c dongle, if you use something else, idk.)
Not a requirement but if you want to boot from nvme you need:
 - bootable NVME (i.e., with /boot/boot.txt having root=/dev/whatever_your_nvme_is plus some operating system. I use Manjaro. if you are unsure how to do this or want to sync your emmc with your nvme before hand, as400 has a great guide) preferably an intel 660p since it is what I have. 


Build and install rkdeveloptool on your other computer, find out all the info to do that on their Github. 
    
sanity test that you have installed it correctly

1. the db flash helper(https://www.ironrobin.net/clover/droppy/$/i1mNQ). This prepares the SPI for a binary, in this case, u-boot.
   
2. the uboot binary (https://www.ironrobin.net/clover/droppy/$/H3yzt), built from dhivael's version of u-boot.