I'm trying to figure out missing pieces in the endeavor of making cameras work. I see that the kernel module for OV5648 is present in 6.6.13-danctnix1-1-pinetab2 kernel and it's linked to the v4l2 subsystem, however none of the /dev/video* devices are operational. Maybe some of you, guys, have already investigated it.

So i was trying to install plasma in arch linux and im now stuck in purism phosh and plasma wayland,. I need some help with removing phosh and leaving plasma as the only option to boot from, When i do start from boot up it starts into the generate gpkey and i have to cancel it out and it sends me back to phosh screen but im not seeing plasma as my default screen, my keyboard is plasma but the rest is phosh. im still seeing chatty and the default phosh layout of phosh. How to fix without having to boot a fresh copy of arch, thanks

Has anyone connected the Pinewatch through Bluetooth Low Energy (BLE) to an ESP32 and found the Bluetooth heart rate service UUID, the heart rate measurement characteristic UUID, and the accelerometer UUID so that they could display that data (i.e., real time heart rate and body motion data) on the serial monitor of the Arduino IDE? I know that many heart rate devices that use BLE also often use a heart rate service UUID of 0x180D and a heart rate measurement characteristic UUID of 0x2A37. However, I also have seen heart rate devices that use different UUIDs from those.

when charging. it was connected to pine64 charger. to its left port, which gives 5.3V.
i felt a smell of burned plastic, came to the phone, and found it like this: backcover melted, and type-c connector melted. it cannot be pulled out now.

glad it didn't explode.

well i guess i can buy a backcover, that's not a problem. but i am afraid that the charging module melted down and that cannot be repaired.
i even afraid of pulling out the usb connector right now. and i hope other modules on the board aren't damaged.
i have photos in the phone, at very least i would be happy just to save those, but no idea if i can connect to its internal storage and unlock luks somehow from outside.

it doesn't turn on anymore.

Remember MakeCode? BBC micro:bit and its Drag-n-Drop App Builder? MakeCode for BBC micro:bit is an awesome creation that’s way ahead of its time (7 years ago!)
- TypeScript Compiler and Arm Assembler in the Web Browser (in JavaScript!)
- Custom Embedded OS (CODAL + Mbed OS)
- micro:bit Simulator in JavaScript

Today 7 years later: How would we redo all this? Maybe with...
(1) Hardware Device: Ox64 BL808 64-bit RISC-V SBC
(2) Embedded OS: Apache NuttX RTOS
(3) JavaScript Engine: QuickJS for NuttX
(4) Web Emulator: TinyEMU WebAssembly for NuttX
(5) C Compiler + Assembler: TCC WebAssembly for NuttX
(6) Device Control: Web Serial API with Term.js

This article explains how we gave MakeCode a wholesome wholesale makeover with NuttX:
Coding Ox64 BL808 SBC the Drag-n-Drop Way

Lup

   

I had to retire my second installation of Mobian Linux on a 500GB chip when the chip's output became much too slow, this happening on the PinePhone Pro of course.

So, I'm new to Arch. Might be more of an Arch question, but here goes:

I recently broke my OS by updating a bunch of stuff from the "extra" repos. When I ran the following to update:

I just received a Pine Phone Pro the other day and was playing around in the pre-beta sailfishOS install when I accidentally disabled Developer mode and the OS sort of bricked itself. I was able to flash Manjaro ARM to keep tinkering with it, so the phone itself is fine.

I've been searching but haven't been able to find a community link to the image the phone shipped with. It was the latest sailfishOS 4.5, does anybody know where I can re-download that image?

Hi,

I'm having an issue with my pinebook pro. I recently was fixing a pinebook pro for a friend, and somehow my screen decided to not turn on anymore. The pinebook pro boots correctly since i can ssh into it. I tried setting the screen brightness via ssh to no avail. Also disconnected and reconnected the screen ribbon cable on the motherboard. But i still have a black screen. Is there anything else i can do to try and fix the screen?

Thanks!

I tried to use Jumpdrive to write an os image to the exposed /dev/hda block device and now the tablet no longer boots. Jumpdrive always boots though and I tried "flashing" the factory default image but still no luck.

Can I somehow use Jumpdrive to restore my PineTab2 to a bootable condition?

I never received a USB/UART with my PineTab2 and shipping to USA is quite expensive so buying this would be a last resort.