CRITICAL, SHOWSTOPPER issue in LineageOS 21: Microphone not functioning with Apps that use RTP/RTCP, eg., Google Voice, Signal, etc.
Expected Behavior
Other end of a phone call should hear my voice clearly when I use Google Voice or Signal Apps.
Current Behavior
Whether it's an incoming or an outgoing call in my Google Voice (GV) and/or Signal App, the other end party does not hear my voice, though I can briefly (before the call drops off) but clearly hear the other caller speaking. Then, the Google Voice App detects that my microphone is not working, complains about "unstable network" and drops the call (whether incoming or outgoing) and neither does the other end caller hears my voice. Sometimes, they hear just a garbled word from my end, before the call terminates.
This bug got introduced into LineageOS 21. LineageOS 20 was working fine, till I upgraded to LineageOS 21 last month (2024-03-16 build for my device 'river').
Logcat has been taken during the GV call that terminated and attached herewith.
This issue in LineageOS 21 seems to be that Microphone is not functioning with Apps that use RTP/RTCP, eg., Google Voice, Signal, etc.
Steps to Reproduce
- Just make/receive a call in any one of Google Voice or Signal Apps.
- When connected, other party does not hear my voice, even though my microphone is unmuted. Problem exists een when using bluetooth headphones and/or wired headphones.
Device information
/device river /version lineage-21 /date 2024-04-13 /kernel 4.9.337-perf+ #1 Sat Apr 13 02:24:10 2024 /baseband M632_43.192.01.165R /mods Google Apps, Magisk 27.0
I have read the directions.
Additional Information
- user @BadDaemon is WRONG to state lies that "(Plus the fact that it hasnt been reported before pretty much proves that it's not as "critical" as claimed)" - There ARE indeed many other bug reports (found by having to intently grope around the bugs database) that have reported similar issues in LineageOS 21 wrt the microphone issue itself, in at least the Motorola family of devices AND the Google PIXEL devices, such as: #6748, #6773, #6798, #6819, #6895, #6898 (closed), #6978, #6989 (closed). The existence of ALL these CRITICAL issues did NOT become apprent due to them NOT being linked together because user @BadDaemon has been unreasonably "locking up" others from commenting on them. Hence THIS issue is a highly CRITICAL issue and indeed deserves to be labeled as a SHOWSTOPPER CRITICAL issue and LineageOS 21's general availability must be pulled for at least the known affected devices IMMEDIATELY and a fix worked upon with the HIGHEST PRIORITY.
- Also, user @BadDaemon stating lies that "Also not everyone even uses stuff like Signal for calls, so there's that." is absolute doggone nonsense as this bug (#7007) report and the tons of other reports outstanding clearly show the popularity of real-time voice-calling and/or video-calling apps such as Google Voice, Signal, Google Meet, Zoom, WhatsApp (which also uses Signal protocol itself for communication), Talkatone, Telegram, Viber, Jitsi, etc., ie., ALL the wifi calling apps are affected by this SHOWSTOPPER CRITICAL ISSUE. Instead of constructively fixing issues, user @BadDeamon is just being an asshole and unreasonably "locking up" discussion on almost ALL bugs being reported on LineageOS in an uncalled for manner, with condescending and useless comments such as "refrain from me too messages, they add no value to a bugreport." - How in the world does addition of useful data-points/info by new commenters about another affected App or method-to-reproduce, NOT add value to a bug report?!?! It might not be of value to this LONE imbecilic asshole, but LineageOS is much bigger than this lone jerk and is used and appreciated by multitudes of users. Locking up bug reports is what is suppressing other users from realizing the existence of similar issue(s) and suppressing the realization of the criticality of the bugs to be fixed. Such uncalled for behavior is very DETRIMENTAL to the open and proper burgeoning of LineageOS itself.
- "And downgrade: not possible, perform a new installation." - Whatever does that short sarcastic quip mean? Will a "new installation" mean that the data cache will have to be wiped out trying to perform a downgrade? If yes, then how in the world is this version of LineageOS 21 still being offered to the public as a "stable" release?!?! It MUST BE pulled for all the affected devices.
- user @BadDaemon is unreasonably "locking up" almost ALL the bug reports that are being raised on LineageOS and MUST BE BANNED from LineageOS development itself, as such illogical and tyrant-like behavior is HIGHLY DETRIMENTAL to people's adoption of LineageOS - nobody needs such an asshole of a "developer" and must be FIRED from LineageOS development right away. LineageOS is a much larger project than this lone jerk.