Infeasible
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.
md...@gmail.com <md...@gmail.com> #3
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.
ra...@google.com <ra...@google.com> #4
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"
"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"
md...@gmail.com <md...@gmail.com> #5
Experiencing the same issues, please see my other report for any useful logs:
https://issuetracker.google.com/issues/235673375
vi...@google.com <vi...@google.com> #6
+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
vi...@google.com <vi...@google.com> #7
Note that I've been able to make it work by:
- Adding
<action android:name="com.google.android.gms.wearable.BIND_LISTENER" />
in the intent filter - Removing
<data android:scheme="wear" android:host="*" />
But I feel like this is not something we should do
Description
I'm using the MediaExtractor and MediaCodec to open and decode a 4-channel FLAC audio file.
I can open the file, configure the codec and "see" it trying to read and decode, but it seems the MediaExtractor is failing to advance while reading. By "see" I mean that in asynchronous mode, the codec calls the callbacks like normal. In synchronous mode, I get what appears to be the right number of input and output buffers when queried. I get many callbacks for input buffers but every time I call
ex.readSampleData()
/ex.advance()
the time fromex.getSampleTime()
never moves off of 0 until the last two callbacks.ex.advance()
returnstrue
until the last two calls to it.On those last two calls,
ex.advance()
returnsfalse
andex.getSampleTime()
returns 2, thenex.advance()
returnsfalse
andex.getSampleTime()
returns 3.Devices tested:
I'm pretty sure this worked previously on the S24+ but is now failing. I'm guessing a recent system update broke it.
The S24+ Software info lists:
Kernel: 6.1.75-android14-11-295443898-ab5926USQS4AXL3
#1 Tue Dec 24 02:23:32 UTC 2024
I recently received an update for the phone which moved the software version to:
#1 Mon Jan 13 04:08:44 UTC 2025
The API level of the S24+ is reported as 34-ext15 in the device manager of Android Studio.
Below is a snippet of code that I use to process the file.