I used to be a tinkerer of my Android phones for long time and being an arm device I thought this would be similar. In Android I used an app called Tasker and would create a task with shell commands to change my gov and clock speeds, I guess this would be like cron jobs or similar for the Linux community out there. When I search  how to do this in Manjaro, a lot of other forums suggest to use the Manjaro Setting Manager. Though there isn't a kernel setting within this manager which makes me think it's handled differently on a non arm Manjaro dist. I tried searching the pine forums but with no success. How does one change the voltage and clock speeds of the cpus in Manjaro arm for our pb pros?

Hi everybody.
I have a problem with my pinephone manjaro ce. Recently I decided to flash the internal emmc through the sd card (jumpstart option).
I was surprised to find out that the phone doesn't recognize the sd card (checked via lsblk command), but a phone sim is detected correctly.
Has my phone a hardware fault ? Do I have to config some software option alternatively ? I'm stuck....

Thank you in advance

P.S.
Sorry for my awful english

Here's how we connect PineCone BL602 Evaluation Board to OpenOCD... For flashing and debugging RISC-V firmware

Connect PineCone BL602 to OpenOCD

From time to time my previously well paired bluetooth headphones refuse to keep a connection to my Pinephone.

No matter how many times I rebooted/upgrade, systemctl restart bluetooth, off/on bluetooth back and forth connect attempts repeatedly w/intermittently stopping of bluetooth on the phone. Still, no bluetooth connection sticking (with previously setup and working well bluetooth headphones).

When I viewed systemctl status bluetooth in terminal, I found this (MAC OUI left as is):

I installed KDE Neon on my phone and there is no sound of any kind, I checked all settings and they seem to be normal settings, I know the sound is ok in other o/s like Manjaro.

Hey all.

I just got my Pinecil.  Immediately hooked it up to PD and tested it.  I'm impressed at how quickly it heats up given the wattage I allocated to it.  (I went into advanced settings and limited it to 15 watts, mostly to compare it to a similar-sized soldering pencil I had lying around.)  I did notice one thing odd though.  I didn't use it for very long (just long enough to dip the tip in some tinning compound and clean it), but the space around the "+" button seemed to get noticeably warm.  Not burning hot, mind you, but given that the housing is made out of plastic, it got warm enough to make me wonder how hot the components underneath were getting.  Anyone else noticed this?  Should I be concerned?

Eric

Hi all,

I ordered a Pinephone 64 in September 2020 and was really excited when it arrived in November. I know the Manjaro OS and software is a work-in-progress, so I was expecting things to be a bit rough around the edges. That's completely ok.

But it has now become impossible to update the OS, even though updates are available. I'm constantly getting errors like "error: key "####################" could not be looked up remotely" and others.

I have Googled possible fixes for these errors and would be interested in trying them out, but the phone has now also started freezing up randomly, which makes it impossible to work at all. I'll be in the middle of executing some command in the terminal and the phone will simply stop responding. The only way to get it to work again is by resetting it (pressing the power button for 5 seconds). 

I have an MCSA certification, but I'm still a novice with Linux, and my Linux experience has been limited to Ubuntu up till now. Under these circumstances, I would say it's time to completely re-install the OS from scratch. However, I have been unable to find a step-by-step guide for installing the OS on the Pinephone specifically. 

I basically have two questions:

1. Is it ok for me to use this guide? https://forum.pine64.org/showthread.php?tid=10403 It was written for the Pinebook Pro, but it seems to be the closest thing available. Or is there a better guide available for the Pinephone?
   
2. Manjaro does not seem to be an OS that was created specifically for phones. If I re-install the OS from scratch, will this delete custom settings in the Pinephone that were implemented at the factory and are necessary to make the phone work? If so, where do I find documentation to re-create those settings after installation?
   

Pretty much what the title says.

Today my Manjaro CE Pinephone showed a bevy of software updates waiting to install. I hit install and checked later and it looked like it was working. When I left the house I found out my mobile data is dead.

I put in a Sailfish OS SD Card, booted, and mobile data works great. (so its not the sim card).

Pulled the SD card and booted back to Manjaro, and: no mobile data.

So clearly this update killed mobile data for me.

Any suggestions on how to fix this?

I'm not a Manjaro expert, but I did run Vector (Slackware) for years, if anybody has any ideas on what to look for.

I'm actually suspecting something like an insmod statement is missing or something. Thoughts?

Any help would be appreciated.

Hello Pine community, I'm a linux newbie and was wondering if there are certain mobile Linux OSes that are more secure than others?  From reading various posts on reddit I've come across some saying Ubuntu Touch is secure because of the apps being isolated from each other, and being able to choose app permissions. Is that not the case for other mobile OSes?  It looks like Mobian is the preferred OS for Pinephone for many people right now because of stability/usability.  How is it as far as security?   I'm trying to learn Linux for privacy and security reasons, and wanting to get away from the Apple/Google duopoly and am happy to support the free/libre philosophy.  Can you explain to me how each mobile distro differs in security, or point to resources I can dive into?  Thank you

Hello all,

This week has actually been a pretty exciting week for MMS support on the Pinephone! I wanted to update you all (and hopefully get some more help on this):

- I found a lot of useful information related to the MMS standard, and documented my findings here: https://source.puri.sm/Librem5/chatty/-/...ote_132167

- I was also have to find an (admittedly hacky) Proof of Concept to send MMS: https://source.puri.sm/Librem5/chatty/-/...ote_132222
      - This compliments the proof of concept I found to recieve MMS.

- Mr. Kyle Evans posted on the chatty thread that he has been working on integrating support of mmsd into purple-mm-sms and modem manager: https://source.puri.sm/Librem5/purple-mm.../issues/20

- He And Mr. Parthiv S showed how to send an MMS via mmsd and Modem Manager https://source.puri.sm/Librem5/purple-mm...ote_132496 !

- Mr. Kyle Evans also indicated that his repository has the modifications needed to integrated purple-mm-sms with mmsd to recieve MMS ( https://source.puri.sm/Librem5/purple-mm.../issues/20 ). The repositories are here:

https://source.puri.sm/fuzzy7k/mmsd

https://source.puri.sm/fuzzy7k/purple-mm.../tree/mmsd

So what is left?

- If your carrier has a seperate APN for MMS and Mobile Data, Modem Manager needs to integrate support for that: https://gitlab.freedesktop.org/mobile-br...ote_721821 
- Modem Manager Also lacks support for Transfer Route MT Messages ( https://gitlab.freedesktop.org/mobile-br...issues/257 ), which some carriers use for SMS WAP Notifications. This means in its current state, you will not be able to recieve MMS on your carrier.
- If your carrier has a combined APN for MMS and Mobile Data and is not affected by the Transfer Route ME Message issue, Modem Manager needs no modifications for you to send/recieve MMS.

- There likely is still integration polishing needed for mmsd, purple-mm-sms, and modem manager.

- Chatty's UI also needs to be updated to support these integrations.

Help and/or testing is welcome on any of these!

It may be good to log which carriers are affected by the two issues with modem manager as well. So far:
- T-Mobile USA has been confirmed to work sending/recieving MMS with Modem Manager in its current state.
- Verizon seems to use Transfer Route MT Messages for SMS WAP notifications, so it will likely not be able to recieve MMS without the Modem Manager issue 257 being solved.

EDIT: I independently confirmed that the forkd mmsd works to send MMS! I tested text, pictures, and group chat.

If there are folks that can/want to help with this, the matrix room to discuss it is here:
https://matrix.to/#/!zaQzHCRfyTXoMIqcxq:talk.puri.sm