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

Root [ROM][WIP] CyanogenMod 7 for the LG Esteem MS910

Awesome, how is it running? Any hardware acceleration, or is it sluggish? I too have been playing around with some stuff for CM7 in my spare time, been trying some solutions for the radios as well.
 
angryGTS said:
Awesome, how is it running? Any hardware acceleration, or is it sluggish? I too have been playing around with some stuff for CM7 in my spare time, been trying some solutions for the radios as well.
Click to expand...
Once it gets booted n settled it doesnt seem to bad, but I know there all sorts of stuff failing in the background tho lol
 
LOL, I hear ya on that, I made some pretty good progress on the build Im working on, again once everything is settled its pretty damn smooth, but lots of progress still to be made, although you will most likely get it going before me, I havnt had much time to play lately.
 
angryGTS said:
LOL, I hear ya on that, I made some pretty good progress on the build Im working on, again once everything is settled its pretty damn smooth, but lots of progress still to be made, although you will most likely get it going before me, I havnt had much time to play lately.
Click to expand...
yea biggest thing atm is RIL, and umm dunno lol
 
Aw man.... my day was almost made until i reread the WIP thread... Cyanogenmod on my Esteem is so close, yet seems so far. :,( oh well, PG is making it meaning itll be prepped to either perfection or near perfection so I can wait. :) (and donate once i get some dang cash in my pocket.>.>)
 
PlayfulGod said:
I have it booting, but radios not working yet so the call, txt, data, wifi, etc etc yet. ;)
Click to expand...


Ah you beat me to it lol :) I was trying to understand the structure etc since it was different. Lemme ask you something tho, you say half the stuff isn't working, to get it working basically you merge driver code in right? (like me trying to get the oc code from your plague kernel and merge it lol, replacing the cpu clock's .c file with your bootloops, so I'm guessing there's another file like cpufreq? I'd appreciate a clue lol)

I just wonder if there are any apps smart enough to better parse all this mess out to identify things and make comparisons, and I mean in a smart semi-automatic way, not line differences in specific files. If one doesn't exist I can write it once I know the general rules in Vb.net 2.0 and it will run with mono installed. Or be brave and directly convert DotNet bytecode to java with xmlvm.
 
kanaida said:
Ah you beat me to it lol :) I was trying to understand the structure etc since it was different. Lemme ask you something tho, you say half the stuff isn't working, to get it working basically you merge driver code in right? (like me trying to get the oc code from your plague kernel and merge it lol, replacing the cpu clock's .c file with your bootloops, so I'm guessing there's another file like cpufreq? I'd appreciate a clue lol)

I just wonder if there are any apps smart enough to better parse all this mess out to identify things and make comparisons, and I mean in a smart semi-automatic way, not line differences in specific files. If one doesn't exist I can write it once I know the general rules in Vb.net 2.0 and it will run with mono installed. Or be brave and directly convert DotNet bytecode to java with xmlvm.
Click to expand...
on the kernel check my commits for when I first added the oc'ing to see what all I changed, or even sum1 elses on github. Off the top of my head you have to edit:

msm7x30-acpuclock.c
cpufreq.c - mainly to add cpufrq braodcasting so CM's cpu settings see em.
Kconfig
your defconfig

I dont know a way to merge linux stuff in windows lol

Now with CM7, basically take my device tree I used for CWM n created a gingerbread branch, then start adding the needed props etc and the product_copy_files lines needed. Create a vendor tree for the proprietary files from the stock rom, create/edit a extract-files.sh to pull those files (mainly for ease of others working with your repo n to not fill github up).

After that its eliminating what files ya dont need or can build from source. Having the src makes life easier if things just dont wanna work because if not you have to find others that will or hack what ya have.

simple eh? ;)
 
No disrespect intended - I'm just curious... has CM9 been abandoned?
I loved CM7... but I've seen nothing for months regarding any real progress with CM9.
It must be a real bear to port CM9 to the Esteem... but I was just wondering if it had been given up on... for now, at least.
(That being said... don't get me wrong - I think the current custom ROMs we have atm are MUCH better than what LG gave us as stock on this phone - but I'd prefer CM7 to not having CM9 at all)
 
Anniedroid said:
No disrespect intended - I'm just curious... has CM9 been abandoned?
I loved CM7... but I've seen nothing for months regarding any real progress with CM9.
It must be a real bear to port CM9 to the Esteem... but I was just wondering if it had been given up on... for now, at least.
(That being said... don't get me wrong - I think the current custom ROMs we have atm are MUCH better than what LG gave us as stock on this phone - but I'd prefer CM7 to not having CM9 at all)
Click to expand...

CM9 is almost a completely different beast than CM7, almost all of the builds I have used on more popular phones with much more developer support have some sort of problem, mainly the cameras don't work and various minor bugs, that being said it will be a while until a relatively bug free cm9 build will be available.
 
angryGTS said:
CM9 is almost a completely different beast than CM7, almost all of the builds I have used on more popular phones with much more developer support have some sort of problem, mainly the cameras don't work and various minor bugs, that being said it will be a while until a relatively bug free cm9 build will be available.
Click to expand...

Understood Angry... that's why I asked the question
 
PlayfulGod said:
on the kernel check my commits for when I first added the oc'ing to see what all I changed, or even sum1 elses on github. Off the top of my head you have to edit:

msm7x30-acpuclock.c
cpufreq.c - mainly to add cpufrq braodcasting so CM's cpu settings see em.
Kconfig
your defconfig

I dont know a way to merge linux stuff in windows lol

Now with CM7, basically take my device tree I used for CWM n created a gingerbread branch, then start adding the needed props etc and the product_copy_files lines needed. Create a vendor tree for the proprietary files from the stock rom, create/edit a extract-files.sh to pull those files (mainly for ease of others working with your repo n to not fill github up).

After that its eliminating what files ya dont need or can build from source. Having the src makes life easier if things just dont wanna work because if not you have to find others that will or hack what ya have.

simple eh? ;)
Click to expand...

it will be simple once I truly understand and know by heart what all the folders and scripts are for and how the build system gets all that stuff merged together with make files :) And as for windows, nothing android will probably really work cause it needs to be case sensitive (unless you install Windows Services For Unix, but that's a long shot.) . What I meant write console apps in windows, but be able to run them as linux console commands. I'm limited to using .net 2.0, but lemme tell you it's not very limited. To me most of this stuff just looks like repetitive work that could be automated little by little with the right set of steps. One thing i'd like to do away with to start is the android kitchen for a single binary or two so we can add a line to a script to automate the packing process after a build from zImage + modules -> new zip in one step.
 
kanaida said:
it will be simple once I truly understand and know by heart what all the folders and scripts are for and how the build system gets all that stuff merged together with make files :) And as for windows, nothing android will probably really work cause it needs to be case sensitive (unless you install Windows Services For Unix, but that's a long shot.) . What I meant write console apps in windows, but be able to run them as linux console commands. I'm limited to using .net 2.0, but lemme tell you it's not very limited. To me most of this stuff just looks like repetitive work that could be automated little by little with the right set of steps. One thing i'd like to do away with to start is the android kitchen for a single binary or two so we can add a line to a script to automate the packing process after a build from zImage + modules -> new zip in one step.
Click to expand...
you lost me lol, Are you talking about when building a kernel n then building a bootimg.zip? If so I can do that in 2 steps nows. I have 3 sh scripts, 1 to build the kernel, 1 to build modules and 3 to install modules to my determined modules dir. When I need modules (only need em when u add something and set it M to build as a module or when/if you change the versioning of the kernel) I just run 3 scripts with one cmd like so:

Code: 
./build_kernel.sh && ./build_modules.sh && ./install_modules.sh

then I have to then copy the modules to where I need em.

IMO trying to automate that too much more isnt needed to me as the where/what I need varies to often.

I only use AK for stock ROMs so lol. CM packages it all as a flashable zip when compiled, AK not needed n shouldnt be.
 
Be patient guys. By the time we get jelly bean in our phones. Then CM9 will functionally released .
 
Hopefully lg gave us all the driver modules source for all the hardware. I haven't really looked one by one but if there aren't any pre-compiled binary blobs it should be possible to get it all working with some time and effort. If they did use closed source drivers (maybe opengl) ill have to call them to request the source, and when they say no lol, I'll look for phones using the same chip and try to take their sources or open source drivers from projects.

Let me know if you need anything driver,module, strange log error related pg. I know it takes a while just finding stuff and I'm not too good with github yet but I got time to debug.
 
You must log in or register to reply here.
Back
Top Bottom