Hi,
In my Auto upload settings, Original file will be... is greyed out and cannot be enabled for the camera folders:
- /storage/emulated/0/DCIM/Camera
- /storage/emulated/0/Pictures/Screenshots
Any idea why?
yes… there are several ideas why.
but maybe you want to enlighten us with some additional infos about the “faulty” systems?
or you might wanna do a search of the forum yourself and find the solution?
I’m not sure how up-to-date the following open issue is now that Nextcloud and Google have come to an agreement regarding the permissions issue. If I were you, I would check whether the app is up to date, test to reinstall the app and test the F-Droid version if necessary.
But I don’t have any further advice.
I normally rely on the forum’s recommendation as I type my post to determine if someone has already asked a similar question.
In this case, it would have been so much easier if nextcloud added an badge next to the Original file will be... to explain its behavior would be different depending on where you installed the apk from.
Instead, what happened is that hundreds of folks had to ask this question over and again.
Reasonably speaking, how many OSes can control the permissions of their applications depending on where they were installed from? This is not the norm and requires education per my suggestion above.
I will be deleting this question.
Update: Sadly, I can’t delete to maintain good discussions on this forum
@mritzmann thanks, I switched to the F-Droid version, but had to re-do all my settings.
@mritzmann Thanks, Markus, for doing the search for them.
I don’t know the answer to that question. But I know that G00gle apparently can do that. Like a pure blackmailing: Remove this and that permissions or you can’t publish your app anymore on our store. As simple as that. And yes, it’s their store so they can command you doing what they like… or face the consequences. You don’t like that? Fine, go to G00gle and complain about it. I’m sure they will change their behaviour immediately after learning of your complaints.
So … the situation was like this: NC had to change the App-version for G00gle to meet their goals. If they liked it or not. And they kept the original App-version on f-droid. This explains well those 2 different versions.
no. they simply didn’t HAD to do that. They just did because they didn’t search the forum, my dear. The answers to the questions were up pretty close to the initial question.. well and on a sidenote to that… I counted every single question referring to that problem… it was exactly 100175757 questions. Not only “hundreds”.
sure enough… this is still an open issue which would need someone taking care about it. It seems that we finally found a volunteer dev for it: YOU!
And well… if you are in train doing that you could develop another “badge”-functionality enabling the common user to just click on “repair” with the software behind it doing all the rest. A dream would come true!
well, dear… if you would have only read the links that were provided to you by Markus above you would have gotten to know the story behind your “problem”. you apparently didn’t since the visit-counter on the links still shows “0”. (3.6.26/6:15h am)
Le sigh…
Thanks for your contribution on here.
Happy NC’ing
NB: indeed as several ppl seem to have complained at G. they changed their mind and now do allow new app-versions with full permissions again. So you can be sure that one of the next G-versions would work again as expected. THAT’S the power of a community and NC-users.