Is it proper to report AI posts as "spam content"?

If not, is there a better way to report them; or, should we not report them at all?

Is it notable to anyone else that since posting comments about updating Arch Linux yesterday my phone has been acting particularly differently?
I'm not sure the cause.  I'm suspicious about external tampering.  That would be a shame.  There's likely nothing to gain.  I'm a poor man with little joy in life.  It'd be in anyone's best interest to have a conversation with me rather than play tricks.  I have more to offer in words, I'm sure, than anything.

I finally got my old model Pinephone running.......   A+

My battery fix is this:

Anker Portable Charger Powerbank 20,000 mAh      $34.00 on Amazon

It has a four light indicator to show the battery charge  ( takes overnight to charge 100% )

Now - I'm running Arch Phosh

Runs all day all night no problems

I calculated it will last 2.6 days

Get a short six inch cord to connect the two together..... maybe a little double back tape

I just need a basic phone - dialing and texting

Both are working Very Reliably



The battery pack is the exact size as the phone -  twice the thickness

Fine job Arch

Hello,

I decided to replace Manjaro on my PBP and try out Void Linux. I never used it before, but would like to see how well it works with musl on the pinebook pro, since Manjaro felt a little heavy on it. I followed the instructions here, https://wiki.pine64.org/wiki/Pinebook_Pr..._Linux_ARM, with the following notes:

• I used a Manjaro live environment to do the configuration, and I booted the live environment from an SD card
  
• I first followed the Arch tutorial to flash Tow-Boot and create the partitions. I used ext4 for both the boot and root partitions.
  
• I then extracted the void rootfs into the root partition, then chrooted into it, and started following the void tutorial located here while avoiding any boot-loader related instructions. I updated xbps and installed base-system and also set the root password. I did not install grub because I figured Tow-Boot woudl be doing the booting
  
• I installed the pinebookpro-kernel package with xbps because I didn't want to build my own kernel.
  
• I installed the u-boot-menu
  
• Despite what the instructions said, I had to write my own extlinux.conf and I made sure to point to the right kernel file, and that fdt points to the right file
  

I wonder if I should update my Arch installation.  It's been running for a tear and I havn't updated anything.  I'm afraid to do so because I'm afraid something will break and the phone/cpu will become unusable.
I'm sure I'm in over my head with Arch Linux, but this is what I'm stuck with.

QuickJS is a small JavaScript Engine that supports POSIX Functions. Can we run QuickJS on Apache NuttX RTOS? And Blink the LED in 4 lines of JavaScript?

  const ULEDIOC_SETALL = 0x1d03;
  const fd = os.open("/dev/userleds", os.O_WRONLY);
  os.ioctl(fd, ULEDIOC_SETALL, 1);
  os.ioctl(fd, ULEDIOC_SETALL, 0);

In this article we…
(1) Run QuickJS on NuttX with Ox64 BL808 RISC-V SBC
(2) Blink the LED by adding the ioctl() function
(3) Reconfigure the NuttX App Stack (because it’s too tiny)
(4) Analyse the Memory Footprint of QuickJS (Code + Data + Heap Size)
(5) Test QuickJS in the Web Browser with NuttX Emulator (and a Simulated LED)

QuickJS is perfect for Iterative, Interactive Experiments on NuttX! Check out the article:
https://lupyuen.codeberg.page/articles/quickjs.html

Lup


   

I have a good understanding of computer technology but in recent years find myself moving towards near complete digital detox, I think there is far too much waved connection.

I run a Mudita Pure e-ink dumb phone which works as a modem and a rooted & degoogled Onyx Boox Note Air 2 Plus for everything else, at least that is the idea. The privatized Boox tablet firmware (controversial because of GPL) has proved a nuisance and thus I find myself using the linux laptop I intend to sell. 

I like a rough, physical, healthy lifestyle, so to compliment it, I would like a rugged / metal Pinenote to work in tandem with a simple phone. Also, my opinion is that a colour e-ink display option would allow for a better multi-purpose device, I have had trouble reading backroad / topographic map-books in grayscale, and colour is helpful for the odd online purchase as well.

Simple e-ink devices seem to me a better path or at least compromise in the balance of things.

So, my take:

• Rugged & metal
  
• Optional colour display
  
• Not too big
  

o Signal for Pinefon is 'signal-desktop_6.44.1_arm64.deb' at Gitlab (Requires
  Signal on your android)...

    - https://gitlab.com/undef1/signal-desktop...s/22135879

Download both files (?.deb and ?.deb.sig) in same dir. Click on the ^ next
to the getlab .deb file and get the check sum. Go to that download dir and
check signature w/...

>sha256sum signal-desktop_6.44.1_arm64.deb
Output: long number
Check long number against the check sum

o  Install...

      >dpkg -i signal-desktop_6.44.1_arm64.deb

-wigan-

I'm looking for the specification for the ribbon cable connecting the track pad to the main board connector. I have a Pinebook Pro that I picked up that does not have the ribbon cable for the track pad on it. Is there anyone who happens to know the specifications? (i.e number of pins, width, etc) Many thanks for any help.

The Quectel modem EG25GGBR07A08M2G of a recently (January 2024) purchased PinePhone Pro Explorer Edition became non-functional after an attempt to replace its firmware with the community one:

https://wiki.pine64.org/wiki/PinePhone#Firmware_update

The described process with the fwupd (0.7.2 is the latest version available there) on Mobian 12 ended up with the modem stably disappeared from the system, without returning back after rebooting or un-/re-powering the device. The recipes from the community repository helped to boot the modem in the QDL mode and flash it again - but it doesn't function any more: it is visible to the system and is generally responding to the AT interface, but it can't be enabled. In particular, some of the AT commands fail - e.g. it is impossible to return IMEI or SN. This seems regardless of firmware: the latest (0.7.4) community version and all the stock versions from the recovery repository were tried with the same result.

So the questions I have:

1. What is the exact version of the stock firmware for the Quectel EG25GGBR07A08M2G modem which the PPP Explorer Edition are being shipped with today?
   
2. Is there any further way to diagnose and fix the issue?