• 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)

But nothing hardly works. And drivers are different so I would say don't flash. I believe someone is working on the VM670 for ICS.
 
ok.. back to work on this.. i believe i have tracked down the problem.. i THINK its in the board_thunderc_input.c, i dont believe is it setup right to handle the new coding of the touchscreen driver.. im looking through now, will update when i know something more, may also have to edit the gpio.h just have to figure out which one lol..

ok, more than just there.. lol.. still digging around in every warning i have compiling.. still trying to figure out where to define max_x and max_y lol

the tlmm-msm7200a.c is where the error comes from.. but i havent found anything in that file saying where its getting its info from.. going to check the headers..
 
tripdoc79 said:
ok.. back to work on this.. i believe i have tracked down the problem.. i THINK its in the board_thunderc_input.c, i dont believe is it setup right to handle the new coding of the touchscreen driver.. im looking through now, will update when i know something more, may also have to edit the gpio.h just have to figure out which one lol..

ok, more than just there.. lol.. still digging around in every warning i have compiling.. still trying to figure out where to define max_x and max_y lol

the tlmm-msm7200a.c is where the error comes from.. but i havent found anything in that file saying where its getting its info from.. going to check the headers..
Click to expand...

Hey trip this link might help you out brother. I'll try and get back to work on this in a couple of days. I got a new nook color for xmas so I will be playing around with that for a few ;) Already got it rooted, CWR installed and I'm about to flash CM7!


https://github.com/mikegapinski/2.6.35/blob/master/arch/arm/mach-msm/lge/board-thunderc-input.c
 
heh thanx brotha, i actually saw something similar to that and made similar changes, i did however see a line taken out of the accelerometer code tehre though.. that happens to be calling tlmm... so i commented that out.. see what happens.. im so deep in includes and such.. looking for anything at the moment lol. thanx again broth, have fun with the nook lol, you know you can dual boot those with CM7 on a sd from what i have read. have fun lol

replaced entire accelerometer and motion with new stuff from above mentioned commit.. see what happens

edit: BAH same error.. looking at other changes..
 
I also noticed all permissions are not being added. I think I'm going to have to copy what the other default phones looked like. To get it working right.
 
ok guys..this question is for the select few that have built CM7..i have posted this question in 3 other places over a week ago with not 1 response :(

i built cm7 from source but my video camera doesnt record.after trying to record it shows a black preview screen and if i tough it,its transparent..... i have searched EVERYWHERE for over a week with NO results and im sorry for posting here..but i know you guys are very good at this and may be able to help! thanks again.
 
mikekelso421 said:
ok guys..this question is for the select few that have built CM7..i have posted this question in 3 other places over a week ago with not 1 response :(

i built cm7 from source but my video camera doesnt record.after trying to record it shows a black preview screen and if i tough it,its transparent..... i have searched EVERYWHERE for over a week with NO results and im sorry for posting here..but i know you guys are very good at this and may be able to help! thanks again.
Click to expand...

what device are you trying to build for?
 
LG has two screens in the Optiums line...a new hitachi and an older novatek.
I believe your max_x issue is coming from include/linux/synaptics_i2c_rmi.h
 
Thanx bobz, I've been over that file a dozen times, do I need to add a definition to it to match the one in the .c file? Like uint16_t max_x, max_y; ?
 
Ok.. From I can see.. Max x and y are not constants.. They are defined by other variables within the driver.. uint is that undefined integer? Cause that's how they are defined lol

yeah continuing on.. i dont think its a driver problem per say.. i mean if i were to re-write the driver to comply with the old kernel source, it would probably work.. not sure if im up to that task.. i have tried editing the existing driver to comply with the new calls... so the problem lies within the kernel source itself.. its looking for max x and y to be defined in a certain way, and they arent defined that way.. so i need to come up with a patch .. to allow it to work th way its written without affecting to much other stuff..
 
so im going through the old driver now, and updating the code to comply.. i think i have added the necessary changes.. im compiling the kernel now.. i have one problem.. when i add my newly compiled kernel to my existing working rom that is using the same kernel, minus the changes to the synaptics driver, it doesnt boot correctly, and once it does finally boot, the screen doesnt come back on.. i didnt edit the config or thevideo drivers.. just the touchscreen.. so i may need @reppard to compile this kernel with the new driver, and then try to flash it..
 
tripdoc79 said:
so im going through the old driver now, and updating the code to comply.. i think i have added the necessary changes.. im compiling the kernel now.. i have one problem.. when i add my newly compiled kernel to my existing working rom that is using the same kernel, minus the changes to the synaptics driver, it doesnt boot correctly, and once it does finally boot, the screen doesnt come back on.. i didnt edit the config or thevideo drivers.. just the touchscreen.. so i may need @reppard to compile this kernel with the new driver, and then try to flash it..
Click to expand...


Pm me a link with the changed files and I will do my best!
 
when i compiled it and then packed it in my rom int he kitchen, it took forever to boot, and also it was trying to play 2 differant boot animations at once the text android one, and the tron looking one... and then the screen went off and wouldnt come on.. wierd.. it alsop shrunk my boot.img from 3.2mb to 2.8 which i thought was wierd as welll
 
tripdoc79 said:
when i compiled it and then packed it in my rom int he kitchen, it took forever to boot, and also it was trying to play 2 differant boot animations at once the text android one, and the tron looking one... and then the screen went off and wouldnt come on.. wierd.. it alsop shrunk my boot.img from 3.2mb to 2.8 which i thought was wierd as welll
Click to expand...


So were looking at the kernel as being problematic right now? The build other wise looks good? Lol
 
KrazeeCracker said:
So were looking at the kernel as being problematic right now? The build other wise looks good? Lol
Click to expand...

not so much sure if it is a kernel problem persay.. yes the kernel is one of the problems.. but the issue im having may be the way the android kitchen is packing the boot image with the new kernel
 
You must log in or register to reply here.
Back
Top Bottom