Database Users

Archos 101 - USB Dead - affected by Turbomode?

Hey guys,
sadly i have to mention - my external USB port also just died...
After contacting archos they told me to reset the revice completely and reinstall - but it didn't help.
As i dont have a recipe anymore - i can't send it in to fix
Well anyway - I never had problems with the device or the USB - but recently I switched my device to settings->deviceinfo->energy...->turbomode the 1st time.
Beside it's draining battery like hell now even with just being idle (suspended) it crashed 1 day ago - having LCD backlight on but showing a black screen (btw my usb keyboard was plugged in meanwhile and the charging-cable was also plugged in).
Next start the USB port didn't react to anything anymore...
(keyboard-lights just turn on shortly (<1s) on plug in and thats all)
(lsusb shows just the 3 default entries: 2 hsot controlers + touchscreen id)
So i assume its dead...
Anyway - after the shock I tried to figure out what I changed the past days an all I can remeber was the turbomode... did anyone make the same experience perhaps?
Eventualy we can figure out the acutal problem of dying USB ports... (if they are not just dieing randomly...)
I searched the internet alot regarding this problem:
Some ppl say its software affected - but i can't really believe since the reset should help obviously... (unless its something deeper in firmware...)
Also the fact that anyone who send in his/her device recieved another device after speaks for some hadware failure...
On the other hand there are 2 host controllers on our archos device (1 for the touchscreen as it seems) and the other 1 for external USB... why is just 1 of em dying all the time?

I had my first unit replaced because the USB was dead after a few months, Board v6; the replacement was a v5 and the USB lived hardly 2 months, the died, too... I did not do anything particular that should have caused this; it really seems it is a weakness in the hardware design; Archos has never admitted that, always suggesting fixes that never worked for anyone and saying, they wouldn't know this is a common problem... I am not the only one having two devices in a row with that problem; I have given up on my USB now and also given up on Archos due to their response on this. Also FW-Updates seem to add more problems than fixes for months now and I downgraded to 2.1.08 recently to get a device that at least works smoothly with whats left... If iPad-owners can live without USB so can I, I suppose... There is always Dropbox, and several tools for filetransfer via WiFi, and the SD-Card-Slot to substitute for a USB-Drive etc. (For my next tablet I might even wait and see, what Windows 8 brings, could become interesting...) Archos as a manufacturer of Tablets has become a no-go for me after this experience. I don't like being lied to, if they made a mistake and admit it, I could trust that the next generation might be better, but like this I would presume to be lied to again so trust in the brand is gone even if they start making it better...

voom said:
I had my first unit replaced because the USB was dead after a few months, Board v6; the replacement was a v5 and the USB lived hardly 2 months, the died, too...
Click to expand...
Click to collapse
Got a v6 too, also replaced by a v5 which lasted at least over a half a year or something. ****ty stuff, srsly

Same here, usb port stopped working after about a year. Not that it mattered - it was useless, only a few usb devices would work correctly. I transfer all my files to the device using the microsd card now. I don't use the tablet very often but I'm very disappointed on Archos. And this isn't my only problem. It was supposed to support HD video playback (even bought the plugins - something which others offer for free) but only a few MKVs will play without stutter.
They won't even bother updating the console with android 2.3!
This is why companies close these days..

@FrEcP - if you registered your device when you 1st got it, and assuming it is still within it's warranty period, you should not need a receipt.
regarding the comments on video playback by other posters - the gen 8 Archos devices have the best video playback support inc HD bar all but the very latest high powered devices, and the plugin is not even required to enable any of the HD formats - it's for mpeg2 (dvd) and AC3 audio only. Providing the files are within the devices specification re resolution and profile, it plays pretty much anything asked of it.

Hi chulri, thx for your root - now that i downgraded to 2.1.08 via SDE anyway, I took the one simple step left to apply your permanent root - and could thus deactivate the daos.apk etc.
As for video, I noticed that 720p HD works perfectly with the Archos-Videoplayer but 1080 plays more like slow motion... 1080 I tried was a MOV or WMV though, not sure, and if I recode stuff for general use I convert anything to 720p MP4 264 with AAC Audio - resulting in up to half the size for similar quality-settings (720 to 720) and of course more significantly smaller going from 1080 to 720. What would be left to try is converting the "slomo"-1080 wmvs to 1080 mp4 264 and see how the 101 handles that... 1080 on the 101 is quite pointless anyway unless playing back via hdmi...

You don't have to try that, as it will not work.
The Archos is using the gpu for videodecoding and that can't handle 1080p/i so softwaredecoding is used.
And for all the people out there that still don't get it, Archos advertises [email protected] with a max of 5Mbs and not [email protected] 5 ( which is used in Animes these days).

fzelle said:
And for all the people out there that still don't get it, Archos advertises [email protected] with a max of 5Mbs and not [email protected] 5 ( which is used in Animes these days).
Click to expand...
Click to collapse
Advertise it where? I see no such thing on the box, in the instructions leaflet nor I've seen anything like that in any of the ads or information in their web site (at least there wasn't when I bought the tablet). The only reason people know of these limitations is because there were people disappointed of the HD capabilities of the device and started asking Archos support questions about it!! Not to mention that "supports the widest range of music and video formats up to 720p HD video" as it mentions on the box couldn't have been any further from the truth since for mkv (ac3) playback you have to pay for the plugins to even get the 3.1 profile support you've mentioned! "Supports a limited range of music and video formats and you have to pay for a few more" would have been truer..
Michael

I fail to see what this has to do with "Archos 101 - USB Dead - affected by Turbomode" which is the title of this thread...

@michpan:
http://www.archos.com/products/ta/archos_70it/specs.html?country=gb&lang=en
Read for yourself

Hi FrEcP!
FrEcP said:
Next start the USB port didn't react to anything anymore...
(keyboard-lights just turn on shortly (<1s) on plug in and thats all)
(lsusb shows just the 3 default entries: 2 hsot controlers + touchscreen id)
So i assume its dead...
Click to expand...
Click to collapse
What does it mean didn't react to anything.... really nothing?
Have you already inspected dmesg output?
May try with USB stick instead of your keyboard.
Some sticks also claim to use more power than others...
You might examine this with lsusb as well, most "tell" the host they will consume 200mA.
FrEcP said:
Anyway - after the shock I tried to figure out what I changed the past days an all I can remeber was the turbomode... did anyone make the same experience perhaps?
Click to expand...
Click to collapse
I don't think there's a side effect with turbomode... though i can't tell for sure.
FrEcP said:
Eventualy we can figure out the acutal problem of dying USB ports... (if they are not just dieing randomly...)
Click to expand...
Click to collapse
From what i found out during hardware investigations is, that there's a DCDC voltage converter that is responsible for the 5V power supply of the type A USB connector. Maybe the converter is to weak for currents above 200mA.
E.g. the kernel hack used on Uruk allows to switch on the USB power for devices claiming up to 500mA (as specified for USB).
There's nothing wrong with this at first sight, but maybe Archos did choose some of the components to weak to deliver this current.
My suspicion is that this converter might die slowly or there's some kind of inrush current while activating a device.
This might kill the chip.
Unfortunately i was not able to identify the manufacturer and model of the chip, i only know the location on the mainboard.
I'm sorry that i can't really help on this issue, but maybe some day there will be light
You might try one thing:
Use a self powered hub and connect it to the Archos, then insert USB device again...
Any difference?
Good luck!
scholbert

I would suspect, that it does not have to do with the power-consumption, since the same hardware that used to work all the time suddenly stops working...
Also, when the USB is dead the port still delivers power, but does not recognize any devices any more. It seems whatever gets broken has more to do with dataflow than with power-supply...

always nice to hear for u scholbert
>What does it mean didn't react to anything.... really nothing?
Well - as i said - the power light light up for about 20ms then noting happens anymore
>Have you already inspected dmesg output?
neither "dmesg" nor "lsusb" show any different output while plug in.
>May try with USB stick instead of your keyboard.
tried a wireless keyborad, a wired keyboard and a usb-stick all just seem to have power for some milliseconds.... then noting else can be noticed.
The only interseting difference i noticed is:
If i have my Keyboard plugged in while startup all lights (capslock,...) light up and STAY ON. Till i pull the plug. Then its like before...
Sadly an USB-Hub (powered) will neiter be recognised... (same bahaviour)
What i noticed - if i resome the device (after is was powered on) there are several wake up commands in dmesg for the screen and the usb hubs...
But it doesnt seem to me that the 2nd hub will get resumed proper... unless those command invoke both of em at once.
What does it tell for u when resuming the device?

voom said:
I would suspect, that it does not have to do with the power-consumption, since the same hardware that used to work all the time suddenly stops working...
Click to expand...
Click to collapse
If it operates at some limit point it might work for while without any problems.
Then it might suddenly stop working...
This is typical for hardware defects (overheat, ESD, other weird things...)
Anyway, i never got these problems, so it's just a kind of "feeling".
voom said:
Also, when the USB is dead the port still delivers power, but does not recognize any devices any more. It seems whatever gets broken has more to do with dataflow than with power-supply...
Click to expand...
Click to collapse
This is new information for me... sounds logic to me.
BTW have you measured the voltage at the port?
It might also be that the device sticks in enumeration at some point.
Let me point out the following thesis:
1. USB device gets plugged into the port
2. OMAP gets an interrupt and is told there's something happening at USB
3. OMAP listens
4. USB device send identifier, power request for full operation.... (enumeration)
5. OMAP gets it, tries to enable power to match requirements and waits for ACK
6. USB device didn't get enough current for operational state and fails
7. ???
There should be something in dmesg though, so just a thesis
FrEcP said:
always nice to hear for u scholbert
Click to expand...
Click to collapse
Thanks, great honour
FrEcP said:
>What does it mean didn't react to anything.... really nothing?
Well - as i said - the power light light up for about 20ms then noting happens anymore
>Have you already inspected dmesg output?
neither "dmesg" nor "lsusb" show any different output while plug in.
>May try with USB stick instead of your keyboard.
tried a wireless keyborad, a wired keyboard and a usb-stick all just seem to have power for some milliseconds.... then noting else can be noticed.
Click to expand...
Click to collapse
O.k., got it... so in fact there's nothing.
FrEcP said:
The only interseting difference i noticed is:
If i have my Keyboard plugged in while startup all lights (capslock,...) light up and STAY ON. Till i pull the plug. Then its like before...
Click to expand...
Click to collapse
That really sounds that there's still some power... like voom already pointed out.
Any measurements if there's some voltage drop or something?
Will need some equipment to do so, i guess.
FrEcP said:
Sadly an USB-Hub (powered) will neiter be recognised... (same bahaviour)
Click to expand...
Click to collapse
FrEcP said:
What i noticed - if i resome the device (after is was powered on) there are several wake up commands in dmesg for the screen and the usb hubs...
But it doesnt seem to me that the 2nd hub will get resumed proper... unless those command invoke both of em at once.
What does it tell for u when resuming the device?
Click to expand...
Click to collapse
I must admit, right now this tells me nothing...
Have to think about it.
Maybe we should compile a kernel with full debug output, at least for the USB part. This way we might get a clue what happens...
I wish a day would have some extra hours
Anyway i'll try to have a look in the kernel sources... looking for debugging as well.
Might take some time though, so you might try it yourself.
Regards,
scholbert

Thanks for the reply- well we are a bit further now as it seems.
Since archos released the lastest firmware .82 wich fixes this"bug" partialy
Anyway - the USB is working again with this version - but just until the device goes into standby without having an usb-device connected. Then u have to reboot to get it working again.
(all is fine if the device goes into standby with device connected)
So the big question is - what happens in between?
Well at least we know its software related now
I will check back dmesg again with this new firmware - and repost.
So the full debug kernel would be a nice idea - can u give me some adives how 2 start? I really have no clue about that yet.
I already compiled kernels in old suse 6.0 days but I think it will be different for "external" devices - I remember having read something about toolchain,...

tried a wireless keyborad, a wired keyboard and a usb-stick all just seem to have power for some milliseconds.... then noting else can be noticed.
Click to expand...
Click to collapse
With the dead port if I plug in a USB-Stick that has LED it lights up and then the light stops, while if it works (as it used to with working USB-Host on the Archos or when used with the PC) the LED stays on and constantly changes brightness. This LED behaviour is related to functioning dataflow.
On the other hand if I plug in a mouse with decorative LEDs in the dead port, the decorative LEDs, not related to dataflow, stay on, even though the mouse is not recognized. If I plugin a device that can be charged by USB it even shows that it is charging, though energyflow is probably not high enough to make that a practical use. Again in this case only the energyflow is relevant but no data activity.

Nexus 7 - Patch to power on when USB power inserted?

I am currently working on a car mod for my nexus 7, I know how to physically insert the nexus 7 to replace my current in built car sat nav, the only issue is the power! - it will be run from a cigarette lighter which gives enough power to charge it BUT theres one big issue, if I dont use the car for a while the battery will obviously run down to flat and when I start the car up again and it starts charging the screen will just show the charging icon and will not power up into the android interface.
This is a big issue as I cannot re route the power button on the tablet, therefore I need to modify the system files to power on when a charger is plugged in, someone on these forums has already done it with an android device:
http://forum.xda-developers.com/showthread.php?t=1187631
there is says to modify this file:
/system/bin/playlpm
however its not present on the nexus 7! - If anyone can help I would very much appreciate it!

I think you can just use Caffeine for that. There's an option in the settings to auto activate when plugged in.
IGNORE ME: forgot it would be turned off.

Yup, Im assuming I need to modify something at the system level.
Does anyone have any idea what file needs to be modified so that when a charger is plugged in to a nexus it powers on instead of coming up with the charging screen?

I am in need of a similar solution! Any help would be greatly appreciated!

I haven't looked at the N7's kernel yet, but if it's any similar to the Android kernels I've seen so far it can be more or less easiely be done with a small kernel edit.
Basically all you need to do is to give "init" (to "mother of all proceses" in Linux) the same .rc for LPM (="Low Power Mode") as for for "normal boot".
Should be something like copying "init.rc" over "lpm.rc".

HellcatDroid said:
I haven't looked at the N7's kernel yet, but if it's any similar to the Android kernels I've seen so far it can be more or less easiely be done with a small kernel edit.
Basically all you need to do is to give "init" (to "mother of all proceses" in Linux) the same .rc for LPM (="Low Power Mode") as for for "normal boot".
Should be something like copying "init.rc" over "lpm.rc".
Click to expand...
Click to collapse
Any more progress on this?

Looking for the same solution, was anyone successful in doing this?

zedix79 said:
Looking for the same solution, was anyone successful in doing this?
Click to expand...
Click to collapse
My particular use case was for my car install, and so I just decided to go with externalizing the power button. I have an external power supply (P-2140) that can pulse/close the circuit at ignition on and off that I plan on using from my old CarPC install. Here's my thread about power button externalization:
http://forum.xda-developers.com/showthread.php?t=1945947
I'm going to mount a button on the dash as well so I can wake the tablet from off. My goal is to have the tablet sleep for 2-3 days in airplane mode and then turn off when it has exceeded this sleep time. This way I'll only have to use this button in cases where I haven't driven my car for a weekend or so.

Add me to the list of people wanting a way to boot up the device when plugged in! (car-install).

Had a quick look at all the custom kernels on the forums here, and none of them mention that they support this. I wonder how hard it would be? Who's taking feature requests!

Would running it through constant power instead of switched power solve our issue? Would it continually drain the battery even if the tablet is @100% battery?

So, this is all from memory, but I looked at the init.rc (I believe) and it had a line that was something like
usb power
system_start charge
and then for many of the other options, it had system_start main.
Remember I'm doing this from memory, so I'm paraphrasing here. Anyway, I changed the action to system_start main (the same that I'd seen). It didn't work, but when I reopened the file (after boot) my edits reverted to default.
I just opened a thread on edits to system files not being saved after they are changed. Anyway, I'm thinking this may be the setting we need. If anyone can't find what I'm talking about, I'll look for the file and the specifics again. If anyone does find the actual information, could you please post. I know my actual names are incorrect.

Yeah, you can't really edit the files in / (root dir) as those are the initial ram disk the kernel boot off, i.e. they are only kind of temporaray in memory, on a reboot the init ram disk is remounted / recreated from the kernel image - hence changes are not persistant.
You need to edit the initrd image in the kernel to actually change those files.

zedix79 said:
Had a quick look at all the custom kernels on the forums here, and none of them mention that they support this. I wonder how hard it would be? Who's taking feature requests!
Click to expand...
Click to collapse
Plus 1 Request...

+2 ...

Someone got a link to the original kernel sources for a lazy cat?
Might take a look when/if I got some time - no promises though, time's very limited ATM.

HellcatDroid said:
Someone got a link to the original kernel sources for a lazy cat?
Might take a look when/if I got some time - no promises though, time's very limited ATM.
Click to expand...
Click to collapse
You can get some instructions and kernel files here I believe:
http://source.android.com/source/building-kernels.html

Guys.... any news on this?

Any updates? I'm in the middle of a similar project
Godswrath said:
Would running it through constant power instead of switched power solve our issue? Would it continually drain the battery even if the tablet is @100% battery?
Click to expand...
Click to collapse
Yes but this defeats the purpose as we are using "external power connected" as a trigger for the displays. In my case I'm running torque and a recording app when power is conected and killing them when disconnected. This way when i start the car the recording will start and Torque will display my gauges and when i turn off the car the apps get killed and the phone turns off. (therefore saving battery) however when we start the car again android boots into "power manager" (the big green battery screen) Android at this point its not booted so daemons are not started and we cant do anymore triggering requiring us to manually long press the power button to continue normal operation.
* My mod installation is persistent. This is an old phone that i intent to leave there at all times. (no GSM conectivity)
I much rather have it be automatically
pheonixsingh said:
Yup, Im assuming I need to modify something at the system level.
Does anyone have any idea what file needs to be modified so that when a charger is plugged in to a nexus it powers on instead of coming up with the charging screen?
Click to expand...
Click to collapse
I have been messing around with this for the whole day. I wil ldo some more investigation tomorrow i believe that while we cant touch the virtual disk files (because they are mounted at root) pm.jar is persistent and we should be able to make some changes in java and put the modified file back having it boot this way without actually having to compile a kernell.
If anyone wants to help reply here (i subscribed to thread)
This is of uttermost importance to me and any help would be appreciated)
Some pics of my project >> dropbox.com/s/ivx9mrry2671g15/2012-12-22%2020.28.14.jpg (couldn't post URL because new user)
phone >> samsung r720
edit:
One question. If i externalize the power button like OP did.... will i still have to long press or could i have it be a flippable switch. ( i could live with that)
---------- Post added at 05:11 PM ---------- Previous post was at 04:54 PM ----------
doing some research I found out that this is more related to firmware than to OS since it has to do with BIOS and POST (not sure if those are the appropiate terms when talking about a phone)
Starting to think a hardware solution might be more approachable.
>>leaving this here for reference
tombtalk.net/?p=627

For someone who has recompiled a kernel, this should be easy. There is one setting in one file that needs to be changed. I can't remember it now, but if someone wants I'll look for it. Basically the line reads something like:
on power = boot charge
and needs to be changed to
on power = boot system

Take that multi-touch! Fix and lock in what works for YOU regardless of updates

By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes? Suddenly you have dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. Touchscreen works ok when held or plugged in, but is unusable on a table?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q, will work on LTE and custom ROMs also):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in this post.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
Settings->About tablet [tap "Build number" 7 times]
Settings->Developer options [check "USB debugging"]
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
wait until Android is COMPLETELY booted
Note: if you are on Android 4.4 the stock 4.3 kernel will not get past the BouncingBalls
wait 120 seconds for the boot to settle down
press/hold the Power button 10-15 seconds until the tablet reboots
proceed to next step
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
if adb reboot does not work for some reason, use the power button to shutdown/reboot
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
upon first reboot you will have the touchscreen software from the installed ROM/kernel
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.

very interesting! lots of FC after loading the file, cant really "Power off using power button" because of FC-windows, using adb reboot instead.
current ROM: [ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 10-TEST][2013/08/27]
ts-10: no more jumping in google maps while zooming/panning, but still jumping in other apps. after second reboot, starts jumping in maps again. after third reboot, no jumping on rightside of screen.
screenshot using two fingers
ts-20: lots of jumping on right side of the screen, zooming/panning in gmaps is still jumpy. after third reboot, still jumpy in gmaps.
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, same effect. after third reboot, still jumpy on right side of screen.
so what exactly are in those files?

neonlite said:
very interesting! lots of FC after loading the file, cant really "Power off using power button", using adb reboot instead.
tried ts-10. no more jumping in google maps while zooming/panning, but still jumping in other apps, will try others.
so what exactly are in those files?
Click to expand...
Click to collapse
When you say lots of FCs, can you tell me what ROM/version you are running?
You should IGNORE any instability in that first boot. While you can boot into android using the files I'm providing (and in some cases run fine), there could be mismatches in versions depending on what you have currently installed, which is why I say in RED you must reboot at least once before the system will become stable.
Once you do that reboot, you are back on your original software with just the touchscreen controller updated.

neonlite said:
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, seems most stable.
Click to expand...
Click to collapse
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.

sfhub said:
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
Click to expand...
Click to collapse
yes, ignored all FC's. no problem.
ts-10 is running perfectly, no more jumpy stuff. maps/right side of screen, hold and drag working great too.

I really appreciate how much effort you've put into helping others with troubled devices here.
Could we get some clarification on what exactly the 3 packages are? Are these touchscreen settings customized by you or simply the settings from each of the 3 versions of 4.3 we have had available to us?

You sent me here from the other thread and i must thank you, the ts10 one worked fine and now no screen problems, cancelled my replacement. Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?

It is the touchscreen controller software.

pashinator said:
Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
Click to expand...
Click to collapse
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.

sfhub said:
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
Click to expand...
Click to collapse
cool i thought i broke it by bashing it to get the screen to work again

i've been a long time lurker at the xda forums and your multitouch fix made me register and become a member just to say thanks. ts10 fixed my multitouch issues, going to observer for a few more days and update you if there are bugs. thanks a lot!

My tablet was working perfectly on the JSS15J then JSS15Q came along and I found letters "sticking" while typing and the screen was unresponsive to touch while laying flat on a table. I flashed the ts-10-lock image and so far, so good. I have been typing for awhile now with no "sticking" letters, and while laying flat on a table. I have not encountered the unresponsive screen at all flat on its back or otherwise. I will continue running through scenarios that used to give me problems and report back if I encounter anything. Also, running Bulletproof kernel and no impact with kernel functions.
Thank you sfhub!

Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
This is the video of my N7 placed on my MBPs' keyboard.
http://www.youtube.com/watch?v=H05N1P0dpTo
Can this really be only a software problem?
I am not really experiencing other touchscreen issues with my N7 except for some very rare stuck touches. This one I triggered by accident.

bandit_knight said:
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
Click to expand...
Click to collapse
So this guy goes to the doctor's office and says my head hurts everytime I hit the wall. The doctor says, then stop hitting the wall.
Couldn't you just slide it over and don't use the tablet on top of the keyboard?
Have you considered the MacBook Pro might be emitting interference? Stray currents and voltages? It doesn't take much to throw these capacitative touchscreens off.
On this thread, most people have it much worse than you making the tablet very hard to use. We are trying to get these units back into a state that is at least usable.
Your case, while an interesting science project really isn't something someone would feel any sense of urgency to help address.

Excellent.
I'll try these now and put them through there paces.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Great work
Incredible!! tried the ts10 and OMG everything is fixed!! Great work, sfhub!!
you should work in Google, seriously! shouldnt he, everybody?
My device is:
1) 4.3 JSS15Q
2) two finger touching registered as one finger, and muiti-touches ghosted. hold on the Left side of screen and the touch is registered repeatedly
1) TS10

Yea I booted 10 first and it is great. I can't reproduce any of the bugs I've seen before using YAMMT.
Google Maps Pinch/Zoom is working flawlessly. I couldn't even zoom in before.
The OP says to "fastboot boot boot-ts10-lock.img". Should we eventually "fastboot flash boot-ts10-lock.img" to make it permanent?
My N7 is:
HW rev_e
Bootloader....... FLO-03.14
15Q - CM 10.2 Kanged Build 9
Sitting the N7 on my Logitech Keyboard doesn't make it go crazy either! LOGITECH FTW

sfhub said:
It is the touchscreen controller software.
Click to expand...
Click to collapse
How do you "lock" it in so that it won't get updated? Is it just a file in the filesystem, if so how do you prevent "fastboot erase" from getting rid of it? I've looked at ektf3k.c and know where I need to make a change so that it will replace any non-matching version, but I don't really know where the actual firmware is stored. It doesn't seem to be in the vendor part of the kernel tree or in the actual ektf3k.c or ektf3k.h files. Where is it kept? kept in fw_data.b
I'm new to Android, but I'm not new to Linux or reverse engineering so please be patient with me. Just looking for a technical description of how you did what you did. What exactly is in the .img files?
EDIT: I haven't booted any of them yet, but I'm guessing these are Linux kernel images with a modified version of the elan driver. Sorry for being stupid, I'm just trying to put this all together in my head and I can't cope with anything that seems like magic. Thanks for your time.
EDIT: Ok, I figured out where the firmware is stored. I also successfully built a ROM with my compiled kernel and flashed them to the tablet. No brick, it booted the second try and seems to work. Of course there's no apps on it hardly.
I'm kinda thinking out loud here, please correct anything that I get wrong:
I started off with the assumption that there was a closed source driver, but that seems to have been incorrect on my part. After looking at the code a little more, I see that ektf3k.c appears to be the lowest level driver, outside the embedded firmware. The driver does only update the firmware in the case that the flash is empty (FFFF.....) or the firmware presented is a higher version (just as you said of course). It appears that a simple change will make it flash any version presented that is different than the one currently flashed in. I plan to try this on my tablet and see if there are any unexpected repercussions from doing so.
I wish I had a datasheet for the controller (hint hint anyone).
DISCLAIMER: I know that you have already solved this problem in an arguably better way, I just want to tinker around a little. Thanks again. :good::good::good:

sfhub said:
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be able to get touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
Click to expand...
Click to collapse
So if we do this can we lock the boot loader backup. If for some reason it doesn't work will I be able to take it back for exchange. After unlocking the boot loader. Do people leave the boot loader unlocked . Is the software staying the same meaning will I be ok downloading future updates.

Is there a way to find out what variance is installed right now on the device? I got JSS15Q and my tablet is useable but sometimes there are ghost touches or the touch is stuck or gets interrupted and the likes.

Voyo Winpad A1s drivers

Hi there.
I recently had to do a full reinstall of Windows 10 on this great little tablet.
Unfortunately I lost some of the drivers in the process...
Windows update was able to install mostly everything, except:
Screen Rotation driver (needed for some games)
Touchscreen driver
Hibernate option
Camera
The camera I really don't use and its pretty bad, my very old nokia was better.
I was able to install the Goodix Touch HID general drivers for touchscreen and the Kionix sensor driver from a different Voyo model.
The touchscreen seems to be fine now, the rotation isn't. It seems to be using a different setup as it turns the wrong way.
I locked it to a landscape direction, so I don't break my neck using it.
Not having the hibernate option is a also an issue for me, as the only problem I have with this amazing tablet is the battery.
It runs fine for 4-8 hours but when it shuts down, it will not turn on properly until its fully charged.
With this limited power its obviously not my main computer, so having the hibernate option allowed me to boot it faster for each use.
I tried enabling the hibernate option on bios, but the system seems to think it simply does not support it.
Its a matter of drivers, of course.
I asked the Voyo company support for them, but no reply...
Is there any kind soul out there that can share their drivers?
It will probably not work properly with drivers from different models, but I'm willing to try, you never know...
I already tested the mini drivers that are here in the forum.

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?