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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,636
» Latest member: Commothe
» Forum threads: 16,232
» Forum posts: 117,083

Full Statistics

Latest Threads
Pinetab-V boot rescue
Forum: General Discussion on PineTab
Last Post: anoduck
20 minutes ago
» Replies: 2
» Views: 59
Should HDMI output work i...
Forum: General Discussion on PinePhone
Last Post: Richy_T
8 hours ago
» Replies: 0
» Views: 23
Pinephone boot.
Forum: General Discussion on PinePhone
Last Post: Richy_T
8 hours ago
» Replies: 6
» Views: 3,769
Revisit and check current...
Forum: General Discussion on PinePhone
Last Post: mikehenson
Yesterday, 09:52 AM
» Replies: 1
» Views: 87
bookworm vs trixie discus...
Forum: PinePhone Pro Software
Last Post: biketool
Yesterday, 07:01 AM
» Replies: 21
» Views: 12,100
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: biketool
Yesterday, 02:48 AM
» Replies: 14
» Views: 10,228
Upgrading from Trixie to ...
Forum: PinePhone Pro Software
Last Post: biketool
Yesterday, 02:39 AM
» Replies: 0
» Views: 46
Diagnosing and fixing fai...
Forum: PinePhone Pro Software
Last Post: biketool
Yesterday, 02:05 AM
» Replies: 0
» Views: 32
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: anonymous
10-19-2025, 05:48 PM
» Replies: 75
» Views: 39,180
trixie update poll questi...
Forum: Mobian on PinePhone
Last Post: anonymous
10-19-2025, 05:45 PM
» Replies: 3
» Views: 200

 
  Unable to switch from Wasp-OS back to Inifinitime using GadgetBridge
Posted by: Bruce Kissinger - 10-02-2024, 07:31 PM - Forum: General Discussion on PineTime - No Replies

I have installed the latest version of Wasp-OS on a new PineTime watch, however I would like to switch back to Infinitime.  I installed Wasp-OS using the latest version of GadgetBridge (v 0.18.0) on an Android phone and the process was really simple.  However, I have run into problems trying to switch from Wasp-OS back to Infinitime.  

The problem is that when I try to use GadgetBridge to install the Inifinitime Zip files, I get an error from GadgetBridge that states "FW/App Installer - Element cannot be installed".  GadgetBridge is successfully connected to the watch via BLE.  I've tried a number of different versions of the Zip files, but all return the same error.  

Does anyone have advice for how to get past this?  Thank you in advance


  Searching for a PinePhone Keyboard Case
Posted by: RubiksCube - 10-02-2024, 12:35 PM - Forum: PinePhone Accessories - Replies (1)

Hey there,

I am looking for an original PinePhone Keyboard Case as it is not possible to buy it from the official store (and sadly will maybe never be). If you have one for sale, just write me a pm with your price and location (and maybe a picture) and we will get this going. I am also willing to pay for international shipping.


Thanks!
P.


  Unable to use umlaut key combos
Posted by: ili - 10-01-2024, 12:44 PM - Forum: General Discussion on Pinebook Pro - Replies (4)

Hi guys,

the pinebook pro wiki says in the keyboard section it should be possible to type German umlauts by using key combos.

--------------
Ä, Ö, Ü, ä, ö, ü

[AltGr]+'[' followed by [A], [O], [U], [a], [o] or [u
--------------

I think i tried everything but i can't get it working.

I used Manjaro ARM Flasher and installed

pbpro kde-plasma 23.02

Is there anything else i need to do?

I left all settings unchanged

Hardware is set to Gerneric 104-key PC


Can anybody help me?

Thanks in advance.


  Some Suspense.... Camerra App
Posted by: biketool - 09-27-2024, 06:25 AM - Forum: Mobian on PinePhone - Replies (3)

Ran updates today and noticed that there were system updates as well as the camera app, I am running Trixie on a Pinephone Pro.
Clicked the camera app just to see and unlike usual it asked me to authorize camera use, had a moment of hope before it prompted that there were no cameras found in the system.
Is there any tracking I could look at on the work being done to bring the PPP cameras front and back to use in Mobian Trixie?  Searching the Mobian wiki doesn't seem to help me.  It also doesn't lead me the the hacks I see mentioned to trick the system into using the cameras on the PPP.


  desktop and lockscreen
Posted by: biketool - 09-25-2024, 05:11 AM - Forum: Mobian on PinePhone - Replies (1)

Is it at this time possible to set a custom lockscreen and/or desktop/background on mobian Trixie?
There is the option in settings but it didn't change anything except under some loading apps where the load screen is not present.


  No HDMI Video - Anything To Check?
Posted by: angrymallard - 09-25-2024, 04:58 AM - Forum: General Discussion on ROCKPRO64 - Replies (2)

Hello all, I am working on a RockPro64 that seems to have a non-functional HDMI output but I'm trying to see if there's anything else for me to check before I RMA the unit. Everything else seems to be working, for example I can load the minimal Armbian image to it, boot it, and then SSH into it and see that the computer itself is working. But at no point is there ever any video output. There's no boot screen visible either. I've tried two different HDMI cables on two different monitors, confirmed these cables/monitors work with other devices, tried to hook up a USB-C hub, etc.

I've tried a few other images as well, LibreELEC (originally I planned for this to be a media center so this was the first one I tried), a few different Armbian images including the XFCE Debian 12 version, the Cinnamon Debian 12 version, the Ubuntu Gnome version, and DietPi. I can't verify that any of these work, although I am pretty certain that these have SSH access disabled by default and without video there's no way for me to enable that to check on these distributions. I also used the "flash_spi" image here https://github.com/sigmaris/u-boot/wiki/...oot-to-SPI to make sure that was working properly.

I also tried to add the kernel module from this guide https://wiki.pine64.org/wiki/ROCKPro64#N..._on_Debian but it seems like my problem is happening before the kernel loads since there's no video output at all when it boots in the first place.

Since I can boot and SSH into the minimal Armbian install, is there anything I should check before I send this unit back? I don't currently have a serial cable but hope that since I can SSH into a terminal I won't need one for looking around at anything.


  Developing on Mac (M3)
Posted by: oksalahti - 09-22-2024, 07:48 AM - Forum: Development Discussion on PineTime - Replies (1)

Hi,

I just bought PineTime and started working on my own watch face.

I managed to compile and run LVGL simulator for Mac with M3 (https://docs.lvgl.io/7.11/get-started/pc-simulator.html)

I tested my watch face with the LVGL simulator and it works as I would like it to work. Next step is to try to get my watch face running on the InfiniSim simulator.

I managed to compile the InfiniSim simulator on Mac but it won't start. These are the error messages I get when trying to run the compiled simulator on mac.

Has anyone managed to run the InfiniSim simulator on mac? Any ideas what's going on? I know I might be able to build InfiniTime project itself and upload my new code on my device but I'd feel much more safe if I can verify that the code runs on the simulator first.

Code:
initial free_size = 40360
info:  systemtask task started!
info:  Last reset reason : Reset pin
info:  [SpiNorFlash] Manufacturer : 0, Memory type : 0, memory density : 0
info:  [SpiNorFlash] Wakeup
info:  DISABLE
info:  displayapp task started!
info:  DISABLE
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'nextEventMatchingMask should only be called from the Main Thread!'
*** First throw call stack:
(
0  CoreFoundation                      0x0000000186420540 __exceptionPreprocess + 176
1  libobjc.A.dylib                    0x0000000185f11eb4 objc_exception_throw + 60
2  AppKit                              0x000000018a37487c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3164
3  SDL2                                0x000000010502d76c SDL2 + 87916
4  SDL2                                0x000000010502da08 SDL2 + 88584
5  SDL2                                0x00000001050aca00 SDL_DYNAPI_entry + 218324
6  SDL2                                0x00000001050acb30 SDL_DYNAPI_entry + 218628
7  infinisim                          0x0000000104706af8 sdl_event_handler + 44
8  infinisim                          0x00000001046dd328 lv_task_exec + 96
9  infinisim                          0x00000001046dd0a0 lv_task_handler + 536
10  infinisim                          0x00000001046944c8 _ZN8Pinetime12Applications10DisplayApp7RefreshEv + 328
11  infinisim                          0x000000010469433c _ZN8Pinetime12Applications10DisplayApp7ProcessEPv + 88
12  infinisim                          0x000000010470b8bc _Z20sdl_function_wrapperPv + 44
13  SDL2                                0x0000000105037e80 SDL2 + 130688
14  SDL2                                0x000000010503aef8 SDL2 + 143096
15  libsystem_pthread.dylib            0x00000001862ce034 _pthread_start + 136
16  libsystem_pthread.dylib            0x00000001862c8e3c thread_start + 8
)
libc++abi: terminating due to uncaught exception of type NSException
zsh: abort      ./infinisim


  Flashing rk2aw to the PinePhonePro
Posted by: mikehenson - 09-21-2024, 06:23 PM - Forum: General Discussion of PinePhone Pro - No Replies

Flashing rk2aw to the PinePhonePro

#https://xff.cz/kernels/

Code:
cd Downloads
wget https://xff.cz/kernels/bootloaders-2024.04/ppp.tar.gz
tar -xvzf ppp.tar.gz
cd ppp
sudo ./spinor-flash-initial-setup.sh

#wait until it finishes

Device: PinePhonePro
OS: DanctNIX Arch with Phosh


  Updating Biktorgj from 0.7.2 to 0.8.0
Posted by: mikehenson - 09-21-2024, 06:09 PM - Forum: General Discussion of PinePhone Pro - No Replies

Updating to Biktorgj from 0.7.2 to 0.8.0

#https://themodemdistro.com/docs
#https://github.com/the-modem-distro/pinephone_modem_sdk/releases/tag/0.8.0

Code:
fwupdmgr get-devices
sudo pacman -S android-tools
cd Downloads
wget https://github.com/the-modem-distro/pinephone_modem_sdk/releases/download/0.8.0/package.tar.gz
tar -xvzf package.tar.gz
sudo ./flashall

# If the modem doesn't disappear when the script starts, try running the flashall script as root.
# Wait for the modem to come back, maybe 2 minutes on my PinePhonePro
Code:
fwupdmgr get-devices

Device: PinePhonePro
OS: DanctNIX Arch with Phosh
Carrier: USA - Patriot Mobile (T-Mobile SIM)
EG25 Firmware: Biktorgj 0.8.0
ADSP Version: 01.003


  2024 Sep 21 - PinePhonePro Calls Working
Posted by: mikehenson - 09-21-2024, 04:48 PM - Forum: General Discussion of PinePhone Pro - Replies (9)

START EDIT: 
Clean up and adding Mobian steps.
OS: DanctNIX Arch with Phosh fully updated
OS: Mobian fully updated
EG25 Firmware: Biktorgj 0.8.0
ADSP Version: 01.003

This uses PipeWire, Not PulsaAudio

DanctNIX Arch with Phosh
pipewire-alsa is required to get call audio.

Code:
sudo pacman -S pipewire-alsa
alsa-utils is required to run alsamixer so we can set the Microphone volume to 0
Code:
sudo pacman -S alsa-utils
pine64-alsa-ucm configuration files
Code:
cd /usr/share/alsa/ucm2/PinePhonePro/
#backups are good
sudo mv VoiceCall.conf VoiceCall.conf.org
sudo mv PinePhonePro.conf PinePhonePro.conf.org
sudo mv HiFi.conf HiFi.conf.org
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/VoiceCall.conf
sudo wget https://raw.githubusercontent.com/dreemurrs-embedded/Pine64-Arch/master/PKGBUILDS/pine64/alsa-ucm-pinephonepro/PinePhonePro.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/HiFi.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/EnableSeq.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/DisableSeq.conf
Restart the phone
During a call, run alsamixer and set the default (PipeWire) microphone value to 0.
The Audio on the "other phone" should clear up
Plug in a headset (3.5mm headphones with microphone)
run alsamixer again and set the default (PipeWire) microphone value to 0.
DONE!

Mobian
alsa-utils is required to run alsamixer so we can set the Microphone volume
Code:
sudo apt install alsa-utils
pine64-alsa-ucm configuration files
Code:
cd /usr/share/alsa/ucm2/Rockchip/PinePhonePro/
#backups are good
sudo mv VoiceCall.conf VoiceCall.conf.org
sudo mv PinePhonePro.conf PinePhonePro.conf.org
sudo mv HiFi.conf HiFi.conf.org
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/VoiceCall.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/PinePhonePro.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/HiFi.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/EnableSeq.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/DisableSeq.conf
Restart the phone
During a call, run alsamixer and set the default (PipeWire) microphone value to 0.
The Audio on the "other phone" should clear up
Plug in a headset (3.5mm headphones with microphone)
run alsamixer again and set the default (PipeWire) microphone value to 0.
DONE!

Benefits
Calls are OK after each reboot
Calls are OK after deep sleep (and calls waking the phone up)
Calls are OK after plugging in a headset and switching to the headset profile in settings >> sound
The volume up and down buttons actually WORK during a phone call!!!

Issues
Plugging IN a headsets (3.5mm headphones with mic) will not switch over correctly. Go to Settings >> Sounds and select headset.
Un plugging a headset will not auto switch back to the phones earpiece and mic. Go to settings >> Sounds and select earpiece


END EDIT

START OF ORIGINAL POST

After many hours, this is how I got Calls to a stable OK state on my PinePhonePro.

OS: DanctNIX Arch with Phosh (archlinux-pinephone-pro-phosh-20240326.img)
BootLoader: rk2aw
Carrier: USA - Patriot Mobile (T-Mobile SIM)
EG25 Firmware: Biktorgj 0.8.0
ADSP Version: 01.003

1) Fresh install of the OS on the eMMC
2) Full upgrade "sudo pacman -Syu"
3) No audio during calls
Code:
journalctl showed:
danctnix callaudiod[4807]: Card 'alsa_card.platform-rt5640-sound' lacks speaker and/or earpiece port, skipping...
"sudo pacman -S pipewire-alsa" stopped the "alsa_card" error.

4) Keep in mind, there is no pulseaudio on this version of the OS, they moved to pipewire.
5) Call audio worked, but sounded like a fright train! Extremely loud.
6) I installed "sudo pacman -S pulsemixer "
Code:
pulsemixer --list
Sink: ID: sink-117, Name: Built-in Audio Headphones, Mute: 0, Channels: 2, Volumes: ['40%', '40%'], Default
Source: ID: source-117, Name: Monitor of Built-in Audio Headphones, Mute: 0, Channels: 2, Volumes: ['100%', '100%']
Source: ID: source-118, Name: Built-in Audio Headset Microphone, Mute: 0, Channels: 2, Volumes: ['0%', '0%'], Default
Source output: ID: source-output-103, Name: GNOME Settings, Mute: 0, Channels: 1, Volumes: ['100%']
Source output: ID: source-output-104, Name: GNOME Settings, Mute: 0, Channels: 1, Volumes: ['100%']

7) I did a volume change on Built-in Audio to volumes set to 0
Code:
pulsemixer --id source-118 --change-volume -100

8) This helped until a phone reboot and new nodes were created with 100 as the volume
9) I then installed "sudo pacman -S alsa-utils" to set the mic default levels to 0
10) I ran alsamixer during a phone call to set the default mic to 0 for the internal mic.
11) I plugged in a 3.5mm headset (headphones with microphone)
12) I ran alsamixer again with the headset and set the default mic to 0 again.
13) "Freight train" sound is fix. Just leaves the echo on the other (not PinePhonePro) phone
14) The default VoiceCall.conf (danctnix) file had to many options and there was an echo...
15) I tried the VoiceCall.conf from biktorgj and I had to set the default mic back to 0 with alsamixer
16) Steps to use biktorgj VoiceCall.conf
Code:
cd /usr/share/alsa/ucm2/PinePhonePro/
#backups are good
sudo mv VoiceCall.conf VoiceCall.conf.org
sudo cp PinePhonePro.conf PinePhonePro.conf.org
sudo mv HiFi.conf HiFi.conf.org
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/VoiceCall.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/PinePhonePro.conf (NOT THIS ONE, it points to a different folder, use the default PinePhonePro.conf)
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/HiFi.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/EnableSeq.conf
sudo wget https://raw.githubusercontent.com/Biktorgj/pine64-alsa-ucm/master/ucm2/PinePhonePro/DisableSeq.conf
#backups are good
sudo cp VoiceCall.conf VoiceCall.conf.biktorgj
sudo cp HiFi.conf HiFi.conf.biktorgj
sudo cp EnableSeq.conf EnableSeq.conf.biktorgj
sudo cp DisableSeq.conf DisableSeq.conf.biktorgj

So, No "echoing" no loud feedback!
Calls are OK after each reboot
Calls are OK after deep sleep (and calls waking the phone up)
Calls are OK after plugging in a headset and switching to the headset profile in settings >> sound
EDIT: The volume up and down buttons actually WORK during a phone call!!!

I messed around with a lot settings. I am not sure the pulsemixer steps are needed...