| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,964
» Latest member: gesav72643
» Forum threads: 16,334
» Forum posts: 117,438
Full Statistics
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
Yesterday, 08:44 AM
» Replies: 0
» Views: 58
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,522
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 128
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 71
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 215,701
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 119
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 187
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,022
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 897
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 575
|
|
|
| 404 error on DHL shipping form - is it just me? |
|
Posted by: Lorcan - 06-16-2020, 03:43 AM - Forum: Shipment Related Discussion
- Replies (3)
|
 |
I'm awaiting a Community Edition: UBports Pinephone. I've tried to change my shipping to DHL, but when I follow this link:
https://store.pine64.org/product/pinepho...t-upgrade/
I get a 404 error.
Is that just me, or is the page not working for everyone?
Some background: earlier today, I was able to load that page without any problem. I added the item to my cart and went to checkout. While filling out the form (carefully checking that the details I entered were an exact match for the original order), I think I may have accidentally hit some key combination that tried to submit the form. I'm not sure what exactly happened, but suddenly I saw a message that said my session had timed out. So I went back to the store's home page and checked my cart - it was empty. So I selected the item again from the home page and got the 404 error.
I've cleared cookies, etc. - but I'm still getting 404.
Any ideas?
My order is Order #126551.
|
|
|
|
| reset sound after suspend to memory (deep sleep) |
|
Posted by: Der Geist der Maschine - 06-16-2020, 01:47 AM - Forum: Linux on Pinebook Pro
- Replies (16)
|
 |
After a suspend from memory, sound does not work.
On my machine (Manjaro ARM XFCE 20.06 Kernel 5.7), the sound driver snd_soc_es8316 needs to reset the sound chip. The problem is the kernel is preventing unloading and reloading of the sound driver snd_soc_es8316.
My first attempt was initializing the sound chip from the shell mimicking what the es8316 driver is doing in its probe function:
Code: # modprobe i2c-dev
# i2cset -y -f 1 0x11 0x00 0x3f
# i2cset -y -f 1 0x11 0x00 0x80
# i2cset -y -f 1 0x11 0x0c 0xff
# i2cset -y -f 1 0x11 0x03 0x32
I got some static noise making me believe I talked to the right device It has not helped.
The es8316 driver can't be un- and reloaded but un- and rebound. Execute this line after returning from suspend:
Code: $ sudo tee /sys/bus/i2c/drivers/es8316/{un,}bind <<< 1-0011
It's quite easy to crash the kernel. I suspect the sound driver should not be accessed in the split-second between its unbinding and binding. So far, I have only seen kernel crashes when executing the unbind/bind command while playing music. I have not seen any kernel crashes otherwise. You never know what happens on a modern Linux in the background, so YMMV.
I have some vague ideas for a proper solution. Will not happen any time soon. Hope others will step in.
|
|
|
|
| Headphones outputting mono only? |
|
Posted by: Subsentient - 06-15-2020, 10:39 PM - Forum: PinePhone Hardware
- Replies (10)
|
 |
So, I've got my BraveHeart PinePhone fixed up fairly well. I got calls, texts and wifi working, and it's *almost* ready to be my daily driver.
Still got issues with bluetooth, seems running bluetooth at the same time as wifi makes both unpredictable and prone to disconnection, so I have to remove the bluetooth firmware to get a usable experience. That necessitates that I use the audio jack for sound.
No matter what I do, I can only get mono sound, and upon further investigation, it's only outputting on the left channel. I tweaked sxmo_megiaudioroute.c to use "DAC" instead of "Mixer" for the headphone output, set both channels enabled, etc, and then I didn't just get the left channel on both earbuds -- I got the left channel on the left earbud only, and silence on the right earbud.
Megi suggested I don't use that utility for music, but A. I do need phone calls, and B. even when I never use it, e.g. a fresh reboot, the issue persists.
Is anyone else getting mono only? How about anyone who has working stereo? Please also post your phone revision (e.g. braveheart) and the OS you're on.
|
|
|
|
| Manjaro XFCE MPV Hardware Acceleration |
|
Posted by: p3pp3r - 06-15-2020, 09:26 PM - Forum: Linux on Pinebook Pro
- Replies (2)
|
 |
Anyone had any luck getting hardware acceleration to work in MPV on manjaro?
I've updated the config file to include the hardware acceleration option, but no dice.
It would be great to be able to playback smooth video since the RK3399 has a hardware video decoder.
|
|
|
|
ERROR: Could not find dependency 'firmware-rtl8723bt' |
|
Posted by: Engineer - 06-15-2020, 09:13 PM - Forum: PostmarketOS on PinePhone
- Replies (4)
|
 |
Does anyone else have the following error when running bootstrap to flash postmarket OS on an SD card?
ERROR: Could not find dependency 'firmware-rtl8723bt' in any aports folder or APKINDEX. See: <https://postmarketos.org/depends>
[23:05:30] See also: <https://postmarketos.org/troubleshooting>
Run 'pmbootstrap log' for details.
Sorry I am still a noob with this. I'm sure that if someone could post a solution to this problem here, other end users would also appreciate the help.
|
|
|
|
| Installing Ubuntu 20.04 (Focal) with BSP uBoot with deep sleep and sound |
|
Posted by: Syonyk - 06-15-2020, 07:46 PM - Forum: Linux on Pinebook Pro
- Replies (17)
|
 |
Or, "As close to a daily driver OS as I can get." Which I have been attempting to daily drive.
Post 1 is getting it installed, working, and sleeping properly, with at least "mostly works" sound functionality. Later parts will cover various other aspects, including abusing the environment into something that can play Spotify (armhf browser in a chroot).
You'll need a microSD card and some time, with the install ending up on the eMMC.
I'm also assuming some general familiarity with Linux - I've got all the steps, but there may be some assumptions missing between them, because I didn't record the exact keystrokes.
Get the initial image, flash it to SD.
Pull the image from ayufan's repo here:
https://github.com/ayufan-rock64/linux-b...ag/0.10.12
You want focal-gnome-pinebookpro-0.10.12-1184-arm64.img.xz - it's ARM64, and Ubuntu 20.04. Unzip this and put it on an SD card with your preferred techniques (Etcher doesn't seem to like these images, so you may have to dd it directly over - I just dd'd the unzipped image onto the SD card and it was fine).
Toss a copy of this image onto a USB drive or local server as well - you'll need it for flashing onto the eMMC.
Put the SD card in, boot, and you should find yourself at something looking generally Ubuntu 20.04-ish. rock64/rock64 will get you in, and it will make you change the password immediately.
Flash the image to the eMMC
Find the eMMC - I think it tends to be /dev/mmcblk0 when booted from the SD card. The 'lsblk' command will show you what your block devices are, and the one that's not got something mounted as root is your eMMC.
Grab a copy of the image again from your preferred source, and we'll put it on the eMMC. It's worth running lsblk and unmounting anything mounted from your eMMC before you start, though it probably won't matter. It's just rude to blow away a filesystem without unmounting it, and in theory it could mess with the flash if something got written to a half intact filesystem.
Code: unxz focal-gnome-pinebookpro-0.10.12-1184-arm64.img.xz
sudo umount /media/rock64/*
sudo dd if=focal-gnome-pinebookpro-0.10.12-1184-arm64.img of=/dev/mmcblk0 bs=1M
I'm not going to say you should mount the new filesystem to do a bunch of 'sed -i -e' over in /etc and rename your home directory. But if you want to, now is a really good time to do it.
Power down, pop out the SD card, and reboot. You should boot into a clean image, same as you had on the SD card.
Initial System Setup and Updates
The terminal font is violently broken. Menu -> Preferences -> Use Custom Font, and pick something sane. Monospace is a decent one.
Connect to wireless, then we'll update the system and fix the timezone to be correct.
Code: sudo dpkg-reconfigure tzdata
sudo apt update
sudo apt -y dist-upgrade -y
reboot
Congratulations! You have an updated Ubuntu 20.04 - but it doesn't have the good stuff yet. It won't deep sleep, sound probably doesn't work, and we can do better.
Build a 5.7 Kernel and Such
Next, we'll build a 5.7 kernel from the development tree. Bleeding edge and all. Do this first, because the 5.6 kernel with the BSP firmware we'll flash takes about 2 minutes to boot, with a black screen in the process.
Be sure your battery is charged! This will drain your battery down, even if plugged in. You'll probably want to leave the screen brightness dim, but even then, the board at full tilt draws more than the barrel plug adapter can source. Beta hardware and all.
We'll be using the pbp-tools repository, which has several useful scripts (and several scripts that will render things non-booting on this install, because the partition layout is different).
You'll need to agree to the menuconfig options in the kernel build step about 5 minutes in - just tab over to exit and call it good unless you want to explore and change things. If you've never poked around menuconfig, it's a fun place!
Code: sudo apt -y install build-essential libncurses-dev flex bison openssl libssl-dev dkms libelf-dev libudev-dev \
libpci-dev libiberty-dev autoconf fakeroot meson
git clone https://github.com/xmixahlx/pbp-tools
cd pbp-tools
./pbp-build-linux-hwaccel
sudo dpkg -i upstream/*.deb
./pbp-update-ap6256-firmware
./pbp-post-install
reboot
After you've left menuconfig, go do something else, because this takes a long time. It's a pretty complete kernel build on a little ARM box. Think two hours, though it might be less - I've not timed it.
Ideally, you come back to the box rebooted, in Ubuntu, with a 5.7 kernel (uname -a will show you the kernel version). If this doesn't work... well, you have a UART, right? You should even have working sound!
Do NOT run the update system partitions script. It will render this system non-booting because it puts things in the wrong places and nukes the boot partition in the deal. It's built for a different partition layout.
Flash the BSP uboot
We will, however, be flashing the BSP uboot. This is different from the "mainline" uboot, which is fully open source. Some of the quirks of deep sleep aren't ported over yet. We'll be using the patched one with NVMe support, but putting it on the eMMC instead of the SPI flash chip (the SPI chip is good to avoid unless you really need to boot from NVMe, because recovering from a bad flash is somewhat harder).
Your eMMC should be mmcblk2 - use lsblk to verify, and adjust if needed.
Code: git clone https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-pinebookpro-bsp.git
cd uboot-pinebookpro-bsp
sudo dd if=idbloader.img of=/dev/mmcblk2 seek=64 conv=notrunc
sudo dd if=uboot.img of=/dev/mmcblk2 seek=16384 conv=notrunc
sudo dd if=trust.img of=/dev/mmcblk2 seek=24576 conv=notrunc
Yes, this is putting stuff in the middle of a mounted partition (/boot/efi). It does seem to work, but we'll do some fixup to prevent that from being overwritten.
Reboot. You should now have deep sleep capability. Ensure that /sys/power/mem_state has "deep" selected, and you should be able to deep sleep with fn-esc, or closing the lid. Done right, you'll lose 2-3% battery overnight. However, it's not always the most reliable thing on the planet, so you might still shut the system down if you really need battery preserved. Beta dev hardware and all that. The system will wake if you plug it in, otherwise you should be able to wake it with the power switch.
Let's Tweak the Trackpad
None of this really helps the trackpad on this system. If it doesn't bother you, well, don't bother changing anything. But if you're constantly clicking stuff you don't intend to click, there are a few changes that might help. It's apparently somewhat hardware specific, but you can make it less annoying.
In Mouse & Trackpad settings, disable tap to click. This will require you to actually click, which seems to eliminate most of the annoyances. I'll also suggest that you can improve things by changing how you type (hands floating), and by using one finger on the touchpad - don't use your thumb to click, use your pointer finger. Yes, it's working around the hardware, but it makes it somewhat less frustrating to use.
You might install and enable the synaptics driver - it seems slightly better, though... YMMV.
Code: sudo apt install xserver-xorg-input-synaptics
Then modify /etc/X11/xorg.conf.d/40-pinebookpro-touchpad.conf with the suggested settings from the PBP wiki:
Code: Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "MinSpeed" "0.25"
EndSection
Adjust other options if needed.
Sound after Sleep
One may, rapidly, discover that sound doesn't work after sleep. Something isn't getting reset properly, and I don't quite know what yet (this is an issue after deep sleep, not the s2idle sleep that burns 7% battery an hour).
One might try this:
Code: pulseaudio -k && sudo alsa force-reload
If this doesn't work, something probably has sound open - try killing off the browser. Sorry, still working out the details on sound and sleep - something isn't getting reset properly after a deep sleep on the 5.7 kernel.
A Little CPU Toggler Script
Care to mess with your CPUs? Perhaps disable the big CPUs for light use, or disable the little CPUs for hardware virtualization experiments? This ought to help you (run with sudo):
Code: #!/bin/bash
if [ $# -eq 0 ]; then
echo "Usage: sudo pbp_cpu.sh [all, big, little, status]"
exit
fi
if [ $1 = "all" ]; then
echo "Enabling all cores."
echo 1 > /sys/devices/system/cpu/cpu0/online
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 1 > /sys/devices/system/cpu/cpu4/online
echo 1 > /sys/devices/system/cpu/cpu5/online
fi
if [ $1 = "big" ]; then
echo "Enabling only big cores."
# Online the big cores first, then take the little ones offline.
echo 1 > /sys/devices/system/cpu/cpu4/online
echo 1 > /sys/devices/system/cpu/cpu5/online
echo 0 > /sys/devices/system/cpu/cpu0/online
echo 0 > /sys/devices/system/cpu/cpu1/online
echo 0 > /sys/devices/system/cpu/cpu2/online
echo 0 > /sys/devices/system/cpu/cpu3/online
fi
if [ $1 = "little" ]; then
echo "Enabling only LITTLE cores."
echo 1 > /sys/devices/system/cpu/cpu0/online
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 0 > /sys/devices/system/cpu/cpu4/online
echo 0 > /sys/devices/system/cpu/cpu5/online
fi
if [ $1 = "status" ]; then
echo "Core status:";
echo -n "cpu0 (LITTLE): "
cat /sys/devices/system/cpu/cpu0/online
echo -n "cpu1 (LITTLE): "
cat /sys/devices/system/cpu/cpu1/online
echo -n "cpu2 (LITTLE): "
cat /sys/devices/system/cpu/cpu2/online
echo -n "cpu3 (LITTLE): "
cat /sys/devices/system/cpu/cpu3/online
echo -n "cpu4 (big) : "
cat /sys/devices/system/cpu/cpu4/online
echo -n "cpu5 (big) : "
cat /sys/devices/system/cpu/cpu5/online
fi
The Results
Do all this, and you should have something more or less daily driverable. Install your desired software, and just go to town. Please let me know what works and what doesn't!
|
|
|
|
| Installing Ubuntu 20.04 (Focal) with BSP uBoot with deep sleep and sound |
|
Posted by: Syonyk - 06-15-2020, 07:46 PM - Forum: Pinebook Pro Tutorials
- Replies (43)
|
 |
Or, "As close to a daily driver OS as I can get." Which I have been attempting to daily drive.
Post 1 is getting it installed, working, and sleeping properly, with at least "mostly works" sound functionality. Later parts will cover various other aspects, including abusing the environment into something that can play Spotify (armhf browser in a chroot).
You'll need a microSD card and some time, with the install ending up on the eMMC.
I'm also assuming some general familiarity with Linux - I've got all the steps, but there may be some assumptions missing between them, because I didn't record the exact keystrokes.
Get the initial image, flash it to SD.
Pull the image from ayufan's repo here:
https://github.com/ayufan-rock64/linux-b...ag/0.10.12
You want focal-gnome-pinebookpro-0.10.12-1184-arm64.img.xz - it's ARM64, and Ubuntu 20.04. Unzip this and put it on an SD card with your preferred techniques (Etcher doesn't seem to like these images, so you may have to dd it directly over - I just dd'd the unzipped image onto the SD card and it was fine).
Toss a copy of this image onto a USB drive or local server as well - you'll need it for flashing onto the eMMC.
Put the SD card in, boot, and you should find yourself at something looking generally Ubuntu 20.04-ish. rock64/rock64 will get you in, and it will make you change the password immediately.
Flash the image to the eMMC
Find the eMMC - I think it tends to be /dev/mmcblk0 when booted from the SD card. The 'lsblk' command will show you what your block devices are, and the one that's not got something mounted as root is your eMMC.
Grab a copy of the image again from your preferred source, and we'll put it on the eMMC. It's worth running lsblk and unmounting anything mounted from your eMMC before you start, though it probably won't matter. It's just rude to blow away a filesystem without unmounting it, and in theory it could mess with the flash if something got written to a half intact filesystem.
Code: unxz focal-gnome-pinebookpro-0.10.12-1184-arm64.img.xz
sudo umount /media/rock64/*
sudo dd if=focal-gnome-pinebookpro-0.10.12-1184-arm64.img of=/dev/mmcblk0 bs=1M
I'm not going to say you should mount the new filesystem to do a bunch of 'sed -i -e' over in /etc and rename your home directory. But if you want to, now is a really good time to do it.
Power down, pop out the SD card, and reboot. You should boot into a clean image, same as you had on the SD card.
Initial System Setup and Updates
The terminal font is violently broken. Menu -> Preferences -> Use Custom Font, and pick something sane. Monospace is a decent one.
Connect to wireless, then we'll update the system and fix the timezone to be correct.
Code: sudo dpkg-reconfigure tzdata
sudo apt update
sudo apt -y dist-upgrade -y
reboot
Congratulations! You have an updated Ubuntu 20.04 - but it doesn't have the good stuff yet. It won't deep sleep, sound probably doesn't work, and we can do better.
Build a 5.7 Kernel and Such
Next, we'll build a 5.7 kernel from the development tree. Bleeding edge and all. Do this first, because the 5.6 kernel with the BSP firmware we'll flash takes about 2 minutes to boot, with a black screen in the process.
Be sure your battery is charged! This will drain your battery down, even if plugged in. You'll probably want to leave the screen brightness dim, but even then, the board at full tilt draws more than the barrel plug adapter can source. Beta hardware and all.
We'll be using the pbp-tools repository, which has several useful scripts (and several scripts that will render things non-booting on this install, because the partition layout is different).
You'll need to agree to the menuconfig options in the kernel build step about 5 minutes in - just tab over to exit and call it good unless you want to explore and change things. If you've never poked around menuconfig, it's a fun place!
Code: sudo apt -y install build-essential libncurses-dev flex bison openssl libssl-dev dkms libelf-dev libudev-dev \
libpci-dev libiberty-dev autoconf fakeroot meson
git clone https://github.com/xmixahlx/pbp-tools
cd pbp-tools
./pbp-build-linux-hwaccel
Code: sudo dpkg -i upstream/*.deb
Code: ./pbp-update-ap6256-firmware
After you've left menuconfig, go do something else, because this takes a long time. It's a pretty complete kernel build on a little ARM box. Think two hours, though it might be less - I've not timed it.
Ideally, you come back to the box rebooted, in Ubuntu, with a 5.7 kernel (uname -a will show you the kernel version). If this doesn't work... well, you have a UART, right? You should even have working sound!
Do NOT run the update system partitions script. It will render this system non-booting because it puts things in the wrong places and nukes the boot partition in the deal. It's built for a different partition layout.
Flash the BSP uboot
We will, however, be flashing the BSP uboot. This is different from the "mainline" uboot, which is fully open source. Some of the quirks of deep sleep aren't ported over yet. We'll be using the patched one with NVMe support, but putting it on the eMMC instead of the SPI flash chip (the SPI chip is good to avoid unless you really need to boot from NVMe, because recovering from a bad flash is somewhat harder).
Your eMMC should be mmcblk2 - use lsblk to verify, and adjust if needed.
Code: git clone https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-pinebookpro-bsp.git
cd uboot-pinebookpro-bsp
sudo dd if=idbloader.img of=/dev/mmcblk2 seek=64 conv=notrunc
sudo dd if=uboot.img of=/dev/mmcblk2 seek=16384 conv=notrunc
sudo dd if=trust.img of=/dev/mmcblk2 seek=24576 conv=notrunc
Yes, this is putting stuff in the middle of a mounted partition (/boot/efi). It does seem to work, but we'll do some fixup to prevent that from being overwritten.
Reboot. You should now have deep sleep capability. Ensure that /sys/power/mem_state has "deep" selected, and you should be able to deep sleep with fn-esc, or closing the lid. Done right, you'll lose 2-3% battery overnight. However, it's not always the most reliable thing on the planet, so you might still shut the system down if you really need battery preserved. Beta dev hardware and all that. The system will wake if you plug it in, otherwise you should be able to wake it with the power switch.
Let's Tweak the Trackpad
None of this really helps the trackpad on this system. If it doesn't bother you, well, don't bother changing anything. But if you're constantly clicking stuff you don't intend to click, there are a few changes that might help. It's apparently somewhat hardware specific, but you can make it less annoying.
In Mouse & Trackpad settings, disable tap to click. This will require you to actually click, which seems to eliminate most of the annoyances. I'll also suggest that you can improve things by changing how you type (hands floating), and by using one finger on the touchpad - don't use your thumb to click, use your pointer finger. Yes, it's working around the hardware, but it makes it somewhat less frustrating to use.
You might install and enable the synaptics driver - it seems slightly better, though... YMMV.
Code: sudo apt install xserver-xorg-input-synaptics
Then modify /etc/X11/xorg.conf.d/40-pinebookpro-touchpad.conf with the suggested settings from the PBP wiki:
Code: Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "MinSpeed" "0.25"
EndSection
Adjust other options if needed.
Sound after Sleep
One may, rapidly, discover that sound doesn't work after sleep. Something isn't getting reset properly, and I don't quite know what yet (this is an issue after deep sleep, not the s2idle sleep that burns 7% battery an hour).
One might try this:
Code: pulseaudio -k && sudo alsa force-reload
If this doesn't work, something probably has sound open - try killing off the browser. Sorry, still working out the details on sound and sleep - something isn't getting reset properly after a deep sleep on the 5.7 kernel.
A Little CPU Toggler Script
Care to mess with your CPUs? Perhaps disable the big CPUs for light use, or disable the little CPUs for hardware virtualization experiments? This ought to help you (run with sudo):
Code: #!/bin/bash
if [ $# -eq 0 ]; then
echo "Usage: sudo pbp_cpu.sh [all, big, little, status]"
exit
fi
if [ $1 = "all" ]; then
echo "Enabling all cores."
echo 1 > /sys/devices/system/cpu/cpu0/online
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 1 > /sys/devices/system/cpu/cpu4/online
echo 1 > /sys/devices/system/cpu/cpu5/online
fi
if [ $1 = "big" ]; then
echo "Enabling only big cores."
# Online the big cores first, then take the little ones offline.
echo 1 > /sys/devices/system/cpu/cpu4/online
echo 1 > /sys/devices/system/cpu/cpu5/online
echo 0 > /sys/devices/system/cpu/cpu0/online
echo 0 > /sys/devices/system/cpu/cpu1/online
echo 0 > /sys/devices/system/cpu/cpu2/online
echo 0 > /sys/devices/system/cpu/cpu3/online
fi
if [ $1 = "little" ]; then
echo "Enabling only LITTLE cores."
echo 1 > /sys/devices/system/cpu/cpu0/online
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 0 > /sys/devices/system/cpu/cpu4/online
echo 0 > /sys/devices/system/cpu/cpu5/online
fi
if [ $1 = "status" ]; then
echo "Core status:";
echo -n "cpu0 (LITTLE): "
cat /sys/devices/system/cpu/cpu0/online
echo -n "cpu1 (LITTLE): "
cat /sys/devices/system/cpu/cpu1/online
echo -n "cpu2 (LITTLE): "
cat /sys/devices/system/cpu/cpu2/online
echo -n "cpu3 (LITTLE): "
cat /sys/devices/system/cpu/cpu3/online
echo -n "cpu4 (big) : "
cat /sys/devices/system/cpu/cpu4/online
echo -n "cpu5 (big) : "
cat /sys/devices/system/cpu/cpu5/online
fi
The Results
Do all this, and you should have something more or less daily driverable. Install your desired software, and just go to town. Please let me know what works and what doesn't!
|
|
|
|
| Still struggling with microphone input |
|
Posted by: diodelass - 06-15-2020, 05:49 PM - Forum: Pinebook Pro Hardware and Accessories
- No Replies
|
 |
I've been here since just about day one - microphone input on the Pinebook Pro is almost there, but I still can't seem to get it to give me any input from the right-side mic. The input audio stream is stereo, but it's just giving me the left-side mic stream twice.
Here is what I know:
- Yes, there are actually two microphones. I opened the device up and looked with my own eyes, and there are two of them, both of which are wired up to the mic connector on the mainboard.
- The Pinebook Pro's audio chip does have a stereo input, so the ability to process data from two microphones exists.
- I can't find anything obvious in alsamixer (e.g. "mono mix" which only seems to be an output setting) to suggest that it's configured to behave like this, but I admittedly don't have a lot of familiarity with most of the available settings, so I could have overlooked something.
Is this just a wiring fault, or is there something in software that still needs to be tweaked? I know I've seen a lot of claims that the Pinebook Pro only has one microphone, and whether or not this is actually true of most units, that might point to the board only being wired for one.
Any thoughts?
|
|
|
|
| Pinebook pro poor performance on 5Ghz WiFi |
|
Posted by: Iolaum - 06-15-2020, 05:44 PM - Forum: General Discussion on Pinebook Pro
- Replies (10)
|
 |
Hello,
I have been testing and enjoying my new Pinebook Pro. I 've noticed however that 5Ghz Wifi is performing poor. I have activated both 2.4 Ghz and 5Ghz wifi on my home router. Things I 've noticed:
- There are times when 5Ghz wifi is not working at all - as if there's no wifi signal available. Devices next to the pinebook, such as a smartphone, work fine with 5Ghz wifi so I know the signal is good but PBP can't interface with it.
- I 've tested wifi speeds when both 2.4Ghz and 5Ghz are working in the Pinebook. The 2.4Ghz connection easily gets 4+Mbytes/sec while the 5Ghz oscillates between 500Kbytes/sec to 1.2Mbytes/sec.
The network connection is 150Mbps.
Has anyone else experienced anything similar?
|
|
|
|
| D2K, my own experimentation fork of Mobian |
|
Posted by: Djhg2000 - 06-15-2020, 03:59 PM - Forum: Mobian on PinePhone
- No Replies
|
 |
I've created a fork of Mobian for testing purposes. I've built my own personal images with this for a few days now and I thought I might as well share it for anyone who's interested. I'm not supplying binary images for two reasons;
- This is not meant to replace regular Mobian for end users
- I'm stuck on a slow and metered connection
The build process is the same as for regular Mobian except you should use ./build-d2k.sh to generate your image.
The ultimate goal is to make merge requests in small pieces, but until then I wanted to have sort of a playground where I can push incomplete things I'm working on without breaking Mobian. Regular forks are great for single tasks but this quickly snowballed into several large pieces I want to test simultaneously. Some changes are more to personal taste as well, and should not to be pushed upstream.
Feedback welcome, feel free to pick out parts you want for your phone 
Oh and during testing I also found a few issues, switching between upstream Mobian and my fork is a bit cumbersome so if anyone wants to confirm if my issues are unique to my fork that would be very helpful. You can find them on this page.
GitLab link: https://gitlab.com/Djhg2000/mobian-recipes
|
|
|
|
|