First feature prioritizing poll

@praveenarimbrathod
The forum post has all the details(1). Biketool (on the forum) got calls with Mobian to work. Here is a high overview.
Device: PinePhonePro
OS: DanctNIX Arch with Phosh fully updated
EG25 Firmware: Biktorgj 0.8.0
ADSP Version: 01.003

DanctNIX Arch needs package pipewire-alsa to get the microphone and earpiece to work.
Mobian and Arch install package alsa-utils to set microphone volumes
copy down Biktorgj pine64-alsa-ucm configuration files (see post for more details)
Restart the phone
During a call, run alsamixer (from alsa-utils package) and set the default (PipeWire) microphone value to 0.
The Audio on the "other phone" should clear up
Plug in a headset (3.5mm headphones with microphone)
run alsamixer again and set the default (PipeWire) microphone value to 0.
DONE!

(1) https://forum.pine64.org/showthread.php?tid=19428

• Mobile data, gps and waking phone on alarm is broken. Things that people do expect to work should be fixed first.

• Not sure about notification LED? Once triggered (for feedbackd to work the phone needs to wake up) it should show in suspend, too. (Isn't that so).
  The 'once triggered' part is about waking the phone on external events (see below).

• If RCS is standard nowadays I'd opt for implementing it - even though I do not use it.

• Tracking mobile data use shouldn't be a problem using existing software, but surely is nothing end users could configure easily.

• Battery and heat improvements are always welcome but here already starts the list of stuff that isn't so important for me at all.

• Having the Librem5 run on mainstreams just sounds nice.

• Fixing geary is generally a good idea, but I don't use it. I'm using tangram (web app viewer) and a selfhosted snappymail web app that is just great.

• PGP - still don't use geary.

• Share files: I use fractal to do that or a self-hosted web app. Isn't really a priority problem I believe.

• I do not use Waydroid. Might be that invested energy will be wasted with Android translation layer becoming better.

• Waking up phones from suspend to receive VoIP calls or push notifications is complicated:

  • either hack their modems to subscribe to some notification service and wake up the main CPU on some events (Librem5, Pinephone - don't know about phones with modem/cpu in one chip)

  • trigger an external event that let's the modem wake the main CPU: SMS / phone call. @Guido is working on something, @Chris Vogel did some proof of concept: https://chrichri.ween.de/o/481d44c6609f4f44ab8ba5ab9c0bd480

  • this is infrastructure work mainly to get services that offer SMS / phone calls when the phone should be woken up

  • shouldn't be deployed on large scale, because to send SMS or call phones there's the phone number involved and that is a very private data point

  • should be organized locally for friends&family

  • works already if done correctly

@Chris Vogel Mobile data and gps are not an issue e.g. on SDM845 phones and PinePhone, for LED blinking in suspend works for SDM845. These devices don't have heat issues either, but e.g. the L5 has phone calls and camera (as does the PP). So the situation differs a lot between devices, I assume you're mostly looking at it from a L5 perspective.

I think we should acknowledge the device differences and look at fixing per device issues (e.g. Purism could fund the L5 bits).

True @Guido , I'm looking at the situation from the Librem5 perspective.

I think it is a good idea to split the issues into device specific ones and the ones where software/apps is generally missing (like easy transfer of files or mobile data usage statistics).

To make tracking these issues easier, I'm proposing we tag threads for first five issues as High Priority, next five as Medium Priority and last five as Low Priority.