PINE64

Welcome, Guest

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

Search Forums

Forum Statistics

» Members: 30,118
» Latest member: Samiha
» Forum threads: 16,363
» Forum posts: 117,536

Full Statistics

Latest Threads

Weatherproof case build
Forum: Enclosures
Last Post: ltorsini
07-07-2026, 07:01 PM
» Replies: 12
» Views: 38,512

Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
07-07-2026, 04:47 PM
» Replies: 16
» Views: 11,056

pinecil v2 dosent negotia...
Forum: General Discussion on Pinecil
Last Post: moses
07-07-2026, 07:28 AM
» Replies: 0
» Views: 73

Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
07-06-2026, 05:22 PM
» Replies: 2
» Views: 225

Rock64 v2.0 u-boot SPI is...
Forum: General Discussion on ROCK64
Last Post: ju0n
07-05-2026, 11:02 AM
» Replies: 0
» Views: 118

Libby - ebook reader that...
Forum: PineNote Software
Last Post: kiwigoldfish
07-04-2026, 04:41 PM
» Replies: 6
» Views: 4,076

PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 306

How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 172

PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,628

Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,245

My Daily QA - 2020-09-02

Posted by: plainenough - 09-02-2020, 09:04 AM - Forum: UBPorts on PinePhone - Replies (8)

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating, SIM installation, Wifi Configuration, and Power Cycling the devices.

Results: ubports/2020-09-02-TMobile

Conclusion: This OS is not ready for the device to become a daily driver.

Notes: Had bamboozeled myself this morning, I thought that 4g outbound calls were finally fixed..... plot twist I left the phone in 3g mode from yesterdays testing...... Damn. Anyways, no real progress. Not much action on the issues tracker. (to be expected to be honest.) Overall the OS hasn't been laggy for some time. The new settings application updates are nice. Worked out a lot of bugs that caused the settings menu to hang when opening. All in all, this OS is making progress. Please feel free to hit up the ubports forum to apply a little 'pressure' to the OS development side. Also, please feel free to leave your feedback on this post. Let us know what your seeing and we will at least attempt to confirm the behavior to validate your experience.

Issues:
Failed outbound 4G calls kills call audio.
Unable to send 3G SMS Since Dev-158
4G outbound calls broken.
Phone gets stuck in a weird lock state when spamming power button.

Having trouble compiling Jumpdrive

Posted by: PineTrees - 09-02-2020, 06:50 AM - Forum: PinePhone Software - No Replies

I am having a great deal of trouble trying to compile Jumpdrive. Specifically, the busybox dependency, but there are other failures. I'm not sure if I need to compile a different version of libc to link to, or if I'm just missing some packages for some cross dependencies. I'll post my build log below, and will answer any further questions if requested. Thank you.

Code:
$ make -j$(nproc) pine64-pinephone.img

Code:
MAKE  initramfs/bin/busybox

Code:
GZ    splash/pine64-pinephone.ppm.gz

Code:
GZ    splash/pine64-pinephone-error.ppm.gz

Code:
MAKE  kernel-sunxi.gz

Code:
MAKE  kernel-sunxi.gz

Code:
MAKE  build/atf/sun50i_a64/bl31.bin

Code:
make[1]: Entering directory '/home/PineTrees/src/Jumpdrive/src/busybox'

Code:
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.

Code:
make[1]: Entering directory '/home/PineTrees/src/Jumpdrive/src/linux'

Code:
make[1]: Entering directory '/home/PineTrees/src/Jumpdrive/src/linux'

Code:
make[1]: Entering directory '/home/PineTrees/src/Jumpdrive/src/arm-trusted-firmware'

Code:
make[2]: Entering directory '/home/PineTrees/src/Jumpdrive/build/linux-sunxi'

Code:
make[2]: Entering directory '/home/PineTrees/src/Jumpdrive/build/linux-sunxi'

Code:
  GEN     Makefile

Code:
  GEN     Makefile

Code:
  HOSTCC  scripts/kconfig/conf.o

Code:
  HOSTCC  scripts/kconfig/conf.o

Code:
  HOSTLD  scripts/kconfig/conf

Code:
  HOSTLD  scripts/kconfig/conf

Code:
/usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/10/../../../../lib64/crt1.o: in function `_start':

Code:
(.text+0x24): undefined reference to `main'

Code:
collect2: error: ld returned 1 exit status

Code:
make[3]: *** [scripts/Makefile.host:116: scripts/kconfig/conf] Error 1

Code:
make[2]: *** [/home/PineTrees/src/Jumpdrive/src/linux/Makefile:568: olddefconfig] Error 2

Code:
make[2]: Leaving directory '/home/PineTrees/src/Jumpdrive/build/linux-sunxi'

Code:
make[1]: *** [Makefile:179: sub-make] Error 2

Code:
make[1]: Leaving directory '/home/PineTrees/src/Jumpdrive/src/linux'

Code:
make: *** [Makefile:102: kernel-sunxi.gz] Error 2

Code:
make: *** Waiting for unfinished jobs....

Code:
scripts/kconfig/conf  --olddefconfig Kconfig

Code:
make[3]: scripts/kconfig/conf: Command not found

Code:
make[3]: *** [/home/PineTrees/src/Jumpdrive/src/linux/scripts/kconfig/Makefile:75: olddefconfig] Error 127

Code:
make[2]: *** [/home/PineTrees/src/Jumpdrive/src/linux/Makefile:568: olddefconfig] Error 2

Code:
make[2]: Leaving directory '/home/PineTrees/src/Jumpdrive/build/linux-sunxi'

Code:
make[1]: *** [Makefile:179: sub-make] Error 2

Code:
make[1]: Leaving directory '/home/PineTrees/src/Jumpdrive/src/linux'

Code:
make: *** [Makefile:102: dtbs/sunxi/sun50i-a64-pinephone.dtb] Error 2

Code:
  GEN     /home/PineTrees/src/Jumpdrive/build/busybox/Makefile

Code:
  CC      bl31/bl31_context_mgmt.c

Code:
  CC      bl31/bl31_main.c

Code:
  CC      bl31/interrupt_mgmt.c

Code:
  Using /home/PineTrees/src/Jumpdrive/src/busybox as source for busybox

Code:
  CC      common/runtime_svc.c

Code:
  GEN     /home/PineTrees/src/Jumpdrive/build/busybox/Makefile

Code:
  CC      drivers/allwinner/axp/axp803.c

Code:
  CC      drivers/allwinner/axp/common.c

Code:
  CC      drivers/allwinner/sunxi_msgbox.c

Code:
  CC      drivers/allwinner/sunxi_rsb.c

Code:
  CC      drivers/arm/css/scpi/css_scpi.c

Code:
  CC      drivers/arm/gic/common/gic_common.c

Code:
  CC      drivers/arm/gic/v2/gicv2_helpers.c

Code:
  CC      drivers/arm/gic/v2/gicv2_main.c

Code:
  CC      drivers/delay_timer/delay_timer.c

Code:
  CC      drivers/delay_timer/generic_delay_timer.c

Code:
  CC      lib/cpus/errata_report.c

Code:
  CC      lib/el3_runtime/aarch64/context_mgmt.c

Code:
  CC      lib/el3_runtime/cpu_data_array.c

Code:
  CC      lib/locks/bakery/bakery_lock_coherent.c

Code:
  CC      lib/psci/psci_common.c

Code:
scripts/kconfig/conf -s Config.in

Code:
#

Code:
# using defaults found in .config

Code:
#

Code:
  CC      lib/psci/psci_main.c

Code:
  CC      lib/psci/psci_mem_protect.c

Code:
  CC      lib/psci/psci_off.c

Code:
  CC      lib/psci/psci_on.c

Code:
  CC      lib/psci/psci_setup.c

Code:
  CC      lib/psci/psci_suspend.c

Code:
  CC      lib/psci/psci_system_off.c

Code:
  CC      plat/allwinner/common/sunxi_bl31_setup.c

Code:
  CC      plat/allwinner/common/sunxi_cpu_ops.c

Code:
  CC      plat/allwinner/common/sunxi_pm.c

Code:
  CC      plat/allwinner/common/sunxi_security.c

Code:
  CC      plat/allwinner/common/sunxi_topology.c

Code:
  CC      plat/allwinner/sun50i_a64/sunxi_power.c

Code:
  CC      plat/common/plat_gicv2.c

Code:
  CC      plat/common/plat_psci_common.c

Code:
  CC      services/arm_arch_svc/arm_arch_svc_setup.c

Code:
  CC      services/std_svc/std_svc_setup.c

Code:
  CC      common/bl_common.c

Code:
  CC      common/tf_log.c

Code:
  CC      drivers/console/multi_console.c

Code:
  CC      plat/common/plat_bl_common.c

Code:
  CC      plat/common/plat_log_common.c

Code:
  CC      plat/common/aarch64/plat_common.c

Code:
  CC      lib/compiler-rt/builtins/popcountdi2.c

Code:
  CC      lib/compiler-rt/builtins/popcountsi2.c

Code:
  CC      lib/xlat_tables_v2/aarch64/xlat_tables_arch.c

Code:
  CC      lib/xlat_tables_v2/xlat_tables_context.c

Code:
  CC      lib/xlat_tables_v2/xlat_tables_core.c

Code:
  CC      lib/xlat_tables_v2/xlat_tables_utils.c

Code:
  SPLIT   include/autoconf.h -> include/config/*

Code:
  CC      plat/allwinner/common/sunxi_common.c

Code:
  GEN     include/bbconfigopts.h

Code:
  GEN     include/common_bufsiz.h

Code:
  AS      bl31/aarch64/bl31_entrypoint.S

Code:
  AS      bl31/aarch64/crash_reporting.S

Code:
  AS      bl31/aarch64/ea_delegate.S

Code:
  AS      bl31/aarch64/runtime_exceptions.S

Code:
  GEN     include/embedded_scripts.h

Code:
  AS      lib/cpus/aarch64/cortex_a53.S

Code:
  AS      lib/cpus/aarch64/cpu_helpers.S

Code:
  AS      lib/cpus/aarch64/dsu_helpers.S

Code:
  HOSTCC  applets/usage

Code:
  HOSTCC  applets/applet_tables

Code:
  AS      lib/cpus/aarch64/wa_cve_2017_5715_bpiall.S

Code:
  AS      lib/cpus/aarch64/wa_cve_2017_5715_mmu.S

Code:
  AS      lib/el3_runtime/aarch64/context.S

Code:
  AS      lib/el3_runtime/aarch64/cpu_data.S

Code:
  AS      lib/locks/exclusive/aarch64/spinlock.S

Code:
  GEN     include/usage_compressed.h

Code:
  AS      lib/psci/aarch64/psci_helpers.S

Code:
  AS      plat/common/aarch64/platform_mp_stack.S

Code:
  GEN     include/applet_tables.h include/NUM_APPLETS.h

Code:
  GEN     include/applet_tables.h include/NUM_APPLETS.h

Code:
  HOSTCC  applets/usage_pod

Code:
  AS      common/aarch64/debug.S

Code:
  AS      lib/aarch64/cache_helpers.S

Code:
  AS      lib/aarch64/misc_helpers.S

Code:
  AS      plat/common/aarch64/platform_helpers.S

Code:
  CC      applets/applets.o

Code:
In file included from /home/PineTrees/src/Jumpdrive/src/busybox/include/libbb.h:13,

Code:
                 from /home/PineTrees/src/Jumpdrive/src/busybox/include/busybox.h:8,

Code:
                 from /home/PineTrees/src/Jumpdrive/src/busybox/applets/applets.c:9:

Code:
/home/PineTrees/src/Jumpdrive/src/busybox/include/platform.h:164:11: fatal error: byteswap.h: No such file or directory

Code:
  164 | # include <byteswap.h>

Code:
      |           ^~~~~~~~~~~~

Code:
compilation terminated.

Code:
make[3]: *** [/home/PineTrees/src/Jumpdrive/src/busybox/scripts/Makefile.build:198: applets/applets.o] Error 1

Code:
make[3]: *** Waiting for unfinished jobs....

Code:
  AS      drivers/ti/uart/aarch64/16550_console.S

Code:
make[2]: *** [/home/PineTrees/src/Jumpdrive/src/busybox/Makefile:372: applets_dir] Error 2

Code:
make[1]: *** [Makefile:112: _all] Error 2

Code:
make[1]: Leaving directory '/home/PineTrees/src/Jumpdrive/src/busybox'

Code:
make: *** [Makefile:76: initramfs/bin/busybox] Error 2

Code:
  AS      lib/xlat_tables_v2/aarch64/enable_mmu.S

Code:
  AS      plat/allwinner/common/plat_helpers.S

Code:
  PP      bl31/bl31.ld.S

Code:
  CC      lib/libfdt/fdt.c

Code:
  CC      lib/libfdt/fdt_addresses.c

Code:
  CC      lib/libfdt/fdt_empty_tree.c

Code:
  CC      lib/libfdt/fdt_ro.c

Code:
  CC      lib/libfdt/fdt_rw.c

Code:
  CC      lib/libfdt/fdt_strerror.c

Code:
  CC      lib/libfdt/fdt_sw.c

Code:
  CC      lib/libfdt/fdt_wip.c

Code:
  AR      build/sun50i_a64/release/lib/libfdt.a

Code:
  CC      lib/libc/abort.c

Code:
  CC      lib/libc/assert.c

Code:
  CC      lib/libc/exit.c

Code:
  CC      lib/libc/memchr.c

Code:
  CC      lib/libc/memcmp.c

Code:
  CC      lib/libc/memcpy.c

Code:
  CC      lib/libc/memmove.c

Code:
  CC      lib/libc/memrchr.c

Code:
  CC      lib/libc/memset.c

Code:
  CC      lib/libc/printf.c

Code:
  CC      lib/libc/putchar.c

Code:
  CC      lib/libc/puts.c

Code:
  CC      lib/libc/snprintf.c

Code:
  CC      lib/libc/strchr.c

Code:
  CC      lib/libc/strcmp.c

Code:
  CC      lib/libc/strlcpy.c

Code:
  CC      lib/libc/strlen.c

Code:
  CC      lib/libc/strncmp.c

Code:
  CC      lib/libc/strnlen.c

Code:
  CC      lib/libc/strrchr.c

Code:
  AS      lib/libc/aarch64/setjmp.S

Code:
  AR      build/sun50i_a64/release/lib/libc.a

Code:
  LD      build/sun50i_a64/release/bl31/bl31.elf

Code:
  BIN     build/sun50i_a64/release/bl31.bin

Code:
Built build/sun50i_a64/release/bl31.bin successfully

Code:
  OD      build/sun50i_a64/release/bl31/bl31.dump

Code:
make[1]: Leaving directory '/home/PineTrees/src/Jumpdrive/src/arm-trusted-firmware'

Code:
rm splash/pine64-pinephone-error.ppm.gz splash/pine64-pinephone.ppm.gz

Manjaro XFCE vs. Manjaro KDE

Posted by: pawlinski - 09-02-2020, 06:49 AM - Forum: Linux on Pinebook Pro - No Replies

	I think Manjaro XFCE on Pinebook Pro is slower than Manjaro KDE. Can anyone confirm this?

Phone calls on New PMOS Community Edition phones

Posted by: bcnaz - 09-02-2020, 06:13 AM - Forum: General Discussion on PinePhone - Replies (3)

Has anyone succeeded in using the new PMOS Community Edition Pine phone to place or receive phone calls or to send & receive sms/text ?

Using the Factory installed operating system...?

Using an alternative operating system... ?

If so what carriers have been tested and working ?

Thanks for sharing

Update :

I received my new PMOS Convergence Pkg phone about 4:00 pm in the afternoon after the above post.

I just did some quick preliminarily tests using an AT&T prepaid sim card, (my sim card needs to be replaced as it does 'connect' to the internet, but will not allow me to 'use' the internet).

First I tried the Post Market that is factory installed, I did the updates, then everything I tried worked.
Both incoming & outgoing voice calls and sms/text works incoming and outgoing.
Using the wifi for web browsing Firefox appears to work slightly better than earlier releases.
The mobile data did 'connect' but I got the AT&T message "it looks like you are trying to connect to the internet, but your account does not have data..."

Then I tried the September 03 nightly release of Mobian, again everything that I tested was working for me, also, same as above for my attempt to connect to the internet.
Both Firefox and the Gnome browser were working fine from the wifi.
I only checked the speaker phone function on Mobian and it did not work.
This test was done with a sd card, but speed was ok, considering....

Both tests were done as a GUI user, just adjusted the usual settings and basic inputs.
So consider this as : "Out of the Box" tests.

NOTE : The first couple of calls on PMOS there was no handset ringtone heard, and no voice/audio ether direction.
But, after that it performed very well.

Dormant Projects and Hardware

Posted by: S265 - 09-02-2020, 04:35 AM - Forum: General - Replies (7)

It is a shame to see the Pine64, Rock64 and PinePro64 no longer being pursued by developers and enthusiasts. Posts to these lists are few and far between. But I understand that passion needs an object of desire and these no longer deliver. Other projects present an appealing challenge.
It would be nice to do more with these great tools. How to reach a wider audience with their potential? We need people who can think outside of the PC world with ideas from left of field, that have been ignored or abandoned by others. The Rasberry Pi has many of these fans. I wish some would come here and take the hardware to new places in science and engineering. My own bias is to see Fedora, and OpenSuse and other mainline distros available to try and reach the wider audience, perhaps with mainline kernel support. But this may not be necessary for some technical projects. What about a competition to find the best new projects for this under-used hardware?
My 2c.

Proud owner of Pine64, Rock64, Pinebook Pro.

Is the volume rocker supposed to work?

Posted by: Mark53 - 09-01-2020, 10:56 PM - Forum: PinePhone Hardware - Replies (3)

	I got my PostmarketOS edition phone today and the volume rocker seems to have no effect on the volume. Is this expected behavior?

Why is PHOSH so PHOSHY

Posted by: Cree - 09-01-2020, 10:17 PM - Forum: PinePhone Software - Replies (2)

I think lots of us agree phosh is a pretty undesireable UI, but im wondering, has there been an effort to improve it? Surely it could be made more efficient, faster, less clunky, less PHOSHY, right? A little housekeeping, some attention to detail. Some salt here and flair over there....

Anyway, if anyone does pick up this project, here beith thy list to launder:
1) smaller sharper icons
2) faster response from keyup (not 1 or 2 second lag)
3) full option menus (settings, camera, back, open bluetooth, wifi, data from top icons)
4) faster opening apps and rendering pages

Maybe some of this has to do with integration of the underlying distros, but i find all running phosh have the same phoshyness

PinePhone development questions (Or: U-Boot PinePhone 3GB support)

Posted by: jbit - 09-01-2020, 09:56 PM - Forum: General Discussion on PinePhone - Replies (1)

Hi,

I'm digging a bit into the nuts and bolts of the PinePhone, and would like to have a ground up OS built working for when my 3GB PMOS edition arrives. I noticed on IRC that there are known issues with OS support and the 3GB PinePhone, so I thought I'd dig into what's going on, here's what I've found so far, but please correct me if I'm wrong Big Grin

The root cause is that upstream u-boot doesn't support dual-rank dram on the R40/A64 SoCs, so it panics.
There was a patch submitted upstream to the u-boot project, but never got merged (because it's RFC, I imagine): https://lists.denx.de/pipermail/u-boot/2...16856.html
PMOS uses source from Pine64/u-boot, and then applies a local copy of the dualrank patch. (According to this APKBUILD)
JumpDrive uses source from upstream u-boot, and then applies a couple of local patches (including the dualrank patch). (According to this Makefile)
Crust uses source from Pine64/u-boot, and then applies a local copy of the dualrank patch. (According to the gitlab config)

It feels a bit chaotic.

So I have a few questions:

What's holding up the patch getting into u-boot upstream?
Is upstream patch progress tracked anywhere?
Is there anything stopping the patch being committed to the Pine64/u-boot repo? (Which would allow projects to simply point at that commit to get support)
Is there anywhere where cross-OS efforts like u-boot fixes/kernel fixes/etc are being tracked and coordinated?

Sorry if these are super noob questions

Cheers

jbit

Mouse unresponsive, keyboard issues...static noise after login

Posted by: mamboozo - 09-01-2020, 09:48 PM - Forum: Pinebook Pro Hardware and Accessories - No Replies

Hey,

I've had the Pinebook for three days. Today my mouse and keyboard are having issues. 3/4 of the time the mouse or keyboard will be unresponsive after KDE loads. Sometimes the keyboard will work. The mouse will work for a few seconds, then lock. Every time I do log in I get static sounds out of the speakers for a few seconds. Sounds like squawk from a ham radio. Disk issue?

Any advice on what to do? Only downloaded a mail client, so no new software or hardware other than that.

Thanks.

No input/output from postmarketOS Convergence dongle

Posted by: yellowtrireme - 09-01-2020, 08:42 PM - Forum: PinePhone Accessories - Replies (4)

Hello everyone. Just got my postmarketOS "Convergence" package in the mail. The phone itself works as expected. However, I'm unable to get any input/output (other than power) to work with the provided USB-C dongle. I've tried multiple mice, keyboards, screens, HDMI cables, etc. The keyboards and mice seem to receive power, but I get no indication that they're recognized by the phone. No HDMI output s detected by any screen I've plugged into it.

Any help would be appreciated.

Pages (1612): « Previous 1 … 753 754 755 756 757 … 1612 Next »

Login




Remember me Lost Password?

About Us