360 ta var. Sen kenar sınırı olanı seçmişsinBut there is no 360 degree touch feature on tincore so when the cursor reaches the edge of the screen you cant move your aim.
360 ta var. Sen kenar sınırı olanı seçmişsinBut there is no 360 degree touch feature on tincore so when the cursor reaches the edge of the screen you cant move your aim.
For me, it closes itself with errorHere are the steps to activate shooting mode
I also attached sample configs which you can learn from
![]()
you can import these through tincore keymapper
↓↓sample configs which you can learn from. ↓↓
After installation, it worked but when I reopened it, it's getting closed... I reinstalled but same problem.360 ta var. Sen kenar sınırı olanı seçmişsin![]()
choose touch area re-enter, i have 360 aim using that optionBut there is no 360 degree touch feature on tincore so when the cursor reaches the edge of the screen you cant move your aim.
Changelogs
- Now your internal laptop keyboard will be detected and is usable! (Credits to @İlhan )
- Set GearLock min-compat version to 7.1.1
- The bug of GearLock be removing "lib64" directory is now resolved.
Bugfix
- internal keyboard won't work (re-patch)
Try supercharging from gearlockIs there any way to set ''keyboard mode'' on games Androidx86 7 r4 32bits without Panda or Octopus? I need because in Toram Online the touch only work if ''Keyboard mode'' is on, and this extension didnot work for me Panda still show ''need activate'' and Toram detect Octopus like a hack.
When i load the extension that scripts just be empty
pasteboard.co/JLZ4EZ0.png
And i dont know if this happens only to me, when i install Gearlock it dont unpack the system.sfs to a folder it just make a system.img and dont install Panda by himself
Same problem mate. I am waiting for @AXON 's reply.I try to install on Android x86 7.1 r5 but after install and reboot is not installing the app why ?
I try to install on Android x86 7.1 r5 but after install and reboot is not installing the app why ?
It seems to be a common problem...Same problem mate. I am waiting for @AXON 's reply.
/gearlock/tmp/gearboot*
log files to get some idea of what's being wrong.