I did a quick check, and noticed that it crashes in my_pthread_mutex_lock, a hybris hook for the original pthread_mutex_lock.
The problem is that the mutex used (__mutex) contains an anddress that's not part of the mapped memory region for the process, causing a segfault when we try to access the content of such variable.
To make things even more complicated, the call is originated by /system/lib/hw/gralloc.tegra3.so, and if you also refuse to handle the lock, it'll crash inside the library later on.
I did a quick check, and noticed that it crashes in my_pthread_ mutex_lock, a hybris hook for the original pthread_mutex_lock.
The problem is that the mutex used (__mutex) contains an anddress that's not part of the mapped memory region for the process, causing a segfault when we try to access the content of such variable.
To make things even more complicated, the call is originated by /system/ lib/hw/ gralloc. tegra3. so, and if you also refuse to handle the lock, it'll crash inside the library later on.