Gt9xx 1085x600 Repack Verified -

Search the "Android General" or "Legacy & Low-Active Devices" sections. Many developers repack Goodix drivers for custom AOSP or LineageOS builds.

Many cheap tablets use MIPI DSI displays with GT9xx touch controllers.
But firmware for these tablets is often leaked, incomplete, or mismatched — e.g., a ROM built for a GT911 touch panel flashed onto a tablet with a GT928. gt9xx 1085x600 repack verified

Result:

Why 1085×600?
Because some kernels report the virtual framebuffer size (including hidden regions) as 1085×600 instead of physical 1024×600. The GT9xx driver expects the physical resolution. Mismatch → touch failure. Search the "Android General" or "Legacy & Low-Active

Even with a "verified" repack, problems can occur due to hardware variances. Why 1085×600

| Symptom | Likely Cause | Solution | | :--- | :--- | :--- | | No touch response at all | Wrong firmware for the GT9XX variant (GT911 vs GT928 have different register maps). | Find a repack specifically for your chip ID. Check dmesg for "Goodix ID". | | X and Y axes swapped | Orientation flag set incorrectly in the repack. | Use a hex editor to modify the repack’s byte at offset 0x15 (rotate flag). Change 0x00 to 0x01 or vice versa. | | Touch jumps or lags | Incorrect refresh rate or filter settings in the config array. | Look for a repack with "filter" or "noise" verified tags. Lower the sensitivity in the config. | | Edges are dead (5mm margin) | The 1085x600 config is using an older coordinate mapping algorithm. | Manually edit the config array’s X_Max and Y_Min/Y_Max registers. Increase by 5-10 units. |

“My Eken T90 tablet (Allwinner A33) touch died after flashing a generic ROM. dmesg showed gt9xx init fail: resolution 1085×600 not supported. User ‘bR0ken’ posted a repacked gt9xx.ko with patched resolution check. Flashed via ADB, set permissions 644, reboot — touch works again. Confirmed working by 12 users.”