Im fully fed up with this cycle of insanity the go puts me through:
Go to bed, discover the GO is empty again because for some completely ungraspable reason it really really needed to drain that 90% battery over the day.
Repair controller because yeah, if it gets fully discharged lets just forget the controller.
Start watching netflix, as usual the go cuts out and switches off after 20 minutes.
After rebooting and watching some more i put it down.
Get woken up by this fucking stupid dong sound it makes in the middle of the night.
Muster all my strength to not outright smash it against the wall.
I really need an eta for a system update for the go, this is beyond broken in its current state.
Edit: Fix has been released, device stays off as supposed when charging now !
Early reports indicate tweaked proximity sensor behaviour aswell.
I can see where he's coming from, when you use it before bed you want to plug it in to charge it up, so its ready for next time, but if it then turns on in the middle of the night with a beep, there's your sleep disrupted to unplug it and turn it off.
The suggested solution is to not plug it in before bed, but plug it in the next morning... except that means it turns itself on when you're out of the house and stays on for a few hours wasting power / battery and screen life.
At least if thats how I'm reading it, as I dont have a GO as yet, but if thats how it worked I'd be pretty annoyed too :smile:
Atleast one person got it, so understanding the now apparently fixed problem only eluded some, probably for reasons way beyond objectivity.
Anyhow - I think more praise to the the engineer who implemented the fix and the flying Spaghetti monster obviously !
Im glad oculus decided aswell that monitoring charging, disconnecting after a full charge and then pressing a button for 10 seconds is a lot but certainly no fix.
Theres a single mention on reddit aswell that it doesnt wake up by itself anymore when switched on, so they might even have tweaked the prox sensors threshold back to basic functionality.
Atleast one person got it, so understanding the now apparently fixed problem only eluded some, probably for reasons way beyond objectivity.
To be fair, lots of us "got it" and agreed that it was something that Oculus should fix.
We just also didn't think it was too big a deal, and that it was likely Oculus would fix it eventually, as the power management quirks have been mentioned a lot to Oculus.
And, it has been fixed.
That's a win win.. 😉
As for being objective or not...
Personally, my definition of objective would be maybe someone mentioning it as something that should be addressed and asking for the perspective of others, but thankful for other people's offers of temporary workarounds, and not thinking that a new product should be returned because of something that is likely to be fixed with an update...
To be fair, lots of us "got it" and agreed that it was something that Oculus should fix.
We just also didn't think it was too big a deal, and that it was likely Oculus would fix it eventually, as the power management quirks have been mentioned a lot to Oculus.
And, it has been fixed.
That's a win win.. 😉
As for being objective or not...
Personally, my definition of objective would be maybe someone mentioning it as something that should be addressed and asking for the perspective of others, but thankful for other people's offers of temporary workarounds, and not thinking that a new product should be returned because of something that is likely to be fixed with an update...
But that's just me... 😉
totally agree, as per my post I think!
13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro, Windows 11 Pro 24H2 (10.0.26100)
Atleast one person got it, so understanding the now apparently fixed problem only eluded some, probably for reasons way beyond objectivity.
To be fair, lots of us "got it" and agreed that it was something that Oculus should fix.
We just also didn't think it was too big a deal, and that it was likely Oculus would fix it eventually, as the power management quirks have been mentioned a lot to Oculus.
And, it has been fixed.
That's a win win.. 😉
As for being objective or not...
Personally, my definition of objective would be maybe someone mentioning it as something that should be addressed and asking for the perspective of others, but thankful for other people's offers of temporary workarounds, and not thinking that a new product should be returned because of something that is likely to be fixed with an update...
But that's just me... 😉
Thing is, i knew of the "Fix" mentioned here day one i got the hmd as i discovered it straight away, but as some people understood it plays absolutely no role for my specific use case so mentioning it again and again not understanding it does exactly nothing. ( And if someone would have really paid attention to what i wrote noone would even have suggested the "fix" either, but yeah i get it, the internet blawarghl. )
Not the way I read your original post (and I still don't see it in re-reading it just now).
I still think that some of the suggested workarounds could have helped given the information, but you chose not to want to put up with those. And that is your choice and perfectly OK, but a nice "Thanx, but that doesn't apply because..." I think goes a long way. IMHO
Atleast one person got it, so understanding the now apparently fixed problem only eluded some, probably for reasons way beyond objectivity.
Still fanning the flames? lol
Everyone got it. What you still can't seem to get is that the disagreement came from how you blew things out of proportion by making it seem as if the Power Management issue was preventing entire households from sleeping. The part you couldn't get from the beginning was that you could solve your problem yourself.
The update that the engineers released has not changed how I manage my GO at all. It's just an update that helps folks like you, who get easily upset over things that can get resolved with a bit of self-reliance.
You intentionally went back and quoted an earlier post from the 19th just to start talking smack again lol
Maybe its some erotic satisfaction you find in watching your devices charging, but in any case i envy you that even the update made it redundant, you still find the time every day / night 😄
Ok gents, the issue has been addressed and I think this thread is no longer productive. Thank you all for your input, your voices have been heard and Oculus has addressed the concern. Win-win for all.
I'm closing the thread 🙂
Core i7-7700k @ 4.9 Ghz | 32 GB DDR4 Corsair Vengeance @ 3000Mhz | 2x 1TB Samsung Evo | 2x 4GB WD Black ASUS MAXIMUS IX HERO | MSI AERO GTX 1080 OC @ 2000Mhz | Corsair Carbide Series 400C White (RGB FTW!)
