New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android embedding v2 #274
Android embedding v2 #274
Conversation
@ened Thank you for your contribution, I will test your modification and merge it without error. |
@cloudwebrtc how is your progress? :-) |
@ened Just now I did some tests. When I lowered the Android SDK API level to 21 or below, GetUserMedia could not get the camera stream. Does it seem that the SDK migration process caused a bug? The loopback example also doesn't work. |
I had some some tests successfully on older Android versions but not extensively. Can you please share the steps you took exactly and I will try to reproduce them here. Have about 7 different phones to test with, starting on Android 6. What do you mean "lowered the Android SDK API level to 21"? It means you just ran a test on older phones, right? No code change was involved, right? Regarding the bug itself, I am 100% sure; it should not have been caused by this, but will test. |
I used AVD Manager to create an emulator and selected Android 5.0 (Google APIs) x86_64 bit API 21 image. It seems that I cannot complete the GetUserMedia action, but the master
|
@cloudwebrtc ok - I was able to reproduce the problem on a 5.1 device. Will try to rework the permission handling a bit more and check the loopback example. |
Out of interest, what sort of devices are you supporting this old?
…On Sat, 13 Jun 2020, 10:02 Sebastian Roth, ***@***.***> wrote:
@cloudwebrtc <https://github.com/cloudwebrtc> ok - I was able to
reproduce the problem on a 5.1 device.
Will try to rework the permission handling a bit more and check the
loopback example.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#274 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABG66E7GMWKRTJHIHEAOQDRWM6C5ANCNFSM4NXGDR3Q>
.
|
@cloudwebrtc can you please share the android studio editor settings this project is using |
@ghenry Samsung J3 comes to mind. Because WebRTC also supports audio-only or data channel operation, it’s not completely out of the equation, yet. |
@cloudwebrtc have tested again & hopefully fixed the bug rgd. the permissions on pre-M devices. Successfully tested the example App on these phones:
This PR now also bumped the webrtc dependency. |
@ened I tested API 21 and can capture the camera, I will merge it now. |
I usually use VSCode to directly edit the code, and Android Studio will be started unless necessary for native debugging, so I use the default settings. xD |
@cloudwebrtc thx for merging & understood rgd your process. If you don’t mind I’d reformat using the flutter recommendation (Google-Java-format), and adjust readme and CI scripts. That should make future PRs a bit easier to read, as typically everyone has a different configuration. |
@ened No problem, we can use standard formats like google (clang-format or java-format) to format the code. |
This migrates the Android side of the plugin to the new Embedding V2 API.
Functionality has been tested locally on a few phones, but I'll appreciate if others can test as well.
Note: My Android Studio installation probably formats the code different than other contributors. Could the project agree on a standard set of rules? Most of the official flutter code uses google-java-format (a plugin in Android Studio) with the Google rules. Maybe this project could use it, too.