Arch Linux ARM Danctnix + Phosh (GNOME/Purism Calls application).

I tried to change the volume the microphone has during calls as per two sources (1) (2):

/usr/share/alsa/ucm2/PinePhonePro/VoiceCall.conf

If I buy a phone in Ireland, will it work in the US?

Have there been any advances in using the Ox64 with common off-the-shelf stuff like XMODEM transfer or any documentation of the actual serial protocol used to communicate over the UART by default? I've had no success thus far getting anything from the Bouffalo folks to work, and even then I've had to do all that experimenting from an AMD64 Windows machine to use Dev Cube as my main computer is ARM64 running Linux.

Ideally what I'm looking for is a workflow that can be operated via GNU screen by hooking up a simple USB<->UART adapter and then using some tool like sx or kermit. Heck, if it's not one of these protocols I'm even willing to spin my own tool in C if the protocol is documented literally anywhere. I'm just at a loss as to where to start with this thing, I really want to get going with it because my other two RISC-V targets that I have had some moderate success with UART on are significantly more complicated and I feel working with the Ox64 will help keep my RISC-V experiments a bit more narrow and focused.

Thanks for any input!

So a good while back, I ordered a pinephone. Mostly to support the project but also because I wanted to use a Linux phone. Unfortunately, before I got to use it, AT&T did their whitelist thing then Verizon bought Tracfone et al which caused not a small amount of grief so the Pinephone sat in a drawer for a while.

Anyway, yesterday, I activated a t-mobile sim and put it in the (unupdated) pinephone. Things seemed to be going well. Sent some texts, did some test calls, things were good. So I left it charging. This morning, I came to use it and it appeared to be off. No biggie. Try to boot - red led, red&green led then just the backlight. Wonder if I didn't have things plugged in correctly so make sure charging is all good and leave it for 10 minutes. Same thing happens.

So now we're in troubleshooting mode. vol-up+power, same deal. vol-up+power, same deal. No apparent recovery mode. Time for research. Find the post at the top of this thread. Could be battery? Don't think so (see above) but pull battery and it's giving a good 4.13V so we appear to definitely be in good shape. Next to try jumpdrive. Download the image, flash to SD, insert and... LED is green (yay, something different) but then we're back to the backlight only. Nothing appeared on the screen at all. A couple of attempts to get to recovery mode again that lead to the same result and then a reboot and the phone's been sitting there for 10 minutes with the backlight on. The metal plate inside the phone is warm (but not hot).

So is there anywhere to go from here?

Hello again.

i have an LTS board and i am trying to find a way to install Armbian on it.
I was using this board since more than 5 years now without any issue or update, but now i need to use it on a different project and i need something more fresh than Bionic.

I was trying to install something newer but actually the only working version of Armbian i found is Armbian_21.02.1_Pine64so_bionic_current_5.10.12.
Is there any way to install something newer on this board or is time to became a paper holder?

I have tryed newer version but the board can't boot.

Thanks in advice for any help.

Hi,

I read the FAQ and know that Linux is off the chart because of the Cortex-M.

Now, Is there anyone who is not afraid of a more expensive DIY watch, that decided to go that route anyway?
I would like a sufficiently powerful starting point to create a nice watch, translating as much as I can my Linux knowledge and existing apps to the watch.

I will create the 3d Printed case and fit the straps.
But I need the electronics set properly, because I am not a "hardware" guy.

So, any existing project going that route ?

Cheers,

geometry dash meltdown
I've recently encountered an issue with my PinePower Desktop where it constantly power cycles if there isn't anything plugged into it. I understand from a previous thread that this might be a known issue. Has there been any firmware update released to address this problem? If so, could someone kindly direct me to the update process or provide any tips on how to apply it effectively?

New post today: https://fosstodon.org/@danctnix/112366650102862145

Quote:Greetings, @pine64 #PineTab2 users!

We have pushed a new kernel (v6.8.6-danctnix2) to the repository.

The new kernel introduces the new #BES2600 community driver which works with suspend.

Power consumption is not tested.

#DanctNIX #ArchLinuxARM

The competition does not sleep. There is a Risc-V laptop for $300 (which configuration?):

- full-sized cursor keys
- up to 16GB Ram
- 8 pin header (on a laptop!)

click on the link for all the details https://www.cnx-software.com/2024/04/30/...-16gb-ram/

My Pinebook Pro is still good enough, but damn ...

Hello! 
I am a new PinePhone user and I recently purchased a PinePhone pro explorer edition. After installing Tow Boot and trying several distributions, I was unable to get voice calling to work. As a result, I attempted to update the modem firmware, thinking that this may be the issue (after no issues with microphone or other audio systems were apparent anywhere). The modem appears to never have booted up properly again, and now the modem is not recognized by the operating system at all.

The reason for this post is because I cannot find the EDL boot test points on the motherboard that are mentioned in several different places (GitHub - Biktorgj/quectel_eg25_recovery: Stock firmware recovery packages for Quectel EG25-G, pinephone_modem_sdk/docs/RECOVERY.md at kirkstone · the-modem-distro/pinephone_modem_sdk · GitHub, https://forum.pine64.org/attachment.php?aid=2843, ...).  The motherboard in my phone does not have these contacts (text on board: "Pinephonepro-V02 2023-0909"). In fact, there is a metal shield attached to the board directly over that area. Is there any way to access these contacts on Pinephone pro explorer edition boards like version 2023-0909?

Thanks for any help!