Package Details: better-adb-sync-git r91.9a226dd-1

Git Clone URL: https://aur.archlinux.org/better-adb-sync-git.git (read-only, click to copy)
Package Base: better-adb-sync-git
Description: Synchronize files between a PC and an Android device using ADB (Android Debug Bridge)
Upstream URL: https://github.com/jpstotz/better-adb-sync
Keywords: adb android synchronization
Licenses: Apache
Conflicts: better-adb-sync
Provides: better-adb-sync
Submitter: willemw
Maintainer: willemw
Last Packager: willemw
Votes: 9
Popularity: 0.020853
First Submitted: 2022-11-11 08:05 (UTC)
Last Updated: 2026-01-11 16:41 (UTC)

Latest Comments

moginheden commented on 2026-02-01 03:33 (UTC)

This fixed it:

paru -S better-adb-sync-git --rebuild⁩

willemw commented on 2026-01-31 11:18 (UTC) (edited on 2026-01-31 11:18 (UTC) by willemw)

@moginheden: I am guessing, because the traceback stacktrace is not detailed enough. Have you rebuilt all out-of-date Python packages? All "site-packages" Python files need to be installed in a single /usr/lib/python3.*/site-packages folder. For example, rebuild all out-of-date packages listed by pacman -Qo /usr/lib/python3.13/site-packages.

moginheden commented on 2026-01-30 23:22 (UTC) (edited on 2026-01-30 23:24 (UTC) by moginheden)

This worked 2 weeks ago on CachyOS after installing with Paru, but now when I run adbsync I'm getting:

Traceback (most recent call last): File "/usr/bin/adbsync", line 5, in <module> from BetterADBSync import main ModuleNotFoundError: No module named 'BetterADBSync'

I tried: paru -R better-adb-sync-git

paru better-adb-sync-git

It still says it can't find BetterADBSync. Is something wrong with this package, or do I need to clear something to use the new jpstotz fork?

lightdot commented on 2026-01-19 10:37 (UTC)

A quick glance over the "Fix date problems on Windows" commit doesn't show anything special.

I'm not using the package actively right now, or I'd confirm or deny replicating this. Perhaps someone else can do so, and a bug report can be opened upstream.

rwuo commented on 2026-01-19 09:32 (UTC)

@willemw: I have investigated a bit further. For me it seems that the new fork gets file times wrong (possibly related to a commit called "Fix date problems on Windows"). Not sure if it is connected to daylight saving time. You can replicate the problem by creating a new file on the phone, check mtime, transfer with adbsync and observe mtime to be 1h off. This will not only re-sync already existing files (since they appear 1h newer) but also corrupt all the mtimes of these files and future files. I have reverted back to the original jb2170 fork and that still works fine. I feel like this issue should be solved before people relying on that package blindly corrupt their file times.

rwuo commented on 2026-01-15 09:42 (UTC)

@willemw: thanks for maintaining this great package! One thing that I noted since the fork switch: Regularly syncing quite a big folder from Android to Local which had many existing files already - what was surprising is that upon first time running the new jpstotz fork command it initially deleted all the existing local files and only then started re-syncing the complete folder! I assume that is because it uses a different form of file comparison? (because each subsequent sync/pull it now works as intended, i.e. not re-syncing the existing files) Posting this since the fact about initially deleting all local files might be important to some users. Thanks again.

willemw commented on 2026-01-11 16:44 (UTC)

@jerf: switched to the jpstotz/better-adb-sync fork.

You probably need to clean the better-adb-sync build cache first.

jerf commented on 2026-01-11 12:45 (UTC) (edited on 2026-01-11 12:45 (UTC) by jerf)

I suggest updating the pkgbuild to use the following fork of better-adb-sync: https://github.com/jpstotz/better-adb-sync

It fixes several issues present in the original better-adb-sync (which seems to be no longer maintained, already for quite some time).

Aftermath commented on 2023-09-24 11:05 (UTC)

Thanks for maintenance.