Re: Error

3 views
Skip to first unread message

Marco Corvi

unread,
Jul 7, 2025, 2:13:27 PMJul 7
to lauren...@home.nl, topo...@googlegroups.com
as stated: without file write permission topodroid cannot work.

On Mon, Jul 7, 2025, 12:41 <lauren...@home.nl> wrote:
Dear Marco, 

i am a quite an expert on topodroid on all kind of machines. 
Now I came up with a problem while installing topodroid for a friend. 
He got a Samsung A7 tablet from 2021. 

which android version ?

I installed all kind of versions of topodroid on the tablet but get all the time the same problem. I updated software first on the tablet.started , restarted etc
After installing topodroid i get the message:
WRITE_FILE  is needed to run. Bye with a topodroid logo. See enclosed.

I cannot start up new survey. I can fill in the page for a new survey. But as soon as I push the button open or save new survey, it stops Topodroid.  I also cannot import a Zip file, as it gives the same problem. 
It looks like the program cannot find the mapfiles to write to. Or it cannot write at all. 

You got a solution??

Thx
Laurens


Verzonden vanaf Outlook voor Android

Rodrigo Severo

unread,
Jul 8, 2025, 3:21:41 PMJul 8
to topo...@googlegroups.com
I got this same problem when I installedTopoDroid  for the first time on a device. It was version 6.3.37.

To fix it I had to uninstall it, delete the TDX folder and install version 6.3.20. At this moment I managed to create or import a topo.

After that I managed to update to 6.3.37 without further issues.


Rodrigo


--
You received this message because you are subscribed to the Google Groups "TopoDroid" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topodroid+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/topodroid/CAJiQYo0Rk4OihdUYHviGaHVKZAcV7ZuJ1wqAMUVp6DqvFJVzqw%40mail.gmail.com.

Marco Corvi

unread,
Jul 9, 2025, 5:19:49 AMJul 9
to topo...@googlegroups.com
thanks rodrigo,

there was an error in the database create statements.
it should be fixed with v. 6.3.38


Reply all
Reply to author
Forward
0 new messages