I often use ACER Iconia W4 820 tablet to watch series in bed. I have it placed on a tablet stand so even when I fall a sleep in don’t break it. It’s great, when video stops playing, it goes into sleep automatically after a bit of time and that’s that.
Problem is, when I want to turn it on again in the morning, it’s just dead. Not even power on LED responds. First I thought battery was flat, but it still had around 50% charge after I managed to force wake it up…
I could wake it up using recessed RESET button to get it running or by holding POWER button for 10 seconds, releasing it and then pressing it again once. But that’s actually reset and that sucks.
After some digging, issue seems to be related to Broadcom’s wireless module “Broadcom 802.11abgn Wireless SDIO Adapter”. Fix was promised by ACER, but they of course never delivered it…
Apparently, in many cases, installing newer wireless driver helps. I managed to dig the latest driver from May 2015, provided by TOSHIBA. From the looks of it, it fixed the issue for me. It might happen again, but so far so good. It might also work with other devices that are experiencing the same wake from sleep problem and are using the same wireless module.
Broadcom Wireless Driver for Windows 10
So, back at fixing my sister’s laptop. It’s a 6 or 7 years old ACER Aspire 5520G. Last major repair was the baking of it’s GPU module because it was completely dud, few days ago I’ve reapplied Arctic MX4 thermal paste for the CPU and now I had to take out the entire optical drive electronics because it was clicking the entire time for no reason. She’s not using it anyway, so I just removed it. Just fixing it with minimal possible expenses, because it’s too old to invest in it anymore. Latest issue? It’s bloody standby mode…
And guess what. Standby problems seem to be by far the most complicated, frustrating problem of them all. I say that mostly because out of like 50 cases that I found on the internet, I don’t remember a single one that would have an easy solution available to that problem. That’s quite scary actually. If you get standby functionality issues, you’re pretty much fucked. All you’ll find are bunch of generic posts from Microsoft techies or vendors to check this and that which never resolved anything.
In my case of this ACER Aspire, I’ve tried reinstalling pretty much every single possible thing and the damn thing just wouldn’t wake from standby anymore (it used to work fine few weeks ago). As soon as it enters sleep mode, it just collapses. Power light shows like the laptop is working, but it just doesn’t wake up. After flying over the Event Viewer logs, there were some pretty scary events related to severe hardware failures (could be CPU or RAM) that I couldn’t properly diagnose even after checking the crash dumps. And since they don’t happen during normal usage and not during Memtest86, I had to cut some more corners again to get it working. And the solution is quite funny, but it works.
So, this laptop locks up as soon as it enters standby (or tries to wake up from it). I could just disable standby altogether, but since she often leaves laptop unused for several hours, half a day or even entire day, it would be a waste of power to keep it running idle on desktop. So it made me thinking, why not just skip the standby and go straight for hibernation. Set the laptop to turn off display after 10 minutes, disabled Standby and set Hibernation after 15 minutes. Left the laptop running idle and guess what, it hibernated perfectly and also woken up without any issues. This test confirmed that this little trick works, so I’ve extended the Hibernation period to 120 minutes (2 hours). This way it will now first turn off the screen after 15 minutes and then go into full shutdown with hibernation after 2 hours, skipping normal standby mode entirely. Brilliant. No more messing around trying to debug the damn standby issues, it can be used as usual, it will save power when not used and it will still wake up quickly from hibernation when needed.
So, here we go. Yet another day, doing crude fixes on ancient hardware that has zero BIOS and software support these days. And I got it working again. Oh joy 🙂