I got a USB-C to HDMI adapter cable and a USB-C to mini-DP adapter cable, and with both of them the right 1/3rd of the screen is bad, digital noise or whatever.

Is this normal? Or is my PBP video output bad? Or could the adapters be not well adapted?

Switching to Full HD video works fine, so it's not a major problem.

Anyone know why I world be getting three vertical bars when I reboot? Does not happen if I shut down and boot. Only on reboot. Any ideas?  https://photos.app.goo.gl/GvTcWRq6KL9VAQys6

I am trying to copy the Manjaro KDE 20.06 image to an SD as step one in creating a 128G eMMC. Have been doing so for over a week.

I was able to create an XFCE SD and eMMC with no problem. Both worked fine. I've tried all the methods I have seen on the forums, but always end up with a non-booting KDE SD and a perpetual green led. Well, all methods but the installer script at https://gitlab.manjaro.org/manjaro-arm/a...-installer. That requires binfmt-qemu-static, which is not in the Arch repository.

So I'm at a standstill for the time being. My PBP is still working fine with the original KDE 64G eMMC or the XFCE 128G eMMC that I made. The XFCE UI is just not what I need.

I'm getting ready to see if a PBP will work as a frisbee. But, until I get to that point, has anyone any ideas that might prevent a flying PBP (not really, I quite like it)?

---

Big edit.

All is well. Boot problem resolved. It was a matter of paying attention.

Today I created a new KDE image for my SD using the Raspberry Pi Imager on my Mac, which works great with no dd, etc., although dd works fine, too. I then tried to boot it and got the perpetual green led again. OK, only thing left was to turn off eMMC. Did that, and poof! Booted as it should. That's an important step, because the machine remembers last boot.

I powered down, switched eMMC back on, and rebooted. Worked fine because the machine remembered it booted last from SD.

Next, I downloaded another image and check file, did all the check and prep, and wrote it with dd to the eMMC. Powered down, removed SD (getting smarter), and restarted. Perfect. Running KDE from my new 128G eMMC.

This was not wasted effort. I learned a lot from the process.

I first experienced the Swype on the Nokia N9 (Harmattan). It was probably the only saving grace (in my own backward mind) that gets me to occasionally use a touch screen, as I really clung hard to physical keyboard for as long as I could, and still prefer to make notes on my Nokia E90 (Symbian).  Is that input method possible on the Mobian Pine Phone? For that matter, is fine handwriting with a stylus possible? 
Would appreciate someone pointing me in the right direction.

Just wanted to say thanks to the support team because they gave great support fast, so thanks.

When I first ran the Pine64+, using Debian, I had a couple of distribution supplied shell scripts that I would execute when updating the software.

/usr/local/sbin/pine64_update_uboot.sh;
/usr/local/sbin/pine64_update_kernel.sh;

Those scripts don't seem to be supplied with Armbian.

Is there a different way in Armbian that boot and the kernel get updated?

Thanks

CVBruce

I got my phone yesterday and it seems to be working per the various caveats I've been reading about online.  So I decided I might as well turn off the cell modem since it seems it will be a while before it's ready to use.  This seemed sensible since it devours the battery and the software toggles on the radios still seem a bit flakey.  However, when I turn the cell modem (sw1) off, wifi no longer appears functional in that I no longer see any access points.  I toggled sw2 off and back on thinking I might have accidentally flipped it too, but that didn't seem to help.  When I turn sw1 back on, I again see wifi access points and can connect.  I've been powering down the device before changing switch settings.  I'm (possibly incorrectly) assuming this is a software issue as it seems like something that would have been noticed if it were hardware... or it could be a problem with my device?

So I've posted about this issue here before; tried some things, still having same problems.

The short of it is that the wifi sucks on this device (or in Debian). I received the Debian 9.12 release early this year, having pre-ordered I believe around October of last year. Did all the related update stuff, etc. to get it running.

The only way I can keep a consistent connection on the device is that I have created a bash script that starts automatically at login, running an ongoing ping to yahoo.com. It runs in the background and when it is running, wireless works good. If that ping dies for some reason, soon the wifi drops and will not connect again. It was the only solution I could come up with to just get this thing to stay on the network.

I specifically ping the domain name (yahoo.com) to verify DNS resolution, which is odd. If I run a regular IP ping, it will work, but not as quickly as when I resolve DNS first; even pinging on my own network. However, opening a browser and going to yahoo.com or another website doesn't seem to pull off the same "kick-start" that the ping is doing; it won't resolve and display the page.

So, I'm open to any suggestions about a better OS to run, or something to make this thing run as it should. Love the hardware, I just think that the release with Debian 9.12 has been ....whatever.

Does anybody know a way to transfer files from a Linux desktop (POP OS 20.04) to the PinePhone using Mobian? The desktop doesn't recognize the PinePhone when connected through USB and I haven't been able to figure out how to transfer files.

Any help would be much appreciated. Thank you.

I saw people installing different icons, which is a pretty cool bit of customization.
I was wondering, is there a way to set a different icon-sets from UI or does that have to be done from CLI?