I am outside of the "Glorious EU Data Roaming Area" for the first time since getting my PinePhone

On arriving at my destination I turned off Aeroplane Mode on my PinePhone and connected to the local Wifi network. I did not turn off the cellular connection.

This morning after watching a few videos last night I discovered that my PinePhone appears to have chomped its way through 400 MB of cellular data that is not included in my monthly subscription instead of using data via the Wifi connection.


Has anyone experienced anything similar?

I have installed "Debian GNU/Linux trixie/sid". I chose the weekly builds (sid) due to some features working already.
My sources.list looks like this:

As far as I know the shared folder option is only integrated in the later versions of Ubuntu to share one folder from one Ubuntu PC to another:

https://youtu.be/X-PSSd-U610

Or from a Ubuntu PC to a Windows 11 PC:

https://youtu.be/KV5fhoawNIo

But there is also the solution to share files with Samba.

I found hree a Guide - «Setting up a SMB(Windows) file server» on Rock 64 in the Pine64 forum:

https://forum.pine64.org/showthread.php?tid=4983

Does this work also on the Pinephone?

- This is the second part of my attempt to solve a probem from which i suffer since a long time that I was not able to solve it to this date

- Here is the first part:

https://forum.pine64.org/showthread.php?tid=18788

- I am a Linux beginner but this problem makes me really suffer.

- This was one of the reasons to buy a Pinephone

- and that is create files on the external SD card of my Pinephone

- and process it further on my Ubuntu PC.

- I created with Abiword a file on the external SD card of my Pinephone

- Then I sticked the SD card with a card reader into my Ubuntu PC

- There I was able to open and modify the Abiword file.

- But when I wanted to save the file under the same name it was created on the Pinephone, I had no permission to do this.

- I suppose to solve this problem I have to create on my Pinephone a file everybody has the permission to modify

- How can I do this?

Hi everyone,

I am trying to run meshtasticd on my Pinephone.
Suddenly tough, the received bytes of the SX1262 are all zero, and I never managed to get the standard 0xA2 answer back.
I2C communication works still, which is why I am suspecting that the radio chip is at fault.
Does anybody know what I was doing wrong or how to debug this?

Onto the details, I simply implemented an SPI device driver which translates to I2C such that mestasticd can communicate with it as if the ATTiny bridge isn't there.
The code for the kernel driver and a dmesg trace with debug output can be found here: https://gist.github.com/pectec/ffddf32ae...041bc92bbe

Any help on this is appreciated

Thank you,
Nick

Edit: I managed to damage it, Pine64 says that there isn't going to be a production batch anytime soon.
My only option is DIY at this point (using a [url=https://www.amazon.de/dp/B0CSFG65MS?psc=1&ref=ppx_yo2ov_dt_b_product_details][/url]Waveshare RP2040), which I'll do when I come around to it, so I'll mark this issue as solved.

Hi All,

Any ideas to run https://gitee.com/openeuler/rockchip openEuler 22.03 LTS SP3 Firefly-RK3399 on RockPro64.

It seams to be easy, but actually not know how. The boards FireFly and RockPro64 are 99% similar hardware.

https://hackerboards.com/compare/t-chip-...rockpro64/

Br,
Yuriy Gavrilov

I followed the command provided by the website[https://wiki.pine64.org/wiki/PinePhone_P..._Debugging] and ran.

Quote:Opening media device /dev/media0
Enumerating entities
looking up device: 81:8
looking up device: 81:9
looking up device: 81:10
looking up device: 81:2
looking up device: 81:3
looking up device: 81:6
looking up device: 81:7
looking up device: 81:11
looking up device: 81:12
Found 9 entities
Enumerating pads and links
no such entity "imx258 1-001a"
media_parse_setup_link: Unable to parse link

'imx258 1-001a':0 -> 'rkisp1_isp':0 [1]
  ^
Unable to parse link: Invalid argument (22)

Quote:VIDIOC_QUERYCAP: ok

VIDIOC_REQBUFS returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_QUERYBUF returned 0 (Success)

VIDIOC_G_FMT returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)

VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned -1 (Broken pipe)

Will Rust Apps run on a 64-bit RISC-V SBC? Like Ox64 BL808 SBC? Let’s find out!

(1) We take a Barebones Rust App (“Hello World!”)

(2) Compile it for QEMU RISC-V Emulator (64-bit)

(3) Run it on QEMU Emulator with Apache NuttX RTOS

(4) Do the same on Ox64 BL808 SBC (via MicroSD)

(5) We’ll discuss the Quirky Workarounds (because NuttX Apps work differently in Kernel Mode vs Flat Mode)

Here's how: Rust Apps on Ox64 BL808 RISC-V SBC and Apache NuttX RTOS

Lup

   

Hello

This time I have basic question:

I use Spacebar program to send and receive messages on my pinephone

but where are these messages stored ?? every single message to separate file
or all messages into one file and can I read it in text editor ??

This presentation explains how we created the Software Emulator for Ox64 BL808 RISC-V SBC, by customising the TinyEMU RISC-V Emulator. Today we run it for Daily Automated Testing of Apache NuttX RTOS for Ox64.

Presentation Slides