Hi,
I am trying to enter single use mode.
The purpose is to move /var /usr and /home to a newly installed ssd.

I tried typing "init 1" and I got a black screen with a blinking cursor, no text input.
The same thing happens when I tried "systemctl isolate rescue.target".

Are there boot options to allow me to enter single user mode?
I could always boot from an sd card and do it from there, only I don't have one handy at the moment. Besides single user mode should work.

I've tried several different os's. And each time i try to make a call the diaper app closes the call screen. The latest one i tried was the kde plasma mobile image. The apn screen would not let me change anything or edit the apn. I did do an update && upgrade before trying. 

It's more than possible I'm doing something wrong. I'm so ready to ditch the Android ecosystem it's not funny. The biggest things I'm needing to do, is calls and texts. Which are supposedly working on most of the os's available. 

Any advice would be appreciated. 
Thank you.

Has anyone been able to get Bliss OS on a Pinebook Pro? Being that it's basically a desktop centric Android, it would seem that this would be a great OS to have in the list of images on the Wiki.

I finally got around to installed my nvme adapter and an SSD. A Sabrent Rocket Nano SB-1342-512 (listed as OK in the wiki). The SSD works as expected on every OS I've tried booting from an SD card (Debian, Ubuntu, Manjaro, Q4OS). The eMMC has the default Debian that came with the machine (update-to-date with both apt-get update/upgrade and the mrfixit_update.sh script).

The OS on the eMMC shows no sign I can find that the drive is there - no /dev/nvme* entries, nothing from lspci. modprobe shows the nvme modules present. I even went as far as to re-load the eMMC with the latest available debian image. The SSD showed up after the reload, but by the time I finished updating everything (as described above) and re-booted, it was gone again ???

So I'm hoping someone has a suggestion of where to look for error messages, diagnostics to try, ... The SDD works fine when booted from SD card (so I don't believe it's a hardware issue). It even works with the default Debian load, fully updated (like the one I put on the eMMC). What Am I missing?

I haven't tried loading a different OS on the eMMC yet. Thought I'd reach out before trying any more reloading ...

I am having an issue where my battery is being used up even when the computer is off.  I had it charged to 100% last night and when I turned it on a few minutes ago the battery was at zero.  I turned it off through the system menu and left it on bookshelf unplugged.  Is anyone else having this problem?  Any thoughts?

I have manjaro with plasma installed on the mmc if that makes a difference.

I haven't checked the other images, but for the Android 64GB bootable SD, I downloaded the file, and the MD5 didn't match the file gziped or not. Are the checksums up to date?

i would like to give you some feedback regarding the Rock 64 image. I have been using Ayufan LXDE image (version 0.83) for one year with Teamviewer and Dwservice and working fine. At my company several colleagues have done the same (Ayufan LXDE 0.83 + Dwservice.net or Teamviewer) without problems.

Nowadays i have updated to 0.94 LXDE version and all have suddenly stopped working. Even we have gone back to 0.83 and neither works. We get a blank screen, we can move mouse or type anything when connected on remote but cannot see the screen. It happens as in Dwservice.net as in Teamviewer.

Looking at forums of Teamviewer, it seems it is due a bug of the graphical driver or the graphical system. Contacting to Dwservice.net, they have connected to both versions and are neither able to identify the problem, they also say it is a problem of the graphical environment.

Has anybody feedback of this issue or a workaround?

Thanks.

Hello everyone,
I'd like to see the kernel boot messages instead of the splash screen when booting up my pinebook pro. I'm running on the default debian image.
In the wiki there is a section about it (https://wiki.pine64.org/index.php/Pinebo...e_messages) mentioning a u-boot config file at `/etc/default/u-boot/` and an update command (`u-boot-update`).
The problem is my filesystem has neither of those. The next best thing I could find is a config file at `/boot/extlinux/extlinux.conf`, suggesting the use of syslinux instead of u-boot.

Can someone clarify this for me? Is the wiki outdated or something is wrong with my installation?

I may be mistaken, but why is it called a pinetab when it looks like a pinelaptop? 

While I was waiting for the phone I had a lot of time to involve to installing the software, but when it arrived I had to work a lot and therefore I didn't have time anymore (actually I live in Austria and the phone took three more weeks to arrive, in those three weeks I would have had time). However, I had found the same the time to try pmos but tring to make phone calls I received an error of a still unsupported function and in addition the signal was really low and I could not even connect to internet. I hope I don't have any hardware problems, but I want to try again and I need some help to know if there is a distribution with connetion/calls already working so that I can test the phone.