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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,713
» Latest member: vicentewilson
» Forum threads: 16,264
» Forum posts: 117,211

Full Statistics

Latest Threads
what is the point?
Forum: General Discussion on PinePhone
Last Post: Zebulon Walton
Yesterday, 03:07 PM
» Replies: 5
» Views: 216
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
Yesterday, 07:38 AM
» Replies: 3
» Views: 11,847
Danctnix USB GPS for Pine...
Forum: PineTab Software
Last Post: biketool
Yesterday, 06:09 AM
» Replies: 0
» Views: 48
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: biketool
Yesterday, 03:39 AM
» Replies: 10
» Views: 6,777
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: realchunkyflea
11-27-2025, 05:01 PM
» Replies: 3
» Views: 274
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-27-2025, 04:23 PM
» Replies: 2
» Views: 89
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
11-27-2025, 10:30 AM
» Replies: 10
» Views: 15,928
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
11-26-2025, 02:45 PM
» Replies: 10
» Views: 16,858
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: j_s
11-26-2025, 11:33 AM
» Replies: 4
» Views: 278
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
11-26-2025, 01:42 AM
» Replies: 1
» Views: 182

 
  Manjaro convergence edition (3GB) charging/power issue
Posted by: Saliency - 11-24-2020, 12:53 AM - Forum: Mobian on PinePhone - Replies (1)

With my newly received 3GB device flashed to Mobian 11/13 image, it seems the battery will not charge beyond 50%. Furthermore the Powersupply app does not report charging when plugged in, although Settings->Power does. 

I will revert to Manjaro tomorrow to make sure it’s not a hardware issue with my device.


  Android apps on Pinephones
Posted by: Raniyah - 11-23-2020, 10:34 PM - Forum: General Discussion on PinePhone - Replies (1)

As I've learned here, PinePhone is running a Linux OS. Though I keen on Pinephones still there are some Android apps I love to used such as Youtube Vanced (Not Google's official app and also not available in the Play store). Is there any chance to use such apps on Pinephone like we emulators to run Android apps on PCs?


  default password for Manjaro pinephone
Posted by: Raniyah - 11-23-2020, 10:12 PM - Forum: General Discussion on PinePhone - Replies (1)

Does anybody know if there is a default password for Manjaro pinephone? One of my friends received his Manjaro pinephone and no password to unlock the locked screen after boot.


  Endless crashes on Pine64 received today
Posted by: luciphercolors - 11-23-2020, 09:01 PM - Forum: PinePhone Hardware - Replies (4)

Hi all,

I received my PinePhone CE 3gb today and was eager to get started tinkering with the device. I expected getting started would be a bit bumpy but nothing as bad as what I encountered:

Basically the device crashes to a black screen after more than a few seconds of use. Sometimes I have enough time to enter my pin, though usually not. I thought maybe it was something with battery (nope), something to do with whether a port splitter was plugged in and HDMI was in use (nope), or with my Wi-Fi (nope), or with Manjaro (also no). I've flashed Manjaro-ARM-phosh-pinephone-beta2-20201119, Manjaro-ARM-plasma-mobile-dev-pinephone-alpha7-200818, and mobian-pinephone-phosh-20201113 and they all do the same thing.

The only OS that seems to run for more than a few minutes is Jumpdrive 0.6, and *possibly* the stock manjaro that shipped on the device. I would like to re-load that version on just to be sure but I can't figure out what build it was actually running.

In any case I found a thread on these forums (here: https://forum.pine64.org/showthread.php?tid=9832) that seems to indicate the issue may be related to RAM clock speeds being too high. The problems people describe there match what I am experiencing.

I would like to apply these patches but I cannot get the device running long enough to feel comfortable deploying them!

Looking for advice on how to proceed, because right now about all this phone is good for right now is being a bulky 32gb USB drive. Should I seek out the last known-good build and run on that for the time being? Is my device busted? Should I sit tight for a while and check back in a month?

To be clear, I can't even get the device up long enough to claim an IP address over its ethernet link, and even if I did the whole thing crashes in a few minutes! (And worse, the included USB port splitter doesn't lock into place, so even slight movements unplug it!)

Is there something I can do with Jumpdrive over telnet to fix this?

Thank you in advance, and I apologize if I'm noobing up the place

Tom


  just booted up my phone greeted by an unlock screen
Posted by: dallytaur - 11-23-2020, 08:56 PM - Forum: Manjaro on PinePhone - Replies (3)

I first booted up my new pinephone only to be greeted by a lock screen I plan to swap to mobian but I wanted to muck about be manjaro first.

I've tried pins like 0000 1234 12345 but they didn't work


  Double your Manjaro eMMC speed
Posted by: xyzzy - 11-23-2020, 08:52 PM - Forum: Linux on Pinebook Pro - Replies (1)

It appears the default partitions Manjaro creates on the eMMC are not aligned.  This is really bad for performance!  Here's how to check this and fix it without re-installing or erasing eMMC.  You do need a boot from a bootable sdcard to do the final step.

First, check the alignment:

Quote:$ sudo sfdisk -l /dev/mmcblk2

Disk /dev/mmcblk2: 58.24 GiB, 62537072640 bytes, 122142720 sectors

Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x87129214

Device         Boot  Start       End   Sectors   Size Id Type
/dev/mmcblk2p1       62500    500000    437501 213.6M  c W95 FAT32 (LBA) 
/dev/mmcblk2p2      500001 122142719 121642719    58G 83 Linux

The start of the root partition should be aligned to a multiple of 4kB, if not more.  That means the start sector (500001) should be a multiple of 8 (8 sectors of 512 bytes is 4 kB).  It's not even a multiple of two!

The process to fix this will be shrink the boot partition, p1, to be a bit smaller and then move the root partition down so it's aligned.

Here's the process for shrinking the boot partition.  It can be done when booted from eMMC since the boot partition isn't actively used and can be unmounted.

There's a tool called fatresize that should be able to shrink it in place, but it doesn't work.  Since it's small, I just make a copy and reflash it.

As we can see in post #1, the current size of the boot partition is 437501 sectors.  I want to shrink that by 289 sectors, which will then align the root partition to 4MB.  The mkfs.vfat command wants the size in kilobytes, which are two sectors.

Quote:$ mkfs.vfat -v -n BOOT_MNJRO -C new-root.img $(( (437501 - 289) / 2 ))

mkfs.fat 4.1 (2017-01-24)
new-root.img has 64 heads and 32 sectors per track,
hidden sectors 0x0000;
logical sector size is 512,
using 0xf8 media descriptor, with 437212 sectors;
drive number 0x80;
filesystem has 2 16-bit FATs and 8 sectors per cluster.
FAT size is 216 sectors, and provides 54592 clusters.
There are 8 reserved sectors.
Root directory contains 512 slots and uses 32 sectors.
Volume ID is 7d933d98, volume label BOOT_MNJRO .

Now we want to loopback mount this filesystem and copy the contents of /boot into it.
Quote:$ sudo mount -o loop new-root.img /mnt

# Check that the filesystems are mounted as expected and the new one is empty.
$ df /boot /mnt
Filesystem     1K-blocks  Used Available Use% Mounted on
/dev/mmcblk2p1    218512 40296    178216  19% /boot
/dev/loop0        218368     0    218368   0% /mnt

# Copy all the files
$ sudo cp -a /boot/. /mnt

# Check fs is filled as expected
# It wouldn't hurt to ls -l /mnt too

$ df /boot /mnt
Filesystem     1K-blocks  Used Available Use% Mounted on
/dev/mmcblk2p1    218512 40296    178216  19% /boot
/dev/loop0        218368 40296    178072  19% /mnt

Ok, now we'll umount both filesystems and copy the new image over the existing fs.  If anything goes wrong while copying then you're in trouble but should still be able to recover from SD since this doesn't wipe out the eMMC u-boot.  But it only takes a couple second to copy the data.
Quote:$ sudo umount /dev/mmcblk2p1

$ sudo umount /mnt


# This is the command that writes the partition.  Be sure you have mmcblk2p1 here!
$ sudo dd if=new-root.img of=/dev/mmcblk2p1


And now for the final step, we'll shrink the size of the boot partition table entry to be 289 sectors smaller.

Quote:
$ echo ",-289" | sudo sfdisk --no-reread -N 1 /dev/mmcblk2

Disk /dev/mmcblk2: 58.24 GiB, 62537072640 bytes, 122142720 sectors

Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x87129214

Old situation:

Device         Boot  Start       End   Sectors   Size Id Type
/dev/mmcblk2p1       62500    500000    437501 213.6M  c W95 FAT32 (LBA)
/dev/mmcblk2p2      500001 122142719 121642719    58G 83 Linux

/dev/mmcblk2p1:
New situation:
Disklabel type: dos
Disk identifier: 0x87129214

Device         Boot  Start       End   Sectors   Size Id Type
/dev/mmcblk2p1       62500    499711    437212 213.5M  c W95 FAT32 (LBA)
/dev/mmcblk2p2      500001 122142719 121642719    58G 83 Linux

The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8).
Syncing disks.


And now reboot so the new table takes effect.  It can't be re-read because the root partition is still mounted from /dev/mmcblk2p2 and you can't unmount that.  If you were booted from SD then the table re-read will have worked.  You might want reboot from eMMC anyway just to be sure it all still works.


  Tiling Windows in Gnome
Posted by: clover - 11-23-2020, 08:39 PM - Forum: Pinebook Pro Tutorials - Replies (1)

As part of my quest for a Pop!_OS experience on a PBP, (see this tweet for a snapshot), I wanted to install Pop Shell tiling Gnome extension. I found there were a couple extra steps to get it working on PBP. Once it works, it's freaking awesome.

This should work with any Gnome image, especially Ubuntu based. 

Personally, I started with Armbian and then installed Gnome. if you want to know how to do that, see my answer to Best Gnome Distro for PBP? thread. 

Install dependencies:

Code:
sudo apt install node-typescript make xutils-dev git gnome-tweaks

I couldn't find the package myself so I build and installed xprop which is yet another dependency:

NOTE: if you are on wayland e.g., with my new groovy image: (see here: https://forum.pine64.org/showthread.php?...3#pid84503), you won't need the xprop dependency below!

Code:
git clone https://gitlab.freedesktop.org/xorg/app/xprop.git && cd xprop
./autogen.sh
sudo make install


Finally, build and install pop-shell from source:
Code:
git clone https://github.com/pop-os/shell && cd shell
make local-install

You may need to open gnome-tweaks -> Extensions -> Toggle Pop Shell

You may also need to reboot or restart gnome to see it show up in gnome-tweaks->Extensions

Enjoy your new awesome multi-tasking skills, there should now be a widget in the right side of the gnome bar where you can toggle window tiling on (off by default)


  Building Address Book
Posted by: alltrue - 11-23-2020, 06:11 PM - Forum: UBPorts on PinePhone - No Replies

Hello,

Recently got a pinephone and I am trying to play around and potentially contribute to ubuntu phone. I am attempting to build the address book from source based on the documentation here
https://docs.ubports.com/en/latest/syste...ice-itself . When I attempt to build the package

Code:
DEB_BUILD_OPTIONS="parallel=2 debug" dpkg-buildpackage -rfakeroot -b
it appears that it succeeds but then fails every unit test and dpkg exits without making the .deb package:
Code:
0% tests passed, 9 tests failed out of 9

Total Test time (real) =   1.70 sec

The following tests FAILED:
          1 - contact_list (Failed)
          2 - Contact_list_model (Failed)
          3 - Contact_list_view (Failed)
          4 - contact_editor (Failed)
          5 - contact_avatar (Failed)
          6 - list_with_actions (Failed)
          7 - contact_preview_page (Failed)
          8 - vcard_parser (Failed)
          9 - ubuntu_contact (Failed)
Errors while running CTest
Makefile:130: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory '/home/phablet/repos/address-book-app/obj-aarch64-linux-gnu'
dh_auto_test: make -j2 test ARGS+=-j2 returned exit code 2
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I kept the screen on the pinephone unlocked in case it tried to launch address book to run unit tests on that display but that didn't work.

Any help would be appreciated!


  Pinebook Pro and usb bus-powered drives
Posted by: qchapter1 - 11-23-2020, 04:23 PM - Forum: General Discussion on Pinebook Pro - Replies (2)

One thing to keep in mind with the PBP and other SBC-based devices is that power for usb powered accessories is limited. This can become more of an issue if you have installed an nvme drive internally.  There is only so much power to go around.  I like to rip CD's to FLAC and have found there is not enough power on the usb bus to power my external optical drive.  I purchased a cheap externally powered optical drive off of Amazon, which should remedy the issue.  Will let y'all know how it goes.


  Buildroot Image
Posted by: k0m37 - 11-23-2020, 04:16 PM - Forum: Development Discussion on PineCube - Replies (3)

Hi all,

I managed to create a buildroot image with kernel 5.10rc4 for the pinecube. The actually usb-patch from daniel fullmer is not yet included.

ffmpeg and v4l2 are preinstalled in the image. I add the link to download the image here (google drive). Simply burn to sdcard.

The image boots on the console UART2. An ethernet connection is done via dhcp and sshd starts automatically.

Login is root & Password pinecube.

Unfortunately Wifi is not working yet. Also media-ctl brings an error "no /dev/media0".

I am grateful for tips on further configuration of the kernel and necessary packages.

Regards

Link Update:

New image with wifi now working & ov5640 driver & ffmpeg preinstalled