Recommended Posts

Waiting for you to turn off the system before it downloads and installs the update is to make sure the user doesn't try to do something that could mess with it.  The only downside is that it doesn't restart on it's own after but waits for you to.  That could be to make sure someone is actually home and not away.  What if you don't have it set to go into standby on it's own after a set period of time being idle?  Then it would stay on till you got home, don't think anyone want's that.  Of course I'm sure they'll update the update process itself so we'll see how it is later on.

I turned my Xbox One off (using "Instant On" mode) a few minutes ago. I can hear the hard drive working. So I'm guessing it's downloading the update? :huh:

 

When I first tried instant On, it took whole minutes for the Xbox to stop making any noise, disk/fan etc.

I completely understand why the system needs to be reboot but they could have made it better.

If some Joe user didn't know about this update and was using instant on, won't he be left clueless why his Xbox doesn't respond to Xbox On anymore?

They could have

- Download the update in the background and go back to "sleep" (instant on) state.

- When user wakes it up the next time, prompt for update, install it, reboot and done!

The only logical way I can see this being possible.

 

MS don goof.

Now if they can just get the "Xbox On" command to work properly, like the rest of the commands... it's like a 25% success rate, and like the mic is too low to pick up the command, unless you get really close to the Kinect, I have verified the issue with the console using 2 different Kinects.

Now if they can just get the "Xbox On" command to work properly, like the rest of the commands... it's like a 25% success rate, and like the mic is too low to pick up the command, unless you get really close to the Kinect, I have verified the issue with the console using 2 different Kinects.

I see this mentioned, but it might not be that the command doesn't work, there could be other reasons:

1. Mic needs to be calibrated again with a louder volume set to your speakers for the calibration

2. Maybe there is a placement issue.

So I would highly suggest anyone that is having the problem you mentioned to try recalibrating and crank that sound. You don't need to blow up your speakers, but I can verify that having that volume too low during calibration results in the mic not picking up commands nearly as well and requiring you to be fairly close.

If it fails to improve at all after that, then maybe its a defective Kinect.

I see this mentioned, but it might not be that the command doesn't work, there could be other reasons:

1. Mic needs to be calibrated again with a louder volume set to your speakers for the calibration

2. Maybe there is a placement issue.

So I would highly suggest anyone that is having the problem you mentioned to try recalibrating and crank that sound. You don't need to blow up your speakers, but I can verify that having that volume too low during calibration results in the mic not picking up commands nearly as well and requiring you to be fairly close.

If it fails to improve at all after that, then maybe its a defective Kinect.

 

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

It can't be a problem with the system in low power because not everyone is having your problem. I am not having your problem. That's why I suggested that something might be faulty.

As far as it not mattering since the room is quiet, I don't think that is true. I think the calibration actually adjusts how sensitive the mic is, in order to say work farther away or while there are other sounds in the room.

So if you have calibrated and it didn't fix anything, complain to MS and see what they say. Anyone having this problem should tell them about it because it shouldn't be happening.

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

 

 

 

 

 

I know exactly what you're talking about.

 

Same issues.. Saying "xbox on" after it's been off all night doesn't get recognized easy enough.

 

I've repeatedly had to say it 3 or 4 times at some points for it to actually hear me. Usually after getting right in front of it for it to hear me.

 

Seems to me it isn't hearing the command effeciently enough after being in the standby Instant On mode overnight as it does when you are actively using it. If you actively use the voice commnads, and even turn it off and back on a minute later, it seems to repsond well enough there. But overnight, it doesn't want to hear you in a dead silent room in the morning.  Like it's in too deep a sleep mode.

I maybe imagining it but Forza 5 doesn't play as smoothly since the update, anyone else notice this, am in the UK?

 

EDIT

 

I fixed this by getting the X1 to redetect the TV and set it to HDMI rather than HDMI(Auto) then changing the resolution from 640 to 1080P.

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

Have you tried "Yo... Xbox On". Or something like that? Sort of waking it up, ready to listen.

 

Does it work if you say it loud enough?

Have you tried "Yo... Xbox On". Or something like that? Sort of waking it up, ready to listen.

 

Does it work if you say it loud enough?

 

 

Doesn't really matter how loud you say it, it only seems to work for me if I get like real close to the sensor 2-4 feet away, then I can say it normal or loud. If I say it normal or loud from 8 feet, it doesn't wake.

Well there has to be some variable that is different for those having the problem and those that are not.

Maybe its the range. My couch is 6 feet away and I can get the X1 to turn on with a normal voice whether that is from sitting overnight or after its been on during the day.

I'll try it from say 8 feet away and see if it is unable to pick me up like xendrome has run into.

Booting from cold start now definitely feels faster for me. I don't have the Instant On feature active as my One is plugged into a plugboard with other stuff that gets switched off at night, I don't turn the console off anyway unless I want it fully off, if I'm in the middle of something I leave it on :)

I completely understand why the system needs to be reboot but they could have made it better.

If some Joe user didn't know about this update and was using instant on, won't he be left clueless why his Xbox doesn't respond to Xbox On anymore?

They could have

- Download the update in the background and go back to "sleep" (instant on) state.

- When user wakes it up the next time, prompt for update, install it, reboot and done!

 

Dude, I knew about the update and I still forgot why my Kinect wasn't responding. Then it clicked afterwards, but whatever, hopefully they smooth out these things.

Booting from cold start now definitely feels faster for me. I don't have the Instant On feature active as my One is plugged into a plugboard with other stuff that gets switched off at night, I don't turn the console off anyway unless I want it fully off, if I'm in the middle of something I leave it on :)

I can second your observation.

I did a quick test and my cold boot times went from 30 seconds to 21 seconds. So they did something to cut those times.

That's good news, I bet they'll make it even faster with a few more updates as they optimize it more and more.  I really want to see what benefits come to the games.

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

Off topic- but which mount did you pick up?  there is only 1 on amazon and the only review says it wont work with the new kinect

 

http://www.amazon.com/LETECK-Xbox-One-Kinect-Camera-mount/dp/B00GU0H5X4/ref=sr_1_1?s=videogames&ie=UTF8&qid=1386874002&sr=1-1&keywords=kinect+tv+mount

This topic is now closed to further replies.
  • Posts

    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
    • They said by this time everyone will have flying cars. WELL...
    • A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. Maybe not as we now know that time can flow backwards.
    • Of course. Simply reverse the polarity.
  • Recent Achievements

    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      577
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!