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?

I placed my order last week, and I haven't gotten any sort of tracking info yet?

Does anyone on here know about their shipping habits, I paid for express, but I haven't heard back from anyone?

Have had this Pinephone (32 GB flash, 3 GB system memory) Beta with Convergence package for a few weeks.  Decided to return within 15 day return period as I need a phone with a smaller form factor.  Just checking to see if anyone wants to buy it first.  Have made no changes to software and OS that came with it.  Put in a SIM card and it works.  Sent a few texts and made a few calls.  Could not get my headphones to work with the headphone jack.  Please PM me with questions.  I can send photos. Reply by July 31st, as it will be shipped back then.

Hello,
I have a Pinophone equipped with the Pinephone keyboard (operating system: Mobian).

As indicated in the instructions, to recharge the Pinephone, I plug the usb cable from the charger into the usb input on the keyboard.
Until a recent update, with Mobian, once the battery was charged, the charge indicator showed 200%. It seemed a little strange to me, but considering that with the keyboard battery, the device has two batteries (keyboard battery + Pinephone battery), there is a logic to the matter… and there was no problem. My Pinephone had a battery life of about two days.

But since a recent update, things have changed:
I can still charge the Pinephone by plugging the usb cable into the keyboard input, but it seems that mobian no longer detects the keyboard battery.
After charging for a whole night, the charge indicator in mobian only shows 65% maximum. Also the keyboard battery doesn't seem to charge the Pinephone battery

Result: the autonomy of my pinephone went down to about ten hours!
Does anyone have a clue to help me?

Thanks

I'm using kernel 4.19 from the repo shared by Shaggy013 user with some modifications in the imx219 camera driver to support extra modes. I have backported the dts from latest RC kernel so mostly everything is working (hw encoding etc.) However the picture I'm getting doesn't look right(very dark, when camera gain is raised it looks very green - other colors are present so it is not un-debayered, but there is an excess of green). It may be simply because I'm getting a raw unprocessed picture, or there is some problem. At the same time I have the following errors. Are those errors perhaps related? Maybe ISP is not doing some image processing? (or perhaps I haven't requested it yet). Either way please let me know what those errors mean if anyone knows.

Additionally I get those errors in dmesg:
[    0.886617] imx219 3-0010: driver version: 00.01.02
[    0.911298] imx219 3-0010: Model ID 0x0219, Lot ID 0x4c2015, Chip ID 0x066e
[    0.912483] iommu: Adding device fdfe0000.rkcif to group 7
[    0.912540] rkcifhw fdfe0000.rkcif: Linked as a consumer to fdfe0800.iommu
[    0.913203] rkcifhw fdfe0000.rkcif: can't request region for resource [mem 0xfdfe0000-0xfdfe7fff]
[    0.915928] iommu: Adding device fdff0000.rkisp to group 8
[    0.915984] rkisp_hw fdff0000.rkisp: Linked as a consumer to fdff1a00.iommu
[    0.916183] rkisp_hw fdff0000.rkisp: is_thunderboot: 0
[    0.916216] rkisp_hw fdff0000.rkisp: max input:0x0@0fps
[    0.916259] rkisp_hw fdff0000.rkisp: can't request region for resource [mem 0xfdff0000-0xfdffffff]
[    0.917220] rkisp rkisp-vir0: rkisp driver version: v01.07.00
[    0.917639] rkisp rkisp-vir0: Entity type for entity rkisp-isp-subdev was not initialized!
[    0.917681] rkisp rkisp-vir0: Entity type for entity rkisp-csi-subdev was not initialized!
[    0.919844] rockchip-csi2-dphy csi2-dphy1: dphy1 matches m01_f_imx219 3-0010:bus type 4
[    0.920677] rkisp-vir0: Async subdev notifier completed

Looking at the dtsi that has those devices(it is included from rk3568.dtsi - I know rk3568 is a different device, but the include statement is the same as in mainline so I assume those dts entries are common to rk3566 and rk3568, but mainline of course doesn't support rkisp etc yet so I'm using rk3568.dtsi from the BSP) it says:
(scroll to see the whole thing)