-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on version MkIIIv38 and upwards- android 4.4.4 #22
Comments
Please, try to collect a crash log: adb logcat -c Repeat the crash. adb logcat -d '*:E' The only thing you need is to turn on the Developer's Mode on the phone and connect it to something with ADB client. |
Out put of logcat on mklllv37
This is output of logcat of the redist release of mklllv47(old-good crashed too) because i could'nt update the mklllv37 risking loss of continers. In the dev version (tried debug and release of redist and old good) and all crashed. Same with all versions from mklllv38 and upwards.
|
Hmm... I need some more details:
adb logcat -d '*:E' |
You could also filter the log this way to make things shorter: adb logcat -d '*:E' | grep 'AndroidRuntime' |
By the way, I'm just a bit curious about your Android environment setup:
But SuperSU Root is described as a root access manager that is supposed to be used on an already rooted device... So your setup should include:
Is it correct? |
This is actually a stock rom with which has twrp recovery flashed using odin, then I flashed Super Su zip via twrp. Everything works nicely on the phone as if it was normal. Maybe the bug is phone specified. |
Here is the output:
|
Please, remove filtering by |
oh okay let me do that |
Here it is
|
Sorry for this newbie question. Is there a way of calling the host su binary from inside the container? Does sylinking it to the container work? I was trying to lldb on my phone but failed. I tried moving the lldb server binary to my phone, but in my little knowledge i think the binary was built from armhf not arm7-a(not sure if im lost). |
How the error message looks like?
I need some more time to understand the matter of this question.
It seems, PRoot is still unable to handle any other processes which use PTRACE including debuggers. |
Tested and verified on oldgood and redist release of both the mklllv48 and mklV_dev_release. The app now works perfectly. Thanks @green-green-avk |
For Android ARM ABI and VFP related questions: |
I installed the app from google playstore. After creating a shell profile i clicked to run it, but as soon as i clicked the app crashed. So then i seach for the project( amazing by the way) , and tried alll previos versions up to MkIIIv37 which ran perfectly (i am currently running it). Am not sure if the problem is my phone.
Phone : Samsung galaxy tab 3 lite sm-t116, kernel version 3.10.17, android 4.4.4, rooted with super su.
The text was updated successfully, but these errors were encountered: