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

Root [ALPHA] ICS for Optimus M (NOW COMPILED AND BOOTING)

i do make clean followed by make clobber.. my changes are present every build, just rearranged somethings, and i renamed the mcs6000.idc file to synaptics_i2c_rmi.idc see if that makes a differance.. i looked at teh file.. theres not a whole lot in it.. not sure if it will work.. but going to find out... here around midnight most likely
 
I dont edit the boardconfig only yhe device make. And I did make clean clobber it said not needes. Cause I already did make clean.
 
so late, because i started compiling at 3pm.. and it takes me about 8-9 hours to compile the whole thing lol, im not complaining.. the first time took me the greater part of 30 hours.. lol
 
so late, because i started compiling at 3pm.. and it takes me about 8-9 hours to compile the whole thing lol, im not complaining.. the first time took me the greater part of 30 hours.. lol


Holy cow, what things are you working on In this compile? Touchscreen and data services?
 
tripdoc, what time is it where you are?

im in fl.. same time as you EST.


Bobz, or pG or reppard, i have a question.. i compiled a rom last night and included the touch_mcs6000.idc in the device.mk following bobz instructions, it was the only change i made to the rom, when i flashed it it didnt boot.. stuck on android screen.. when i opened the system.img in the kitchen, the touch_mcs6000.idc file wasnt there. i do make clean clobber b4 every build. i just copied the touch_mcs6000.idc file intot he system,img and flashed it, screen still doesnt work, i then renamed it synaptics_i2c_rmi.idc and tried again.. now im not sure what the specifics have to be int hat file per device, but the idc file looked pretty basic, not sure if the one for the synaptics (which i have found references to, but have yet to find one) would be any differant, but.. both roms flashed, and booted but the screen didnt work on either of them. My question, does that files need to be build in tot he rom? or can it be copied into the system.img? if it can be copied in, then im at a lost.. i am currently compiling a rom with it named synaptics, and see if that makes a differance.. but if it doesnt.. i guess im back to trying to compile the kernel error free and see if i can get it working that way.. any advice or tips that you all may have would be greatly appreciated.
 
im in fl.. same time as you EST.


Bobz, or pG or reppard, i have a question.. i compiled a rom last night and included the touch_mcs6000.idc in the device.mk following bobz instructions, it was the only change i made to the rom, when i flashed it it didnt boot.. stuck on android screen.. when i opened the system.img in the kitchen, the touch_mcs6000.idc file wasnt there. i do make clean clobber b4 every build. i just copied the touch_mcs6000.idc file intot he system,img and flashed it, screen still doesnt work, i then renamed it synaptics_i2c_rmi.idc and tried again.. now im not sure what the specifics have to be int hat file per device, but the idc file looked pretty basic, not sure if the one for the synaptics (which i have found references to, but have yet to find one) would be any differant, but.. both roms flashed, and booted but the screen didnt work on either of them. My question, does that files need to be build in tot he rom? or can it be copied into the system.img? if it can be copied in, then im at a lost.. i am currently compiling a rom with it named synaptics, and see if that makes a differance.. but if it doesnt.. i guess im back to trying to compile the kernel error free and see if i can get it working that way.. any advice or tips that you all may have would be greatly appreciated.

What do you mean it doesnt boot exactly? Where does it stop exactly in the boot sequencing? If it actually starts to boot but doesn't complete maybe you can get a logcat. Flash the rom and boot it up with the USB connected to your computer. Then issue either of these commands to see if we can get a log of some sort:
Code:
adb logcat
or
Code:
adb dmesg

This might give you an idea of whats going on exactly. hope this helps!
 
i also noticed the / in #1 should that be deleted?

#1 device/lge/thunderc/files/touch_mcs6000.idc:--->/<---system/lib/idc/touch_mcs6000.idc

#2 device/lge/thunderc/usr/idc/touchmsc6000.idc:system/usr/idc/touchmsc6000.idc \

i been looking at someone that has gotten a lot of stuff working for another rom for ics. and i was wondering is that path suppose to look like #2. i was wondering if it matters where the path of the device of where its calling the idc have to almost match the same file as the out folder?
 
#1 device/lge/thunderc/files/touch_mcs6000.idc:/system/lib/idc/touch_mcs6000.idc

#2 device/lge/thunderc/usr/idc/touchmsc6000.idc:system/usr/idc/touchmsc6000.idc \

i been looking at someone that has gotten a lot of stuff working for another rom for ics. and i was wondering is that path suppose to look like #2. i was wondering if it matters where the path of the device of where its calling the idc have to almost match the same file as the out folder?

so long as the file path is accurate in locating the file needed it shouldn't matter.
 
Very excited to see this, hope all goes well. If I knew more about compiling I would help lol. Thanks for working to get ICS on our phones.
 
ok so im back to trying to update our kernel.. google has released kernel source code for 6 devices.. one of which is called common.. and the other msm.. im grabbing the msm.. im going to see whats been included in it.. and maybe if im luck i can pull some drivers.. maybe.. either way it will give me a better idea of what i need to do with our kernel to get stuff to work correctly.
 
I know the feeling =) I built cm7 about a million times and everytime you clean your build environment it takes that much longer. There are some tricks you can do to store a cache and anything that has not been changed will just get recopied instead of compiling the same source over and over again. Good luck!

so how do i do this ?
 
Back
Top Bottom