It is a shame to see the Pine64, Rock64 and PinePro64 no longer being pursued by developers and enthusiasts. Posts to these lists are few and far between. But I understand that passion needs an object of desire and these no longer deliver. Other projects present an appealing challenge.
It would be nice to do more with these great tools. How to reach a wider audience with their potential? We need people who can think outside of the PC world with ideas from left of field, that have been ignored or abandoned by others. The Rasberry Pi has many of these fans. I wish some would come here and take the hardware to new places in science and engineering. My own bias is to see Fedora, and OpenSuse and other mainline distros available to try and reach the wider audience, perhaps with mainline kernel support. But this may not be necessary for some technical projects. What about a competition to find the best new projects for this under-used hardware?
My 2c.

Proud owner of Pine64, Rock64, Pinebook Pro.

I got my PostmarketOS edition phone today and the volume rocker seems to have no effect on the volume. Is this expected behavior?

I think lots of us agree phosh is a pretty undesireable UI, but im wondering, has there been an effort to improve it? Surely it could be made more efficient, faster, less clunky, less PHOSHY, right? A little housekeeping, some attention to detail. Some salt here and flair over there....

Anyway, if anyone does pick up this project, here beith thy list to launder:
1) smaller sharper icons
2) faster response from keyup (not 1 or 2 second lag)
3) full option menus (settings, camera, back, open bluetooth, wifi, data from top icons)
4) faster opening apps and rendering pages

Maybe some of this has to do with integration of the underlying distros, but i find all running phosh have the same phoshyness

Hi,

I'm digging a bit into the nuts and bolts of the PinePhone, and would like to have a ground up OS built working for when my 3GB PMOS edition arrives. I noticed on IRC that there are known issues with OS support and the 3GB PinePhone, so I thought I'd dig into what's going on, here's what I've found so far, but please correct me if I'm wrong 

• The root cause is that upstream u-boot doesn't support dual-rank dram on the R40/A64 SoCs, so it panics.
  
• There was a patch submitted upstream to the u-boot project, but never got merged (because it's RFC, I imagine): https://lists.denx.de/pipermail/u-boot/2...16856.html
  
• PMOS uses source from Pine64/u-boot, and then applies a local copy of the dualrank patch. (According to this APKBUILD)
  
• JumpDrive uses source from upstream u-boot, and then applies a couple of local patches (including the dualrank patch). (According to this Makefile)
  
• Crust uses source from Pine64/u-boot, and then applies a local copy of the dualrank patch. (According to the gitlab config)
  

• What's holding up the patch getting into u-boot upstream?
  
• Is upstream patch progress tracked anywhere?
  
• Is there anything stopping the patch being committed to the Pine64/u-boot repo? (Which would allow projects to simply point at that commit to get support)
  
• Is there anywhere where cross-OS efforts like u-boot fixes/kernel fixes/etc are being tracked and coordinated?
  

Hey,

I've had the Pinebook for three days. Today my mouse and keyboard are having issues. 3/4 of the time the mouse or keyboard will be unresponsive after KDE loads. Sometimes the keyboard will work. The mouse will work for a few seconds, then lock. Every time I do log in I get static sounds out of the speakers for a few seconds. Sounds like squawk from a ham radio. Disk issue? 

Any advice on what to do? Only downloaded a mail client, so no new software or hardware other than that.

Thanks.

Hello everyone. Just got my postmarketOS "Convergence" package in the mail. The phone itself works as expected. However, I'm unable to get any input/output (other than power) to work with the provided USB-C dongle. I've tried multiple mice, keyboards, screens, HDMI cables, etc. The keyboards and mice seem to receive power, but I get no indication that they're recognized by the phone. No HDMI output s detected by any screen I've plugged into it.

Any help would be appreciated.

1. I flashed the sd card with the latest jumpdrive.
2. I put the sd card in the  phone.
3. I rebooted the phone.
4. I got the message "jumpdrive is running"
5. I connected the phone to my computer
6. In the file manager "pmos boot" and "pmos root" appeared
7. In the linux terminal /dev/dm-0 appeared.

What next? How to flash the harddrive?

Hi.




Every few weeks, I search the forums and blog posts for news of the upgrade kit.



I would like to be notified as soon as one becomes available.  I worry that only a small batch of them will be sold, and I don't want to miss out!



I could just buy a Pro..  But.. You see, my spouse occasionally reminds me that I purchased an Arm-based laptop (My Pinebook 1080p) and never did anything productive with it.  So.. I want to upgrade it, and somehow imply that the original purchase was a wise one after all.



So.  I activated the "email notifications" option for this thread.  Please let me know when upgrade kits are available by replying to this thread!



Discussion of the upgrade kits is also welcome.  Here are is a search link to my other threads on these forums, all of which are related to the upgrade kit (at this time, at least!). https://forum.pine64.org/search.php?acti...r&uid=9462



Questions...



When I say Pinebook 1080p, does that refer to exactly one model, unambiguously?  Or must I be more specific?



Will the upgrade kit be compatible with the exact model of Pinebook I have?



Thank you, thank you,

--sebboh

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results:  ubports/2020-09-01-TMobile

Conclusion: This OS is not ready for the pinephone to become a daily driver.

Notes: Needed to restart phone to get audio after failed 4G test. Submitted an issue. Outbound 3G SMS broken, submitted a ticket. Needed to restart camera app to test. Initial load rendering was completely incorrect. (SPlit the image in half and put the bottom half on the top.) Also I did not test Verizon because results not likely to change. Instead I might begin testing PMOS since I just got my PMOS device today,


Issues:
Failed outbound 4G calls kills call audio.
Unable to send 3G SMS Since Dev-158
4G outbound calls broken.
Phone gets stuck in a weird lock state when spamming power button.

Below is a link listed from the Mobian wiki that should take screenshots once the "required packages are installed" my issue is it says notify-send isn't installed but when I use "sudo apt install bash libglib2.0-bin" as per the notify-send GitHub page, it says everything is installed. Has anyone tried this and had success? I'm at work right now or else I would dig a bit deeper.

https://puri.sm/posts/easy-librem-5-app-...creenshot/