So I got a problem with my modem, the phone will not connect to cellular service and it's not detected by the software. This has been an issue from day 1 with the phone and its a Manjaro CE 2GB version (I also have a 3GB version that works just fine). Tried opening an issue with the company but there response has been lack-luster and i have given up with them.
-- carrier is AT&T
-- Yes the switches are are on tried cycling on/off several times and verified the switch is good
-- using the sim card that works in my 3GB phone
-- manually entering in APN does nothing
-- phone has never showed missing sim card icon with or without sim card installed
-- confirmed coaxial cable is plugged in fully, even swapped out for the one on the 3GB phone
-- physically main board and solder pads look good
-- running the auto test it will hang up when testing the modem is i cancel the test then re-launch it the modem says it passes. Going to the debug button will sometimes not show anything, sometimes will be some info always missing IMSI though, it will also never read the sim card. if it does bring up modem info there will barely be a signal.
-- WiFi always work, I have no use for Bluetooth so i never tested but seems to be ok

-- I get this when i run dmesg;

dmesg | grep -i modem
modem-power serial-0: the modem didn't report powerup success in time

forcibly cutting off power, data loss may occur.

power up failed


-- no modem is listed when i run lsusb

-- mmcli -m any
errror: couldn't find modem

-- nmcli c
will list wifi and anbox

-- sudo bash -c “pinephone-modem-stop.sh && pinephone-modem-start.sh && pinephone-modem-setup.sh”
will do nothing and still no modem listed with lsusb, mmcli, etc.

-- can not get into EDL mode to update firmware, after jumping test points on the board no modem is listed with lsusb still! :@ (treied many times with different jumpers)
-- when i run the firmware from @Biktorgj
quectel_eg25_recovery
./qfirehose -f ./
Quectel module not found
qfirehose.c main 324 fail


--I have tried a lot of different distros both from the multi-boot and eMMC install with jumpdrive(manjaro plasma, lomiri, and phosh, Mobian, Arch, Postmarket OS, Sxmo, Sailfish, etc.)

I have been off and on dealing with this issue for months now and have kind of reached my limit with this phone, please any help will be much appreciated. I have not seen this particular issue in the forums either and maybe I have the one dud out there. :( 

Cheers,
al_x

Am I becoming crazy ?
In Armbian, the white led seems blinking like a heart. But it also accelerate according to the load as if it is running ! That’s super cool !

Hello everyone,
I'm sorry if this is a duplicate, I couldn't find any thread that mentions this.
On the page for the Pinebook Pro from pine64.org
https://www.pine64.org/pinebook-pro/
the wiki button links to https://wiki.pine64.org/index.php/Pinebook_Pro_Main_Page, but should link to https://wiki.pine64.org/wiki/Pinebook_Pro

this should be fixed by changing line 495 of the HTML source code for the page

Hello all,
 I just made a fatal mistake  ! Here is the story.
I power up my rockpro64 boards with a ATX psu with a EPS12V to 8 DC barrel connectors. Until now no major problems. Then I decided to use a server power unit (which is common in the miner rigs domain why not use it for my boards ?) with a special adapter for PCIE (to power GPU cards) ... why not ?
   

The connectors are rather alike and I naively think that they are the same since they have the same function. Indeed we can plug them together.
When  I switched on ... sparks and flames ! Then I realized how stupid it was. The +12V and ground are inverted. It was simple though : 1st principle : connect the black wire with the black wire. I did not check, over confidence.

So RIP my dear Rockpro64   
"By chance" I just plugged one.

*If you are sensible do not watch the following pictures*
       

Is there a way to replace the components ?

Would it be possible to have the phone ecrypt when you hold down the power button instead of locking the phone.  I have a encypted os Mobian

Hey everyone, I've just posted this on Keysmith's issues page at https://invent.kde.org/utilities/keysmith/-/issues but I thought I'd crosspost here as I am in some dire straits.

I got my KDE Plasma CE (Manjaro) Pinephone yesterday and began the process of putting my details in.

I put some 2FA accounts and keys into Keysmith and it worked perfectly. I had to unregister my other device to get a new TOTP key, so all of my keys are stored on the Pinephone in Keysmith. After using it last night, everything ran fine. Perhaps I was a bit foolish to put this data into an experimental phone, but of all things I didn't expect the 2FA app to fail, and initially it was running perfectly.

I didn't do much with it last night except a system update. When I opened it again this afternoon, I get a blank screen. I have no idea what changed.

When opened from the terminal, it gives me an error message saying "org.kde.keysmith.accounts.actions: Unable to unlock storage:failed to request password for accounts".

Directly before that is a message saying "file://usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.breeze.AbstractApplicationHeader.qml:62: Type Error: Cannot read property 'header' of null"

I don't know enough about KDE development to hazard a guess, but could it be that something in the Kirigami interface isn't working, and is blocking the usual password dialog? This feels like a very small software error that can be solved by deleting a cache or changing a settings file, but I have no idea what I need to do.

All I really want is to be able to get access to my 2FA tokens! I need them to log in to my email and banking.

Hi,

Sorry if this isn't the right place for this, I'm a first time poster. Just let me know if I need to move it, and I will do so happily.

I'm trying to install a new instance of an OS over the original OS on my Pinebook Pro using an SD card with Debian Desktop Community Build Image [microSD to eMMC] by mrfixit2001 loaded to it via balenaEtcher. I think this is the same OS currently on it. 

I seem to have broken something a while ago while experimenting with the OS, so I need to repair the install. Part of the issue is that the login isn't functioning properly. I've done research and it seems using a fresh install is the best way to fix it.

I've managed to get the live image to run on the laptop, but I'm not sure what to do next. I've installed linux on old Windows machines before and none of the normal steps seem to apply in this situation. 

Any help is appreciated!

Hello,

Firstly, sorry if this isn't where I should post this, I'm a first time poster. Just let me know and I'll move it.

I''m trying to use an SD of the Debian Desktop Community Build Image [microSD to eMMC] (which is the same OS as my pinebook pro laptop) to install a new OS over the OS on my pinebook. I have been able to access the live boot on the SD card, but don't know where to go from here. I have installed other linux distros over other OSs in the past using bootable USBs before, but the procedure for this seems to be different. None of the normal prompts are appearing.

So far I've updated and upgraded. At this point, I'm not sure whether the changes I've made are applying only to the SD card or to the actual hard drive, I suspect just the SD card.

Any help with installing an OS to the actual laptop is appreciated!

I've got a DisplayLink-based (DL-41xx) USB display working with my Pine64, although very slowly (glxgears 1fps...)
The key part is updating to Debian unstable (to get the DRI driver), and cross-compile a libevdi.so using the source provided in /opt/displaylink. I used evdi-dkms from the repo.
Sadly, due to the poor performance, it seems like that it's not very practical to use...

An ICM file can be a simple lookup table or an algorithm.  They're used for correcting colors, in this case of the display, so if you're going to be editing photographs the display is accurate.  I've used them with xcalib before on other computers quite successfully. 

I do have an old Color Munki which I've never used under Linux so maybe I could make one.  They're usually supplied by a display manufacturer.  The colors seem pretty good but a human eye isn't a reliable judge.