techtrio.blogg.se

1. UNGOOGLED CHROMIUM EXTENSIONS ANDROID INSTALL
2. UNGOOGLED CHROMIUM EXTENSIONS ANDROID PATCH
3. UNGOOGLED CHROMIUM EXTENSIONS ANDROID CODE

Regular Chromium just doesn't cut it privacy-wise and I don't see the point in the many Chromium clones except that one project that just removes anything Google, resulting in a plain Chromium without all the nasty stuff. There is an open issue for adding FreeBSD support but that hasn't found more interest since 2016, though I'm confident that is willing to provide support if any questions arise.

UNGOOGLED CHROMIUM EXTENSIONS ANDROID CODE

Required code could be found either in Kiwi repo or in my patches.Is anybody interested in creating a port for this (preferably with libva support for HW accelerated video)?

In addition if you're going to do it on a mobile device, you have to use a desktop User Agent for Webstore since it's not intended to work on a mobile Chrome.

UNGOOGLED CHROMIUM EXTENSIONS ANDROID INSTALL

I'm sure it should be tied to domain/URL, so Ungoogled patches should replace to some unreadable nonsense thus making it impossible for Webstore to actually install anything.Īs you've mentioned.this API leaks at minimum a list of installed extensions to Google, so enabling it unpatched isn't privacy-friendly. I've never examined that part of Chromium, but that's my understanding of it based on Firefox, so it may be partially or fully wrong.įor me it looks like Chromium provides some sort of private JS API to Chrome Webstore to allow installing extensions. However personally I feel againt adding back the ability because this will give Google an ability to detect your browser type and potentially tracking your usage of extensions, which is against the goal of this project. I searched the issues in main repo but cannot find an explanation on this so I am going to open an issue there. Now about whether this should be reverted needs a whole discussion.

UNGOOGLED CHROMIUM EXTENSIONS ANDROID PATCH

To work-around that, one solution is to init without extensions the first time ("if (early_initialization)"), vs "if (init_with_extensions)" the second Ok so I did a quick test with vanilla chromium on windows and the web store can recognize it as chrome, so there is some patch in ungoogled-chromium that removed the ability of webstore to detect the browser.

However, when you have extensions enabled, there is a circular dependency, so you always end-up with non-met dependencies (hence the undefined pointers) On Android, the session profile is loaded early (earlier than the desktop version), and to load the session profile, it depends on other components (it's actually called "DependsOn(XXXX)" in the code) which are supposed to be lazy-initialised. The null references is because there are inter-dependencies that cannot be met at the moment the session profile is loaded the first time. Looks like you've achieved some really interesting results, I'm curious to look at it closer ASAP. Sadly I could not figure out that caused that. I had NULL dereferences in extensions API init, somewhere in socket lazy inits. Do you have any idea about this?ĮDIT: I solved it by delaying the initiliazation depends on extensions. And they like to spam if true || so needs to double check to make sure nothing is enabled by Did you run into a SEGV_MAPERR caused by HostContentSettingsMapFactory/ CookieSettingsFactory in chrome_browser_main_extra_parts_? I tried to delay them with if (full_init) but then I ran into another problem where extensions::ExtensionsBrowserClient::Get() is null in chrome/browser/profiles/profile_ and I cannot find a way to initialize it. chrome/android:trichrome_chrome_bundle_module_paks_locales_asĪlso the patch seems to be not only for extension (it mixes with some other modifications like safe browsing). chrome/android:monochrome_bundle_module_paks_locales_as chrome/android:monochrome_apk_paks_locales_as chrome/android:chrome_bundle_module_paks_locales_as chrome/android:chrome_apk_paks_locales_as out/Default/gen/extensions/strings/extensions_strings_as.pak chrome/android:trichrome_chrome_bundle_module_paks_locales_afīut no targets in the build generate that file. chrome/android:monochrome_bundle_module_paks_locales_af chrome/android:monochrome_apk_paks_locales_af chrome/android:chrome_bundle_module_paks_locales_af chrome/android:chrome_apk_paks_locales_af Is listed as an input or source for the targets:

out/Default/gen/extensions/strings/extensions_strings_af.pak ERROR Input to targets not generated by a dependency.