Still trying to use my Pine Phone as a cell phone, the closest I have came is calling another cell phone they could hear me but with the volume all the way up and holding my ear to the speaker I could barely hear them.

Have had the Pine Phone since 6-10-20 and have yet to make a phone call, send a text or take a picture.

At this point I either have a defective phone or Pine Phone has screwed me.

What are my options I am feeling the need to start a "Buyer Beware Of Pine Phone" campaign on several popular Social Media sites as the whole thing seems like a total scam to me.

Suggestions?

WHO EVER set up these forums and defaulted "Do not subscribe to this thread" is NO GENIUS!

This sites administrator needs to set the default to "Subscribe and receive email notification of new replies" If I have to explain why you should not be the administrator, you should also be changing the option FONTS to be BLACK AND NOT LIGHT GRAY on a BRIGHT WHITE background, what are you trying to hide and why

Thanks in advance

Hello All,

I have three PBP's running the pre-package Manjaro KDE setup. After a recent update one of them has been having this lockup problem a couple of times per day (with heavy use during the work day). The symptom is that the UI freezes, no mouse movement and no keyboard response.

I've dug through the journalctl logs to try to identify errors that could help to explain what's happening. Here are a few entries that are correlated with the time of the latest incident. I've tried searching for similar bug reports along these lines and they appear to be either very old and/or have nothing to do with the OS version and/or hardware set that we have here. I think the most striking thing here to me is that there are multiple segfaults happening and there's a serious error in the kernel. These are near the bottom below, but I've added other errors leading up in case they can provide more hints.

Upon starting up and logging in my new Pine64 Pinephone (KDE Community Edition Plasma Mobile Manjaro), expected Navigation buttons are missing. This is the X and square and icon in the middle at bottom of screen.  At the botom are three icons for Phone / Phone Book / Angelfish, but that's all.    I can open usual application like Settings and AngelFish but once inside any application there are no virtual buttons on the bottom of the display to allow "back" or "exit" function.   Is there some action or setting or update I can take to make them appear? I've tried swiping all directions, etc.   No amount of reboot makes these buttons available.  How to make navigation buttons appear, on desktop and  while within application?  Thanks.

Update Feb 28 - Running all updates, perhaps that will take care of it.

Hi,

I have my second pinephone now. It is the KDE Plasma Edition. I quite like the UI and it runs ok it seems. Only problem is, I am missing functionality like scale-to-fit that is available for phosh. I can't for example configure nextcloud client since buttons are missing on the UI. Is there something like scale-to-fit or wlr-randr for KDE Plasma?

Best Regards,

anhilde

I believe I read on the pine64 block or wiki that a pineobok distro 'should' or 'might' work on a pineTAB, possibly with some minor adjustments?
I know that is pretty vague .... sorry.  :-)

I was looking to try a Manjaro-ARM distro, and the TAB flavors lag the *book and *Pro devs by quite a bit. 

Thanks,
Dennis

Hi,
I've heard that gnome is working on letting gnome-clocks wake up the phone but didn't find anything in that regard.

So i experimented a little bit myself and got it to work with a little dirty hack. I don't really know a lot about the gnome ecosystem, vala, dbus, flatpack etc. so it really is a mess  but kinda working.

I first tried to write directly to /sys/class/rtc/rtc0/wakealarm from gnome-clocks when an alarm is changed but it outright refused to. Even with chmod-ing that file. I don't really know why but my guess it's b/c of some flatpack specific stuff.

So i wrote a small external program "waked" which let's other programs register alarms via dbus to wake up the system. It's just a little experiment and still relies on /sys/class/rtc/rtc0/wakealarm being chmodded but better then nothing. Running waked as root didn't work because then the dbus sessions didn't play nicely.

Then i slapped some spaghetti to gnome-clocks to register it's alarms in waked. Really messy, just a poc.

You can find the result here: https://gitlab.com/seath1
waked needs sdbus-cpp to build

What do you think, could that be a step in the right direction? I'm a bit surprised I couldn't find something existing to schedule rtc wakeups other than systemd timers which afaik doesn't let users add their own timers.

Hello @Danct12 ,

I've uploaded a package with some scripts to the AUR.
This package is a collection of shell scripts which sets up a USB Gadget interface and initiates a network on this interface.
The created network will use subnet 10.66.0.1/8 as it's subnet.

The purpose of this package is to facilitate easier means of debugging.
Sometimes the GUI on the Pinephone decides to fail and then it's difficult for a lot of users to obtain the valuable debugging logs.
This package ensures that the usb gadget interface is up-and-running.
Whenever you input a USB cable from any PC/Laptop it will initiate the network, and hand out a IP-Adress for the Host PC.
Now it's easy to connect to a SSH session with the command: ssh <username>@10.66.0.1
From here it's easy to obtain the neccasary debugging information such as dmesg and systemctl statusses etc.

You can find the package: https://aur.archlinux.org/packages/pinephone-dev-tools/

Let me know what you think of it.

Greetings
Jasper

Like many of you, I have been struggling to find a working browser for Mobian. Chromium was the most usable — until it wasn't. Half the time, it doesn't even load for me and I just get a gray screen.

On desktop, I use Vivaldi exclusively, which I would argue is the best browser ever made. I never had luck installing it on Mobian, because I couldn't find it in the right architecture. Well, If you go over to 'old versions' on their website, you can find a new, stable version of Vivaldi for Arm64.

After you install it, I would recommend you disable all animations, clean up the interface, and maybe find a tutorial or two on how to speed up Vivaldi. I would also go to developer tools (f12), click the three dots in the upper right, then go to more tools, network conditions, and under 'user agent' uncheck 'Select Automatically'. Then set the user agent to Chrome, Android Mobile (high-end). Then restart. This will cause far fewer sites to deliver the full desktop version of their site when you're browsing.

I'm still getting some horizontal scrolling on some sites, but luckily, Vivaldi has a zoom slider right in the status bar, so it's easy to tweak sites on a case-by-case basis.

Vivaldi also has an integrated mail client and calendar now, and they also work on Mobian. I haven't spent too much time with these, but they display at the correct scale, unline Geary and Gnome Calendar.

Hi I am starting to use the USB-C deck to connect to my 4K monitor.

The description for the item on Pine store is 4k/P30 (means 30 fps?), and that's what I got when I am using it. But on the other hand the USB-C to HDMI converter I had is allow me to select 4K at 60 fps on the display setting, where the PBP deck only allow the 4k 30 fps selection. 

Is it possible the HDMI cable I am using the bottlenect, there isn't any meanful lable I can tell. Happy to buy a new one if it might be the issue? But on the other hand, it might be a hardware limitation due to the deck need provide USB3 and HDMI outputs at the same time from a single USB-C connected to the PBP for input?

Hi,

as some of you might know there is a known issue with handling of PCIe errors on the RP64 as discussed here:

https://forum.pine64.org/showthread.php?tid=8374
https://forum.pine64.org/showthread.php?tid=6329

I am getting this error when I try to build/rebuild my RAID for the first time. Sometimes I am lucky and it works, but most of the time it does not and I don't have much confidence in putting my backup on a machine with a malfunctioning PCIe interface. If it happens, I see entries like these in the logs: