Hi folks,

It seems some of us are having issues with the cellular network in our pinephones and I thought it would be useful if we can get a list of the combinations to try to look for what is the culprit

HTH

haveing a really hard time too get the mobiel internet working
 some have any tiips or  picure how too sett it up

Hello everone,

I just booted postmarketOS from my SD card and logged into it over SSH. I noticed that

Hi there, I recently received my PinePhone, and while I'm excited about the project, the phone itself is not totally usable, yet. I get that this has been established, while I admit I didn't read the fine print, my old phone still works for now and my PinePhone is something I'll ease into.

My questions are as follows:

1. Is it safe to assume my hardware will not need to be upgraded? I'm assuming all the updates from here on out will be software, and sometime — maybe in a few months, maybe a year — I'll be able to use my PinePhone as my primary phone. 
   
2. Realistically, when do you think the PinePhone will be more or less ready for prime time? Are we thinking 6 months? A year? Just curious. sorry if this has been addressed elsewhere.
   
3. If I'm going to dual boot, what other OS is the farthest along? I read that the next sound of PinePhones will ship with Postmarket OS, but PinePhone's position seems to be that UBports is the most stable right now. Someone on the forum said Mobian is working best for them.
   
4. Is there any reason not to run the bleeding-edge repos? At this point, if the phone is semi non-functional anyway, It seems the fastest way to get stability would be to move to the dev channel.
   

Got my first PBP a couple weeks ago - Manjaro KDE ... did the steps in the wiki for it:

https://wiki.pine64.org/index.php?title=...KDE_system


Everything was running fine..... until:  I got the debian image onto SD card and booted it.   The screen was immediately over bright, flickering rapidly & steadily, and had a vignette effect (darker soft band around the outer edges).    I booted Debian a couple more times and observed the same.   then I removed microSD and booted back to manjaro KDE and the same video effect persists! 

So, what do I do now?   did booting Debian jack the firmware or something?   Is this a coincidental manufacturers defect?

Is it possible my pinebook pro suffers from a similar issue as mentioned in https://forum.pine64.org/showthread.php?tid=7387 ?

When I try to compile large projects (using Manjaro), i.e. GHC (Haskell Compiler), I suffer from segfaults and similar errors. Most of the time (if the previous object files weren't broken), just restarting helps.

I already extended the cooling pads. Using make -j 6 yields errors quicker, but single thread compiling doesn't fully fix the issue. Using different govenors yields the same observation - using powersave instead of the performance ones does lead to errors later, but don't fully fix them.

Anyone else seeing the same? Is there a way to limit the RAM clock on the pinebook pro?

Best regards, Markus

sir,
i am working on wasp OS for pinetime want to check out the pin config of all protocols like spi, i2c, vibration motor pin, button pins etc. where can i find that file. i have been searching all day but didn't got. Can you help me out in this.

thankyou so much.

I've got CRUST installed on my BraveHeart with a modern Megous kernel, but I can't get the device to wake on calls/texts.
Apparently it's supposed to work on BraveHeart now.

What do I have to do in order to get my phone to wake on ring or text? Set some parameters in /sys/power that I don't know about?
I'm just using a vanilla Fedora 32 install with XFCE and the Librem5 "Calls" app for the phone functionality.

I tried to enable cellular data on my UBports Edition. In stable (OTA-03 eMMC)as well as developement (Version 58 build number 2020-06-25/2 on SD card) I cannot switch cellular data on. The switch is a darker grey in the menu and seems to not let me activate it. I entered APN details myself. I tried it with two different SIM cards of different networks.

Am I missing a step? Any suggestions where my problem comes from?

I just received my PINE64 Community Edition: UBports Limited Edition Linux today. And it seems it got some issues:

1) It seems the power on my laptop's USB port is NOT powerful enough to power PINE64 up, PINE64 always restart after I see the PINE64 logo.
2) Therefore, I tried to power PINE64 up using USB power adaptor with the delivered Type C cable. Now, PINE64 boots into Ubuntu 16.04. However, it's NOT changing at all. the Battery Charge Level sticked to 0%, no matter how many hours I left PINE64 for charging. As long as I disconnect the Type C cable, PINE64 is out of power and shut down right away.
3) What'e even more weird. In Settings->Battery, there is even choices for Wi-Fi and Bluetooth? What's that for?
4) And in Settings->Wi-Fi, there is ONLY 1 option: Previous networks , PINE64 won't be able to show Wireless network around. 

So, in sum: PINE64 ALWAYS stick to batter charge 0%, and Wi-Fi doesn't search wireless network at all.

Did anybody have those issue as well? Is there a way to let me reflash Ubuntu onto PINE64 from scratch ?? Say, how can I flash Ubuntu 20.04 onto PINE64 ?


Thank you very much. Looking foward to have some fun on PINE64.

Pei