On a PC, running chrome 25 (non beta)
shows me a microphone icon, clicking on it prompts for input.
When I stop talking, my alert call is executed. All good.
On a Galaxy Note smart phone running chrome 25 (non beta) running Android 4.04,
loading the same page does not show the microphone icon.
Also doesn't work on a Google Nexus-10 tablet running android jelly bean.
I've also tried
which also fails to show the microphone option on android chrome 25.
Given that the Chrome 25 release touts both Android speech capabilities
and more compatibility between Android and desktop Chrome,
I'm surprised this doesn't work.
Anybody else tried this and gotten it to work?
As of M25 and M26 Beta it is not implemented in Chrome for Android.
You should star this bug https://code.google.com/p/chromium/issues/detail?id=112934
Also of interest is the continuous speech input API, so follow this issue https://code.google.com/p/chromium/issues/detail?id=116954
CanIUse says this functionality is available in Chrome 55 released December 7th 2016
Related
I am getting the following error (see image) when running a very basic Ionic 4 / Capacitor app on an Android 6 device.
I think it is because the the Android system webview needs to be updated.
I don't have access to the device myself as it is with a client, all I have is an emulator. I can't seem to update the webview version on the emulator and I don't think this is possible so I can't replicate.
Capacitor states it should work with back to Android 5.1 if the webview is up to date.
I am not that familiar with older Android devices.
Is it as simple as sending this link and getting them to update the webview via the play store?
Will the device have play store installed?
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en
Capacitor docs:
https://capacitor.ionicframework.com/docs/android/
**Note:** Currently to use an Android Emulator you must use a system image of at least Android version 7.0 on API 24. This is due to the System WebView version not being able to be updated on emulators. Physical devices should work as low as Android 5.1 so long as they are kept updated.
Update:
I go the app to run on the device by removing all Capacitor plugins.
How ever I still have several issues:
I need to use plugins in the app
The css is not getting displayed correctly at all. None of the Ionic 4 colors are applying and the style are off.
It appears even after updating the Android system webview via google play to the latest and updating google chrome it is still using an old version of the webview.
Here is the userAgent output:
Mozilla/5.0(Linux; Android 6.0; C72 Build/MRA58K; wv) AppleWebKit/537.36(KHTML, like Gecko) Version/4.0 Chrome/44.0.2403.119
Mobile Safari/537.36
The latest version on chrome is 73.0.3683.90 so it is way off.
This is the device:
https://www.chainway.net/Products/Info/42
Final Update:
I contacted the manufacturer of the device and they confirmed that the webview was locked to version 44 on the firmware.
They are look at providing an updated version of the firmware with a more recent webview version.
Also it was only the capacitor/core plugins that were not working. I could still use other 3rd party plugins such as a barcode reader.
If you are in the situation above I recommend using navigator.userAgent to determine the webview version as mentioned by #jcesarmobile in the comments below.
Yes, if you send that link and they update the Android System WebView then the app should work fine.
Unless your customer is in China, Play Store doesn't work there.
I'm using Android Studio and run AVD emulator (Nexus 5X API 25, Android 7.1.1 with Google APIs).
The project is a demo one, from https://github.com/commonsguy/cw-omnibus/releases/download/v7.0/RuntimePermTutorial.zip
When I press Record Video button (the green one), the video freezes and nothing happens however the settings button is active and actually 'defreezes' the video, but the only way to exit recording mode is the BACK button.
I tried it with emulators on API 23 and 24 and didn't see the same issue.
Does API 25 system require some additional setup for video?
Thanks!
Since the built-in Camera app on the 7.1 emulator has similar issues, and since the problem is limited to that emulator, I am going to consider this an emulator issue. For 7.1, test on hardware. Ideally, for all versions of Android, test on hardware.
On a PC, running chrome 25 (non beta)
shows me a microphone icon, clicking on it prompts for input.
When I stop talking, my alert call is executed. All good.
On a Galaxy Note smart phone running chrome 25 (non beta) running Android 4.04,
loading the same page does not show the microphone icon.
Also doesn't work on a Google Nexus-10 tablet running android jelly bean.
I've also tried
which also fails to show the microphone option on android chrome 25.
Given that the Chrome 25 release touts both Android speech capabilities
and more compatibility between Android and desktop Chrome,
I'm surprised this doesn't work.
Anybody else tried this and gotten it to work?
As of M25 and M26 Beta it is not implemented in Chrome for Android.
You should star this bug https://code.google.com/p/chromium/issues/detail?id=112934
Also of interest is the continuous speech input API, so follow this issue https://code.google.com/p/chromium/issues/detail?id=116954
CanIUse says this functionality is available in Chrome 55 released December 7th 2016
I have been trying to investigate during these days exactly which browser is the one that comes by default in the android devices, but I am still confused.
If I understood this correctly, there are two possibilities depending on the device and Android version:
"Android Browser" (its version depends only on the Android API? no updatable? based on WebKit?)
"Chrome for Android" based on WebKit
I have done some tests with all the devices that I have been able to obtain and I have seen that approximately from version 5.0 or 5.1 of Android the default browser begins to be Chrome for Android. I think that because on versions smaller than 5.0 I cannot debug the app-browser connecting it to my PC and from the chrome://inspect and on versions higher I can do it, but maybe I'm wrong. I would like to ask if anyone can verify or correct that?
I have also realized that in versions higher than 5.0 there is an application called "Android System WebView" also available in PlayStore, but I would also like to ask: Does this have any relation to the type of browser installed (Android Browser or Chrome For Android)?
How to enable WebGL in WebView widget for Android 5.1.1 emulator? I checked WebGL status through Webglreport and the result was "This browser supports WebGL, but it is disabled or unavailable. Sometimes this is the result of older video drivers being rejected by the browser. Try updating your video drivers if possible".
I also tried to use Crosswalk webview on Android 4.4.4 emulator and there were same problems, but I fixed it by adding xwalk-command-line xwalk --ignore-gpu-blacklist. Is it possible to make something similar for standard WebView widget?
UPDATE: The WebView team says WebView does not allow gpu blacklist override, now or in future plans, due to security/stability risks: more details.
//
Chrome for Android 47 and Chromium/WebView 47 use different gpu blacklists and/or bug workarounds. What is allowed to successfully render in one may not be allowed to successfully render in the other even on the same hardware. Both browsers are scheduled to release updates to the Play Store every 6 weeks.
For example: I have a Nexus 10, Mali T-604 tablet (Lollipop 5.1.1. Also, Android Studio 1.5.1 with SDK 6.0 Marshmallow API 23 or 22).
In Chrome for Android --
chrome://flags, #ignore-gpu-blacklist NOT enabled, and all reset defaults
chrome://gpu, "graphics feature status-WebGL: Hardware accelerated" and Reset notification strategy 0x0000 surprisingly (see this last Crosswalk related) answer
webglreport, "This browser supports WebGL 1"
get.webgl.org, cube spins
In WebView --
webglreport, "This browser supports WebGL 1, but it is disabled or unavailable. Sometimes this is the result of older video drivers being rejected by the browser. Try updating your video drivers if possible."
get.webgl.org, "Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card."
chromium blacklist (link from Khronos WebGL blacklist wiki): "GPU rasterization and canvas is blacklisted on Nexus 10".
chromium bug list (link from Khronos WebGL blacklist wiki): "The Mali-Txxx driver does not guarantee flush ordering" and "The Mali-Txxx driver hangs when reading from currently displayed buffer".
The Pixel C tablet has a Nvidia Tegra X1 which does not appear on the chromium lists, and I've confirmed that it does support WebGL in WebView.