So, here it is.
Manjaro Phosh, 3G_RAM/32GB_STORAGE PinePhone board.
After discovering that my pinephone stopped charging, I tore it down to see the main diode on the usb-c board blew. Replaced it and started charging. But now I can not keep convergence active on any external display using, a NexDock lapdock(usb-c to usb-c alt mode), an Anker HDMI dock, or the official pinephone dock. The external display just flickers and will not stabilize. A quick connect, disconnect, repeat issue. I thought I may have fixed it by tearing it down and unplug, then reapply the ribbon cable on the usb-c board and main board.
External displays worked again, or so i thought. Cut to class today. screen kept flickering, so I switched out my SIM card to my backup android phone and tried to dock it again, it worked.
The thing that baffles me is this, any other peripheral works without fail, (ie flash drive, mouse, keyboard)
After trying this multiple times, using an external display will ONLY work without the SIM card inserted.
I switched off the WLAN DIP, SIM inserted, wont work. WLAN DIP switched on, no SIM, convergence works flawlessly.
Should I just get a new mainboard, as I am thinking the diode didn't blow soon enough before some extra voltage screwed up the main board.
There are other threads on modem firmware. However, this post is specifically targeting the use of the gnome-firmware application to update the modem firmware.
I recently installed the gnome-firmware package on mobian. As far as I know gnome-firmware is not installed by default on mobian. I wonder if it has been tested under mobian. When I opened it three devices were listed for possible updating, only the Qualcomm modem actually had an update available. The available release is designated 0.6.1, offered by Biktorgj. It is also designated as a Downgrade (maybe due to a different versioning system than Qualcomm).
I'd like to know if anyone has used gnome-firmware to install this update and if they found the process to be without issues. Did the update improve the functionality of the modem? What improvements were noticeable.
Has anyone been able to restore the original modem firmware using gnome-firmware?
I do a lot of work on Wireshark, but mainly on the dissector side (eg, 802.11 dissector stuff these days.)
I am thinking of exploring the possibility of using Wireshark on a phone form-factor device and the PinePhone Pro looks like it might be usable.
However, what sort of attachments would I need (keyboard, monitor, external NVMe storage) and is it possible to build with cmake and gcc etc on such a device.
I guess the flash storage is going to be much slower than NVMe ... maybe a cross development environment would be better. Ie, build on Ubuntu targeting ARM, and then install on the PinePhone Pro.
I have a PBP (2021 batch) and screwed up the original Manjaro KDE eMMC image with some combination of cups and display resolution mischief. I have been using Armbian successfully from a microSD card but want to fix my eMMC boot. The only image of Majaro that targets eMMC specifically is this one, but it's way out of date. I have since tried to update packages etc but am running into pretty difficult challenges getting things updated to a point where I could update the OS to a current version (namely I can't access the current mirror list). This is preventing me from using the manjaro-arm-installer package that would help update OS. Has anyone else run into this issue and solved it? Or is there another OS with a current eMMC version?
Audio volume and its indicator on the screen goes the opposite direction of the up or down buttons when they are pressed. Repeating the button press eventually fixes the problem temporarily until the desired volume is reached. Do you have this problem?
i have the software application running that states there are updates. but it just does not install any of them. when i click on "install" or "upgrade" or what that button shows, it shortly says "cancel" and thats it, nothing else happens.
i thought i could do that manually with a terminal like apk update, but i dont have any root password
so how can i install updates without all the time reinstalling the complete OS?
For 2 years I’ve been running Debian 10 Buster on my PBP, installed, with encryption, on the eMMC with Daniel Thompson’s awesome installer (thank you Daniel!!). The PBP is my daily driver.
Last week I tried upgrading to Debian 11 Bullseye following the instructions on the Debian website (https://www.debian.org/releases/bullseye...de-process). All seemed to go smoothly until it came to rebooting, which unfortunately only produced a green power LED and a black screen.
I tried installing Tow-Boot, hoping I could salvage something with that or otherwise do a clean install of Debian 11. Unfortunately booting from the Tow-Boot installer SD card fails in the same way: Only the power LED lights, otherwise nothing happens. I tried 2 different SD cards (both Kingston 32 GB Class 10 U1 though) and wrote the spi.installer.img to the cards using both dd and the disks utility.
I can boot Bullseye from a similar SD (previously created with Daniel Thompsons installer) though.
I recorded the upgrade with “script” as per 4.4.1 in the Debian upgrade instructions but don’t really know what to look for.
I’ve been a linux user for around 15 years, happy to use the command line for simple things and to fix problems with instructions found online but otherwise very much a GUI person. I can’t really find any information relating to my 2 problems so I’m more than a bit out of my depth here.
Is there anyone with an idea what I’m doing wrong?
My Pinephone (convergence) has horizontal pinstripe lines throughout the screen. I suspect it has to do with the resolution being set at 360x720. I can't find an xrandr mode that will let it be set at 720x1440.
I'm running Manjaro Phosh.
In case this has anything to do with the problem, I do not have a ~/.monitors.xml or ~/.config/monitors.xml file. If it's supposed to be there, it's gone.
Was trying to use Spot to listen to my music, and for the longest time I thought there was some sort of driver issue... Wasn't really sure, but the audio would get really choppy and laggy whenever I tried to play on the speaker, so I just assumed that something (library, pipewire, IDK...) was broke, but the choppiness seemed to by a CPU thing, so I got the serendipitous idea to check it at low volume, and what do ya know, it works great! So I am not sure if there are still fixes for this coming down the pipe, but to anyone who might be in my position and think it is broke, it isn't! Just the speaker seemingly draws too much current from the CPU.