My PinePhone64 stopped connecting to my router wi-fi. After several tests I determined that the problem was the phone. I contacted customer service and they asked me to download and run a test program (app). Not easily done with no Internet connection. But I managed. It took several attempts but finally I got a test that reported RTL8723CS had failed. Nevertheless they asked me to repeat the test several times as I had not tested for all the devices. Not really a problem, but it took some extra time. Then they asked me to remove the motherboard and its many tiny screws to ship it to them for replacement. I was concerned I would damage the board. I objected, telling them that I had bought a complete phone not a motherboard and that I would ship them the whole phone (minus battery). They agreed. Shipping from Sweden to Slovakia was expensive. They received it on 27th. July.

It arrived today 15th. August and it works normally. I would call that good customer support. But downloading your test version from “Historic factory builds” on https://wiki.pine64.org/index.php?title=...Download_9 and running it will speed up the process.

Hello,

I've been testing Plasma Mobile a few times, and there are quite a few things I do like better than on Phosh, but I always end up considering it unsuitable for serious use as a phone because of one major issue: the screen doesn't turn off or even lock when putting the phone on the ear during a phone call! The screens stays on and your ear can randomly open menus and change settings by touching the screen. I'm really surprised that this still doesn't work, as it's a rather basic and vital feature of any phone UI.

On Phosh, the screen stays on but gets locked and blanked when the proximity sensor is covered. That's not ideal, but usable.

On sxmo and Gnome Mobile, it gets properly turned off.

Is there something I didn't figure out to enable the feature, or is the proximity sensor really not supported by Plasma Mobile?

Hello,

Currently giving sxmo a try, I'm annoyed by the SMS log breaking words in order to fit full lines.

Instead of randomly brok
en words I'd like to hav
e line breaks occuring b
efore or after entire wo
rds...

I redact my messages in the "micro" editor and there I can enable the options "softwrap" and "wordwrap" to get lines to break on spaces only, but I don't know how to configure a similar behaviour for the log. Any idea?

Hi everyone,
I am new in for this kit. I want to check maximum toggle speed in Rockpro64 board. I am getting 2.2Ghz using rpi 4 8GB board. But this speed is not enough for my project. So can you please suggest me how can i achieve atleast 2.5 Ghz using RockPro64 board.

but before starting i want a simple C++ or C code to test default gpio toggle speed. can ayone help me please.

As to make this tablet truly sustainable....

For quite awhile now I’ve been looking for a suitable battery to run this SBC. I’ve seen several posts which helped determine that it can’t be powered by usb-c, or the onboard lithium battery port. I don’t know much about electricity, but there has to be a solution to run the unit without plugging into the wall. My MacBook Air runs & charges off usb-c, and it seems it would need much more power than an SBC. It also seems very inefficient to run an expensive battery bank to go from DC - AC - DC. I’m also not going to carry a 12V car battery around in my backpack.

Has anyone found a solution to battery power the RP64? I will run headless, so no additional accessories are needed (except for onboard or usb Wi-Fi adapter).

Power Input: 12V 3A or 5A type M 5.5mm OD/2.1mm ID barrel type DC Jack Power Supply.

I really waaant a pine64 (flip) dumb phone with a very light OS like the one in the pinetime, perhaps with a bit of a better hardware to be able to listen to music but that's it !!
There was another discussion about this but it went full political about something else, so I opening this here

I don't know if you've already thought about it, kaios phones are really not satisfying enough from an open source point of view since most manufacturers don't release sources

dumbphone are really becoming a thing again, lots of us rely on bad dumbphone we can't really hack into

Hello,

I have archlinux running on pine64+, everything is fine except mic input. Output to 3.5mm jack works nice, but I can't get recording anything. Can you please share asound.state file with mic enabled.
So far I went through sound codec code and tried to enabled the path from Mic2 -> DAC Mixer -> AIF1 -> Capture, but only thing I'm having is white noise.

Here is some debug info from capture:

I installed a Lenovo tablet (an x86 model) with a vanilla Debian, and one of the problems is that at boot, when prompted for the password that decrypts the disk, there is no virtual keyboard that spawns, which means that the tablet is not usable if one hasn't a USB keyboard nearby during boot.

It's quite logical that the minimum software loaded to decrypt LUKS doesn't have a virtual keyboard in it, but that made me think : how does Pinephone manage it ? I have an encrypted Pinephone, and (luckily for me) the virtual keyboard spawns when I boot, so that I can decrypt the partition which has the OS.

Not that I'd be able to port this solution to a Debian tablet, but still it made me curious...

At the Apache Asia Conference "Community Over Code" (19 Aug 2023), I'll talk (remotely) about Apache NuttX Real-Time Operating System (RTOS) for PinePhone. Here are the pre-recorded video and presentation slides...

Video Presentation

PDF Slides with Transcript

Presentation Slides

What's inside a Smartphone? Exploring the internals with Apache NuttX Real-Time Operating System

Smartphones are incredibly complex gadgets. What if we could learn the internals of smartphones... By booting Apache NuttX RTOS (Real-Time Operating System) on our phone?

Over the past year, we have written a series of 24 articles explaining the inner workings of PINE64 PinePhone, and how we implemented the smartphone features with Apache NuttX RTOS.

The articles cover the essential (and esoteric) topics on smartphone technology: MIPI DSI LCD Display, I2C Touch Panel, USB Controller, LTE Modem, Accelerometer / Gyroscope, Arm64 Interrupts and many more.

We are also experimenting with newer, easier ways to create Smartphone Apps, with LVGL Graphics Library, Zig Programming Language, WebAssembly Simulation and Arm64 Emulation.

More about Apache NuttX RTOS for PinePhone

Articles on Apache NuttX RTOS for PinePhone

Apache NuttX RTOS for Star64 64-bit RISC-V SBC (StarFive JH7110)