-
Notifications
You must be signed in to change notification settings - Fork 35
Microphone access not working #399
Comments
@Flohack74 I heard that with your 6P such feature is working, can you please try the link above and confirm? |
Yes it works for me, trust prompt appears, and recording seems to work as the round circle pulses when i speak. |
Broken at least on fp2, volla phone and pro 5. |
js log, tells when i request permission and allow them with
|
Also wont work on volla phone and nexus 5. Neither microphone or camera access. Tried using on jitsy |
On my Xperia X 32 bit devel using morph I have just tested a web based video conference system senfcall.de (an instance of BigBlueButton TM):
I was asked if I want to give microphone permissions. Confirmed that. Yeah, works! Also tried a jitsi.meet conference. Works too. |
Just tested on my E5 (devel, Qt5.12 test environment enabled). Microphone does NOT work. Only listening to callers. So this really seems to be device dependend. Xperia X seems to be on the lucky side. ;-) We need to find out what does make the difference. |
Btw. microphone access works for me now in Morph on Halium9 FP3. |
I confirm the issue. Device: Xiaomi Redmi Note 7 Lavender Website replied that Microphone access has been denied. (See screenshots) Remark: App "Music Recognition" does not start recording. luksus42/soundrecog#7 Btw, no problem with Nexus 5 + Vollaphone. Only my Redmi Note 7 is affected by this issue. Thank you beforehand. Regards, Steve |
Mir expects a PID of a process that have a Mir session. Meanwhile, the trust-store users supply us the PID of the requesting process, which might not be the same process. For example, QtWebEngine uses a helper process to record the audio. In this case, Mir won't be able to find a session and fails. What we do here is that, when we encounter such error from Mir, get the process's parent pid, and then try again. Thanks @mariogrip for the idea. Fixes: ubports/morph-browser#399 Fixes: ubports/ubuntu-touch#1668
uh, I thought we would get a fix for this soon :-( |
@UniversalSuperBox Ok... So will this issue be reported in OTA-19? |
@stanwood77, possibly, if review of any contributions completes and works correctly for your device. I'm not sure if the linked pull request will fix your device exactly, since Ratchanan doesn't have a Redmi Note 7. But you could certainly test it out to help us test it, that will improve the likelihood that it gets merged in OTA-19. |
Hm, I just tried and at least with the PinePhone running last devel (692) this isn't fixed. Tried on https://online-voice-recorder.com/ |
Trust prompt for microphone access in morph browser ( or MorphWebView) does not appear on:
|
@luksus42 can you please provide a screenshot of "trust-prompt", because now I'm confused about what we are talking about. As said when I created that issue, I do have a prompt asking to access mic on FP2, but accepting it doesn't grant the permission. |
Trust prompts are currently broken. Please see ubports/ubuntu-touch#1814. |
@Danfro well actually they should not be broken in RC and devel :) |
Darn, sure. :-D You are right. It was broken but should not be broken anymore.
(IF it is still broken, then please comment on the OTA20 board.)
…--
|
so to conclude:
|
So I reopened this issue and moved it OTA-21... Sorry to say but this does not work at all it seems @peat-psuwit |
Oh thx for looking. Doh! Will do |
So this seems to work now. (FP3, halium 10 devel, 2021-11-21) I have had on issue though, but I cannot reproduce it:
|
Appears to work, tests so far no longer complains about mic access |
Works well on XperiaX, with that website: https://fr.mictests.com/ |
To be able to send vocal messages with Axolotl, we need to access the microphone. It looks like even with OTA-13 and the QtWebEngine upgrade, the microphone isn't working. When going to a website like https://framatalk.org/test, the access to the microphone is asked, but even after saying Yes in the UT popup to give permission, the website can't access the microphone.
Tested on a Fairphone 2 Halium 5.1 port, running the last devel build.
Same problem with my Pinephone last devel.
The text was updated successfully, but these errors were encountered: