Database Users

[Q] Keyboard Dock Issue

I have done a search of the forum and only came up with bits and pieces of what I need to know, so here goes....
I bought a keyboard dock the other day (separate from the tablet) and brought it home, upon initial connection nothing popped up and my tablet didn't read that it was even there. I thought it may be a software issues since the dock charged fine when it was by itself, AND when the dock is connected to the tablet and I plug the supplied usb cable into my computer it actually reads the internal memory from my tablet. Anyways, I called ASUS tech support and after 1.5 hours of my life i will never get back I am back to square one.
A little info about my software version... I am running the 8.x.3.09 version from ASUS' website, originally it was 8.x.3.6 until I updated it to get the dock working. Now here is my real question, when the dock is NOT attached my "MobileDock Version" appears as "Not Available"...is that normal? Should the software version always show up? It does not change even when I plug the dock in, it still says "Not Available". Is there a way to flash the firmware update for the dock manually? I have read there is a "fu" file that is the dock firmware but where abouts do I get it?
RMA'ing is not really an option since ASUS want me to send both the tablet AND the dock...even though they are separate purchases, and returning either is out of the question when there are 300+ people waiting in line to get one at NCIX (don't really want to end up at the back of the line). Any help would be greatly appreciated.

I've got the exact same issue.
The USB ports, SD card slot and charging connector all work fine. It's the keyboard and trackpad that don't work.
I can even plug in a USB keyboard and mouse into the dock usb ports and they are recognised.
I've tried various different updates and I'm starting to think about rooting the device to help figure out why the keyboard isn't mounting.

First, when you dock your dock, make sure it's seated all the way. The switch on the dock should be completely to the right when docked, and completely to the left when undocked.
Whenever and everytime you dock, a black screen with a message should come up "Asus Keyboard is not selected, Change to ASUS Keyboard to keep consistency with Hardware Keyboard. Press OK"
The Mobile Dock version should ONLY be displayed when docked, and will display 'not available' when you're not docked. I believe the latest dock firmware (for the US) is EP101-0209. If yours isn't, update it.
Also, download https://market.android.com/details?id=org.flexlabs.widgets.dualbattery&feature=search_result from the market, it'll display both your tab/dock battery life status. It's a widget. After you download it, hardclick on your homescreen and select the widget and dragit onto the homescreen

Tjwoo said:
I believe the latest dock firmware (for the US) is EP101-0209. If yours isn't, update it.
Click to expand...
Click to collapse
I've been searching for a place to download this update so we can force-update the dock. Do you know anywhere to get it for manual installation?

Nook Simple Touch freezes completely

Hey
I've begun having problems with my rooted Nook a while ago - it was just freezing at random moments, sometimes unable even to be restarted.
Today I finally decided to perform a factory reset, hoping it would help. Unfortunately, it still happens - at first I wasn't even able to go through the registration process, as it freezed on a wifi page or on a login page. Now I've passed it and am on a home screen, but looks like the factory reset hasn't fixed my problem.. Any ideas what I should do?
I don't have any backups.
From what I've noticed the Nook usually gets back to life when I plug it in, so it might be a battery issue. The problem is, I can't my warranty to replace it, because I left it at home on the other side of the world, where I won't be back until january.. so I'm looking for something I can do on my own.

You only need your serial number to trigger a warranty replacement, as far as I know.
You will need to call BN and be ready to be on hold a long while, but they ought to be able to help you out.

roustabout said:
You only need your serial number to trigger a warranty replacement, as far as I know.
{/QUOTE]
That's a good thing then. And who covers the cost of shipping to US?
I've contacted their CS by email but seems like I'm getting answers not related to my problem..
Click to expand...
Click to collapse

They ship the unit to you, and I think they box is prepaid for the return shipment.
You will need to do this over the phone, as far as I know -- their CS is weak to start with, and I'd be very surprised if you were able to get a warranty replacment moving as a result of an email conversation.

roustabout said:
They ship the unit to you, and I think they box is prepaid for the return shipment.
You will need to do this over the phone, as far as I know -- their CS is weak to start with, and I'd be very surprised if you were able to get a warranty replacment moving as a result of an email conversation.
Click to expand...
Click to collapse
Just called them and looks like I need an american credit card or to go to USA, both being impossible for me (and probably they can send a new nook only to US either). So I'm looking for any other options, don't care about my warranty.

I think that I'd do some sleuthing and figure out if it is the battery.
Use any of the utilities to look at battery voltage and not "percentage".
If the battery is dead I'd try replacing it with a generic 3.7V Li ion battery.
The temperature sensor could be replaced with a fixed resistor if required.

There are some folks who have found that opening the device, disconnecting the battery, then doing something that reads like discharging a capacitor - there is sometimes a problem with the battery, where it is fully charged but the OS thinks it is fully discharged.
Here is a post that describes a fix which might apply for the OP:
http://forum.xda-developers.com/showthread.php?t=1813384

Simple Fix for Freezing Nook Simple Touch
I am going to post this here and on the xda thread referenced above. This may not work for everyone but it worked for me. And it is a simple fix that does not involve taking the NST apart.
Run the Battery Calibration v 1.2 app per the instructions on its opening screen (start app, charge to 100%, touch button in app.) App can be run while nook plugged in.
I found it here
https://battery-calibration.en.uptodown.com/android/download
But note that it is found here also (some of the mirror links still work)
https://forum.xda-developers.com/showthread.php?t=1033529
The Nook Simple Touch runs a modified version of the Eclair version of Android. Finding Eclair compatible apps is becoming increasingly difficult. So finding a battery calibration app that actually works is golden.
MY SYMPTOMS
Nook Simple Touch froze. Battery showed mid 70% range when plugged in to charge. After recharge everything was fine until it got back into the mid 70's again.
Then it started freezing in the 80% range.
I finally decided I needed to do something when it started freezing in the 90's.
I had even ordered a new battery (which will likely fix this issue also.) But decided to try this super simple fix first.

Need Help with APX Mode Brick.

Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app

I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app

I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986

You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!

I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.

ZenWatch Always-On screen option doesn't work

My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.

Is cinema mode on?

annik1s said:
Is cinema mode on?
Click to expand...
Click to collapse
Thanks, no, cinema mode isn't on.
It's really curious, the screen fades slightly in brightness after five seconds, then goes to the dim version of the watch face, then goes completely black a second later. One tap brings it back so I'm it's like the regular off screen mode.

TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.

Chewie01 said:
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.
Click to expand...
Click to collapse
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.

TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Just got my Zenwatch and I am having the same problem... Resetting the watch helped. But, I am still not getting the watch to vibrate on notifications. It vibrates when I set an alarm (on the watch) to it's not the vibrating device itself...

TheGreatWaldopepper said:
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.
Click to expand...
Click to collapse
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.

Chewie01 said:
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.
Click to expand...
Click to collapse
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.

TheGreatWaldopepper said:
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.
Click to expand...
Click to collapse
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.

Chewie01 said:
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.
Click to expand...
Click to collapse
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.

TheGreatWaldopepper said:
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.
Click to expand...
Click to collapse
Well the good news is I now have the replacement watch and it works as advertised. I did have to complain a lot to get the difference in price resolved. I ended up complaining so much that the store manager gave me the money out of his own pocket just to get rid of me .

NuVision - TMAX ( TM800W560L / TM800W610L ) Information

I wanted to start a thread to solve some minor headaches regarding NuVision tablets. Specifically the TM800W560L, but may include others.
The manufacture is TMAX, and the brand is NuVision. Some of you have these. I picked up the 560 at the Microsoft store, a couple of days before Christmas, 2016. I ghosted the factory image as backup, and wiped clean to start from scratch, using Windows 10 Pro.
Let's say my hack started at the Microsoft Store, social engineering a sale of $25 for the unit. Yes you can get these for free, if you were buying a Windows Surface, but why would you want this if you have a Surface? It's such a terrible device to support for the sod who got one...
This unit is the most similar to the HP Stream 7, MSRP $79. I have a couple of these as well. I a bit miffed that, although the CPU is 64-bit, we can only use 32-bit Windows. This produces some problems as only 64-bit drivers are readily supported via Windows Update. I have made use of some of these drivers for the 560 to solve some problems.
Lets get down to the issues at hand:
1. The Camera drivers.
OV2680 ( OVTi2680 Ven_OVTi&Dev_2680 )
OV5648 ( INT5648 Ven_INT&Dev_5648 )
Problem: For every Windows Feature Upgrade, the drivers are wiped out and replaced with some non-functional version. Frankly, I don't think I have been able to get the cameras to work at all. At least, not by using the Windows 10 Camera App. I pulled a litany of drivers from various sources and I can get them to at least seem okay, as far as the device manager is concerned, but not much beyond that.
2. Intel Chip Set drivers.
Problem: Much like the camera drivers, for every Windows Feature Upgrade, the chipset drivers are updated as well, but then the supplied drivers are non-functional. This results in the lost of touch and gravity sensors, among other functions. This requires the use of a USB OTG adaptor, (Yes you can have USB and power at the same time!) and reinstallation of the original chipset drivers.
All in all I get the sense this is abandoned technology, and I feel that no-one particularly cares. In addition, I am a little bored with this thing, and I would like to see if I can make it better.
If anyone has questions or advice, I am open minded, but it should be sincere.
Thanks,

I picked the TM800W610L. I will see if the camera drivers and chipset drivers from this model will work for the 560. However NuVision has reduced their driver set to bare bones. In some respects this is admirable, but in my case, it leaves little hope that there's any 32bit support.
For the uninitiated, the 560, although has a 64bit CPU, the BIOS only boots 32bit Windows. This is the same situation on the same CPU, for the HP Stream 7, which I am also leveraging for support.

I have been able to dig around a little bit, regarding the BIOS firmware, for both models. Geekbench is a nice repository of data, for a shallow dive.
This is what I have, for known BIOS revisions:
I have the installer for version H, supporting the 610.
I can backup version R, installed on my 560.
If anyone is interested in an "update" from an older version, it would be interesting to get a backup of what you currently have in exchange for an update.
TMAX TM800W610L
JK-BI-8-HLK80CR100-C34A-101-F-LCD3 08/01/2016
JK-BI-8-HLK80CR100-C34A-101-H-LCD2 ‎03/02/‎2017
TMAX TM800W560L
JK-8-BI-PX5S10TCR100-X534A-001-G
JK-8-BI-PX5S10TCR100-X534A-001-H
JK-8-BI-PX5S10TCR100-X534A-001-L
JK-8-BI-PX5S10TCR100-X534A-001-O
JK-8-BI-PX5S10TCR100-X534A-001-P
JK-8-BI-PX5S10TCR100-X534A-001-Q
JK-8-BI-PX5S10TCR100-X534A-001-R 08/25/2016
JK-8-BI-PX5S10TCR100-X534A-001-T

I just picked one of these up myself (the TM800W560L) and am working on getting it upgraded to Pro (and put on the Insider preview program, because I like my devices consistent) at the moment. I was a little sad to see that these machines have 32-bit UEFI effectively making the 64-bit enhancements useless and limiting software support to 32-bit only (that immediately threw out my plans for using WSL/Ubuntu on the thing since Windows Subsystem for Linux is a 64-bit only feature), but after a couple hours with this tablet, I'm really enjoying it. It took about 4 hours to install the latest batch of updates, but unlike your own experiences, all my drivers still worked after the upgrade from 1511 to 1709 (Build 16299).
I did see some very negative reviews for the product on Amazon, mostly about customer support, so I knew what I was getting into when I ordered it.
EDIT: My gripes about the device were apparently for a defective device. Got a new one after the note below caused a brick and have had a much better time with it.
Important! For my first real contribution to this thread, I wanted to give a warning, don't mess with the BIOS options if you can help it on these devices. I simply changed the "Boot to State when Power is resumed" from G0 to S5 and the tablet no longer powers on. It's charging, but nothing is happening from the buttons. So I guess it's to the exchange with this one.. Learned for the next one though :/ [Update: Turns out that it caused an actual brick, lesson learned, don't mess with the Power Management firmware settings! There's no good way back from a brick caused by UEFI firmware settings, you apparently have to reflash the BIOS using an SPI programmer to fix those. These manufacturers really should be designing their firmware better (and not using 64-bit firmware on a 64-bit processor, shame on them for that travesty!)]
Edit 2: I ran into an actual issue that I can reproduce pretty frequently. With the native Windows auto-rotation on, going from Landscape to Portrait (or vice-versa) leaves the touchscreen in this weird state where it's still looking for touch input from the previous orientation. Not sure if this is a Windows 10 version 1709 build 17043+ bug, but it appears to be, as the issue does not happen if I turn rotation lock on and manually change orientation. It's an interesting issue to say the least. [It appears after browsing the feedback hub that this is indeed a Windows 10 Insider bug, if you are affected by this, turn off auto-rotation and then manually rotate the screen using Settings, the touch input works as expected then.]

Hi, thanks for the great info! I'm trying to start a little robot makerspace and wanted to mount these little cheap tablets on mobile robots. The only issue appears to be not being able to use USB devices while supplying external power to the device. It sounded like you mentioned this is somehow possible, could you elaborate on that?
Thanks!
Jesse

ShadowEO said:
Edit 2: I ran into an actual issue that I can reproduce pretty frequently. With the native Windows auto-rotation on, going from Landscape to Portrait (or vice-versa) leaves the touchscreen in this weird state where it's still looking for touch input from the previous orientation. Not sure if this is a Windows 10 version 1709 build 17043+ bug, but it appears to be, as the issue does not happen if I turn rotation lock on and manually change orientation. It's an interesting issue to say the least. [It appears after browsing the feedback hub that this is indeed a Windows 10 Insider bug, if you are affected by this, turn off auto-rotation and then manually rotate the screen using Settings, the touch input works as expected then.]
Click to expand...
Click to collapse
I can confirm the strange rotation behavior, on the 610L. I got out of it by hooking up an OTG cable, keyboard and mouse.
Boot up and log in, rotate to landscape and reboot, not messing with the touch screen. After the reboot, the touch screen worked in landscape, and seems to be in sync again.
I installed 17083, that was a chore, and all seems well. However I am getting app crashes, which I think is an OS issue. (currency ran sfc /scannow - no probs. And dism /online /cleanup-image /startcomponentcleanup /resetbase) Next is to run chkdsk and reboot... I have no real hope this will take care of things until the next fast build, which could be in a week or two at the moment.
To get the recent build installed, I had to run a custom script, to clean up all the known temp and softwaredistribution/downloads folder. Additionally I removed the upgrade assistant and one drive. Then ran the Windows Update trouble shooter, and ran (compact /compactos:alwasy) and set NTFS compression on the C drive, ignoring all errors. I was able to get 16GB free, and finally able to install the latest Fast Insider's Build.
Some of these things are not recommended, however extreme conditions require extreme measures... 32GB MMC Crive is a bit restricted.

jjurban55 said:
Hi, thanks for the great info! I'm trying to start a little robot makerspace and wanted to mount these little cheap tablets on mobile robots. The only issue appears to be not being able to use USB devices while supplying external power to the device. It sounded like you mentioned this is somehow possible, could you elaborate on that?
Thanks!
Jesse
Click to expand...
Click to collapse
I am having mixed results here. I plainly am not getting good results with an OTG/HUB combo with three power settings. I am not getting power and USB/date to the micro USB port, as the same time. It's either/or.
610L - Nope, one or the other. I originally thought it was possible, but it's not.
560L - Nope, just confirmed, same result as the 610L - will charge in power+data mode, while completely off.
I have confirmed as well, 17063 build, on both the 610L and the 560L, has this strange screen rotation, mouse, touch screen orientation lock thing. That is, the screens rotate, but the touch alignment does not. The mouse pointer only moves in the same space as if it was prorate mode. Touch is fully prorate mode, while the screen rotates to landscape. Then got the BSOD (green screen)... Rebooting while in landscape mode, (requires a mouse), does fix the issue. Touch alignment comes back with screen rotation. (works on both models)

I see a future problem which I think we will have to address on our own. No help from TMax/NuVision I suspect.
When the microcode is finalized by Intel, we will have to come up with a solution to update the code, to protect against Meltdown and Spectre.
I have doen this before, prior to Compaq merger, on the HP VLi8 and VL400. But I don't know if it's possible to inject new microcode on the TMax firmware/bios update.
As you can see above, I have listed a number of firmware for our tablets, I am hoping we can work with some recent purchasers and see if there's an arrangement, where we could come to trade.

The USB OTG ACA support is weird. There are times it does work and times it does not. I have two USB OTG hubs that support supplying the tablet power while USB OTG is in use. With one hub, this works fine; with the other though, it will either not charge, or it will claim to be charging, but I assume not receiving enough power on the tablet side to charge the tablet enough while it's in use. It does however work, I have used it multiple times already with my 560L.
As for storage space, yes, I recommend running
Code:
compact /compactos:always
after each update. You can also get away with storing your user profile on the MicroSD card (and applications, thus rendering the internal storage an OS only drive)
As for my previous complaint about screen rotation, this disappeared after the upgrade to 17083. It was confirmed to be a problem with the Desktop Window Manager service by Microsoft and even had a fix posted to the Feedback Hub entry for the issue.
@CraveTech It may indeed be possible to modify our firmware, but the risk of doing so may outweigh the benefits. Windows already has user-mode mitigation of Spectre and Meltdown that isn't dependent on the microcode to be installed. We also have to worry about the possibility of bricking the devices without recovery (at least in my case, as I don't have access to an SPI programmer, nor do I feel comfortable cracking this thing open) seeing as a single option change in the BIOS effectively bricked the device.

anyone try to unrar the current image from nuvision for model w610L
test the archive and i get errors.
same with drivers.
tried newest unrar and also older version.
wtf??

ShadowEO said:
The USB OTG ACA support is weird. There are times it does work and times it does not. I have two USB OTG hubs that support supplying the tablet power while USB OTG is in use. With one hub, this works fine; with the other though, it will either not charge, or it will claim to be charging, but I assume not receiving enough power on the tablet side to charge the tablet enough while it's in use. It does however work, I have used it multiple times already with my 560L.
Click to expand...
Click to collapse
What is the model of the one that works for you?
I just got a TM800W610L the other day and have been looking for one that works with this tablet.
Thanks

netstat_EVO said:
What is the model of the one that works for you?
I just got a TM800W610L the other day and have been looking for one that works with this tablet.
Thanks
Click to expand...
Click to collapse
the exact hub I had the best experience on so far (I am still buying and trying hubs) was this one: https://www.amazon.com/gp/product/B00LTHBCNM/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1
It charged when it said it was charging and had no qualms with the other devices. There's a Cerrxian branded 4-port rectangular hub which doesn't seem to work well at all for my devices. Even when the Cerrxian says the system is charging and the system shows it, it still dies. I assume that it just isn't supplying enough power to the VBUS :/

ShadowEO said:
the exact hub I had the best experience on so far (I am still buying and trying hubs) was this one: https://www.amazon.com/gp/product/B00LTHBCNM/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1
It charged when it said it was charging and had no qualms with the other devices. There's a Cerrxian branded 4-port rectangular hub which doesn't seem to work well at all for my devices. Even when the Cerrxian says the system is charging and the system shows it, it still dies. I assume that it just isn't supplying enough power to the VBUS :/
Click to expand...
Click to collapse
Interesting. I had seen that one on Amazon and quickly glossed over it since it had a switch for OTG/Charge, so I assumed it couldn't do both simultaneously. At $7 I'd say it's a cheap enough experiment though. Thanks for the info.

netstat_EVO said:
Interesting. I had seen that one on Amazon and quickly glossed over it since it had a switch for OTG/Charge, so I assumed it couldn't do both simultaneously. At $7 I'd say it's a cheap enough experiment though. Thanks for the info.
Click to expand...
Click to collapse
Ya I was surprised too, but it worked with my Nexus 7 and LG G2 with their ACA enabled kernels. I had to fidget with the switch a little before charging started, but I was able to confirm in Ubuntu Touch on the Nexus 7 that it still saw the USB devices via lsusb. I seem to have lost that exact hub within the past week or so, but I had used it last month to charge the tablet while reinstalling Windows from my flash drive with a keyboard and mouse attached. I can't testify that it actually charged the device since I hadn't been able to see percentages (being in Windows setup and all), but the charging indicator was on, the screen was as bright as Windows normally makes it when charging, and it didn't die while the device was at ~15% battery before starting the installation. The Cerrxian hub couldn't do that and the tablet died while attempting installation, So I assume it was charging the tablet, or at least provided enough power to keep the device's battery stable.
I also just bought another 3-port hub from Acasis, another Chinese company making these cheap devices, but so far, I have yet to get that hub to charge the device either. So it seems that this is a very specific type of configuration inside the adapter, but the device does support OTG+Charge.
That said, Windows itself (at least the desktop versions) does not actually support this feature according to Microsoft's USB driver documentation. That it works at all seems to be a bug in the USB driver, or perhaps the adapters are doing something strange to trick the device into pulling down it's own VBUS and using the external one, possibly independently from the OS (Firmware USB drivers maybe?).

Does anyone have screenshot of the BIOS main menu and the save and exit screen? I'm trying reset to the bios. I was messing MIPI and eDP. I thought eDP was meant for external display port.
lol I fixed it. I gamble on different version of this tablet. I press F3 and Left arrow key for yes and enter. Then I press F4 and Left arrow key for yes to save and restart.

snkchaos said:
Does anyone have screenshot of the BIOS main menu and the save and exit screen? I'm trying reset to the bios. I was messing MIPI and eDP. I thought eDP was meant for external display port.
lol I fixed it. I gamble on different version of this tablet. I press F3 and Left arrow key for yes and enter. Then I press F4 and Left arrow key for yes to save and restart.
Click to expand...
Click to collapse
Glad to see that you fixed it. I would recommend against modifying the firmware settings if you can avoid it, especially any power management settings as changing one of those can completely brick the tablet leaving you unable to even enter the firmware.
EDIT 2/27: I came across my other OTG hubs and have some bad news, it appears that the OTG+Charge works on the 560L, but doesn't on the 610L. Perhaps NuVision changed USB chipset revisions between models?

Just picked up the 610L last week for $66 as a small option to use a program I need mobile. Updated to 1709 after a struggle (why Microsoft, why?).
Ran great for a week and now it’s starting to freeze and BSOD with mainly “Clock Watchdog Timeout”.
Not really getting any indication of why, I know I can run a log dump, but I often can’t get it to stay on log enough. It will even hang and crash when trying to wipe/revert.
Anyone have any suggestions?
Been a long time since I was active around here

update:
Was able to locate the stock ISO files and made a bootable usb. It’s currently restoring back to OEM status.
The installer is another language, but it’s working.
I think I won’t be install updates until I finish this project I have to do.

Another update:
Getting an intel framework and thermal error in the logs, which I notice while the device gets hot while charging and operating. If I let things be without charging it stays cooler.
I’ve only had had one BSOD and it was for System Service Exception but the logs don’t show much.
I let things update overnight with it plugged in and the screen off and it was still operating this morning.
Not sure if this is a driver issue or not. Seems that way.

Been trying to restore this but get an hour into the nuvision software and it times out. Anyone have an idea how to get this back to stock?