Anyone tried that 100 USDT airdrop on alphapepe.net? Was it legit?
PINE64
forum.pine64.org ↗Foro MyBB en inglés. 8 secciones seguidas: Lengua Española, News Threads: 117 // Posts: 3,270, Getting Started Threads: 499 // Posts: 2,982, Remix OS, Shipment Related Discussion, Community and Events Threads: 76 // Posts: 579, Android on Pine A64(+) y General Threads: 1,004 // Posts: 6,483.
- Discusiones por día
- 2
- Discusiones recopiladas
- 117
- Mensajes por día
- 19
- Secciones
- 8
- Fuentes seguidas
- 10
- Motor
- MyBB
Últimas discusiones
Recogido cada 4 horas desde el feed público del foro. Solo se reproducen el título, el enlace y el principio del mensaje; cada enlace remite a la fuente.
Having my Rock64 card for over 8 years running ayufan's Android TV (thanks a lot for this perfect job!) i tried to migrate to Android 10. Here is a patch set that can be applied to Firefly SDK. Not sure it makes sense still... https://github.com/vtsick/rock64-android10-tv
Hacklink Paneli | Hacklink Satın Al | Hacklink Satışı Hacklink panel ile hızlı şekilde hacklink satın alabilirsin. Hacklink girişi yapmak kolay ve SEO da backlink önemlidir. Hacklink güvenilir ve hızlı gerçek kaliteli link alımı yapmanıza sağlar. Sende Hacklink panel giriş ile satın al. ? Website: https://panel.hacklinkmarket.com/ ? Hacklink Panel - Hacklink Panel - - - - - - - - - - - - - -
She's in your city GirlSingle.com She's waiting for you to say yes
Hey everyone, I’ve been a long-time lurker here and a huge fan of the Pine64 ecosystem for a few years now. My journey started with a Pinebook Pro that I used as a dedicated "distro-hopping" machine, and more recently, I’ve been experimenting with a small cluster of Quartz64 boards for some home automation and a localized private cloud. One thing that’s been on my mind lately, especially as I start pushing more containerized workloads and heavier database tasks, is the "memory ceiling" we often hit with SBCs. I’ve noticed a specific point in a few recent dev threads discussing how we can better optimize swap and zram, but it really makes me wonder about the hardware side of things. I recently did a refresh on my main desktop/home server, moving it up to a 16GB kit of DDR5-4800MHz memory . It’s that PC5-38400 spec, and honestly, seeing the jump in raw bandwidth compared to my older DDR4 rig was a bit of a wake-up call. It’s not just about the capacity; it’s how quickly the system can move data for multitasking and heavy I/O. It made me realize how much I’ve grown accustomed to the snappiness of higher-frequency RAM in the x86 world, and it left me wishing for a bit of that "oomph" in my ARM projects. I know we’re dealing with completely different power envelopes and thermal constraints here, but as we see more powerful SoCs coming down the pipeline, I can't help but dream of a Pine64 board that supports something like the PC5-38400 standard. Even if it was soldered LPDDR5 to s
Hardware Feature Suggestion: SPI Flash Hardware Write-Protect & Factory-Flashed Secure Boot First of all, thank you for providing amazing open-source hardware to the community. I am a developer, privacy enthusiast, and independent researcher, and I would like to propose a simple yet high-value hardware revision for future batches of the Quartz64 or upcoming single-board computers. Currently, the board relies on DIP switches for boot priority, which is firmware-based and does not physically cut the power line for the SPI Flash write operations. For users focused on sovereign security, physical containment, and preventing persistent firmware implants (rootkits), having a Hardware Write-Protect (WP# linked to GND via a physical Jumper or a Screw mechanism)—similar to the Chromebook write-protect screw—is crucial. Adding small exposed copper jumper pads (open pads) between Pin 3 (WP#) and Pin 4 (GND) on the PCB layout would allow advanced privacy users to bridge them and achieve true physical, air-gapped read-only isolation for the Tow-Boot/SPI flash. Furthermore, for PINE64 boards that come with a pre-soldered SPI Flash from the factory, we strongly suggest shipping them with a clean, verified, and officially signed open-source bootloader (like Tow-Boot) pre-flashed out of the box. Many security-conscious buyers operate in highly compromised, untrusted, or heavily monitored network environments where flashing a clean image locally from scratch is incredibly risky or nearly impos
Hardware Feature Suggestion: SPI Flash Hardware Write-Protect & Factory-Flashed Secure Boot First of all, thank you for providing amazing open-source hardware to the community. I am a developer, privacy enthusiast, and independent researcher, and I would like to propose a simple yet high-value hardware revision for future batches of the Quartz64 or upcoming single-board computers. Currently, the board relies on DIP switches for boot priority, which is firmware-based and does not physically cut the power line for the SPI Flash write operations. For users focused on sovereign security, physical containment, and preventing persistent firmware implants (rootkits), having a Hardware Write-Protect (WP# linked to GND via a physical Jumper or a Screw mechanism)—similar to the Chromebook write-protect screw—is crucial. Adding small exposed copper jumper pads (open pads) between Pin 3 (WP#) and Pin 4 (GND) on the PCB layout would allow advanced privacy users to bridge them and achieve true physical, air-gapped read-only isolation for the Tow-Boot/SPI flash. Furthermore, for PINE64 boards that come with a pre-soldered SPI Flash from the factory, we strongly suggest shipping them with a clean, verified, and officially signed open-source bootloader (like Tow-Boot) pre-flashed out of the box. Many security-conscious buyers operate in highly compromised, untrusted, or heavily monitored network environments where flashing a clean image locally from scratch is incredibly risky or nearly impos
So, I’m running my Star64 headless for crypto mining, but lately I’ve been wondering—why not give it a co-processor that’s a little more… interactive? Has anyone ever tried to cohabitate with an SBC in a way that’s more about shared leisure than silent computation? MeetAgree.com Your city's hottest girls are here
So, I’m running my Star64 headless for crypto mining, but lately I’ve been wondering—why not give it a co-processor that’s a little more… interactive? Has anyone ever tried to cohabitate with an SBC in a way that’s more about shared leisure than silent computation? MeetAgree.com Your city's hottest girls are here
So, I’m running my Star64 headless for crypto mining, but lately I’ve been wondering—why not give it a co-processor that’s a little more… interactive? Has anyone ever tried to cohabitate with an SBC in a way that’s more about shared leisure than silent computation? MeetAgree.com Your city's hottest girls are here
So, if you're already soldering tiny boards and debugging firmware at 3 AM, why not repurpose that Pinecil as a social debugging tool—like a playful way to "hotwire" connections with fellow tinkerers at meetups? Ever tried turning a soldering iron into an icebreaker? MeetPrettyGirls.com Find a girl to share the night with
So, if you're already soldering tiny boards and debugging firmware at 3 AM, why not repurpose that Pinecil as a social debugging tool—like a playful way to "hotwire" connections with fellow tinkerers at meetups? Ever tried turning a soldering iron into an icebreaker? MeetPrettyGirls.com Find a girl to share the night with
117 discusiones recopiladas desde el 31 de agosto de 2026. Seguir este foro por palabra clave →