Kiwi Browser has no syncing option, while other Chromium browsers do have. A workaround ------------ The idea/hack is to: 1. install another browser (like Chrome Beta), 2. not use it, 3. and hard-wired Kiwi's data into the former's data folder. 4. *(existing Kiwi will trigger the other browser syncing activity)* The following experimental script, --------------------------------- is trying to hard-link Chrome's data to a different folder. *Note that Kiwi Browser isn't involved yet at all.* This is just a POC, to see how well a Chromium browser works with "hard links". Is it working? - No. -------------------- Chrome is able to open correctly. But it saves nothing as expected. Not Preferences, not History, not nothing. # Source (Chrome's data), # Target (the folder outside of Chrome): S="./app_chrome/Default" T="/data/data/shared/app_chrome/Default" # Creation of hard links: cd /data/data/com.android.chrome ln -f $T/History $S ln -f $T/Bookmarks $S ln -f $T/Preferences $S *P.S.: with 'soft' (symbolic) link (instead of the above 'hard-links'), Chrome will not even be able to launch.*

I have a Realme 1 with Android 9. No matter what Chromium I use, sometimes the pages don't load, the loading bar being a bit filled. This happens randomly. It even happens with about:blank. I have faced this problem for years with Bromite, Kiwi Browser, Brave etc. The Webview browsers do not have this problem. I do not have Chrome installed.

A client of ours has a website that works on most browsers. However, when trying to open it in Chrome (114), Edge (114) or Samsung Internet (21) on Android, there is an error message saying >Your connection is not private ERR:ERR_CERT_AUTHORITY_INVALID. We tried several phones with Android 12 and 13, but the results are all the same. Also: - Firefox on Android works - Chrome and Safari on iPad and iPhone work - Chrome, Edge and Firefox on Windows desktop work Because it works in almost all browsers, I think it's safe to assume there is nothing wrong with the certificate, and the problem lies with Chromium. My question is, how can I further investigate this issue? (I realize this question may not necessarily be about Android, but I'm not sure where else to post it)

In Chromium, command-line options can be enabled by browsing to chrome://flags and setting "Enable command line on non-rooted devices" to "Enabled". However, is there a way to do this programmatically (i.e., from the shell)? I need to enable this flag as part of my automatic tests.

There are command line flags (or "switches") that Chromium (and Chrome) accept in order to enable particular features or modify otherwise default functionality. - Chromium Command Line Switches - Run Chromium with flags I want to add --sync-url flag to use my sync server instead of Google sync servers. chrome://flags only enable/disable flags but won't let you add a new flag. Tried Chrome 41.0.xx and Chromium 43.0.xxx shell with: # echo "chrome " > /data/local/tmp/android-webview-command-line # echo "chrome " > /data/local/tmp/content-shell-command-line # echo "chrome --sync-url whatever" > /data/local/tmp/chrome-command-line Any idea how to run Chrome with flags on Android or directly add these to the default profile?

I'm using Chrome version 74.0.3729.136. My phone is not rooted. I'm trying to use flags in Chrome command line without root. I use the guide from Run Chromium with flags . According to that guide, with flags, it can be done. The guide said: > For production build on a non-rooted device, you need to enable "Enable command line on non-rooted devices" in chrome://flags, then set command-line in /data/local/tmp/chrome-command-line. When doing that, mind that the first command-line item should be a "_" (underscore) followed by the ones you actually need. Finally, manually restart Chrome ... I successfully set up the flag "Enable command line on non-rooted devices". But then I need to copy the data file to /data/local/tmp/chrome-command-line - and I cannot do that. I tried: 1. Command like that:

C*:\WINDOWS\system32>adb shell 'echo --unsafely-treat-insecure-origin-as-secure=TestTest > /data/local/tmp/chrome-command-line'*
   The system cannot find the path specified.

1. Recommendation from https://android.stackexchange.com/questions/103646/run-google-chrome-with-flags-not-from-chrome-flags # echo "chrome --sync-url whatever" > /data/local/tmp/chrome-command-line 1. Use different Android OS (5-7). 1. Use construction like the following for copying files: run-as com.example.app "cat /sdcard/temp_prefs.xml > shared_prefs/com.example.app_preferences.xml" but nothing happened. Anyone has tried it?

I've got Chromium 106 installed on my phone and can successfully launch it via

$ adb shell am start -n org.chromium.chrome/com.google.android.apps.chrome.Main

However, when I try to bring up a specific page at launch time with

$ adb shell am start -n org.chromium.chrome/com.google.android.apps.chrome.Main -d http://127.0.0.1:8080 

(I've got a web server running on port 8080 on my host with reverse TCP forwarding set up.) the app doesn't launch but I get the error

Starting: Intent { dat=http://127.0.0.1:8080  cmp=org.chromium.chrome/com.google.android.apps.chrome.Main }
Error type 3
Error: Activity class {org.chromium.chrome/com.google.android.apps.chrome.Main} does not exist.

Is this not the right way to use am with Chromium? Note: The command works if I run under su -c.

I have some HTML files in the SD card in my phone, which I want to open in Chrome. But, when I am entering the URL of those files in the Chrome's address bar with the file:/// prefix, Chrome says **Access to the file was denied**. But, I have checked that Chrome has access to the storage. See this screenshot: " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> Please help me out. I have Android 7.0 Nougat and please ask if any more information is required.

How can I change the User Agent string in either Edge or Chrome on Android? I found old tutorials suggesting either going to about:debug or about:useragent but neither of these seem to work anymore.

I am trying to sign in to Chromium for Android from my Android phone and it is not working. I am getting the following error message. > The account already exists on your device. I tried to delete the Google account on my phone and tried to set it up again. Still, it is not working. Is it not possible to sync Chromium on the PC and Android?

I have created a script for modifying the chromium browser's behavior when it starts. If the browser is freshly installed and if anyone opens it for the first time, the user will get a welcome note and sign-in form, which I want to suppress. According to my findings, the solution is to replace the /data/data/org.chromium.chrome/shared_prefs/org.chromium.chrome_preferences.xml file with a version that is generated after skipping the welcome note and sign-in form. The script changes the folder's permission successfully, replaces the file, and again changes back the folder's permission. But when I open the browser after reboot or without rebooting, that file is overwritten again and I still get the welcome note and sign-in form in both cases. But if I manually replace that file through the Android device monitor and reboots the device, it works. The browser I am using is Chromium v73.0.3674.0 for android. And here is the script

#!/system/bin/sh
su -c "chmod 777 /data/data/org.chromium.chrome"
su -c "chmod 777 /data/data/org.chromium.chrome/shared_prefs"
su -c "rm -r /data/data/org.chromium.chrome/shared_prefs/*.*"
su -c "cp /mnt/internal_sd/MokiMDM/org.chromium.chrome_preferences.xml /data/data/org.chromium.chrome/shared_prefs/"
su -c "chmod 660 /data/data/org.chromium.chrome/shared_prefs/org.chromium.chrome_preferences.xml"
su -c "chown root:root /data/data/org.chromium.chrome/shared_prefs/org.chromium.chrome_preferences.xml"
su -c "chmod 771 /data/data/org.chromium.chrome/shared_prefs"
su -c "chown root:root /data/data/org.chromium.chrome/shared_prefs"
su -c "chmod 751 /data/data/org.chromium.chrome"
su -c "chown root:root /data/data/org.chromium.chrome"

One of the touted features of Android 5 is the updates of WebView through Google Play. The official documents state: > The initial release for Android 5.0 includes a version of Chromium for WebView based on the Chromium M37 release... and: > Although WebView has been based on Chromium since Android 4.4, the Chromium layer is now updatable from Google Play. 1. Does it mean that the default built-in "Android Browser" is now actually Chromium M37 after updating to Android 5.0? 2. Does it mean that the default "Android Browser" auto-updates itself like the evergreen browsers on desktop? Assuming Play Store account is set up. After updating a Samsung Galaxy S4 to Android 5.0, What's My User Agent? shows that the default Internet Browser is "Chrome 34". What's going on?

I really like the Chromium browser, it's quite speedy, but I can't find any functioning downloads for Android. All the sites I've tried so far have the following error while trying to install the APK file: >Parse Error >- >There is a problem parsing the package. I've tried [Download Chromium](https://download-chromium.appspot.com/?platform=Android) (which was invaluable in getting Chromium working on my Desktop) and [Github's paul99/clank](https://github.com/paul99/clank) , but neither source seems to work. Does anyone know where I can download Chromium? (*not* Google Chrome!) I'm running a non-rooted Android 2.3.4 on Droid X.

Call me dumb, but, I don't see an obvious way to do this. I want to add duckduckgo.com as the main search engine in Google Chrome for Android (beta, stable...)

I am using Chromium build 353428 on PacROM 5.1. After signing in with my Google account, I tried to set a separate sync passphrase (using instructions given [here](https://support.google.com/chrome/answer/1181035?hl=en)) . However, when I click on my account name second time (with caption "Please update your sign in details"), the next screen has entries for "Password" as well as "Encryption" greyed out. Curiously, in Settings → Save Passwords, the options to save passwords is active. Do Chromium builds support saving passwords and encrypting them with separate passphrase? If yes, what might be causing the above mentioned behavior?