• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM10 test build

EGL_BAD_ALLOC
seems to be the main issue
it cant allocate the graphics ram, also that stuff about the media player service dieing can cause it to not boot. you gotta be careful what parts from stock you use, alot of things like camera libs will do that if you use the stock copies kuz it wont match the main media libs and stuff.

i have no doubt you guys can figure it out but i think the dalvik virtual machine is dieing because of onw of those things from a preliminary inspection. havent made it far tho its a big file
 
well after all of that, and i think a soft reboot in there, its saying it cant find cache at ALL. so i sent a pull request (which was merged) to mount cache at boot like its supposed to cuz zte mounts cache thru init.rc and not fstab like they're SUPPOSED to, cuz they have to check it for consistency (android does this anyways but zte will be zte)
 
Code: 
[ 01-06 10:50:32.502   552:  558 W/Adreno200-EGLSUB ]
<GetBackBuffer:2421>: handle base address is NULL

[ 01-06 10:50:32.502   552:  558 W/Adreno200-EGL ]
<qeglDrvAPI_eglSwapBuffers:3494>: EGL_BAD_ALLOC

over and over and over, the memory base address in gralloc is set to null... no good at all


Code: 
[ 01-06 10:52:58.408  8184: 8184 E/dalvikvm ]
Could not stat dex cache directory '/cache/dalvik-cache': No such file or directory
and that is either a mount, permission, or formatting issue with cache it looks like
 
yea i saw the cache not being read WAY down in the log lol. im sure it can be done via fstab just not sure how to set it up properly. if you fix that though then you still gotta fix the gralloc and possibly even the media and camera and audio services, the media/camera/audio crap is probably just one or two libraries pulled from stock causing a domino effect
 
cache should fix dalvik cache, the dalvik vm may be related to that, may be crashing because of the media crap failing. libcameraservice.so for instance, you replace that with the stock one, itll cause those errors
 
junkie2100 said:
yea i saw the cache not being read WAY down in the log lol. im sure it can be done via fstab just not sure how to set it up properly. if you fix that though then you still gotta fix the gralloc and possibly even the media and camera and audio services, the media/camera/audio crap is probably just one or two libraries pulled from stock causing a domino effect
Click to expand...

yea i made this commit:
https://github.com/jimsmith80/android_device_zte_warplte/pull/1

i think we should pull the libs from stock in /system/lib/hw/ and figure out which ones are erroring (this is how i got a 4.2.2 rom to boot on my OG warp ported from HTC Evo Design 4G)
 
well, gralloc is erroring i promise you that, though that may be something about ion not gralloc itself causing the error its just throwing the error. possibly hwcomposer, and possibly the camera and audio parts, you could leave the build camera and audio stuff instead of using stock and itll boot, may not the other way around. audio and camera may very well not work with the built stuff unpatched but it wont stop it from booting im 90% sure where as the stock libs very well might be causing the failures in the media services
 
I just "repo sync"'d this morning
and i get this:
Code: 
igned int}' to 'int' inside { } is ill-formed in C++11 [-Wnarrowing]
hardware/qcom/display/msm8960/libcopybit/copybit_c2d.cpp:1391:55: warning: narrowing conversion of 'src->copybit_image_t::h' from 'const uint32_t {aka const unsigned int}' to 'int' inside { } is ill-formed in C++11 [-Wnarrowing]
target thumb C++: libmemalloc <= hardware/qcom/display/msm8960/libgralloc/ionalloc.cpp
hardware/qcom/display/msm8960/libgralloc/ionalloc.cpp: In member function 'virtual int gralloc::IonAlloc::alloc_buffer(gralloc::alloc_data&)':
hardware/qcom/display/msm8960/libgralloc/ionalloc.cpp:76:18: error: 'struct ion_allocation_data' has no member named 'heap_mask'
hardware/qcom/display/msm8960/libgralloc/ionalloc.cpp:77:46: error: 'ION_FLAG_CACHED' was not declared in this scope
make: *** [/home/rbheromax/android/cm11/out/target/product/warplte/obj/SHARED_LIBRARIES/libmemalloc_intermediates/ionalloc.o] Error 1
make: *** Waiting for unfinished jobs....
rbheromax@agerthorn:~/android/cm11$ nano device/zte/warplte/*.mk

im just trying to see where the compile gets, and i think he modified something there since its not compiling str8 out for me
 
lib/hw/camera.msm8960.so
lib/libaudcal.so
lib/libaudioalsa.so
bin/v4l2-qcamera-app
bin/mm-pp-daemon
bin/mm-qcamera-daemon
from the proprietary-files.txt
and
system/lib/libmmcamera_plugin.so
from device_warplte.mk

all seem to be possible culprits in the media failure
also, you can remove...
$(LOCAL_PATH)/prebuilt/etc/wifi/bcmdhd.cal:/system/etc/wifi/bcmdhd.cal
because that is for stuff we dont use lol
 
In member function 'virtual int gralloc::IonAlloc::alloc_buffer(gralloc::alloc_data&

pretty much matches the logcat error we had... not sure how he got past it but it probably wasnt fixed right, so im actually glad we got that error now so you can trace it and fix it properly
 
one or two of those you may not be able to just remove... you may need the built copies. the camera lib is the most likely in my mind tho
 
lol, its very possible. it uses ion though so the memory probably wouldnt map right, causing serious issues. its also possible a different toolchain would make it pass the error without halting but it would still have the bad lines in it
 
Ive been flying blind on this. I'll be the first to admit. I have no clue what I am doing, and learning as I go. Both of your input is very helpful.
 
I plan on scrapping the work I have so far, and starting over. I had some luck with CAF on the force. All I did was start out by letting android build everything, and then picked through dm, junkies, and hroarks work to find solutions to issues I was having.
 
caf or legacy display variant might help. might bypass the compile error without fixing the problem, but thats not to say its not worth a shot. i dont know where to get a legacy display variant for that version of cm tho
 
You must log in or register to reply here.
Back
Top Bottom