The Public Test Channel (PTC) for Quest and Quest 2 v.38 is starting to roll out today. Let's use his thread for collecting feedback on it. Share your impressions and let us know if you see any issues. Please make sure to alsosend in bug reportsalong with posting in this thread you notice anything wrong.
When sharing feedback, try to include as much detail as possible to help the team investigate.
Hello, my headset updated automatically to v38, and as I would guess many people are, I am kind of disappointed about the logo change on startup. Other than that, the only difference that I’ve noticed is that some things in the UI are more spaced out and it looks much cleaner in my opinion.
Device bricked with v38 PTC. The firmware uploads (firmware icon and green bar completes) but when it reboots the logo just keeps flashing. If I power on again, the green bar loads again and it goes back to the flashing logo. Have tried multiple reboots, hard reboots, factory resets, wifi router reboot, powering down from Android menu, etc. Looks like its bricked my device! Any suggestions welcome. Thanks. John.
Got the firmware today. Also after the firmware update i got an update for the "SocialPlattform" app. Since then "SocialPlattform" is crashing everytime if i try to open a chat trough the Messenger icon.
Hello, my headset updated automatically to v38, and as I would guess many people are, I am kind of disappointed about the logo change on startup. Other than that, the only difference that I’ve noticed is that some things in the UI are more spaced out and it looks much cleaner in my opinion.
I have it finished too, and so far like you the only change I noticed is the logo... out side of that and having to re select my environment, I haven't noticed any difference from v37, mine is still blurry, I have tried all the visual settings for the EyePiece as for 1,2, and 3 but 2 is still the best of the 3 and still blurry. I feel dissapointed as well, as I haven't gotten anything new or different at all other than a logo change.
Any idea if oculus link discharge will ever be resolved? The headset used to charge during link but now it always discharges, no matter what adapters and powered hubs I use.
Maybe sharing what has changed will increase the chance of getting useful feedback. Otherwise I might assume a given bug is an old bug, or that a new feature is a bug etc.
I'm now kinda glad I opted out of the Quest Beta a few weeks ago. Feedback did not seem to make much difference with beta v37 anyway and there is no way to roll back until the next public release. Very silly imho, lol!
You know how some grocery stores have carts you have to pay a quarter to get, I feel the same about the updates, you pretty much get your leg caught in a bear trap and cant open it to release your leg unless you pay a quarter... you are trapped with the updates untill HOPEFULLY the public release, but then 37 shows us that even then you are sometimes in that bear trap and dont have a quarter to spend.
Hi Ryan, or anyone out there. Is it likely that my device will be recoverable when new firmware versions are released - or have I permanently bricked it?
Today for the first time since getting Quest (more than a year ago), I've experienced what seemed like overheating (Quest kept going to sleep every few minutes while I was using it without any prior notice).
v38 installed yesterday, Quest was connected to USB charger. Bug report submitted.
v38 has been great so far, with the exception of the Android Settings. Some panels like Account Section don't work. This is a problem since the Account Section is used by some 2D Android apps to log out / manage the account associated with an app. After some investigation it seems like this piece of code in Settings.apk (com.android.settings.accounts.AccountPreferenceController) is the culprit as there was an additional check added in the Settings app from
public boolean isAvailable() {
return !this.mUm.isManagedProfile();
}
in v37 to
public boolean isAvailable() {
if (!this.mContext.getResources().getBoolean(R.bool.config_enable_account_dashboard)) {
return false;
}
return !this.mUm.isManagedProfile();
}
in v38.
Is this supposed to be in the final version of v38 and will there be a way for me to manually set config_enable_account_dashboard to true in the future? Also what is the reason for this check to be added? Thanks!
I think it's a shame that there is nothing to test or that we don't know what to test at each update. Version 37 brought blur to the headset and v38 a new Meta logo...
Are you going to fix any long standing issues and add support for Windows 11, or is this another release with some new features and where you break things further?
A new 'Mobile ASW' option which is set to Auto (I'm on a Quest2). And PC-ASW is now disabled by default, and has been given the PC tag.
Attached image of the changes. I'm curious if anyone had the chance to try Link and if they notice anything different to their ASW/Reprojection experience
I still don't understand what the point of pushing out a test release and seeking feedback is without publishing at least a basic change log so testers have some idea of what's changed and where to direct their scrutiny. Facebook's Meta's development methodology continues to be baffling with the results, of course, speaking for themselves in the number of broken (and non-revertable) updates that have been pushed out to the general user base since release.
That said, since the v38 update my headset now has to be fully powered off when not in use because if left in standby mode, it will randomly power up. This behaviour so far only seems to occur when with a lens cover in place (essential to provent sun damage in a house with a lot of open windows), so I assume something has been screwed up with the proximity sensor.
I got v38 over the weekend, and every time I go to use my Quest 2 since then, the battery is dead. This typically happens when an update has just been installed, because I keep my headset in standby, with a lens protector on. The headset wakes during the update process, and then stays on (because the proximity sensor sees the lens protector) until the battery is drained. I don't think there have been further updates since the initial one (I haven't noticed a change in the version number), but something is causing my headset to wake from standby every day now under v38. Rather inconvenient--I guess maybe I need to cut a hole in my lens cover to prevent triggering the sensor.
Thanks @Anonymous and @nalex66! That's just the sort of feedback we have the PTC for, and what the PTC team is looking to identify early. I've brought this to the attention of the team to investigate.
And thanks to everyone for providing your feedback so far.
Hey guys, I appreciate the sentiment, but let's try and keep focused threads like this helpful and constructive. Windows 11 certification being worked on by the team, but it's a much different task from bug fixes that might be found during PTC.
I got v38 over the weekend, and every time I go to use my Quest 2 since then, the battery is dead. This typically happens when an update has just been installed, because I keep my headset in standby, with a lens protector on. The headset wakes during the update process, and then stays on (because the proximity sensor sees the lens protector) until the battery is drained. I don't think there have been further updates since the initial one (I haven't noticed a change in the version number), but something is causing my headset to wake from standby every day now under v38. Rather inconvenient--I guess maybe I need to cut a hole in my lens cover to prevent triggering the sensor.
On further investigation, it might just be poor battery management. I just checked my headset, and it’s lost 15% in standby from a full charge 5 hours ago. This is definitely not typical behaviour.
Edit: Yeah, my battery is just draining too fast in standby with v38. I checked it again this morning, and I’m at 54% at 14 hours of standby after a full charge. I’m losing a little over 3% per hour. I used to lose 5 to 10% over 24 hours of standby.
I can't remember if I left manually or if it was automatic after a reset so you might want to confirm that before if you are in and plan to do a reset, so I'm out and my kudos this round goes to putting the desk and couch feature in the guardian setting.
On Initial boot... Meta icon and 3 dots appear center of screen regardless of orientation, either laying down or sitting upright, however when room lights are off, the warning image that follows with confirmation box is not center of screen vertically, making you have to sit back up to select confirmation button, also the pointer dot randomly starts un-aligned with controller, even after pressing Oculus button to attempt alignment, sometimes you have to point in very odd direction to select. After confirming the lights are dim and tracking is being turned off, you are notfied a second time in the home environment... a tad annoying...
I like the animation tweaks in the Space Station Home Environment, but the ships pass behind the starfield so the stars are closer than the ships. The ships also pass thu each other like Tie Fighters 😉
Hi, following my initial post on v37 which made the rendering blurred and chromatic aberrations the 37.0.0.147 patch had partially solved the problem and removed much blur. With the version 38 I find the blur of the beginning of the v37 😐.
Did you get this resolved? Ive had 3 of them do the same exact thing. It wasnt during an update or anything. Just random, i put it on after playing for a bit and all i have is the fading O logo. Is your unit new or a refurb? Ive read on another thread its a hardware issue. Some ribbon cable that doesnt sit snug on the mobo comes disconected
Feedback: It would seem there is some audio issue with v38.
I used to keep my Rift CV1's volume level in Windows (10) at 70% because 100% was painful. But now after the latest update, setting the volume to 100% is still too quiet - it's off-putting to play something like BeatSaber so quietly lol
100% on v38 feels more like 50% from v37 now 😞
I have tried going via Oculus support, but they're unable to help me downgrade my version so I'm stuck now - no amount of fiddling with audio settings in Windows is letting me up that volume any higher (and I can tell something's being throttled because the device test sound effect is very loud when I click it)
@Rogod, thanks for reporting! I haven't heard of any changes in the PTC for PC which might have changed any volume settings, but I've brought it up with the team in case there's any change that I hadn't seen. If you haven't yet, it'd also be good to put in a bug report with your details.