Assigned

Bug

Status Update

No update yet.

Description

lu...@gmail.com

created issue #1

Aug 12, 2022 11:15AM

It appears that android does never set the hardware volume of USB DACs/USB 3.5mm adapters and instead uses whatever the default is. On some DACs/Adapters, this is problematic, because the default volume is pretty low, for example the Apple USB C - 3.5mm adapter. It reports a range of -15360 to 0 1/256dB range, it defaults to -5120.

Since android uses software volume control and never touches the hardware volume of USB DACs, the expected behaviour should be to set the hardware volume of USB DACs to the maximum possible value (e.g. in kernel/sound/usb/mixer.c, at some point do snd_usb_set_cur_mix_value(cval, [channel no.], [index no.], cval->max) ) to use the entire supported volume range of the DAC.

Comments

vi...@google.com <vi...@google.com> #2Aug 12, 2022 09:54PM

Assigned to vi...@google.com.

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3544660

Remove android specific NavControllerViewModel

Expand for full commit details

Remove android specific NavControllerViewModel 
 
Everything in NavControllerViewModel is common API so we don't need an 
Android version. Moving that code to common. 
 
Test: all tests pass 
Bug: 403616316 
 
Change-Id: Ibe154b2d04adc0a536f9a5e170cc8fbb44ed1bcf

Files:

D navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavControllerViewModel.android.kt
M navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/NavControllerViewModel.kt

Hash: 3bb40a6be709d8c7e13f56f248a6433154aec72e
Date: Fri Mar 14 21:37:30 2025

lu...@gmail.com <lu...@gmail.com> #3Aug 13, 2022 04:14PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3544945

Implement nonAndroid NavType

Expand for full commit details

Implement nonAndroid NavType 
 
Moving call common implementation of NavType to commonMain and then 
allow both the nonAndroid and Android implementation to use them. 
 
Test: all tests pass 
Bug: 403616316 
Change-Id: I297d8846859aaa719b179c7e69e993d0d6e28fd6

Files:

M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavType.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavType.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavType.nonAndroid.kt

Hash: 8f968ddbb3b8296af2033db4cf2658255fa43853
Date: Fri Mar 14 22:41:34 2025

mixer.c

Restricted

72 KB

View

Download

ra...@google.com <ra...@google.com> Aug 16, 2022 05:51AM

Status: New

pa...@google.com <pa...@google.com> Aug 16, 2022 06:45AM

Assigned to pa...@google.com.

pa...@google.com <pa...@google.com> #4Aug 18, 2022 11:39AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3555283

Change NavBackStackEntryState to SavedState

Expand for full commit details

Change NavBackStackEntryState to SavedState 
 
Instead of NavBackStackEntryState being a Parcelable, we can change it 
to use SavedState. This allows for compat with other platforms. 
 
Test: all tests pass 
Bug: 403616316 
Change-Id: I1da40e98fbc70413e0818a95cb00aa1e5aa7a3dd

Files:

M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavBackStackEntryState.android.kt
M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavController.android.kt
A navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/NavBackStackEntryState.kt
A navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/internal/NavBackStackEntryStateImpl.kt
A navigation/navigation-runtime/src/nonAndroidMain/kotlin/androidx/navigation/NavBackStackEntryState.nonAndroid.kt

Hash: 52447f8ffb1f3e1f9890f8bb9d1ac1690aad508d
Date: Thu Mar 20 19:48:37 2025

lu...@gmail.com <lu...@gmail.com> #5Aug 18, 2022 07:38PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3555586

Introduce NavContext

Expand for full commit details

Introduce NavContext 
 
Providing a multiplatform compatible version of Context that can be 
used across navigation. 
 
RelNote: "Added multi-platform NavContext that helps to wrap Android's context." 
Test: all tests pass 
Bug: 403616316 
Change-Id: Ic4b1249ea6dc1a363855a4162ef136bf74809256

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavBackStackEntry.android.kt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavDestination.android.kt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavGraph.android.kt
A navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/internal/NavContext.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavBackStackEntry.kt
A navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/internal/NavContext.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavBackStackEntry.nonAndroid.kt
A navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/internal/NavContext.nonAndroid.kt
M navigation/navigation-runtime/src/androidInstrumentedTest/kotlin/androidx/navigation/NavBackStackEntryTest.kt
M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavBackStackEntryState.android.kt
M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavController.android.kt
M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavDeepLinkBuilder.android.kt
M navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/NavController.kt
M navigation/navigation-runtime/src/nonAndroidMain/kotlin/androidx/navigation/NavController.nonAndroid.kt
M navigation/navigation-testing/src/androidMain/kotlin/androidx/navigation/testing/TestNavigatorState.android.kt
M navigation/navigation-ui/src/main/java/androidx/navigation/ui/NavigationUI.kt

Hash: 11b876fc10dec008f1f3b979795470f92ed4bb19
Date: Fri Mar 21 15:15:05 2025

98...@gmail.com <98...@gmail.com> #6Jan 1, 2023 05:50AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3561523

Introduce AtomicInt

Expand for full commit details

Introduce AtomicInt 
 
Adding a multi-platform AtomicInteger implementation and using it in 
NavController. 
 
Test: all tests pass 
Bug: 403616316 
Change-Id: I4126b3b9f946bd651afe06a242194e6f2d40302c

Files:

M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavController.android.kt
A navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/internal/AtomicInt.android.kt
A navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/internal/AtomicInt.kt
A navigation/navigation-runtime/src/nonAndroidMain/kotlin/androidx/navigation/internal/AtomicInt.nonAndroid.kt

Hash: f6fe240b918e01ca382e741b728f43c068e3d9db
Date: Tue Mar 25 19:34:06 2025

al...@gmail.com <al...@gmail.com> #7Feb 2, 2023 01:02PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3552203

Provide NavController implementation in common

Expand for full commit details

Provide NavController implementation in common 
 
Adding a new internal NavControllerImpl to clean up NavController 
implementation. 
 
RelNote: N/A 
Test: all tests pass 
Bug: 403616316 
Change-Id: I7aee97b1c3a497803534480cb10205fdf0455310

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavDestination.nonAndroid.kt
M navigation/navigation-runtime/bcv/native/current.txt
M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavController.android.kt
M navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/NavController.kt
A navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/internal/NavControllerImpl.kt
M navigation/navigation-runtime/src/nonAndroidMain/kotlin/androidx/navigation/NavController.nonAndroid.kt

Hash: 08d41ac1a7d63948d9747e5572e9bc47e2c539d6
Date: Wed Mar 26 07:51:37 2025

pr...@gmail.com <pr...@gmail.com> #8Feb 7, 2023 05:09PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3559987

Provide additional NavGraph and NavDestination APIs

Expand for full commit details

Provide additional NavGraph and NavDestination APIs 
 
Adding a public int id and an internal getDisplayName to 
NavDestination. 
 
Adding startdestinationId and findNodeComprehensive to NavGraph. 
 
RelNote: N/A 
Test: all tests pass 
Bug: 403616316 
Change-Id: Idf3293890e4cd69f88aa4d72634c9be821663449

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavDestination.android.kt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavGraph.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavDestination.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavGraph.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavDestination.nonAndroid.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavGraph.nonAndroid.kt

Hash: 5f335b3312dfb96723faa7b7c57e3981d13f40f3
Date: Wed Mar 26 07:45:00 2025

j....@gmail.com <j....@gmail.com> #9Feb 10, 2023 10:22AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3561524

Provide internal multi-platform Log

Expand for full commit details

Provide internal multi-platform Log 
 
Ensuring that we have the ability to log from common code. This only 
takes over for info logs, other types of logs remain on the android 
platform only. 
 
Test: all tests pass 
Bug: 403616316 
Change-Id: I14b8b1e16cc7565b0789fd11bf85143fe0ed38d3

Files:

M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavController.android.kt
A navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/internal/Log.android.kt
A navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/internal/Log.kt
A navigation/navigation-runtime/src/nonAndroidMain/kotlin/androidx/navigation/internal/Log.nonAndroid.kt

Hash: 55f9ec50929827a5becc445c22805be6f3d28950
Date: Tue Mar 25 20:22:11 2025

na...@gmail.com <na...@gmail.com> #10Feb 21, 2023 08:37PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3560566

Provide popUpToId for NavOptions

Expand for full commit details

Provide popUpToId for NavOptions 
 
Adding an expect for popUpToId and implementing it in nonAndroid 
targets. 
 
RelNote: N/A 
Test: all tests pass 
Bug: 403616316 
Change-Id: I9a354359828786be54268096859bf8b3b35b51ac

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavOptions.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavOptions.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavOptions.nonAndroid.kt

Hash: b8a7d84a3201329cd33b11c12b2154b4a4215cf1
Date: Wed Mar 26 07:30:20 2025

vo...@hotmail.com <vo...@hotmail.com> #11Feb 23, 2023 05:40AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3560964

Move all of NavBackStackEntryProvider to common

Expand for full commit details

Move all of NavBackStackEntryProvider to common 
 
Adding expect/actual for WeakReference and UUID to move the entire 
NavBackStackEntryProvider class to common. 
 
Test: all tests pass 
Bug: 403616316 
 
Change-Id: I7e3b82e1788edd40e7a7cf92f3ec16c07f7e6bda

Files:

M navigation/navigation-compose/build.gradle
D navigation/navigation-compose/src/androidMain/kotlin/androidx/navigation/compose/NavBackStackEntryProvider.android.kt
M navigation/navigation-compose/src/androidMain/kotlin/androidx/navigation/compose/internal/NavComposeUtils.android.kt
M navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/NavBackStackEntryProvider.kt
M navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/NavHost.kt
M navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/internal/NavComposeUtils.kt
D navigation/navigation-compose/src/nonAndroidMain/kotlin/androidx/navigation/compose/NavBackStackEntryProvider.nonAndroid.kt
A navigation/navigation-compose/src/nonAndroidMain/kotlin/androidx/navigation/compose/internal/NavComposeUtils.nonAndroid.kt
D navigation/navigation-compose/src/nonAndroidMain/kotlin/androidx/navigation/compose/internal/NavHostInternals.nonAndroid.kt

Hash: e59c45ab84ef047b9a5f455851f99a394cd30cbd
Date: Wed Mar 26 19:03:12 2025

ko...@gmail.com <ko...@gmail.com> #12Mar 20, 2023 10:53AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3555747

Change the NavUri parse function

Expand for full commit details

Change the NavUri parse function 
 
Changing the parseStringAsNavUri into more of a factory function. 
Ideally this would be a function on a Compantion objects of NavUri, but 
if we want to alias NavUri to android's Uri, this is not possible. 
 
RelNote: "parseStringAsNavUri function has been changed to `NavUri` 
function that takes a String." 
Test: ./gradlew checkApi 
Bug: 403616316 
 
Change-Id: I4db6eeb13f86b3dbd987f9b55a49e9a45a8d0b38

Files:

M navigation/navigation-common/api/current.txt
M navigation/navigation-common/api/restricted_current.txt
M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavUri.kt

Hash: f353bd4db8d3ef6ea1d9fab22f8423e2217b69c0
Date: Mon Mar 24 04:02:30 2025

pi...@gmail.com <pi...@gmail.com> #13Mar 28, 2023 02:52AM

Android API Change

This bug was referenced by a recent CL that changed the Android API surface area.

The Android API Council regularly reviews API changes for consistency and sustainability, and we've just added this bug to our hotlist of pending reviews.

We'll wait until you mark this bug as 'Fixed' before starting our review, but please reach out if you'd like us to review it sooner.

Changes to navigation/navigation-common/api/current.txt

androidx.navigation
androidx.navigation.NavUriKt

http://go/agw/platform/frameworks/support/+/f353bd4db8d3ef6ea1d9fab22f8423e2217b69c0%5E%21
https://android-review.googlesource.com/3555747

[Gerrit:https://android-review.googlesource.com/3555747]
[API-Approvers:ilake@google.com]
[Branch:androidx-main]

[LIBRARY_API_REVIEW_TAG:navigation/navigation-common/api/current.txt]

th...@gmail.com <th...@gmail.com> #14Mar 31, 2023 11:02PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3566057

Fix NavUri call

Expand for full commit details

Fix NavUri call 
 
This function was parseStringAsNavUri and now is just NavUri. 
 
Test: all tests pass 
Bug: 403616316 
Change-Id: I16d4fe29a85ee825935480674ec3f1edd4a49a29

Files:

M navigation/navigation-runtime/src/commonMain/kotlin/androidx/navigation/internal/NavControllerImpl.kt

Hash: 941f6ed079da0acc34ff5053206d221eb6b660ec
Date: Fri Mar 28 00:55:28 2025

ma...@gmail.com <ma...@gmail.com> #15Apr 6, 2023 02:34PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3566235

Provide NavBackStackEntryImpl class for common

Expand for full commit details

Provide NavBackStackEntryImpl class for common 
 
Moving all eligible code to the common source set and exposing it to the 
android and nonAndroid specific implementations via an 
NavBackStackEntryImpl class. 
 
RelNote: "The AndroidX Navigation library now provides a nonAndroid 
implementation for NavBackStackEntry" 
Test: all tests pass 
Bug: 403616316 
 
Change-Id: I57547cfc013b0ded47e9719afa433c1d8244c6b5

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/build.gradle
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavBackStackEntry.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavBackStackEntry.kt
A navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/internal/NavBackStackEntryImpl.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavBackStackEntry.nonAndroid.kt

Hash: 5a80707e8348ea92b8b71d66f78b145a0f94ae02
Date: Fri Mar 28 02:12:56 2025

ed...@gmail.com <ed...@gmail.com> #16Apr 13, 2023 09:44PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3571368

Implement NavDeepLinkRequest in common

Expand for full commit details

Implement NavDeepLinkRequest in common 
 
Moving all of the NavDeepLinkRequest to common. 
 
RelNote: N/A 
Test: all tests pass 
Bug: 403616316 
Change-Id: I791195c7e73f745f9212ffee37cb3616c602c5ac

Files:

M navigation/navigation-common/bcv/native/current.txt
D navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavDeepLinkRequest.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavDeepLinkRequest.kt
D navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavDeepLinkRequest.nonAndroid.kt
M navigation/navigation-runtime/src/androidMain/kotlin/androidx/navigation/NavController.android.kt

Hash: 610e71c06b4b10c8e6543fbb3dbcae4d65ca61ea
Date: Wed Apr 02 02:14:30 2025

gu...@gmail.com <gu...@gmail.com> #17Apr 20, 2023 08:21PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3571367

Provide NavGraphImpl

Expand for full commit details

Provide NavGraphImpl 
 
Moving all common code to the common source set and allowing the 
specific platforms to use that source. 
 
RelNote: N/A 
Test: all tests pass 
Bug: 403616316 
Change-Id: If77617d32d274ea2f5f76107336293b562fda300

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavGraph.android.kt
A navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/internal/NavGraphImpl.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavGraph.nonAndroid.kt

Hash: 162602b9a59566b2f341aea043de202b72fccbed
Date: Wed Apr 02 01:40:22 2025

sh...@gmail.com <sh...@gmail.com> #18Apr 27, 2023 09:04AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3565864

Provide NavDestinationImpl

Expand for full commit details

Provide NavDestinationImpl 
 
Moving all common code to the common source set and allowing the 
specific platforms to use that source. 
 
RelNote: N/A 
Test: all tests pass 
Bug: 403616316 
Change-Id: Ia7ea5ba90d98353147c710bc43780e120f608c84

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/build.gradle
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavDestination.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavDestination.kt
A navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/internal/NavDestinationImpl.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavDestination.nonAndroid.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/internal/NavContext.nonAndroid.kt

Hash: 3c59943b0caac826903b5cbc5d033b69ab0c3b5c
Date: Fri Mar 28 03:56:37 2025

em...@gmail.com <em...@gmail.com> #19Jul 7, 2023 12:05AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3562704

Move Navigator to common

Expand for full commit details

Move Navigator to common 
 
There is no platform specific code in Navigator. 
 
RelNote: N/A 
Test: all tests pass 
Bug: 403616316 
Change-Id: I28c3cec15401a458124ee8e209d88fb807435fa6

Files:

M navigation/navigation-common/bcv/native/current.txt
D navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/Navigator.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/Navigator.kt
D navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/Navigator.nonAndroid.kt

Hash: 0ed3a0167619b3af5eabd1e167936ad6acd8dc46
Date: Wed Mar 26 19:59:07 2025

mo...@gmail.com <mo...@gmail.com> #20Jul 30, 2023 08:41PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3563405

Move noOpNavigator to common

Expand for full commit details

Move noOpNavigator to common 
 
Moving the implementation of the NoOpNavigator to the common source set 
and deleting the platform specific versions. 
 
RelNote: n/a 
Test: all tests pass 
Bug: 403616316 
Change-Id: I6cae3b46879633059eb50d768819cafb7de95cb6

Files:

D navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NoOpNavigator.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NoOpNavigator.kt
D navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NoOpNavigator.nonAndroid.kt

Hash: fa6cc966c5fa9773f8c1a5610b0f9252f5fb18f4
Date: Thu Mar 27 00:16:35 2025

lu...@gmail.com <lu...@gmail.com> #21Jul 31, 2023 01:31AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3571431

Move ComposeNavGraphNavigator to common

Expand for full commit details

Move ComposeNavGraphNavigator to common 
 
Moving the implementation of the ComposeNavGraphNavigator to the common source set 
and deleting the platform specific versions. 
 
RelNote: n/a 
Test: all tests pass 
Bug: 403616316 
Change-Id: Id01ca3d5db0399c61cba4588f67668213cc5af4b

Files:

D navigation/navigation-compose/src/androidMain/kotlin/androidx/navigation/compose/ComposeNavGraphNavigator.android.kt
M navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/ComposeNavGraphNavigator.kt
D navigation/navigation-compose/src/nonAndroidMain/kotlin/androidx/navigation/compose/ComposeNavGraphNavigator.nonAndroid.kt

Hash: d41eac2e40be89122d8204321e48e49cd1791f81
Date: Wed Apr 02 05:36:30 2025

mo...@gmail.com <mo...@gmail.com> #22Jul 31, 2023 05:27AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3572787

Move ClassType to common

Expand for full commit details

Move ClassType to common 
 
Even though ClassType is only used by tools, we should still provide an 
equal level of support on the Android side. Moving this to common allow 
us to keep this around for other Navigation implementations that are in 
Common. 
 
RelNote: N/A 
Test: ./gradlew checkApi 
Bug: 403616316 
Change-Id: I81efc0571178051fe9ef7ee00fab37378b271876

Files:

M navigation/navigation-common/bcv/native/current.txt
M navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavDestination.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavDestination.kt
M navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavDestination.nonAndroid.kt

Hash: 58806860cf5cd0eb2ffd4a0886b56b2e48587aa8
Date: Wed Apr 02 21:42:19 2025

bj...@gmail.com <bj...@gmail.com> #23Aug 16, 2023 11:43AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3571430

Move NavGraphNavigator to common

Expand for full commit details

Move NavGraphNavigator to common 
 
Moving the implementation of the NavGraphNavigator to the common source set 
and deleting the platform specific versions. 
 
RelNote: n/a 
Test: all tests pass 
Bug: 403616316 
Change-Id: Id28c449a52d14e2df101db25ded4d8e428c37c80

Files:

M navigation/navigation-common/bcv/native/current.txt
D navigation/navigation-common/src/androidMain/kotlin/androidx/navigation/NavGraphNavigator.android.kt
M navigation/navigation-common/src/commonMain/kotlin/androidx/navigation/NavGraphNavigator.kt
D navigation/navigation-common/src/nonAndroidMain/kotlin/androidx/navigation/NavGraphNavigator.nonAndroid.kt

Hash: a011b3bc23a80d510086701719d9a1ed88d7a15d
Date: Wed Apr 02 05:22:24 2025

st...@gmail.com <st...@gmail.com> #24Aug 19, 2023 06:10AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3571370

Move DialogNavigator to common

Expand for full commit details

Move DialogNavigator to common 
 
Moving the implementation of the DialogNavigator to the common source set 
and deleting the platform specific versions. 
 
RelNote: n/a 
Test: all tests pass 
Bug: 403616316 
Change-Id: Iaa801c14d263d7f372dabdc6e08c80d15926ed5b

Files:

D navigation/navigation-compose/src/androidMain/kotlin/androidx/navigation/compose/DialogNavigator.android.kt
M navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/DialogNavigator.kt
D navigation/navigation-compose/src/nonAndroidMain/kotlin/androidx/navigation/compose/DialogNavigator.nonAndroid.kt

Hash: cc99a247b36eeacb363a87d379bea7da32a86d31
Date: Wed Apr 02 05:51:40 2025

na...@gmail.com <na...@gmail.com> #25Aug 19, 2023 10:14PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Jeremy Woods <jbwoods@google.com>
Link: https://android-review.googlesource.com/3571369

Move ComposeNavigator to common

Expand for full commit details

Move ComposeNavigator to common 
 
Moving the implementation of the ComposeNavigator to the common source set 
and deleting the platform specific versions. 
 
RelNote: n/a 
Test: all tests pass 
Bug: 403616316 
Change-Id: I76f5ed06735867797b42cc22ef1efcf072200f5f

Files:

D navigation/navigation-compose/src/androidMain/kotlin/androidx/navigation/compose/ComposeNavigator.android.kt
M navigation/navigation-compose/src/commonMain/kotlin/androidx/navigation/compose/ComposeNavigator.kt
D navigation/navigation-compose/src/nonAndroidMain/kotlin/androidx/navigation/compose/ComposeNavigator.nonAndroid.kt

Hash: 27fca1659aa6ae2f085c758cb939e5990e3d8fc2
Date: Wed Apr 02 05:43:44 2025

ma...@gmail.com <ma...@gmail.com> #26Sep 10, 2023 06:59PM

This has been completed and will be available in Navigation 2.9.0-beta01.

vi...@google.com <vi...@google.com> #27Sep 13, 2023 05:32PM

Our engineering team is still working on this issue. We will provide more updates as they become available.

fc...@gmail.com <fc...@gmail.com> #28Sep 14, 2023 09:35AM

Fix it please :(

sa...@google.com <sa...@google.com> Sep 27, 2023 12:44PM

Reassigned to ps...@google.com.

pi...@hotmail.com <pi...@hotmail.com> #29Oct 2, 2023 04:25AM

same issue
honestly android drivers should be taking control of the DAC volume on hardware level like it happens when you plug them to windows devices instead of software volume control

es...@gmail.com <es...@gmail.com> #30Oct 7, 2023 07:47AM

I can confirm that bug also happens on my Nothing phone 2. Fix it please.

mt...@gmail.com <mt...@gmail.com> #31Oct 7, 2023 05:43PM

Can you fix this
still same issue
samsung s21 fe (android 13)

ra...@gmail.com <ra...@gmail.com> #32Oct 11, 2023 09:25PM

Is this fixed in Android 14?

https://source.android.com/docs/setup/about/android-14-release#audio

ra...@gmail.com <ra...@gmail.com> #33Oct 13, 2023 08:30PM

Just tested the latest Apple USB-C to Mini Jack converter...

Works fine on my:
a) Apple iPad Air 5 running iPadOS 17
b) Dell XPS 9550 running Windows 11

Craps out on my:
Google Pixel 7a running Android 14

Please don't tell me that Apple and even Microsoft write better drivers... and get this bug finally fixed!

go...@gmail.com <go...@gmail.com> #34Oct 13, 2023 09:41PM

Yep, it is working on my windows 10 laptop and the same low volume issue on my pixel 6a running Android 14

al...@gmail.com <al...@gmail.com> #35Oct 15, 2023 09:38PM

This still hasn't been addressed on Android 14 what a joke issue has been president for quite some time now

dj...@grailbio.com <dj...@grailbio.com> #36Oct 18, 2023 03:21PM

Agree, this is still an issue on Pixel 7 and Pixrl 6a. looks like incorrect voltage during dongle initialization.

be...@gmail.com <be...@gmail.com> #37Nov 4, 2023 11:22AM

same issue on galaxy fold 4

ra...@gmail.com <ra...@gmail.com> #38Nov 4, 2023 02:29PM

Without being capable to drive an hardware DAC (and ADC) directly, Android devices will never be an option for audio professionals or audiophiles... No wonder Apple still dominates that market...

lo...@gmail.com <lo...@gmail.com> #39Nov 4, 2023 03:35PM

same issue for me on my galaxy s23 ultra. any update?

ya...@gmail.com <ya...@gmail.com> #40Nov 6, 2023 05:04PM

It's been more than a year and still this issue is going on. Have some shame Google!

rs...@gmail.com <rs...@gmail.com> #41Nov 7, 2023 10:22AM

Could this be an elaborate plan to force us to buy Google's dongle? Seriously, fix this. There was almost nothing added in android 14, and this issue makes me consider going back to iPhone, since I can't listen to music on my phone (pixel 6A) properly.
The bug has been open for 1.5 years and likely requires a just few lines of code at max. Fix it.

pe...@gmail.com <pe...@gmail.com> #42Nov 8, 2023 02:15PM

Comment has been deleted.

Message last modified on Nov 8, 2023 02:17PM

ze...@gmail.com <ze...@gmail.com> #43Nov 8, 2023 05:38PM

I'm amazed this shenanigans is still going - but just to throw mine in as well, Pixel 7 Pro with Apple dongle, maxed out phone media volume and I might as well just be playing through the phones internal speakers 🙄 c'mon Google

lu...@gmail.com <lu...@gmail.com> #44Nov 11, 2023 01:46PM

Pixel 8, build UD1A.231105.004, same issue of course.
Until now i have just compiled and flashed a custom kernel to fix the issue.
But when doing that, the device fails play integrity checks of course.
So now you also need to root etc. it to atleast pass basic attestation.

I have reported this bug over a year ago, it is ridiculous that there is still no proper fix and no developer option to atleast be able to set the volume manually.

Maybe consider that not all people can or want to use wireless headphones for a variety of reasons.

I'm at a point where i probably will just get a phone with headphone jack (with the only higher end option being the Asus Zenfone) or switch to team Apple.

se...@gmail.com <se...@gmail.com> #45Nov 11, 2023 01:55PM

This is indeed a real issue and Google should be ashamed: USB audio
handling in Pixels is really a joke.

But for the record, USB Audio Player seems to solve most issues, including
this one, as you can directly control the hardware volume via the app:
being forced to use a specific app is not great either, but if you're
already a Pixel owner, it's cheaper than buying a new phone.

On Sat, 11 Nov 2023, 14:46 , <buganizer-system@google.com> wrote:

- Show quoted text -

lu...@gmail.com <lu...@gmail.com> #46Nov 11, 2023 02:53PM

I guess you could. Last time i tried that it didn't work all that well though. Not to mention it doesnt help when you want to listen to music/audio from other apps (games, spotify, youtube, ...)

al...@gmail.com <al...@gmail.com> #47Nov 12, 2023 09:50PM

Sad to report this issue is stil a problem on my new Pixel 8. I am on my second USB-C to jack dongle because I thought the issue was the no branded one I bought. Went with Apple because of price and availability for the second and now I'm here.

lu...@gmail.com <lu...@gmail.com> #48Nov 12, 2023 11:56PM

On Pixel devices it is atleast pretty straight forwards to compile and flash a custom kernel to mitigate the issue

ra...@gmail.com <ra...@gmail.com> #49Nov 13, 2023 12:03AM

Great! So what is stopping Google?

lu...@gmail.com <lu...@gmail.com> #50Nov 13, 2023 12:38AM

To be fair, my solution isn't really a fix. It just adds a special case for the apple adapter and sets volume to maximum. But as I said before, considering android currently exclusively uses software volume, I really see no reason to not just set max. volume for all DACs.

mi...@gmail.com <mi...@gmail.com> #51Nov 15, 2023 11:03PM

ridiculous this is an issue that needs root to fix

gr...@gmail.com <gr...@gmail.com> #52Dec 21, 2023 11:53AM

Of course, Google wants to sell more wireless ear pods, make such changes will have a negative impact on their wireless earpods business. "Don't be evil" my ass

gr...@gmail.com <gr...@gmail.com> #53Dec 21, 2023 12:00PM

Never gonna buy another hardware from google until this is fixed

je...@gmail.com <je...@gmail.com> #54Dec 22, 2023 09:40AM

I can confirm the issue, with my nothing phone one in combination with the apple dongle. I think an easy fix could be an androind app that lets us controll external audio interfaces or a little control interface in the main preferences. Cause as far as I'm informed all those dongles are just that, little audio interfaces. I'm no software engineer, but this shouldn't be so hard to implement. Seems to be a completely software related problem. I've tried to amplify the signal internaly with googles audioaplifyer app and got complete distortion and a noisy mess as a result. Please fix the issue google. :)

ra...@gmail.com <ra...@gmail.com> #55Dec 22, 2023 09:54AM

This is an easy OS fix, nothing to do with the hardware but Google just doesn’t care…

I guess all we can do is to refer to this issue here on every social media, forum, YouTube channel… and ask people to upvote….

an...@gmail.com <an...@gmail.com> #56Dec 24, 2023 12:25AM

Can confirm still happening on Samsung S23 Ultra. SMH

an...@gmail.com <an...@gmail.com> #57Dec 27, 2023 12:01PM

Can confirm that it is happening with my Pixel 7 on the latest QPR 2 beta 1

fi...@gmail.com <fi...@gmail.com> #58Jan 8, 2024 09:38PM

Can confirm the problem as well on S22+

30...@gmail.com <30...@gmail.com> #59Jan 8, 2024 11:30PM

Bump to confirm it's still an issue. Pixel 7 Android 14 using Walmart brand dongle, the same one works fine on iPhone

co...@gmail.com <co...@gmail.com> #60Jan 9, 2024 05:35PM

why is this not being worked on? the phones are defective if you can't even use headphones on them...

pixel 6a

da...@gmail.com <da...@gmail.com> #61Jan 10, 2024 12:10PM

PLEASE ship even a crude workaround in developer options. I'm using a Pixel 8 Pro and this issue has been driving me crazy!

da...@gmail.com <da...@gmail.com> #62Jan 10, 2024 12:24PM

The following workaround was posted by u/walog98 on reddit:

I had the same issue on my S21 and solved it by using the free Neutron app for Android. The problem is probably that Android outputs only 0.5V instead of 1.0V because of some miscommunication. Neutron can use the full power but does not work with streaming platforms. I think it initializes the dongle with 1.0V, then stays at 1.0V even if the Neutron is not running anymore.

Plug in the Apple dongle
Neutron asks if I want to use the Neutron app for audio, I press 2 times yes
I close the Neutron app
I go to, for example, Spotify
Then Neutron asks me again, but now I decline both (It does not work with Spotify...)
voila, full volume everywhere

jb...@gmail.com <jb...@gmail.com> #63Jan 16, 2024 03:30PM

Same issue on new Google Pixel 8 phone, using Apple USB-C to 3.5mm dongle.

Also testing 3.5mm jack vs. USB-C with dongle (same apple wired earbuds) on my old Pixel 3a XL, and the volume is waaay lower using USB-C. Tried the Neutron fix, and I can eventually get it to work (though clunky), but the free app dies after 5 days and this just feels like something that should just work.

These devices are all crippled now with the loss of the headphone jack, and the USB-C implementation is buggy, so these phones are not usable as phones, which is ridiculous.

This is my third Pixel and while it's a great phone, it should more usable as a phone.

Google, Fix This!!

we...@gmail.com <we...@gmail.com> #64Jan 17, 2024 07:02AM

Same issue here. Using Apple USB Dongle with Samsung Galaxy M53 %G - running Android 14. Volume is unusably low.

Would love to see the Android hardware volume issue fixed.

It will surely increase the range of hardware that can be used with Android devices.

mi...@gmail.com <mi...@gmail.com> #65Jan 17, 2024 04:26PM

With the USB DAC dongle "Ugreen" (

https://fr.aliexpress.com/item/4001037281541.html?spm=a2g0o.order_detail.order_detail_item.3.70697d56R4ouNh&gatewayAdapt=glo2fra ), volume is loud for headphone but very low for the microphone !
I managed to turn up a little but the volume of the microphone with "tinymix" but it is not perfect and I have to do it each time I plug the dongle... plus I need root access.. It would be possible to modify the android image to do this operation each a dongle is plugged...

lu...@gmail.com <lu...@gmail.com> #66Jan 17, 2024 04:32PM

Same issue as with headphone volume. You can use the app automate to set up a task that is executed every time a headset is plugged in or you compile and flash a custom kernel that fixes it (see my initial workaround, it works basically the same for mics).
For automate + rinymix, you need root, for custom kernel you don't.

ta...@gmail.com <ta...@gmail.com> #67Jan 20, 2024 04:58PM

Comment has been deleted.

Message last modified on Jan 20, 2024 04:58PM

ta...@gmail.com <ta...@gmail.com> #68Jan 20, 2024 04:58PM

Please please please, at least put a workaround for this in developer options. The current workaround of installing a third-party app that opens every time you plug your headphones in is crazy.

ra...@gmail.com <ra...@gmail.com> #69Jan 21, 2024 10:38AM

IssueTracker > /dev/null

… not even a single response from Google …

Not even a we’re working on it or we’re currently testing a fix, hoping to include it in next release or even a simple “won’t fix it, buy an iPhone you audiophiles”

ni...@gmail.com <ni...@gmail.com> #70Feb 10, 2024 05:45AM

This is really apalling behaviour from google/android, its been so long & not even a temp fix, until the next update...

kk...@gmail.com <kk...@gmail.com> #71Feb 14, 2024 03:39PM

Type-C adapter to 3.5mm gives very low volume... When fix????

al...@gmail.com <al...@gmail.com> #72Feb 16, 2024 12:02PM

Low volume with DAC (type-c to 3.5mm adapter)... Many users are complaining, why Google do not fix it????

re...@gmail.com <re...@gmail.com> #73Feb 16, 2024 12:03PM

Same issue with Xiaomi Pad 6 with the lastest Android firmware.... Help!

br...@gmail.com <br...@gmail.com> #74Mar 3, 2024 08:28PM

Same issue on PIxel 8 Pro. Have tried using USB Audio Player Pro, but realized that this only helps in specific uses, and does not interact well when switching the driver back over to android for something like phone calls.

jg...@gmail.com <jg...@gmail.com> #75Mar 17, 2024 01:29PM

Issue is still present on my Pixel 6a, can't properly hear music on my headphones with every dongle I've tried due to this issue. If Google is going to remove the headphone jack on their devices then they NEED to FIX this issue ASAP! This is ridiculous!!

dn...@gmail.com <dn...@gmail.com> #76Mar 18, 2024 08:31PM

This is quite embracing, it is 2024, this bug is still present on there in Android 14 on Pixel 7PRO

an...@gmail.com <an...@gmail.com> #77Apr 11, 2024 07:39AM

1.5 years and no progress snd no communication. let's face it, google won't fix it betting on wireless audio. my first and last google device i bought.

ga...@gmail.com <ga...@gmail.com> #78Apr 12, 2024 08:08PM

Serious issue, pretty unacceptable that this has not been resolved yet. Please consider resolving this! It is important for people who care about audio.

cl...@gmail.com <cl...@gmail.com> #79Apr 17, 2024 09:29AM

Please fix it: you cannot sell a phone that works with bluetooth earbuds only.

da...@gmail.com <da...@gmail.com> #80Apr 28, 2024 06:16PM

this issue is also documented here:

https://www.youtube.com/watch?v=eQBFBT2SD3Y&t=593s
its outrageous that compatiblity is not assured with DAC adapters

ki...@gmail.com <ki...@gmail.com> #81May 4, 2024 02:48AM

Please correct this Google. This is important to us that care about audio quality.

tb...@gmail.com <tb...@gmail.com> #82May 7, 2024 04:51PM

This makes certain audio hardware unusable on Android devices. Please fix this.

ba...@gmail.com <ba...@gmail.com> #83May 9, 2024 12:50PM

This needs to be picked up asap. This is unacceptable.

ps...@gmail.com <ps...@gmail.com> #84May 11, 2024 07:51PM

I think addressing this issue is important especially regarding Apple's Type-C DAC adapters, specifically because they handle AHJ correctly, allowing the volume buttons on Apple 3.5mm ear buds / headsets to work correctly on Android. I suspect this issue affects the direct Type-C variant of Apple ear buds, in which case the user can't just get a Google DAC adapter to work around the volume issue.

sw...@gmail.com <sw...@gmail.com> #85May 14, 2024 02:59PM

In store locations in NYC like bestbuy have stopped carrying googles usb c to 3.5mm jack adatper. So now when people get replacements they are getting apples instead. I'm an IT admin and have had nearly every android headphone user come to me about the volume being low after getting a new adapter, only to see they got an apple one.

Only thing people see this as their phones no longer working correctly with adapters, not an apple issue. How is this still a problem?

From my personal experience issue is with every samsug galaxy phone from the past 3 years, every pixel phone from the last 3 years, a few sony phones, and literally any android tablet.
Frequency is 100% of the time.

br...@gmail.com <br...@gmail.com> #86May 19, 2024 09:55PM

This would be great to get fixed. Lots of bad or even paid work arounds.

jj...@gmail.com <jj...@gmail.com> #87May 23, 2024 08:56PM

Same issue - would be really good to see this standardised and fixed.

pr...@gmail.com <pr...@gmail.com> #88May 24, 2024 03:37PM

I am also suffering from the same issue, these phones are crippled. The USB DAC hardware volume is not being controlled and then the headphones jack has been removed. FIX IT google, At this point I am even willing to pay for the fix.

ra...@gmail.com <ra...@gmail.com> #89May 28, 2024 01:00AM

I'm reading the comments here, and wow this issue sounds quite major! I think there's a trend towards a strong minority of people using wired headphones as opposed to wireless ones these days, although wireless headphones are still far more propular. The Apple USB-C dongle has a very high performance amplifier for its class, being often the preferred option for people shopping for an adapter for this type. So this issue is even more important considering that. I wonder are there any developer settings to adjust maximum gain for different devices? I think being able to adjust the limit for maximum gain is helpful for those who use IEMs for example, and volume management in general sounds like a big headache for those who use IEMs on android and a simple developer setting in the settings app would fix this issue in addition to the apple adapter issues.

na...@gmail.com <na...@gmail.com> #90Jun 1, 2024 04:02AM

Same issue with Samsung S20fe Snapdragon version - Android 13
Please fix this

cz...@gmail.com <cz...@gmail.com> #91Jun 4, 2024 04:12PM

Could you please fix this? Pixel 6, being in the EU makes the issue worse.

ni...@gmail.com <ni...@gmail.com> #92Jun 14, 2024 01:48PM

How long do y'all intend to ignore this issue? If there's no fix coming, please say so. I figured Google wouldn't be so content with Android being unable to handle wired headphones of all things.

an...@gmail.com <an...@gmail.com> #93Jun 14, 2024 02:00PM

well, it's assigned to ps...@gmail.com, that person decides to ignore it, probably because P2 and S2 is not important enough, and the rest of the company will refer to this persons decision and focus on something else. it's the place where bug reports go to die the silent dead of "known issues".

em...@gmail.com <em...@gmail.com> #94Jun 17, 2024 12:55PM

Such a trivial issue that has already been diagnosed by the original reporter not being fixed indicates just one thing. They are intentionally not fixing this, which is understandable, the financial motives at play are quite obvious and the people who use wired headphones are a small enough community that annoying them doesn't come at any significant cost.

jo...@gmail.com <jo...@gmail.com> #95Jun 23, 2024 06:04PM

are there instructions on how to (and is it possible to) install the kernel fix for the Apple adapter on any consumer Android device? it has to be stressed with Google pulling the sale of its own adapter, and many of three tiers party adapters in the high street simply not working, there is now no supported solution for this whatsoever. the Pixel itself has removed the 3.5 jack input and pixel 6 is nearly out of support for Android updates, so this could become an issue with no way out.

ra...@gmail.com <ra...@gmail.com> #96Jun 23, 2024 10:56PM

… easy and only way out is to buy a phone from Apple!
A company that cares about audiophiles…

sh...@gmail.com <sh...@gmail.com> #97Jun 24, 2024 07:14AM

I have found two fixes, One of them worked for me and now I use it everyday. The other one is related directly to the kernel so It might help.

Kernel Fix :-

https://github.com/polkaulfield/android_kernel_google_gs101/commit/fd86681a040119610bd54b02c7e152e03f8cff7c (I asked my Devices' Custom Kernel developer to add these line into the kernel, But it did not seem to work after that too.)

Fix for Rooted Devices :-

https://www.instructables.com/Apple-USB-C-35mm-DAC-on-Android/ (This is the one that I use everyday, It works flawlessly. You can use Automate as a free alternative to Tasker)

[You Can Also use Alsamixer(root) which I used to use earlier, Link :-

https://xdaforums.com/t/apple-usb-c-to-3-5mm-dac-dongle-and-android-remove-the-power-limit.3917495/ , If you are on higher versions of android make sure to install Magic_Overlayfs module to make you system partition R/W, Also the module sent by "_mysiak_" works just fine.]

Fix for Non-rooted Devices :- UAPP, Neutron Music Player, Hiby Music Player. (This is the only fix I have found yet for non-rooted devices, It was getting annoying so I had to root my device.)

For root I am using KernelSU. My Device is Nothing Phone (2a).

in...@gmail.com <in...@gmail.com> #98Jun 26, 2024 04:35AM

Please fix this google!

co...@gmail.com <co...@gmail.com> #99Jun 28, 2024 01:58AM

Any update on when this will be fixed?

le...@60228.dev <le...@60228.dev> #100Jul 12, 2024 09:14PM

With Android 14 adding support for hardware volume control to the USB audio HAL, I think a simple fix could be to change this code from

    if ((flags & AUDIO_OUTPUT_FLAG_BIT_PERFECT) != AUDIO_OUTPUT_FLAG_NONE) {
        out_stream_find_mixer_volume_control(out, device_info->profile.card);
    }

    out_stream_find_mixer_volume_control(out, device_info->profile.card);
    out_set_volume(&out->stream, 1.0, 1.0);
    if ((flags & AUDIO_OUTPUT_FLAG_BIT_PERFECT) == AUDIO_OUTPUT_FLAG_NONE) {
        out->volume_ctl = NULL; // FIXME: is this necessary?
    }

I don't understand the codebase well enough to know if this is the best approach, though, and I don't have an Android build environment set up to easily test this.

ma...@gmail.com <ma...@gmail.com> #101Jul 30, 2024 01:03PM

This issue does remain on my pixel 8.

mt...@gmail.com <mt...@gmail.com> #102Aug 1, 2024 09:11AM

please fix this still with android 14 on my samsung s23

do...@gmail.com <do...@gmail.com> #103Aug 1, 2024 05:37PM

I have this issue on my pixel 6. Please fix it.

ar...@gmail.com <ar...@gmail.com> #104Aug 5, 2024 05:27AM

I have the same issue on my both devices Nord 3 and Galaxy A53 while using apple usb c earpod..

j9...@gmail.com <j9...@gmail.com> #105Aug 21, 2024 05:45PM

same issue on Pixel 7

ma...@gmail.com <ma...@gmail.com> #106Aug 30, 2024 02:39AM

same issue. S24 Ultra. Both Focal Bathys and B&W Pi8 using the retransmission via USB C because Pixel nor S24 supports Qualcomm Adaptive! Listening on Windows 11 and zero issue. Fix this issue. There are many people that care about audio quality and its silly this is not fixed!

nu...@gmail.com <nu...@gmail.com> #107Sep 1, 2024 09:19AM

such an easy fix takes such a long time... pls fix

cr...@gmail.com <cr...@gmail.com> #108Sep 17, 2024 07:59PM

come on... fix it already

uf...@gmail.com <uf...@gmail.com> #109Sep 24, 2024 11:56AM

How is this STILL NOT FIXED!?
There are solutions, plenty of workarounds and it's been more than two years now.

Be a *Hero* and sort up the code, eh?
🦄

ma...@gmail.com <ma...@gmail.com> #110Oct 10, 2024 01:23PM

The same issue is still present on the new Pixel 9 running Android 14 and using Apple's official adapter, as Google doesn't seem to sell theirs anymore. WTF.

Was surprised I HAD to buy an active adapter with a DAC for my pixel in the first place, as my old normal adapter didn't work anymore, was even more disappointed when the new adapter's maxed volume was like 30% of what the max volume used to be with my old phone+simple adapter.

Then tried the workarounds here and they worked, how the hell has such a simple bug not been fixed in YEARS?!

an...@gmail.com <an...@gmail.com> #111Oct 10, 2024 01:26PM

just a reminder to never buy google hardware again ;)

sa...@gmail.com <sa...@gmail.com> #112Oct 22, 2024 12:24PM

Problem is still here on s23 ultra using the latest update

de...@gmail.com <de...@gmail.com> #113Nov 11, 2024 09:48PM

s24 still..

an...@gmail.com <an...@gmail.com> #114Nov 18, 2024 01:17AM

I have the same issue with the Pixel 7 Pro and the Edifier W830NB used via USB. The maximum playback volume via USB-C sounds about 50% of that played over Bluetooth.

When I install Neutron Player from the Play Store the maximum playback volume on the headphones is the same as vie Bluetooth when I set Neutron Player to have direct access to the USB device and to bypass the OS.

I do not have this issue when using a Google USB-C to 3.5mm audio jack converter and a pair of OneOdio Bluetooth headphones with a 3.5mm audio jack socket.

fr...@googlemail.com <fr...@googlemail.com> #115Nov 25, 2024 09:10PM

Same here.
LineageOS 21 / Android 14 on Pixel 6a
Please, I love my Porta Pros :)

mt...@gmail.com <mt...@gmail.com> #116Nov 30, 2024 11:27AM

Any update on it?
it is been 2 years

ra...@gmail.com <ra...@gmail.com> #117Dec 10, 2024 07:22PM

Huh… was this just fixed with the latest Android 15 update of December 2024? Or am I dreaming?

je...@gmail.com <je...@gmail.com> #118Dec 12, 2024 05:24PM

It's not fixed with Android 15.

<buganizer-system@google.com> schrieb am Di., 10. Dez. 2024, 20:22:

- Show quoted text -

ka...@baastrup.org <ka...@baastrup.org> #119Dec 30, 2024 05:42PM

Please fix it

da...@gmail.com <da...@gmail.com> #120Jan 6, 2025 07:10PM

PLEASE FIX THIS.

OR EVEN BETTER.

GIVE US THE JACK CONNECTOR BACK!

uf...@gmail.com <uf...@gmail.com> #121Jan 8, 2025 06:48PM

This is just atrocious...

For everyone experiencing his utter train crash of priorities, there is (kind of) a *WORKAROUND*

Works on Samsung Galaxy S20 Fe (SM-G780G/DS) and the standard cheap Apple USB C Audio Dac.

1. Download and install "HiBy Music"
Avaliable on playstore:
<

https://play.google.com/store/apps/details?id=com.hiby.music>

2. With your Dac plugged in, go to "Settings" and toggle "Exclusive HQ USB audio access". Agree to the warning prompt and then toggle the setting off again.

This workaround enables full volume from my cheap Apple USB Dac.

Hope it works for y'all too!

Sidenot this sets the Usb Dac hardware volume to what it should be. Why the devs have made an active decision to not fix this is beyond me. Seriously considering going Apple after this...

mt...@gmail.com <mt...@gmail.com> #122Jan 12, 2025 06:55AM

Android limitation

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

Only way I found out
I purchased usb audio pro

https://play.google.com/store/apps/details?id=com.extreamsd.usbaudioplayerpro

When I connect dongle I get pop up of this app and when It gets opened i increase the volume (there is hardware volume option in it) and close the app.

Then volume is increased system wide

ro...@gmail.com <ro...@gmail.com> #123Jan 17, 2025 05:53PM

Hi Team,
Kindly update us.

uk...@gmail.com <uk...@gmail.com> #124Jan 21, 2025 01:24PM

Hello
Kindly asking to take this into fixing

an...@gmail.com <an...@gmail.com> #125Jan 25, 2025 01:30PM

If anybody has got the HiBy Music workaround to work for a Google Pixel 7 Pro, please share your method.

Thanks!

vi...@gmail.com <vi...@gmail.com> #126Jan 26, 2025 04:37PM

UAPP only boosts the audio for as long as it is running in the background. You have to put the hardware volume to full every single time you connect the Apple dongle.
UAPP has "captured a market" that never needed to exist in the first place, and profited off of Google's incompetence.

The Apple dongle still has lower volume than it is capable of, due to a few lines of code. It is shameful.

For anyone considering buying the Apple dongle; don't. There is now a huge market of USB DAC/Amps. I particularly recommend looking for the keyword "CX31993" and buying whichever dongle you find. It will always be louder than the Apple dongle.

I wasted my money buying UAPP and Google won't even refund me for it.

lu...@gmail.com <lu...@gmail.com> #127Jan 26, 2025 05:10PM

The Apple dongle costs only 8€ here and is significantly better than even a lot of more expensive dongles. Besides that, there are a bunch of other dongles affected by this.

kd...@gmail.com <kd...@gmail.com> #128Feb 13, 2025 03:14AM

someone made an app that change the hardware volume of usb dacs... i tested with my apple dongle and it works

https://github.com/guyman624/usbDacVolumeAndroid

og...@gmail.com <og...@gmail.com> #129Feb 22, 2025 04:46AM

^ Does not work on S23 Ultra, but i hope in lieu of a proper Android fix, that this will work soon.

de...@gmail.com <de...@gmail.com> #130Feb 23, 2025 02:27AM

Works with my regular S22, getting full volume now. Can finally use it with my car radio aux input.

kr...@googlemail.com <kr...@googlemail.com> #131Mar 6, 2025 05:39PM

^^^ Worked on my Motorola edge 50 fusion.
Works also with Spotify, so it finally became enjoyable in an overloaded public bus again.

lu...@gmail.com <lu...@gmail.com> #132Mar 6, 2025 05:42PM

What Android version?

ch...@gmail.com <ch...@gmail.com> #133Mar 16, 2025 09:30AM

Same here. Apple USB-C to 3.5mm, Pixel 6a, Android 15 BP1A.250305.019. Tested with Spotify and Poweramp.
Around 20dB to low, with max Volume, on a -10dB LineInput. Even there are distorted Peaks at max Volume.

ur...@gmail.com <ur...@gmail.com> #134Mar 28, 2025 02:23AM

Same issue with the new Pixel 9 Pro i just bought.
And I already regret that I bought that Pixel 9 Pro without 3.5mm Jack.

1. Volume issues with USB-DACs
2. In-line Controls no working
3. Apps that fixed 2.) aren't on Play Store anymore and APK not compatible with Android 15

All that together makes the Pixel 9 Pro unuseable for listening Music for me.

I can't understand that Google don't fix those years old bugs.
And I also don't understand why you still need third party apps for in-line controls.

But perhaps it's on purpose so that I buy a iPhone next time... xD

ra...@gmail.com <ra...@gmail.com> #135Apr 10, 2025 04:05PM

I read that in the April (2025) update (

https://source.android.com/docs/security/bulletin/2025-04-01), Google will fix two critical bugs, located in the USB-Audio:

https://nvd.nist.gov/vuln/detail/CVE-2024-53150

https://nvd.nist.gov/vuln/detail/CVE-2024-53197

Patch is not yet available in my region but does anyone know if they bothered fixing this bug while updated the USB-Audio code?

Shame on Google...

ka...@gmail.com <ka...@gmail.com> #136Apr 12, 2025 06:25PM

P.L.E.A.S.E fix this issue. USB DAC support is seriously crippled because of this.

sa...@gmail.com <sa...@gmail.com> #137Apr 20, 2025 02:41PM

Just moved from an iPhone to the Pixel 9 pro and got the same issue with Apple's USB-C to jack DAC. Please fix this 4 years old issue, it's a basic use case of Android.

Issue 242221770

Description

Issue summary

Comments

vi...@google.com <vi...@google.com> #2Aug 12, 2022 09:54PM

lu...@gmail.com <lu...@gmail.com> #3Aug 13, 2022 04:14PM

ra...@google.com <ra...@google.com> Aug 16, 2022 05:51AM

pa...@google.com <pa...@google.com> Aug 16, 2022 06:45AM

pa...@google.com <pa...@google.com> #4Aug 18, 2022 11:39AM

lu...@gmail.com <lu...@gmail.com> #5Aug 18, 2022 07:38PM

98...@gmail.com <98...@gmail.com> #6Jan 1, 2023 05:50AM

al...@gmail.com <al...@gmail.com> #7Feb 2, 2023 01:02PM

pr...@gmail.com <pr...@gmail.com> #8Feb 7, 2023 05:09PM

j....@gmail.com <j....@gmail.com> #9Feb 10, 2023 10:22AM

na...@gmail.com <na...@gmail.com> #10Feb 21, 2023 08:37PM

vo...@hotmail.com <vo...@hotmail.com> #11Feb 23, 2023 05:40AM

ko...@gmail.com <ko...@gmail.com> #12Mar 20, 2023 10:53AM

pi...@gmail.com <pi...@gmail.com> #13Mar 28, 2023 02:52AM

Android API Change

th...@gmail.com <th...@gmail.com> #14Mar 31, 2023 11:02PM

ma...@gmail.com <ma...@gmail.com> #15Apr 6, 2023 02:34PM

ed...@gmail.com <ed...@gmail.com> #16Apr 13, 2023 09:44PM

gu...@gmail.com <gu...@gmail.com> #17Apr 20, 2023 08:21PM

sh...@gmail.com <sh...@gmail.com> #18Apr 27, 2023 09:04AM

em...@gmail.com <em...@gmail.com> #19Jul 7, 2023 12:05AM

mo...@gmail.com <mo...@gmail.com> #20Jul 30, 2023 08:41PM

lu...@gmail.com <lu...@gmail.com> #21Jul 31, 2023 01:31AM

mo...@gmail.com <mo...@gmail.com> #22Jul 31, 2023 05:27AM

bj...@gmail.com <bj...@gmail.com> #23Aug 16, 2023 11:43AM

st...@gmail.com <st...@gmail.com> #24Aug 19, 2023 06:10AM

na...@gmail.com <na...@gmail.com> #25Aug 19, 2023 10:14PM

ma...@gmail.com <ma...@gmail.com> #26Sep 10, 2023 06:59PM

vi...@google.com <vi...@google.com> #27Sep 13, 2023 05:32PM

fc...@gmail.com <fc...@gmail.com> #28Sep 14, 2023 09:35AM

sa...@google.com <sa...@google.com> Sep 27, 2023 12:44PM

pi...@hotmail.com <pi...@hotmail.com> #29Oct 2, 2023 04:25AM

es...@gmail.com <es...@gmail.com> #30Oct 7, 2023 07:47AM

mt...@gmail.com <mt...@gmail.com> #31Oct 7, 2023 05:43PM

ra...@gmail.com <ra...@gmail.com> #32Oct 11, 2023 09:25PM

ra...@gmail.com <ra...@gmail.com> #33Oct 13, 2023 08:30PM

go...@gmail.com <go...@gmail.com> #34Oct 13, 2023 09:41PM

al...@gmail.com <al...@gmail.com> #35Oct 15, 2023 09:38PM

dj...@grailbio.com <dj...@grailbio.com> #36Oct 18, 2023 03:21PM

be...@gmail.com <be...@gmail.com> #37Nov 4, 2023 11:22AM

ra...@gmail.com <ra...@gmail.com> #38Nov 4, 2023 02:29PM

lo...@gmail.com <lo...@gmail.com> #39Nov 4, 2023 03:35PM

ya...@gmail.com <ya...@gmail.com> #40Nov 6, 2023 05:04PM

rs...@gmail.com <rs...@gmail.com> #41Nov 7, 2023 10:22AM

pe...@gmail.com <pe...@gmail.com> #42Nov 8, 2023 02:15PM

ze...@gmail.com <ze...@gmail.com> #43Nov 8, 2023 05:38PM

lu...@gmail.com <lu...@gmail.com> #44Nov 11, 2023 01:46PM

se...@gmail.com <se...@gmail.com> #45Nov 11, 2023 01:55PM

lu...@gmail.com <lu...@gmail.com> #46Nov 11, 2023 02:53PM

al...@gmail.com <al...@gmail.com> #47Nov 12, 2023 09:50PM

lu...@gmail.com <lu...@gmail.com> #48Nov 12, 2023 11:56PM

ra...@gmail.com <ra...@gmail.com> #49Nov 13, 2023 12:03AM

lu...@gmail.com <lu...@gmail.com> #50Nov 13, 2023 12:38AM

mi...@gmail.com <mi...@gmail.com> #51Nov 15, 2023 11:03PM

gr...@gmail.com <gr...@gmail.com> #52Dec 21, 2023 11:53AM

gr...@gmail.com <gr...@gmail.com> #53Dec 21, 2023 12:00PM

je...@gmail.com <je...@gmail.com> #54Dec 22, 2023 09:40AM

ra...@gmail.com <ra...@gmail.com> #55Dec 22, 2023 09:54AM

an...@gmail.com <an...@gmail.com> #56Dec 24, 2023 12:25AM

an...@gmail.com <an...@gmail.com> #57Dec 27, 2023 12:01PM

fi...@gmail.com <fi...@gmail.com> #58Jan 8, 2024 09:38PM

30...@gmail.com <30...@gmail.com> #59Jan 8, 2024 11:30PM

co...@gmail.com <co...@gmail.com> #60Jan 9, 2024 05:35PM

da...@gmail.com <da...@gmail.com> #61Jan 10, 2024 12:10PM

da...@gmail.com <da...@gmail.com> #62Jan 10, 2024 12:24PM

jb...@gmail.com <jb...@gmail.com> #63Jan 16, 2024 03:30PM

we...@gmail.com <we...@gmail.com> #64Jan 17, 2024 07:02AM

mi...@gmail.com <mi...@gmail.com> #65Jan 17, 2024 04:26PM

lu...@gmail.com <lu...@gmail.com> #66Jan 17, 2024 04:32PM

ta...@gmail.com <ta...@gmail.com> #67Jan 20, 2024 04:58PM

ta...@gmail.com <ta...@gmail.com> #68Jan 20, 2024 04:58PM

ra...@gmail.com <ra...@gmail.com> #69Jan 21, 2024 10:38AM

ni...@gmail.com <ni...@gmail.com> #70Feb 10, 2024 05:45AM

kk...@gmail.com <kk...@gmail.com> #71Feb 14, 2024 03:39PM

al...@gmail.com <al...@gmail.com> #72Feb 16, 2024 12:02PM

re...@gmail.com <re...@gmail.com> #73Feb 16, 2024 12:03PM