Hi,

Anything I plug into the USB-C connector on the phone is very easily dislodged.  I mean I barely touch the phone and it comes unplugged.  Any suggestions?  It feels like things don't plug in far enough to lock into place.  Perhaps there is a cable extender/adapter that would help?

Thanks!

Hi,

I have a PinePhone convergence device and dock and when I plug in, the keyboard and mouse work fine but I get no output on the HDMI display.  Is there a maximum (or minimum) resolution that must be supported?  I'm plugging in a Dell Ultrasharp 27 (U2720Q) monitor (specs) which is a 4k panel.

Thanks!

Hi guys,


    I've bough a pine phone 2 months ago(approx) that doesn't outputting video through HDMI, it doesn't matter if I use the convergence adapter or other adapters(like ANKER USB-C adapters), I'm aware the same issue that has been reported by so many other users in this forum and unfortunately there's non advances from the pine64 hardware and software designer team, I'm know this is a beta phone/test device, but even on this phase of the product its crucial at least to have more info about this issue coming from the designer team[not the community/testers], I'm aware of the theories that exist around this issue(DRAM freq., lack of support to the USB PMIC driver) but again beyond this, first of all the HW team should post if they've changed something on the recipe on this batch(replace/remove some resistors, capacitors, inductor, active device, routing, etc) to certainly track from where this issue came from and help to the whole community and even to help the actual development. I really like the device.... but anyway.


btw I'll leave two different dmesg logs(I've used the 3.5mm FTDI serial adapter for extracting it):

dmesg_using_convergence_adapter

dmesg_using_anker_usb-c_adapter


I hope someone else could have more info about/advances of this and even if someone has already fixed it, please let me know.

Installed this OS by flashing a 32gig SD Card to a UbPorts 2Gig RAM version of Pinephone. Was wondering if anyone has like a few command lines to put into King's Cross/Bash terminal to add even more functionality to this OS? I mean I can already make calls and receive calls, but it doesn't seem to install apps from the Software store? Does anyone have like a helpful to do list to improve the experience on this? The potential is there, this could be the best OS out there for Pinephone so far, so I am stoked. It might even be close to a daily driver phone with a few tweaks. Thanks in advance.

Recently my Tab key got broken so I had to replace keyboard.
Price for new keyboard from official store however was too expensive for me, so I took the risk and ordered from HERE (total price inc. shipping was 27$ while price from official store was 20$ + 30$ shipping!).
Seller first asked about part number printed on keyboard cable, after providing number he warned me that cable is a little longer than original (this wasn't much of issue).
Keyboard arrived without the case, so I had to disconnect keyboard from the case. This was pretty difficult, because keyboard was hard-connected with the case with plastic caps, tearing caps off is irreversible. New keyboard fitted quite well, however holes in the keyboard didn't match perfectly, I had to push some spots in after keyboard was installed. I think height of keys is a little lower than in original, see picture.
Keyboard worked right away after booting (I have ANSI version from August 2020). Some keys are different (most notably right ctrl and Fn keys), these keys however work like on the original keyboard.
Updating to latest ANSI keyboard firmware from HERE worked fine.
If you want to save 30$ from shipping (seriously PINE64, why shipping to europe costs 30$) and you're not afraid of replacement procedure, this is viable alternative.

I've been using my Pinephone CE running Mobian for a few months. Recently, I apparently executed a command in terminal that has caused the phone on startup to display this message that I can't dismiss because I don't know the passphrase:

Enter disk decryption passphrase

Can I fix this easily? Or, should I flash and install another system on the phone? 

Hello,

I am looking to buy a Pinebook Pro ANSI. I am from the US.

I am willing to pay around 200 dollars for one in good condition.

Please PM me if interested.

after an reboot after an update my screen kept black after the kde logo. After messing around a rogognised that the backlight was of but the screen was working. With a strang lamp I was able to see enough to check the display brighness seams like it was set to zero. after setting it to a higher value everything was normal but setting the slider to a low value makes the phone unusable again.

It would be fine to make the allowed minimum high enough to actually see anything without an external light source.

Hello Community,

I am looking to buy a Pinetab with keyboard if anyone is interesting in selling one. I am in the USA.

Thanks,

As the title suggests, my problem is not related to any modem management software.

The first incoming call after the modem starts up works fine.
But after that first call, regardless of whether I answer it or not, new incoming calls won't go through - They won't even do the ringing tones on the other phone that I'm calling the PinePhone with.

If I had to guess, I'd say the modem is announcing to the network that it is busy or something like that, causing it to not receive any calls, because for what it seems, the call isn't even reaching the modem. Again, I'm just guessing, I don't really know how cellular networks work.
Is there any AT command that would set/unset some busy state like that?

If not, then I was hoping somebody could test to see if you get the same results:
1. Boot an OS and stop ModemManager (I suggest using an sxmo image, not sure how easy it would be to completely stop modem management on other UIs).
2. `sudo screen /dev/ttyUSB2` (or just use atinout or minicom if you prefer)
3. Unlock the SIM (AT+CPIN=<YOUR_SIM_PIN>)
4. Give yourself a call from another phone.
5. You should hear the ringing tones on the calling side.
6. The caller's number should show on the output of "AT+CLCC"
7. Hang up
8. Repeat from step 4. Does the call go through? Can you hear the beeping on the calling side? Does it show up on "AT+CLCC"? Cause for me it doesn't ;-(
9. If everything works without a problem, try again a couple more times just to be sure. It does have some unexpected behavior for me sometimes.

My firmware revision (AT+GMR) is EG25GGBR07A08M2G
Restoring the factory defaults with "AT&F" didn't fix it