Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,701
» Latest member: Stunnned
» Forum threads: 16,260
» Forum posts: 117,188

Full Statistics

Latest Threads
Volumio (PINE A64-LTS / S...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: kapqa
Yesterday, 02:02 AM
» Replies: 8
» Views: 15,540
Reinstallation Arch Linux...
Forum: General Discussion on PineTab
Last Post: rth
11-22-2025, 08:25 PM
» Replies: 1
» Views: 217
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: brorean
11-21-2025, 08:45 PM
» Replies: 1
» Views: 160
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: brb78
11-20-2025, 04:15 PM
» Replies: 0
» Views: 119
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
11-20-2025, 09:04 AM
» Replies: 5
» Views: 617
Light Sensor / Proximity ...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-18-2025, 03:07 PM
» Replies: 1
» Views: 182
How to stop it turning on
Forum: General Discussion on PinePhone
Last Post: biketool
11-18-2025, 02:30 PM
» Replies: 3
» Views: 482
8/24 status of JumpDrive
Forum: PinePhone Software
Last Post: biketool
11-18-2025, 01:27 PM
» Replies: 5
» Views: 2,180
Questions about running U...
Forum: General Discussion on PineTime
Last Post: alicesphere
11-18-2025, 12:48 AM
» Replies: 0
» Views: 110
Difficulty with openSUSE ...
Forum: PinePhone Software
Last Post: danm1988
11-17-2025, 07:49 AM
» Replies: 0
» Views: 106

 
  Is the PinePhone board open source?
Posted by: jacobgadikian - 02-11-2020, 03:23 AM - Forum: PinePhone Hardware - Replies (1)

Hi!

I'm researching and developing hardware for Virgo.  

https://virgo.org/about/

Our end-goal hardware-wise is an open source mobile phone, and I wanted to follow up with you guys about the PinePhone.  

I'm curious if any of the hardware on the PinePhone is open source?  

For example, the PCB design, case, display, or anything else for that matter.


Thanks!

-Jacob 

PS: I really love the idea of phone as dev platform for mobile Linux, and I plan to pick up a PinePhone as soon as the next batch is available.


  very wierd, no boot, sort of fixed
Posted by: wdt - 02-10-2020, 11:56 PM - Forum: Linux on Pinebook Pro - No Replies

If this happens to you, something to try, costs little

This fairly serious, I just spent 2-3 hours to narrow it down
So, I thought I had broke it, the power button did nothing, removed q4os SD, still nothing
For some reason, I tried holding power 15 sec, nothing, thought try longer (and 20+ is right)
Then a short push and started right up, hmm, hmm
Put q4os back in, reboot, same senario (dead power button, hold 20+s, then works (q4os out))
Tried with nothing in SD slot, worked OK, tried with debian bullseye, worked OK,
tried with manjaro, worked OK (reboot worked, after shutdown restarts normally)
Checked 1st 16M, diff and cmp they vary quite a bit,
downloaded a stock mrfixit and updated, 1st 16 match (aside from mbr) (with emmc)
So q4os has some problem with uboot? or ibdloader?
I never did get q4os booted
why the 20 second push????
--edit-- SOLVED
turned out to be wrong card, identical (appearance) card hiding nearby
I wish there was a way to mark cards, that doesn't rub off or gum up SD slot


  Bug: When you initially boot it does not bring up the password screen
Posted by: realrichardsharpe@gmail.com - 02-10-2020, 09:34 PM - Forum: PostmarketOS on PinePhone - Replies (5)

I installed postmarkOS on an SDcard.

First issue, probably a bug with postmarkOS.

When you first boot it does not bring up the password screen. However, after some minutes of inactivity, it brings up the time/date display and then you need to enter the password.

Where should I submit bug reports?

If I can figure it out I will submit a patch.


  Brave Heart Not Vibrating?
Posted by: hnaguski - 02-10-2020, 05:18 PM - Forum: PinePhone Hardware - No Replies

So I received my phone recently, and in the factory tests the phone doesn't vibrate. Is this an issue with software or is my unit defective?


  No IMEI for Braveheart Pinephone?
Posted by: curtvaughan - 02-10-2020, 12:48 PM - Forum: PinePhone Hardware - Replies (4)

Forgive me if this has already on the web forums somewhere - I can only find references to topics about changing IMEI, or references to IMEI in conjunction with activating micro-SIM cards on the Pinephone.  I have Ubports installed on my Braveheart Pinephone that I received two days ago and got wireless to work with a couple of command line entries and a reboot. I've ordered an ATT compatible micro-SIM card, and once inserted, would like to activate the phone on my pre-paid account with ATT.  If I go to att.com/prepaid it looks as if I'll have to supply an IMEI number in order to activate the phone.  If I go to "settings>about" to looke for the IEMI number, "None" is listed.  Is this really the case?  Is there another path to finding out the IMEI of the phone?  How can one get around that in order to activate cellular service?


  Setup power profile from nvme bootscript
Posted by: korneliuszo - 02-10-2020, 10:56 AM - Forum: Pinebook Pro Tutorials - Replies (2)

Code:
[Unit]
Description=Set nvme powersave
ConditionPathExists=/dev/nvme0

[Service]
Type=oneshot
ExecStart=/usr/sbin/nvme set-feature /dev/nvme0 -f 2 -v 2
RemainAfterExit=yes

[Install]
WantedBy=sysinit.target
put this into /etc/systemd/system/nvme.service

and run systemd enable nvme
x (x)

#ir-ext-ui { position: fixed; padding: 1px; z-index: 9999; display: none; font-family: Consolas, "Lucida Console", "Courier New", Courier, monospace; text-align: right; }


  I messed up and flashed my phone
Posted by: obyx386 - 02-10-2020, 08:38 AM - Forum: PinePhone Software - Replies (2)

I accidentally flashed my phone. Is there any way to reinstall the phone's BIOS? I was unable to connect the phone to my computer (Linux Mint 19.3)


Video [Videos] Introducing the Pinebook Pro ANSI Edition
Posted by: Baldnerd - 02-10-2020, 07:50 AM - Forum: General Discussion on Pinebook Pro - Replies (2)

Here are the introductory videos I did for the Pinebook Pro ANSI Edition. Hope you enjoy!

Announcing Availability of the Pinebook Pro ANSI Edition



Unboxing the Pinebook Pro ANSI Edition with US Keyboard Layout



Disassembling the Pinebook Pro



Debian Linux: The Default OS on the Pinebook Pro


I hope to do more Pinebook Pro videos in the near future, so be sure to subscribe to my YouTube channel to ensure you see them.

For starters, I want to get my hands on the m.2 adapter and try it with a few different NVMe drives to see how it works. I also plan to show viewers how to move their home folder to the m.2 so they can use the eMMC as the boot disk but have all their files stored on the m.2.

Lots to come! Please let me know what you think and if you have any requests for future video series.


  pmboostrap to emmc
Posted by: Gobelin - 02-10-2020, 03:58 AM - Forum: PostmarketOS on PinePhone - Replies (5)

In order to install PostmarketOS on EMMC, Pinephone page on postmarketos' wiki instruct to run the following :


Code:
pmbootstrap install --sdcard=/dev/mmcblk(...)


I currently run postmarketOS from SD card (not the demo image, but current release), and still have stock test image on EMMC. The partitions looks as follow :

Code:
sudo ls /dev/mmcblk*
/dev/mmcblk0    /dev/mmcblk0p2    /dev/mmcblk2boot0  /dev/mmcblk2p1
/dev/mmcblk0p1    /dev/mmcblk2    /dev/mmcblk2boot1  /dev/mmcblk2p2

when I try to run :


Code:
pmbootstrap install --sdcard=/dev/mmcblk


I get the following error :


Code:
.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/home
(006470) [10:30:29] NOTE: (1/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (2/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (3/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (4/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (5/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (6/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (7/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (8/20) failed to find the install partition. Retrying...
(006470) [10:30:29] NOTE: (9/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (10/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (11/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (12/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (13/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (14/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (15/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (16/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (17/20) failed to find the install partition. Retrying...
(006470) [10:30:30] NOTE: (18/20) failed to find the install partition. Retrying...
(006470) [10:30:31] NOTE: (19/20) failed to find the install partition. Retrying...
(006470) [10:30:31] NOTE: (20/20) failed to find the install partition. Retrying...
(006470) [10:30:31] ERROR: Unable to find the partition prefix, expected the first partition of /dev/mmcblk1 to be located at /dev/mmcblk11 or /dev/mmcblk1p1!
(006470) [10:30:31] See also: <https://postmarketos.org/troubleshooting>
(006470) [10:30:31] Traceback (most recent call last):
 File "/usr/lib/python3.8/site-packages/pmb/__init__.py", line 63, in main
   getattr(frontend, args.action)(args)
 File "/usr/lib/python3.8/site-packages/pmb/helpers/frontend.py", line 196, in install
   pmb.install.install(args)
 File "/usr/lib/python3.8/site-packages/pmb/install/_install.py", line 547, in install
   install_system_image(args)
 File "/usr/lib/python3.8/site-packages/pmb/install/_install.py", line 397, in install_system_image
   pmb.install.partitions_mount(args)
 File "/usr/lib/python3.8/site-packages/pmb/install/partition.py", line 49, in partitions_mount
   raise RuntimeError("Unable to find the partition prefix,"
RuntimeError: Unable to find the partition prefix, expected the first partition of /dev/mmcblk1 to be located at /dev/mmcblk11 or /dev/mmcblk1p1!


Now, if I try :

Code:
pmbootstrap install --sdcard=/dev/mmcblk0
or
Code:
pmbootstrap install --sdcard=/dev/mmcblk1
or
Code:
pmbootstrap install --sdcard=/dev/mmcblk2
I got this error:

Code:
(006763) [10:42:19] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/dev
(006763) [10:42:19] % sudo du --summarize --block-size=1 /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone
1711869952    /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone
(006763) [10:42:19] % sudo du --summarize --block-size=1 /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/boot
53035008    /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/boot
(006763) [10:42:19] % sudo du --summarize --block-size=1 /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/home
8192    /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/home
(006763) [10:42:19] % sudo touch /home/laurent/.local/var/pmbootstrap/chroot_native/dev/installp1
(006763) [10:42:19] % sudo mount --bind /dev/mmcblk0p1 /home/laurent/.local/var/pmbootstrap/chroot_native/dev/installp1
(006763) [10:42:19] % sudo touch /home/laurent/.local/var/pmbootstrap/chroot_native/dev/installp2
(006763) [10:42:19] % sudo mount --bind /dev/mmcblk0p2 /home/laurent/.local/var/pmbootstrap/chroot_native/dev/installp2
(006763) [10:42:19] (native) mount /dev/installp2 to /mnt/install
(006763) [10:42:19] (native) % mkdir -p /mnt/install
(006763) [10:42:19] (native) % mount /dev/installp2 /mnt/install
(006763) [10:42:19] (native) format /dev/installp1 (boot, ext2), mount to /mnt/install/boot
(006763) [10:42:19] (native) % mkfs.ext2 -F -q -L pmOS_boot /dev/installp1
/dev/installp1 is apparently in use by the system; will not make a filesystem here!
(006763) [10:42:20] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(006763) [10:42:20] NOTE: The failed command's output is above the ^^^ line in the log file: /home/laurent/.local/var/pmbootstrap/log.txt
(006763) [10:42:20] ERROR: Command failed: (native) % mkfs.ext2 -F -q -L pmOS_boot /dev/installp1
(006763) [10:42:20] See also: <https://postmarketos.org/troubleshooting>
(006763) [10:42:20] Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/pmb/__init__.py", line 63, in main
    getattr(frontend, args.action)(args)
  File "/usr/lib/python3.8/site-packages/pmb/helpers/frontend.py", line 196, in install
    pmb.install.install(args)
  File "/usr/lib/python3.8/site-packages/pmb/install/_install.py", line 547, in install
    install_system_image(args)
  File "/usr/lib/python3.8/site-packages/pmb/install/_install.py", line 407, in install_system_image
    pmb.install.format(args)
  File "/usr/lib/python3.8/site-packages/pmb/install/format.py", line 94, in format
    format_and_mount_boot(args)
  File "/usr/lib/python3.8/site-packages/pmb/install/format.py", line 35, in format_and_mount_boot
    pmb.chroot.root(args, ["mkfs.ext2", "-F", "-q", "-L", "pmOS_boot", device])
  File "/usr/lib/python3.8/site-packages/pmb/chroot/root.py", line 90, in root
    return pmb.helpers.run_core.core(args, msg, cmd_sudo, None, output,
  File "/usr/lib/python3.8/site-packages/pmb/helpers/run_core.py", line 301, in core
    raise RuntimeError("Command failed: " + log_message)
RuntimeError: Command failed: (native) % mkfs.ext2 -F -q -L pmOS_boot /dev/installp1

if i try :


Code:
pmbootstrap install --sdcard=/dev/mmcblk0p1


I got this error :


Code:
(007060) [10:47:53] *** (3/5) PREPARE INSTALL BLOCKDEVICE ***
(007060) [10:47:53] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_native/mnt/install
(007060) [10:47:53] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/var/cache/distfiles
(007060) [10:47:53] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/var/cache/apk
(007060) [10:47:53] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/proc
(007060) [10:47:53] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/mnt/pmbootstrap-rust
(007060) [10:47:53] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/mnt/pmbootstrap-packages
(007060) [10:47:53] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/mnt/pmbootstrap-git
(007060) [10:47:54] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/mnt/pmbootstrap-ccache
(007060) [10:47:54] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/mnt/pmbootstrap-abuild-config
(007060) [10:47:54] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/etc/apk/keys
(007060) [10:47:54] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/dev/shm
(007060) [10:47:54] % sudo umount /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/dev
(007060) [10:47:54] % sudo du --summarize --block-size=1 /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone
1711869952    /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone
(007060) [10:47:54] % sudo du --summarize --block-size=1 /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/boot
53035008    /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/boot
(007060) [10:47:54] % sudo du --summarize --block-size=1 /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/home
8192    /home/laurent/.local/var/pmbootstrap/chroot_rootfs_pine64-pinephone/home
(007060) [10:47:54] NOTE: (1/20) failed to find the install partition. Retrying...
(007060) [10:47:54] NOTE: (2/20) failed to find the install partition. Retrying...
(007060) [10:47:54] NOTE: (3/20) failed to find the install partition. Retrying...
(007060) [10:47:54] NOTE: (4/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (5/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (6/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (7/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (8/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (9/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (10/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (11/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (12/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (13/20) failed to find the install partition. Retrying...
(007060) [10:47:55] NOTE: (14/20) failed to find the install partition. Retrying...
(007060) [10:47:56] NOTE: (15/20) failed to find the install partition. Retrying...
(007060) [10:47:56] NOTE: (16/20) failed to find the install partition. Retrying...
(007060) [10:47:56] NOTE: (17/20) failed to find the install partition. Retrying...
(007060) [10:47:56] NOTE: (18/20) failed to find the install partition. Retrying...
(007060) [10:47:56] NOTE: (19/20) failed to find the install partition. Retrying...
(007060) [10:47:56] NOTE: (20/20) failed to find the install partition. Retrying...
(007060) [10:47:56] ERROR: Unable to find the partition prefix, expected the first partition of /dev/mmcblk0p1 to be located at /dev/mmcblk0p11 or /dev/mmcblk0p1p1!


Does anyone know which command I should run to install on EMMC ?


  Setting Time and Date
Posted by: noeman5 - 02-10-2020, 12:23 AM - Forum: PinePhone Hardware - Replies (6)

Has anyone had any luck changing the time and date?  It seems to be stuck on GMT.  I can get to the setting that allows me to enter my location, it suggests my city, state, country but when I click on it, nothing happens.  If I try to manually set the time, it ignores the reset.  I've tried a couple of command line entries in terminal, but even those haven't helped.  Being connected to wi-fi doesn't seem to help, maybe once I get a carrier and connect it to their network it will force the change.  Anyone know?