| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: dave3294
3 hours ago
» Replies: 11
» Views: 9,082
|
Girls In Your Town - Anon...
Forum: General
Last Post: wilsonmatt
7 hours ago
» Replies: 0
» Views: 31
|
Girls In Your City - Anon...
Forum: General
Last Post: publishers
Yesterday, 06:44 PM
» Replies: 0
» Views: 34
|
Girls From Your City - An...
Forum: General
Last Post: publishers
Yesterday, 04:32 PM
» Replies: 0
» Views: 30
|
asterisk or FreePBX on pi...
Forum: PinePhone Software
Last Post: vanja
Yesterday, 09:24 AM
» Replies: 0
» Views: 52
|
Jami on Pinephone [ IM an...
Forum: PinePhone Software
Last Post: marlboro1950
Yesterday, 05:02 AM
» Replies: 15
» Views: 21,980
|
Thread management hurdles...
Forum: General
Last Post: reyohi4392
06-15-2026, 05:12 AM
» Replies: 0
» Views: 69
|
Let's get the PPP and Mob...
Forum: General Discussion of PinePhone Pro
Last Post: Rsquared
06-15-2026, 12:01 AM
» Replies: 0
» Views: 96
|
PinePhone Game Thread
Forum: General Discussion on PinePhone
Last Post: elinkser
06-11-2026, 02:50 PM
» Replies: 31
» Views: 80,034
|
Introducing RoutineHero: ...
Forum: General Discussion on PineTime
Last Post: oscar-gardiazabal
06-06-2026, 03:33 PM
» Replies: 3
» Views: 2,723
|
|
|
| pinephonepro.ini for Megapixels |
|
Posted by: biketool - 01-04-2025, 01:30 PM - Forum: Mobian on PinePhone
- Replies (1)
|
 |
Can anyone who has successfully built Megapixels in Mobian for the PPpro please post the contents of their /usr/share/megapixels/config/pine64/pinephone-pro.ini file?
Since this build of Mobian sid has libcamera I am guessing there is a good chance of megapixels working once I add this required file.
thanks!
|
|
|
|
| How to use QR codes on Mobian Sid(unstable) Pinephone Pro |
|
Posted by: biketool - 01-02-2025, 12:14 PM - Forum: Mobian on PinePhone
- Replies (1)
|
 |
With Mobian Sid we get a working libcamera so we can pipewire the sensors to the camera app.
Unlike Megapixels, which doesn't work yet on PPpro(some have succeeded in compiling in trixie), the system Camera app doesn't have a built-in QR reader.
It is a bit of a kludge but installing qtqr (it is a desktop package and needs scaling in Mobile Settings to work correctly, bring reading glasses)
Code: sudo apt install qtqr
lets you snap a photograph, then load that photo as a file in qtqr and either directly open a web link or load the text into the editor window on qtqr.
unless you really want a record of all the QR codes you read delete the files when finished. Qtqr cannot currently find the camera device so itonly works in this indirect way.
A kludge for now, extra steps, but I use my camera more to read QR codes than to shoot pictures.
I mostly use simple QR code plugin for firefox to generate QR weblinks on computer that I read with my phone.
|
|
|
|
| Keyboard issue |
|
Posted by: j0rs - 01-01-2025, 10:29 PM - Forum: General Discussion on Pinebook Pro
- Replies (3)
|
 |
Keyboard issue
https://forum.armbian.com/topic/47099-ke...are-issue/
Is there any chance to check if the keyboard failure is hardware or software related?
The keyboard stopped working correctly when computer was in the drawer. There was no possibility for any physical damage to the keyboard.
Can I solve the issue by myself or do I need to buy the new keyboard or use my Pinebook pro as a coaster only.
Thanks.
*UPDATE*
On top of keyboard issue - I solved it by buying external usb keyboard.
*I cannot power up my trashy laptop i.e. PBP.*
1a. battery disconnected, I used bypass cables.
eMMC with Armbian
Code: U-Boot TPL 2020.10-armbian (Aug 08 2021 - 16:26:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
Trying to boot from MMC2
NOTICE: BL31: v2.5(release):c158878-dirty
NOTICE: BL31: Built : 16:26:51, Aug 8 2021
U-Boot 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
Net: No ethernet found.
starting USB...
Bus usb@fe380000: failed to get usb phy
Port not available.
Bus usb@fe3a0000: failed to get usb phy
Port not available.
Bus usb@fe3c0000: failed to get usb phy
Port not available.
Bus usb@fe3e0000: failed to get usb phy
Port not available.
Bus dwc3:
All led are dead.
1b. - eMMC is disabled, Armbian on sd card
Code: U-Boot TPL 2020.10-armbian (Aug 08 2021 - 16:26:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
Trying to boot from MMC1
NOTICE: BL31: v2.5(release):c158878-dirty
NOTICE: BL31: Built : 16:26:51, Aug 8 2021
U-Boot 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
2. Battery is connected (with reset), eMMC disabled.
Code: U-Boot TPL 2020.10-armbian (Aug 08 2021 - 16:26:56)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
Trying to boot from MMC1
NOTICE: BL31: v2.5(release):c158878-dirty
NOTICE: BL31: Built : 16:26:51, Aug 8 2021
U-Boot 2020.10-armbian (Aug 08 2021 - 16:26:56 +0200)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 Pinebook Pro
All led are dead.
|
|
|
|
| Advice and experience on daily driving ppp |
|
Posted by: JadenSki - 12-30-2024, 05:48 PM - Forum: PinePhone Pro Software
- Replies (19)
|
 |
Hello all,
I've been distro hopping on my ppp for a little while now. And I am trying to figure out which os I should settle down on, to use for a daily driver. So far everything I need to work has not all worked out of the box on any os, which is to be expected obviously. And based on other's experience I am fairly confident that I can get most, if not all, of the main things I want, to work. However, this will obviously take time and effort, and the question is 'which os do I focus on getting working?' So I thought I would ask the community for advice/personal experience. If ya'll could take the time to let me know: 1. if you daily drive a ppp, 2. what os you use, 3. what desktop interface you use, 4. what do you have working (eg camera, calls, sms...) and 5 maybe just some simple tips that might be helpfull. I would be extremely grateful.
The main things I would like to work (listed in order of priority) are: sms, calls, mms, gps, camera (to some extent at least), and usb-otg. I would definitely prefer plasma mobile above posh, but if I cannot get everything working on plasma then posh is the next best.
Thank you in advance!
|
|
|
|
| PinePhone earpiece too quiet |
|
Posted by: Waffelo - 12-30-2024, 04:58 PM - Forum: General Discussion on PinePhone
- Replies (3)
|
 |
I got my PinePhone and I have been trying to call with people, but it seems like the earpiece is just too quiet and low quality because I cannot understand a lot of what the person at the other end says and also it sometimes sounds like those low bitrate chinese toy phones. I don't know if this is an issue with my distro or hardware but it is pretty annoying. I use ArchLinux with Phosh, I found the image from the official Pine64 software releases page.
|
|
|
|
| Improved battery life with TLP daemon |
|
Posted by: Surehand53 - 12-30-2024, 07:46 AM - Forum: Linux on Pinebook Pro
- No Replies
|
 |
In one of the recent Manjaro system updates TLP was mentioned as an option to power-profiles-daemon to manage battery life for the Pinebook Pro.
On the Pinebook Pro the TLP power management gives subjectively better battery performance over power-profiles-daemon. Especially sleep lasts over night without problems. My PBP is one of the earliest (second batch, I believe) and yet with TLP the battery performance is great.
The downside is that the PBP user interface feels slightly more sluggish in KDE Plasma. Everything seems to be a bit slower than it used to be. This might be different in a simpler (tiling) window manager. The TLP documentation mentions that their power management suits light users best (writing, etc).
However, the battery performance feels much improved.
If you are interested:
## Install TLP
Code: $ sudo pacman -S tlp
You will be asked to uninstall **power-profiles-daemon**, say yes.
There is an additional package `tlp-rdw`, check in the docu if you want that.
To enable the service use (and reboot)
Code: $ sudo systemctl enable tlp.service
## Config
I have used this config change to improve performance when power is plugged in:
Edit /etc/tlp.conf and un-comment and update:
CPU_ENERGY_PERF_POLICY_ON_AC=performance
You can check the config with:
Code: tlp-stat --config
tlp-stat -p
tlp-stat -p -v
If you want you can set `CPU_ENERGY_PERF_POLICY_ON_BAT` to `performance` as well.
Here is a link to the TLP documentation
# power-profiles-daemon
To switch back to the **power-profiles-daemon**:
Code: $ sudo pacman -S power-profiles-daemon
$ sudo systemctl enable power-profiles-daemon
And here is the link to some power-profiles-daemon documentation
|
|
|
|
|