Sorry if this has been asked before but I have not followed pinephone development for a year or two.

I received the PPP today and updated pacman-mirrors followed by a full system upgrade via `pacman -Syyu'

During the update I get a Y/N prompt asking if I want to replace 'kwayland' with 'kwin' . I decided no as I thought this was a bug and the system was attempting to install the default plasma window manager (A big assumption I know, but a search at the time turned up nothing).

Following the update everything seems to be working fine (so far) with the exception of screen locking.

When attempting to wake the screen, instead of the lock-screen I get a text message I can not fully see due to it's size, something along the lines of " lock screen broken". Turning the screen off and back on presents me with a lock-screen that looks like a desktop and asking for a pin but no virtual keyboard is available to deliver user input.

Since I haven't been following development I don't know if the lock-screen misbehavior is 1) From my decision not to replace kwayland or 2) From the update or 3) a common bug everyone is dealing with.

Any insight  to help me get up to speed would be greatly appreciated.

HI
I have Rock64 v2. I ran debian 11 on it. It works.

How to turn on the sound on the headphones? On HDMI, sound and picture work.

alsa-utils is installed

speaker-test -c2 -D hw:0,0    --- headphones - it's quiet
speaker-test -c2 -D hw:1,0    --- HDMI is ok

Quote:root@rock64:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SPDIF [SPDIF], device 0: ff030000.spdif-dit-hifi dit-hifi-0 [ff030000.spdif-dit-hifi dit-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDMI], device 0: ff000000.i2s-i2s-hifi i2s-hifi-0 [ff000000.i2s-i2s-hifi i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I have an up to date PinePhone Pro with Siglo and my PineTime is running Infinitime 1.10.0. The watch shows an active Bluetooth connection but the watch is not receiving any notifications. Any idea how I can get notifications to work? Thanks.

As many no doubt know one requires this proprietary windows tool called RKISP2.x_Tuner to adjust camera calibration files (iq files).

Unfortunately I believe this file was never officially released by rockchip despite it being claimed to be present in exernal folder of the SDK. There are some references in the documentation to "contacting rockchip about a commercial service" if one wants to get a camera chip work. However I have found older versions of this software on the internet. But the version of the tuner software has to match the AIQ kernel driver and the library and the latest now is version v2.0x60.1.

Therefore if anyone has access to this tuner software version v2.0x60.1 please let me know. (alternatively if you have an iq file for imx219 that would be good too).

I found an imx219 iq file for an old version of AIQ. It was in ASUS tinkerboard 2 image, but alas, an old iq file will not work with the new driver and it is not possible to downgrade because rk3566 requires driver 2.x.

I hope there is a solution this. Otherwise this may severely limit the usefulness of the rockchip platform for quite some time. There is only a small handful of camera chips supported that doesn't include the most popular sensors like ov5647, imx219 etc.

Good evening, 

I just received my PinePhone Pro and already a whole list of issues. Below I would give a summary: 

1) Downloading applications from Discover is not possible. In the application, the errors: 'The Packagekit daemon has crashed', 'Too few items to process', 'Internal error' and 'Message recipient disconnected from message bus without replying'. 

2) Through the terminal it is not possible to download git then it gives the error 'file /var/cache/pacman/pkg/manjaro-system-202619-1-any.pkg.tar.zst is corrupted'. 

Do any of you have an idea to fix these errors?

I just received my PinePhone Pro. The phone says there are 298 available updates. When I try to update through the app (not the command line), the update fails but does not give an error code. I would be grateful for any help with this. Thanks.

I was trying to distro-hop without an eMMC adapter (there's one in the mail but I got impatient) but my SD card wasn't being recognized. Being the clown that I am I thought it was an issue with uboot booting from eMMC before the SD card even though I know this not to be the default boot order. Being an even bigger fool (and in my defense after about an hour of troubleshooting and a long day of work) I decided to break rule 1 of computing and blindly copied a command I found online thinking it would solve my issue.

I then ran the following command in u-boot:  

(08-12-2022, 02:47 PM)jpalus Wrote:

(07-27-2022, 11:20 AM)Tango Drango Wrote: does anyone know what the default bootcmd environment variable is?

You can always restore default environment with:

Code:

env default -a

Note that it restores settings for current "session", to persist do:

Code:

env save

For more details see:
https://u-boot.readthedocs.io/en/latest/...d/env.html

A few months (or maybe even more than a year ago now) my PineTab broke itself, possibly the battery swelled and destroyed the screen, I’m not sure. But there’s nothing I could do about that since there aren’t PineTab replacement parts available. 

A member of Pine64 did reach out to me offering a replacement PineTab as well as some other stuff to review on my YouTube channel, which was much appreciated but sadly that never went anywhere and I never got much word as to whether it was still going ahead or not.

I get that the Pine64 team are busy but I can’t help but feel frustrated since I’m left with not much word as to what’s going on and a PineTab that I can’t use (which is a shame because I love the PineTab)

Pinephone craches after each call and needs to be restarted

Is there something like a battery management for the PinePhone?
If you plug in the usb charger, the battery level will raise up to 100% (as expected).
Would it increase the lifespan of the battery if battery level would be kept in a reasonable range (e.g. between 60% and 70%)?
Would it increase the lifespan of the battery if charging is not with full power (1.5A) if not needed?