Is there any OS that is actually working and stable? I am going down the list installing every OS but there's always a problem to be found, some more than others but none of them work enough to make the device live up to it's name - the Pine "Phone".

If anyone has had any luck with an OS please let me know. I have installed more than half the available OS's and am on the precipice of giving up.

Thanks.

Hello, what are the main differences between megi's and sunxi64 kernels, what are the functionalities advantages, privacy and security trade-offs between them?
I've been using arch with megi's kernel and would like to know more about the possible privacy and security problems regarding the wifi firmware as described here: https://linmob.net/how-about-more-libre-...ath9k-htc/

My screen bottom side has loosed its tactile function (I don't know if it's a hardware screen issue or just a bad connection of the screen). But, meanwhile, I have a problem to start my mobile because the OK button, when decrypting the device at the starting process (my device is encrypted) is very hard to touch (I should try dozens of times). I wonder if I can set:

an inversion of top/bottom sides, at mobile start, or always (when I'm in the graphical screes, auto rotate help me, there is not a major issue)

"Cancel" the bottom last centimeter of the screen.

Are there any settings file where I can modify these parameters?

At Settings > Sound I have NO output or input device so I suppose my device sound is not available...

Hi guys,
  I am developing a board to use the Ox64 for a commercial application and while mapping out the planned pin usage and creating a KiCAD part I found a mismatch between the four documents I was referencing:

• PINE64_Ox64-Schematic-202221007.pdf from the wiki.
  
• PINE64_Ox64_placement-Bottom-202221007.pdf from the wiki.
  
• BL808_DS_en_1.1(open).pdf from the wiki.
  
• Ox64 Pin Assignments spreadsheet, probably from the original announcement blog.
  

1. Pin 4 on the schematic is labelled as GPIO12 but on the bottom placement is labelled as GP21.
   
2. Pin 5 on the schematic is labelled as GPIO13 but on the bottom placement is labelled as GP31.
   
3. Pin 6 on the schematic is labelled as GPIO41 but on the bottom placement is labelled as GP14.  There is no GPIO41 pin on the BL808C datasheet.
   
4. Pin 7 on the schematic is labelled as GPIO40 but on the bottom placement is labelled as GP4.  There is no GPIO40 pin on the BL808C datasheet.
   
5. Pin 12 on the schematic is labelled as GPIO20 but on the bottom placement is labelled as GP2.
   

1. Pin 4 is actually GPIO12.
   
2. Pin 5 is actually GPIO13.
   
3. Pin 6 is possibly GPIO5.  Low confidence in this guess.
   
4. Pin 7 is possibly GPIO4.  Low confidence in this guess.
   
5. Pin 12 is actually GPIO20.
   

- Qt6 efforts continues
- Greg Goncharov created some nice wireframes.
- @felixonmars is packaging Glacier to ArchLinux.
- some strange Qt bug
- Fosdem 2023 invitation

http://nemomobile.net/pages/nemomobile-i...mber-2022/

Hi, arch/pacman/mankaro noob. When I try to upgrade dostro, software versus pacman, software update center on lower right scroll bar I am always asked to pick betwern two themes. Regardless of which I choose all stops with a pop-up window giving a conflict dependencies between pasma5 themes breTh and breath2? How to fix please? Thank you.

I'm enjoying SXMO on my new PinePhone (PPHONE-BE2). For the most part, it is working well. When I have LTE reception, calls and data work without problems. However, LTE coverage is still patchy in Germany, UMTS is disabled and 5G is unsupported on PinePhone. So whenever LTE is unavailable, the phone should use GSM and that is not working at all. I have never seen the phone registering successfully in the GSM network of my carrier. Same with the preinstalled Plasma Mobile (in Manjaro ARM I think).

Here is some data that may help with diagnosis.
* Carrier: Congstar (Germany, a brand of Telekom).
* The SIM is old (from around 2008) but GSM works in another phone.
* I flashed an open source firmware onto the modem but had the same problem before doing so.
* Below is the output of mmcli -m 0 and mmcli -m 0 --3gpp-scan --timeout 300 in a spot where I do not have LTE coverage.
* Note that 3gpp-scan finds the GSM network of O2 but not the one of my carrier.
* It also finds the LTE network of my carrier (26201 - TDG) but I think reception is too bad to connect.

Any thoughts on how to fix this? I consider ordering a new SIM. I may also switch to a different carrier, so recommendations for German carriers that work well with PinePhone would be appreciated.

Did a dist-upgrade this morning and now when I receive a MMS message mmsd-tng goes into a cycle of messages like:

Hello! I have an interest in the Pinephone Pro but I'm still curious about a few things.

1. Is the battery life really so bad that it can't last a whole day? There's no battery upgrade that allows it to last?
   
2. I imagine some may frown on the idea, but what is the possibility I can get Android 10 on it? I would idealistically like to use Android 10 as my daily driver, while...
   
3. How can I multi-boot the phone? I wish to be able to test out Linux phones and possibly learn to develop on that platform. Idealistically I'd love to have a phone with easy repairability, battery/SD card replacement, a battery that lasts ~a full day, runs Android 10 until Linux phones are comprable, and to test/mess with Linux OS's. My Pixel 3a is very good but I can't upgrade storage, film plus and I don't know how to repair it bee tv.