# Keep getting conflicts generated on Android device for files modified only on a desktop PC

**URL:** https://forum.syncthing.net/t/keep-getting-conflicts-generated-on-android-device-for-files-modified-only-on-a-desktop-pc/19060
**Category:** Android
**Created:** [October 6, 2022, 10:19pm UTC](https://forum.syncthing.net/t/keep-getting-conflicts-generated-on-android-device-for-files-modified-only-on-a-desktop-pc/19060 "2022-10-06T22:19:51Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [November 5, 2022, 11:05am UTC](https://forum.syncthing.net/t/keep-getting-conflicts-generated-on-android-device-for-files-modified-only-on-a-desktop-pc/19060/17 "2022-11-05T11:05:50Z")

</div>

Could be the inode change time check, which is new. If the underlying FS doesn’t support it, like FAT, it probably returns the mtime instead, which is fine. If the underlying FS is a lie and the mtime/inode-change-time fluctuates, as might be the case on Android, weird things will happen. Maybe we should disable that code on Android. You, as a self-compiler, might try to add a `if runtimeos.IsAndroid { return time.Time{} }` at the top of `(basicFileInfo)InodeChangeTime()` in `fs/basicfs_fileinfo_linuxish.go`.

---

_[View the full topic](https://forum.syncthing.net/t/keep-getting-conflicts-generated-on-android-device-for-files-modified-only-on-a-desktop-pc/19060)._