Decompressive transcoding with more compression schemes [139143567]

Assigned

Feature Request

adexe s nau

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

Aug 9, 2019 12:13PM

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:
Upload a Brotli compressed file and have GCS perform decompressive transcoding on requests from clients that don't "Accept-Encoding: br" similarly to how GCS already does for gzip.
Even better would be to upload multiple compressed versions of a fileand have GCS select between them.

How this might work:
Like for gzip transcoding, but with other algorithms.

If applicable, reasons why alternative solutions are not sufficient:
gzip is good but I can save more megabytes with Brotli.

Other information (workarounds you have tried, documentation consulted, etc):
I implemented my own server to handle the Accept-Encoding header, but lost the benefits of a CDN and it was much more expensive to run.

Comments

di...@google.com <di...@google.com> #2Aug 9, 2019 11:53PM

Assigned to gc...@google.com.

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

cs...@gmail.com <cs...@gmail.com> #3Aug 23, 2019 08:08PM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

da...@gmail.com <da...@gmail.com> #4Feb 10, 2022 11:33PM

Also, I'm seeing this message in the Logcat:

"2022-06-12 18:47:15.156 1841-4562/? W/PackageManager: Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER"

Message last modified on Feb 10, 2022 11:36PM

[Deleted User] <[Deleted User]> #5Aug 4, 2022 08:05AM

Experiencing the same issues, please see my other report for any useful logs:

https://issuetracker.google.com/issues/235673375

ic...@hopper.com <ic...@hopper.com> #6Jan 26, 2023 01:14AM

+1, can confirm it doesn't work on Android 13:=

2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver }
2022-07-15 11:26:15.023   589-5347  PackageManager          pid-589                              W  Access blocked: ComponentInfo{xxx/xxx.WatchMessageReceiver}
2022-07-15 11:26:15.023   589-5347  ActivityManager         pid-589                              W  Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=xxx/xxx.WatchMessageReceiver } U=0: not found

Issue 139143567