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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,577
» Latest member: Escape75
» Forum threads: 16,212
» Forum posts: 116,989

Full Statistics

Latest Threads
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
49 minutes ago
» Replies: 13
» Views: 5,826
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: anoduck
Yesterday, 03:14 PM
» Replies: 5
» Views: 8,825
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: biketool
09-21-2025, 02:03 PM
» Replies: 71
» Views: 32,887
Special keys stopped work...
Forum: General Discussion on PineNote
Last Post: j_s
09-19-2025, 04:04 PM
» Replies: 3
» Views: 10,442
Wifi 5Ghz Issue
Forum: PineNote Software
Last Post: nicolaos
09-17-2025, 06:36 PM
» Replies: 0
» Views: 3,940
the self built bl602_boot...
Forum: Getting Started
Last Post: pinecheng
09-16-2025, 02:15 PM
» Replies: 2
» Views: 5,014
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: Gary2003
09-16-2025, 01:13 PM
» Replies: 13
» Views: 14,162
Cannot flash the modem fi...
Forum: Mobian on PinePhone
Last Post: anonymous
09-16-2025, 12:18 PM
» Replies: 7
» Views: 6,295
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
09-16-2025, 11:18 AM
» Replies: 8
» Views: 9,048
Mobian MMS/SMS text probl...
Forum: Mobian on PinePhone
Last Post: georgegohl888
09-15-2025, 02:42 AM
» Replies: 16
» Views: 25,118

 
  HDMI troubles with Pinephone beta edition
Posted by: caveman250 - 04-23-2021, 08:38 PM - Forum: General Discussion on PinePhone - Replies (9)

HI all, i just recieved my beta edition of the pinephone, and was very excited to try out the HDMI docking features as i have previously been using a UB Ports edition which does not support the feature.

However i am unable to get the phone to recognize that a HDMI cable is connected, i have tried under factory Manjaro Plasma, Manajaro Phosh Beta 8 and Mobian nightly with no luck. I was under the impression that HDMI out was mostly supported as of now? is there some setup that I'm missing? does it only work on certain distros? is it just broken atm?

Any help is very appreciated, overall i am head over heels with this device, it's exactly what i've been missing form my life!


  GhostCloud workaround for PinePhone
Posted by: mark1250 - 04-23-2021, 03:14 PM - Forum: UBPorts on PinePhone - Replies (1)

So, due to some missing parts between UBports and Wayland you cannot setup online accounts on the PinePhone. Bug and Bug.

Here is a way to make it work until the bugs get addressed.

  • We need to build a click package of GhostCloud. I setup a minimal Ubuntu 20.04 virtual machine as I use openSUSE and didn't want to try installing the click build environment on it. Then I setup the click build environment as described here. - I used the PIP method.
  • Then following fredldotme's instructions, I built a click package of GhostCloud version 0.9.6 which does not use UBports online account mechanism.
  • I transferred the click package to my PinePhone, and then using the UT Tweak Tool available in the Open Store installed GhostCloud.
  • I was able to enter the URL, username, and password for my NextCloud instance. I now have access to files on my NextCloud server.
  • For Calendar and Contacts, I setup syncevolution following the instructions on this github page.
I hope this will help others.

Mark


  Pinephone Case Question (Canada)
Posted by: cptantiles - 04-23-2021, 02:49 PM - Forum: PinePhone Accessories - Replies (2)

Hello,

My pinephone just arrived today, but i hadn't realized the pinestore also sells cases for the Pinephone. My question is, If i decide to order a case, Am i going to have to pay import fees on it again? Obviously Shipping would be charged, but I'd  prefer not to have to drop another $25 on customs to get a case.

Thanks in advance for any answers.


Sad Dead in less than 10 minutes...
Posted by: misterdid - 04-23-2021, 01:39 PM - Forum: General Discussion on Pinecil - Replies (3)

Hi,

I received my Pinecil, purchased March 31st, yesterday.

I powered it with an old laptop power supply (21v - I checked it).

I played with the menu for 5 minutes or so, then I tried my first soldering...The temperature barely reached 314C (and oscillated from 310 to 314 during that time)...it lasted 10 seconds or so (just the time to tin the tip and try it on my solder wire...and it died.

Since, not powering up, no USB registration if I plug it into a computer....I think it is dead. 

Any similar experience? Any hint? I opened a ticket early this morning, but no answer so far...
It is really frustrating to wait for 3 weeks...for less than 10 minutes of lifetime...


Sad Webcam not working in pinebook pro with Manjaro
Posted by: jcarball - 04-23-2021, 11:39 AM - Forum: General Discussion on Pinebook Pro - Replies (2)

I need working with the webcamera!

Does anyone know how to enable it? 

Cheese> NO device found


  PineTab restock
Posted by: *PorcuPine* - 04-23-2021, 11:07 AM - Forum: General Discussion on PineTab - Replies (3)

Can anyone at Pine64 give an approximate date for when the PineTab will be back in stock again?
I wouldn't mind a pre-order with a long shipping delay either. Just want to get my hands on one asap :)
From where does Pine64 ship? I live in Germany, do they ship from within the EU or will I have to pay import duty?


  Setup My Pinebook 64 and Lost Password
Posted by: jersdayoff - 04-23-2021, 11:00 AM - Forum: Getting Started - Replies (5)

Hi everyone! I am new here. What is the easiest way to reset the OS, I have completely forgotten the password and am locked out. Thanks in advance for the help Smile


  UB Touch build with debos
Posted by: layton-dev - 04-23-2021, 08:12 AM - Forum: UBPorts on PinePhone - No Replies

Hi !

I'm currently trying to build from source a UBTouch image, for the Pinephone and I'm following these instructions :
https://gitlab.com/ubports/community-ports/pinephone

Apparently, the images are built using the tool "debos" : https://gitlab.com/ubports/core/rootfs-builder-debos
But after following the provided instructions (installing Docker, etc) and running the command :

./debos-docker -m 5G pinephone.yaml

I have the following error :
"Action `Pine64 common` failed at stage Run, error : stream error: stream ID 1; INTERNAL_ERROR"
... right after trying to download the UB Touch rootfs.

I'm wondering whether this is some kind of network or proxy problem (I can download the rootfs just fine with a web browser, though), or if anybody else has the same issue ?

Thanks !


  PinePhone Keyboard update [April 24/04]
Posted by: Luke - 04-23-2021, 06:56 AM - Forum: News - Replies (73)

A look at PinePhone keyboard prototype

In this month's community update I wrote that once the keyboard molding arrives from the factory I'll make a post about it. I know that many of you are eagerly awaiting news, so now that it is here (well sorta, I'll get to that) I'm happy to oblige with some show-and-tell.

I decided on posting a forum rather than a blog post simply because there isn't enough here for me to write about to warrant a blog entry. I currently don't have an ETA of final molding, store availability date, functionality status report, etc,. Also, if you just found out about the keyboard's existence, then I encourage you to first read this blog post, followed by the March community update.

Let me give you some context for the pictures and video. This pictured molding isn't actually final - there are still a handful of touchups needed. Most notably, the key caps need to be remolded because the tolerances are currently not quite right. This will take some 2 weeks or so I'm told. The final keyboard will also be all black (although I think it looks nice with the white bit), and of course the key caps will have latter and labeling we all decided on a while back.

Lastly, the video and pictures were shot at the factory, and are meant to show progress rather than being promo material. Also, that PinePhone has seen things Sad 

That's all I have for you today, but it is likely I'll have more details to share in the May community update.
Enjoy the pictures and video below.


[Image: vvqdJPv.jpg]

[Image: QEdy2VI.jpg]

[Image: jplrqr8.jpg]

[Image: 3uedtMo.jpg]

[Image: gyNFZJI.jpg]

Video showing the PinePhone + keyboard open, close, hinge position and stiffness


Information Pinedio Project: Notes Sharing/Log
Posted by: RTP - 04-22-2021, 03:15 PM - Forum: P64-LTS / SOPINE Projects, Ideas and Tutorials - Replies (45)

EDIT: installing https://github.com/righttoprivacy/rak_co...or_gateway sets the Pinedio gateway devices (concentrator/gps) listed below. (Leaving notes for context/reference).
See lower page for example image with fork installed.

Hello! Smile

Post to share things that are found helpful/work, progress/Notes along Pinedio Gateway/modules/Kit.

(Pinedio uses Rak Wireless "LoRa"/Mesh related/compatible hardware).

Pinedio's Wiki has been started and can be found here: https://wiki.pine64.org/wiki/Pinedio

Thread for sharing some found to be working notes that can be edited out/posted to WiKi as wanted.

The Pine64 Gateway's underlying hardware runs on the A64-LTS (this looked the best place to post this - feel free to move).

Working SOPINE/Patched Armbian image can be found at:

*** Removed one of the images as users reported ethernet was not working- my working image is below this:

https://mega.nz/file/Wd5CGRhB#spBqSQrhLm...HopFs4Ho9o (576MB) (Uploaded this copy after patching it)

sx1302_hal compiles/installs on Armbian without issue.

EXPERIMENT: SET UP RAK_COMMON_FOR_GATEWAY (ORIGINALLY FOR RPI: SOME MOD REQUIRED - NOT QUITE FINISHED):

Run sudo armbian-config. Enter System to enable SPI/UART for sx1302/rak/GPS.

Then Add The Following Line To /boot/armbianEnv.txt:

Code:
param_spidev_spi_bus=0

***After this reboot Gateway***

NEXT:

Code:
clone https://github.com/RAKWireless/rak_common_for_gateway.git

Then:

Code:
cd rak_common_for_gateway

In rak/install.sh comment out the line (add hash mark in front of)

Code:
# systemctl stop hciuart
(or you will receive errors aborting your install)

Run the install.sh script in the main directory.

Select: 7 : rak2287/GPS without LTE

We can use gateway-config command to make some device location changes (if needed).

Before entering gateway-config -> edit packet forwarder, we need to grab our mac address based Gateway ID for all LoRa networks. To grab this Gateway ID run:

Code:
gateway-version

It will print out your Gateway ID (based on your unique mac address).

Inside gateway-config make the following changes:

Code:
{
    "SX130x_conf": {
        "com_type": "SPI",
        "com_path": "/dev/spidev0.0",
        "lorawan_public": true,

Set GPS to /dev/ttyS2 and grep -i reset to find reset pin swapping 17 with 71.

GPS section of the packet forwarding should look as below

Code:
/* GPS configuration */
        "gps_tty_path": "/dev/ttyS2",
        /* GPS reference coordinates */

Above GPS, replace the default GatewayID with your gateway ID retrieved from gateway-version (from earlier). The line looks like:
Code:
"gateway_conf": {
        "gateway_ID": "03BD3EFFFF21D2F",

Restart packet forwarder. You may need a reboot.

GPS Related:

If experimenting with The Things Network I discovered Gateway does not appear on the map until the GPS signal is stable. I ran a line towards a window to give it a clear line of sight for GPS. Using a temporary antenna I was able to get a better GPS reception. Immediately after setting up this stable GPS link, the Gateway appears on the map and the PPS counter begins.

journalctl log example (still more to look at):

Code:
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: Opening SPI communication interface
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: Note: chip version is 0x10 (v1.0)
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: using legacy timestamp
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: LoRa Service modem: configuring preamble size to 8 symbols
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: ARB: dual demodulation disabled for all SF
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: found temperature sensor on port 0x39
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: [main] concentrator started, packet can now be received
Apr 24 23:45:14 rak-gateway ttn-gateway[10543]: INFO: concentrator EUI: 0x00xxxxxxxx (masked)
Apr 22 16:57:19 rak-gateway ttn-gateway[6400]: CoreCell reset through GPIO71...
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: *** Packet Forwarder ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: Version: 2.0.1
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: *** SX1302 HAL library version info ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: Version: 2.0.1;
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: ***
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Little endian host
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: found configuration file global_conf.json, parsing
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: global_conf.json does contain a JSON object named SX130x_conf, parsing SX1302 parameters
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: com_type SPI, com_path /dev/spidev0.0, lorawan_public 1, clksrc 0, full_duplex 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: antenna_gain 0 dBi
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Configuring legacy timestamp
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: no configuration for SX1261
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Configuring Tx Gain LUT for rf_chain 0 with 16 indexes for sx1250
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: radio 0 enabled (type SX1250), center frequency 904300000, RSSI offset -215.399994, tx enabled 1, single input mode 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: radio 1 enabled (type SX1250), center frequency 905000000, RSSI offset -215.399994, tx enabled 0, single input mode 0
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 5 to 12
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8, Explicit header
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: FSK channel 8 disabled
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: gateway MAC address is configured to AAxxxxxxxxxxxx (mac masked)
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: server hostname or IP address is configured to "router.us.thethings.network"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: upstream port is configured to "1700"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: downstream port is configured to "1700"
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: downstream keep-alive interval is configured to 10 seconds
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: statistics display interval is configured to 30 seconds
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: upstream PUSH_DATA time-out is configured to 100 ms
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with a valid CRC will be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with a CRC error will NOT be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: packets received with no CRC will NOT be forwarded
Apr 22 16:57:23 rak-gateway ttn-gateway[6400]: INFO: GPS serial port path is configured to "/dev/ttyS2"
....
Apr 23 03:17:37 rak-gateway ttn-gateway[17110]: # PUSH_DATA datagrams sent: 1 (124 bytes)
Apr 23 03:17:37 rak-gateway ttn-gateway[17110]: # PUSH_DATA acknowledged: 100.00%

[OP actively being edited and may change - will clean up as I go]

(Thanks JF for sharing some hardware/SPI related information especially on GPS as I have not worked with an LTS/A64 board until now)

My thought is to continue looking at what may not yet work, change things along the way until all is functional.

Having some odd things happen where I make a small edit to packet forwarder and it resets to original RPI, leading me to have to re-edit leading to starting of concentrator (as far as can see - will end up testing a node on it coming up and checking more details that might differ between RPI/Pine64- if you have anything helpful to share, thanks).

(For now mainly looking at Gateway and using rak_gateway as a starting point to test hardware and make changes).

If you have anything/thoughts/suggestions to add, related, or unrelated, please do! Smile