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

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • 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
  • Popular Contributors

    1. 1
      +primortal
      591
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      75
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!