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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,447
» Latest member: Anonymous1989
» Forum threads: 16,185
» Forum posts: 116,832

Full Statistics

Latest Threads
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
5 hours ago
» Replies: 0
» Views: 16
does the Joplin note taki...
Forum: PineNote Software
Last Post: Francus
11 hours ago
» Replies: 4
» Views: 1,333
PulseAudio dropouts after...
Forum: Linux on Pinebook Pro
Last Post: Dendrocalamus64
Yesterday, 06:40 PM
» Replies: 1
» Views: 63
Any updates on Bluetooth ...
Forum: General Discussion on PineTab
Last Post: biketool
Yesterday, 06:38 AM
» Replies: 1
» Views: 59
Keyboard availability?
Forum: PinePhone Pro Accessories
Last Post: Peter Gamma
08-04-2025, 08:37 PM
» Replies: 9
» Views: 1,120
PINETAB-V doesn't boot.
Forum: Getting Started
Last Post: FEC
08-04-2025, 03:38 AM
» Replies: 0
» Views: 41
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
08-03-2025, 01:51 PM
» Replies: 4
» Views: 254
Trying to attach a serial...
Forum: RockPro64 Hardware and Accessories
Last Post: marietto
08-03-2025, 08:50 AM
» Replies: 0
» Views: 57
Full desktop Surfing and ...
Forum: General Discussion on Pinebook Pro
Last Post: KC9UDX
08-02-2025, 08:55 PM
» Replies: 1
» Views: 266
* /lib64 is a symbolic li...
Forum: PineNote Software
Last Post: Francus
08-02-2025, 08:16 AM
» Replies: 3
» Views: 203

 
  Selling original PinePhone postmarkedOS edition, 3GB RAM, keyboard cover + more
Posted by: ajtakrajta - 02-22-2022, 01:28 PM - Forum: General Discussion on PinePhone - Replies (4)

Hi,
I never managed to use Pinephone as a daily driver. I hoped to use it as a PDA, but I do not like the keyboard after all. I'm a bit spoiled by mechanical keyboards. So I'm selling the Pinephone postmarkedOS edition with 3GB RAM and larger storage, keyboard cover, hard protective case, one screen protector applied and one additional unused. There's also extra battery charger, pins break-out board and USB-C dock. I always used it with the screen protector - no scratches.

I'm located in the EU, Czechia, so I paid the VAT for some stuff.

Photo: https://i.imgur.com/WH0zhzR.jpg

Price: A reasonable discount from the official store. I can demonstrate it's all working fine during a video call.


  PCIe not working on custom board (soquartz)
Posted by: dferrg - 02-22-2022, 12:40 PM - Forum: Linux on Quartz64 - Replies (1)

I designed a custom board for the soquartz and I'm currently testing it.
HDMI, ethernet and SD work correctly, but the PCIe card (ASM1064) is not being detected.
Tried booting manjaro and debian (from this repo), both using rk3566-soquartz-cm4.dtb, and the logs look like this in both cases:

Code:
# lspci
00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01)
# dmesg | grep pci
[    0.201109] vcc3v3_pcie: will resolve supply early: vin
[    0.201629] reg-fixed-voltage 3v3_pcie: Looking up vin-supply from device tree
[    0.202348] vcc3v3_pcie: supplied by vcc12v_dcin
[    0.203523] vcc3v3_pcie: 3300 mV, enabled
[    0.204115] reg-fixed-voltage 3v3_pcie: vcc3v3_pcie supplying 3300000uV
[    0.458682] rockchip-dw-pcie 3c0000000.pcie: Looking up vpcie3v3-supply from device tree
[    0.460417] rockchip-dw-pcie 3c0000000.pcie: host bridge /pcie@fe260000 ranges:
[    0.461198] rockchip-dw-pcie 3c0000000.pcie: Parsing ranges property...
[    0.461876] rockchip-dw-pcie 3c0000000.pcie:       IO 0x0301000000..0x03010fffff -> 0x0001000000
[    0.462799] rockchip-dw-pcie 3c0000000.pcie:      MEM 0x0302000000..0x033fffffff -> 0x0002000000
[    0.464088] rockchip-dw-pcie 3c0000000.pcie: iATU unroll: enabled
[    0.464717] rockchip-dw-pcie 3c0000000.pcie: Detected iATU regions: 8 outbound, 8 inbound
[    1.572091] rockchip-dw-pcie 3c0000000.pcie: Phy link never came up
[    1.573002] rockchip-dw-pcie 3c0000000.pcie: PCI host bridge to bus 0000:00
[    1.573708] pci_bus 0000:00: root bus resource [bus 00-0f]
[    1.574260] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0x1000000-0x10fffff])
[    1.575189] pci_bus 0000:00: root bus resource [mem 0x302000000-0x33fffffff] (bus address [0x02000000-0x3fffffff])
[    1.576283] pci_bus 0000:00: scanning bus
[    1.576765] pci 0000:00:00.0: [1d87:3566] type 01 class 0x060400
[    1.577403] pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]
[    1.578201] pci 0000:00:00.0: supports D1 D2
[    1.578631] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    1.579206] pci 0000:00:00.0: PME# disabled
[    1.584472] pci_bus 0000:00: fixups for bus
[    1.584924] pci 0000:00:00.0: scanning [bus 01-ff] behind bridge, pass 0
[    1.585807] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-0f] (conflicts with (null) [bus 00-0f])
[    1.586886] pci_bus 0000:01: scanning bus
[    1.591578] pci_bus 0000:01: fixups for bus
[    1.592037] pci_bus 0000:01: bus scan returning with max=01
[    1.592609] pci 0000:00:00.0: scanning [bus 01-ff] behind bridge, pass 1
[    1.593288] pci_bus 0000:00: bus scan returning with max=ff
[    1.593875] pci 0000:00:00.0: BAR 6: assigned [mem 0x302000000-0x30200ffff pref]
[    1.594626] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    1.595500] pcieport 0000:00:00.0: assign IRQ: got 46
[    1.601107] pcieport 0000:00:00.0: PME: Signaling with IRQ 47
[    1.601864] pcieport 0000:00:00.0: saving config space at offset 0x0 (reading 0x35661d87)
[    1.602684] pcieport 0000:00:00.0: saving config space at offset 0x4 (reading 0x100507)
[    1.603475] pcieport 0000:00:00.0: saving config space at offset 0x8 (reading 0x6040001)
[    1.604319] pcieport 0000:00:00.0: saving config space at offset 0xc (reading 0x10000)
[    1.605107] pcieport 0000:00:00.0: saving config space at offset 0x10 (reading 0x0)
[    1.605863] pcieport 0000:00:00.0: saving config space at offset 0x14 (reading 0x0)
[    1.606618] pcieport 0000:00:00.0: saving config space at offset 0x18 (reading 0xff0100)
[    1.607416] pcieport 0000:00:00.0: saving config space at offset 0x1c (reading 0xf0)
[    1.608209] pcieport 0000:00:00.0: saving config space at offset 0x20 (reading 0xfff0)
[    1.609000] pcieport 0000:00:00.0: saving config space at offset 0x24 (reading 0x1fff1)
[    1.609789] pcieport 0000:00:00.0: saving config space at offset 0x28 (reading 0x0)
[    1.610544] pcieport 0000:00:00.0: saving config space at offset 0x2c (reading 0x0)
[    1.611298] pcieport 0000:00:00.0: saving config space at offset 0x30 (reading 0x0)
[    1.612079] pcieport 0000:00:00.0: saving config space at offset 0x34 (reading 0x40)
[    1.612853] pcieport 0000:00:00.0: saving config space at offset 0x38 (reading 0x0)
[    1.613611] pcieport 0000:00:00.0: saving config space at offset 0x3c (reading 0x2012e)
[    1.727024] ehci-pci: EHCI PCI platform driver
[    1.729180] ohci-pci: OHCI PCI platform driver
# uname -a
Linux buildroot 5.17.0-rc3 #1 SMP PREEMPT Wed Feb 16 00:41:25 UTC 2022 aarch64 GNU/Linux


I connected RX, TX and REFCLK differential pairs, and checked length matching for every pair (although not between pairs). Also connected nRST net. Traces are about 2-3 inches long. 

Am I missing something with my board design? Is PCIe supposed to currently work on soquartz?
Any help would be appreciated.


  Glacially slow system updates on Mobian - waiting on boot 20m - 1h
Posted by: bujiraso - 02-22-2022, 10:34 AM - Forum: Mobian on PinePhone - Replies (5)

Hello!

I have Mobian installed to the embedded SD in my PinePhone PmOS edition.

Any time I do a System Update with a reboot, it takes very long. I haven't timed it, but I wager the better part of an hour was spent updating once, then when I loaded in it asked for another (it's been a while, so that's fine), but then that took ~20m.

What are the average system update times for anyone else here?
Is there a way to speed this up? Is it affected by system encryption?


Question calls and voice mail blocked
Posted by: optimus - 02-22-2022, 07:58 AM - Forum: PinePhone Hardware - Replies (6)

Hello pinephone thread,
I'll probably be searching on that problem for a while, but I case someone can help, I'll post here first.

After having using a mmcli command that was meant to reboot the modem manually, I lost the ability to make or receive call. This is, what I suspect to be the cause, but it can be due to other factors, like hardware failure or carrier blacklisting me.

Among important symptoms that I can mentions are:
- I do can send/receive sms
- But I can't call/receive calls.
- Cell tower is fully detected.
- When my sim card is inserted in pinephone, people who try to call me, are unable to leave a message on my voice mail box, as if my carrier was thinking that my pinephone was answering, thus not activating the voice mail.
- On the other hand, when sim card is inserted in android, I can call/receive call, and people can leave messages on voice mail box.
- The problem persist after installing a fresh distro, as well as an upgraded one.


  Home Assistant Supervisor for rock64
Posted by: karbon17 - 02-22-2022, 07:10 AM - Forum: Linux on Rock64 - Replies (4)

Hi everyone, I'm Paolo and I'm Italian and sorry for my English, I wanted to install Home Assistant Supervisor on the rock64 with 4gb of ram but all my attempts failed; could someone kindly help me figure out which version of linux to install and what other steps I need to take to install it? i tried to use Armbian_21.05.1_Rock64_buster_current_5.10.35.img but then when i proceed with this:
1) sudo apt-get update && sudo apt-get upgrade -y
2) sudo apt-get install jq wget curl avahi-daemon udisks2 libglib2.0-bin network-manager dbus apparmor -y
3) sudo apt --fix-broken install
4) sudo reboot
5) curl -fsSL get.docker.com | sh
6) wget https://github.com/home-assistant/os-age..._armv7.deb
here is the error ....
7) sudo dpkg -i os-agent_1.2.2_linux_armv7.deb

thanks to those who can help me  Smile


  Pinecil 24V mod
Posted by: alex_grach - 02-22-2022, 05:10 AM - Forum: Pinecil Hardware and Accessories - Replies (1)

Hello.

Here is my solution to make Pinecil work with 24V power supply. Simple over voltage protection with 1k resistor and 20v zener diode.

       


  Problem updating
Posted by: gilwood - 02-21-2022, 06:40 PM - Forum: Mobian on PinePhone - Replies (5)

I have been running Mobian bookworm Phosh on my pinephone. Lately, when updating by using the software update under settings I have been receiving the message "unable to install updates. Prepared update not found: /var/lib/PackageKit/prepared-update". I also tried to update using the terminal and sudo apt update followed by sudo apt install. No luck. Am I missing something? In the past Mobian would post updates every week and the updater under settings worked great. Any help or ideas would be appreciated. Thanks


Big Grin Android 12 Tablet , Box/Atv
Posted by: shaggy013 - 02-21-2022, 10:08 AM - Forum: Android on Quartz64 - Replies (3)

While i was searching for the linux bsp/sdk i saw a sdk for android 12 , so after downloading the 80G of the rk android 11 sdk and comparing
i saw that i got the android 12 rk sdk Smile , so after removing the vendor and adding a quartz64 dts to the rk3566_s , got it compiling and to my surprise it is booting.

# SDK Version
PRODUCT_PROPERTY_OVERRIDES += \
    ro.rksdk.version=ANDROID$(PLATFORM_VERSION)_RKR1


the test in the calculator works (same codes as in android 11 000.= and the 839...) , the videoplayer (not the mediaplayer) plays video , sound i dont know (no speakers Smile ) ,wifi works , bluetooth ?
and not much more it , i have no experience with building android , limo was the last time .


i only post a image wich you can flash with rkdevtool on a emmc !!!

NO POST OF SOURCES ( i dont know how public the source is ,proberly not (think a dev didn't got his setting in git right) compared to the custom linux sdk wich you can find public). and dont see a vendor with android 12 on their devices while there is a sdk for android12 since november last year .

i noticed the codecs are diffrent comapred to android 11 codecs .

so have fun whith the little custom preview Smile

 
https://drive.google.com/file/d/1uPbpYv4...sp=sharing


  Would be possible to use a Good diplay DES 10.1" Eink
Posted by: fasani - 02-21-2022, 08:03 AM - Forum: Quartz64 Hardware and Accessories - Replies (2)

If I understand correctly there is already an Android 11 eink SDK for Quartz64 model A that is compatible with the eink.com 10.3" eink panel.
So I will first go for that. But I was wondering if it would be possible to connect one of this eink displays:

https://www.good-display.com/product/385.html

Actually has the same pin up 40 pins FPC connector. But another Waveform and it has a color filter always on so I guess the resolution is downgraded 3x using color.
I've one of this lying in my studio since months and I could never control it yet since there is no controller yet from Good display. There is only a tablet being sold commercially that is called Reinkstone with the display.

On another topic, I would like to ask if there are any other pointers on how the Eink interface works?
I would love to read about people doing stuff with this, on how the Android version works, refresh rate etc. I've only tried a Hisense eink phone and I'm quite impressed with the refresh rate and usability on UX since I expected it to be much slower. At the same time I'm a bit dissapointed on how color works since it's always a bit pale and frontlight does not help much.

Looking forward buying my first Model A board in the following weeks and start exploring it's possibilities. I'm quite impressed with it so far and it's very cool to see people trying it and the video reviews about them (Some playing games at an impressive framerate)


  Keyboard Case Power Management Daemon
Posted by: estokes - 02-20-2022, 09:48 PM - Forum: PinePhone Software - Replies (2)

Hi, I've made an attempt at writing the daemon Megi described in his blog post about the keyboard case. It's gone well enough that I thought it was time to share. Initially it only worked on the Pinephone Pro, however I've just released a version (0.1.2) that works on both the PP and the PPP.

https://github.com/estokes/pinephone-kbpwrd

The focus is on maximizing efficiency by avoiding moving charge into the main battery where possible. I'm open to discussion, and especially feedback and data.