|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000378||Cheat Engine||(No Category)||public||2015-03-01 00:50||2015-03-01 00:50|
|Platform||Android Emulator (Andy)||OS||Android 4.2.2 (rooted)||OS Version||x86_32|
|Summary||0000378: [ceserver] CE client frequently unresponsive in Windows after connecting.|
|Description||Problem: The CE client is generally unresponsive after connecting to the ceserver on android. |
Running the emulator using: Windows 8.1 x64, 6GB RAM, 2GHZ AMD QuadCore APU. CPU and RAM usage both average 50%.
The ceserver and client (for 32bit android) obtained from:
|Steps To Reproduce||1 - Replaced cheatengine-x86_64 executable in CE 6.4 installation directory with the one provided in rar file.|
2 - Transfered ceserver and libceserver-extension.so to emulator's system/xbin and maximized permissions as root (777).
3 - Executed ceserver binary as root in terminal emulator on android. ceserver waits for client connection.
4 - Launched provided cheatengine-x86_64 and open process list and can see the server correctly listed in network list.
5 - Connected to server. At this point, the CE client becomes frequently unresponsive as errors appear looping within the android terminal.
|Additional Information||Is this normal? This did not happen with the version (although lacking in features) compiled by CEF user greyman. |
It happens immediately after connecting. The client still works (scanning, memory viewing etc.), but is unusable due to the overall slow and non-neglible unresponsiveness that makes it hard to navigate and make changes using CE (In other words, it's like a bad case of FPS lag).
Ironically, giving the VM more CPUs makes the problem worse for the CE client as the frequency at which it is unresponsive increases.
|Tags||No tags attached.|
|2015-03-01 00:50||Kyokyonos||New Issue|
|2015-03-01 00:50||Kyokyonos||File Added: Capture.PNG|