Extra runtime permission visible in App Settings
Hello, I am testing my app, and I only use WRITE_EXTERNAL_STORAGE for media access. However, in Headset Settings → Privacy & Security → Installed Apps → [my app], I see that three permissions have been added. My manifest looks like this: <!--?xml version="1.0" encoding="utf-8" standalone="no"?--> <manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" package="com.example.app" android:installlocation="auto"> <uses-permission android:name="android.permission.INTERNET" tools:node="merge"> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"> <uses-permission android:name="android.permission.ACCESS_WIFI_STATE"> <uses-permission android:name="android.permission.RECORD_AUDIO" tools:node="remove"> <uses-permission android:name="android.permission.READ_MEDIA_AUDIO" tools:node="remove"> <uses-permission android:name="android.permission.READ_MEDIA_VIDEO" tools:node="remove"> <uses-permission android:name="android.permission.READ_MEDIA_IMAGES" tools:node="remove"> <uses-permission android:name="android.permission.ACCESS_MEDIA_LOCATION" tools:node="remove"> <uses-permission android:name="android.permission.READ_MEDIA_IMAGE" tools:node="remove"> <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" tools:node="remove"> <application android:name=".AppDelegate" android:label="@string/app_name" android:networksecurityconfig="@xml/network_security_config" android:requestlegacyexternalstorage="true" android:icon="@mipmap/app_icon" android:allowbackup="false"> <activity android:theme="@style/Theme.AppCompat.DayNight.NoActionBar" android:configchanges="locale|fontScale|keyboard|keyboardHidden|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode" android:launchmode="singleTask" android:name="com.unity3d.player.UnityPlayerGameActivity" android:excludefromrecents="true" android:exported="true" android:screenorientation="landscape"> <intent-filter> <action android:name="android.intent.action.MAIN"> <category android:name="android.intent.category.LAUNCHER"> <category android:name="com.oculus.intent.category.VR"> </category></category></action></intent-filter> <meta-data android:name="com.oculus.vr.focusaware" android:value="true"> </meta-data></activity> <meta-data android:name="unityplayer.SkipPermissionsDialog" android:value="false"> <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only"> <meta-data android:name="com.oculus.supportedDevices" android:value="quest|quest2|questpro|quest3|quest3s" tools:replace="android:value"> <meta-data android:name="com.oculus.ossplash.background" android:value="black"> <meta-data android:name="com.oculus.telemetry.project_guid" android:value="xxx"> </meta-data></meta-data></meta-data></meta-data></meta-data></application> <uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true"> </uses-feature></uses-permission></uses-permission></uses-permission></uses-permission></uses-permission></uses-permission></uses-permission></uses-permission></uses-permission></uses-permission></manifest> and this is what I see in the app settings: As you can see, the "Photos and videos" and "Music and audio" permissions are also listed, even though I only requested the "Storage" permission. In my testing, I also found that disabling the "Photos & videos" toggle causes my app to stop working, even if the "Storage" permission remains enabled. I believe that seeing multiple permissions in the list may cause users to lose confidence and feel uncertain about granting them—especially "Music and audio," which is unrelated to my app.
The error message:SocketError.Accessdenied
Hi guys, could someone help me? I'm making an online game. When testing on quest2, it was found that on the V35 system, it can be connected through the Internet (TCP protocol). However, on the V56 system, it cannot be connected through the Internet (TCP protocol). The error message "Client Recv: failed to connect to ip=34.86.33.208 port=9000 reason=System.Net.Sockets.SocketException (0x80004005): Access denied" will appear. Is it because I set something wrong? Could you share a similar experience? Thank you so much.
Updating Quest 2 refresh rate causing physics stuttering
Hi community, I'm trying to get my Unity Quest 2 application (standalone) updating the headset refresh rate to the maximum available Problem: Updating to any refresh rate higher than the default 72 causes the physics to start stuttering. When I grab an object with a rigidbody and start moving my hand I see it jittering/choppy movement What I've tried: OBS shows the in game FPS is meeting the cap 72/90/120, and everything else except physics based movement is buttery smooth. My understanding is that physics has it's own timestep value `Time.fixedDeltaTime`. I tried updating that in my refresh rate code below: Additional info: My time settings Unity Version 2021.3.12f1 URP Any help is much appreciated, thanks
How to get Oculus Quest 2 Controller Battery in Unity?
How to get Oculus Quest 2 Controller Battery in Unity? I am connecting Quest 2 using Oculus Link. Since it is catchable in official Oculus Software (Image Above), I think it is possible? But I can't access the battery either with SystemInfo.Battery() or SteamVR ETrackedDeviceProperty.Prop_DeviceBatteryPercentage_Float or Unity XR battery level.Headset keeps freezing
Hi im destiny, And i have a issue my quest 2 keeps freezing if it using memory, When it using memory my headset it also get hot not normal warm or something realy hot, On a cold start and while using it it freezes a lot. What do i mean with freezes like all the apps not even one giving me a frozen screen when i try to rotate my head it is black on the edges and when i turn 180 its upside down and its issn't playable anymore. Iv'e tried: restarting factory reset cleaning lenses for tracking its even getting it on cold or hard boot. Let me say i have tried everything but the issue keeps existing. My headset is more than 2 years old and i have no idea what to do anymore. I hope somebody can help me. Greetz Destiny.
v63 - The wireless ADB debugging prompt shows a black screen.
Hi, Two tickets were opened here : https://communityforums.atmeta.com/t5/Get-Help/PTC-v63-The-wireless-debugging-prompt-does-not-appear-and-shows/m-p/1171644 and here https://communityforums.atmeta.com/t5/Get-Help/PTC-v62-The-USB-debugging-prompt-does-not-appear-when-the/m-p/1171979 But I was asked to post this here. To resume : On Q2, Qpro and Q3 (v62, v63) when the authorize WiFi debugging through adb prompt shows up, the Quest will first enter a black screen state. Then, we must click the home button on the right controller to make this window show. If I do not click the home button, it will remain in a black screen state. USB debugging prompt had same problem on v62 but it has been fixed on v63 thank to the new look/UI of the prompt. But the wireless debugging prompt have not been updated and still run into this problem. To fix the problem, Meta developers should update the wireless debugging prompt to the new look/UI.
