Discussion in 'Hewlett Packard' started by penname, Feb 9, 2013.
Maybe there is a power management item you could turn off so it does not shut down.
We have many of these devices in our environment and are using the latest drivers. I could make a list of the drivers and version numbers but would prefer to hear if other people have this issue as well before hand. and if anyone has fixed the issue.
1. Wi-Fi sometimes just vanishes from the network connection list.
2. Mobile Broadband vanishes from the network connection list.
3. Screen Rotation stops working.
When ever any of these happen the HID sensor and Geolocation Sensor both get an error 43. and display a yellow exclamation mark in device manager. Any ideas?
(I have also tried the power setting on USB Root , l2C HID , and disabled selective suspend from the mobile broadband driver.)
I own 6 elitepads( 1 is elitepad 1000), surface pro 3 i7, Samsung ativ 700 i5 and three no-name Atoms and I must say the problems I had with Elitepad 900s are quite identical to the ones I have with the other Win10-tablets I own. I do strongly believe the Atom-processor( the chipset) is the main cause to all the problems( as the problems with Epads are identical to the no-named Atoms') the Elitepads have. Additionally the i5 and i7 tablets have similar issues, but also some new ones, so my conclusion is that they are all OS-based rather than HW design-based issues.
I did not have that many problems with Win8.1 on the devices and I've read from quite many places that the biggest cause, in Win10, is the drivers have to be signed/certificated( or alike) and that system seems not work.
Not sure if anyone else is still using their ElitePad 900 but thought I'd mention that I successfully updated mine to Windows 10 Creators yesterday. Took forever especially since it forced me through the Anniversary Update first. Minor problems with drivers but nothing too difficult to fix. And I'm pleasantly surprised that it seems a bit snappier with Creators.
My Elitepad is now 50 months old, used every version of Windows 8, public previews of Windows 10, and now every production release of Windows 10. Extensive travel by air and car coast-to-coast and still chugging along. I've moved on to a Surface Pro 4 but still regret that HP gave up on the ElitePad infrastructure.
Well I'm still using my Elitepad 1000 anyway. It has become frustrating this year though, because since I updated to BIOS 1.40 Rev.A in Jan, the tablet has begun to crash (some kind of 'Kernel Power State' error) once or twice a day, meaning I can't keep any apps open. It's really frustrating, because under BIOS 1.33, even on Win10, this didn't happen, and now 'due to security changes' I can't go back to that BIOS version apparently.
I guess maybe these sleep-state issues are similar to those experienced by Win10 tabs like SP4 etc, but damnit, it wasn't happening on my original BIOS. I wish I'd ignored HP's 'Critical Alert' and just kept it as was.
EDIT: Oh yes, I believe screen rotation has become flaky since the BIOS update too. Basically made tablet use much worse.
UPDATE: They just released BIOS 1.41. It still crashes each night. Sigh.
Wish I ignored those BIOS updates for the 1000G2 also. Same issues, randomly.
I had two elitepads that randomly crashed but I'm not sure it was the bios version. I think it's a hardware issue. One was on a very old bios and was returned under warranty 18 months ago. The one I have now is on bios 1.41 but rarely crashes. Still does though which is annoying at the worst times.
The other random thing I noticed on the 1000G2 (BIOS 1.41), is that after resume from sleep, the system seems to slow down considerably. It seems to depend on what apps are up. It's weird. Thinking about doing an OS reinstall. Never did a clean one on this device.
I've been seeing a lot of stories recently that Windows 10 Creator is being blocked on devices using the Clover Trail, like the ElitePad 900 G1.
The interesting thing is that I successfully installed Creator on my ElitePad 900 back in mid-April. Not sure if I got it installed before Microsoft cut off access. I even just checked the installed version to confirm I actually have Creator - I do. But from reading various articles, the root cause is the GPU which does not surprise me at all.
My guess is that unless they fix they problem, I'm at the end of the line as far Win 10 OS updates. If the next Win 10 release doesn't install, I'll give some thought to reverting back to Windows 8.1
Separate names with a comma.