Search Issue Tracker
Fixed in 5.3.6
Votes
27
Found in
5.3.5p3
Issue ID
804894
Regression
Yes
The sound will stop when there is an alarm or notification in a particular smartphone from Unity 5.3.5
When phone alarm starts to ring when Unity app with sound is running, all sound in app will be gone even after alram sound is turn off. Regression from 5.3.5
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
artoonie
Jun 03, 2022 16:28
Encountering this too, 2020.3.30f1. Perhaps a regression?
ivoras
Nov 17, 2021 23:24
Not fixed. Bump from 2021.
rendermouse
Nov 07, 2016 15:32
Still broken in 5.4.2f2.
Pablo-Isidro
Jul 08, 2016 12:16
Same problem here, hope Unity 5.3.6 releases soon :D
Ill-Fish
Jul 08, 2016 11:35
I still have that problem in Untiy 5.3.5p6 . Testet on Huawei P8 and Samsung S4.
mwk888
Jul 07, 2016 00:06
This problem absolutely exists with 5.3.5f1 I can reproduce it 100% e.g. just by sending an email to my account while playing game on Android. After I hear the email notification sound (without leaving/suspending app) Unity sounds stop permanently
pepepompin
Jul 01, 2016 16:39
Still a bug, silll a CRITICAL BUG
Trond_Tactile
Jun 28, 2016 09:05
When will this fix be released, or rather, when will 5.3.6 be released?
liiir1985
Jun 26, 2016 07:15
Tried 5.3.5p5, this bug is still there
yruizw
Jun 25, 2016 23:40
I've just found the same issue on my android app, I'm using 5.3.5f1, is this will be solved soon? or included on the next release?