Can't use another ringtone picker

de0u

dangerous-orange It sounds as if the Google Sounds app may expect privileges that it has on the stock OS but does not have on GrapheneOS. Perhaps a recent OS release tightened things up. It might be useful to share a system log for the app, if you examine it and feel comfortable sharing the contents.

dangerous-orange

de0u I've saved what I could find from system logs. There was no crash within the apps logs when clicking from the app info section.

The system log extract: https://notebin.de/?98c661c876574e4a#5W9Vg7yukR1J1vqpzq2513A7HDrmUHFmZfoLxPBVxEaw

I'm unsure of how useful this is, as it's my first time posting logs online

de0u

dangerous-orange I see a lot of things like com.google.android.soundpicker not qualified for android.app.role.DIALER due to missing RequiredComponent{mIntentFilterData=IntentFilterData{mAction='android.intent.action.DIAL', mCategories='[]', mDataScheme='null', mDataType='null'}, mMinTargetSdkVersion=1, mFlags='0', mPermission='null', mQueryFlags=0, mMetaData=[]}

To me that looks like the Google app is accustomed to having special privileges on devices that are running the stock OS.

dangerous-orange

I also have not disabled the original AOSP sound picker app. As that doesn't change anything and wasn't required when this worked previously a few weeks ago

dangerous-orange

de0u I would agree with you, but I'm not sure if this might be exactly the issue since the app was working before the Android 15 updates. I would imagine the app would have also expected a similar amount of permissions before the update.

I could be wrong in my guess though.

muhomorr

Usage of custom ringtone pickers is intentionally blocked in AOSP since Android 15:
https://github.com/GrapheneOS/platform_packages_apps_Settings/commit/0bd014c4977c3c4d35daf3df390cfcdc61d18b3e#diff-05294bf286e4f0023c6e06440c105ba21d54a50c548e40659a8fb3de15bcb8abR77

https://github.com/GrapheneOS/platform_packages_apps_Settings/commit/37f992aeccfa4c37db9514a3bb1d14761682aada#diff-36baccaa4417a70d63be553b3077b796397c84b254e492977edc08aa3e006b0cR287

DeletedUser87

muhomorr okay, and why is that? Does that have any benefit at all? Because that is degrading the user experience for sure.

dangerous-orange

muhomorr Thank you for the explanation. I wonder if this would be a change the GOS devs would consider reverting?

Should I open an issue about this?

de0u

DeletedUser87 okay, and why is that?

The commits muhomorr graciously referenced are from Google. The first one contains an explanation. According to Google's revised thinking, their app should be declaring the intents it relies on. Perhaps this is to enable the permission system to prompt users to allow (or reject) the app's changes to the UI.

DeletedUser87 Does that have any benefit at all?

Apparently Google believes that upgrading the framework has benefits. Presumably they have some plan for also upgrading the app. Perhaps they already did upgrade the app and forgot to ship it!

DeletedUser87 Because that is degrading the user experience for sure.

Increasing security often does complicate the user experience. On the other hand, getting exploited typically complicates the user experience a whole lot.

de0u

dangerous-orange I wonder if this would be a change the GOS devs would consider reverting?

I would be surprised. The GrapheneOS developers historically prioritize security improvements, not undoing security improvements.

dangerous-orange Should I open an issue about this?

Overall it might be productive to see if an issue already exists on Google's AOSP bug tracker and to file one there if not. But it seems pretty plausible that Google will, on their own, upgrade their app to comply with their change to their permission-management system.

Please note that I do not speak for the GrapheneOS project (or for Google).

dangerous-orange

Thanks for the reply, de0u . If this incompatibility is going to be resolved by Google, then I see no reason to post any issues anywhere.

I suppose all that's left is to wait and see until if this change to the Google Sounds app happens and becomes available via 3rd party sites.

I'm glad to know this is a feature, and not a bug

Bouzenzel

dangerous-orange
I wanted to post about the issue today, luckely you did, what I've noticed from my part is that Google changed this feature before Android 15 update I guess in the last update of Android 14, i was thinking that it was a GOS issue but it seems that Google wanted otherwise,I hope we will be able to get back sounds app or maybe we could open an issue for the GOS team to have a solution ! What do you think ?

Bouzenzel

Is there anything new about this matter !?

reunion

Here's what I was able to do:

Install Google Sounds apk
Install Activity Launcher (Play Store) and launch it
Under Sounds (with the note icon, not the android) select the activity that ends in 'GalleryActivity'
Pick a ringtone and save
Go to Settings > Sounds and vibration > Phone ringtone
The sound from step 4 has appeared on the list, select it.

I don't know if the Google Sounds app includes notification/alarm sounds but ringtones work for me this way.

Edit: forgot link

« Previous Page