Hi,

I dont know if this is the right forum for this. 

I am looking for a document or guide on how to integrate a working wifi driver for the phone to a simple rootfs that is not based on any distro.

I am trying some trial and error referring to a PMOS rooots dump. But it would be nice to understand the method in detail.

I am using the pinephone as a device to know more about low level working for a linux device. 

Thanks in advance.

According to the braveheart v1.1 errata in the section entitled "Excess power usage while driving VBUS" it says:

" the PMIC continues to draw power from the USB port, and this doubles the drain on the battery (since the whole phone is being powered by the USB OTG boost regulator). This could be fixed by populating R1300."

My naive reading of this is that without populating R1300, the battery is always going to get double the drain.

I'd like an honest answer therefore to the following question:

1. Can we expect normal battery performance from the v1.1 BH edition phones at any point, i.e is there a software fix, or is this unfixable?

Much appreciate being part of the BH cohort and don't regret my decision, but would like to know if the phone will ever have a practical battery life

Cheers

Ashley

Hi, I was asking my self, (but I think I have the answer), how much current in mA is the max supported by a PineA64+ board, I will plug a hard drive(2,5") in USB port, I´m using wireless module, and runing Pihole and NextCloud services.

I have 2 DC sources that provides 5v/4400mA and other 5v/3000mA, so I would like not burn it , any advice?

My answer is supplied by table 5.6 in (http://files.pine64.org/doc/datasheet/pi...t_V1.1.pdf):

CPU:----------------2000mA
memory:-------------800mA
USB:-------------------80mA

Total:---------------2880mA


I guess 5v/3000mA is enoug, but can I use the 4400mA source?

Since Rockchip released Android 10 last month for all their chipsets, hope it will also be released for Rock64.

When I I try to login the screen turns black then goes back to the login screen.wtf any idea how to fix this ?

No audio on PBP as delivered. Read message about trying with another operating system. After much trouble I succeeded in booting OpenSuse (from microSD); still no sound. Am I not doing something (in config files), or have I got bad hardware?

I'm looking to upgrade from a Raspberry Pi 4 2GB to a RockPro64 4GB.

Is anyone running Gentoo?  I did a forum search but only found one user working on an image back in 2018 but didn't seem to get too far.

I mostly need to figure out how to get a minimal stage3 to boot and I can probably figure out the rest from there.

Thanks.

[Edit: here is a video showing the issue: https://youtu.be/9qhO412xwaE ]

So my PinePhone arrived today - and I have to say from afar the phone looks just like any other modern smartphone (which is great) - replaceable battery is a godsend and the hardware switches on the back much appreciated. All in all this is a very well made device.

Mine just has one issue, and I wanted to discover if others have the same issue?

** Now firstly - I know when you order a PinePhone it says - 'if you are going to complain about the odd dead pixel then please just don't order the phone' - I nearly didn't write this for that reason - but I believe my issue doesn't fit that criteria, a dead pixel is cosmetic - this significantly handicaps usage, so here goes **

Can I buy a new touchscreen to install myself? Mine came damaged, in the centre, about 60% of the way down the screen - I have no issue with it looking bad - I don't care - I really don't. The issue is it makes it impossible to press the screen at that location, the affected area is about 0.7cm by 0.7cm. It is most noticable when I try to type text on the inbuild keyboard in Ubuntu Touch for example - when I click the 't', an 'r' appears. I know the issue is the touchscreen as if I turn the phone upside down or rotate it, then the keyboard works fine.

So this isn't meant to be a moan - just simply that my PinePhone came disabled, and I'd like to know how easy it will be in the future to fix it?

In the meantime I turn the phone upside down when I need to press that part of the screen - which obviously will only work where implemented in software.

Does anyone else has an issue whereby they literally can't touch a reasonable large part of the touch screen - right in the middle?

This is most probably due to my lack of familiarity with Arch/Manjaro but running Manjaro 20.04 KDE (from a sd-card flashed earlier today) I have a problem with an update. the system tells me there are 150 updates available and after pressing the key to start the update it starts downloading and checking integrity. Then it encounters an already exisiting file and quits with an error.
Installation of a single package halts with the same message:

Was just catching up on threads from over the weekend, when I came across this post, specifically:

maxjrh:

Quote:Binaries called "chrome" or "chromium" are explicitly blacklisted by the panfrost driver.