Forgot to update this,
The above issues were due to incompatibility in the EGL and OpenGL
libraries, after using the right propriety libraries things worked, these
libraries are platform version specific.
The recent updates are in the below thread
https://groups.google.com/forum/#!topic/andro
>
> Somehow reached till the bootanimation(stuck here), couldn't reach the
> home screen. The logcat shows a fatal message* 01-01 00:09:03.862 392
> 392 F SurfaceFlinger: no suitable EGLConfig found, giving up. *
>
EGL INFORMATION FROM LOGCAT
01-01 00:08:57.971 139 139 D libEGL : loade
Thanks Parthib, it worked. Now we're facing a new problem, the services get
started and killed in a loop, but adb shell works. Any idea how to solve
this?
[ 10.011370] type=1403 audit(946685004.610:2): policy loaded
auid=4294967295 ses=4294967295
[ 10.020478] type=1404 audit(946685004.61
Find this line on system/core/init/init.CPP >
https://github.com/LineageOS/android_system_core/blob/cm-14.1/init/init.cpp#L369
And change unknown to your chipset name.
--
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
---
How to get kmsg when my ROM is not booting and adbd also doesn't start only
stuck at the manufacturer logo.
Sorry for off-topic
--
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
---
You received this message because you ar
> LATEST UPDATES:
>
We figured out that the boot stopped since the kernel couldn't start, after
using a proper kernel now boot proceeds till init stage but falls into an
infinite loop showing ..* [12.953154] binder: 110:110 transaction failed
29189, size 0-0. *
However seeing this line (high
Do you have a debug port on the board? What does the output show?
Is the display driver correctly configured for your board? A white display
would indicate that something with timing.
On Wednesday, 20 December 2017 23:56:27 UTC+7, Jeshurun Edward wrote:
>
> Hello,
>
> We have successful
