Okay so it bluetooth pairs with my phone (Motorola ThinkPhone Android 13) but Bangle.js Gadgetbridge doesn't want to discover it.

What am I forgetting to do?

Still running just regular InfiniTime vrs 1.11.0 fosdem edition bootldr 1.0.0

At present I am using my PPP as a daily driver in all capacities. What I have noticed is in order to keep heat to a minimum and also maximum battery life I tend to shut certain things down when not required. For example if I'm on wifi and shut down the modem, when done with BT and wifi I shut down BT and enable modem. Both cameras are shut down on dip switches always. 

Something else I have noticed is that certain sim cards even from same carrier may operate differently. My Blackberry uses my main sim card and works perfectly. When I place that same sim in the PPP the connection is up and then drops and this cycle goes on and on. However when I place my newer sim card in PPP it works perfectly and never drops. That same sim in my Blackberry also works perfectly. The signal strength of my Blackberry sim is slightly weaker than PPP sim and I wonder if sim cards 'get tired'? 

Also I use a Blackberry ear bud set with a 3.5mm jack for comms as nothing else seems to work. The sound is very good. I tried my son's gaming headset with 3.5mm jack and the sound was excellent.

Has anyone tried the PinePhone or PineBook USB-C docking station on the PineTab2?

I've thought of buying an ethernet adapter, but if one of the Pine64 docking stations works, I'd love to to support Pine64 rather than someone else.

bookworm vs trixie discussion for mobian in pinephone pro.

this is a discussion of bookworm vs trixie and maybe staging. so like possible problems and how to fix them. which one is better, and how well it works. here are some generic arguments.

arguments for bookworm:
- stable.
- basics work.
- do not have dependency problems, or broken packages.
- smooth security updates.

arguments against bookworm:
- gets outdated.
- some features are missing, because pinephone is a beta product.
- stuck to the older kernel.

arguments for trixie:
- newer packages.
- features, which are missing in older versions.
- newer kernel.

arguments against trixie:
- dependency nightmare, broken packages.
- some thing do not work, because of unstable packages.

in both cases users have the choose between which audio routing they use, i don't know which one is default.
"pipewire-pulse"
"pulseaudio"

because pinephone pro is beta product, it practically means that users usually need to go on trixie. i recently updated pp pro into trixie, and it seems ok. however, there was dependency issues, so update is not smooth. more information later, how it goes. pp pro is not stuck to lts kernel, unlike pp regular (might be temporary issue though).

Pine64 Ox64 is an affordable RISC-V SBC ($8) based on Bouffalo Lab BL808 SoC with 3 (Asymmetric) RISC-V Cores:

(1) D0 Multimedia Core: 64-bit T-Head C906 with MIPI CSI, Neural Processing Unit
(2) M0 Wireless Core: 32-bit T-Head E907 with WiFi, Bluetooth LE, Zigbee, Audio, USB, Ethernet
(3) Low Power Core: 32-bit T-Head E902

In this article we boot Linux on Ox64 BL808 (with OpenSBI and U-Boot Bootloader). And we explore how Apache NuttX RTOS might run on Ox64.

Check out the article:
Ox64 BL808 RISC-V SBC: Booting Linux and (maybe) Apache NuttX RTOS

Lup
   

irradium - source based Linux distribution CRUX adhering to ideology keep it simple, has its own package system, also supports the port system.

irradium


packages aarch64
packages riscv64


installation README.TXT
irradium-3.7-riscv64-core-star64-6.1.61-build-20231103.img.zst
irradium-3.7-riscv64-core-star64-6.1.61-build-20231103.img.zst.sha256

Hello. I have a Pinetab 2 lying around, waiting for the WiFi driver being ready as I need a little bit of WiFi for most of my use cases.
From time to time I connect a USB-C NIC to the PineTab to check for updates, but now I recieve an error:
Fetching Updates shows an amber exclamation mark and (trying to) updating the PineTab 2 shows a Package Conficr between plasma-framework5 and plasma-framework with conflicting dependencies.

Any ideas how to solve that?

Hi everyone, I'm having a strange problem with my Pinecil v2. I'm using this one for an important project. At first everything was fine. Today I wear an anti-static bracelet and he started burning my wrist. At first I felt tingling. This happens when I hold the Pinecil soldering iron. I point out that this had not happened before. J There also a crackling noise inside the soldering iron

hello dear pinecil comunity, i just unpacked the beautiful iron and tried out functions. i've put it in sleep mode by pressing minus-button on start screen some seconds (iron-crossed-icon on screen) and now i don't find the way back out. powering off and factory reset did not help. hope it's a stupid/easy question which can be solved by pressing the right buttons .. can anyone help? thx in advance!

Hey all! First post here.

I'll keep it quick, but before I start I want to say that I have a workaround and I'm OK with it, although I'd like to have a "cleaner" solution in place if possible.

Long and short of it: Just received my Pinebook Pro a few days ago with Manjaro ARM. All was well until I found out that the version Manjaro I had didn't support external monitors at all, due to patch not being in mainline. Tried different monitors, different cables, rotating cables, etc. No dice.

So I switched to a custom kernel to fix that problem, however that knocked out my WiFi. OS wouldn't even acknowledge that hardware was there. I thought it may have been hardware failure until I starting finding errors about loading Broadcom firmware in dmesg.

I tried the usual suspects such as ensuring /boot was properly mounted, cold booting, privacy switch, etc. Nothing. Reverting back to the original kernel made no difference either.

After many hours of trial & error and searching for answers, I found a set of firmware files which worked when placed in the proper location, but it wasn't "plug-and-play" so to speak. Every time now when I want to use WiFi after booting, I have to use that "(un)bind" trick: