Power measurements of kernel builds on X cores with make -jX. [Note, the base system is booted off an SD card with the kernel source code located on the eMMC card. Eventually, I will redo the measurements when booted straight from eMMC].

-j1: 10.0W +/- 0.5W (0 ... 07.0W with screen disabled)
-j2: 12.7W +/- 0.5W (0 ... 09.6W with screen disabled)
-j3: 13.7W +/- 0.5W (0 ... 10.2W with screen disabled)
-j4: 14.3W +/- 0.5W (0 ... 11.2W with screen disabled)
-j5: 15.0W /- 0.5W (0 ... 11.3W with screen disabled)
-j6: 15.0W /- 0.5W (0. .. 11.4W with screen disabled)

When the screen is turned on, power consumption is quite constant with a variance of +/- 0.5W. It's puzzling that occasionally no power is consumed for a few seconds when the screen is turned off. Maybe the battery is taking over during these short intervals?

The external power supply can provide up to 15W. Utilizing 4 cores, the system requires from time to time almost all that power and while utilizing 5 or 6 core, the system requires all the time all that power and probably occasionally even more. This helps explaining the sudden drops in battery charge from 100% to 91% on systems under load (there are are a few threads here on this board).


I also noticed weird things going on which are barely explainable [the actual timestamps are rough guesses. Numbers for the sake of numbers]:

t=00min. I stress the system with make -j5. Power consumption 15W
t=10min. I continue stressing the system with make -j5: Power consumption goes to 0W.
t=11min. I stop the make -j5. Power consumption remains at 0W.
t=20min. Power consumption goes to 13W.
t=40min. Over the last 20 min, the power consumption went slowly down from 13W eventually reaching 8.4W. 8.4W also the power consumption of a freshly booted system.


I gain the impression that at t=10min, the internal battery may have taken over and then from t=20 to 40, the power supply charged back the internal battery. I did not see any capacity drops on /sys/class/power_supply/cw2015-battery/charge, though. Maybe the charge dropped by less than 0.5% keeping the rounded value of 100?


Let's focus on display off (without load): When the display is off, there is an oscillation of 0W for 2 seconds and 5.4W for two seconds. Do here really main power and battery flip flop charging the Pinebook Pro?

Any comments? Can you guys do further power measurements?

It's about time.

Just keep in mind that this is a PoC about native virtualization on AW A64, Windows 10 ARM on A64 is not really usable as you thought, no networking, keyboard/mouse get borked most of the time when you do something, frequent BSODs because watchdog keeps timeout and very slow.

The way how this is being done is the same as Pinebook Pro, but you have to skip OOBE using audit mode (Shift+Ctrl+F3 when it fails to update).

But better yet, just replace the ISO Windows with a Linux distro, it makes your life easier, and it's also faster too.

In the page at https://www.pine64.org/pinebook-pro/ put a link to the page at https://wiki.pine64.org/index.php/Pinebook_Pro

Assuming editing (and spamming) isn't available to the general public.  The wiki page is a go-to for fairly in-depth information.  If you're the sort that always downloads a manual before buying something it's much better than the advertising-type stuff on the promo page.

Assuming there's a large drive, probably NVMe, with space enough to install multiple alternative operating systems.  It would be nice to boot to a GRUB menu asking which to boot. It might also be able to offer eMMC vs SD options.

But I don't know if GRUB is at all compatible with ARM and u-boot.  My guess is that if done right each GRUB choice could replace having u-boot for that choice.  The GRUB installation might not know how to set that up, it might need doing manually.

hey all,

just loaded 23 feb 2020 latest omg of ubports.

having an issue where the demo , long swipe from left edge is not working , the screen does nothing.

if i power off and back on then everything is working until the demo long swipe from the left edge with the white screen loads after a few seconds.

Hey,

I'm having trouble registering on a network with my Pinephone. I already opened a thread about this but still no answer after two weeks, so I guess I'm on my own.

I'd like to try my SIM card on another Pinephone, and a working card on my Pinephone.
Is anyone in Paris and want to go grab a beer or whatever sometime to do a couple of tests?

Thanks in advance!

I've modified pinebook pro with internal LCD.

code in: https://github.com/korneliuszo/ILI9341/tree/st7789

Photos in attachments.
x (x)

#ir-ext-ui { position: fixed; padding: 1px; z-index: 9999; display: none; font-family: Consolas, "Lucida Console", "Courier New", Courier, monospace; text-align: right; }

Attached Files

  IMG_20200223_134704.jpg.resized.jpg (Size: 202.4 KB / Downloads: 836)
  IMG_20200214_132001.jpg.resized.jpg (Size: 247.61 KB / Downloads: 883)
  IMG_20200213_173657.jpg.resized.jpg (Size: 347.93 KB / Downloads: 782)
  IMG_20200208_121259.jpg.resized.jpg (Size: 213.48 KB / Downloads: 766)
  IMG_20200128_212320.jpg.resized.jpg (Size: 468.23 KB / Downloads: 788)

I am trying to record the screen of the Pinebook Pro with audio from the webcam mic.
I tried Kazam, but it can only record in AVI (huge file and audio died after 30 seconds!) and not with h264.

I'm testing with FFMPEG, but I get audio drops and the image quality is not what I hoped for.
This is the command I'm using at the moment:
ffmpeg -video_size 1920x1080 -framerate 30 -f x11grab -i :0.0 -vcodec libx264 -c:v h264_rkmpp -thread_queue_size 32 -f alsa -ac 2 -i hw:0 output.mkv

Anyone has a working solution for recording the screen, or knows how to tweak FFMPEG?

I also installed the package x264 from the Synaptic Package Manager.

Hi all,

I'm trying to get microphone input working, but I'm not having any luck. Even with a alsa config which I believe should work, my recordings (with arecord) are empty. Anyone having any luck with this?

I've been exploring the possibility of running Manjaro on the eMMC but with a BSP kernel on the SD card. Not totally stable yet but wanted to see if anyone has thoughts on this.

Why

I love the overall experience in Manjaro ARM a lot (up-to-date packages, AUR etc). I've installed it to the eMMC and use it on a daily basis. The included mainline kernel has come a long way and mostly works well, but I'm still running into a few issues compared to the BSP kernel in mrfixit2001's Debian and ayufan's Ubuntu images:

• Redshift doesn't work. This is a big problem for me as I use the laptop mostly in the evenings at home.
  
• Sound from the speakers is fairly quiet even at max volume.
  
• S3 sleep: wakes up a few seconds after closing the lid.
  
• (minor) Power LED indicator doesn't change color during sleep.
  

• Write ayufan's Bionic image containing BSP kernel to SD card
  
• Change the kernel boot flags on SD card to use the Manjaro partition on the eMMC as rootfs
  
• Copy over BSP kernel modules and firmware from Bionic image to Manjaro partition on the eMMC
  

• Note that with the mainline kernel in Manjaro, mmcblk1 is the SD card and mmcblk0 is the eMMC storage, but with the BSP kernel in Bionic it's the other way around where mmcblk0 is the SD card and mmcblk1 is the eMMC storage.
  
• Say the Manjaro root partition is /dev/mmcblk1p1 in Bionic and is mounted at /mnt. The default Manjaro eMMC installer sets a label of "ROOT" on the partition, which you can confirm with "ls -l /dev/disk/by-label/".
  

• The line to be edited is the first line that starts with "append". After editing, the first few lines of my /boot/extlinux/extlinux.conf looked like this:
  
  Code:

  timeout 10
menu title select kernel

label kernel-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310
    kernel /boot/vmlinuz-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310
    initrd /boot/initrd.img-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310
    devicetreedir /boot/dtbs/4.4.190-1233-rockchip-ayufan-gd3f1be0ed310
    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=ROOT rootwait rootfstype=ext4

• I located the necessary modules by looking through the "linux-image-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310" and "board-package-pinebookpro-0.9-182" packages:
  
  Code:

  dpkg -L board-package-pinebookpro-0.9-182 linux-image-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310
• Ultimately, here are the files I copied over:
  
  Code:

  sudo cp -a /lib/modules/4.4.190-1233-rockchip-ayufan-gd3f1be0ed310 /mnt/lib/modules/sudo cp -a /usr/lib/linux-image-4.4.190-1233-rockchip-ayufan-gd3f1be0ed310 /mnt/usr/lib/sudo cp -a /vendor /mnt/sudo cp -a /lib/firmware/rtlbt /mnt/lib/firmware/[/list]