[media] apex update media, but next reboot, media crash [391417816]

Assigned

Bug

[AOSP] assigned

Status Update

No update yet.

Description

po...@gmail.com

created issue #1

Jan 22, 2025 06:11AM

To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted (

https://developers.google.com/issue-tracker/concepts/restricted-content)” when creating a bug or adding a comment. Restricting or deleting your comment or attachment can also be done using the overflow menu after submitting.

Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (

https://policies.google.com/privacy), and you agree that we may share it with engineering partners potentially impacted by your issue.

Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes

android version: android V

email: wonder.wang@cooseagroup.corp-partner.google.com

Question: After the machine was restored to factory settings, all special features were enabled, and all applications were updated. Once the preconditions for testing were prepared, testing was conducted for one hour. Then the device was left on standby overnight. In the morning, after manually rebooting, an automatic restart occurred.

./kernel_log_6__2025_0110_235250:123048:<14>[ 1151.981728][T23966] apexd: Found "/apex/com.android.media@350820420" backed by file /data/apex/decompressed/com.android.media@350820420.decompressed.apex
./kernel_log_6__2025_0110_235250:412334:<14>[ 5176.195418][ T5556] apexd-unmount-all: Found "/apex/com.android.media@351010060" backed by file /data/app-staging/session_1277534585/com.google.android.media.apex
./kernel_log_6__2025_0110_235250:398395:<14>[ 4605.458574][ T3803] apexd-otachroot: Successfully mounted package /data/app-staging/session_1277534585/com.google.android.media.apex on /apex/com.android.media@351010060 duration=472

[ 52.254750][ T1] init: starting service 'media'...
[ 52.273076][ T674] apexd: Native process 'media' is crashing. Attempting a revert
[ 52.274601][ T674] apexd: Not restoring active packages in checkpoint mode.
[ 52.275772][ T674] apexd: Successfully reverted. Time to reboot device.
[ 52.277949][ T674] apexd: Rebooting device
[ 52.279504][ T1] hang_detect: init set reboot command.

Thanks

Comments

wo...@cooseagroup.corp-partner.google.com <wo...@cooseagroup.corp-partner.google.com> #2Jan 22, 2025 06:16AM

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

debuglogger.zip

Restricted

81 MB

Download

vi...@google.com <vi...@google.com> Jan 22, 2025 02:48PM

Assigned to vi...@google.com.

vi...@google.com <vi...@google.com> #3Jan 22, 2025 03:56PM

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.

wo...@cooseagroup.corp-partner.google.com <wo...@cooseagroup.corp-partner.google.com> #4Feb 12, 2025 01:31AM

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"

wo...@cooseagroup.corp-partner.google.com <wo...@cooseagroup.corp-partner.google.com> #5Feb 17, 2025 09:34AM

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

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

wo...@cooseagroup.corp-partner.google.com <wo...@cooseagroup.corp-partner.google.com> #6Feb 21, 2025 09:24AM

+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 391417816