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

    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
    • Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release by Usama Jawad Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time. In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement. Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now. Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles: 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026. As such, IT admins have been encouraged to begin validating Windows Insider releases in the Experimental Channel, plan rollout rings, and strategize the utilization of their existing deployment tools.
    • Windows 11 gets new audio improvements in the latest builds by Taras Buria Today's Experimental builds (26H1 and Future Platforms, formerly Canary) pack several audio-related improvements. If your device is enrolled in the Experimental Channel (26H1), you can download build 28120.2315, while those in the Future Platforms version have build 29613.1000 to try. Here is what is new in build 29613.1000: [Audio] Following up on our previous improvements, we’re making some more adjustments to Settings > System > Sounds based on your feedback. Namely, we’ve updated the “All sound devices” page so: You now have the ability to change default devices from this page. Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. We’ve adjusted the page design slightly so now you can filter whether you’re viewing input or output devices. We’ve added toggles so you can choose if you want to hide or show disabled, disconnected, and unplugged devices on this page. We’ve also updated the input and output audio properties page for devices in Settings to now include jack information for those that need it. And here is the changelog for build 28120.2315: This update includes a small number of minor bug fixes and improvements. [Accessibility] This update improves caption style responsiveness by redrawing captions immediately for caption style changes. If no current caption is visible, a sample caption string is displayed. [Audio] This update improves the reliability of the inbox HD Audio driver. You can find the official release notes for build 28120.2315 here and for build 29613.1000 here.
    • I agree with what I think you are saying, just not in the way you are saying it. Like any tool, the amount it represents your work is perorational to the effort you put into it. It is similar to why 2nd grade math students learning to add and subtract are not allowed to use calculators, but a high-school calculous student is. For the 2nd grader, that tool would completely replace the work they are doing, for the calculous student the same tool allows them to work far more effectively while in no way replacing their effort or knowable. If you spend 30 seconds writing a prompt, then the image that comes out is no more "yours" than if you found the same image with a Google Image search. However, many of these generative tools also support highly iterative processes that allow back and forth, and merging generated images with photos or human created images. I am sure you would agree that a human spending hours of time working on a project, even if AI was involved in the process, still reflects that human's work.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      575
    2. 2
      +Edouard
      189
    3. 3
      Michael Scrip
      79
    4. 4
      PsYcHoKiLLa
      78
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!