4 ms·
> I hate that I still feel bad using it as a phone (terrible audio) If there are some handcrafty people on Pinephone Pro around: try some opensource denoiser l
by phh 3y ago
> I hate that I still feel bad using it as a phone (terrible audio)
If there are some handcrafty people on Pinephone Pro around: try some opensource denoiser like rnnoise. If it works, then it's probably worth the effort to integrate a opensource software VoWifi (using doubango IMS -- even if it's to do VoWifi over LTE), since that will allow you to use the denoiser (and the codec!) of your choice, rather than using whatever Qualcomm has in that quectel module.
In my opensource software VoWifi for Android implementation, I already implemented rnnoise, because I know that the denoiser you get on smartphones vary wildly, and there is a nice "unprocessed" audio source on most smartphones to bypass the vendor denoiser.
I've had various issues with vendor denoiser, going from, no denoising and no silence injection at all, but with AGC, so when I stop speaking the other side hears the noise very well. I've had vendor denoiser eat some very specific pronunciations: my guess is that it was calibrated for CN languages rather than europeans. And then, there is Qualcomm which have various levels of denoiser ("fluence"), which costs more or less, so if OEM is cheap... well denoiser is cheap.
On the rest of the article, despite my love for opensource software, PPP is nowhere near usable for me, so I commend the author for sticking with it so hard. I've tried PPP a bit, but the form factor alone kills me (well my daily driver is smaller than anything you can find.
Camera is really an issue, we really need opensource software processing pipelines -- that'd be slower, but much easier to improve, evolve and customize, and you can do the processing "later" (save only 10 raw frame burst, and process them during the night into merged photos). That's my wish, though sadly I tried doing it and so far failed spectacularly...
> are also getting completely open source firmware, like the Modem itself,
yeah... it isn't. opensourcing the AP of the modem is not very interesting, since you just end up with something as open as a smartphone. The modem's modem is still closed source.
> Texting in SXMO happens through the Linux console, neatly wrapped up in scripts and menus that make it easy. All you need to know, is that the text editor requires one press of the "i" key, before you can start writing.
Uh. That's next level usability... Don't get me wrong, I'm a fan of vim, but uh maybe not on a smartphone. At least that's not a selling point.
- seba_dos1 3y agoI'm daily driving a Librem 5, with Phosh and PureOS. Unlike PinePhones, it's using pulseaudio-module-echo-cancel to handle audio (the modem is seen as just another I2S card on the system) which seems to do its job well. Nobody complains at least. You can, of course, easily replace it with any other kind of processing you'd like to have there. > Camera is really an issue, we really need opensource software processing pipelines Since the camera app already stores raw DNG files, what I do when I want to share some nice photos is to load them into darktable, which is an easy way to make them look much better: https://dosowisko.net/l5/photos/ https://dosowisko.net/l5/photos/ You could prepare some reasonable template and run darktable-cli on the phone itself in a script. > Don't get me wrong, I'm a fan of vim, but uh maybe not on a smartphone. At least that's not a selling point. It sure is for the kind of people that opt to use SXMO. Back in the Openmoko days there were people who used Emacs as their phone interface too. There are more conventional DEs out there though:)