Hi

Recently I repaired the screen on my PinePhone and I had some issues with the USB-C board that are now fixed, now the loud speaker isn't working, any ideas?

As fun as the terminal is I would like to have a desktop environment again.

I am running Manjaro-ARM-phosh  on a UBports Edition pinephone.  I ran the latest update on Sunday and after I rebooted it did not boot into the desktop environment.  With an external keyboard I can still login and run terminal commands so I was hopeful a new update would fix the issue but yesterdays update did not change anything.  Is anyone else having this issue or just me? Any suggestions on a next step? I could always flash a new install on but I would like to learn how to fix this in case it comes up again.
thanks

Hi, I'm trying to get the new Debian installer RC3 to give me a working Debian server on the RockPRO64, but I'm stuck. I'd like to know if I'm missing anything. The steps I followed are:

• Got testing/unstable daily builds from: https://d-i.debian.org/daily-images/arm6...rd-images/
  
• Squashed the images together as instructed
  
• Flashed to a USB with Balena Etcher (A few months ago I flashed a U-Boot image from Ayufan to get USB boot working)
  
• Put USB into the USB 3 port (No SD or eMMC inserted)
  
• Installer starts successfully, run until partitioning
  

• 500MB ext2 mounted to /boot, bootable flag enabled (Boot from USB because U-Boot doesn't seem to support SSD's yet)
  

• 56GB ext4 mounted to /
  
• 2gb swap at the end
  

• 2TB ext mounted to /hdd
  

Hi, I have been long watching this product and waiting, and like many was glad someone finally chose the smartest choices to make it easy for developers AND users.  KDE + Manjaro is brilliant!

My UX/UI idea is mostly an idea about how to arrange a mobile phone screen so that it is just like using a computer.
I want to actually like using a mobile device, in the way i like using my computer.  If it was structured the same way, it would help it be more intuitive.

   

I hope it is clear.  This is a mockup, but the circles are 72px, spaced 20px apart.  I chose this for accessibility reasons, but of course users could decrease the sizes and fit more circles, as well.
Light grey represents your ~/Desktop.  This is handled by any file manager that handles it.
The top and bottom panels are again, any one that works.  The bottom panel would "Intellihide" and serve a purpose like many mobile phones but actually be useful, and let you use it like a computer, and add any other applets you like, etc.

Are there any filemanagers that currently support different sets of Desktop items per virtual desktop?
It would be really easy to implement for a mobile-only solution.  If it already has some sort of XDG standard, I apologize for not knowing

Of course you could use a different configuration when the dock is plugged in.
It would be pretty easy for new users to figure out to push the big middle circle to find a program, even if they were inexperienced, it would be like the whole 'start' button thing.  Just make a nice big green Pinecone outline with an appgrid cutout
Anyhow, let me know if anyone is thinking along these same lines.

Hi

Recently I attempted a PinePhone screen repair and when I tried to power the phone on again the screen worked but the phone was constantly vibrating and wouldn't take charge, any ideas as to what the problem could be?

Thanks

Hi

Anyone with good experience of a industrial memory on RockPro64?
The memory card shall handle S.M.A.R.T-interface and support fort smartctl from https://www.smartmontools.org.

BR
Mats

Hi all for the past couple months I've been having some stability issues with my RockPro64 NAS. It would just seem to hang and require physical power cycle to get back online. About a week ago it seems to have given up the ghost.

This evening I hooked up an ftdi232 so I could look at the serial console as it attempts to boot, and I'm getting output similar to below pretty consistently, but with slight variations. I'm not so deep in the weeds with SBC init procedures to make too much sense of this, but "Cap error!" seems to indicate to me that there may be a faulty capacitor somewhere on my board, and the failure to read a given memory address seems to indicate that it may be a capacitor related to the ram chips. My question is, is there a good way for me to test and identify which if any capacitor may have gone bad so I can try to re-solder a new one on? If its the ram I'll resign myself to tossing the board as I don't have a reflow station, and the wife would kill me if I tried to use the oven to do that. I have a basic multimeter, and a cheapo oscilloscope from aliexpress if those tools may help drill into what I may need to replace here.

I'd really like to bring this little computer back to life if its not too much headache. This thing lasted me less than 2 years. For $80 I expected a lot better components and QC. I have an early 1st gen Raspberry Pi that's still chooching at 19 years old.

To install Mobian on an SD card I, all I theoretically have to do is to download mobian-pinephone-phosh-20210314.img.gz, write it to the card, put the card into the phone and start it, right?

However, when I do that, the "resizing file system during initial boot" screen is there for quite a long time (30 minutes maybe) and afterwards the screen turns black (not pitch black though, the display remains switched on) and that's it.

I have used two different 64 GB cards  (a new Sandisk Extreme and and old Sandisk Ultra). I tried

Has anybody run motion eye on the cube?
Also can you write an image to an SD card and boot with it like the Pinephone or a Raspberry Pi?
I have tried motioneyeos-pine64-20200606.img.xz and I was hoping to get it to connect to my network so I could avoid the serial-terminal process.
I haven't found any basic instructions to get this up and running.

Hello everyone

I'm new to this forum and joined here to follow the development of Sailfish OS on Pinephone and the utilization of killswitches that appear to be very unpractical location wise. So is there any modification available to allow the killswitches be used without removing the whole back cover? Like some sort of switcher slider in the cover or something? Or is the only option to burn or drill a hole to the cover oneself If you want to keep the mic off always when not having a call?

Thanks