Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 27,942
» Latest member: ayishadawson
» Forum threads: 15,618
» Forum posts: 114,260

Full Statistics

Latest Threads
I Went on a Roadtrip With...
Forum: PinePhone Pro Software
Last Post: nekonosuke
4 hours ago
» Replies: 0
» Views: 23
Image Latest Phones Ship ...
Forum: PinePhone Pro Software
Last Post: aular
6 hours ago
» Replies: 5
» Views: 115
How to install Plasma Mob...
Forum: PineTab Software
Last Post: aular
7 hours ago
» Replies: 14
» Views: 2,807
Pinetab 2 just arrived + ...
Forum: General Discussion on PineTab
Last Post: Surehand53
9 hours ago
» Replies: 15
» Views: 6,707
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: cringeops
9 hours ago
» Replies: 0
» Views: 29
stuck between phosh and p...
Forum: Arch Linux on PinePhone
Last Post: aular
Yesterday, 05:55 PM
» Replies: 0
» Views: 22
Heart Rate and Accelerome...
Forum: General Discussion on PineTime
Last Post: pinetimer
02-26-2024, 11:35 PM
» Replies: 0
» Views: 23
Internal WiFi status?
Forum: PineTab Software
Last Post: Username_012
02-26-2024, 08:53 PM
» Replies: 30
» Views: 4,410
my pinephone melted
Forum: PinePhone Hardware
Last Post: tllim
02-26-2024, 04:53 PM
» Replies: 2
» Views: 195
AI posts
Forum: General
Last Post: KC9UDX
02-26-2024, 01:42 PM
» Replies: 6
» Views: 191

  I Went on a Roadtrip With PostmarketOS
Posted by: nekonosuke - 4 hours ago - Forum: PinePhone Pro Software - No Replies

I went on a 10 hour roadtrip with PostmarketOS and did not have a great experience, actually. There are a handful of persistent bugs that I have been bashing my head against since day one that have caused me to completely lose my patience. It would be easiest to make a list of features and report what is or is not working - all of which I have tested both with and without the keyboard case:

[ ] = Not working at all; [X] = Working out of the box; [\*] = Working with some setup; [\B] = Works but has bugs; [P] = Partially working; [?] = Not readily available or did not spend enough time testing

[X] Install: The experience installing this distro to the phone was quick, easy, and effective unlike certain other distros that make you add/change passwords/user names/host names/etc after you've already installed it on the phone. These things can be set up during the install process like you would expect when installing most desktop distros.

Linux: (Okay, this section is mostly just opinion. I shouldn't even include this since it's likely to derail any productive discussion) OpenRC...just why? Why would this be used instead of systemd? I'm not saying OpenRC has no uses but I see absolutely zero benefit to dying on that hill here with the Pinephone Pro. And Ash as the only preinstalled shell? Absurd. Seriously, why not include Bash at the absolute minimum? I didn't even realize it was possible for a distro to function without Bash installed. APK feels like a watered down apt. First experience with Alpine Linux, hope it's my last.

[X] SMS: Totally fine, never had any issues at all with this. Much prefer Spacebar over Chatty.

[\*] Call: Took a lot of configuring to tame the microphone but works reliably now.

[\*] MMS: Overall works well and relatively stable. I have 2 APNs and if I receive any MMS messages after losing connection to my Data APN, the MMS will permanently fail to download.

[ ] Camera: Completely broken. Neither have ever worked for me on PMOS. I have tried installing or compiling 6 apps and none worked. Most of the time the camera is simply not detected. Megapixels likes to seg fault. On Mobian, the default app Pinhole works. Even compiling this and its dependencies on PMOS resulted in no camera being detected.

This was especially useful when I was rear-ended and couldn't take a picture of the person's insurance card.

[ ] Alarm: Completely broken. Will not wake phone from sleep. Tested with default app and wakeup-mobile which had an APK that included wakeup-rc or some such similar packages. This also did not work.

[\B] Battery: Battery life is fine using the community modem sdk. Aftermarket battery percentage readings were working fine until the latest firmware update and now the number frequently bounces around both up and now.

[?] Printing: I actually did need to print something while I was on my trip and for the life of me couldn't figure out how. I honestly didn't spend much time on it as I just asked someone else to print it for me but I'm not even sure there's a print server running.

[P] Suspend: Sleep after media playback is very broken. I even wrote a script that runs in the background and kills the media player after 30 minutes and suspend will still fail. I altered the script to run "loginctl suspend" 15 seconds after killing the media player and suspend will still fail. This manifests when I wake up 4 hours later, the phone is very hot to the touch, screen is off, battery nearly dead after falling asleep with a full charge.

dmesg does not return any errors and the app is successfully closed when I unlock. Ran out of ideas and patience for toubleshooting this. I rely on this feature every night to listen to music or asmr so I can fall asleep. This bug is especially egregious to me. Occassionally suspend with no active tasks stops working but for the most part is stable.

[\*] Flashlight: Works. Had an issue where the udev rule got deleted (no clue how or if I somehow caused this) and I had to recreate it so the flashlight would work again.

[\*] GPS: No toggle to turn on/off location services, had to write a script and assign keyboard shortcuts. I use Pure Maps and have had no issues navigating with it,

[\B] Bluetooth: Mostly okay. After about 3 to 4 hours of use, perhaps the physical module or antena is overheating? This might not be specific to PMOS however I have not tested bluetooth this long continuously on other distros. After the 3 or 4 hours, bluetooth will disconnect and music starts playing over the hardware speakers. Bluetooth will reconnect, play music for a few seconds, and disconnect again. The only fix is to wait an indeterminate amount of time and restart the phone.

When my CD player also stopped working, I had a painfully quiet 4 hours left on the drive home. It's not uncommon to use bluetooth for 8 hours consecutively however I readily admit that it is far from the average use-case. I should have brought a cable for the aux input...

[X] Mobile Data: Works fine. I don't have issues surfing the web or streaming videos up to 720p. There is a second package offered for Firefox that must be installed for the UI to scale correctly - it also installs ublock origin and tweaks some other settings. User agent reports as Linux-mobile which is indeed correct however that sticks out like a sore thumb.

[X] Wifi: Works perfectly fine out of the box.

[ ] USB: Completely broken. I can't plug anything into the usb-c port other than a charger. I even went and found a usb-c only flash drive and nothing was reported in dmesg or lsusb when plugged in. Phone is detected by my computer as a Pine64 Pinephone Pro but MTP is unavailable.

[\B] UI: I went with PMOS largely because they offer Plasma-Mobile out of the box which generally speaking I love the look and feel of however there are some issues. Occasionally, using the volume buttons will crash the display session to a black screen. Sometimes the power menu will still trigger in this state. Very frequently, when phone is unlocked in a different rotation than it was locked in, autorotate fails to display half of the screen and needs to be rotated back and forth to get it to display properly. Rarely, this can crash the display similarly to the volume button.

[\*] Keyboard Case: The top row symbols did not work out of the box. I had to change the 3rd level composition key to Right-Alt after installing the proper keymap files. Now it works perfectly fine. Still need to figure out how to change the Pine key to caps-lock but that's unrelated and non-default behaviour.

[P] Keyboard - Virtual: English keyboard works perfectly well. Japanese was easy to install but practically unusable. お こ and そ (o, ko, and so) cannot be typed since any attempt to swipe over these characters causes the virtual keyboard to be closed. Swiping down from the top of the virtual keyboard in any language causes it to be closed, this needs to be inhibited with Japanese input so that only the back arrow minimizes it or the grab window needs to be adjusted.

Conclusion: I can live with something that's takes effort to set up properly. Most of the bugs and issues listed here are negligible or one time fixes. The distro is very close to being useable for Pinephone Pro. There are a few things though that I absolutely cannot tolerate: broken alarm, broken suspend (after media playback), broken camera, broken Japanese keyboard, frequent crashes. My phone crashes every other day at best. It crashed on the drive down and twice on the drive back.

These issues are deal breakers in my opinion and I will switch to a different daily use distro while keeping PMOS on the backburner until these issues are resolved (and stay resolved, ideally). I don't mean to be insulting or overly critical to the developers for PostmarketOS, all said and done there are reasons I chose this to daily drive and I think this distro has a lot of potential. I want to see this succeed and if I can contribute to bug testing, I will.

I probably could have posted some of these to their Gitlab issues page but I also needed to organize what all the issues I experienced were and which ones would be worth reporting there in addition to needing some time to recharge my patience. Plus hopefully this gives people an idea of what to expect when considering PMOS - not that my experience will dictate what yours may be though.

Video Pinetab2 camera drivers
Posted by: cringeops - 9 hours ago - Forum: PineTab Software - No Replies

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.

➜  ~ lsmod | grep ov5648
ov5648                32768  0
v4l2_fwnode            28672  1 ov5648
v4l2_async            28672  3 v4l2_fwnode,dw9714,ov5648
videodev              339968  8 v4l2_async,v4l2_fwnode,videobuf2_v4l2,dw9714,hantro_vpu,rockchip_rga,ov5648,v4l2_mem2mem
mc                    77824  8 v4l2_async,videodev,videobuf2_v4l2,dw9714,hantro_vpu,videobuf2_common,ov5648,v4l2_mem2mem

➜  ~ cat /sys/bus/platform/devices/fe5b0000.i2c/i2c-2/2-0036/name

➜  ~ sudo dmesg | grep ov5648
[    8.541190] ov5648 2-0036: failed to find 168000000 clk rate in endpoint link-frequencies

The dmesg suggest that the driver expects 168000000 clock rate, but cannot find it in the device-tree.

UPD: I found the DTS used for the device, and indeed, the clock rate is 400000.

  stuck between phosh and plasma
Posted by: aular - Yesterday, 05:55 PM - Forum: Arch Linux on PinePhone - No Replies

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

nvm i uninstallee phosh but i have no keyboard access when trying to login to wayland

  Heart Rate and Accelerometer, ESP32, Arduino
Posted by: pinetimer - 02-26-2024, 11:35 PM - Forum: General Discussion on PineTime - No Replies

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.

  my pinephone melted
Posted by: norayr - 02-25-2024, 05:24 AM - Forum: PinePhone Hardware - Replies (2)

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.

[Image: DSCF0469.jpg]

[Image: DSCF0466.jpg]

[Image: DSCF0467.jpg]

[Image: DSCF0468.jpg]

[Image: DSCF0470.jpg]

  [Article] Coding Ox64 BL808 SBC the Drag-n-Drop Way
Posted by: lupyuen - 02-24-2024, 06:38 PM - Forum: General - Replies (1)

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



  Is it only me? MicroSD chips do not last.
Posted by: mburns - 02-24-2024, 02:05 PM - Forum: PinePhone Pro Accessories - No Replies

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.

  Updating the "extra" repository breaks the Danctnix OS
Posted by: Evergreen - 02-24-2024, 12:40 PM - Forum: PineTab Software - No Replies

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:

sudo pacman -Syu

It asked me if I wanted to basically reinstall a bunch of already installed packages via the "extra" repository. I was tired of seeing that prompt, so I finally just said yes to everything. After that, the OS wouldn't boot. I did this twice actually. Same thing happened.

I successfully reinstalled the OS, I just don't want to make the same mistake a third time.

How do I either avoid breaking the OS with extra or make sure that the prompt isn't annoying me all the time?


  Image Latest Phones Ship with
Posted by: vorell - 02-24-2024, 11:39 AM - Forum: PinePhone Pro Software - Replies (5)

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?

  Screen on pinebook stays black but can ssh into machine
Posted by: tuxxpine - 02-23-2024, 04:22 PM - Forum: General Discussion on Pinebook Pro - No Replies


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?