I am experiencing some stability issues on Windows 10. Sometimes the system randomly freezes (screen stays on, but no reaction until hard power off) or does not wake up, while being charged with Windows running. Other times the system runs perfectly for hours. I am not experiencing any problems under load.
My problems are not load related, and I have disabled the fast boot option in energy management. As there is no blue screen, I cannot find any info on what is causing it. It is a clean install. Except the two drivers for the cameras, all drivers are signed and either downloaded from Windows Update or gathered by scanning the Win 10 driver folder that has been uploaded on this and the techtablet forums. The graphics driver has been updated with the most recent Intel version.
What are your experiences with Windows? Anyone experienced something similar or is there a known faulty driver?
Other things I tried:
Error check on drive
sfc /scannow
Windows and this tablet have some problems... my experience http://forum.xda-developers.com/x98...-2048x1536-t2913035/post63550338#post63550338
They also occur when idle, when using the tablet everything is fine, problems are not easily reproducable and I did not find anything valuable in the event log, so i gave up and live with it.
I reinstalled windows, tried different bios versions, drivers... energy options, nearly everything I could think of^^
Wasted a lot of time, I now hard power it off instead of letting it "sleep" or whatever it does, I guess some driver is faulty with the windows deep sleep aka "connected standby".
I narrowed it down a bit. I kept looking for driver updates via Windows Update and examining the different powercfg reports. (my thought was, if the driver or app misbehaves in connected standby, it is not good). Now the system seems stable on battery power and connected standby seems to work as expected.
I do have problems while connected to the charger. The device will not wake up after a longer time if it goes to sleep while charging. I also noticed that the sound driver seems to alter its behavior when power is connected, so testing now with volume=0. (some well known problem with the audio driver on other tablets)
My fresh install of win 10 (1511) just slept to death again. This time there was an entry in event log. LockApp.exe crashed after waking up, so silly, eventlog is full of errors that shouldn't be there on a fresh install.
One question, does shutdown work for you (win or android)? Mine seems to power off, but it isn't really off. Drains battery and before you can turn it on again you have to hard power off (even though it looks like it is off).
Positive thing about fresh install of win 10 (1511) is that wlan works out of the box, also some more drivers are downloaded automatically (but seems not the ones that cause problems^^).
fraz0815 said:
One question, does shutdown work for you (win or android)? Mine seems to power off, but it isn't really off. Drains battery and before you can turn it on again you have to hard power off (even though it looks like it is off).
Click to expand...
Click to collapse
I did not switch it off often enough to reach any conclusions. Seen it fail when shutting down from Windows several times, from Android things seem pretty stable. To test, I attach an USB lamp to the OTG adaptor. When the tablet shuts down it turns off USB power and the lamp turns off.
Related
So two key events happened with my phone - the replacement battery I ordered finally arrived, and I also crawled out from under a rock and flashed the ICS partition and pengus77's CM10.
I was advised to calibrate the replacement battery by charging it from 0 to 100 with the phone powered off. So I streamed a random high res youtube video to drain the battery as fast as possible, then powered off the phone and plugged it into a USB port on my work laptop (a HP Elitebook running Windows 7 Enterprise x64).
The phone started charging (battery animation screen appeared) - and then my laptop started to install drivers. A few minutes later, I got a windows BSOD - yes the blue screen of death, not the black screen on android.
I initially thought something else caused the BSOD, so I left the phone plugged into my laptop and rebooted. As soon as my laptop got past the "starting windows" screen, it BSODed again. Didn't even get to the "Please wait..." screen.
Tried to reboot again - BSOD before getting to the "Please wait..." screen. Finally I suspected my phone was the culprit, so I unplugged it. Another reboot - it successfully got to the "Please wait..." screen, and then I plugged in the phone (still off), triggering a BSOD in under 10 seconds, before I could even get the field to input my password.
Rebooted with the phone plugged in but powered on this time, and my laptop fully booted all the way, no BSODs. But if I powered off the phone and plugged it in, BSOD! Looks like I'll have to wait till I get home to my AC charger before I can calibrate this battery
This is quite strange - I never had any problems like this on the old GB partition, if I were to plug in my phone to the laptop with the phone powered off.
Has anyone else experienced such an issue before? If it helps, my work laptop is a corporate machine so I don't have admin access over many of its functions (though I can still install and uninstall programs like normal), and it's loaded to the brim with corporate bloatware, and it's possible these properties contributed to the BSOD.
Charging(forming) new battery via usb is never recommended to be honest
Most usb device don't provide enough power or stable voltages like charger designed for our phone
I personally never liked charging via usb(most usb hub's dont work properly also if they need to provide current to hungry device(our phone example)..
I have no prob's with that options and also using custom battery 1700mah...
I have no sod's on win but have read that people had problems and sods sometimes with usb charging...
It's hard to pinpoint exactly where problem lies,could be your low power usb on motherboard crashing your win or something else..
Hmm that sounds likely. I'm back home anyways and will use my AC charger to condition the battery.
I remember that on the old CM10 nightlies (before the call bug was fixed), the USB charger always BSODed my phone...
... an easy solution would be to start using a real operating system on your computer instead of windows
pengus77 said:
... an easy solution would be to start using a real operating system on your computer instead of windows
Click to expand...
Click to collapse
Believe me, I do - I use Linux as my main OS on my home computer, and only boot into Windows for games
However this is a corporate laptop that doesn't actually belong to me and I can't meddle with it like that.
Suddenly, my HTC One turned off while listening to music, I thought that it just overheated and powered down like it had once before. I tried to power it on but it didn't work (I held the button down for 30-60 seconds, and then re-tried whilst holding the volume buttons and exposing the ambient light sensor to a bright light). The phone has a recent version of CyanogenMod running on it (a nightly from July) and the AGK kernel on it. I did mess with the clock speed of the processor and tweak some kernel settings, not sure if this had anything to do with the problem though (double-tap to wake was enabled along with 'Logo2Menu' or whatever the actual name is). The phone also doesn't seem to be charging at all; the red LED indicator doesn't turn on at all. Any solutions or possible reasons why it's not working?
TheGoldenMagikhrp said:
Suddenly, my HTC One turned off while listening to music, I thought that it just overheated and powered down like it had once before. I tried to power it on but it didn't work (I held the button down for 30-60 seconds, and then re-tried whilst holding the volume buttons and exposing the ambient light sensor to a bright light). The phone has a recent version of CyanogenMod running on it (a nightly from July) and the AGK kernel on it. I did mess with the clock speed of the processor and tweak some kernel settings, not sure if this had anything to do with the problem though (double-tap to wake was enabled along with 'Logo2Menu' or whatever the actual name is). The phone also doesn't seem to be charging at all; the red LED indicator doesn't turn on at all. Any solutions or possible reasons why it's not working?
Click to expand...
Click to collapse
connect it to your pc and open windows device manager, is the phone listed? Maybe qhsusb_dload?
alray said:
connect it to your pc and open windows device manager, is the phone listed? Maybe qhsusb_dload?
Click to expand...
Click to collapse
Nope, Windows does not seem to recognize the device at all...
TheGoldenMagikhrp said:
Nope, Windows does not seem to recognize the device at all...
Click to expand...
Click to collapse
Ok, so after hours of trying to turn it on it turns out the battery was completely drained and coincidentally my charger has stopped working making it seem as though it wouldn't charge or turn on. That though still doesn't explain why the battery went from 59% to 0% in an instant while listening to music.....strange.
TheGoldenMagikhrp said:
59% to 0% in an instant while listening to music.....strange.
Click to expand...
Click to collapse
looks like a defective battery...
Hi,
My techlast won't turn on anymore. The power button does nothing, no matter how long I press it. Also pressing power and volume + of - doesn't do the trick.
This thursday I upgraded to Windows 10 and installed bios v2.02 plus lollipop using 'mirek190_rom_v5.0 - android Lollipop.' All went well, I could boot Windows 10 as well as Lollipop. Booted several times and switched operating systems.
Then from lollipop I chose to boot into Windows. After using Windows I shutdown Windows and it shut down normally.
Then the thing died or something, it just does not respond to anything anymore. When charging I do feel that the tablet is a bit warm, but it just does not respond to the buttons on it anymore.
Is there anything I can do besides keeping it as a coffee coaster? I have looked at how to unbrick the tablet on these forums, but I just turned it off and it was not bricked during flasing or anything. Oh, it's a c5j6
It works again!!
I connected the teclast to my laptop with USB and pressed the power button for 30 seconds (I read that somewhere). Nothing happened... Then I disconnected it from my laptop, and pressed the on button for like 7 seconds... just for the sake of it.... And...YESS, normal boot screen, chose Android and everything works! Very happy
Holy crap, I did exactly what you did with my X98 Plus — and it also worked! I've no idea why. My tablet is almost new, had it for a month or two and used it for like 15-20 hours in total, no gaming and other heavy stuff. It was ~90-95% charged yesterday, I didn't install anything new, just put it to sleep (short press of the power button) yesterday from Win10, and it won't turn on today. Tried holding the power button for different amounts of time, tried charging it with different chargers (both the charger and tablet were always cold though). Nothing. Then found your post and did the same thing, connected to a laptop, power button for 30 sec, then disconnected and power button for 5-7 sec.. And it turned on!
What's the logical explanation here, why did it turn on after that? Something to do with the laptop's usb power? Mine had a usb3 port, so it should be quite "beefy", probably the same current as some of the chargers I used before. Something different about laptop usb ports that I don't know about?
Thanks
Hi guys, I have a huge problem.
Currently I'm on vacation in Croatia, where it's around 38-40 C every day. One day I had to log into an unsecured wi-fi. I know, i shouldn't have done that but it was urgent. Well, the same night (while charging) my phone turned off itself and I had to turn it back on on the next day. It worked the whole day until I opened the camera. Suddenly the phone went off and I wasn't able to turn it on. At first I thought the battery has drained so I plugged it into the original OP charger (dash). It gets warm while charging, but the LED is not turning on. After an hour of charging I still can't turn the phone on. Not even after a charging over night. There's also no vibration after holding the power button, neither holding the power-button for 20 (or more) seconds . I can't even get into recovery mode by holding volume-down and power.
I'm on original Resurrection Rom.
Is there anything else I could try? Could it be that some hardware is damaged (overheated)?
Since I'm on vacation there's currently no way for me to do any kind of unbricking until I find some phone-repair service.
I'm not a pro, but Im pretty sure the problem occur on the hardware side since the phone is not taking the charge and no vibration
I once had an Android phone (not 3t), the same thing occured, the phone I had had some hardware damage near the battery so I experienced the same problems you listed, ended up getting a new phone
Overheating is probably not the issue, at least not the 40C air temps you mentioned. These devices can probably something like 60C (internal temp at CPU or battery) before seeing any damage. Lot of folks live where it's just as hot as where you are, if not hotter. So I have to think the device is designed to work under such conditions.
Try holding the power button longer (a minute or more). I don't know about this device. But on my old HTC M8, there were instances where the phone powered off by itself. And the power button needed to be held over a minute, to make it boot. Although no charge LED is concerning.
Mine did the same a few days ago, was tethering and the phone just shut off. Buttons didn't work, no vibration, no charge LED, no anything. Thought it died but after plugging it into a PC it was detected as QHSUSB_BULK (hardbrick).
But it turned on normally after a minute lol.
Hallo. Mine also crashed. I was in the sunset playing game and taking pictures. Then phone suddenly got so warm and lagged, It turned off itself. No reaction. I connected into charger and then turned on hopefully. I think you must take care, because it has metal body and easy heating, and when heating it's lagging and not works good
My opinion is that it's overheat problem
BTslo said:
Thought it died but after plugging it into a PC it was detected as QHSUSB_BULK (hardbrick).
Click to expand...
Click to collapse
You will see Qualcomm download mode message (QHSUSB_BULK) whenever the device is powered off. It needs to be powered on, at least to bootloader (or recovery or OS) for the PC to connect in any other way.
Update
After 3 days, it finally turns on and charges as expected. Don't know if it has to do anything with it, but i let it in the charger for 1 day.
but now another problem occured.
every time I press the homebutton the phone crashes and goes off. this only happenes if the fingerprintscanner is not requested.
i.e. unlocking phone with fingerprint, does not crash, but... pressimg homebutton to go back to home screen crashes.
Essentially, been using LineageOS ROMs since I got this phone two years ago, everything had been working just fine and generally happy with this phone.
The story starts that I had just charged my phone overnight, had woken up, unplugged it and was looking at my notifications.
Opened a WhatsApp notification, instantly the launcher seemed to crash and was unresponsive, although the notification tray was functioning still. Tried to turn off the phone via the power menu, device did not shutdown. Forced power off on the phone, phone turned off.
Immediately I was unable to turn the phone back on. Tried recovery, fastboot boot methods and the device would not turn on at all. The screen is black and the device not responding to anything power related button combinations. When I plug the device into power, no charging light appears on the phone, the screen doesn't turn on at all with the typical charging animation when it's in the off state. When I plug the device into my Ubuntu machine, no USB device is detected by the kernel - as though nothing is plugged in at all. When I plugged it into my battery pack however, it did appear that it detected a device and flashed it's LED as though it was charging a device that was plugged into it.
I had not wet the device, or *recently* dropped it. It lives in a pretty reasonable case and has stood the couple years of my use with essentially no scratches other than some very minor abrasions on the screen.
I have a little phone electronics tool kit and a hair dryer, and as the battery was fully charged before this had occurred, I decided to pull the phone apart and disconnect the battery from the mainboard behind the NFC assembly. I also tried disconnecting the power charging circuitry in case something was shorting in that area - still nothing. Left the device with the battery unplugged from the mainboard for 5 days, and just tried it again - still no dice.
I'm just wondering if anyone knows what the cause might be. At this stage, I'm suspecting a mainboard failure, in which case data recovery seems unlikely. I have had over two years out of the device, it's far from the end of the world. I'm reluctant to spend any money trying to repair it particularly if it's the mainboard, I'll lose my data anyway. If I were able to retrieve the data from the device that would be of some benefit to me, about a weeks worth of photos and some chat history with my GF; so some questions I have:
1. Should I be able to power on the device with a USB C cable plugged in but the battery unplugged?
2. Apart from what happened above, does anyone have any suggestions about the cause remembering that it doesn't turn on into any boot mode at all?
Do you have any windows device?
jjgvv said:
Do you have any windows device?
Click to expand...
Click to collapse
No I don't sorry. I also bought a new battery for the Mi 8, the device still didn't turn on or charge. I think I can safely say the phone is cactus.
berglh said:
No I don't sorry. I also bought a new battery for the Mi 8, the device still didn't turn on or charge. I think I can safely say the phone is cactus.
Click to expand...
Click to collapse
you are probably in edl mode and linux does not kinda very like edl mode
Hi, I have the same problem, but with the latest Xiaomi eu stable. I just put my phone in my pocket after a full charge and when pulled it out just a black screen and now it's exactly like yours
Did you solved the problem?