[suisse]

I am about to flash from Mirek’s v6.0 to 7.0. Just in case, what brightness app did you use ? Would seem to me it’s a simple permissions thing of some file that maybe was wrong right after flashing and fixed due another app.

So what brightness app did you use ?

[suisse]

Hi Marcos,

I am having an X98 Air 3G. Maybe Kionix sensor is different on your Air 2?

Did you try above link to driver or the sticky post that Chris made under

http://techtablets.com/forum/topic/teclast-x98-air-series-inverted-screen-gsensor-drivers-fix/

Actually, I used only the driver to install and made registry entries by hand. It turned out I had to tweak those, as presumable in may Air 3G the sensor is mounted differently. But that does not relate to driver not reporting properly installed. Maybe try to remove the driver and give the link in Chris’s above sticky post a try (, while I used the other link).

 

suisse

[suisse]

Just in case somebody comes over this one and picks up the rotation issue.

I downloaded newest Kionix driver from kionix. Then made a binary registry ‘Orientation’ entry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ROOT\SENSOR\0000\Device Parameters\kxfusion

For my X98 Air 3G C5J6 I set to hex  01,00,00,01,01,00,02  to have the mounting orientation of Kionix chip properly cared for.

After having figured out (via other forums) and done that I found somebody here in our forum back in August had already that very same solution and even got a full turnkey solution by Kionix directly 😎

(see http://techtablets.com/forum/topic/trouble-with-g-sensor-drivers/)

 

[suisse]

Sorry I meanwhile found in another forum the registry entries to fix that after having updated Kionix driver from Kionix directly. It works since 1h. Just now I found it here solved also already:  Aargh why didn’t I find that before, blind I am …

http://techtablets.com/forum/topic/trouble-with-g-sensor-drivers/

[suisse]

Martynas,

 

thanks. Yeah, think now it is crystal clear. I assume Teclast is only having licenses for a pure Chinese Windows 10 not a mutlilanguage W10.

This is presumable were sellers in Europe come in with grey ideas how to activate English or mutlilangual W10 by means of some KMS fake. Haven’t found kmspico files on the tablet which would be a huge hack after all as it hacks anything ! But I remember having seen Windows defender erasing an OEM8.exe back in November nearly some hours after starting the tablet the first time. I also found Chris here writing when testing an X98 Pro he found that thing, too. I assume it is a KMS faking service, faking a KMS host in the net that’s just mimicked on the local machine. Being deleted by Defender and therefore not in place when the 1511 build rolled-out (which is in effect a new installation), kicked (the only hacked) activation away.

No way, for me to support that kind of grey to black ideas of seller as I want to use that tablet for real work also. Fortunately (for me, only), I found an unused second Window 10 key, I got on top in a special bundle when purchasing another laptop recently. I used that one now to legitimate the W10 on my X98 Air 3G.

Thank you for help in proper understanding what was going on. Really curious if I’ll be getting an answer from geekvida …

Anyway, I am legal now.

 

But I am now having another problem with G sensor. When tilting the tablet in W10 screen is no longer autorotating. Neither a “rotation lock” field is present in the information center popping up from right side, nor do I see in settings-> screen any more a tick mark to check autorotation or not. I can see however Kionix driver being properly installed. Did not touch anything. W10 was just updating automatically to 1511 as I said. And before this did work. Also G-sensor is fully functional in Android (Mirek 5.0 v6). Maybe I should take this to another Topic not to cross subjects …

 

suisse

 

[suisse]

Thanks for your reply.

It had Windows 10 activated from the beginning. I bought it here in Germany at geekvida.de. But maybe you are right that the seller installed and maybe hacked Win10. Contacted them already, but got no answer so far. I remember having seen windows defender complaining about a OEM8.exe or something the like and erasing that one back in November. It states and stated being Windows 10 Home Edition.

So maybe this is the problem now, that the 1511 build is basically a Windows 10 re-install and now that hack is no more around ?

What do you mean by roll back to previous version ? I thought this is no longer possible once on 1511. The pitty is I a have an unused Windows 7 key, but cannot use that on a Windows 10, that already once had been activated I assume to now reactivate it. That would only work starting from new (?). I would even not know how to start from new on this tablet. Is this feasible at all now that once by whatever trick it had been on Windows 10 and activated ?

 

Any ideas or links on what I could look at in addition.

suisse

[suisse]

Not sure, but it might be related to what I wrote in another thread of mine relating to a strange “over-counted power use” item in battery statistics.

Your drop is really heavy on the other hand. What I see, is that once I load to 100% and do nothing is it linearly or if shut off immediately dropping to around 95%. This is nothing astonishing as you need to be aware of the fact the 100% is just fake. No system really loads a Lithium battery to 100%, this would strongly affect its lifetime. But to make customers happy they pretend it was 100%. Since they need to recover to reality once in time, you often see either (fake) linear deloading curves or sudden deloading jumps to the real value it was, while you have done nothing on the system to consume power.

But a deloading with such strong jump you have might be more another, maybe  hardware issue.

[suisse]

update:

I maybe have partially understood that over-counted battery stats thing:

To begin with, I’ve now two times nearly fully loaded after being at around 3% my X98 Air 3G C5J6. Currently that item “Over-counted power use” is gone on battery statistics page !

Still see the linear drop from 100% to around 96% while not doing anything on the tablet, after which it stabilizes on that level for hours. Nothing much to be surprised about. That’s what I explained above. 100% has never been 100% and so the battery stats framework need to virtually let it go down to the real value it had once in time, but told you it were 100%. If you are interested and speak German, read

http://www.giga.de/downloads/firmware/news/warum-die-akku-anzeige-von-smartphones-lugt-und-warum-das-gut-ist/

Second, I seems that “over-counted power-use” is something that comes straight from Android, not just mirek’s ROM (Sorry, was not intending to blame you. I love your ROM on the Air 3G, it’s awesome!). I somehow have not seen it on any other device I own. But it looks like the Android framework for power stats can detect that estimated values are wrong based on power profile tables:

https://source.android.com/devices/tech/power/index.html

I assume this over-counted item states that the sum of estimate sub-mAh values drawn is too high. After all you cannot have consumed more than is your maximum physical battery capacity …

I don’t know why this over-counted item is now not showing up any more, but maybe it is sort of calibrated out now, having two times fully depleted and fully loaded (“fully” in the software and not physical sense…).

Cheers, suisse

 

 

 

 

[suisse]

UPDATE: Shame on me. I am such (an impatient) stupid. Ever teach my daughters, first read then act. Damn would I have seen TecKnight’s mentioning not to install iSOC drivers … Got rid of those, and guess what, now it works !

Mirek’s 5.0 v6 works like a charm.

Still having the dualboot option screen to select either OS. everything is as I wanted.

Since I am a What/Why,/Really ? guy, for curiosity and completeness:

1. BIOS tpad2.05 is this indicating a 2.05 BIOS, whatever this be ?
2. I assume given the Intel SoC we have the Intel Manufacturing tool is the best of all flash tools, or say safest, as it is the only one using the dedicated Intel Download aNd eXecute mode (DNX). DNX might be able to do some dedicated repair. Need to look that DNX up once …
3. I am just remembering that when using heimdall on Linux for flashing my ancient Galaxy Note N7000 to Lollipop 5.1.1 that <waiting for device> message for ever was related to fastboot not running on proper privileges. I am now almost sure I forgot to run Mirek’s bat script on administrator privileges, that might have been the easy reason it stuck at that message. Will never know, as I now went the Intel Mnfct tool path.

Thanks for this forum and hopefully, no one has already prepared to solve my problem. Just writing this down such that others may find it.

Cheers, suisse

 

 

 

[Author]

Posts