Database Info

My MicroSD card is starting to corrupt

My /Removable/MicroSD is starting to corrupt. I've been editing scripts on my MicroSD with ES note editor. It started today with files not overwriting other files with the same name, then progressed into edited files saved with corrupt or no data at all, then a few files disappeared, then a directory became corrupt and I could not see a file that ES told me I was overwriting with another file with the same name, and now I am loosing full directories. Is this a partition issue or is the whole card going/gone bad? The card is as factory shipped. I have never formatted or partitioned it.
I have unmounted and remounted the card. That allowed me to edit and save for a few hours. Then another corrupted file happened. I just took the card out and reinserted it as this fixed a similar problem I had a while ago but it only happened once and went away until now, so we'll see if it just wasn't seated properly. One of the 2 directories that disappeared came back after reinserting the card but the second is still missing. I had already backed up my scripts, and now I will back up the entire card to disk.
Does this sound like its going or gone South, or will pulling all the data off, formatting the card, and putting it all back on work to fix it? Is it safe to trust this card anymore or should I RMA it as it should still be under warranty? Its a Sandisk 64 SDXC and not "officially" compatible and was wondering about that as well. I've had it for about 6 mos. I had hoped by spending the little extra $ and picking a name brand it would be more reliable but I guess I got a bad one despite the on-average Sandisk quality. Any advice would be appreciated.

So far, I've only once suspected my microSD (as in yoru case a 64 GB Sandisk UHS-1 Class card) to have gone bad. (Re)formatted it with Gparted (was running data2sd at the time, kicked that out, too) and it has been going strong since without a single hitch.
I'd try and format it, doesn't hurt, only takes time, and it satisfies your tinkering needs at the same time.

MartyHulskemper said:
So far, I've only once suspected my microSD (as in yoru case a 64 GB Sandisk UHS-1 Class card) to have gone bad. (Re)formatted it with Gparted (was running data2sd at the time, kicked that out, too) and it has been going strong since without a single hitch.
I'd try and format it, doesn't hurt, only takes time, and it satisfies your tinkering needs at the same time.
Click to expand...
Click to collapse
Thanks for the reply. What is interesting and seems far-fetched to be coincidental is the corrupted directories are the directories that I am constantly editing and saving files to - My scripts dir and its sub-directories. Guess they mean it when they say flash was not designed to be constantly written to. I can't *believe* I have cycled it to its limit just editing scripts over a 6 mos span. I couldn't have saved files more than a couple thousand times if that.
Waterproof**, x-ray proof**, temperature proof**, shockproof**, but NOT write-proof**

Double directories? This is getting out of hand!
Well I am backing up my MicroSD now, and I just ran across two directories with the same name in the same folder? Two "Scripts". How is this possible? One had files, the other was blank? How can the OS allow this to happen? When it copied to Windows, a (1) was appended to the directory name of the second duplicate.
Just for S&G, I tried to copy a file from one into the other and Windows errored saying something like "device is busy or has been disconnected."
If I had files in both directories and I cd to that directory, which one would I get (trick question)? I believe the dups are only on Windows. I don't think the device actually sees both directories. At least it doesn't show them to me in ES. Bizarre corruption. That surely might explain why files in this directory were getting corrupted. Or maybe the corruption of the files was responsible for the double directories. Time for a format (and a beer) for sure.
Let this be a word to the wise:
So yes I am going to format this, but I wanted to play with this problem a bit and see what I could figure out. As I predicted, and made about my 5th backup just in case, here's what just happened.
1. When there were Script dir duplicates, I could copy from the one with files.
2. I deleted the one without files (predicting it may delete both, but it only deleted the blank one as intended but...)
3. The remaining Script dir could not be copied from, nor a new sub-directory created inside. File names could not be changed. Actually it did allow me to make a copy, but the target directory was blank.
4. Deleted the second Script directory. Now the B2R script is lost forever (no just kidding, I have 5 backups at least)
5. Copied one of my backup copies of Scripts back to the card
6. Now its fine (until I can format it), I can copy from it and create sub-dirs inside it, etc. But I will be working off another copy in Internal storage until I format this card.
7. So the lesson here is ALWAYS make a backup before something glitches out on you because it eventually will and you will need it, or choose to be SOL; life is full of choices. And if it has already glitched out on you, make a second backup of your critical files just in case something like this happens to you and you've made incremental changes. Without my backups I would be loosing about 3 months work in just this one folder alone. It contains every script I have ever written and a bunch of example scripts to learn from.
@_that to comment, but this is what I think happened: This must be some kind of corrupt FAT problem. Very similar to the recovery blob not being found by the bootloader issue from a recent post, but instead of a partition problem its a file allocation table problem, as they reside on the same partition in my case, quote _that below:
"I have a new theory about why this happens: partition tables mismatch. In other words: The location where the recovery writes the blob is not the same as where the bootloader expects it. Thus the bootloader ignores your blob."
It seems the empty directory was the directory the system thought the files were in. Once that directory was removed, the actual one (as the human perceives; as seen in ES) containing files no longer contained them, as far as the OS was concerned. So by deleting the one you effectively deleted the other because its impossible that can can coexist and both be functional. I thought something like this would happen and it did. Like I said earlier, its Miller time.

elfaure said:
7. So the lesson here is ALWAYS make a backup before something glitches out on you because it eventually will and you will need it, or choose to be SOL; life is full of choices. And if it has already glitched out on you, make a second backup of your critical files just in case something like this happens to you and you've made incremental changes.
Click to expand...
Click to collapse
Good advice. Always make one backup more than you think you need.
elfaure said:
This must be some kind of corrupt FAT problem.
Click to expand...
Click to collapse
Probably. ExFAT is a proprietary and patented Microsoft filesystem, and support for it in our TF700 is through a proprietary closed-source third-party kernel module that contains this licensed "technology".
You could try running chkdsk in Windows on the card to detect and fix filesystem errors.

_that said:
Good advice. Always make one backup more than you think you need.
Probably. ExFAT is a proprietary and patented Microsoft filesystem, and support for it in our TF700 is through a proprietary closed-source third-party kernel module that contains this licensed "technology".
You could try running chkdsk in Windows on the card to detect and fix filesystem errors.
Click to expand...
Click to collapse
Funny how they don't even support exFAT in XP without an extension. Maybe it was developed after XP was released. I would assume it is supported by default in W7 and above?
Question: Do you know what is the su password for the terminal app in GParted Live? Or is this limited to GNU staff use??
Do I "sudo gparted" or "sudo passwd root" and set a new password??

elfaure said:
Funny how they don't even support exFAT in XP without an extension. Maybe it was developed after XP was released. I would assume it is supported by default in W7 and above?
Click to expand...
Click to collapse
Good guess. See http://en.wikipedia.org/wiki/ExFAT
elfaure said:
Question: Do you know what is the su password for the terminal app in GParted Live? Or is this limited to GNU staff use??
Do I "sudo gparted" or "sudo passwd root" and set a new password??
Click to expand...
Click to collapse
http://lmgtfy.com/?q=gparted+live+root+password
GParted live is based on Debian live, and the default account is "user", with password "live". There is no root password, so if you need root privileges, login as "user", then run "sudo" to get root privileges.
Click to expand...
Click to collapse
You can run "sudo -i" to just get a root shell if you want.

_that said:
Good guess. See http://en.wikipedia.org/wiki/ExFAT
http://lmgtfy.com/?q=gparted+live+root+password
You can run "sudo -i" to just get a root shell if you want.
Click to expand...
Click to collapse
Looks like my windows\system32 dir has a 2004 date on it. So just before it came out. Nice they have a patch now.
lmgtfy.com is very cool! I've never seen _that before. Really a good way to say "why can't YOU just Google it YOURSELF". Yes, I already followed the same link to get the commands I asked about.
I couldn't figure out a way to get a Logitech bluetooth mouse working in Gparted Live. Probably need linux drivers?

elfaure said:
I couldn't figure out a way to get a Logitech bluetooth mouse working in Gparted Live. Probably need linux drivers?
Click to expand...
Click to collapse
That's a live distro for partitioning stuff, not for supporting all kinds of exotic hardware. Most likely it doesn't even have any bluetooth stack. Use a full desktop distribution like Mint if you want support for bluetooth input devices.

_that said:
That's a live distro for partitioning stuff, not for supporting all kinds of exotic hardware. Most likely it doesn't even have any bluetooth stack. Use a full desktop distribution like Mint if you want support for bluetooth input devices.
Click to expand...
Click to collapse
Yeah, I figured as much but I thought you possibly have a trick.
Cinnamon or Mate desktop? Live iso version available somewhere (couldn't find one)? Never mind, I think I got it. I don't need you to send me another lmgtfy link. But still, Cinnamon or Mate desktop?
Ok, here's my problem. I need to make a bootable CD (not DVD). The iso for Mint 15 Cinnamon is 923MB. It won't fit on a 700MB CD, and my PC can't boot off DVD or USB. Any suggestions besides having to partition a HDD to install a dual-boot configuration which I don't want to have to do just to run Linux once in a while. I would like a Live CD instead. Reduced size minimal distro somewhere to be found?
Ok, found one here for Linux Mint 13 Maya. Hope its not someone's hack. But I think its a better option than Plop. I don't want to start hacking my Windows PC all up just to get Linux. If its any more hassle than burning a CD I'll just use GParted with a corded mouse.
Only 7 available seeds for this torrent, and only 1 is up now. Popular item! (ha). Had it going with 4 but I was hogging too much bandwidth and had to pause fpr a bit then restart. When it restarted, looks like 3 of my seeds blew away in the wind. Looks like tomorrow then...I was hoping to burn the iso and play with it tonight. Oh wait, just got another 1 back. Now were up to 100kB/s. Whoopee
**********************************************************************************************************
http://forums.linuxmint.com/viewtopic.php?f=46&t=110933 (last link goes to next link)
http://forums.linuxmint.com/viewtopic.php?f=61&t=103449&p=604069

elfaure said:
Ok, here's my problem. I need to make a bootable CD (not DVD). The iso for Mint 15 Cinnamon is 923MB. It won't fit on a 700MB CD, and my PC can't boot off DVD or USB.
Click to expand...
Click to collapse
You have a strange PC. Or no DVD drive?
All PCs that I know (that have been produced in this millennium) can boot from DVD or USB with correct BIOS setting and a correctly formatted bootable medium.

_that said:
You have a strange PC. Or no DVD drive?
All PCs that I know (that have been produced in this millennium) can boot from DVD or USB with correct BIOS setting and a correctly formatted bootable medium.
Click to expand...
Click to collapse
Yes I know. I'm cheap and old school with PCs, what can I say. The rest of my devices are current offering. I haven't bought a new PC for over 10 years. Its an older "failed" CAD station that was slated for the dumpster about 3 years ago, then being about 3-4 years old, because our admin was too lazy to test for a simple problem - a failed RAM SIMM. I resurrected it, replaced the failed 512 SIMM and added two more, added a scavenged drive (now 3), and now its my home $100 desktop (replacing the free Pentium I had but was too slow to use). It already had the Quadro FX 3800 video card with a dual core Xeon CPU @ 3.33 GHz. But no DVD drive, only CD drive. BIOS does not support boot from USB either.
Its faster than my old work Dell Precision 690 before I got my new 6-core Xeon T3500. So those were my limitations to work with. And I think I found the best possible solution with Mint 13 Maya iso CD. Looks like Mint 15 just was released. Beautiful OS by the way, I checked out some uTube on it last night. Can't wait to test drive it. Might even make an MS defector out of me. Linux seems to run well on older hardware with slower CPUs vs Windows on the same hardware, so I'm hoping it can breath new life into this semi-archaic box I call my desktop. Now you see why I'm on the tablet so much.

Hey @_that
You were right again. It is a DVD drive. In XP Pro SP2 it was just a CD but after installing SP3 it shows up now as a DVD/CD. Getting Mint 15 32 bit now instead. The DVD drive bay load door is scratched and faded, so I couldn't tell just by looking at it, and was going off what Windows device manager was showing in its tree. I did initially pop a DVD in and it couldn't read it which further substantiated that it was a CD and I never questioned it. Turns out the DVD I tested it with was a DL, and this is only a SL DVD drive. Now I have a 1.7GB limitation, not 700MB which opens up most iso options. But I still have no boot from USB option in my BIOS. I'll look to see if there's an updated BIOS available to open up that option. It would be very nice to have a few thumb drives with different Linux distros to test drive, and a puppy Linux on my key chain.
Sent from my ADR6350 using xda app-developers app

Live Mint 15 Mate
Hey @_that-
Coming to you live from Linux Mint 15 Mate. I guess when running this off a live CD, there is no way to copy a file to /etc is there? I opened it as administrator, and it still wouldn't let me copy the file because this directory is on the CD, not the HDD, correct? I was trying to get my Synergy connected between my MS PC and my other PC running live Linux so I can share my mouse and keyboard seamlessly without my KVM switch. I'm impressed with how easy this is to setup. Also with your ability to see me as a Windows transitional user, and point me to Mint and not Ubuntu. I like it.

elfaure said:
Coming to you live from Linux Mint 15 Mate. I guess when running this off a live CD, there is no way to copy a file to /etc is there?
Click to expand...
Click to collapse
I don't know about the live environment - it's normally only used to install the OS to a real hard drive. I find it still strange that your PC doesn't support booting from USB. Maybe that's a sign that you really should install Linux on a HDD.
elfaure said:
I was trying to get my Synergy connected between my MS PC and my other PC running live Linux so I can share my mouse and keyboard seamlessly without my KVM switch. I'm impressed with how easy this is to setup. Also with your ability to see me as a Windows transitional user, and point me to Mint and not Ubuntu. I like it.
Click to expand...
Click to collapse
2 monitors, 1 keyboard, 1 mouse? Yes, Synergy is nice.
And why Mint: I simply don't agree with Mark Shuttleworth's direction where he is taking Ubuntu - fortunately there are alternatives in the OSS world. I consider Mint as the "sane", i.e. actually usable, version of Ubuntu.

_that said:
I don't know about the live environment - it's normally only used to install the OS to a real hard drive. I find it still strange that your PC doesn't support booting from USB. Maybe that's a sign that you really should install Linux on a HDD.
2 monitors, 1 keyboard, 1 mouse? Yes, Synergy is nice.
And why Mint: I simply don't agree with Mark Shuttleworth's direction where he is taking Ubuntu - fortunately there are alternatives in the OSS world. I consider Mint as the "sane", i.e. actually usable, version of Ubuntu.
Click to expand...
Click to collapse
Yes, this is my work environment now. I have two Dell Precisions, one a 690 and the other a T3500. You got it, two monitors, 1 kb, 1 mouse. Downloading and installing Wine now. I am interested to see if I can run Solidworks on Linux thru Wine. Wow, Linux had come a long way. "sudo apt-get install synergy". All the terminal commands I learned for Android are very useful now, thanks!
ps-"sudo -i" works like a charm.
[Edit] Doesn't look like SW wants to run on Linux loaded thru Wine. I figured as much, but it was worth a try.
Video is not bad at all, despite all I've read. They really must have clean it up for 15. Picture is good, sound is good, seeking is a bit slow, and my biggest complaint is there is no stretch or zoom to fill the entire screen. You have to select from predefined aspect ratios and get as close as you can. Android has better tools in this area than Mint, or maybe it more closely matches a standard aspect ratio like 16:9 for 1920 x 1200 is close (1.77 vs 1.6). Ok, _that's it for the day. Got to get some real work done here now.

Regarding the live environment, its used all the time to test drive different Linux distros before deciding which one to finally install. That's the beauty of a free open OS and a 50 cent DVD and its advantage over a flash card in this case, if you wanted to test 3-5 different ones (back and forth, not sequentially) before deciding on *the one* to finally install to HDD.

elfaure said:
Video is not bad at all, despite all I've read. They really must have clean it up for 15. Picture is good, sound is good, seeking is a bit slow, and my biggest complaint is there is no stretch or zoom to fill the entire screen. You have to select from predefined aspect ratios and get as close as you can. Android has better tools in this area than Mint, or maybe it more closely matches a standard aspect ratio like 16:9 for 1920 x 1200 is close (1.77 vs 1.6).
Click to expand...
Click to collapse
I have no idea what you are talking about. There are lots of media players to choose from, and all that I know have a fullscreen mode.

_that said:
I have no idea what you are talking about. There are lots of media players to choose from, and all that I know have a fullscreen mode.
Click to expand...
Click to collapse
What I mean is by toggling full screen in Mint, its less than full screen because the movie aspect ratio of its recorded resolution is preserved in the scaling function. So there are still black bands either high/low or left/right if you don't play with the player aspect ratio (4:3 vs 16:9) to best match that of your movie in the distros fullscreen mode with the stock player. Which ever limits to extents first in the scaling horiz or vertical DPI defines the "fullscreen" size you get which is less than a full screen. A zoom function does not but a stretch function does override the recorded aspect ratio to fill the full screen (I'm talking about TV's and Dice/BS/MX Player features now, not what's in the Linux default distro player) so with stretch you can get a distorted picture (disproportionate scaling) but not with zoom. These are not included in the stock distro player.

elfaure said:
What I mean is by toggling full screen in Mint...
Click to expand...
Click to collapse
I am using mplayer for video playback - I don't know if that is still included in end-user-focused distros like Mint, but it's one of the most powerful video players that exist. Mplayer has no GUI at all (everything is controlled via the keyboard) - and the "f" key toggles between fullscreen and window.

[Q] Shield Controller Not Detected by PC

Hey Everyone,
I thought about posting this into the mobile kepler thread because thats where I started from. However, no one else running mobile kepler seems to have this issue.
I have a macbook pro running windows 8 in boot camp. I installed steam (beta client enabled), geforce experience and the latest beta graphics drivers. Games work great while playing on the laptop (burnout, GTA 4 and Half Life). The registry hack to skip mobile GPU check works to enable streaming to the shield. When go into shield streaming on the shield, it sees the laptop and games. I can pick Steam and it changes the resolution on the laptop and steam opens and goes into big picture mode.
Sound and video stream to the shield fine. But I can't control anything with the shield. I can control anything with the touchscreen or with the controller. If i go into settings in big picture mode (with the mouse on the computer), I can click on Controllers and it says none detected. This is the case in every game as well. Sound and video make it to the shield without issue, but I can't control anything.
I have tried restarting, reinstalling geforce experience, trying non-beta graphics drivers, etc. Nothing seems to work. I had also installed Splashtop streamer (just because I use that product on every machine I have) and I thought that might be conflicting with things. But uninstalling it did not help.
Has anyone experience this? Anything I can try to get it to work?

There are other people reporting similar issues on the GeForce forums. There are two issues that I've seen.
1. SecureBoot incompatibility - seems unlikely for you since the Mac's EFI version doesn't support it.
2. Short file name issue
The way that NVIDIA gets their input DLL loaded into every process is using a registry value that only supports short file names. If short file names are disabled for some reason, it won't be able to load the DLL and the controller won't work.
There's more info in the forum links from this post. http://forum.xda-developers.com/showpost.php?p=44678873&postcount=40

Thanks for your reply. I did some research after posting and found those two items you mentioned. Mine Mac is booting in Legacy mode so thats not the issue. I tried the short name recommendation which was to change 8dot3name to 0 (mine was originally set at 2) and then uninstall geforce experience and drivers, delete the Nvidia folder from both program files folders and then restart and reinstall. That hasn't solved the problem. I also tried changing it back to 2 and and doing the same with no success.
Supposedly NVIDIA is testing a fix internally and it should be out this month. I'm just worried that my issue has something to do with boot camp. I have seen others with MacBook pros on here getting this to work and I don't really see what the difference is between their setup and mine that is causing this to not work.

Does windows keep logs of errors of things it couldn't load? I imagine if the registry was telling windows to start something but it couldn't find it on the disk (due to short names) it would throw an error right? (sorry, I'm mostly a mac guy so I don't know what the PC equivalent to Console.app is)

jeffburg said:
Does windows keep logs of errors of things it couldn't load? I imagine if the registry was telling windows to start something but it couldn't find it on the disk (due to short names) it would throw an error right? (sorry, I'm mostly a mac guy so I don't know what the PC equivalent to Console.app is)
Click to expand...
Click to collapse
is console.app the terminal? If so on windows its cmd (hold windows key + R to open the run dialog, enter cmd, OK) but windows cmd is vastly inferior to the mac terminal in my opinion (I am a windows guy, just saying, the windows command line isnt as good as the one on UNIX like systems).
The windows event log can be opened from control panel. http://www.techrepublic.com/blog/wi...ack-down-issues-that-cause-slower-boot-times/.

Console looks to be equivalent event viewer. Thanks for the suggestion. I should be able to inspect it tonight and look for errors loading the rxinput dll file.

Wow. What an annoying issue. So the problem was that my Program Files folders don't have short name. On top of that when I try to give them short names with admin prompt and fsutil file setshortname it says permission is denied. I'm assuming this is because the Programs files folders are super super system folders.
I tried using %PROGRAMFILES% in the registry entries for rxinput.dll but that didn't work either. So I found the jankiest workaround ever. I copied the dll to the C drive root and then linked the registry to that file. (I actually copied the both dll files. one is under Program Files X86 and on under regular)
Now it works!!!!!
Jankiest workarund ever... but it works.

jeffburg said:
Wow. What an annoying issue. So the problem was that my Program Files folders don't have short name. On top of that when I try to give them short names with admin prompt and fsutil file setshortname it says permission is denied. I'm assuming this is because the Programs files folders are super super system folders.
I tried using %PROGRAMFILES% in the registry entries for rxinput.dll but that didn't work either. So I found the jankiest workaround ever. I copied the dll to the C drive root and then linked the registry to that file. (I actually copied the both dll files. one is under Program Files X86 and on under regular)
Now it works!!!!!
Jankiest workarund ever... but it works.
Click to expand...
Click to collapse
Wow, bit of an odd one. Good that you got it sorted though :good:
With windows you often have to take "but it works" as the correct solution There probably is a better way in this case (taking ownership of program files and then trying to make the changes you require first before resetting the ownership is what I would have looked at doing) but if it works now your probably best to just leave it rather than tempting the computer to say no again

8.1 Jailbreak (not typical)

Salutations folks,
Before you get ready to get your flame on, I'm NOT asking about the STATUS of a RT Windows 8.1 Jailbreak. I'm posting about jailbreaks in general. I'm from a linux/android background. I got an Asus Vivotab RT LTE (AT&T version) for a steal off 1Sale. Before I even looked into doing anything with my tablet, I updated it to 8.1. Then I finally got around to looking into running desktop apps on Windows RT (not knowing how it all worked with RT vs desktop), I ran into the issue of not being able to run them (duh, right?). Then I found out about jailbreaking. So.. do you HAVE to jailbreak to run desktop apps? As I understand it, we currently have to run 8.0 to jailbreak/run desktop apps, yes? Well.. I obtained the Asus recovery files to downgrade my 8.1 to 8.0. On a whim, I updated my 8.1 with the 8.1 big spring update (basicly 8.1.1). I seem to be able to run some of the ported desktop apps without any problem. Am I missing something? How'd my tablet manage that without having run the jailbreak? And jailbreak doesn't work on 8.1 anyways? Before anyone says I'm full of it.. (you can click the thumbnail for full pic)
(windows rt 8.1 with 8.1 spring update installed)
(windows rt 8.1 running desktop 7zip)
(windows rt 8.1 running desktop putty)
(windows rt 8.1 running desktop notepad++)
Can anyone clarify if I'm missing something or I've come across an anomaly or even a blessed relief?
Thanks.

This is sure amazing
1. Can you run *any* unsigned application or only a few work (and the rest throw signature errors?)
2. Check the status of Secure Boot in PowerShell. Run as admin, "Get-SecureBootPolicy", press enter (http://technet.microsoft.com/en-us/library/jj603043.aspx)
3. Could you detail exactly your process? I understand that you did the following:
(On 8.1) Run unsigned desktop app, fail with digital signature error.
(Downgrade) Downgrade to 8.0 -> (On 8.0) Run Jailbreak -> Run Desktop Apps and they work.
(Upgrade) Upgrade to Windows RT 8.1 (via Store?) -> Upgrade to 8.1.1 (Spring Update) via Windows Update -> Run Desktop Apps and they work (partly or all of them?)
4. I'm not sure if it'd be any useful, but perhaps you could look in your EFI system partition (mountvol S: /s) as there has been a previous report of Asus leaving debug tools in VivoTab RTs before (http://forum.xda-developers.com/showthread.php?t=2477285). If you could retrieve a "debug" version of Secure Boot Policy from your EFI partition then it means that Secure Boot has just disabled itself on your tablet. It's highly unlikely, however, since you weren't able to run desktop apps in your original 8.1 install...

jimmielin said:
This is sure amazing
1. Can you run *any* unsigned application or only a few work (and the rest throw signature errors?)
Click to expand...
Click to collapse
I only grabbed the ported Putty, 7zip and Notepad++ desktop apps as those were the only ones that I was needing.. Oh I recently grabbed the FileZilla one too. All ran without any problems and never got any signature errors. Hell.. even my 7zip integrated into the shell and replaced archive icons with 7zip archive icons and opens my archives by default with the desktop app. Were there any particular applications you wanted me to try so that I can see if I can replicate any signature errors?
jimmielin said:
Check the status of Secure Boot in PowerShell. Run as admin, "Get-SecureBootPolicy", press enter (http://technet.microsoft.com/en-us/library/jj603043.aspx)
Click to expand...
Click to collapse
SecureBoot is enabled and it displays a Publisher GUID. Confirm-SecureBootUEFI confirms SecureBoot is enabled too.
jimmielin said:
3. Could you detail exactly your process? I understand that you did the following:
(On 8.1) Run unsigned desktop app, fail with digital signature error.
(Downgrade) Downgrade to 8.0 -> (On 8.0) Run Jailbreak -> Run Desktop Apps and they work.
(Upgrade) Upgrade to Windows RT 8.1 (via Store?) -> Upgrade to 8.1.1 (Spring Update) via Windows Update -> Run Desktop Apps and they work (partly or all of them?)
Click to expand...
Click to collapse
hmm
- Received clean OEM install Vivotab RT LTE with RT 8.0
- Upgrade to Windows RT 8.1 via Store
- (attempted to run some ported desktop apps, received error)
- was going to downgrade back to 8.0 after getting Asus recovery files but instead..
- Upgrade to RT 8.1.1 (Spring Update) via Windows Update
- (attempted to run some ported desktop apps, ran successfully, no errors)
NOTE: Not once had I ever gotten around to downloading or installing the Jailbreak. Is there some way to confirm if I have the jailbreak installed at startup or something?
jimmielin said:
4. I'm not sure if it'd be any useful, but perhaps you could look in your EFI system partition (mountvol S: /s) as there has been a previous report of Asus leaving debug tools in VivoTab RTs before (http://forum.xda-developers.com/showthread.php?t=2477285). If you could retrieve a "debug" version of Secure Boot Policy from your EFI partition then it means that Secure Boot has just disabled itself on your tablet. It's highly unlikely, however, since you weren't able to run desktop apps in your original 8.1 install...
Click to expand...
Click to collapse
I copied a SecureBootDebugPolicy.p7b (dated 02/13/2014 @ 3:19PM) file from there. From what I was reading, I take it that's a good thing? (click thumbnail for full pic)
SecureBootDebugPolicy in the certificate manager tool

what is the icon that next on the left of action center (bottom-right, triangle flag) and at the right side of OneDrive?

hisoft said:
what is the icon that next on the left of action center (bottom-right, triangle flag) and at the right side of OneDrive?
Click to expand...
Click to collapse
USB/SD eject (I have SD card I keep in the slot for extra storage)

thesawolf said:
USB/SD eject (I have SD card I keep in the slot for extra storage)
Click to expand...
Click to collapse
Good job ASUS :good:

If you were able to retrieve a SecureBootDebugPolicy.p7b that is functional, it probably means that there was a Debug policy on your device at some point? (ref. Original Thread on ASUS). I've just looked into my Surface RT and there's a file with that name too, but it cannot be opened (it's simply an empty 0-byte file) and probably you're another lucky one who has a debug policy. (However it can't be explained why Get-SecureBootPolicy shows that you're using a production policy? Does it show the production policy GUID that TechNet says is normal, or something else? Policies don't disable secure boot, Confirm-SecureBootPolicy showing true is perfectly normal even in debug.)
Would it be possible to share this SecureBootDebugPolicy.p7b and then we'd able to see if there is someone else with a VivoTab RT that could test it? I assume it's locked to your device but it's always worth a try.
Could anyone else with experience working with Secure Boot look into this? While it's probably a lucky isolated case, it's nevertheless promising...

Just to double check: does anybody else have a Vivo Tab RT with 8.1u1 they could check this against? It would be amazing / hilarious if the update disabled signature enforcement. The question would then be whether that was Microsoft's idea or Asus's...
Oh, and one other quick test: grab a built-in program (CMD.EXE or Notepad.EXE, for example) and make a copy of it to somewhere you can edit it (like the desktop). Open the file in a hex editor (if needed, copy it off the tablet first) and change something unimportant, like a few characters in a string (not a file path, more like "is not recognized as an internal or external command..." or some such thing) to some other value that has the same number of characters. Save the file and try running it on the tablet again. The idea is that this will be an EXE with an *invalid* signature (as opposed to just being unsigned) and that would be very surprising if it works... but this whole thing is surprising!

GoodDayToDie said:
Just to double check: does anybody else have a Vivo Tab RT with 8.1u1 they could check this against? It would be amazing / hilarious if the update disabled signature enforcement. The question would then be whether that was Microsoft's idea or Asus's...
Click to expand...
Click to collapse
Tried it on a VivoTab RT LTE (AT&T) with u1 -- ran 7z ARM and it failed on signature verification.

I would never run another update on that device. Don't want to patch up the botched update.
Sent from my Z10 using XDA Premium 4 mobile app

I wonder if there's some way to take a full image of your current installation (possibly using a backup utility?) that can be restored onto other peoples' tablets. Even better would be if the relevant bits could be extracted from your image and carried over to other tablets (such as Surface RTs, Surface 2s, Lumia 2520s, etc.) but that may be harder. Still, worth investigating more...

Was it new or used when you got it? And if it was used, is it possible the original owner JB'd it and it stuck through the update?
Sent from my HTC6600LVW using XDA Premium 4 mobile app

GoodDayToDie said:
I wonder if there's some way to take a full image of your current installation (possibly using a backup utility?) that can be restored onto other peoples' tablets. Even better would be if the relevant bits could be extracted from your image and carried over to other tablets (such as Surface RTs, Surface 2s, Lumia 2520s, etc.) but that may be harder. Still, worth investigating more...
Click to expand...
Click to collapse
Should be able to use dism.exe. Not sure if it will capture the online image, but you can definitely use it in recovery mode. Should be able to capture with new-windowsimage too. Going to try it out real quick and report back... I would choke puppies for this image.
---------- Post added at 11:24 AM ---------- Previous post was at 10:35 AM ----------
Okay it you can't capture the online image. You'll need to have a USB drive with enough space to capture the whole thing. Make sure you either suspend bitlocker or make sure you have a copy of the recovery key handy (It's 48 decimal digits).
Boot to the recovery partition (it doesn't matter if it's on the local storage or a USB key - it can even be the same USB key you will copy the disk image to if you have enough free space).
Choose language, troubleshoot, advanced, command prompt (I think - point is, you want a command prompt).
Verify the drive letters are what you expect them to be (internal storage is c, usb disk is d, ramdisk is x).
run: dism /capture-image /ImageFile:d:\winrt81u1.wim /CaptureDir:c:\ /Name:WinRT81U1vivotab
Let it finish. It will take a while. Probably a long time since it's writing to USB 2.0 flash storage. Bet on an hour. You probably want to make sure it's plugged in to power (but you're not writing anything to the local storage, so you won't break anything if it goes dead).
Upload that wim file to skydrive and share it with me!

Sjflowerhorn said:
Was it new or used when you got it? And if it was used, is it possible the original owner JB'd it and it stuck through the update?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That is impossible, the 8.0 jailbreak was performed in memory and it not written to the disk.

Toxickill said:
That is impossible, the 8.0 jailbreak was performed in memory and it not written to the disk.
Click to expand...
Click to collapse
Gotcha, I haven't JB'd mine yet, so I have no idea how it works. Apparently I'm Windows ShmeShmarted and can't make a bootable flash drive that contains the rollback. And coming from android devices where everything sticks except for some very select mods/devices I just figured it might be possible.
Sent from my HTC6600LVW using XDA Premium 4 mobile app

Sjflowerhorn said:
And coming from android devices where everything sticks except for some very select mods/devices I just figured it might be possible.
Click to expand...
Click to collapse
Believe me, that's what all RT owners would WANT to have. Although there's many reasons to jailbreak a device, I personally prefer feeling like I've gained full control of hardware I own. The in-memory jailbreak was good, but it didn't have that satisfying feeling of permanence you often get with an Android rooting / OS replacement.

southbird said:
Believe me, that's what all RT owners would WANT to have. Although there's many reasons to jailbreak a device, I personally prefer feeling like I've gained full control of hardware I own. The in-memory jailbreak was good, but it didn't have that satisfying feeling of permanence you often get with an Android rooting / OS replacement.
Click to expand...
Click to collapse
Until the carrier gets to your device and locks the bootloader (AT&T)

I actually preferred the in-memory jailbreak in many ways. It meant we couldn't modify system files or run unsigned code for a couple minutes after boot, but it also meant we could trivially easily "un-jailbreak" and we could install updates with no fear of them destroying anything. Even the huge 8.1 update, which broke the jailbreak *process*, could be started on a device which was already jailbroken without causing any harm (unlike, say, many iOS jailbreaks).

I agree. I liked that the 8.0 jailbreak wasn't permanent but also exceedingly simple to install at boot. It meant that sending my Surface RT back to my Microsoft under warranty had no problems at all.

Lumen_Melano said:
I agree. I liked that the 8.0 jailbreak wasn't permanent but also exceedingly simple to install at boot. It meant that sending my Surface RT back to my Microsoft under warranty had no problems at all.
Click to expand...
Click to collapse
The in-memory Jailbreak is great when you hard brick your Surface and take it to the Microsoft Store. They just gave me a new one with no problems at all.

Bosch Emulator On Jailbroken Windows 8.1 RT?

I've jailbroken my Surface 2 running Windows 8.1 RT and have started downloading and using apps, it's so much better, although I did think they'd install but they just run like portable apps, is that how it's supposed to be?
But that aside, my main query is what's the easiest way to achieve a full operating system on Windows RT? I've downloaded Bosch emulator because it's still being developed whereas QEmu isn't. I installed Bosch on my Surface and downloaded the Linux disk image from http://bochs.sourceforge.net/diskimages.html
Now from here how do I make the emulator run it? I've gone to the start menu, edited the 'Disk & Boot' option to enable ATA Channel 0, checked 'Enable this device' on First HD/CD on channel 0' and browsed to the downloaded .img file to input into the 'Path or physical device name'.
Then once I click Start I get a Panic popup with the message: couldn't open ROM image file'(null)/B....
Anybody else experienced this and have a way around it? I would have thought seeing as I downloaded the file from their website it would be fine.
If no-one has experienced this or has a fix, is there an easier way to emulate a full system?
Thank you

Jailbreak Windows RT on Surface? How?

Like this
banjax said:
Jailbreak Windows RT on Surface? How?
Click to expand...
Click to collapse
http://forum.xda-developers.com/win...ent/windows-8-1-rt-jailbreak-exploit-t3226835

Chuwi Hi10 Air Linux Installation Guide

Disclaimer: I got this device from the Manufacturer to test Linux on it. The below findings are my own and express my own opinion.
Specs and short review:
Intel Atom x5-Z8350 CPU (4x1,92 GHz)
Intel Integrated GPU
1920x1200 10.1" IPS Screen
4GB RAM
64GB Internal Storage
1 x USB C
1 x USB Micro B
1 x Mini HDMI
Bluetooth 4.2
2.4GHz WiFi
Rotation Sensor
Front and Back Camera
Mico SD Card slot up to 400GB (Website claims 64GB but I sucessfully tested it with an 128GB Card that uses the SDXC Standard)
Headphone Jack
Stereo Speakers
Keyboard Dock Support
Touchpen support
The Chuwi Hi10 Air is a compact 10.1" Tablet running a Windows 10. It has a sturdy Aluminium Body and the overall build quality is astonishing.
The speakers are surprisingly good for a tablet in that price segment. Paired with Bluetooth, a headphone jack and the 1920x1200 WUXGA display it's perfect for all kind of Media Playback. The battery is powerful enough to easily survive a few Movies. The optional detachable keyboard is a welcome addition for when you need to write some text.
The keyboard is nice to type on, but I had cases where it would send keys out of nowhere. I can't guarantee that's not caused by the few drops of water I accidentally spilled on the connection to the tablet at some point. I'm not a big fan of the trackpad, mainly because it's way to small to be usable for me but that might be because I am used to the trackpad on my 15" MacBook Pro.
The Touchpen is very accurate thanks to the digitizer, however the touchscreen does not send different signals for Pen and Finger to the System. That means trying to take notes while resting your hand on the screen doesn't really work.
Sadly, the full Windows 10 install user experience is really impacted by the entry level Intel Atom Z8350. It's just not powerful enough to accomplish any advanced tasks.
However, Chuwi sent me the device to bring linux to it, so that's what I did. This allows us to use lighter Window Managers and therefore more resources for actual tasks, resulting in a better performance.
Install Linux
First of all you need to install Linux on the tablet. That means you will erase your internal Windows installation, so make sure to either do a backup of it, or at least make yourself familiar with how to reinstall Windows in case it's needed.
Please note that you can NOT install Linux on an SDCard because the BIOS can not boot from the SDCard.
Backup
You can find the Hi10 Air Windows drivers here:
https://forum.chuwi.com/forum.php?mod=viewthread&tid=6861
And a guide here (applies for the Hi10 Air too):
https://forum.chuwi.com/forum.php?mod=viewthread&tid=15&page=7#pid29091
https://forum.chuwi.com/thread-15-1-1.html
Install
Next up, it's time to choose your Linux distro.
I recommend anything that is based on Arch Linux and that uses either LightDM or lxdm, because that is what my guide will be using to setup certain features. Of cause you're free to choosewhatever you want.
That means you could for example use Antergos, an ArchLinux based distro that includes Desktop managers (for Antergos I recommend XFCE), or go the hard way and install ArchLinux from scratch and use lxdm with LXQt. LXQt proved to me to be the best lightweight and yet High-DPI friendly Desktop Environment, so that's what I used.
I trust you will be able to find the guides on how to install either with a quick Google search, so I will not go much further into detail here.
To get into the boot menu, you need to press F7.
After your installation is done most things are already working.
Fixing Remaining Issues
Out of the box, there are a few issues and things that do not work because they are missing drivers or similar.
Automatic Rotation
We're getting started with the most important which is rotation.
As you'll need to enter a couple commands to get automatic rotation working, start off with manually rotating the screen by opening a terminal and run the command
Code:
xrandr -o left
Note: xrandr is part of xorg-xrandr, and you will need that package for autoration to work.
There are a couple solution on how to rotate the screen out there, however I decided to go for the one with least overhead that looked the cleanest to me.
First of all, compile the 2in1screen binary. The sourcecode can be found on my GitHub. Download, compile it and push it to /usr/local/bin.
Note: Make sure to install xorg-xrandr and xorg-xinput for this tool to work.
Code:
wget https://raw.githubusercontent.com/Myself5/Chuwi_Hi10_Air_Linux/master/2in1screen.c
gcc -O2 -o 2in1screen 2in1screen.c
sudo mv 2in1screen /usr/local/bin/
sudo chmod +x /usr/local/bin/2in1screen
Now configure the Desktop Manager to start it after login.
LXDE: add
Code:
/usr/local/bin/2in1screen &
to
Code:
/etc/lxdm/PostLogin
LightDM: Place the screenrotate.sh in /etc/lightdm/screenrotate.sh and set
Code:
display-setup-script
in
Code:
/etc/lightdm/lightdm.conf
to
Code:
display-setup-script /etc/lightdm/screenrotate.sh
screenrotate.sh
Code:
#!/bin/bash
pkill -9 2in1screen
/usr/bin/2in1screen &
Reboot and make sure everything works as desired.
Touchscreen
The Hi10 Airs Silead touchscreen requires drivers that are not bundled with a Linux install. You can download them here: https://github.com/onitake/gsl-firmware/tree/master/firmware/linux
See the Readme on how to install them.
These drivers get loaded by the Linux kernel. I submitted a commit to add support for the Hi10 Air to the Linux Kernel and it has been approved. The commit is merged in the 5.1 (and newer) Kernel. That means you need to update your kernel for a proper touch support.
If you previously used my Kernel you can go back to the official kernel by running:
Code:
sudo pacman -R linux-chewbacca linux-chewbacca-headers
sudo pacman -Syu linux linux-headers
sudo grub-mkconfig -o /boot/grub/grub.cfg
Now reboot and enjoy your touchscreen.
Audio
If your Audio isn't working, make sure to update the alsa-lib to Version 1.1.7 or above. On Arch that package is in the stable repos so a
Code:
sudo pacman -Syu
will be enough.
Bluetooth
Install blueman and follow the firmware instructions mentioned here:
https://github.com/lwfinger/rtl8723bs_bt/issues/28#issuecomment-432806835
Which means you need to clone https://github.com/lwfinger/rtl8723bs_bt
and run
Code:
sudo cp rtlbt_fw /usr/lib/firmware/rtl_bt/rtl8723bs_fw.bin
sudo cp rtlbt_config /usr/lib/firmware/rtl_bt/rtl8723bs_config.bin
cd /usr/lib/firmware/rtl_bt
sudo ln -s rtl8723bs_config.bin rtl8723bs_config-OBDA8723.bin
General UI
Now, you probably already noticed, everything is a bit small to use your Fingers.
As a browser I recommend Google Chrome as that has a great touchscreen UI already.
For File browsing and reading I suggest using nautilus and evince because of their touch friendlyness.
System DPI
For the whole system, there is a few things you can improve:
First of all, increase the general DPI.
You can do so by adding
Code:
Xft.dpi: 150
to
Code:
~/.Xresources
. If the file doesn't exist, create it.
LXQt Tweaks
Next up a few additional tweaks for LXQt:
First of all increase the Panel bar
Rightclick on the Panel and Press "Configure Panel". Then set the Size to 50px and the Icon Size to 30px.
Next up, Go to the Menu -> Preferences -> LXQt settings -> Appearance -> Font and set the DPI to 96
and finally go to Menu -> Preferences -> LXQt settings -> OpenBox Settings -> Font and increase the individual fonts to get a window title bar to drag/drop as well as hit the navigation with the finger. I set mine to Cantarell 16 and Cantarell 14.
Install OnBoard
Another Handy feature I found myself in need of was an onscreen keyboard. For that I installed OnBoard, and found a very neat feature here: https://bugs.launchpad.net/onboard/+bug/1232107
You can map a button to open/close the keyboard.
I set mine to Super L, which equals the left Windows button and the touch button on the tablet itself.
In the LXQt Settings Menu you can configure Shortcut Keys.
Create or edit the existing shortcut and either map the following DBus Call.
DBus Call:
Service:
Code:
org.onboard.Onboard
Path:
Code:
/org/onboard/Onboard/Keyboard
Interface:
Code:
org.onboard.Onboard.Keyboard
Method:
Code:
ToggleVisible
If your Desktop environment doesn't support DBus calls, use the following command:
Code:
dbus-send --type=method_call --dest=org.onboard.Onboard /org/onboard/Onboard/Keyboard org.onboard.Onboard.Keyboard.ToggleVisible

I got a Chinese manufactured pad-like device which is supported by the Linux mainline kernel and works pretty well except for the ****ty wifi chipset from Broadcom. That device has z8300 Soc and runs pretty well. I really like the On-The-Go device design as it is easy to carry around. Thanks for sharing!

Does this do a total partition wipe? Can you install to the Android partition and keep windows?

Droid_Nut said:
Does this do a total partition wipe? Can you install to the Android partition and keep windows?
Click to expand...
Click to collapse
The Hi10 Air is Windows only, there's no Android on it.
You could, however, resize the Windows Partition and install Linux alongside it. Generic Tutorials that float around the internet apply just fine here.
For Tablets that have Android and Windows like the Hi10 Plus, I don't quite know how the Android system is setup there. As far as I know you can remove Android entirely though, then you can just follow the procedure to resize Windows and Install Linux alongside.

I would love to get one of these units for review

Myself5 said:
The Hi10 Air is Windows only, there's no Android on it.
You could, however, resize the Windows Partition and install Linux alongside it. Generic Tutorials that float around the internet apply just fine here.
For Tablets that have Android and Windows like the Hi10 Plus, I don't quite know how the Android system is setup there. As far as I know you can remove Android entirely though, then you can just follow the procedure to resize Windows and Install Linux alongside.
Click to expand...
Click to collapse
Okay, I have the Chuwi hi10, dual boot Android and Windows 10. I will have to run live CD and run Gparted and take a look at the Partition Structure. I suppose I will be doing a total backup with Clonezilla before I do anything.

@Myself5 How's the battery life? And I guess, technically it's possible to install Android-x86 on it right?

Droid_Nut said:
Okay, I have the Chuwi hi10, dual boot Android and Windows 10. I will have to run live CD and run Gparted and take a look at the Partition Structure. I suppose I will be doing a total backup with Clonezilla before I do anything.
Click to expand...
Click to collapse
That sounds like a good plan. Clonezilla backup is what I went for too.
silv3rfox said:
@Myself5 How's the battery life? And I guess, technically it's possible to install Android-x86 on it right?
Click to expand...
Click to collapse
Battery life is great, i'd say better than Windows. Can't give you any numbers though because I didn't really pay attention to it yet.
Android-x86 is technically possible and with the Linux drivers even easier but I havn't looked into that yet.

Hey guys happy to see there is interest in this tablet. I do got the dualboot version too.
To install Android i found this:
jonathansblog. co.uk/ factory- restore- android- on- chuwi- hi10
After i personally Installed remix OS
konstakang.com /devices /chuwi_vi10plus /RemixOS/
When I installed Ubuntu, just Ubuntu Started, Android stuck, i found a solution here:
github.com /floe /tuxblet

I Just cant figure out this one:
Unfortunately, this still causes the Android install to hang on boot after Linux has been installed. I was assuming, for a very long time, that this is also an EFI-related problem. However, after multiple factory resets (see https://forum.chuwi.com/thread-2341-1-1.html and https://01.org/node/2463 for instructions), I finally found out that the problem is related to the very eager Ubuntu automounter, which grabs any ext4 filesystem it can find and mounts it read-write.
Of course, this shouldn't be a problem in theory, but this also happens for the Android system/data/etc. partitions, and whatever Ubuntu does to the ext4 FS when it's mounted, causes Android to croak. This means that even just booting a Ubuntu Live System from USB one single time will likely render the Android installation unbootable.
I've finally managed to fix this by setting the respective UUIDs to noauto in /etc/fstab as follows:
# do _not_ automount the Android partitions
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b1 /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b2 /none ext4 ro,noauto 0 0
UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b3 /none ext4 ro,noauto 0 0
If you look closely, you will notice that entries 2-4 are not actually proper UUIDs, they have an additional digit from 1-3 at the very end. The reason for this is that all the Android partitions (system, cache, data, config) have the same UUID and show up with the extra digit when the automounter grabs them. I'm not sure if this UUID duplication might actually be the root cause...
Unfortunately he does not explain how to no auto mount this partitions without a live CD and / or it is going to work even if Ubuntu installed is.

Hi everybody
Did kernel 5.1 resolve any problem. I use mint 19 but it seems that nothing happened

nikmag said:
Hi everybody
Did kernel 5.1 resolve any problem. I use mint 19 but it seems that nothing happened
Click to expand...
Click to collapse
5.1 includes the touchscreen fix on it's own so you don't need to use the kernel I provided anymore.

Thanks for your reply. I had 5.09 and I installed 5.1 but no touchscreen activation. I had to return to 5.09. Any update for Bluetooth drivers? I installed them manual, it seems to be active but cannot see any Bluetooth device . Also the problem with the bios or boot screen is always in vertical position and not touchscreen or other way to select OS. I use windows 10 and Mint 19.1 Thanks again.

nikmag said:
Thanks for your reply. I had 5.09 and I installed 5.1 but no touchscreen activation. I had to return to 5.09. Any update for Bluetooth drivers? I installed them manual, it seems to be active but cannot see any Bluetooth device . Also the problem with the bios or boot screen is always in vertical position and not touchscreen or other way to select OS. I use windows 10 and Mint 19.1 Thanks again.
Click to expand...
Click to collapse
So it does work with my 5.09 kernel though, right? Otherwise you'd have forgotten to install the touch drivers (see the OP on how to do that).
Bluetooth works flawless for me on Arch. Maybe Mint has some other packages that don't fully work with the chip yet?
As for Grub: there's nothing we can do about that. As it currently stands grub has no support for touchscreens or screen rotation. You could try different UEFIs (rEFInd comes to mind here) but other than that it's not possible. I thought about possibly mapping the volume buttons to up/down for selection, but that would still leave us without an enter key.
Although, now that I think about it again: it might be possible to register the windows touchkey as "enter". I guess I'll take a look into that

Actually I did not use your 5.09 kernel. I had already done a successful procedure with different kernels before reading your post. Yes probably is Mint issue. I need to find some time to install Arch. If you manage to do something with buttons it will be wonderful. I boot to Mint and then with a command a switch to win10. Are you pleased with the active pen? I really thank you for your support. I would also like to help if I can.

nikmag said:
Actually I did not use your 5.09 kernel. I had already done a successful procedure with different kernels before reading your post. Yes probably is Mint issue. I need to find some time to install Arch. If you manage to do something with buttons it will be wonderful. I boot to Mint and then with a command a switch to win10. Are you pleased with the active pen? I really thank you for your support. I would also like to help if I can.
Click to expand...
Click to collapse
According to a quick Google search custom keymapping for grub seems to be harder than expected. rEFInd seems to have touch support for some tablets though. I might look into that instead.
The "active Pen" on Windows is useless because it's not "active". It does get prefered over your hand, but the Hi10 Air doesn't have proper pen support. So the 256 pressure level touchpen they sell you is effectively as good as your finger. There is no pressure sensitivity support. On Linux this get's even worse because the pen is apparently using a different kind of calibration, so if you use it it's horribly offset. I was looking to use it for Notes during lectures, which is impossible to do. Even on Windows it's just not working. I've been in contact with my contact at Chuwi (who also sent me the device) and he just kept on talking around the topic. He never officially claimed the Pen would be supported but also never denied it. All he did was keep on sending me different touch drivers to "make the pen work" (although the definition of the term "work" can mean everything here).
TL;DR: Not pleased AT ALL.
P.S: I just updated the OP. the 5.1 kernel is released and works flawless on my Hi10 Air.

Hey everyone.
Can't make touchscreen work even on 5.1.2
see some screenshots:
https://imgur.com/598zrHM
kernel version:
https://imgur.com/qGtHJoc

heenry20 said:
Hey everyone.
Can't make touchscreen work even on 5.1.2
see some screenshots:
https://imgur.com/598zrHM
kernel version:
https://imgur.com/qGtHJoc
Click to expand...
Click to collapse
So which tablet do you have? A normal Hi10 Air?

Myself5 said:
So which tablet do you have? A normal Hi10 Air?
Click to expand...
Click to collapse
Yes, running kde neon.

M5 you are right, the finger is much better than 'active' pen! I bought also nebo app for recognition but the pen is totally invisible. Probably you checked drivers from you know https://forum.chuwi.com/thread-6861-1-1.html. It will be a big help if you manage to do something with rEFInd . Thanks