Meta Quest Pro Lens Issue

-

The Problem Meta Doesn't Want You to Know About...and The Worst Customer Support Ever

The Problem

When using the Meta Quest Pro with a game or app taking place in a dark environment, yellow / brown / auburn colored haze appears along the outer edge of the lenses (more so, seemingly, on the right lens, and more near the top of the lens). In a bright game or app, the problem isn't visible, but when using a dark one, this problem is apparent.

In the picture below, the issue can be observed most prominently near the top of the lens -- that brownish haze.


It's been speculated that the issue could be backlight bleed or IPS glow, but as far as I know, neither has been confirmed.

Here are some of the threads from Reddit and from Meta's Support forum discussing the issue:


(This one contains a "solution" that does not fix the problem.)





This one is the most concerning, where the author states that Meta told him this was "normal":

These are just a few of the online discussions about this issue.

The issue was noticed shortly after the product was released. So what has Meta said or done about it?

Very little.

Meta's Support Staff

At this point I have to admit to purchasing this headset. There were people skeptical of the price, and of the technology, and they were right. There are some things the Quest Pro does very well, but overall, between the price, this lens issue they seem to be trying to keep quiet, and their awful support process, Meta is a company to be avoided.

My own experience with the support staff followed these general steps:
  1. I submitted a support ticket, providing the details of the problem along with links to pictures of it.
  2. I was advised to do a factory reset (on a device I had owned for a handful of days at that point and had installed few apps on).
  3. The factory reset did not help.
  4. I was offered a replacement unit.
  5. I expressed concern about getting a replacement unit if the engineers did not know the cause of the problem.
  6. Reports began rolling in to Reddit about people getting replacement units having the same problem (sometimes having it worse than the unit they sent back).
  7. After a lull, Meta followed up, again offering me a replacement.
  8. I, again, expressed my concerns.
  9. Meta claimed to inspect each unit thoroughly before sending it out for replacement.
  10. I let them know about the people getting replacement units having the same problem.
Then, the following steps would repeat:
  1. I'd follow-up with Meta, asking for an update on this problem.
  2. Meta would ask me for information I had already provided.
    1. The support rep seemed to not know anything about my ticket, nor did they seem to have read anything prior in the thread.
This happened multiple times. It's worth noting that I don't think I ever received a response from the same person at Meta. They seem to have a pool of people, and each new person on the thread would appear to be unfamiliar with the issue, as if they hadn't read any of the previous messages.

Finally, I asked to speak to a supervisor. Twice. After the second time, they told me it was not possible, gave me instructions on how to get in touch with support over the phone, then told me they were closing my ticket.

Additionally, I left messages on the Meta Support forum. This is the only place where I saw any response that mentioned that they were aware of the issue but still trying to determine what the cause was. And unfortunately, the lack of care and attention to detail was the same here as well. At one point, I mentioned having submitted a ticket about the issue and not getting any help, and a moderator responded and advised me to...open a support ticket. At one point in this whole process, I had even created a support ticket about how bad Meta Support is, and that I need support of an issue, and was admonished for creating a second ticket.

This company just does not care. Legendary developer John Carmack summed it up best in his recent resignation letter from Meta, when he said "Make better decisions and fill your products with 'Give a Damn!'".

Tell Us What You Think
One last point to illustrate Meta's terrible support process is the pop-up you get when visiting their support forum. It's titled "Tell Us What You Think", and asks you to provide feedback. I did this once, and was prompted to again later. So, again, I took time to provide information, only to have the prompt reject my feedback because I'd already provided it. For a forum that requires you to be logged in to post any messages, rather than check who you are and if you've already provided feedback, the company asks for your feedback regardless. For those of us already unhappy with them, spending a few minutes to provide feedback only to be told "Nevermind" just makes us angrier.

Next Steps?

I remember a number of years back when Samsung had released defective DVD players and wasn't making things right with their customers, a class action lawsuit was filed. I'd love to know if this an option. If anyone reading this knows more, or would like to join one, I would be very interested.

Comments

Post a Comment

Popular Posts

Resolving the "n timer(s) still in the queue" Error In Angular Unit Tests

-
A few months ago one of the developers I work with ran into the below error in an Angular unit test: 1 timer(s) still in the queue The fix was to specify a particular amount of time in the tick() call as shown below: it( 'should set accountConfirmationDetails when getAccountConfirmationDetails is called' , fakeAsync(() => {          // Arrange          let  spyGetAccountConfirmationDetails = spyOn(accountService,  'getAccountConfirmationDetails' )         .and         .returnValue(Promise.resolve(AccountMockData.mockAccountConfirmationDetails));                    // Act         fixture.detectChanges();         tick(15000);          // Assert         expect(spyGetPaymentConfirmationDetails).toHaveBeenCalled();           expect(comp.zone).toBe(42);           expect(comp.hasValidProfile).toBeTruthy(); })); Hoping this helps someone!
Read more

How to Get Norton Security Suite Firewall to Allow Remote Desktop Connections in Windows

-
Image
I ran into an issue recently with RDP connections being blocked by the firewall in Norton Security Suite. I checked the traffic rules under Settings > Firewall > Traffic Rules  and found that it was enabled by default (and couldn't be edited): But during further research, I found  this page  on Norton's support site which discusses the different trust levels of networks and mentions that, for the Public trust level, "This setting also blocks remote desktop connections by default.". I checked my network's trust level, and sure enough, it was set to Public (I'm not sure how/why). (Sidebar: Notice in the screenshot above that allowing Remote Desktop for Public Networks is defaulted to Allow , though that rule is not active). Here's what my network trust level looks like now after changing the setting to Private (accessible under Settings > Firewall > General Settings > Network Trust ): After changing the network trust level t
Read more

How to Determine if a Column Exists in a DataReader

-
I recently had to work on something which required me to query a database, open the results in a DataReader, and check for the existence of a particular column. While the DataReader doesn't have a method to do this, with just a few steps I was able to accomplish this task. Here's how. First, the DataReader has a method named GetSchemaTable() , which returns a DataTable consisting of information regarding the data contained in the DataReader. The first column in this DataTable is named ColumnName , and its value is (obviously) the name of the column. Knowing this, we can loop through the rows in the DataTable, checking the ColumnName column for a value that equals the name of the column we're looking for. To this end, I wrote a static method in one of my classes which takes the DataReader and the name of the column being sought: (C#) public static bool HasColumn(DbDataReader Reader, string ColumnName) {    foreach (DataRow row in Reader.GetSchemaTable().Rows)    {       
Read more

Silent Renew and the "login_required" Error When Using oidc-client

-
I recently implemented the Silent Renew functionality of oidc-client in an Angular application I work on, and was getting reports that the users' tokens were still expiring. This made no sense to me as I'd verified the code was working during development, but yesterday I found the problem and am hoping it will save someone some time. The error we were getting back was "Error from signinSilent: login_required". This indicates that the user's session is no longer active on IdentityServer and they must re-authenticate -- which, of course, is what we're trying to prevent by using Silent Renew. In our case, the problem wasn't with the Silent Renew functionality, but rather the user's session was expired. The reason why  it was expired was because, for some reason, we were setting the session length to 15 minutes instead of the default 10 hours . What was occurring was that Silent Renew was attempting to renew a token after 55 minutes (60 minutes expirat
Read more

Fixing the "Please add a @Pipe/@Directive/@Component annotation" Error In An Angular App After Upgrading to webpack 4

-
I'm currently in the process of upgrading an Angular application which does not  use the Angular CLI from webpack 2 to webpack 4. The incremental upgrade from webpack 2 to 3 was easy, but once I made the jump from 3 to 4, I encountered a lot of problems. I went through them one by one, but the one that had me stumped was the following: Unhandled Promise rejection: Unexpected value 'MakePositivePipe' declared by the module 'SharedModule'. Please add a @Pipe/@Directive/@Component annotation. ; Zone: <root> ; Task: null ; Value: Error: Unexpected value 'MakePositivePipe' declared by the module 'SharedModule'. Please add a @Pipe/@Directive/@Component annotation. The code was transpiling/compiling fine, but this error was occurring when I'd navigate to a page containing this pipe. This code has worked fine under webpack 2 and 3. I made sure that the pipe was being set up as a declaration , which it was. What finally  corrected the issue for me w
Read more