I thought for sure that there was something wrong with ofono.  I even compiled ofono's master branch from source and learned how to create a pkgbuild, then eventually post my attempt on the AUR.  Apparently, they didn't like that very much.  However, I managed to get through it.  However, this approach led to a phone that would not make calls.  So, I reinstalled the original ofono and went back to the drawing board.

I started chasing down a few items online, including a few interesting items that turned out to not be too relevant.  I began to look at the network interfaces and noticed how wwan0 never had a link and only had an ipv6 address.  I ventured a guess that my service would be on ipv4 and couldn't find a good way to obtain or renew a lease.  I downloaded udhcpd from the AUR and ran it.  It spit out an ipv4 address along with DNS servers!  Everything went sideways after that and I thought I broke the phone.  However, with a few restarts I was back to the business of trying to get my mobile data working.

I disabled NetworkManager and enabled dhcpcd instead.  I noticed that wwan0 had an ipv4 address, but still no Internet or calls.  I went back to NetworkManager to keep things as close to default as I could.

Through more research, I stumbled across this post on the Manjaro gitlab for the Plasma Mobile Pinephone.  I was struggling with the same issue.  It just happens to be the case that my modem was on and registered while my wi-fi was off when I tried the following command:

Hello everyone!

I'm trying to work out why my PBP won't power on/boot anymore.

I'm at the stage where I've disconnected everything from the main board and using the bypass rather than battery.

If I power it through the barrel port, nothing seems to happen. CPU remains cold even if I leave it plugged in for a while. Hitting the 'reset' button also seems to do nothing.

What daughter boards/peripherals need to be connected for the main board to power/boot? For example, do I need to have the keyboard connected for it to boot?

Thanks

PS At present I can't test any voltages, currents etc until Monday evening because my fluke is at work. I might even have to wait until Thursday because of recent COVID19 lockdowns being imposed.

Model: Community Edition: KDE Plasma Mobile 2GB Ram

I'm currently waiting to hear back from support for an issue I'm having with my phone, in the mean time I was looking into this method to possibly fix it by triggering the device to boot into FEL mode.

https://linux-sunxi.org/FEL

These are the instructions I'm attempting to follow, under the section "triggering FEL mode" I don't believe my model has a special button unless someone can tell me? I have a reset button on the back but I believe that only hard boots the device. The only physical buttons I have on the sides of the phone is a volume up and down and a power button, I was hoping I could trigger it "By holding a standard button" as the instructions said where it explains by pressing a certain button combination on the device itself you could activate this mode. I've tried the directions with volume up and down and it doesn't seem to be working.

I've already downloaded and built "Sunxi-tools" on my distro to be able to use for the next step when the phone is recognized, the directions says to know if I've booted into FEL mode successfully I should see a new device appear with the `lsusb` command. Will the USB-C to USB-A cable that came in the box to charge my phone work with these directions?

Without going the serial cable route, does anyone know how I could boot into FEL mode with my specific model? If I was able to get the device to recognize on my distro then I could flash an image to the emmc directly?

Thank you in advance anyone willing to try and help me with this

Using my wireless provider, I have been unable to use mobile networking with certain OSes, particularly Mobian, Arch, pmOS. 
I have been able to surf the web and receive updates using oddball multiboot options such as Sailfish, Luna OS, and UBPorts.
This is consistent and I have demonstrated it for several months, configuring each accordingly with APN names. There is simply no way to get connected under these distros, no incoming data transfer after connectivity is established.

What is the difference?

Have  successfully used megapixels in the past.  Tried taking a photo today and experienced the following failure symptoms:
1.  megapixels launches normally, with normal viewfinder performance
2.  after clicking the shutter button, the spinner indicator never stops spinning (even after several minutes)
2a.  Other megapixel buttons (settings, folders, etc.) respond normally
2b.  /tmp/megapixels.set_of_random_chars folder created; however, is empty
3.  i close megapixels normally
4.  re-opening megapixels repeats step 1
5.  after clicking the shutter button, megapixels quickly closes itself
5a. /tmp/megapixels.another_set_of_random_chars folder created.  Contains single 59 kB file 0.dng.
6.  Steps 5 and 6 repeat until rebooting pmos CE pinephone, running pmos phosh.  After which steps 1 through 3 behavior occurs, and then 4 through 6.
Read a post that a debian libtiff update recently broke megapixels; so, updated my version to the latest on pmos repo, 0.14.0.  Issue repeated.
Has anyone else had this problem, and know a fix?
Thanks.

My Pinecil was chewed on by my dog and he managed to break the case and one of the small copper tabs on the inside that holds the tip in place and makes electrical contact with the board. I went to the Pine store and bought a new case and some other goodies (soldering tips, a case for my PinePhone, a dev kit for the pine watch) but I cannot find any where to purchase these copper contacts. 

If anyone from Pine is on these forums can you please point me in the direction of where other parts may be found? I would gladly purchase the needed pieces from the store but nothing is listed online other than the case and accessory tips.

Attached Files

Thumbnail(s)
   

I'm having troubles installing Telegram on archlinux-pinephone-phosh-20210124.
In Chats\Preferences when I tap Telegram the phone reboots almost always. If I can add my telegram user ID, I've no clue about the Telegram password required.

If I try to install telegram Desktop, the phone remain stuck in Pending Installation.
Any idea on how to solve these issues?

I'm new to Linux despite I'm an old (and retired) system engineer with experience about hp-ux.
Thanks

I checked the wiki and it said for Ubuntu touch, hold the power button until the phone shuts down and then hold it again until the LED lights up. I did this but it just have me the red LED again.

I'm not sure what to do. My OS is on the EMMC and I don't have it backed up. I can't SSH into the phone either.

Hi all!

Proycon (a fellow co-maintainer of sxmo) posted on irc a link to this subforum. Unfortunately, the maintainers of sxmo had no idea that this subforum even existed! There exist a number of very active official forums for sxmo users including:

A bug tracker: https://todo.sr.ht/~mil/sxmo-tickets

A mailing list for discussion and patches: https://lists.sr.ht/~mil/sxmo-devel

An irc channel for end user help and general discussion: #sxmo on freenode.

The maintainers of sxmo and other experienced sxmo users are active on all these channels!

Thanks for all the love you have been showing sxmo!

Hi

Is h264 hardware encoding available on the pinephone? I looked at the status of Cedrus driver and it seems to me that only hardware decoding is working not encoding.


Am I wrong?

Thanks