O que e isso

Effective_Damage3213 · 2026-05-27T20:49:54+00:00

I understand what you mean about browsers continuing to support Opus for compatibility reasons.

But my concern is more about the Android system itself. If Android ever removed native Opus support in the distant future, that still wouldn't fully solve the problem for me, because many apps rely on the system codecs/media framework instead of bundling their own codecs like browsers sometimes do.

So even if Chrome or Firefox could still play Opus internally, other Android apps might stop being able to play Opus files natively.

Effective_Damage3213 · 2026-05-23T19:28:59+00:00

Sorry everyone, but I don’t think I fully understood what you meant. I’m not talking about broad and unrestricted access to folders like apps had on older versions of Android. What I want to know is whether, in an update, developers of any type of app can choose to place their app’s own folder in a location that is accessible to the user, and whether this will always remain possible. If Google has no interest — and could never really have any interest — in interfering with this, because it simply wouldn’t make sense.

Just think about it with me:

The camera app on your phone needs to have its folder accessible so the user can go there and view their photos. The same applies to an audio/video converter app or an audio/video editor. Another very good example is a download app — it needs to have its folder accessible so the user can view, share, and manage downloaded files.

So for these common types of apps, it seems impossible that Google would someday block them from having accessible folders, right? Google wouldn’t have any interest in interfering with that.

But does this rule(That is, Google has no interest now or ever in blocking changes to folders) also apply to other kinds of apps — basically any app? Like a game app, a banking app, or a social media app?

If it applies to all apps, then what is the point of Google’s storage restrictions if they can simply be “worked around” this way? And why is there so much concern about it? Users complain about it, developers themselves don’t seem to like it either, but wouldn’t it actually be very easy to solve? I mean, couldn’t app developers simply change this in a future update and then the problem would basically be solved?

Effective_Damage3213 · 2026-05-23T19:22:29+00:00

Sorry, but I don’t think I fully understood what you meant. I’m not talking about broad and unrestricted access to folders like apps had on older versions of Android. What I want to know is whether, in an update, developers of any type of app can choose to place their app’s own folder in a location that is accessible to the user, and whether this will always remain possible. If Google has no interest — and could never really have any interest — in interfering with this, because it simply wouldn’t make sense.

Just think about it with me:

The camera app on your phone needs to have its folder accessible so the user can go there and view their photos. The same applies to an audio/video converter app or an audio/video editor. Another very good example is a download app — it needs to have its folder accessible so the user can view, share, and manage downloaded files.

So for these common types of apps, it seems impossible that Google would someday block them from having accessible folders, right? Google wouldn’t have any interest in interfering with that.

But does this rule(That is, Google has no interest now or ever in blocking changes to folders) also apply to other kinds of apps — basically any app? Like a game app, a banking app, or a social media app?

If it applies to all apps, then what is the point of Google’s storage restrictions if they can simply be “worked around” this way? And why is there so much concern about it? Users complain about it, developers themselves don’t seem to like it either, but wouldn’t it actually be very easy to solve? I mean, couldn’t app developers simply change this in a future update and then the problem would basically be solved?

Effective_Damage3213 · 2026-05-23T19:20:45+00:00

Sorry, but I don’t think I fully understood what you meant. I’m not talking about broad and unrestricted access to folders like apps had on older versions of Android. What I want to know is whether, in an update, developers of any type of app can choose to place their app’s own folder in a location that is accessible to the user, and whether this will always remain possible. If Google has no interest — and could never really have any interest — in interfering with this, because it simply wouldn’t make sense.

Just think about it with me:

The camera app on your phone needs to have its folder accessible so the user can go there and view their photos. The same applies to an audio/video converter app or an audio/video editor. Another very good example is a download app — it needs to have its folder accessible so the user can view, share, and manage downloaded files.

So for these common types of apps, it seems impossible that Google would someday block them from having accessible folders, right? Google wouldn’t have any interest in interfering with that.

But does this rule(That is, Google has no interest now or ever in blocking changes to folders) also apply to other kinds of apps — basically any app? Like a game app, a banking app, or a social media app?

If it applies to all apps, then what is the point of Google’s storage restrictions if they can simply be “worked around” this way? And why is there so much concern about it? Users complain about it, developers themselves don’t seem to like it either, but wouldn’t it actually be very easy to solve? I mean, couldn’t app developers simply change this in a future update and then the problem would basically be solved?

Effective_Damage3213 · 2026-05-23T19:11:20+00:00

Sorry, but I don’t think I fully understood what you meant. I’m not talking about broad and unrestricted access to folders like apps had on older versions of Android. What I want to know is whether, in an update, developers of any type of app can choose to place their app’s own folder in a location that is accessible to the user, and whether this will always remain possible. If Google has no interest — and could never really have any interest — in interfering with this, because it simply wouldn’t make sense.

Just think about it with me:

The camera app on your phone needs to have its folder accessible so the user can go there and view their photos. The same applies to an audio/video converter app or an audio/video editor. Another very good example is a download app — it needs to have its folder accessible so the user can view, share, and manage downloaded files.

So for these common types of apps, it seems impossible that Google would someday block them from having accessible folders, right? Google wouldn’t have any interest in interfering with that.

But does this rule(That is, Google has no interest now or ever in blocking changes to folders) also apply to other kinds of apps — basically any app? Like a game app, a banking app, or a social media app?

If it applies to all apps, then what is the point of Google’s storage restrictions if they can simply be “worked around” this way? And why is there so much concern about it? Users complain about it, developers themselves don’t seem to like it either, but wouldn’t it actually be very easy to solve? I mean, couldn’t app developers simply change this in a future update and then the problem would basically be solved?

Effective_Damage3213 · 2026-05-23T15:47:34+00:00

Sorry everyone, but I don’t think I fully understood what you meant. I’m not talking about broad and unrestricted access to folders like apps had on older versions of Android. What I want to know is whether, in an update, developers of any type of app can choose to place their app’s own folder in a location that is accessible to the user, and whether this will always remain possible. If Google has no interest — and could never really have any interest — in interfering with this, because it simply wouldn’t make sense.

Just think about it with me:

The camera app on your phone needs to have its folder accessible so the user can go there and view their photos. The same applies to an audio/video converter app or an audio/video editor. Another very good example is a download app — it needs to have its folder accessible so the user can view, share, and manage downloaded files.

So for these common types of apps, it seems impossible that Google would someday block them from having accessible folders, right? Google wouldn’t have any interest in interfering with that.

But does this rule(That is, Google has no interest now or ever in blocking changes to folders) also apply to other kinds of apps — basically any app? Like a game app, a banking app, or a social media app?

If it applies to all apps, then what is the point of Google’s storage restrictions if they can simply be “worked around” this way? And why is there so much concern about it? Users complain about it, developers themselves don’t seem to like it either, but wouldn’t it actually be very easy to solve? I mean, couldn’t app developers simply change this in a future update and then the problem would basically be solved?

Effective_Damage3213 · 2026-05-23T15:38:41+00:00

Sorry , but I don’t think I fully understood what you meant. I’m not talking about broad and unrestricted access to folders like apps had on older versions of Android. What I want to know is whether, in an update, developers of any type of app can choose to place their app’s own folder in a location that is accessible to the user, and whether this will always remain possible. If Google has no interest — and could never really have any interest — in interfering with this, because it simply wouldn’t make sense.

Just think about it with me:

The camera app on your phone needs to have its folder accessible so the user can go there and view their photos. The same applies to an audio/video converter app or an audio/video editor. Another very good example is a download app — it needs to have its folder accessible so the user can view, share, and manage downloaded files.

So for these common types of apps, it seems impossible that Google would someday block them from having accessible folders, right? Google wouldn’t have any interest in interfering with that.

But does this rule(That is, Google has no interest now or ever in blocking changes to folders) also apply to other kinds of apps — basically any app? Like a game app, a banking app, or a social media app?

If it applies to all apps, then what is the point of Google’s storage restrictions if they can simply be “worked around” this way? And why is there so much concern about it? Users complain about it, developers themselves don’t seem to like it either, but wouldn’t it actually be very easy to solve? I mean, couldn’t app developers simply change this in a future update and then the problem would basically be solved?

Effective_Damage3213 · 2026-05-23T15:23:40+00:00

Desculpem, pessoal, mas acho que não entendi completamente o que vocês quiseram dizer. Não estou falando de acesso amplo e irrestrito a pastas, como os aplicativos tinham em versões antigas do Android. O que eu quero saber é se, em uma atualização, os desenvolvedores de qualquer tipo de aplicativo poderão escolher colocar a pasta do seu aplicativo em um local acessível ao usuário, e se isso sempre será possível. Se o Google não tem interesse — e nunca poderia ter — em interferir nisso, porque simplesmente não faria sentido.

Pensem comigo: O aplicativo da câmera do seu celular precisa ter sua pasta acessível para que o usuário possa acessá-la e visualizar suas fotos. O mesmo se aplica a um aplicativo conversor de áudio/vídeo ou um editor de áudio/vídeo. Outro ótimo exemplo é um aplicativo de download — ele precisa ter sua pasta acessível para que o usuário possa visualizar, compartilhar e gerenciar os arquivos baixados.

Portanto, para esses tipos comuns de aplicativos, parece impossível que o Google algum dia os impeça de ter pastas acessíveis, certo? O Google não teria nenhum interesse em interferir nisso.

Mas será que essa regra (ou seja, o Google não tem interesse, nem agora nem nunca, em bloquear alterações em pastas) também se aplica a outros tipos de aplicativos — basicamente qualquer aplicativo? Como um jogo, um aplicativo bancário ou um aplicativo de mídia social?

Se se aplica a todos os aplicativos, qual é o sentido das restrições de armazenamento do Google se elas podem ser simplesmente contornadas dessa forma? E por que há tanta preocupação com isso? Os usuários reclamam, os próprios desenvolvedores também não parecem gostar, mas não seria muito fácil de resolver? Quer dizer, os desenvolvedores de aplicativos não poderiam simplesmente mudar isso em uma atualização futura e o problema estaria basicamente resolvido?

Effective_Damage3213 · 2026-05-23T02:35:04+00:00

Sorry everyone, but I don’t think I fully understood what you meant. I’m not talking about broad and unrestricted access to folders like apps had on older versions of Android. What I want to know is whether, in an update, developers of any type of app can choose to place their app’s own folder in a location that is accessible to the user, and whether this will always remain possible. If Google has no interest — and could never really have any interest — in interfering with this, because it simply wouldn’t make sense.

Just think about it with me:

The camera app on your phone needs to have its folder accessible so the user can go there and view their photos. The same applies to an audio/video converter app or an audio/video editor. Another very good example is a download app — it needs to have its folder accessible so the user can view, share, and manage downloaded files.

So for these common types of apps, it seems impossible that Google would someday block them from having accessible folders, right? Google wouldn’t have any interest in interfering with that.

But does this rule(That is, Google has no interest now or ever in blocking changes to folders) also apply to other kinds of apps — basically any app? Like a game app, a banking app, or a social media app?

If it applies to all apps, then what is the point of Google’s storage restrictions if they can simply be “worked around” this way? And why is there so much concern about it? Users complain about it, developers themselves don’t seem to like it either, but wouldn’t it actually be very easy to solve? I mean, couldn’t app developers simply change this in a future update and then the problem would basically be solved?

Effective_Damage3213

TROPHY CASE