Forum Replies Created
-
AuthorPosts
-
I use Hans Sprungfeld ‘.exe in autostart’ suggestion (post #46110);
http://techtablets.com/forum/topic/keyboard-trackpad-issues/#post-46110
@Eduardo, use update-option within device manager.
@Blackburn@Bleb, disabling IPv6 (if not using it), might also improve stability.I must admit the iWork10 is far from perfect but in their defence, hardware-acceleration seems a big problem with Chrome, also on other pc’s/chip sets. It’s either not working (while activated) or is unstable.
If your talking about Windows (not Android), Happened to me too (also with less wifi-activity). I updated the wifi driver (Device manager) and it seems to work better now.
Thanks for the input @brainvision. In my case the power-on problem usually occurs while on battery power 🙁
Could indeed by a problem with the button. I will give your suggestions a try. I have noticed the bootlogo appearing a few times at boot. I thought it was a response because I had pressed some buttons a few times 😉
Thanks for the tip @Jonas.
When I feel confidant enough I will give it a try (usually takes me a few days) 😉
First I have to figure out al the different modeltypes.
Anybody knows, is a TC is the same as TCL? And T same as TD?
@hans; It doesn’t switch on at all. After some time, after keeping the power button pressed for some tine (and/or with volume rocker) it switches on. Battery is ok and Windows seems to shut down ok.
I found hardware acceleration also problematic with Opera and Chrome browsers (both 32- and 64 bit). Not strange because Opera uses the same engine as Chrome. Firefox however seems to work ok with hardware acceleration activated.
And I guess Windows has hardware acceleration activated with most other apps (among Windows buildin apps like Edge browser)? So … Chrome-based browser problem?
@S K, I completely removed the driver (to default Windows driver) and ran the Intel update driver. Then choose the non-N version.
In my case it seems like an 64-bit Chrome-browser with its hardware-acceleration activated. I have Chrome start in the background (because of the hangouts-app) so also random black-screens working with other apps.
So far, If I turn off hardware-acceleration or use the 32-bit Chrome, no more black screens (fingers crossed).
Ok… How about a second partition then?
Making the Windows partition smaller, create an extra partition and somehow make it available to Android?
Thank you for your reply @brianvision 😉 But I do switch OS a lot so I don’t want to skip this menu 🙁
Was wondering which card-types have the least problems on a type-c model; SD-HC or SD-XC? UHS-I, UHS-II or non-UHS (regular 10-mark?)?
Maybe the Init.d scripts are also executed at boot but too early (before link2sd starts doing its part)?
Absolutly true guys 😉 Will Kingroot do the job?
-
AuthorPosts

