Not much concrete information about activating SIM cards. This is how I got lucky and got things to work without too much trouble. I can make and receive calls, send and receive texts, and have 4G data with PMOS. Hope this helps.

1. Bought a Tracfone SIM and plan kit from eBay. I chose the T-Mobile network because Pinephone supports 3 of its LTE bands (2, 4, 12).
   
2. Installed SIM on Pinephone and tried to activate on Tracfone website, but got an error at the IMEI information step.
   
3. Installed SIM on Moto G5S+ and tried to activate, but got the same error.
   
4. Reinstalled SIM on Pinephone and booted.
   
5. Called customer support and successfully activated the SIM through their automated system. It never asked for IMEI information. I never even spoke to an actual human being.
   
6. Rebooted phone.
   
7. Profit.
   

What are the chances of getting a line64 mini arm based computer similar to Apple mini with a arm linux distro for a OS?

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: ubports/2020-09-03-TMobile

Conclusion: This OS is not ready for the device to become a daily driver.

Notes: Still open to the idea that the camera button is to reverse the image not switch to the 'selfie camera' if anyone can confirm either way I would appreciate it. Although there were 4 builds between yesterday and today, I didn't notice any improvements directly. Still no outbound SMS on 3g. Still no outbound calls on 4g (volte). Just to note: This seems like an issue with a couple of providers specifically, I am aware that 4G calling (VOLTE) is different between carriers. I make this note because it seems to be debated. If anyone can give help troubleshoot this issue we can pin information on the tickets listed below. Failed 4G calls still kills call audio.

Issues:
Failed outbound 4G calls kills call audio.
Unable to send 3G SMS Since Dev-158
4G outbound calls broken.
Phone gets stuck in a weird lock state when spamming power button.

PostmarketOS convergence edition phone. Software fully up to date. Plugging in the dock shuts off the screen immediately, no matter what is in (or not in) the dock, even if it's empty. Unplugging it immediately restores the display.

When plugging in a basic 4-port USB3 to type C hub I had laying around, the screen dims significantly. Thinking perhaps the screen shuts off when power draw is too high I plugged an LED keyboard into that USB hub, but screen brightness did not change, the keyboard just lit for a moment then shut off.

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: [/url]mobian/09-03-2020-Verizon.html
               mobian/09-03-2020-TMobile.html[url=https://tosstalk.com/pinephone/mobian/2020-08-28-TMobile.html]

[b]Conclusion: [/b]OS is not Ready for pinephone to be daily driver.


Notes: The Microphone is still really sensitive. The audio out quality is suffering. Camera still super laggy. Boot time when up to 34 seconds. The UI seems much more glitchy. Its less smooth and apps take forever to open.

I have a Pinebook (not Pro), bought in March. Last week I updated to the current Manjaro-ARM, using wifi to connect to my router. The next day wifi did not work. No access points were visible. The command 'nmcli device wifi' told me that wifi was enabled. How do I find out whether the wifi chip is broken or has simply been disabled (accidentally?) by a privacy switch (if there is one)?

I know the pinephones camera is not fully functional yet. But since i work with cameras on a regupar basis, i figured i challenge myself and try to get some worthy pics with it. These two were my first attempts. I was mainly trying to figure out where the camera's focus point is. The pics were edited in darktable. If you guys get any cool shots, i would love to see.

Attached Files

  20200517_151002.jpg (Size: 292.77 KB / Downloads: 638)
  IMG_00000008.jpg (Size: 466.31 KB / Downloads: 610)

This is the second time I have installed mobian on the eMMc of my Pinephone UBPorts Edition.

The first time I changed the password from the default "1234" using the terminal emulator with the
command "sudo passwd" and it worked.

However, after making some annoying changes I couldnt revert, I decided to reinstall everything and now,
when I try to change the password in the terminal emulator using the same command "sudo passwd", it says:

passwd: password updated successfully

But, when I lock the screen and then attempt to unlock it with the new password. It doesnt work.
When I try with the default "1234" password it works like if I had never changed it "successfully".

Not sure what is happening or what Im doing wrong, maybe Im just tired. Any ideas?

Can someone confirm that he has Ubuntu Touch installed on the Pinephone and can make phonecalls with it?

https://www.reddit.com/r/pinephone/comme...t_working/

Several years ago(2013ish) when the (folded project)Neo900 http://neo900.org/ was taking shape I requested hardware switches on all radio transmitters and a POCSAG pager module on the board.  The desire for an optional rx only radio silent un-trackable phone mode evolved into the Neo900's hacker interface where a developmental POCSAG pager module could connect in the future once the phone was available.  I had a few interactions with RMS and had an email thread with him where even the 'man who would not own a cell phone' admitted that if his conditions were met he might consider such a phone as his first mobile device.

The head of the Neo900 project, JoergRW, who's work you all probably know from the OpenMokos many of us have played with, sadly ran out of health and had to fold the ambitious project.

I want to see what can be done to get a POCSAG pager module and required software working with my pinephone.

The idea is that POCSAG paging service is still reasonably universal for medical and emergency services and is broadcast from FM broadcast, 400mhz, or 900mhz towers, these pages are passively received by the pager receiver.  If using a dedicated chip we were already getting 30 days or more form a AA alkaline cell so power budget is minuscule I believe most hardware comms are simple serial.

Use case:
If I were to soft deactivate my telephony modem I could be radio silent and untrackable, should I be in what I consider a safe location and wish to make a call it is simple for me to automatically soft activate my modem as part of the dialing process script and also soft deactivate when I complete my call.  More interesting to us all is that as long as I have a subscription to a paging service I can also receive calls under most conditions, often with better coverage than some mobile telephony providers, by receiving a page with a caller-ID which can be called back quickly with an answer button in the paging rx app.  The paging service can also often receive SMS and emails forwarding them to the user, with some middleware these could even be encrypted and decrypted at the phone removing another privacy invasion.
The always on nature of a mobile telephony device is used to track our every move, I want us here to break this cycle.

I believe that one-way paging, wireless peer-to-peer fidonet-like programs like Briar, consideration of integrated or tethered UHF radio tx/rx for amateur radio or unlicensed bands, and perhaps even use of fixed or mobile one/two way satellite data services can free us from many of the tracking and anti-user technologies which have grown up with cellular and internet technologies since the 90s.