High-pitched voices with Skype 8.138 on FP4 with /e/OS 2.8
- /e/ version: initially 1.18 (based on Android 12)
- Device model(s): Fairphone 4
- Developer mode enabled: no
- Device rooted: no
- Trackers blocker enabled: no
Summary
High-pitched voices with Skype 8.112 on FP4 with /e/OS 1.18 (and subsequent updates of Skype and /e/OS)
The problem
To the kind attention of /e/OS support/developers,
PLEASE NOTE.
- My experience with smartphones and their operating systems is extremely low and, for instance, the procedure to create a log reported here https://doc.e.foundation/support-topics/create-a-log seems complicated for me to follow
- I am creating this new issue based on what suggested here https://doc.e.foundation/support-topics/report-an-issue and also since I wasn't able to find any useful info related to my problem on gitlab.e.foundation, forum.fairphone.com and community.e.foundation
- For instance, no useful info in the following three posts to which I contributed already (I tried all the suggestions from the following three posts but still no success): https://forum.fairphone.com/t/skype-high-pitched-voices-on-fp4-with-custom-rom/97438 https://community.e.foundation/t/microsoft-teams-high-pitched-voices/39205 https://community.e.foundation/t/high-pitched-voices-with-skype-8-110-on-fp4-with-e-os-1-18/54348
When I call (or receive a call) on Skype the voices that I hear from the loudspeaker of my FP4 are very high-pitched. I don't use headphones/headsets. On the other side of the Skype calls people can hear my voice loud and clear and texting is OK in Skype. If I play a YouTube video from Firefox the sound I hear from the loudspeaker of my FP4 is just perfect and same goes for normal telephone calls and WhatsApp calls. The FP4 was brand new when I installed Skype 8.110 on /e/OS 1.18 and I immediately experienced this problem; updating to Skype 8.112 didn't solve the issue.
If the issue is with Skype than that’s fair enough and I’ll wait to see if the issue disappears with new Skype versions.
What about if the issue is with /e/OS? Is this issue already known to /e/OS support and when a correction will be available?
Thank you
Best Regards
Nedo