Hey all,
I'm new to this forum but excited to be a part.
I have an application "*****ute" in the Google Play Store and here's the source code:
hxxps://github.com/hexag0d/*****ute_mobile_android_a2
My app uses Android WebKit WebView and since the Chrome 71 update, WebRTC no longer works inside the app. Does anyone know if it would be possible to downgrade to the Chrome 70 WebClient and what problems that would cause for other apps on the device?
WebRTC no longer works in Brave either.
Another question I have is if it's possible to force my WebView to use an older chrome client? Or, could I change the WebView to not use chromium?
This issue in Chromium supposedly won't be resolved until March, at the earliest.
Hi,
I have the same problem. Did you find any solution?
Related
Hello,
i am a long time cyanogenmod user without any google services installed. It seems like chromecast is just possible to be used with google play service api. There are some tools (UniefiedNlp, NOGAPPS) replacing parts of google api but it does not seem like its working with chromecast.
Is there any chance to get a chromecast work without installing google software?
I know from my own experiences that in general a chromecast can work without google services. So this is not impossible what you are asking for. But i am sorry i have no idea about android apps capable of doing that ...
Can anyone advise on a good product and installation method that would protect me system wide using both android apps/chrome apps? For example, if I installed a vpn product through the play store, would it only provide security only in that "sandboxed" android app environment? Or installed to chrome OS, could it provide better security for the whole ecosystem?
I'm using an asus chromebook flip, on stable regular build (54). Thanks
So, I Also have a flip, and I've noticed that when using a VPN like Tor It will only cover android apps, so I'd use Tor and Firefox together to have a VPN'd web browser.
VPN's from Android Only cover android apps,
VPNS from Chrome only cover Chrome.
i was thinking about this myself, since i have a VPN client as a chrome extension. I will enable it and install an android app to test and see if the VPN is working for both
I have to use PIA VPN app for Chrome, and install PIA for Android in Android from the Play store. One does not 'cover' the other. Equally, the Afwall app will only affect Android apps installed.
I use TunnelBear. The Chrome extension only affects Chrome tabs. The Android app seems to affect all apps, including Chrome. I tested by checking my IP address in Chrome and in an Android browser.
Sent from my Pixel using Tapatalk
Hi..
im so curious about this, what is the difference between:
1. AOSP Webview and Google Webview?
2. What are the advantages of them?
3. Which one is better (or suggest) to using in custom roms nougat?
i noticed, mostly all custom roms preinstalled with AOSP webview (as you can see it in dev. options on "webview implementation".) but once we donloaded google/android system webview in playstore it automatically replaced the AOSP webview with Google one. and theres no option to switch or choose between them.
4. does the Dev's or AOSP webview will always be updated?
(since google webview always does within playstore)
If anyone have ideas about them, a bit of explanations which one should i pick on custom rom, i would be much appreciated, and im sure people would like to know also, thanks a lot!
It honestly depends on the developers to update the WebView implementation themselves. The difference comes in that ROMs ship Chromiums implementation instead of Chromes meaning that we lack the proprietary stuff shipped in Google's standard WebView. You will also notice that Chrome can provide WebView features too. Often Canary is the best route to take on this as it provides the latest implementation of WebView, and in my experience, has been more than stable (WebView at least, the browser isn't excactly a joy)
I've found Google Webview to be more stable than some ROM's builds of AOSP Webview. If you notice apps using that little web browser within apps crashing more often than normal switch it.
I prefer the Android Web Viewer because its less invasive. MHO They may crash more because of google play's aggressiveness as an intrusive APP
Hello,
I want to inspect some traffic from one specific app and found this blog post https://medium.com/@gaikwadchetan93...rk-traffic-via-mitm-proxy-part-1-886f6324f705
The MITM Proxy is working fine with HTTP and also HTTPS in Chrome, but not in other Apps.
I've found out, that since Android Nougat no certificates from user store will be trusted and in the blogpost he wrote to edit res/xml/network_security_config.xml.
But how do I do this? I didn't developed this app, I've downloaded it from play store.
I think i have to use a rooted phone, whats no problem, but how to I do this.
How do I edit the res/xml/network_security_config.xml or is it possible to move the certificate from user to system store?
Thank you for your Help
Hello,
I have an Iiyama ProLite TW1523AS-B1P Android screen. -> https://iiyama.com/gb_en/products/prolite-tw1523as-b1p/
It's a 15" touch screen that runs Android 8.1.0. without GMS. I want to use it as a dashboard for my Home Assistant setup. The only thing it needs to do is run some sort of Kiosk app/browser that points to my Home Assistant URL. I tried "Fully Kiosk Browser" and some other apps but my Home Assistant URL won't load, it appears that the Android Webview component is too old (61.0.3163.98).
But Iiyama never issued updates, the screen comes with Android 8.1 and that's it. I installed Aurora store and installed Chrome & Chrome Beta & the lastest Android Webview in the hope to adjust the WebView implementation to use anything other then Android Webview but it's the only option I get in the Developer Tools, I can only select the Android Webview, not the installed Chrome or Chrome Beta.
From the Fully Kiosk FAQ:
If you’ve installed the latest Android Webview and Google Chrome but Fully Kiosk still shows an outdated Webview version in the Device Info box (in Other Settings) your Android device likely has an AOSP ROM where you can’t update the Webview. The integrated Webview has another app ID (com.android.webview) than one provided by Google Play (com.google.android.webview). So the new Webview will be installed side by side but the old integrated Webview will still be used by Android system (and it’s app ID is hardcoded in Android OS). There is a workaround for rooted devices however it’s very complicated to use.
I think that's my problem as well. I installed Magisk to try and root the device but it bricked it so I had to ask for a replacement screen, not sure if that will work every time Do I have any other options? I was really hoping that Android 8.1 was "new" enough to load my Home Assistant URL but apparently not, but I could not test it before trying the screen so now I'm a bit stuck with this screen, hoping to update the webview component or change it to Google Chrome so it loads my Home Assistant URL. Thanks!