@andi-again I'm having the exact same issue. Do you mind elaborating a bit on what exactly you did to fix this?

@flaun-in it doesnt either on my Nexus 5

@marlboro50 yup. agree!

@flaun-in I had a similar issue. user @lduboeuf pointed out "This is a current Morph Browser limitation, you cannot access Microphone and Camera see https://github.com/ubports/morph-browser/issues/399"... that wont help ya but at least you're not alone. Cheers

I have solved the problem. The issues had nothing to do with my code. Just in case it helps anyone else: In the file

yourappname.apparmor

(which is automatically generated by clickable) you need to add the policy group "picture_files_read". I assumed "content_exchange" would suffice but it doesn't. So this issue is solved

@kugiigi Thanks for the links. Will have a look at it tonight. I am coding in html/css/js and using clickable to create the ubuntu touch package/app. I think I found another solution here

https://developer.mozilla.org/en-US/docs/Web/API/File/Using_files_from_web_applications

Dear all,
in the web app I'm developing the user is supposed to upload an image via a input element:

<label for="file">Upload</label>
<input type="file"  accept="image/*" name="image" id="file"  onchange="loadFile(event)">

This then prompts the JS function

var loadFile = function(event) {
  var image = document.getElementById('pic');
  image.src = URL.createObjectURL(event.target.files[0]);
};

This works in all the browsers on my ubuntu desktop but not in the app itself on my phone. This screen opens, when I click the 'upload button'

Any idea what the problem is here would be much appreciated...

Thanks so much @lduboeuf for pointing this out!!! This certainly explains all of the above described behaviour!!!

So after studying this a bit I came to the conclusion that I mixed a few things up. So my tuner IS of course a web application. So if Morph Browser is not allowed to access the mic then neither should be any web app, right? I understand the security issues with a browser allowed to access these system components but it does strike me as odd that it should be a priori impossible to grant these permissions on a case to case basis - so to speak. What is also odd is that according to the UT Tweak Tool my app does indeed have access to the microphone

Thanks @Flohack and @libremax. Yes, I observe the same behaviour with morph and the online tuner. But since my app isn't a web application I don't see why morph would have anything to do with it. It could just be a case of RTFM on my part, i.e. that I set the wrong policy group (http://docs.ubports.com/en/latest/appdev/platform/apparmor.html).... I'm working on it now

Thanks for the reply! It actually doesn't for me. The 'Guitar Tools' App doesn't work on my Nexus 5. It freezes after a few seconds and the 'more sophisticated' components of the app like the tuner doesn't work in those first few seconds. But I'll have a look at their code anyway

Dear all,
I've been experiencing some difficulties with my guitar tuner app I'm developing. I'm totally new to all this so I might be overlooking something essential.

I have developed a simple guitar tuner app with HTML/CSS/JS. It works fine in any browser (It's not a webapp tho! It's a native app and all the resources necessary are local) I test it with on my Laptop.
I have converted it into a .click package and managed to run it on my UT Phone (Nexus 5). When I start the app I am prompted to allow Microphone access which I allow. Now the problem is that this access is never really granted. First of all the tuner does not work because it gets no signal from the microphone and in the 'Security & Privacy' Setting the app is not listed as having access to the microphone. So how can I grant this app acces to the microphone?
What am I missing here?