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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,714
» Latest member: listtodata
» Forum threads: 16,264
» Forum posts: 117,212

Full Statistics

Latest Threads
what is the point?
Forum: General Discussion on PinePhone
Last Post: biketool
Yesterday, 10:32 AM
» Replies: 6
» Views: 307
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
11-28-2025, 07:38 AM
» Replies: 3
» Views: 11,850
Danctnix USB GPS for Pine...
Forum: PineTab Software
Last Post: biketool
11-28-2025, 06:09 AM
» Replies: 0
» Views: 69
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: biketool
11-28-2025, 03:39 AM
» Replies: 10
» Views: 6,786
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: realchunkyflea
11-27-2025, 05:01 PM
» Replies: 3
» Views: 334
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-27-2025, 04:23 PM
» Replies: 2
» Views: 113
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
11-27-2025, 10:30 AM
» Replies: 10
» Views: 15,933
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
11-26-2025, 02:45 PM
» Replies: 10
» Views: 16,863
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: j_s
11-26-2025, 11:33 AM
» Replies: 4
» Views: 338
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
11-26-2025, 01:42 AM
» Replies: 1
» Views: 213

 
  Good glue for reattaching Pinebook Pro feet
Posted by: rigorist - 02-04-2021, 11:10 AM - Forum: General Discussion on Pinebook Pro - Replies (4)

The feet on my PBP are barely holding on. It looks like this is a common problem, so I'm asking for advice of others who are . . . footloose . Cool

What glue works well for reattaching loose feet?


  Bountysource for porting Anbox to Wayland
Posted by: paju1986 - 02-04-2021, 02:00 AM - Forum: PinePhone Software - No Replies

Hello
Anbox currently doesnt work with wayland backend right now due to a pbuffers issue: https://github.com/anbox/anbox/issues/1270
This is why it looks so fuzzy on pinephone, because its using xwayland witch its not ideal and makes it slower.

There is a bounty source for making Anbox work on Wayland. Currently its at 180$ if someone is interesting on contributing to the bounty or making the work and reclaiming the price its here:

[color=var(--tertiary)]https://www.bountysource.com/issues/95432153-implement-native-wayland-support-for-anbox[/color]


  Patch to add ability to discard calls...breaks calls
Posted by: MungFuSensei - 02-03-2021, 08:08 PM - Forum: Sxmo on PinePhone - Replies (3)

This one.

This was merged upstream I guess (not up on the terminology here, so bear with me). I decided to set up the sxmo build environment so I can tweak some things, so I ran the build script which installs all the latest versions of the little scripts and all that.

Today I get a call, and it starts executing my ring hook, except it's doing it over and over and over, overlapping. I go to pick up the call and it's still ringing (x100 overlapping) and also somehow hangs up when I pick it up, while still ringing. All hell is breaking loose.

So I'm testing out what broke tonight, and I disabled my ring and pickup hooks just to be sure. Sure enough, I get a call in, go to pick up, and it just hangs up immediately. There was no option to discard, so I'm guessing that the pickup and discard functions are happening simultaneously when selecting to pick up. 

For now I've commented out these lines in sxmo_modemmonitor.sh in the checkforincomingcalls section:

Code:
+    sxmo_notificationwrite.sh \
+        "$NOTIFDIR/incomingcall_${VOICECALLID}_notification_discard" \
+        "sxmo_modemcall.sh hangup $VOICECALLID" \
+        none \
+        "Discard - $CONTACTNAME" &

And now it's working. Probably not the cleanest solution, but at least it's some temporary sanity until someone finds a fix.

I know this should be on the sourcehut git thing, but I'm not up to speed with all that so I figured this is the next best place.


  Is Pinebook Pro Available or Is It Not?
Posted by: CDMacalister - 02-03-2021, 05:57 PM - Forum: General Discussion on Pinebook Pro - Replies (7)

The Pine64 website gives conflicting claims about the availability of its products.

On the home page, it gives the option to pre-order Pinebook Pro. But pressing this leads to a product page which gives no option to preorder, which says that the product is out of stock, and gives no indication of when or if it will be back in stock.

So I guess, shortly phrased, my question is "When will Pinebook Pro be available to purchase?"


Wink Extremely fast pmOS build for the pinephone
Posted by: lucasanss - 02-03-2021, 04:05 PM - Forum: PostmarketOS on PinePhone - No Replies

Hi folks!
You might think your pinephone is a slow POC device.
Welp! that's true BUT pmOS sxmo is an incredibly smooth OS!
You can check my review here: https://youtu.be/Q6L9K0EW3qg

*How to install?*

# 1. Easy way --

## 1.1 From the computer
Download https://lucasanss.xyz/pine64-pinephone.img
then burn the image to you sdcard*. 
On a linux desktop the fastest way to do so is to download
the image while uncompressing it while writting the decompressed
output on your device.
if your sdcard is `/dev/mmcblk0` run: 
`curl https://lucasanss.xyz/pine64-pinephone.img.zst | zstdcat > /dev/mmcblk0`
if you want to check the writting progress:
`curl https://lucasanss.xyz/pine64-pinephone.img.zst | zstdcat | dd of=/dev/mmcblk0 status=progress`
Then boot 

## 1.2 From your phone

- Boot from your internal storage, /!\ -- important!
- Open up a terminal, run**:
  `sudo su`
  `curl https://lucasanss.xyz/pine64-pinephone.img > /dev/mmcblk0`
  /dev/mmcblk0 is the default partition for your external sdcard.

## 1.1 credentials
Default login : pine
Default password: enip

# 2. The hard way
Read the wiki https://wiki.postmarketos.org/wiki/PINE6...pinephone)
Follow the `pmbootstrap` instructions.

# 3. Important notes
READ the user instructions: https://git.sr.ht/~mil/sxmo-docs/tree/ma...ERGUIDE.md
Sxmo is easy to use but there is a certain learning curve.
For example by default the modem is disabled. While you'll
be able to make phone calls and receive sms, you'll can't 
receive any. So you'll need to enable it via the menu.

---
* If you use windows, I'd suggest using `rufus` in dd mode, or etcher.
Nonetheless, I haven't tested burning the image on windows

** Make sure curl is installed and that you have a reliable internet.
If download fails restart. Otherwise download the image and flash it
with `wget` and `dd`:
`wget https://lucasanss.xyz/pine64-pinephone.img`
if download succedeed:
`sudo dd < pine64-pinephone.img > /dev/mmcblk0`
yes you can use “<” and “>” instead of “if=” and “of=”


  PCIe Armbian and Ayufan for nvme ssd
Posted by: LMM - 02-03-2021, 02:50 PM - Forum: General Discussion on ROCKPRO64 - Replies (1)

Hi all,

  I made a test on nvme ssd performance.
 
- 2 rockpro 64
    - one with Armbian (tried 5.9.14 and 5.10 rc7)
    - one with Ayufan’s kernel (5.9.)
- 2 pcie to nvme cards
    - a black one from Pine64 (gen2)
    - a red one  (perhaps gen3)
- 2 ssd samsung evo plus

The result :


Code:
+-------+-----------+---------+
|       |  Armbian  |  Ayufan |
+-------+-----------+---------+
| black |  OK       |  OK     |
| red   |  KO       |  OK     |
+-------+-----------+---------+


The only problem seems coming from the red card which does not work with Armbian )module failed). Moreover the performance seems degraded with Armbian.
If we look at the dmesg we notice that capacity are different :

Ayufan :

Code:
[    4.078013] pci 0000:01:00.0: 16.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x4

Armbian :

Code:
[    2.700909] pci 0000:01:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link

Note that
- for Armbian I activated the pcie-gen2 in the armbian-config tool.
- the result Ayufan + black is similar to the Ayufan + red

I just wonder what differs between the two kernels... Ayufan secret ingredient ? Or am I doing things wrong ?



log details



with Ayufan + red

dmesg :
Code:
rock64@chen:/mnt$ dmesg | grep -i pci
[    0.006736] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created
[    1.611973] vcc3v3_pcie: supplied by vcc12v_dcin
[    1.633826] PCI: CLS 0 bytes, default 64
[    2.919080] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[    2.919131] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[    2.919160] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[    2.919705] rockchip-pcie f8000000.pcie: bus-scan-delay-ms in device tree is 1000 ms
[    2.919883] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[    2.920029] rockchip-pcie f8000000.pcie: supply vpcie1v8 not found, using dummy regulator
[    2.920153] rockchip-pcie f8000000.pcie: supply vpcie0v9 not found, using dummy regulator
[    3.004174] rockchip-pcie f8000000.pcie: wait 1000 ms (from device tree) before bus scan
[    4.071716] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    4.071738] pci_bus 0000:00: root bus resource [bus 00-1f]
[    4.071755] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    4.071774] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    4.071834] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    4.071962] pci 0000:00:00.0: supports D1
[    4.071977] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    4.076939] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    4.077169] pci 0000:01:00.0: [144d:a808] type 00 class 0x010802
[    4.077262] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    4.077428] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 256)
[    4.078013] pci 0000:01:00.0: 16.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x4 link at 0000:00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[    4.106343] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
[    4.106380] pci 0000:00:00.0: BAR 14: assigned [mem 0xfa000000-0xfa0fffff]
[    4.106403] pci 0000:01:00.0: BAR 0: assigned [mem 0xfa000000-0xfa003fff 64bit]
[    4.106457] pci 0000:00:00.0: PCI bridge to [bus 01]
[    4.106475] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[    4.106672] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    4.106945] pcieport 0000:00:00.0: PME: Signaling with IRQ 231
[    4.298192] ehci-pci: EHCI PCI platform driver
[    4.377616] ohci-pci: OHCI PCI platform driver
[    5.163253] nvme nvme0: pci function 0000:01:00.0
and iozone :

Code:
rock64@chen:/mnt$ sudo iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2
    ...
                                                              random    random     bkwd    record    stride                                   
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
          102400       4    96710   151834   159335   160318    64290   114505                                                         
          102400      16   222798   330544   332777   336250   191985   326480                                                         
          102400     512  1060460  1144479  1045592  1077316  1015649  1138965                                                         
          102400    1024  1175145  1189215  1069909  1102438  1070189  1186475                                                         
          102400   16384  1434425  1443247  1304941  1359970  1357994  1433817                                                         

with Armbian + black

Code:
rock64@ondine:/mnt/tmp$ dmesg | grep -i pci
[    0.007076] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created
[    1.246712] vcc3v3_pcie: supplied by vcc12v_dcin
[    1.399192] PCI: CLS 0 bytes, default 64
[    2.627404] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[    2.627433] OF: /pcie@f8000000: Missing device_type
[    2.627466] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[    2.627488] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[    2.628625] rockchip-pcie f8000000.pcie: supply vpcie1v8 not found, using dummy regulator
[    2.628778] rockchip-pcie f8000000.pcie: supply vpcie0v9 not found, using dummy regulator
[    2.694122] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    2.694136] pci_bus 0000:00: root bus resource [bus 00-1f]
[    2.694147] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    2.694159] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    2.694216] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    2.694369] pci 0000:00:00.0: supports D1
[    2.694378] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    2.699724] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    2.699984] pci 0000:01:00.0: [144d:a808] type 00 class 0x010802
[    2.700080] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    2.700259] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 256)
[    2.700909] pci 0000:01:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at 0000:00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[    2.714404] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
[    2.714435] pci 0000:00:00.0: BAR 14: assigned [mem 0xfa000000-0xfa0fffff]
[    2.714453] pci 0000:01:00.0: BAR 0: assigned [mem 0xfa000000-0xfa003fff 64bit]
[    2.714502] pci 0000:00:00.0: PCI bridge to [bus 01]
[    2.714516] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[    2.714721] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    2.715032] pcieport 0000:00:00.0: PME: Signaling with IRQ 78
[    2.715414] pcieport 0000:00:00.0: AER: enabled with IRQ 78
[    2.754347] nvme nvme0: pci function 0000:01:00.0
[    2.809211] ehci-pci: EHCI PCI platform driver
[    2.843136] ohci-pci: OHCI PCI platform driver

rock64@ondine:/mnt/tmp$ sudo iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -
Code:
random    random    bkwd    record    stride                                   
              kB  reclen    write  rewrite    read    reread    read    write    read  rewrite      read  fwrite frewrite    fread  freread
          102400      4    90237  127839  138090  138675    63069  126696                                                               
          102400      16  259529  325606  332023  334611  194739  321260                                                               
          102400    512  502510  659573  596504  607196  589030  675306                                                               
          102400    1024  716099  715984  659933  672370  659097  727990                                                               
          102400  16384  814970  821047  774083  794068  791828  818859                                                               

iozone test complete.


  Didn't receive phone, no response from Pine64 at all
Posted by: rn43x - 02-03-2021, 07:08 AM - Forum: Shipment Related Discussion - Replies (8)

Hey guys,
this is a rather sad story:
I ordered a phone with convergence pack last year and was hoping to get it by christmas. But it never arrived.
Instead DHL (who shipped it) decided to return it. So it got back to Poland (Warehouse location for EU). According to DHL it arrived there on the 24. of December. DHL told me that I'm not their contractual partner and pine had to start an inquiry.
Since then I've ben writing emails asking for support but nobody is replying anymore. It seems they're just ignoring me.
The only option left is to claim at least my money back via paypal.

IMHO, if this is the common way to deal with such customer issues it's disappointing.
So this is yet another desperate approach to try to get any reaction.

As usual best regards from Germany

rn43x


  quick camera question
Posted by: 112113101098101077 - 02-03-2021, 06:59 AM - Forum: Arch Linux on PinePhone - Replies (3)

Thanks for reading my post

flashed the Arch image from 24.01.2021 - is the main camera supposed to work?
Images from the back camera produces a black image with two vertical stripes.

The same behaviour on Mobian (as of 15.12.2020)

Fingers crossed for a software problem.


  PineBookPro does not charging
Posted by: floppy_rofling - 02-03-2021, 05:29 AM - Forum: General Discussion on Pinebook Pro - No Replies

Hello , I met with problem my PineBookPro doesn't want to charge . 
The charging block kinda work but accumulator shows low power . 
I tried to charge him 24 hour but it still low power . 
The red lamp near to power input is blinking red (when it real charging lamp doesn't blinkin')
Hope for ure advise .


  VoLTE calls with o2 (Germany)
Posted by: arno_nuehm - 02-03-2021, 05:26 AM - Forum: General Discussion on PinePhone - Replies (6)

Hello there,

did anyone manage to set up VoLTE calls with o2 (Germany)?

In my case (Mobian), the modem was automatically set to Telefónica Germany but the phone always switches to 3G for calls.

I'm curious, if other distros can do VoLTE calls with o2 (Germany) and if anyone could provide some help.

Thanks in advance!