I upgraded to Proton Unlimited today and I’ve set Proton Drive to back up my whole camera gallery, a few hundreds of GBs, so it will take a while. But I noticed that it skips large videos, e.g. it skipped a 9.8GB video file. Is this intended behavior? I can’t find documentation of it anywhere and it seems to happen silently. I easily could have missed it, assumed that it backed up everything down to a certain date, and deleted the only copy of the videos.
Unrelated to that, I think I’ve found a bug: every once in a while, the process stops, complains about low device storage and I have to push “retry” - after which it keeps going. It seems like the app doesn’t clear its temporary files until it fails due to low storage. I can see the app’s size growing and growing to over 50GB - which at the moment is all the free space I have - and then, when it hits the wall, suddenly shrink back to 144MB. The largest single file in the Camera folder is 17GB. Then I have to open the app manually and tell it to retry. This means I have to babysit it and can’t have it back up everything overnight.
Here’s some screenshots:
… later …
then:
It probably needs some space to compress/archive the files to transmit and not just send them as they are. At least that could be an explanation why local device storage is needed - and it seems you’re running petty low on that
It doesn’t need 3x the size of the biggest file it needs to compress.
Maybe it does some parallelization?
But yeah, that should be enough storage
Thanks. Maybe it does, but as you say that still doesn’t explain it and it should still have ample space. Most of the files are photos or very short videos, and it’s definitely uploading them in order. It wouldn’t parallelize more than, say, 5 at a time. As my OP says it completely skips the biggest videos, so it has a cutoff of (I’m estimating) 5GB or so? So at worst it’s going to deal with two 5GB videos and 3 relatively tiny photos/videos simultaneously. 55GB is plenty for this scenario.
Also, this doesn’t mean much but it doesn’t feel like it’s parallelized. I think it’s just doing them sequentially. Just my hunch though, nothing conclusive.
And you know that how?
Many moons ago, working with command-line compression tools, they definitely needed 2.5x+ working space to compress things.
Android needs some free space to function. 99% full? Hahah, you’re kidding, right? Nothing will work right when storage is that full, with pretty much any OS.
99% full was when Proton Drive was using all the storage it could before it gave up. Half the reason I want to use Proton Drive is to free up storage space on my phone.
Edit: and factually it works if I just tell it to retry (until the next time it runs out of space) so any excuse you make for it is bullshit. I hope Proton support/devs would take this more seriously than that.
Please be respectful of other user’s comments, even if they don’t share your perspective. We don’t allow that kind of vocabulary around here.
Thanks!
Fair enough, I changed the offensive word. You should probably take a look at how BearOfaTime basically implied I’m an idiot.