Related
Dear all,
The original design of ASUS Eee Pad Transformer keyboard dock was intended to provide the most user-friendly usage experience, where the keyboard would quickly wake the tablet on a single key press. However, this requires the keyboard to remain in an ever-ready standby state. While this feature was initially well received, we have since monitored feedback requesting an even longer battery life, considering the substantial battery capacity when the Eee Pad is docked.
Subsequently our engineering team has fulfilled this request by providing an additional, optional battery saving mode. This turns off the ever-ready standby state, enabling the keyboard dock battery life to last longer. However, the trade-off is that the keyboard dock now requires a press of the power button on the Transformer Pad to wake it instead. Eee Pad users now have the freedom to choose between longer battery standby (battery saving mode) or ever-ready keyboard wake-up at any time, from the settings menu. We have already implemented this free update for the Eee Pad, and it is ready to use today.
At this point of time, most of the keyboard docks that have been sold and everything in stores today supports this new battery saving option, except those of very early shipments. While the addition of this mode may not be critical to most users, we realized some owners of the earlier units may still desire this additional feature. Despite our best efforts, unfortunately this function is not upgradable on a limited number of keyboard docks and it requires an ASUS engineer to update the device. For those customers that require this optional function, ASUS will arrange an update. Please contact local ASUS service center to make the arrangement.
The following is a step-by-step guide on how to verify if your unit can support the new optional battery saving mode:
(1) Make sure your software is updated to 8.2.3.13 or later; and your mobile dock is updated to 0209.
*([Setting]>[About Tablet]>[Build Number] & [Mobile Dock version])
(2) Dock the Pad into the keyboard dock.
(3) Go to [Settings] > [Screen] and select [MobileDock Battery saving mode]
(4) Press power button on the Transformer Pad to make the unit go to sleep.
(5) With the option checked, if your unit does NOT wake up with the tap of a keyboard, the new battery saving mode is enabled and working.
(6) With [MobileDock Battery saving mode] checked,if your unit still wakes up by a key press, you have the earlier design.
(7) If #6 is true and you also require the new feature, then please contact your local ASUS service center.
best regards,
ASUS
Interesting. I did notice that with my new dock, it doesnt wake up. My first dock did, and the battery drained very quickly
I will assume pressing Power on TF to make it sleep should be instantaneous (no wait time).
I just tested mine and, sure enough, with the Sceen option selected, it does wake.
Appreciate this explanation. I'll take the dock to ASUS support.
And big Thanks for all the great Honeycomb support. Looking forward to 3.2.
Sent from my Transformer TF101 using XDA Premium App
Asus_USA said:
Dear all,
The original design of ASUS Eee Pad Transformer keyboard dock was intended to provide the most user-friendly usage experience, where the keyboard would quickly wake the tablet on a single key press. However, this requires the keyboard to remain in an ever-ready standby state. While this feature was initially well received, we have since monitored feedback requesting an even longer battery life, considering the substantial battery capacity when the Eee Pad is docked.
Subsequently our engineering team has fulfilled this request by providing an additional, optional battery saving mode. This turns off the ever-ready standby state, enabling the keyboard dock battery life to last longer. However, the trade-off is that the keyboard dock now requires a press of the power button on the Transformer Pad to wake it instead. Eee Pad users now have the freedom to choose between longer battery standby (battery saving mode) or ever-ready keyboard wake-up at any time, from the settings menu. We have already implemented this free update for the Eee Pad, and it is ready to use today.
At this point of time, most of the keyboard docks that have been sold and everything in stores today supports this new battery saving option, except those of very early shipments. While the addition of this mode may not be critical to most users, we realized some owners of the earlier units may still desire this additional feature. Despite our best efforts, unfortunately this function is not upgradable on a limited number of keyboard docks and it requires an ASUS engineer to update the device. For those customers that require this optional function, ASUS will arrange an update. Please contact local ASUS service center to make the arrangement.
The following is a step-by-step guide on how to verify if your unit can support the new optional battery saving mode:
(1) Make sure your software is updated to 8.2.3.13 or later; and your mobile dock is updated to 0209.
*([Setting]>[About Tablet]>[Build Number] & [Mobile Dock version])
(2) Dock the Pad into the keyboard dock.
(3) Go to [Settings] > [Screen] and select [MobileDock Battery saving mode]
(4) Press power button on the Transformer Pad to make the unit go to sleep.
(5) With the option checked, if your unit does NOT wake up with the tap of a keyboard, the new battery saving mode is enabled and working.
(6) With [MobileDock Battery saving mode] checked,if your unit still wakes up by a key press, you have the earlier design.
(7) If #6 is true and you also require the new feature, then please contact your local ASUS service center.
best regards,
ASUS
Click to expand...
Click to collapse
Thank you very much for the detailed explaination and commitment to resolving this issue. Great to see you guys are here and monitoring our forum...
Now, about the LIGHT BLEEDING...???
Got my RMA after running the required steps. Painless, but will be painful to be without my tablet for however long it takes. I've grown accustom to using it so much. Thanks for being in contact with us here. I know for me at least it means a lot knowing that you listen to our inquiries. I second the light bleed too! Wonder if I can add that to my RMA?
Does Asus have sufficient quantities of all the parts required for the fix on hand?
I have read a few posts where people have RMA'd for this issue only to be told their repair is on hold due to "waiting for parts".
Does anyone who has submitted an RMA have a copy of the RMA_COMPONENTS_CHECKLIST.pdf? For some reason I can't get it to download from the e-mail sent to me. Says file is corrupted. Greatly appreciated in advance
Hi Asus_USA, and thank you for your post.
Would the local ASUS (France for instance) know about this and do what is necessary to exchange the product ?
is this a "dock only" rma? I could probably live without the dock for a while but I'd rather not have to surrender my tablet.
ryan stewart said:
is this a "dock only" rma? I could probably live without the dock for a while but I'd rather not have to surrender my tablet.
Click to expand...
Click to collapse
Just RMA'd mine and it's a Tablet only RMA. I figured I'd list my other discrepencies along with this when I sent it in. We'll see my luck compared to others
danr238 said:
Just RMA'd mine and it's a Tablet only RMA. I figured I'd list my other discrepencies along with this when I sent it in. We'll see my luck compared to others
Click to expand...
Click to collapse
Am I reading this right? The problem is with the TF and not the dock? Hmmmmm....
OP can you read this and edit your original posting.
Thank you.
PS: There is a NSFW version in that thread. LOL
I'm concerned that this has been posted by a new single-post user, rather than one of the existing, known Asus accounts, and the fact that the same information hasn't been provided anywhere that I can see on the official Asus site, nor on their Facebook page.
Hence, I've posted on Facebook asking for confirmation that this is really an Asus employee and procedure, and if so, asking for clarification as to whether it is only the dock that need be returned, or the tablet too.
http://www.facebook.com/ASUS/posts/252930108053047
For reference, my dock does *not* pass this test, and mine is a B5O unit, so if this test is real, then only B6O units are able to pass the test.
For what it's worth I spoke with tech support and they had me reproduce the steps identical to those of the OP and also said that my tablet needed to update to support this feature. I implicity asked if this was a problem with the tablet or the dock and the support guy insisted it being the tablet. I realize that he is just reading off the screen as to what to say, but this is enough verification for me to believe that it's the tablet. I guess the complete truth will be told when I receive it back from ASUS. Again though I ask if anyone has RMA'd can you provide me with a copy of the checklist pdf so I don't have to sit on hold to have them resend it to me. And just a heads up its B5OK.....not B50K. I didn't realize this until I went to register my device on their website.
For reference, my dock does *not* pass this test, and mine is a B5O unit, so if this test is real, then only B6O units are able to pass the test.
Click to expand...
Click to collapse
That's not true, my B50 dock passes the test. Some B50 units fail, and some pass. I think that's why they don't just say, check if it's a B50 unit and send it in.
AustinMartin said:
That's not true, my B50 dock passes the test. Some B50 units fail, and some pass. I think that's why they don't just say, check if it's a B50 unit and send it in.
Click to expand...
Click to collapse
Yes, but what version is your Tablet? I think the problem is with the Tablets, not with the actual dock. I have a b50 dock and have the screen wake. However, my tablet is a b40.
dictionary said:
Yes, but what version is your Tablet? I think the problem is with the Tablets, not with the actual dock. I have a b50 dock and have the screen wake. However, my tablet is a b40.
Click to expand...
Click to collapse
Interesting and a bit disheartening -- I really don't want to be without my tablet for a period of ... who knows how long ... given that it's apparently a manufacturer design issue, and not a hardware failure.
For reference, my tablet's also a B5O, the 32GB version. My wife also has a tablet which I guess we'll also need to be returned, although we're still waiting for her dock to be delivered. I think hers is a B4O if memory serves, but it's not in front of me right now.
More frustratingly, I bought a third 16GB Eee Pad and dock for my father, who lives in the United Kingdom, as his Christmas present (he's holding it until then, charging and discharging the battery occasionally to keep it healthy). So I guess we're going to need to get into figuring out how Asus' international warranty works, too...
My Tablet's a B5O, but I would be very surprised if it's a tablet issue.
I have started this poll quite some time ago, http://forum.xda-developers.com/showthread.php?t=1155151, but cannot figure out a way to make it sticky!
My B50 tablet and B50 dock passed the test.
This is how I test it:
Check the option, then press power button. Scren turns off and pressing keyboard keys shouldn't turn it on.
Uncheck the option, then press power button. Screen will turn on if I press the keyboard.
Btw, I don't have battery drainage issue.
Sent from my Transformer TF101 using Tapatalk
Hey gang. Wondering if you can help me with a strange issue I've got. I can't seem to connect my phone to my computer via USB. Wondering if anyone could help determine if there's a possibility of repair or not.
==Possibly relevant info==
Samsung Vibrant
Android 2.2 Froyo
Kernel version: 2.6.32.9
Build number: FROYO.UVKB5
==End relevant info==
So, my USB is acting up. Has been for the last few months, where although it charges when I plug into a computer, it's not connecting to allow data transfer. I haven't been too terribly worried, this happened before then cured itself when I did a factory reset. The thing that usually triggered it was when I tried connecting to my linux box in media player mode. The phone would just kinda lock up, I'd have to restart it and then USB wouldn't connect. But after doing the factory reset it was fine the first time. THIS time however, since I'd just left it stock now I'm itching to flash a custom rom but even though I've wiped the whole stupid phone totally clean, it still won't connect. I'm trying to follow a method on an article on dkszone.net called "Bypass E - Signature Verification Fail Issue On Vibrant Android 2.2".
So it seems I need USB for the debug mode.
What I think my main problem is, and where I need some help, is that I had purchased a super cheapwad USB car charger off of amazon for like 35 cents. Every time I connected to it, my phone would ask me if I wanted to connect using kies, media player mode, or data storage mode. I thought it was annoying but didn't really think it would harm anything. But now that I'm thinking about it, it's probably been pumping 5v into each pin on the USB port, whereas the USB functionality uses probably 3.3v, and I'm afraid I cooked something.
The random part here though is that about 5% of the time it does (sortof) connect. It brings up the USB options when I want to connect, brings up the icon saying it's using debug mode, etc. But my machine just reports that it didn't recognize the USB device. So, I'm thinking it's on the fritz, but figured I'd check here to see if I could possibly find a ray of hope.
Scooterx3 said:
So it seems I need USB for the debug mode.
Click to expand...
Click to collapse
You can use ADB over tcpip. There's many a free widget to enable it on google play or Do it manually
Thanks for that, I had been wondering if there wasn't a way to do that over wifi. My issue is that sadly I haven't even rooted the phone. ADB over WiFi requires root, whether I do it manually or use one of those super sweet apps.
So anyways, guess what?
My brother in law has the same phone I do, and I grabbed his phone one day and plugged it into my computers and had the same problem as with my own, and I know he hadn't plugged into the same charger I had, hadn't tried the media mode on Linux like I had (which were what I thought were the big contributing factors). SO, I kept digging, found that I hadn't quite yet cleaned it properly. I'd tried my best to clean it but until I swabbed it well with some rubbing alcohol it wasn't as clean as it should've been.
Long story short, I'm backing everything up so I can start flashing roms.
Moral: just clean the dang thing really well
Ok I dug around looking for a way to enable usb charging on the tab 2 the "force usb charging" option is not in the stock file structure, was a custom kernel used in the first version of the tab to acheive this .... was going to post the url but because im new i cant, on a side rant i find this feature very annoying, how can you as a person ask good questions and give valid examples without being able to link and show my point, anyway aside from that is their a way to modify the kernel ICS 4.0.3 in the tab 2 to enable the charging via usb
Additionally i user a terminial emulator and actually looked before i asked about this no joy, looks like Samsung once again got wise to this and took away the option
Wildcat2083 said:
Ok I dug around looking for a way to enable usb charging on the tab 2 the "force usb charging" option is not in the stock file structure, was a custom kernel used in the first version of the tab to acheive this .... was going to post the url but because im new i cant, on a side rant i find this feature very annoying, how can you as a person ask good questions and give valid examples without being able to link and show my point, anyway aside from that is their a way to modify the kernel ICS 4.0.3 in the tab 2 to enable the charging via usb
Additionally i user a terminial emulator and actually looked before i asked about this no joy, looks like Samsung once again got wise to this and took away the option
Click to expand...
Click to collapse
As far as I know, no stock device enables you to charge at the full AC rate via a computer USB port. The "charge only" options are usually just to prevent the device from mounting in any way on the computer (disk, modem, media device, etc.). Also, I'm assuming that you want a "fast charge" mod. As for USB charging, even on the stock firmware (and CM9), the tablet doesn't show that it is charging when plugged in to my computer, but it does charge, albeit very, very slowly.
As for not being able to post links, that is to prevent link spam. Ever see forum bots that just join, make spam posts and link to phishing, scam, and other not so great sites? There is no way to guarantee that you're a genuine user, so there are no links allowed until you reach a certain post quantity to verify you're a legit user. Odds are, spam accounts will be caught before they reach this preset limit to post links.
I have the P5113 usa model and stock firm, and i think that when it plug to PC the tablet don't charge, but it use the power of usb instead discharge the battery because the % of the battery don't change when i use it.
i've got a 10.1 P5113 and the only way I've been able to charge via USB is being on CM9. the tab says it is charging when i plug it in to my computer.
gregorovitch said:
i've got a 10.1 P5113 and the only way I've been able to charge via USB is being on CM9. the tab says it is charging when i plug it in to my computer.
Click to expand...
Click to collapse
Ok thx for the quick replies, i assumed a custom ROM was needed ...
I have a TF101 that's seemingly dead after being dropped. Currently, it does not power on. When plugged in with the ac charger, it shows no sign of charging, i.e., no light of any kind - amber, green or otherwise. I assume the mainboard has gone south.
When I connect it to my laptop, however, Windows 7 gives a chime and recognizes it as an MTP device, and even lists it as a TF101 in device manager. Linux also acknowledges that much. I can pretty much browse and access the content of the internal SD card like an external HD. Holding the power button long enough will unmount the device in either OS, which suggests that the device has turned itself off, and thus still responding to physical commands, or functioning on some level.
So it appears dead but not really. Being totally unfamiliar with this model, I'm not sure what possibilities the current state of affairs might indicate insofar as the device's vitality. Any input as to what this means is greatly appreciated.
If is it determined that the mainboard is done for, can anyone point me to a source for a replacement? If this kind of info solicitation is proscribed by regulation, my apology. Thank you.
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Lethe6 said:
My guess is, if the board was dead, you wouldn't be able to mount the device at all. It would suggest that it's actually alive and well, but the graphic/monitor part is dead, so you have no display at all. Mine also shows no signs of life (assuming I don't check the display) while it's charging and not on the dock. Only the dock has charging status lights as far as I can tell.
Sadly I can't help you further than that. I know they sell replacement parts on ebay and such, but I never even opened mine up, so I have no idea how easy it would be to replace any part. I know there's repair videos on youtube for the tf101, it might give you a clue if you open it up and run some tests.
Also check this out.
Click to expand...
Click to collapse
On second thought, I'm not too keen on replacing the MB just yet. Cracking the thing open is no big deal. I am dexterous enough. However, I am more intrigued by what is possibly going on.
If you guessed right, and transferring PC knowledge to this, the board would have a video chip integrated, with the other part consisting of an inverter and the LCD. If the integrated video circuit is dead, then connecting the device via HDMI to a TV would show nothing. If the device shows up, for instance, it's just the display part from the inverter on and so forth.
But I'm hesitant to go down that route. If it's the video part, then I should be able to do everything else like putting it in APX Mode, or flashing as with a normal device. Unfortunately, my computer never registered such activities; the tablet does not respond beyond the symptoms I described above.
As a matter of fact, I'd entertain any mad proposal on what should be tried on the thing at this point, just for the fun of it. I stand to lose little. So you can use your imagination and shoot some crazy ideas my way, and we'll see what.
So you tried with HDMI and it didn't work? You're right about APX though unless you're missing the drivers.. so maybe there really is some damage to the board. Sadly I don't have any crazy/mad suggestions at this point
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Mike_NZ said:
My normal approach to possums (and the only legal thing I can do with them once captured) is to kill them or get someone else to kill them for me. :good:
As for your TF101, I seem to remember reading on another forum that when these devices are dropped and show the symptoms you describe, it can be caused by a ribbon cable that connects the display to the motherboard being jolted loose. It might be worth opening it up and check both ends of the appropriate cable for secure fit.
Click to expand...
Click to collapse
Hey I totally agree that killing it may be the only option right now. And I don't mind that, just that I'd prefer the scalpel to the cleaver, and doing it in such a way that I would learn something about it that may be of benefit to me and incidentally, to others. I did open the thing, and you're again right, people have run into this problem of the LCD cable being jarred loose on impact from Asia to the Western Hemisphere to Eastern Europe. But it's not that, as I did unseat and reseat the cable on both ends, for naught.
As to the APX drivers, I did try both Easy Flasher and PERI 0.4. They act as if they finish the job. However, the tablet remains consistently inert. Lethe6, am I missing something here? How do you tell if the APX drivers are missing? Normally Windows would show the USB device as in APX mode right? Mine did not do that. When I tried to update the driver in Device Manager, Windows refused to do it claiming it was not necessary. Is there a way to force-install the drivers just to see?
Oh well, I'd just let the issue hang at this point and see what else comes this way.
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Lethe6 said:
Yeah if you connect your device in APX mode it should pop up in the device manager, just right-click uninstall then re-install the drivers. I don't remember what's the exact device name but iirc it's something generic. Sorry I can't check I'm on a Mac at work and my TF101 is at home.
What about HDMI? Did you ever get a signal through there? Tried having it connected when assuming to do a full boot?
Click to expand...
Click to collapse
I never had the chance to try the HDMI output. Still waiting for the adapter to arrive. Ebay can be a pain during holiday season. But I'd sure to report the result. When I plugged the thing in, Win recognized it as an MTP device and proceeded to install drivers automatically. After which it showed in Device Manager as TF-101. So apparently the drivers are correct, though they dated back to 2006!!?? However, with other devices like the Acer A500, the USB device symbol normally would appear at the right bottom bar with the designation "APX device." With this thing, nothing - not even the icon. What's your thought on this?
I don't have any other devices that I can boot into APX (HTC won't tell anyone and my other tablet is a craplet, have to ADB on the live FS, which is awesome lol) so I can't compare here, but have you tried these drivers for APX? It's been a while but I seem to remember needing special drivers for APX. The device had a weird name.. like a bunch of numbers and letters... haven't used it since easyflasher though.
When I plug it in APX the device is called "NVIDIA USB Boot-recovery driver for mobile devices" and it's dated 1/31/2011.
When I plug it in Rogue Recovery the device is called "Asus Android MTP Device" dated 7/17/2012.
When I plug it in booted to 4.0.3 the device is called "Transformer TF101" dated 7/17/2012.
So I'm guessing yours never enters APX or has the wrong drivers? Maybe try installing the ASUS Sync software? Not sure but it may bring newer drivers...
I assume you're doing all this undocked as well?
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?