reboots phone Game Guardian restarts my phone

[PublicEnemyJere]

Running android 4.2.2 jellybean 

When i open gg ot works then I open the game I want to modify I look for the values and press search then right after I press seaech a few seconds later the gg reboots my phone

2016-05-15-15-27-44.txt

[Enyby]

I do not see any problems in log. Search ended normally.

Send kmsg to me.

http://bootloader.wikidot.com/linux:android:kmsg

 

If you firmly believe that the problem in the GG and it constantly happens, I can build the test versions with increased logging. You'll run each of them three times and sent me three log to understand after what point there is a restart.

[PublicEnemyJere]

Yes send me test gg

kmsg

last_kmsg

Also catlog ended fine because thats when my phone restarted it only restarts after I open gg and use it for 1 minutes for less

[Enyby]

Ok. Look like your kernel reboot device. But I do not know why.

 

When test build be ready I posted it here. Currently busy with other tasks.

[PublicEnemyJere]

Thanks man I appreciate the assistance

[Enyby]

I make test build for you. You need install it and reproduce problems three times. After each you need copy file /data/dbg.txt to some other place. After that - send it to me inside zip archive.

I described this process before:

 

GameGuardian.git_signed.apk

[geribaldi]

I has similar issues if gg autoinject in the first process (samsung touchviz) 

 

Menu key and touchviz stop work and after few minutes phone reboots. Maybe a bug with autopause

 

Edit: please make sure that gg dont can self take any app in the list without permissions.

 

Everytime i start gg first and then the game, gg autochose touchwiz launcher and this ends with a reboot or some lags

Edited June 5, 2016 by geribaldi

[Enyby]

21 minutes ago, geribaldi said:

I has similar issues if gg autoinject in the first process (samsung touchviz) 

No any "injection" exists.

22 minutes ago, geribaldi said:

Maybe a bug with autopause

It is not bug. it is intendent behaviour. Selected app autopaused as you selected in settings. Disable autopause for resolve this issue.

[PublicEnemyJere]

Enyby gg works now it doesn't crash anymore I turned off auto start options in my phone and now it works no more freezing or reboots

[geribaldi]

9 minutes ago, Enyby said:

No any "injection" exists.

It is not bug. it is intendent behaviour. Selected app autopaused as you selected in settings. Disable autopause for resolve this issue.

 

Yes i didnt mean real inject, better word is "autoselect these process"

 

After start gg its ask for the process to select. I ignored that everytime but gg select the launcher app by himself (low pid like 13000)

Edited June 5, 2016 by geribaldi

[Enyby]

19 minutes ago, geribaldi said:

but gg select the launcher app by himself (low pid like 13000)

Yes. Currently gg can not allow have nothing selected. Because of that it selected first found process.

If this not be we can not do if user choice search or anything else but app not selected. This need many of checks. In future it can be written but not now.

24 minutes ago, PublicEnemyJere said:

I turned off auto start options

May be you mean auto pause?

[BenCleric]

The only way to fix this issue is to clear your dalvik cache. (Phone should be turn off first) Just press and hold the power button+menu+vol up. When the logo pops up on the screen unpress the power and keep holding the menu button and volume up.

 

 

I experienced this problem after i accidentally press the category of run the program without protection. Then the phone suddenly restart. So everytime i open the app or the game, phone suddenly restart itself. Even i reinstalled the game. Same problem again. So when i clear the dalvik cache on my phone, the problem disappear.

Edited January 8, 2018 by BenCleric

[Enyby]

Need reboot phone manually and problem must be gone. Or run GG - it is clear all bad settings on start.

_______________________________________________

added 0 minutes later

Clear dalvik cache not related. Your issue fixed not by clear dalvik cache, but because you normally reboot phone after that.