5 Commits
Author SHA1 Message Date
AlexeyBarabash b62347bad5 [cr148][Android] SyncServiceAndroidBridge methods signature changed
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/7555add0775582ef4c8b7458f4e95f7493c80d9e

commit 7555add0775582ef4c8b7458f4e95f7493c80d9e
Author: Andrew Grieve <agrieve@chromium.org>
Date:   Wed Mar 11 17:24:07 2026 -0700

    Add @JniType to a batch of files in //components (#4)

    Bug: 491444984
    Change-Id: I14feaa20d1cde9479f5742c171e955d504fd3f05
    Cq-Include-Trybots: luci.chrome.try:android-internal-dbg,android-internal-binary-size
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7654452
    Reviewed-by: Peter Wen <wnwen@chromium.org>
    Owners-Override: Andrew Grieve <agrieve@chromium.org>
    Commit-Queue: Andrew Grieve <agrieve@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#1598092}
2026-04-27 12:00:46 +01:00
Artem Samoilenko 79cb1bbb57 [cr145][Android] Replace JavaParamRef -> JavaRef
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/0d6ec7e0f328e9ddd6f5174f61676ff85c777af6

commit 0d6ec7e0f328e9ddd6f5174f61676ff85c777af6
Author: Andrew Grieve <agrieve@chromium.org>
Date:   Tue Dec 2 12:37:02 2025 -0800

    Android: Replace JavaParamRef -> JavaRef (part 5)

    JavaParamRef used to be different, but now is an alias for JavaRef.

    Bug: 40173007
    Change-Id: I9bfa2fcdd012fc90859886ee2e747cb360733421
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7217772
    Commit-Queue: Andrew Grieve <agrieve@chromium.org>
    Owners-Override: Andrew Grieve <agrieve@chromium.org>
    Reviewed-by: Martin Kong <martinkong@google.com>
    Cr-Commit-Position: refs/heads/main@{#1553033}
2026-01-29 13:40:24 -05:00
Aleksei Khoroshilov a41bf5350b Replace "src/" includes with <> in chromium_src. (#30096)
This change updates how brave/chromium_src overrides can reference original files: it adds ability to use #include <...> along with #include "src/...". This is enabled by replacing -I../../brave/chromium_src with -iquote../../brave_chromium_src, which adds an include search path only for #include "..." directives.

With this approach, other files in the build tree can reference brave/chromium_src overrides using #include "...", while the overrides themselves can reference original Chromium files using #include <...>. Since Chromium uses #include "..." for all in-tree files, we can leverage this convention and configure our overrides so that we can drop support for #include "src/" later by removing -I../../.. and making rbe_exec_root modification obsolete (the main goal).
2025-07-24 17:37:44 +07:00
Artem Samoilenko bebe6c8a32 [Android] Move JNI bridges to syncer namespace
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/df43047ad08a3bc0c54ef91ac94db9a33e116486

[sync] Move JNI bridges to syncer namespace

No behavior change. Code in //components/sync/ should be in the
syncer namespace.

Change-Id: I1d82d16164ef7189b33bbb82717d6a903b246ba2
2024-09-10 14:42:30 -04:00
AlexeyBarabash b1c5789209 Empty SyncServiceAndroidBridge::KeepAccountSettingsPrefsOnlyForUsers method (#24535)
* Fix duplication of synced Android devices.

Override SyncServiceAndroidBridge::KeepAccountSettingsPrefsOnlyForUsers with empty implementation.

This prevents re-generating of device's cache_guid, which leads to appearing duplicated device at device list.

Fixes brave/brave-browser#39470

Related Chromium change:
https://source.chromium.org/chromium/chromium/src/+/d291751ad49b35720b6928527d0b876b8a247a25

	Make SyncTransportDataPrefs account-keyed

	Before this CL, SyncTransportDataPrefs only stored data for the
	currently-syncing account.
	One consequence was that this data had to be cleared on signout, and
	thus, signing out and back in would create a new set of data, in
	particular a new cache GUID.

	This CL makes SyncTransportDataPrefs account-keyed (behind a
	killswitch), so data for multiple accounts can be kept around, even
	after signout. This allows reusing the cache GUID when an account
	signs back in.

	Account-keyed data gets cleared when the corresponding account is
	removed from the device, using the same code path that's already used
	for other account-keyed prefs. It's also cleared when the sync server
	requests it (e.g. CLIENT_DATA_OBSOLETE), and in some error cases.

	Bug: 337034860
	Change-Id: I979b302901b91dfe220971aec838add8d22846b7
	Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5537450
2024-07-09 23:56:39 +03:00