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

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!