It seems that being stuck on a blank screen after the pine64 splash screen is a pretty common issue lately. Most of the time it happens after an OTA update but for me, it happened as well when I hard shutdown my PinePhone after being unresponsive. 

I'm not sure if this is always the case but here's some steps you can try to recover your UT installation.

1. Shutdown your PinePhone.
   
2. Press and hold Power + Volume Up until it boots to the recovery mode screen (one that shows Installing Update)
   
3. Connect your PinePhone to a desktop/laptop via USB cable.
   
4. Check if all partitions in your UT installation, either emmc or sd card, can be mounted. In my case, the userdata is corrupted and cannot be mounted.
   
5. If you found a partition that cannot be mounted, run the command below
   sudo fsck /dev/<partition id>exampleudo fsck /dev/sdb10
6. The command will check for errors and you will be asked if you want to fix them. Just answer Y in those questions.
   
7. Eject your PinePhone and shut it down.
   
8. Turn it on and see if it boots properly now.
   

Has anyone tried calligra gemini ( https://calligra.org/gemini/ ) on their pinephone. This is made for touchscreen devices. This is created by the KDE community. This might be really good on the pinetab. Has anyone tried any office suites like libreoffice on their pinephone.

Hello.
About HW accelerated video with subtitles support. I've tried many OS images for pinebook 1080p, but this is one of the two things I couldn't figure out, to be almost fully satisfied with the device. On the factory default KDE neon, the video can be accelerated, but without subtitles or media control overlay. On latest armbian or manjaro images, the subtitles work, but even 420p video is lagging.

My questions are:
Why is it so hard to achieve HW accelereated video with subtitles/overlay on pinebook?
Has anybody figured out how to do this? (every OS counts) 

Thank you for your time and I'm looking forward for your replies.

Has anyone succeeded in running Plasma Desktop (not Mobile) yet? I quite liked it on pmOS after some tweaks. Much more than Pasma Mobile. It ran on X11 much better than on Wayland. But I had problems getting phone calls and mobile data to work so I thought I'd try it on Mobian.

Sddm runs without any problems. But when I start Plasma in X I get a black screen where only the mouse cursor is visible. It changes position with each touch so it seems to be working generally. But plasmashell doesn't seem to load. I couldn't find any logfiles, so no idea what's wrong.
It starts up properly on Wayland but crashes after a few seconds back to sddm.

The loudspeaker on my Braveheart Pinephone used to work in the past. Now I realized it doesn't work anymore, while both the earpiece and headphones continue to work normally. I cannot pinpoint the exact moment when it stopped working.

While I'm not certain this is a hardware problem, I've tried various current system images (ubports, pmos, mobian) as well a factory test image and even an older image from March (when I'm positive the loudspeaker was working) with no luck, so I'm inclined to think it is.

Did this happen to anybody? Any clues on what the reason may be? Any chance there is a solution?

Thanks.

As Manjaro is now the default OS as shipped from the factory I'd like to flash my PBP to the "official" OS.

Can someone point me to the correct image?

I've looked on the Wiki and its still debian-centric and the Manjaro section has various different desktop options.
Looking in the forums there are versions 19 and 20 manjaro threads, so I'm not sure which is the correct one that will match the version flashed onto the PBP in the factory.

Cheers

Hey y'all!

Some of the keys on my keyboard are not working, and I don't know if it's soft- or hardware-related.

My Pinebook Pro is an early model from last year. It arrived here in November, and right from the start the space bar didn't seem to work properly. Some of you will remember that back then there were some problems with the touchpad's palm rejection leading to keyboard inputs being dismissed. I have updated the keyboard/touchpad now, but the problem apparently has gotten worse, some of the other lower keys seem to not be working sometimes. The space bar flat out stopped working altogether.

Here's my question, is this a known problem with the software? I haven't followed development so closely since last year, and to me it seems like a random hardware problem. I'm evaluating what's the next right step (software patch, RMA, buy a spare keyboard and build it in myself, etc.).

Any information or pointers in the right direction appreciated.

Hi

Anybody knows the power intervall of RockPro64? I have only seen 12V. Plan to use it in a car.

BR
Mats Ekström

I haven't the search functionality on these forums, but someone must have considered using PBP with alter sbc like substantially more powerful odroid-n1.

Okay, so I have been having this issue for close to 2 months now, and I finally have enough time to play with.

I am a big fan of phosh DE, but I have been having this issue where, since March, I have had a problem where after start up I get a black screen, backlight on, that persists even through pushing the power button (sleep). Pushing the power button just cycles the backlight on and off, but the black screen remains. (though it did help me find a dead pixel). The only way to get it to stop has been to hard shutdown the phone and restart. This however, just restarts the cycle. It shows be the PmOS splash screen, flashes me the desktop menu and then shortly afterward, (usually before I can access the menu and turn on wifi) it does the black screen again.

So I have been doing random updates to new images since, only every few weeks due to class, with no change. I finally got done with the semester and have actually started messing with it again, and nothing has changed.

I have now tried building from pmbootstrap and using an image, they both do it. I have used USB network to get the wifi started and updated, it didn't solve the issue. Finally, I noticed that it seemed like the camera made a whole lot of noise shortly before the death, so I tried hardware kill-switching the cameras to see if that helped. It seemed to have worked for a bit, I could get into the menu and open settings, and even get into the terminal before it froze up and died. It also seemed to always be after I changed the brightness (not too low, just touching it), but it still happened, just later, if I never touched it.

Now it is still happening as soon as I touch the screen with the newest pmbootstrap build even with the switches flipped. The closest I ever got was with the pmbootstrap build and the switches flipped and I used usb network ssh to turn on wifi and seemed to have everything working until the update, and it started again. 

I have also tried phosh with pureOS and it does the same thing, (they called it the black screen of death) and they told me it could be fixed with hitting the vol+ and vol- 3 times each in under 5 sec. This did not work for their OS, nor for PmOS. So at this point, I'm really not sure what to do. Everything on the phone works fine with the terminal and ssh, but it wont let me use the screen with phosh.

Also, when this first started I tried PmOS with KDE plasma, and it worked fine. That was months ago and I haven't tried again since. I'm 90% sure it is something in phosh, but no one else seems to be having this issue. So, I'm not sure if it's something wrong with my hardware (would be weird since it doesn't break in other DEs) or something weird happening with me writing the images, even though I have done it a few different ways now...

Any help would be appreciated, cause I am really hoping to get to play with the phone some while I have this bit of free time. Thanks!

PS: If it's not obvious, I'm on a Braveheart.

PPS: Don't know if this is due to the voltage change to the screen, but it happened around the same time.