it may be a lower-priority issue, an unconfirmed hardware problem, or one we haven’t received enough reports on yet.
I’m going to try to recreate your issue on my Fairphone 5 today and let you how it went.
If more people notice the same thing on their devices and we don’t find a clear cause or solution, I think you should reach out to Fairphone’s Customer Support using their contact form. As they say:
This is the primary way we collect and evaluate bug reports for prioritization and resolution.
the new alarm displays and plays a different sound
Do you mean that your new alarm sound shows “Carbon” as the selected sound? If so, what happens when you select a new sound for that specific alarm?
I remembered that you can Send feedback to Google via the 3-dot menu on the Clock app. Maybe it is worth a shot.
My device is a FP5 5G running build number is FP5.VT32.C.116.20260903
Yes, the new alarm always displays and plays “CARBON,” regardless of whether the default sound is another built-in sound or a downloaded audio file.
Just as if my default choice was CARBON (who on earth would do that haha.)
So I end up with creating an alarm set up on the CARBON sound but I still can change the sound on “X” (every choice works) and at this point this alarm will always respect this choice (display on screen, AND play it in the morning.)
To summary : this is only a malfunction of the “default choice” option. Not so annoying.
We share both the same phone, built, and ClockApp version.
You’re right. I just sent feedback to Google following ur advice.
I’ll feedback this to Fairphone too, just the time for me to find my proof of purchase, necessary when requesting a diagnosis.