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

in my area cdma is the only service that works. i cant find any carrier that supports my modom. my verizon sim works (mostly) but i cant stream on it. so im wondering if that because i cant register my imei? if anyone knows of a carrier that will, plese respond.

Got a brand new ROCK64 and would like to drive one of those SPI LED strips with it. I know I can do that with, for example, Python's [/url][url=https://github.com/doceme/py-spidev]spidev module.

So what is the best way to get from an empty SD card to a ROCK64 with spidev?

I noticed this thread from 2018 but I imagine the situation may have changed since then.

Thanks very much!

I posted the same question 5 days ago in "getting started" but perhaps it wasn't the right place.

I received my pinephone with mobian 5 days ago. After playing around and failing to update anything with the software update app, I saw I needed to do that via the command line and using dist-upgrade.

I did that but during the upgrade, as I was touching the screen to avoid the screensaver, I touched the battery icon and the phone immediately wet off. As I powered it up again, I could enter the password to decipher but after seing mobian and the logo, I have a graphical message saying that something went wrong in the session start and I need to try again, but f I power off and on again the same occurs.

Is there any solution apart from reinstalling mobian?

While the phone is connected to my PC running Trisquel, there is no device for it so I guess the only solution to reinstall mobian is to first install mobian on a SD card and after I have a working phone, I can try to access the eMMC to install mobian there again, but I am not sure whether that can be the installer at https://images.mobian-project.org/pinephone/installer/ that is copied to the eMMC directly or not (in order to install the FS ciphered).

I finally received my phone and the second day I apparently snapped the thin plastic in between the volume and power buttons.  When the back cover was removed the buttons fell off.  With a careful hand I was able to put it back together and buttons are working, however now I am afraid to take the cover off again when needed.  

I could go on blah blah.  My only question is does anyone know of a ETA on back cover https://pine64.com/product/pinephone-bac...46c16e2e66  availability?  


thanks everybody

I bought a Syncwire dual 3A charger and a USB to H barrel cable from the Pine64 shop to try out.
I thought that this would be useful for travelling because it should be able to charge the PBP and a phone at the same time.
Initially it worked well but then I hit a problem.
One day I let the PBP run totally flat, and the Syncwire would not recharge it.
I put this down to experience and suspected that the Syncwire was not performing to spec, but then last week a youtube video popped up with a fellow connecting a USB-C second monitor, and in the video he says that by connected a 5A power supply to the PBP it could run the monitor on a higher brightness than is possible with the standard 3A one.

This got me thinking that if the PBP is capable of pulling more than 3A then maybe when it is totally flat that it does, and maybe this causes the Syncwire to protect itself and shutdown?

Is this possible?

How does a totally dead PBP will recharge from the stock power supply?  Does it just current limit by reducing its input voltage?

Haven't received sms for about a week. I am able to send SMS. I am on Mobian and phosh. My carrier is Verizon

Here is what I have tried:

• running the mmcli to check for and delete sms. However MMCLI claims there is no messages.
  
• Janky-mms which I think probably just uses mmcli and had the same result.
  
• minicom -D /dev/ttyUSB2 with a couple of different commands (I can't find where I got these commands but they were supposed to clear the cache and reset the modem I think.)
  
• Changing APN
  
• Ran the following to check for messages on modem. Like above it showed nothing
  
  Code:

  socat - /dev/ttyUSB10,crnl
AT+CMGL