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

Root CM10 test build

cm10.1 version of legacy display probably wont work right in cm10.2+ so keep that in mind. now at the same time, they apparently got cm11 running on the old warp sequent with very few issues... might talk to the guys on that project and see whats up with their repos
 
keep in mind though, i dont think the sequent used ion even with the 3.4 kernel... they might have a legacy display variant you can use tho or they may have upgraded to using ion somehow
 
I pulled the prebuilts as suggested. Same result. I am also still having issues with the ram disk, but at least its building with the correct offset now. I am going to take a few days break and then get back at it. I took superr's stock deodexed rom and meshed it with cm10, and finally got to see the cm boot animation on this thing. It looks like its just a matter of finding the correct prebuilts to use
 
Well. I have some progress. Still getting the Dalvikvm errors though

[ 01-02 12:55:08.161 260: 351 I/gralloc ]
using (fd=14)
id = msmfb43_90801
xres = 720 px
yres = 1280 px
xres_virtual = 720 px
yres_virtual = 3840 px
bpp = 32
r = 24:8
g = 16:8
b = 8:8


[ 01-02 12:55:08.161 260: 351 I/gralloc ]
width = 56 mm (326.571442 dpi)
height = 99 mm (328.404053 dpi)
refresh rate = 0.00 Hz


[ 01-02 12:55:08.161 260: 351 D/CALCFPS ]
DEBUG_CALC_FPS: 0

[ 01-02 12:55:08.161 260: 351 D/CALCFPS ]
period: 10

[ 01-02 12:55:08.161 260: 351 D/CALCFPS ]
ignorethresh_us: 500000

[ 01-02 12:55:08.161 260: 351 D/CALCFPS ]
DEBUG_CALC_FPS: 0

[ 01-02 12:55:08.161 260: 351 D/CALCFPS ]
period: 10

[ 01-02 12:55:08.161 260: 351 D/CALCFPS ]
ignorethresh_us: 500000

[ 01-02 12:55:08.192 260: 351 D/libEGL ]
loaded /system/lib/egl/libEGL_adreno200.so

[ 01-02 12:55:08.232 260: 351 D/libEGL ]
loaded /system/lib/egl/libGLESv1_CM_adreno200.so

[ 01-02 12:55:08.232 260: 351 D/libEGL ]
loaded /system/lib/egl/libGLESv2_adreno200.so

[ 01-02 12:55:08.242 258: 258 I/DEBUG ]
 
those are the same errors im getting on my cm10.2 builds for og warp (minus the dalvik stuffs)

my guess try the updated adreno drivers from qualcomm's website
 
Ive got a few ideas now. I'll update if I make any headway. Sucks building with an old celeron lol. I literally can do a max of 2 builds in a day with.
 
its gonna be... gonna have to work on finding a good legacy display variant or fixing the kernel. probably just need the includes adjusted but i know very little of that aspect
 
Junkie if you have a minute could you take a look at my ramdisk setup. It is more or less stock with a small mod to fix the dalvikvm errors. For some reason it still won't boot the system, and I end up having to flash the stock ramdisk with the same modified lines to make it work. The output of unmkbootimg shows that the kernel and ramdisk addresses are correct, so I'm a little lost. The only files cm is building for the ramdisk is default.prop and it modifies init.usb.rc
 
Have you guys been having any luck with this? My little brother just bought a warp 4g tonight and im wanting to show him what android can really do. 4.1.2 is just garbage. :/ I only mess with 4.2+ myself anymore.
 
its not the android version its the android variant thats the problem. cm10 is still only 4.1.2... so youd still be on the dame version

i still dont have a working unit tho myself and uploading test builds is a pain given my internet situation, there are others working on it but there are other things in play too. cm has been booted on an awe, but it was horribly laggy to the point of being unusable, graphics issues

we have a hell of a team assembled, but we also have alot on our plate. nearly a dozen devices being worked on, recoveries, cms, kernels
 
still unusable tho, and that phone they fixed up uses an entirely different kernel, this one doesnt seem itll have the same issue, it has completely different issues. i may have to poke around and see what i can find for the force with that but sadly it wont help the warplte
 
Did anyone ever figure out the ramdisk issue on this? I think the kernel command line might be what is keeping this thing from moving along. I've managed to get rid of the ion / gralloc errors
 
rbheromax said:
What is the error?
Click to expand...

Don't have a logcat handy, but the error is caused by the adreno driver not finding libgenlock.so. the build completes and boots to a blank screen. I looked through the libs from the builds out put, and libgenlock.so is missing from the build
 
you tried the stock one? toss it in there see what happens and if that works you can just do that in prebuilts for now. but isnt there already a cm11 booting and almost complete? lol
 
You must log in or register to reply here.
Back
Top Bottom