I was trying to improve my touchscreen and especially stylus performance, and found a HiPen update here on the forums (DON’T DO IT). It installed fine but was obviously incompatible with the Minibook X and now the touch is mis-aligned, mirrored, and has deadzones. These settings live on the touch controller, so re-installing windows or drivers doesn’t help.
Chuwi is so far unable to find the correct file that would fix this, so I wrote a small program that can read these settings from a properly setup Minibook X, and I could then use it to fix my device. Just need to run the app and copy the data that it prints out (click and drag to select, Enter to copy). If there are many 0x00s or there’s an error, try running it a few times. This happens rarely.
I know that running some program made by a stranger on the internet is a big ask but you can check the forum here that I’ve been posting about the Minibook X for some time, so this really isn’t a long-planned scam Your help would be really appreciated, this is my only hope for fixing the Minibook
You’re a hero! Not too late at all (unfortunately, lol), thanks a lot!
I’m almost there. I don’t know if something changed due to Windows or driver update (or I messed up during testing) but it didn’t work quite right and it’s missing the last 20 or so values. It worked perfectly for me 90% of the time but now I always get the same results as you
I might be able to figure it out eventually but if it’s not too difficult, could you try this new version? I added some delays which seem to fix it, and made the output clearer.
All the stuff below isn’t really important, just some background information for curiosity or anyone else who runs into this issue later.
I tried combining your configuration with the ending of mine, but it’s not recognized - the last value is a checksum that is calculated based on the rest of the file to verify it’s not “corrupted”, so I’d have to find how it’s calculated somehow.
Not sure what exactly went wrong here. The configuration is split into 65-byte chunks. The first 5 are a header, 3 of them aren’t important. Then it tells you the batch #, and how much actual data it has (3C is the maximum 60, 0F is 15). It moves to a different location after batch 0x04 so it resets the count.
But in the highlighted row instead of going to batch 3, it goes to 0 again, and the data also repeats from the beginning. This cuts off the end of the configuration.
While I was waiting for a response, I tried another way. There’s a tool called GTP (GuitarTestPlatform ??? ) that lets you change the settings of the touchscreen directly (after installing an unsigned driver).
Unfortunately there’s like a million settings and almost no explanation or documentation, so it’s not going very well. I was only able to fix the flipped axis. So the situation is like this now. The screen is divided into 4 sectors (with some dead zones), and a touch on one of them is detected as being on the one to the left/right of it. They grey deadzones interrupt the touch movement.
As I understood, the screen has a number of “drivers” along one edge, each of which has a bunch of “sensors”, creating a grid. So for example you could invert the response if you put them in the opposite order. And this worked! But it will not let me swap the two groups of Sensors (everything before Sensor_CH26) with those after. This would theoretically fix my main issue.
Of course there would be other problems with the deadzones and even worse, random false touches. Sometimes the screen just goes nuts and starts detecting touches at random points, which makes it almost impossible to even revert back. So it’s pretty dangerous.
Anyway, the tool is quite difficult to find, so here’s a copy a former poster here shared. Again, don’t use it if your touchscreen works fine, you’ll only make it worse probably
Yes it does! Thank you!!! I can paypal you like ten bucks if you want, just send me a PM.
For some reason I had to change the output resolution to what was in my config, otherwise it didn’t map correctly to the screen coordinates. But now it works exactly like it did before. So not great, but at least it works!
The reason I tried to install the stupid update in the first place is that the stylus was really bad at making small circles especially if you did them at normal speed. On the right is how it was stock (and now). After the bad update, the diagonal jitter is still about the same, but the circular shapes are much better (my handwriting just sucks).
Does it work the same for you? Which stylus are you using? I had the Hipen H6 from my mom’s Ubook so that could be the reason, but I don’t want to spend another $40 on the H7 to find out it’s the same.
Of course now I have the two versions, I could compare them to find out the difference, but I probably won’t have much time soon because of work.
So, if someone installed the wrong update as well, here’s the stock configuration for the Minibook X Goodix 7382 Touchscreen controller. You’ll know what to do with it
Haha I lied, I couldn’t let it go! Thankfully it turned out to be super easy.
The configuration has settings for the stylus, and with the GTP tool you can see them on one of the tabs. Even after just a quick look, it’s clear that the stock settings have much higher values for various filters, which I assumed correspond to stronger smoothing/filtering.
I just copied all the values (except for tilt, I don’t think tilt works anyway?) from the updated settings to Jagosz’s configuration, and that did the trick.
As you can see from the small sample, the letters now have normal shapes, or as normal as I can make them. The default settings were trying to smooth out the inputs way too much for some reason. I don’t know if it had the same effect for everyone, but for me it made writing normal sized text almost impossible.
Right now I’m very happy with it. Other than slightly worse diagonal jitter, I’d say it feels about the same as the pen on X1 Yoga (it would be great to store the stylus inside the laptop!). Maybe still not as natural as the Wacom EMR tablet / S-Pen, but I’m not a real artist so it’s good enough.
Wow, awesome job! I have bought RENAISSER 520C, which is supposedly a really good pen, but it was so bad on the Minibook X i stopped doing any handwritten notes. It is so much worse than Wacom EMR I was using before, completely unusable for handwriting in my opinion. Oh and on Linux it actually is even slightly worse than on Windows, like if polling was even lower or smoothing even higher.
So if it works reliably for you for a few days I would really want to mod mine too, so the pen becomes actually usable.
@mobby Could you describe in short how change and flash it myself?
I want to try to change some of the settings you did to try and see if it helps.
I totally understand the risks, but the stylus input right now is unusable for my handwriting.
What is the program you showed in those screenshots?
In your case it seems that the resolution was for some reason different than on my Minibook, so I wouldn’t suggest using my file directly. I think the simplest way would be:
Open the “a_JacekJagosz_original” file with the GTP tool. This is exactly the settings you gave me earlier.
Change the filtering settings (as on the screenshot) and save it to a new file
Use the “hid_i2c_update” tool to flash the new configuration
This is exactly what I did at the end: used your file, changed the resolution and filtering, and then uploaded it. The upside is that you don’t have to install/uninstall drivers. This worked perfectly for me, but I can’t guarantee it
Disclaimer for anyone else brave enough to try it: Following this could make your touchscreen or even the whole laptop useless. It involves updating data on the touchscreen controller chip, and no Windows or driver re-installations will fix it if something goes wrong.
There are two options overall:
The GTP software, it has GUI but requires installing unsigned drivers. Another downside is that the touchscreen stops working with these drivers (until you restore them) so it’s more difficult to test.
Use my tool to make a backup of your settings, then use Chuwi/Goodix? Tool to update the configuration. No drivers to install but it’s all command line
For the first option, download the zip file and see the powerpoint with instructions inside. It already existed, I just added some slides. The general process is
Install drivers
Use the tool to read your current settings and back up to file
Make the changes in the tool, or load one of our settings from the file
Upload the new settings to the controller
Uninstall drivers
For option two:
Run the HID_Dumper and copy the output to a text file. It should look like above, and have 444 bytes. To make a valid config file, you’ll have to manually copy the appropriate number of bytes from each batch (should be 60, 15 or 5) after skipping the first 5, separated by commas.
You can try one of our files. Or, open your backup with the GTP tool (no drivers needed, just make sure to set to the 7382/5 model first), make changes as you want, and save it. This will also confirm if the config file is correct, otherwise it will give you an error.
Run the command “hid_i2c_update-20180419.exe -d -p name_of_config.txt” This will update the configuration while printing more information about what is happening. If you see errors, you can try running it again.
Thank you a ton, once my Minibook X comes back from warranty I will get onto it.
This laptop is so nice on one hand, and so unreliable from the other, this time SSD died, all my data lost. Probably from the heat of no active cooling.
No way, I used my previous config as a base, just input your settings and it is SO MUCH better! Now the stylus is actually usable for handwriting, thank you so much!
For future reference I used my config as a base that was included in the download, opened the tool and CFG edit in it, didn’t have to change the device type, just changed the values and saved it.
The update script didn’t work on 2 first tries, but after a reboot it finally did.
Awesome, really glad it worked for you! It’s just such a bizarre issue that made the pen almost completely useless because of a few settings.
I’m not 100% sure if changing the model is necessary, I noticed that for certain models some pages in the settings are just missing, but if it doesn’t wipe out those values then it should be still fine.
We probably talked about this in another thread, but the Minibook X refresh is still not out, they announced it in November-December. I hope it’ll be updated with the new processors, it’s like 60% faster which would be a huge update: https://browser.geekbench.com/v5/cpu/compare/19709299?baseline=18508547
I just think the default one when you open the software is correct, for me it was GT7385P. When I set it to GT7385 the settings looked completely different to what you showed in a screenshot, meanwhile with the default they looked exactly the same as what you showed. So I went back to the default.
As for the Minibook X upgrade, the CPU performance was not a problem for me on Linux, on Windows it can be sluggish, but on Linux it actually flies. I even set the CPU Governor to maximum power saving and it still is fast.
I more hope they fix the reliability woes, mine came back from the second warranty repair, I really hope it will stay working from now on, but I doubt it. I guess the SSD failed from too much heat, so active cooling might help with that, but the keyboard, stylus, actually using locktite on the screws mounting the screen so it doesn’t fall off, all need to be adressed. And that still leaves the too small battery
Hmm, maybe it’s something I changed in the GTP settings, the important thing is that it worked
I’m afraid the SSDs in these budget devices are the cheapest stuff possible. The only SSD that failed for me was also in a cheap Cube Mix Plus tablet. So it’s better to have backups and/or replace it with Samsung or something.
I checked the temperature and it’s not even updating correctly, it’s always showing 40C lol.
Tried with a thermal camera and the controller is around 54 degrees and the flash chips probably around 40, even when not doing heavy read/write. It might be worth putting some thermal pads on it but it’s hard to test without a working temperature sensor.
Glad it was useful for someone else, thanks for sharing!
Pretty shocking that this is still happening with a completely different model. I guess there’s a step to update this configuration to the correct one and it usually works, but based on my experience, sometimes the config update process just randmoly fails and they don’t catch it.
Your help would be really appreciated, this is my only hope for fixing the Minibook 
