I have an app built with Unity. There seems to be an issue with audio on Android 12. When the app loses focus (minimized) and is brought back to focus again, the sound/audio no longer plays, almost as if it's been muted.
Is anyone else experiencing this issue? And is there a fix?
I'm testing on a Samsung A22-5G.
Unity version is: 2020.3.35f1
Still investigating the problem, but here's a quick workaround (tested with Unity 2021.2.19f1).
Go to Project Settings > Player > Other Settings, enable "Mute Other Audio Sources".
Still working on a softer solution...
Currently can't check the issue with the newest Unity version.
Update 1
Seems like the issue is related to FMOD and should have been fixed in the newest Unity versions. https://issuetracker.unity3d.com/issues/android-player-crashing-in-fmod-when-targetting-sdk-level-31
Related
So this is a new type of issue I am currently facing, Recently I ran an APK of React Native Application I recently built on my system. After running that APK successfully. I started facing some issues regarding my phone's ** sound key **.
I tried restarting the device [Samsung], So it stopped showing the 1st issue. But after a few days a 2nd issue arrives.
1st issue => The volume up button stops working manually and starts increasing the volume automatically.
2n issue => Now whenever I write a new Text Message to someone it automatically starts increasing the font size of the text.
I gave a reboot to the device and even formated it, but nothing helped.
I want to know if it's a software side issue or hardware? So that before submitting the device to a Samsung store, If it's a software issue and if I can fix it. It will save me some bucks.
I actually solved this issue and that was due to the Hardware issue that has happened to my Android Samsung device and I researched it.
This type of issue was very common with users having that old version of smartphones and that is why new design keys for power and volume were introduced in most of the new smartphones which were launched in later 2016. This has actually reduced the key issues and if in case there is an issue, now it is easier to fix it since the keys are separated from the board as it was used to be earlier.
Also, some useful sources if someone is facing a similar issue in their old version android devices.
Volume Slider.
Volume button not working
Currently, I am trying to make the Virtual Tour app to play with cardboard, then get the demo completed and it's working like a charm in Editor Play mode and on my Lenovo Phab 2 phone. Unfortunately, when I install it on Samsung Note 9, the app displays upside down. I have tried change the orientation in player setting and edit the android manifest but still no luck are there any one know the solution? or is it the bug in GoogleVRSDK or Unity ,caused at first there is the lack in app build that Unity build the app as normal app not Cardboard one even GoogleVR Demo scene, but after restart Unity it works fine.
This is apparently an issue with Unity 2019.1.x and both Android and iOS.
Either, switch rendering from Vulkan to OpenGLES3 (Android, not sure about iOS)
Or, downgrade to 2018.3.14f (is said to work for both iOS and Android)
Track updates here:
https://github.com/googlevr/gvr-unity-sdk/issues/1030
https://github.com/googlevr/gvr-unity-sdk/issues/1031
My app has an embedded Youtube player. I am using the latest version of the Youtube Android Player (1.2.1). I am using the YouTubePlayerSupportFragment and this fragment is nested inside another fragment of my app.
It works on Android 4.4 and Android 5.0.
On Android 5.1 it works at the beginning, but after playing some videos the problem arises. The entire device slows down up to the point of it becoming nearly unresponsive. If I kill the app (if the Youtube Android Player gets killed) the device goes back to normality. However, from now on the Youtube Android Player cannot play any more videos (the device becomes unresponsive again).
Edit: in case the problem was in the fact that it is an embedded fragment, I have tested with an Intent (YouTubeIntents.createPlayVideoIntentWithOptions). The problem remains the same.
Has anybody experienced this kind of problems?
Solved! I was compiling with targetSDK 21, but Android 5.1 is SDK 22. It looks like compiling with an older SDK was causing the problem. After updating the targetSDK to 22, now it work like a charm.
I'm writing an android audio player and on my nexus 5 running android 5.0 the MedaPlayer stops playing audio tracks around 2 to 5 seconds early. It's not predictable. It can change on the same track. Is there anyone else experiencing this, that found a workaround. I know this is not just my app that's having this issue on this device, because I tested it in Vanilla Music Player and it did the same thing. I've seen a few other people post on things sort of similar, but in most cases I see it has to do with steaming.
According to this answser:
https://stackoverflow.com/a/27827402/1415199
This is a bug in Android.
Ok it looks like the issue is Android 5.0.1's experimental MediaPlayer
called NuPlayer. NuPlayer is being enabled by default on all Android
5.0.1 devices and is only disabled through Developer Options. I've filed a bug against Android here:
https://code.google.com/p/android/issues/detail?id=94069&thanks=94069&ts=1420659450
The link above contains a suggested workaround
this is the built version
this is the game view version
settings
it was working fine before and building the same untill i switched platforms and built web player version and google native client version, i cannot find anything on it, before i built the other version it was just for android, im trying to revert back so they will build the same on android again, im looking for some insight on this, thank you for your time
Seems like you have to adjust your quality settings. In Unity 3.5.x go to Edit / Project Setting / Quality and ensure that more than 0 pixel lights will be rendered and shadows are enabled. I have not yet upgraded to Unity 4 but it should be similar there.
Be aware that this affects rendering performance.