Optimizations on top of original idea by @XspeedPL.
- introduced new manifest parameter: xposedsharedprefswatcher
- file watcher daemon starts only in case there is at least one module in the hooked process that requested file watcher feature either by specification in the
manifest or using new constructor XSharedPreferences(file, enableWatcher)
- XSharedPreferences instance registers watcher events only when it has support for watcher enabled so even if watcher daemon is already running
due to request by other module, it won't watch for events on files that belong to XSharedPreferences instance that has watcher disabled
- reduced log ouput in case of release builds
This would help to resolve the issue: now the user can look into that file and see what's inside an try to resolve the issue or fixing/cleaning up that file.
C3C0
Xspeed
Jim Wu
LoveSy
kotori0
binarynoise
solohsu