View Single Post
Old 03-12-2024, 05:37 AM   #53
neil_swann80
0000000000101010
neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.neil_swann80 ought to be getting tired of karma fortunes by now.
 
neil_swann80's Avatar
 
Posts: 5,897
Karma: 12981955
Join Date: Mar 2023
Location: An island off the coast of Ireland
Device: PB632 [HD3]
Quote:
Originally Posted by llaumgui View Post
And remove .lock can be solution ?
I'm not sure, might be an encrypted and profile specific part of the database.
How big is the .lock file compared to the standard .db?

You could try renaming this file and rebooting... but at your own peril as I have no idea what effect it will have on your database and read history/progress etc. (Renaming it again afterwards may not restore lost functionality).

Unless you're in a rush, wait for me to test and mess up my own device!

Last edited by neil_swann80; 03-12-2024 at 05:40 AM.
neil_swann80 is offline   Reply With Quote