Doubts regarding QLockFile and QSettings

[d_stranz]

From the QSettings documentation:

Accessing Settings from Multiple Threads or Processes Simultaneously

QSettings is reentrant. This means that you can use distinct QSettings object in different threads simultaneously. This guarantee stands even when the QSettings objects refer to the same files on disk (or to the same entries in the system registry). If a setting is modified through one QSettings object, the change will immediately be visible in any other QSettings objects that operate on the same location and that live in the same process.

QSettings can safely be used from different processes (which can be different instances of your application running at the same time or different applications altogether) to read and write to the same system locations. It uses advisory file locking and a smart merging algorithm to ensure data integrity. Note that sync() imports changes made by other processes (in addition to writing the changes from this QSettings).

Even though you are using QSettings instances within the same thread, these comments still apply.

[pradesah]

Thank you. This removes the suspect.

The main problem still remains. As I mentioned, upon application reset and device reboot, the lock files are still present in the file location.
Will try with setStaleLockTime(0), removeStaleLockFile() etc and see if any of these helps.