I cannot fix my dependancy issues.

For context I updated my phone, when it asked to replace dependancies I hit yes and all was well until maybe 3 updates later when it began asking for dependancy switches again and now it won't work and claims there is a dependancy conflict.

What must I do? reflash the OS? there has to be another way right?

I got my PP keyboard when they first launched and within about 2 months it stopped charging my phone. I've shimmed it, changed kernels, changed OS's and did all the troubleshooting steps found on Megis website and the only conclusion I can come up with is that the charging chip is fried. 

I can check the keyboard battery with UPower and it shows 100% but no matter how good/bad of a charger I connect to it, the power never gets to my phone. The good news is, I can type on it though. 

So my question is, since there is no working connection to the charging chip, would it be safe to charge the phone directly while it is connected to the keyboard?

My experience with the pinetab2 has been very good.  I was lucky to have a wifi dongle that worked.  I've kept the Danctnix OS updated via the command line.  I would like to backup my eMMC, but I haven't found a Jumpdrive release for the pinetab2, only the pinetab at https://github.com/dreemurrs-embedded/Ju.../releases/.  Am I missing something here?

01-17-2024
I tried adamz's "noob friendly" backup procedure for the Pinebook pro:

1.Get a MicroSD card the same size as your eMMC, and insert it into the PineBook Pro

2.In Terminal, run: lsblk

3.Figure out which disk is the one you want to back up and which one is the one you want to back up to.

4.In Terminal, run: dd if=/dev/mmcblk1 of=/dev/mmcblk0 status=progress
(where the first one (if=) is the name of the drive you want to copy, and the 2nd one (of=) is the name of the drive you want to copy to.)

5.When finished, reboot Pinebook Pro with microSD card inserted and confirm that it boots to a copy of your eMMC's drive.

6.Keep MicroSD card as backup, or create an image of it on another hard drive in another computer.

Everything seemed to copy fine, except the card is not bootable. Also, I wondered about making a backup on a system in use as I've read some posts that don't recommend it.

I've been searching for a VoIP app that works well on Pinephone, and so far, the only one that appears to be useful is the default app, Gnome Calls. However, I've encountered an issue with this app where it functions fine for making outgoing calls but fails to work for incoming calls. tunnel rush

Upon capturing with tcpdump, I've noticed that the app maintains registration as long as the phone has an internet connection. However, when there is a temporary disruption in the internet connection followed by its restoration, the app fails to re-register. Even toggling the app's UI on and off (with the process running in the background) doesn't resolve the issue. To re-establish registration, I either need to make an outgoing call or disable and re-enable the VoIP account. This workaround works until the next internet outage occurs.

I'm curious if anyone has experience using a VoIP app with Pinephone, running either Arch or Postmarket OS, that consistently maintains SIP registration and reliably handles incoming VoIP calls.

How is gnome mobile working on pmos? Already stable like phosh?

I saw an interesting post on mastodon this morning:

https://fosstodon.org/@danctnix/111701823196412037

It sounds like progress on the wifi driver, though I don't know what the near-term implications might be for end-users.

I get the error named in "subject" above when trying to play a .mp4 file with the preinstalled video player.

Though I can use Clapper to watch these files, I'd like to learn and understand, what the problem here is. Is it app related or is it an OS issue?
Maybe someone can give me a short explanation?

Thanks!

Has anybody else noticed SIGNAL make it very hard to install and run there app unless its on an android or IOS device?

The likely reasons for this is they are collecting fingerprint data on o devices...

For example
ts very difficult to install SIGNAL Desktop unless u scan the QR code from your phone - IE a camera is needed and this also links your phone device fingerprint to your desktop signal.

Signal could easily allow us to use an SMS or call Verification, but suspiciously, they do not.

1) Are there any other ways to setup Signal or Signal desktop without them secretly collecting our device data?
2) Any non-Signal alternatives



I managed to convince 13 of my friends to use Signal, I can easily convince them the app is compromised and get them to switch to another app.

I’ve been at this for days now and I think it’s safe to say that despite the number of detailed walkthroughs and guides, I’m still unable to get this thing figured out.

Some context: 
PinePhone Pro w/ RE button, purchased Dec 2023. It was loaded with TowBoot, rk2aw and SailfishOS.

What have I done: 
So, I believe my attempt to flash a Kali image to the eMMC failed. No big deal, I’ll wipe the eMMC and start again. All I need is an image on my SD card, right?

Regardless of what I do now, my phone only boots to a blank screen with a steady green LED. No SD card image will boot. It doesn’t matter if I short press or long press the power or RE button. I’ve tried USB-C plugin combos and 6-8 different distros (Kali, UT, Manjaro, Arch, Mobian, Arch, Rhino)

The only time I’ve managed to break out of this hopeless loop is when I load the factory test builds for either hardware or battery testing. When I use the hardware test build it boots to a barebones Android distro, however I can’t see eMMC storage. When I hold the power up button (while booting the factory test build) I can boot to the bootloader that mentions side loading from ADB etc, however my PPP isn’t recognised by either of my machines when in this state.

With the factory build loaded my machine recognises the device as a tablet but I can’t access or view the eMMC. My device is only visible in lsusb and never lsblk. I have also tried using rk2aw to see if I could figure a workaround, however this only helps me to boot into Masked ROM mode and I have no idea how to recover with such limited access.

What am I missing? I’ve read through so many of these posts thinking the answer is right here somewhere. If someone could help me solve this I would love to help document this whole fix because it shouldn’t be this difficult. 

Thank you in advance.

I asked in pine64 support and they said everything is fine and to ask here. Basically I have two different usb hubs one is an anker and one is a kind of no-name brand one. Neither work with the pinetab2. I plug them in and they make a concerning humming sound and no device actually works on them. Are there certain hubs that are known to work? The issue is that with using an wifi dongle it monopolizes my USBs and then I can't use a keyboard and mouse so I was hoping to use a hub to give me more ports. 

Thanks!