Revision history [back]

Strangely, the tag combination SailfishX + filesystem returns no thread (so far). Nevertheless, my Xperia X with SailfishX (2.1.3.5) has an unexpected behavior in some circumstances:

(i) file managers in 'root' mode (with Schtuman's hacks) usually fail to access root-protected resources, but may succeed after 'some' (not too short, not too long) waiting (filebrowser, cargodock, filetug, filecase with 'startasroot').

(ii) patchmanager 2.0 (in settings) displays a couple of patches in red, meaning "not compatible with current OS release", although those patches are actually installed and enabled. A new attempt a couple of minutes later may show (not always) all patches OK with current OS.

Is there any utility to manage/improve/repair the file system in case of need?

Strangely, the tag combination SailfishX + filesystem returns no thread (so far). Nevertheless, my Xperia X with SailfishX (2.1.3.5) has an unexpected behavior in some circumstances:

(i) file managers in 'root' mode (with Schtuman's Schturman's hacks) usually fail to access root-protected resources, but may succeed after 'some' (not too short, not too long) waiting (filebrowser, cargodock, filetug, filecase with 'startasroot').

(ii) patchmanager 2.0 (in settings) displays a couple of patches in red, meaning "not compatible with current OS release", although those patches are actually installed and enabled. A new attempt a couple of minutes later may show (not always) all patches OK with current OS.

Is there any utility to manage/improve/repair the file system in case of need?

Strangely, the tag combination SailfishX + filesystem returns no thread (so far). Nevertheless, my Xperia X with SailfishX (2.1.3.5) has an unexpected behavior in some circumstances:

(i) file managers in 'root' mode (with Schturman's hacks) usually fail to access root-protected resources, but may succeed after 'some' (not too short, not too long) waiting (filebrowser, cargodock, filetug, filecase with 'startasroot').

(ii) patchmanager 2.0 (in settings) displays a couple of patches in red, meaning "not compatible with current OS release", although those patches are actually installed and enabled. A new attempt a couple of minutes later may show (not always) all patches OK with current OS.

Is there any utility to manage/improve/repair the file system in case of need?

Strangely, the tag combination SailfishX + filesystem returns no thread (so far). Nevertheless, my Xperia X with SailfishX (2.1.3.5) has an unexpected behavior in some circumstances:

(i) file managers in 'root' mode (with Schturman's hacks) usually fail to access root-protected resources, but may succeed after 'some' (not too short, not too long) waiting (filebrowser, cargodock, filetug, filecase with 'startasroot').

(ii) patchmanager 2.0 (in settings) displays a couple of patches in red, meaning "not compatible with current OS release", although those patches are actually installed and enabled. enabled (and working). A new attempt a couple of minutes later may show (not always) all patches OK with current OS.

Is there any utility to manage/improve/repair the file system in case of need?

Strangely, the tag combination SailfishX + filesystem returns no thread (so far). Nevertheless, my Xperia X with SailfishX (2.1.3.5) has an unexpected behavior in some circumstances:

(i) file managers in 'root' mode (with Schturman's hacks) usually fail to access root-protected resources, but may succeed after 'some' (not too short, not too long) waiting (filebrowser, cargodock, filetug, filecase with 'startasroot').

(ii) patchmanager 2.0 (in settings) displays a couple of patches in red, meaning "not compatible with current OS release", although those patches are actually installed and enabled (and working). A new attempt a couple of minutes later may show (not always) all patches OK with current OS.

Is there any utility to manage/improve/repair the file system in case of need?

Strangely, the tag combination SailfishX + filesystem returns no thread (so far). Nevertheless, my Xperia X with SailfishX (2.1.3.5) has an unexpected unexpected/unpredictable behavior in some circumstances:

(i) file managers in 'root' mode (with Schturman's hacks) usually fail to access root-protected resources, but may succeed after 'some' (not too short, not too long) waiting (filebrowser, cargodock, filetug, filecase with 'startasroot').

(ii) patchmanager 2.0 (in settings) displays a couple of patches in red, meaning "not compatible with current OS release", although those patches are actually installed and enabled (and working). A new attempt a couple of minutes later may show (not always) all patches OK with current OS.

Is there any utility to manage/improve/repair the file system in case of need?