I am currently developing a mobile app that converts voice to text using pocketsphinx imported in worklight. Its working fine in mozilla alone but the microphone is not getting recognised in any of the other browsers or in the worklight. So how to get away with this??
Google's documentation for capturing audio states that you must add the following permissions in AndroidManifest.xml. You do not state whether you've done so or not, nor do you provide any errors you see in LogCat, nor anything else to work with.
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
Verify you've added the above permissions.
Edit the questions with error logs.
Provide demo Worklight project exhibiting your problem.
Related
I am trying to run my react native app on my real android device as the laptop gets too hot while using Android studio (8 Gb RAM, the pain). Hence, I enabled my USB debugging, plugged the cable and ran the command "react-native run-android". The app started with no issue. I started the backend server also which are up and running on localhost:3000 and localhost:3001. The app runs and greets with a login and sign up page. I tried to sign up but there is an error saying
Error [TypeError: Network request failed]
I am connecting via WIFI on the same network and hoping the server and the app can communicate but the app doesn't.
There is not any issue with the code itself as I ran it multiple times in android studio previously and the app ran well. I was able to sign up as a new user and login with the same id. I am not able to do the same in the real device.
My questions:
I read the official document and it said to open in-app developer menu and put the machine ip address and localhost server. Is this localhost server the one that the Metor JS runs on or the backend server of the app itself?
What am I missing here, any commands or any configuration?
Why is my app not able to communicate with the server?
Reason behind the network error.
You should follow these steps to connect with the bundler.
Make sure that the app and bundler using the same network.
If you are using android add this code in your androidMenifest.xml file.
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission
android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<application
android:usesCleartextTraffic="true" // make sure that this line is added.
.......>
.......
</application>
if you are adding localhost in the developer setting try to add your IP address like this, yourIP:yourPort
example: 192.168.89.24:8081
My Flutter application accesses a REST API on my web site. When I run with the local emulator it works 100%, but when I use it with the device (Samsung A80 cell phone using Android) or install the apk on the phone, access to the database does not work.
Is there a configuration missing?
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.mysongs_v2">
<!-- Flutter needs it to communicate with the running application
to allow setting breakpoints, to provide hot reload, etc.
-->
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.WAKE_LOCK"/>
</manifest>
The error does not appear to be the access to the database, but it only happens when I use the cell phone.
This is when I run using the emulator.
I have integrated voip call in react-native using react-native-webtrtc and in-call-manager (https://github.com/react-native-webrtc/react-native-incall-manager) for call management.Everything working fine with call. In-call-manager works fine for playing ringtone/busytone but also want user to have options to mute mic or turn on/off speaker phone while on call.
I have tried InCallManager.setSpeakerphoneOn(true/false) InCallManager.setMicrophoneMute(true/false) but no change occurred. Also I have opened issue on git but no response so hoping to get answer here
I expect if both function works fine then User is able to mute/unmute mic or turn on/off speakerphone.
I have dealt with this issue before you just have to add
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
in the manifest file of your project.
Both InCallManager.setMicrophoneMute() and InCallManager.setSpeakerphoneOn() will work.
You are right though. This is not clearly mentioned on their Github page.
I have upgraded my Android app from Quickblox Version 2.6.0 to 3.3.0. I am now experiencing the issue of missing audio on my video calls. It seems to be an outbound issue, as I have tested the app in interaction with the old version. In the logs i can see following error:
E/libjingle: (stunport.cc:283): Jingle:Port[0xb850ea58:audio:1:0:local:Net[lo:127.0.0.0/8:Loopback]]: UDP send of 96 bytes failed with error 22
Has anybody experienced an similar issue?
Coming back to this issue I shamefully have to admit, that I was missing the proper permission in the AndroidManifest. :P
<uses-permission android:name="android.permission.RECORD_AUDIO" />
The communication now works as expected. But I still see the errors in the logs. Can anybody shine some light on why they are occuring? Is this only network related (and not preventable)?
I had follow the below instruction from offical wso2 site https://docs.wso2.com/display/EMM220/Data+Containerization+for+Android+Device
But after completed the setup work profile and unstall the agent app from personal profile.
And I have checked my work profile there is no agent app is in accounts page. Please let me know if any solution.
This probably occurs due to an issue in the android agent. To fix it, you can edit the following line and set the android:exported to true.
https://github.com/wso2/product-emm/blob/master/modules/mobile-agents/android/client/client/src/main/AndroidManifest.xml#L99
<receiver
android:name=".services.AgentDeviceAdminReceiver"
android:permission="android.permission.BIND_DEVICE_ADMIN"
android:exported="true">
Once you have done this, you can re-build the agent application and then you will be able to generate the work profile successfully. Fix for this issue should be available with the next release.