Windows Phone 8 users report random reboots and battery issues


Recommended Posts

Windows Phone 8 users report random reboots and battery issues

Windows Phone 8 devices have been available since the beginning of the month and users are starting to report early issues across HTC and Nokia handsets. In a thread over at WPCentral with 143 replies, a variety of HTC 8X users report that handsets randomly reboot while in use. A thread on Microsoft's own support forums has also gained 50 replies complaining about the issues. The Verge can confirm that an 8X we are testing has rebooted on more than one occasion.

Nokia Lumia 920 users are also reporting random reboots and freezes, with some complaining of poor battery life too. In a thread on Nokia's support forums, a number of users appear to be complaining of lock ups and resets with the Lumia 920. Battery life issues have led to some users wiping their devices in hope of a quick fix, unfortunately that seems to have resulted in some devices left stuck on a Nokia splash screen. In our own experience with several Windows Phone 8 devices, we've found that disabling the tap + send (NFC) feature results in improved battery life. We have reached out to Microsoft, HTC, and Nokia to discuss the issues and we'll update you accordingly.

Source: The Verge

Interesting, haven't had any issues with my 8X yet, although I was thinking a bit before launch that with these unibody designs what happens when it locks up. I would say its rare but my WP7 device locked up a cpl times and removing the battery was the only way to reboot. I guess you could wait for the battery to drain. Will be interesting to see what comes of it but I always have BT and NFC disabled until I need them otherwise yeah just chewing battery, only a cpl of taps to quickly re-enable them.

I have waited a week before I coming to any conclusions. The verdict is my battery is draining faster than it should. Turning off every service on your new phone isn't how it should be. Just a small example, gleek and a battery monitor is all that I had allowed for background tasks and I put the phone in my pocket at 90% about 25 min later it had gone down 10%. Medium brightness. Started angry birds star wars at 43% after 10 min I got a battery warning, phone was at 10%.

So I've started to participate in those threads the OP posted. A week in and I doubt MS or Nokia will acknowledge issues with these phones. I'll be on the phone with AT&T in the morning. If I get hassled for a replacement 920 I may just replace the OS entirely.

I've had mine restart 8x, I thought the battery died, but still had 20%~ left.

One issue thats driving me bonkers, is it takes 15 seconds to connect to wifi after you wake the device up. Why can't they always be connected like my iphone :(

I went from the Lumia 900 to 920.

Other than hangs and reboots I've enjoyed the experience.

Uninstalled FB and nokia Maps and Drive as a safety.

I got BT issues, my car hates this phone right now to the point where I can stream music but get no navigation options from my steering wheel or locks the phone. The LTE option causing network drops which I experienced quite a bit, 0 drops when I switch to 3G or 2G.

I turned off all phone features, starting with BT, WiFi, NFC then even switching to 3G then 2G. I even turned off the high sensitive setting on the screen. Turned off backup options and rebooted the phone so it would save those settings. I notice even if you change a setting it wouldn't really save if it rebooted 30 min later....

Any other ideas? Mind you it's running atm... I'll test bluetooth later since my phone doesn't "lock with password"

This topic is now closed to further replies.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • 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.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!