Search the Community

Not always. Lets say: -the game has a lot of small levels. -you can't use the currency you gain in game mode. Lets say level has 10 battles that might give You currency. Initial scan would be unknown. If You get a battle with no currency gain then You do get rid of counter values. Means You do need to find the value with max of 11 scans. You can't use specific scan and initial scan being unknown won't allow you to get rid of enough values to make it possible to find the right one. Lets say You get lucky few times and You do get the AoB with correct wildcards. You still aren't able to find the value easily later on since You can't scan for array of bytes.

There are literally unlimited ways they can make you not find the values. For example RPG Maker games use "(2x value)+1" to store their values. I have seen games that have used "value +255" or " 4,294,967,295 - value" They can just store visual value for You to step on. Lets say you have variable "visual_gold" and "real_gold". visual_gold would be just a calculated field that would there for You to see for example "visual_gold=real_gold/10". All other (real calculations) would be done using real_gold value itself and You changing the visual_gold value wouldn't do anything for you. (Can be used to flag Your save file as cheater and make the game a lot harder for You just because You changed virtual value just once) With gg there isn't any way to find such values hidden by means of Increment or decrement. If as You say game got patched and You can't find values anymore. Array of Byte scan would easily give You new value if they haven't changed the base structure of the object at hand (they usually never chage structure just to prevent hacking).

Same here. Since the last update, GGuardian finds about 10-15 numbers for example for the search 920 (ammount of gold you need to buy crate packs[Float]) instead of 100-200 lines. You can modify them, but none of them works. And if you start a new search, the GGuardians finds new lines again (You can repeat it forever. No real result) I think, they made a cheatsafe client.

Speedhack will crash the app. And show alert "Operation not permitted". Same as first posted. 2016-01-13-10-21-16.txt

I ran ps in terminal command and this is what I got u22_a243@Lenovo:/ $ ps USER PID PPID VSIZE RSS WCHAN PC NAME root 1 0 1272 956 ffffffff 00000000 S /init root 2 0 0 0 ffffffff 00000000 S kthreadd root 3 2 0 0 ffffffff 00000000 S ksoftirqd/0 root 5 2 0 0 ffffffff 00000000 S kworker/0:0H root 6 2 0 0 ffffffff 00000000 D kworker/u8:0 root 7 2 0 0 ffffffff 00000000 S migration/0 root 8 2 0 0 ffffffff 00000000 S rcu_preempt root 9 2 0 0 ffffffff 00000000 S rcu_bh root 10 2 0 0 ffffffff 00000000 S rcu_sched root 11 2 0 0 ffffffff 00000000 S migration/1 root 12 2 0 0 ffffffff 00000000 S ksoftirqd/1 root 14 2 0 0 ffffffff 00000000 S kworker/1:0H root 15 2 0 0 ffffffff 00000000 S migration/2 root 16 2 0 0 ffffffff 00000000 S ksoftirqd/2 root 18 2 0 0 ffffffff 00000000 S kworker/2:0H root 19 2 0 0 ffffffff 00000000 S migration/3 root 20 2 0 0 ffffffff 00000000 S ksoftirqd/3 root 22 2 0 0 ffffffff 00000000 S kworker/3:0H root 23 2 0 0 ffffffff 00000000 S khelper root 24 2 0 0 ffffffff 00000000 S netns root 29 2 0 0 ffffffff 00000000 S kworker/0:1H root 30 2 0 0 ffffffff 00000000 S smd_channel_clo root 31 2 0 0 ffffffff 00000000 S smsm_cb_wqroot 33 2 0 0 ffffffff 00000000 D kworker/u9:0 root 34 2 0 0 ffffffff 00000000 S rpm-smd root 35 2 0 0 ffffffff 00000000 S kworker/u9:1 root 36 2 0 0 ffffffff 00000000 S irq/47-cprroot 37 2 0 0 ffffffff 00000000 S deferwq root 38 2 0 0 ffffffff 00000000 S mpm root 59 2 0 0 ffffffff 00000000 S writeback root 60 2 0 0 ffffffff 00000000 S bioset root 61 2 0 0 ffffffff 00000000 S crypto root 62 2 0 0 ffffffff 00000000 S kblockd root 63 2 0 0 ffffffff 00000000 S khubd root 64 2 0 0 ffffffff 00000000 S system root 65 2 0 0 ffffffff 00000000 S irq/75-msm_iomm root 66 2 0 0 ffffffff 00000000 S irq/75-msm_iomm root 67 2 0 0 ffffffff 00000000 S irq/273-msm_iom root 68 2 0 0 ffffffff 00000000 S irq/274-msm_iom root 69 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 70 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 71 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 72 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 73 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 74 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 75 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 76 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 77 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 78 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 79 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 80 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 81 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 82 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 83 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 84 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 85 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 86 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 87 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 88 2 0 0 ffffffff 00000000 S irq/102-msm_iom root 89 2 0 0 ffffffff 00000000 S devfreq_wqroot 90 2 0 0 ffffffff 00000000 S cfg80211 root 91 2 0 0 ffffffff 00000000 S kswapd0 root 92 2 0 0 ffffffff 00000000 S fsnotify_mark root 93 2 0 0 ffffffff 00000000 S cifsiod root 112 2 0 0 ffffffff 00000000 D mdss_dsi_event root 113 2 0 0 ffffffff 00000000 S apr_driverroot 114 2 0 0 ffffffff 00000000 S pil_vote_wq root 115 2 0 0 ffffffff 00000000 S mem_share_svc root 116 2 0 0 ffffffff 00000000 S qmi_hndl0000000 root 117 2 0 0 ffffffff 00000000 S msm_ipc_router root 118 2 0 0 ffffffff 00000000 S hwrng root 119 2 0 0 ffffffff 00000000 S diag_real_time_ root 120 2 0 0 ffffffff 00000000 S diag_modem_data root 121 2 0 0 ffffffff 00000000 S diag_lpass_data root 122 2 0 0 ffffffff 00000000 S diag_wcnss_data root 123 2 0 0 ffffffff 00000000 S diag_sensors_da root 124 2 0 0 ffffffff 00000000 S diag_wq root 125 2 0 0 ffffffff 00000000 S DIAG_USB_diag root 126 2 0 0 ffffffff 00000000 S diag_cntl_wq root 127 2 0 0 ffffffff 00000000 S diag_dci_wq root 128 2 0 0 ffffffff 00000000 S kgsl-3d0 root 129 2 0 0 ffffffff 00000000 S kgsl-events root 130 2 0 0 ffffffff 00000000 S governor_msm_ad root 131 2 0 0 ffffffff 00000000 S kgsl_devfreq_wq root 132 2 0 0 ffffffff 00000000 S proximity_als root 133 2 0 0 ffffffff 00000000 S spi0 root 136 2 0 0 ffffffff 00000000 S usbnet root 137 2 0 0 ffffffff 00000000 S sharedmem_qmi_w root 138 2 0 0 ffffffff 00000000 S qmi_hndl0000000 root 140 2 0 0 ffffffff 00000000 S k_gserial root 141 2 0 0 ffffffff 00000000 S uether root 142 2 0 0 ffffffff 00000000 S irq/328-ft5x06_ root 143 2 0 0 ffffffff 00000000 S sns_akm root 144 2 0 0 ffffffff 00000000 S elan_sensor_wq root 147 2 0 0 ffffffff 00000000 S msm_cpp_workque root 148 2 0 0 ffffffff 00000000 S dm_bufio_cache root 149 2 0 0 ffffffff 00000000 S cfinteractive root 150 2 0 0 ffffffff 00000000 S irq/170-7824900 root 151 2 0 0 ffffffff 00000000 S irq/253-7864900 root 172 2 0 0 ffffffff 00000000 S binder root 173 2 0 0 ffffffff 00000000 S usb_bam_wqroot 174 2 0 0 ffffffff 00000000 S krfcommd root 176 2 0 0 ffffffff 00000000 S irq/460-wcnss root 177 2 0 0 ffffffff 00000000 S irq/428-modem root 178 2 0 0 ffffffff 00000000 S msm_vidc_worker root 179 2 0 0 ffffffff 00000000 S pm_workerq_venu root 180 2 0 0 ffffffff 00000000 S mmcqd/0 root 181 2 0 0 ffffffff 00000000 S mmcqd/0rpmb root 182 2 0 0 ffffffff 00000000 S irq/309-fifo_up root 183 2 0 0 ffffffff 00000000 S irq/310-fsm_sta root 184 2 0 0 ffffffff 00000000 S mmcqd/1 root 185 2 0 0 ffffffff 00000000 S irq/298-fastchg root 188 2 0 0 ffffffff 00000000 S irq/301-batt_pr root 189 2 0 0 ffffffff 00000000 S rq_stats root 190 2 0 0 ffffffff 00000000 S bam_dmux_rx root 191 2 0 0 ffffffff 00000000 S bam_dmux_tx root 192 2 0 0 ffffffff 00000000 S k_bam_dataroot 193 2 0 0 ffffffff 00000000 S f_mtp root 194 2 0 0 ffffffff 00000000 S file-storage root 195 2 0 0 ffffffff 00000000 S msm_thermal:hot root 196 2 0 0 ffffffff 00000000 S msm_thermal:fre root 197 2 0 0 ffffffff 00000000 S msm_thermal:the root 198 1 972 576 ffffffff 00000000 S /sbin/ueventd root 200 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p23 root 201 2 0 0 ffffffff 00000000 S ext4-dio-unwrit root 205 2 0 0 ffffffff 00000000 S kworker/1:1H root 206 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p30 root 207 2 0 0 ffffffff 00000000 S ext4-dio-unwrit root 211 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p25 root 212 2 0 0 ffffffff 00000000 S ext4-dio-unwrit root 213 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p24 root 214 2 0 0 ffffffff 00000000 S ext4-dio-unwrit root 217 2 0 0 ffffffff 00000000 S kworker/2:1H root 251 2 0 0 ffffffff 00000000 S IPCRTR root 252 2 0 0 ffffffff 00000000 S modem_IPCRTR logd 253 1 9096 2576 ffffffff 00000000 S /system/bin/logd root 254 1 1672 172 ffffffff 00000000 S /sbin/healthd root 255 1 2348 500 ffffffff 00000000 S /system/bin/lmkd system 256 1 1616 544 ffffffff 00000000 S /system/bin/servicemanager root 257 1 5804 880 ffffffff 00000000 S /system/bin/vold system 258 1 96644 7536 ffffffff 00000000 S /system/bin/surfaceflinger nobody 259 1 6892 544 ffffffff 00000000 S /system/bin/rmt_storage system 260 1 3228 540 ffffffff 00000000 S /system/bin/rfs_access system 262 1 2928 520 ffffffff 00000000 S /system/bin/qseecomd system 263 1 1820 496 ffffffff 00000000 S /system/bin/vm_bms shell 266 1 1520 360 ffffffff 00000000 S /system/bin/sh audit 267 1 1320 468 ffffffff 00000000 S /system/bin/auditd root 268 1 14004 3072 ffffffff 00000000 S /system/bin/netd root 269 1 1516 436 ffffffff 00000000 S /system/bin/.krsh root 270 1 248 28 ffffffff 00000000 S /system/bin/debuggerd64 radio 271 1 33144 3416 ffffffff 00000000 S /system/bin/rild drm 272 1 13680 1528 ffffffff 00000000 S /system/bin/drmserver media 273 1 85836 21360 ffffffff 00000000 S /system/bin/mediaserver install 274 1 1532 592 ffffffff 00000000 S /system/bin/installd radio 277 1 12884 324 ffffffff 00000000 S /system/bin/qmuxd radio 278 1 12872 1208 ffffffff 00000000 S /system/bin/netmgrd radio 279 1 33104 2836 ffffffff 00000000 S /system/bin/rild root 280 1 33200 700 ffffffff 00000000 S /system/bin/thermal-engine system 281 1 4512 720 ffffffff 00000000 S /system/bin/wcnss_service root 282 1 936352 22844 ffffffff 00000000 S zygote camera 283 1 14136 2328 ffffffff 00000000 S /system/bin/mm-qcamera-daemon system 284 1 7404 708 ffffffff 00000000 S /system/bin/time_daemon system 285 1 10312 1108 ffffffff 00000000 S /system/bin/audiod media_rw 286 1 5184 2288 ffffffff 00000000 S /system/bin/sdcard system 287 1 6032 964 ffffffff 00000000 S /system/bin/cnd root 288 1 4852 720 ffffffff 00000000 S /system/bin/dpmd root 302 1 252 32 ffffffff 00000000 S /system/bin/debuggerd64 root 312 2 0 0 ffffffff 00000000 S kauditd system 313 1 5576 700 ffffffff 00000000 S /system/bin/mm-pp-daemon system 325 262 7164 508 ffffffff 00000000 S /system/bin/qseecomd root 327 1 3424 472 ffffffff 00000000 S /system/bin/perfd root 333 2 0 0 ffffffff 00000000 S irq/318-mbhc sw root 334 2 0 0 ffffffff 00000000 S irq/316-Button root 335 2 0 0 ffffffff 00000000 S irq/315-Button root 336 2 0 0 ffffffff 00000000 S irq/314-Elect I root 337 2 0 0 ffffffff 00000000 S irq/317-Elect R root 338 2 0 0 ffffffff 00000000 S irq/321-HPH_L O root 339 2 0 0 ffffffff 00000000 S irq/320-HPH_R O root 341 2 0 0 ffffffff 00000000 S kworker/3:1H root 360 1 428 72 ffffffff 00000000 S /system/xbin/ku.sud system 379 288 6980 968 ffffffff 00000000 S /system/bin/dpmd root 381 1 444 124 ffffffff 00000000 S /system/xbin/ku.sud root 448 1 428 144 ffffffff 00000000 S kuInotify root 688 269 2032 828 ffffffff 00000000 S /system/bin/debuggerd_real system 790 282 1178096 138632 ffffffff 00000000 S system_server keystore 958 1 4332 824 ffffffff 00000000 S /system/bin/keystore root 2140 2 0 0 ffffffff 00000000 S IPCRTR root 2142 2 0 0 ffffffff 00000000 S wcnss_IPCRTR root 3147 2 0 0 ffffffff 00000000 S kworker/0:2 u22_a19 3486 282 956116 26880 ffffffff 00000000 S com.google.process.gapps u0_a74 4289 282 1086192 71212 ffffffff 00000000 S com.touchtype.swiftkey system 4412 282 978004 28504 ffffffff 00000000 S com.quicinc.cne.CNEService system 4436 282 972256 25664 ffffffff 00000000 S org.mokee.services u0_a6 4494 282 972328 25696 ffffffff 00000000 S com.android.incallui u0_a63 4530 282 973708 25740 ffffffff 00000000 S com.atmos radio 4560 282 1044948 45992 ffffffff 00000000 S com.android.phone u0_a11 4585 282 1019688 71968 ffffffff 00000000 S com.mokee.launcher root 4593 1 260 60 ffffffff 00000000 S k_worker/31:0 u22_a109 4664 282 967656 40996 ffffffff 00000000 S com.kingroot.kinguser:service media_rw 4698 1 4392 1248 ffffffff 00000000 S /system/bin/sdcard u22_a109 4786 4664 428 4 ffffffff 00000000 S ku.sud root 4790 1 1452 40 ffffffff 00000000 S /system/xbin/ku.sud root 4791 4790 1468 532 ffffffff 00000000 S k_shell/2210109:4786 u0_a59 4896 282 973320 25172 ffffffff 00000000 S com.android.smspush u0_a19 5167 282 1111764 52348 ffffffff 00000000 S com.google.android.gms.persistent u22_system 5294 282 988068 36016 ffffffff 00000000 S com.android.settings root 5340 2 0 0 ffffffff 00000000 S kworker/u8:7 u22_a35 5523 282 966368 24768 ffffffff 00000000 S com.android.email u22_a115 5577 282 960216 27104 ffffffff 00000000 S com.cmplay.activesdk:service u22_a63 5802 282 947124 22096 ffffffff 00000000 S com.atmos u22_a60 5821 282 998860 27192 ffffffff 00000000 S com.android.de u0_a167 5922 282 983804 29656 ffffffff 00000000 S com.oasisfeng.greenify:service u0_a167 5947 5922 1500 416 ffffffff 00000000 S sh u0_a167 5952 5947 1424 560 ffffffff 00000000 S logcat u22_a110 5990 282 1156420 115336 ffffffff 00000000 S com.chrome.dev u22_a110 6079 282 1058820 64524 ffffffff 00000000 S com.chrome.dev:privileged_process0 u0_a60 6419 282 946620 23600 ffffffff 00000000 S com.android.de u22_a19 6440 282 1078752 40400 ffffffff 00000000 S com.google.android.gms.persistent u22_radio 6589 282 950000 23616 ffffffff 00000000 S com.qualcomm.qcrilmsgtunnel root 7155 2 0 0 ffffffff 00000000 S kworker/0:1 u22_a15 7179 282 1012280 61768 ffffffff 00000000 S com.android.systemui u22_a239 7835 282 991592 59300 ffffffff 00000000 S com.janerking.archery u22_a239 7863 7835 428 4 ffffffff 00000000 S su root 7868 1 1452 40 ffffffff 00000000 S /system/xbin/ku.sud root 7869 7868 2636 784 ffffffff 00000000 S kworker root 7958 7869 0 0 ffffffff 00000000 Z getenforceroot 7960 7869 0 0 ffffffff 00000000 Z getenforceroot 7961 7869 0 0 ffffffff 00000000 Z sh root 7963 7869 0 0 ffffffff 00000000 Z sh radio 8266 282 949004 22212 ffffffff 00000000 S com.qualcomm.qcrilmsgtunnel root 8303 1 252 28 ffffffff 00000000 S /data/data-lib/com.kingroot.kinguser/ktools u0_a109 8311 282 970008 32096 ffffffff 00000000 S com.kingroot.kinguser:service root 8383 2 0 0 ffffffff 00000000 S kworker/u8:1 u0_a109 8395 8311 260 4 ffffffff 00000000 S k_worker/31:10109 root 8408 4593 260 36 ffffffff 00000000 S k_worker/31:0 root 8409 8408 1528 576 ffffffff 00000000 S sh u0_a19 9532 282 1180452 45008 ffffffff 00000000 S com.google.android.gms u0_a19 9563 282 958264 29184 ffffffff 00000000 S com.google.process.gapps u22_a19 9657 282 1382200 81128 ffffffff 00000000 S com.google.android.gms u0_a15 10236 282 1102684 115992 ffffffff 00000000 S com.android.systemui root 10581 2 0 0 ffffffff 00000000 S kworker/3:0 root 11166 2 0 0 ffffffff 00000000 R kworker/u8:8 u22_a235 11191 282 1198252 176288 ffffffff 00000000 S com.ea.game.nfs14_row u22_a237 11287 282 955840 28280 ffffffff 00000000 S com.android.vending.billing.InAppBillingService.LACK:billing u22_a237 11321 11287 428 4 ffffffff 00000000 S su root 11328 1 1452 40 ffffffff 00000000 S /system/xbin/ku.sud root 11331 11328 1496 832 ffffffff 00000000 S k_shell/2210237:11321 root 11643 2 0 0 ffffffff 00000000 S kworker/1:1 u22_i170 11815 282 1157936 87616 ffffffff 00000000 S com.chrome.dev:sandboxed_process7 root 11886 2 0 0 ffffffff 00000000 S kworker/0:0 root 11929 2 0 0 ffffffff 00000000 S kworker/3:1 root 12004 2 0 0 ffffffff 00000000 S kworker/1:3 root 12272 2 0 0 ffffffff 00000000 S kworker/2:1 root 12273 2 0 0 ffffffff 00000000 S kworker/u8:2 u22_i172 12317 282 1061872 39948 ffffffff 00000000 S com.chrome.dev:sandboxed_process9 root 12561 2 0 0 ffffffff 00000000 S mdss_fb0 u0_a34 12766 282 989784 40136 ffffffff 00000000 S com.cyanogenmod.eleven:main u22_a34 12911 282 989700 39952 ffffffff 00000000 S com.cyanogenmod.eleven:main root 13246 2 0 0 ffffffff 00000000 S VosWDThread root 13247 2 0 0 ffffffff 00000000 S VosMCThread root 13248 2 0 0 ffffffff 00000000 S VosTXThread root 13249 2 0 0 ffffffff 00000000 S VosRXThread root 13250 2 0 0 ffffffff 00000000 S wlan_logging_th wifi 13251 1 4436 1388 ffffffff 00000000 S /system/bin/wpa_supplicant dhcp 13588 1 1432 444 ffffffff 00000000 S /system/bin/dhcpcd root 13944 2 0 0 ffffffff 00000000 S kworker/0:3 system 13959 282 983708 36284 ffffffff 00000000 S com.android.settings u22_a16 14049 282 953904 27996 ffffffff 00000000 S org.cyanogenmod.theme.chooser u22_a12 14176 282 1126912 103952 ffffffff 00000000 S com.android.vending u22_a7 14219 282 949704 35208 ffffffff 00000000 S android.process.media u0_a12 14244 282 996112 42552 ffffffff 00000000 S com.android.vending u22_a77 14290 282 1523528 150512 ffffffff 00000000 S com.google.android.gm u22_a4 14502 282 950688 32632 ffffffff 00000000 S android.process.acore u0_a84 14538 282 1027644 57504 ffffffff 00000000 S com.whatsapp u0_a4 14590 282 960120 42536 ffffffff 00000000 S android.process.acore u0_a235 14636 282 959496 26536 ffffffff 00000000 S com.ea.game.nfs14_row root 14703 2 0 0 ffffffff 00000000 S kworker/1:0 root 14720 2 0 0 ffffffff 00000000 S kworker/3:2 u0_a121 14809 282 956172 34512 ffffffff 00000000 S imoblife.startupmanager u0_a5 14844 282 945720 26572 ffffffff 00000000 S com.android.defcontainer u22_a16 14894 282 944864 28592 ffffffff 00000000 S org.cyanogenmod.themes.provider u22_a20 14916 282 946280 26168 ffffffff 00000000 S com.google.android.partnersetup u22_a39 14939 282 951964 28420 ffffffff 00000000 S com.android.gallery3d u22_a52 14959 282 945724 25300 ffffffff 00000000 S com.svox.pico u22_a237 15042 282 953752 29624 ffffffff 00000000 S com.android.vending.billing.InAppBillingService.LACK u22_a243 15155 282 1008300 68928 ffffffff b6deda40 R jackpal.androidterm u22_a243 15176 15155 1520 876 c03ff48c b6ec48c8 S /system/bin/sh u22_a243 15191 1 3524 1416 ffffffff b6f55b7c S adb root 15330 2 0 0 ffffffff 00000000 S kworker/2:2 u0_a19 15336 282 1054660 25928 ffffffff 00000000 S com.google.android.gms.nearby.connection root 15411 2 0 0 ffffffff 00000000 S kworker/2:3 u22_a243 15432 15155 1516 844 c012c1a8 b6ef8694 S /system/bin/sh u22_a243 15441 15432 2700 988 00000000 b6f328c8 R ps u22_a11 16656 282 1009124 60224 ffffffff 00000000 S com.mokee.launcher root 17227 1 260 36 ffffffff 00000000 S k_worker/44:0 u22_a74 17799 282 1066312 82160 ffffffff 00000000 S com.touchtype.swiftkey u0_a197 23100 282 998668 52768 ffffffff 00000000 S com.zerodesktop.appdetox.qualitytime root 30886 2 0 0 ffffffff 00000000 S kworker/2:0 u22_a243@Lenovo:/ $

2016-01-11-10-42-46.txt

01-10 00:59:23.891 D/BulldogService(5270): try: exec /data/app-lib/com.janerking.archery-1/libdaemon.so com.janerking.archery 01-10 00:59:38.511 F/libc (5295): Fatal signal 8 (SIGFPE) at 0x0804c677 (code=1), thread 5295 (libdaemon.so) 01-10 00:59:38.631 I/DEBUG (574): pid: 5295, tid: 5295, name: libdaemon.so >>> kworker <<< 01-10 00:59:38.631 I/DEBUG (574): #00 pc 00004677 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): #01 pc 0000657b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): #02 pc 00034b71 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): #03 pc 00035bae /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): #04 pc 000011de /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): #06 pc 000012d8 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82e7b8 08049d49 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82e7bc 08099f1c /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82e7cc 0804c63b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): #00 bf82e7d0 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82e7f0 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82e804 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82ed94 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82ed98 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82ed9c 080949a0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82edbc 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82edc4 080948ab /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82edc8 080948b9 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82f2c8 0809473e /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82f2cc 08094be7 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): bf82f2d0 08094634 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.631 I/DEBUG (574): 08048000-08099000 r-x /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): pid: 5295, tid: 5295, name: libdaemon.so >>> kworker <<< 01-10 00:59:38.691 I/DEBUG (574): #00 pc 00004677 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): #01 pc 0000657b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): #02 pc 00034b71 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): #03 pc 00035bae /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): #04 pc 000011de /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): #06 pc 000012d8 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82e7b8 08049d49 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82e7bc 08099f1c /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82e7cc 0804c63b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): #00 bf82e7d0 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82e7f0 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82e804 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82ed94 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82ed98 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82ed9c 080949a0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82edbc 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82edc4 080948ab /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82edc8 080948b9 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82f2c8 0809473e /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82f2cc 08094be7 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): bf82f2d0 08094634 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:38.691 I/DEBUG (574): 08048000-08099000 r-x /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): pid: 5295, tid: 5295, name: libdaemon.so >>> kworker <<< 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): #00 pc 00004677 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): #01 pc 0000657b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): #02 pc 00034b71 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): #03 pc 00035bae /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): #04 pc 000011de /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): #06 pc 000012d8 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7b8 08049d49 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7bc 08099f1c /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7cc 0804c63b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): #00 bf82e7d0 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7f0 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e804 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82ed94 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82ed98 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.301 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82ed9c 080949a0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): pid: 5295, tid: 5295, name: libdaemon.so >>> kworker <<< 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): #00 pc 00004677 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): #01 pc 0000657b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): #02 pc 00034b71 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): #03 pc 00035bae /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): #04 pc 000011de /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): #06 pc 000012d8 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7b8 08049d49 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7bc 08099f1c /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7cc 0804c63b /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): #00 bf82e7d0 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e7f0 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82e804 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82ed94 080949b0 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82ed98 08094992 /data/app-lib/com.janerking.archery-1/libdaemon.so 01-10 00:59:39.421 E/bulldog-daemon(5270): I/DEBUG ( 574): bf82ed9c 080949a0 /data/app-lib/com.janerking.archery-1/libdaemon.so

In some firmware for use GG, you need to allow the use of floating windows. Sometimes it is called the notification, alert, docking area, dropzone and so on. MIUI v5: Go to Settings - Applications - everything. 2. Find Game Guardian 3. Enable slider "Pop-ups" Screenshot https://www.youtube.com/watch?v=0Xxj7Kz7WjQ MIUI v6 / Flyme: Go to "Settings" - "All Applications" - "All" found "GameGuardian", in its turn slider settings "pop-ups". https://www.youtube.com/watch?v=hZfcIT74PS8 Sometimes Flyme meets mistranslation as the Alarm (second paragraph): MIUI v7: Go to the application "Security" - permission - permission - GameGuardian - Pop-up windows. EMUI: Phone Manager - Go to Settings (Settings) - Shortcuts - looking there dropzone manager - activate it. Now its icon available on the desktop. We go to the dropzone manager in the list of GG and allow access. The popup does not show on Huawei phones by default. You will need to allow GameGuardian to show popup. Please open the Phone Manager, then Dropzone Management and please make sure it is turned on for GameGuardian . The Popup also does not show on some Xiaomi phones. You need to head to Settings -> Installed apps -> GameGuardian -> Other permissions -> Display pop-up window. Also, other phones may have different procedures to allow apps to show Popup windows. All such apps are usually affected this way, for example the Google Translator app with the Tap To Translate functionality. Therefore, you can simply google "YOUR_PHONE tap to translate" to find the solution. For example, for Xiaomi Redmi devices the solution is as follows: https://productforums.google.com/forum/#!topic/translate/1Pywh5vI1kE

No. The problem is not the point. They start another thread that connects to the debugger main process. Well, since the debugger can be only one, the GG has not connect. app_25 18501 17857 406968 136224 ffffffff 00000000 S com.buffstudio.timinghero app_25 18514 18501 205728 27312 ffffffff 00000000 S com.buffstudio.timinghero signed int __fastcall sub_25C44(__pid_t a1, int a2) { __pid_t v2; // r4@1 __int32 v3; // r0@1 __int32 v4; // r5@1 int v5; // r1@3 int stat_loc; // [sp+4h] [bp-14h]@1 stat_loc = a2; v2 = a1; v3 = ptrace(PTRACE_ATTACH, a1); v4 = v3; if ( v3 < 0 ) return 255; if ( !v3 ) { if ( waitpid(v2, &stat_loc, 0) == -1 && *_errno(0, v5) == 10 ) waitpid(v2, &stat_loc, -2147483648); if ( ptrace(PTRACE_CONT, v2) < 0 ) { ptrace(PTRACE_DETACH, v2); return 255; } } return v4; }

Oh ok. i just did and it works, but when i pause/play the game too often, the entire device freezes until i hold 10 seconds to shut down my device. can you fix it? My device is Sony Xperia Z3 Compact (ARM processor), and the firmware, SuperSU and Busybox are updated to the latest version.

When I use the game acceleration, it will crash the app. I tried running GG8.X on touchwiz 5.1.1, but the same results However, GG7.3.6 works fine Is device problem or bug? Androidversion: touchwiz 5.0.1 Device model: samsung galaxy j cpu: snapdragon 800 2015-12-27-12-10-10[1].txt

It's a problem of your firmware, not the application. All it falls before the application starts somewhere in the system code. It seems that the ART compilation took place correctly. I'm here I can not do anything. Perhaps this is due to the fact that the new version was used data type "long" in Java code. Similarly, it's hard to say. *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint: 'samsung/zeroltexx/zerolte:5.1.1/LMY47X/G925FXXU3COI9:user/release-keys' Revision: '10' ABI: 'arm64' pid: 13690, tid: 13690, name: m.cnplay.tiles2 >>> com.cnplay.tiles2 <<< signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xca900000000217 x0 0000007f89c933c0 x1 0000007fe63a5b80 x2 0000007f89c933c0 x3 0000000000000000 x4 000000007771a1b0 x5 0000000000000001 x6 0000000000000000 x7 0000007f89c8a1bc x8 0000000000000000 x9 0000007f89c8a1b8 x10 0000000000000000 x11 0000000000000000 x12 0000000000000000 x13 0000000000430000 x14 0000000000550000 x15 0000000000430000 x16 0000000000000000 x17 89ca90000000007f x18 0000007f89bfd520 x19 0000000000000060 x20 0000000074115020 x21 0000007f89ca9000 x22 0000007f89ca9090 x23 0000007fe63a5d50 x24 00000000718e4c79 x25 0000007fe63a5d50 x26 0000007fe63a5d60 x27 0000007fe63a5d98 x28 0000007fe63a6270 x29 0000007fe63a5c00 x30 000000007414002c sp 0000007fe63a5b70 pc 0000000074115024 pstate 0000000060000000 v0 00000000000000000000000000000000 v1 00000000000000000000007f89c65560 v2 00000000000000000000000000000000 v3 00000000000000000000007fe63a7118 v4 00000000000000000000007fe63a70a8 v5 00000000000000000000007fe63a7108 v6 00000000000000000000007fe63a7098 v7 000000000000000070c1a93870c1a938 v8 00000000000000000000007fe63a6388 v9 000000000000000000000000714f51e8 v10 00000000000000000000000000000011 v11 00000000000000000000000000000045 v12 00000000000000000000007f89ca0400 v13 00000000000000000000007f89ca0400 v14 00000000000000000000007fe63a7aa8 v15 00000000000000000000000000080000 v16 00000000000000000000007fe63a7088 v17 70c1a93870c1a93870c1a93870c1a938 v18 70c1a93870c1a93870c1a93870c1a938 v19 70c1a93870c1a93870c1a93870c1a938 v20 70c1a93870c1a93870c1a93870c1a938 v21 70c1a93870c1a93870c1a93870c1a938 v22 70c1a93870c1a93870c1a93870c1a938 v23 70c1a93870c1a93870c1a93870c1a938 v24 70c1a93870c1a93870c1a93870c1a938 v25 70c1a93870c1a93870c1a93870c1a938 v26 70c1a93870c1a93870c1a93870c1a938 v27 70c1a93870c1a93870c1a93870c1a938 v28 70c1a93870c1a93870c1a93870c1a938 v29 70c1a93870c1a93870c1a93870c1a938 v30 000000000000000000000000ebad608e v31 000000000000000000000000ebad608f fpsr 00000010 fpcr 00000000 backtrace: #00 pc 0000000000000024 /data/dalvik-cache/arm64/system@[email protected] #01 pc 000000000002b028 /data/dalvik-cache/arm64/system@[email protected] stack: 0000007fe63a5a70 0000007f8a000178 [anon:libc_malloc] 0000007fe63a5a78 0000007fe63a5b68 [stack] 0000007fe63a5a80 0000007fe63a5c30 [stack] 0000007fe63a5a88 0000007f898e0dfc /system/lib64/libart.so (art::gc::allocator::RosAlloc::AllocFromRun(art::Thread*, unsigned long, unsigned long*)+420) 0000007fe63a5a90 0000000012c6f6e0 /dev/ashmem/dalvik-main space (deleted) 0000007fe63a5a98 0000007f89ccf0e8 [anon:libc_malloc] 0000007fe63a5aa0 0000007f89c05e98 [anon:libc_malloc] 0000007fe63a5aa8 0000000000000001 0000007fe63a5ab0 0000007f7f4036d8 [anon:libc_malloc] 0000007fe63a5ab8 0000007f00000001 0000007fe63a5ac0 0000007f8a0001e8 [anon:libc_malloc] 0000007fe63a5ac8 0000007fffffffff 0000007fe63a5ad0 0000007f8a0001e8 [anon:libc_malloc] 0000007fe63a5ad8 0000007f89a0d840 /system/lib64/libart.so (art::mirror::Class::GetInterfaceTypeList()+108) 0000007fe63a5ae0 0000007fe63a5c00 [stack] 0000007fe63a5ae8 0000000074140014 /data/dalvik-cach processName:com.cnplay.tiles2 broadcastEvent : com.cnplay.tiles2 SYSTEM_TOMBSTONE You can try to uninstall and install. Maybe it works, if it was a temporary problem in the compilation of ART.

Update: I decompiled the APK and found a Java file labeled MD5Util in a series of files in a droidhang/utilities directory (droidhang is the name of the dev company). I don't believe this is the function that provides the 10-digit hash spoken of, BUT I think this might help in figuring out how the OTHER XML files for the levels, heroes, and stats are encrypted. Here's the source code: package com.droidhang.util; import java.security.MessageDigest; public class MD5Util { private MD5Util() { } public static String getHexDigest(byte[] digestBytes) { if (digestBytes == null) { return null; } StringBuilder sb = new StringBuilder(); int len$ = digestBytes.length; for (int i$ = 0; i$ < len$; i$++) { sb.append(String.format("%02x", new Object[]{Byte.valueOf(arr$[i$])})); } return sb.toString(); } public static void main(String[] args) throws Throwable { System.out.println(getHexDigest(MessageDigest.getInstance("MD5").digest("asdasdadsasdasadasda".getBytes("utf-8")))); } } MD5Util.java MD5Util.java MD5Util.java

During the first log it freezes somewhere above 60-70%, during 2nd search and edit on results was working fine at all. Restarting just GG, searching for different value and freeze around 10% of search. dbg1.zip dbg2.zip dbg3.zip

It is not md5. md5 length of 32 characters, and then they 10. Or is it part of the hash or some other hash. A study of the source code can answer this question.

Good. Thanks. But a full translation will only be available in the next release after 8.0.4, because at the time of release 8.0.4 transfer has not been completed. No problem mate, next release. Cheers

version 8.0.3 is even worse. it sometime freezes the app and freezes my device too! when i search auto (slow), cancel, search and choose (dword), it still continue to search as auto (slow). app pausing does not work, play button appeap not not pause by default. when i tap it many times, it freezes my device and i can't hold 10 seconds to force power off my device. uninstalled GG and please give me 7.3.6

2015-11-16-20-10-22.txt

Comparsion GameKiller with GameGuardian Let the points tell what GK best. And then, at the same time update the cap. And the fact that there is not drawn to the "best": Of the features: 1. call icons that can be dragged Doubtful plus all the utilities so able. GameGuardian version 7.3.5. Also got the opportunity to drag the icon. Although previously it was possible to change its position, even slightly more sophisticated way. 2. You can pause the game That Yes, until recently, very few people knew how. But again GameGuardian 7.3.5 is able. 3. You can choose to between open applications (some of them want to hack) GameHacker and GameGuardian it can. 4. Search value with the sign "-" GameGuardian knows how long ago. 5. off-line instructions and assistance Someone reads HELP? At the start GameGuardian minihelp opens. 6. any search settings In GameGuardian also have "any search settings". 7. search value type (4 bytes, 2 bytes, 1 byte, float) GameGuardian knows all this, plus he knows how to search for XOR, which does not know how anybody. And now you can go through the rest of the items, which are not present at GK: 1. Controlling the speed of the game is? No. In GameGuardian there, but only for the ARM. 2. Support for x86-based devices have? No. In GameGuardian there. 3. Lollipop support? Somehow yes, judging by the reviews on the forums. We GameGuardian this is much better. 4. Editing a large number of results once there? No. All that is greater than 500 is not shown. And you can edit GameGuardian least the first 10 000 of found 1 000 000. The main thing that had the memory. 5. Freeze there? Yes, the usual. And GameGuardian 7.3.5 has expanded. Usually, only the increase, decrease and only on the band, in ArtMoney. 6. Displays the status of the search there? No. Sit and wonder, search, or simply goes the inscription on the screen. GameHacker GameGuardian and show the status of the search process. 7. Is it possible to enter a hexadecimal value to search for? No. In GameGuardian you can, if you add the letter h at the end. 8. If the ability to search / produce screenings for conditions other than equality? For example, all that more / less / not equal 100? No. In GameGuardian and GameHacker such a possibility. 9. Can I run 10-20 fuzzy search for equality immediately for screening random values? No. Sit and manually tap. In GameGuardian such a possibility. 10. What is the situation with the transfer and support? And in any way. If not translate enthusiasts, there will be Chinese. Developer there. Bug reports or suggestions for improving writing nowhere. And what we have in GameGuardian? Developer online, normal Russian (and not only) in the language of the official version, you can write bug reports and something to offer / ask for. 11. Can I make an icon GK was not visible on the screen (some anti-cheat do screenshots)? No. In GameGuardian possible. 12. You can adjust the transparency of the icon? No. And GameGuardian possible. 13. Specify the path to a temporary file, you can (for example you have two cards and the first goal)? No. In GameGuardian possible. 14. You can find these regions? No. There is something unintelligible, called as an upper limit, but it is not the regions, and a certain amount. A GameGuardian possible. Perhaps enough. Do not pull the GK on the "best of its kind." I would be glad if you can prove otherwise.

By the way, about the speed of the search. Starting with version 8.1.0 adds the ability to store data in memory. If you have enough RAM available, it can greatly speed up the search (10 times more). Go to settings and select the desired setting: Spoiler However, the application may crash if memory is insufficient. Therefore, this option is not enabled by default. If the application closes spontaneously, try to choose the lesser value, or disable this option entirely. On the emulator, the same as the BlueStacks, memory usage may be slower than the use of files. Try. Spoiler (General Recommendations) The search speed depends on the speed of reading and writing to the memory card. Therefore, to seek faster, it makes sense to put as much as possible high-speed memory card. Especially when using the fuzzy search. To make it clearer, citing figures. Displacement of the temporary file, depending on the situation, can reach 100-300 MB and above. Say it 100 MB. This is about 10 million dword values. Normal operation on the file is in its full reading and writing. Typically, reading faster than writing, so I will focus on the recording speed. Take the usual Class 2 memory card on which the maximum write speed will be about 2 MB / s. Record 100 MB will be carried out within 50 seconds. Now let us compare with the 10 class (10 Mb / s) - 10 seconds. Sensible difference. If you take more high-speed card, for example, SDCA10 from Kingston, and there speed (I was to write 25 MB / s) allows you to record 100 MB 4 seconds. Search time will not be less than the figures shown above. If we consider the search time, the distribution cost of time, in decreasing order of importance, is: Read / write to the memory card. Reading the memory process. Various mathematics (comparison, search, etc.) As can be seen, the basic search time is not strongly dependent on the program code, as defined by your device or equipment thereon. To speed up the search, you can do the following: As I wrote - to use the fastest memory card. Select only the necessary regions of memory and does not use slow regions (Others) - access to them can be very significantly slow searching. To reduce the maximum amount for the search. For example: after the start of a fuzzy search use the "not equals" rather than "is" because the memory addresses that have changed are always much smaller than those that have not changed. The search is performed on "fresh" start the game, if it is possible, because the longer the game runs, the greater the amount of memory used and the more space for the search. Try not to use the data type to "Auto", because there is a lot of checks carried out, which may be unnecessary in your case.

Using filters The annex contains the filters, which is not in any similar application. Currently filters work with Java code. This means that they are not very fast, and can consume a lot of memory. In the future, filters will be improved and rewritten in C. So, what is a filter? Filters are special rules used to filter the current results. Unlike dropout filters do not affect the status of the search. Once you remove the filters, everything was back to the same state it was in before filtration. What is comfortable? You can search for any special significance, not being afraid to make a mistake and lose the rest. Filters are available on "..." button, click Filter. After his selection will be shown the settings window filters: Consider the order of each field: Filter, not more than - specifies the number of entries to filtration See, no more than - specifies the number of entries displayed in the search results Then came various filters, which we will consider later. So far, the return to the mechanism of the filters in order to understand why we need these two numbers. I must say about the second - is the number of results you see at the end of the search. It always works, even if you do not select any filter. It is necessary to bring the first 1000 results, please enter 1000 and presses apply. At least 10 million. The value is not limited in any way. But remember, the more results you upload, the more memory consumption. Then the memory is not enough, and the system washes GG. So do not put very many. We looked at how many found: In this case, we found 8,674,304 results and shows the first 100, and you need 10 000. So you put the filters in the second number 10 000. And get your 10 000 results, and then change them all. And then the game because of it flies, as you there is something broken. But that's another story. Let's go back to the first field in the filters. To understand what it means, you need to talk a little bit about how filters work. So, imagine that we have included filters and found 10 million results. The application will receive the results and check each against all filters. Get results the program is not everything, but no more than that number, which is indicated in the first field. Why not more? Because as soon as the typed number to display, continue to receive will be discontinued. Returning to the example. 10 million total results. Filter we will be 1000, and output 100. This means that there will be obtained the first 1000 results and tested for the filters. Those that have passed, but no more than 100 will show. I hope it is clear. Here you can still make an analogy with a sieve. The first number is the amount that you ship in a sieve, and the second - the maximum amount of results of the last sieve. If it has a screen more than the second number, it will be only the first of them. So now on the filters themselves. Their is 5 pieces: Skip similar addresses - if this filter is enabled, after the result which matches the rest of filters, will be missed all the results, the distance to less than or equal to the specified number. Let me explain with an example: is the number 10, it fits the filter, followed at a distance of 8 bytes is the number 11, which is under the filter is not suitable, but if you have activated the filter "to pass close to the address" with a value of not less than 8, then 11, also fall into conclusion. What is comfortable? For example, you know that after the number 10 goes to 12 bytes the desired value. You are filtering by value and turn the filter parameter 12. Example of usage. Address > - skips all options that address more than the specified number. This way you can portions of, for example, 1000, to view all found each time putting here the last address of the found variants. Address < - same as above, but applies to all addresses less parameter. Value > - similar and values. Here there is only a small problem - all values are treated as dword, regardless of what they actually are. So this will work fine only dword. This will be corrected once. Value < When the filter is the number of results displayed, not as a single number or two, but as three numbers. For example, I asked a search of 101 in the first 1000 results: But he was not there: If the filters are included, there are always three numbers: the first - the number of results found, and the second - the number of results submitted to the input filter, and the third - the number of results past the filters. If the filter is not enabled, there may be one or two numbers. If the number is one, it means that all results have shown results. For example, "(20)" means that we have found 20 results, and they are all displayed. If the two numbers, the first number is the number found, and the second - the number shown. For example, "(20/10)" - found only 20 and 10 are shown first. Let's go back to the filters. I still want to find her 101. Somewhere as it should be. And I do not weed out hunting. Therefore, I will increase the number of results submitted to the input filters. By the way, the more of them, the slower will be updated list. Take 100 000 for example: And then we are fine: You can now with these values do something - to remember to change or something else. That's all. Oh yes. When you enter values or addresses, you can enter it in hexadecimal by adding the letter h at the end: 100 = 64h 102 = 66h The result is the same as above, as a record of the same filter, just in a different form. This option can be used in almost every place where you need to enter the number: Edit the values of the variable parameters of filters and so on.

Of course... I do not think it will change anything, because it is not so based on a crash or so. It is somehow not listed here. Why dont you just add it as a new language... Screens are the same, skipping those... 2015-10-15-16-46-50.txt last_run.log

Android 4.3 Samsung i9300 last_run.log 2015-10-13-17-12-51.txt 2015-10-13-17-13-43.txt

And according to the log it has found no less than 1484 values: Progress: 75 482 from 75 520, found: 1484During the 156 seconds (about 3 minutes). After that was launched another search results you did not wait - came out of the GG. But in the second search, at the time it was found 571 value: Progress: 8097 from 74 503, found: 571Besides, I see that you arm64 system and x64 is not supported. Another note. Finding results 0 is not an error. If you are looking for a number that is not in memory, it will be 0, and the results it is absolutely logical. It is quite another thing, if you have any number of 0 results. For example the number "10".

I could give you a logcat but this takes like, 10-15 minutes to do a scan, log will be massive. Is why I didn't send one. Sure it's fine? Using the most recent version of Gameguardian I think. Is version 7.3.6 Not only this, but speed hacks don't work at all. on my old galaxy Note 2 yesterday I could use SB game hacker to slow down time in a game called "Kill me again" With Gamegaurdian, nothing happens at all. Should I make a log of that too?