kartaview / openstreetcam.org

The openstreetcam.org web site
MIT License
76 stars 10 forks source link

Remaining "storage limit reached" message despite a lot of free memory #110

Open derSoe opened 7 years ago

derSoe commented 7 years ago

When I try to start recording a track the app tells me after the first picture that the storage limit is reached and stops recording. However, I've got 6.5GB free memory.

Previous to that I recorded a long track that indeed may have reached the storage limit. I did not check. In any case, the recording stopped sometime. After loading the track up I wanted to start a new record but since then it shows the above described behavior. Removing and installing the app again has no effect.

App Version: 2.0.2 System: Sailfish OS with alien dalvik (= Android 4.1)

Maybe you could at least name a file I have delete to work around this. That would help much.

Thanks in advance!

Regards, sö

james2432 commented 7 years ago

Just to be clear memory and storage space are not the same thing. Do you have 6.5GB of storage left? It may be your alien dalvik that is reporting wrong free space, or has an imposed limit on how much it can use. Also because sailfish is linux based, it might have reserved a bigger portion to the root (/) vs the /home Where you could be writing. Check "df -h" and make sure the partition you have is actually the one that has the freespace.

No issues with freespace on native android.

brusspi commented 7 years ago

I have the same problem. At a given time the recording stopped with the message that I have reached the storage limit. After uploading the pictures and trying to take other pictures, I get that message again and I can't capture no longer.

Regards, Pieter

derSoe commented 7 years ago

@Pieter Are you using the app on native android?

@james2432 I checked free space. The whole remaining space is available for the alien. (Sorry for not answering until now. I just forgot it.) Meanwhile I observed the behavior and it is reliably reproducible. I found out that loading a large file with another android app (an OSM map of several hundred MB) fixes the error condition. Recording a long track restores it.

brusspi commented 7 years ago

@derSoe I'm using a fairphone1 with Android 4.2.2

derSoe commented 7 years ago

Thumbs up! :) Maybe the problem is related to our old Android versions...

brusspi commented 7 years ago

It means that you are working on an update version of the app?

derSoe commented 7 years ago

I'm not if I understood your question correctly. I'm currently using version 2.0.2 of the app.

brusspi commented 7 years ago

my version of the app is 2.0.8

derSoe commented 7 years ago

2.0.2 is the latest version in the dropbox folder linked to at the homepage. It is the only way to get the app without using Google stuff. The .apk is called "latest". Seems not to be true... Anyway, the issue seems not to be related to the app version.

kalmanbencze commented 7 years ago

Sorry about the confusion related to the latest version, I have updated the apks on dropbox, you can go ahead and download the latest build which is the beta 2.0.10. (2.0.8 being the latest release version) Unfortunately the access link got modified, you can use this link until it is fixed on the site: https://www.dropbox.com/s/xoxv175fgkhz2zr/app-release-latest.apk?dl=0

derSoe commented 7 years ago

@kalmanbencze Never mind! Many thanks!

kalmanbencze commented 7 years ago

I'll try to investigate the issue with storage space, but the check relies on the native api's storage access, and if the partition table or the symlinks are modified it could lead to unexpected behaviour.

xkomczax commented 6 years ago

The same issue here :-( OpenStreetCam version: 2.1.4 Android version: 4.1.2