It seems as if a lot of the reason people are hesitant to switch to froyo is the lack of custom kernels. custom kernels provide much better battery life as well as the ability to overclock as well as many other very useful features that create faster and more efficient operating system functions. From personal experience with froyo roms i have noticed the system to be quite slow compared to 2.1 and also i have noticed absolutely horrid battery life. We all know that these leaks may be far from complete but thats not to say that we shouldnt be making them better. It is obvious that Firon and noobnl have the correct information on this matter seeing as they have rooted all of the froyo releases inside of the zImage. If they were kind enough to share the information they have it would be very easy to either port our drivers to a i9000 froyo source or to use backported eclair libraries and use our current kernels. With this being said, I am very sure that this information could be the dealbreaker for froyo roms. With a good kernel comes a good functioning phone.
TO FIRON OR NOOBNL:
Please share your method of extracting the initramfs in order to quickly advance the development of froyo roms and to prolong the necessity for an updated source code
https://github.com/atinm/initramfs-utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
bubby323 said:
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
Click to expand...
Click to collapse
THANKS A lot man
You have tested this on froyo kernels? And technically if we used a correct froyo initramfs combined with a 2.6.29 kernel with backported eclair libraries for certain hard/software aspects we should be able to acheive an eclair kernel on a froyo rom. Ive done it before on other phones
the jump from .29 to .32 is a massive one, but all the power to ya...
shabbypenguin said:
the jump from .29 to .32 is a massive one, but all the power to ya...
Click to expand...
Click to collapse
Ive done it on evos/nexus' and i can confirm that its been done on galaxy s phones. it may be a massive jump in version number and overall base code. but as far as android and our devices go it really hasnt changed too much. actually i can almost guarantee that it will boot just by swapping the kernel inside the zimage. but to get camera and other functions requiring updated drivers we would need older libraries. or we can just patch our board specific files onto a i9000 kernel. but hey. doubting is more fun than doing
bubby323 said:
https://github.com/atinm/initramfs- utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
Click to expand...
Click to collapse
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
help
EnVolved said:
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
Click to expand...
Click to collapse
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
If you want better battery life editing the initram isn't going to do it.Your gonna need kernel source to play with to be able to do anything about battery life.
justlovejoy said:
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
Click to expand...
Click to collapse
There should be only one way to use that script to extract.
./extract_initramfs.sh zImage
and here's the header from the repack script.
usage : ./repack.sh [kernel] [initramfs_direcotry] [kernel source dir] "title of build"
example : ./repack.sh /data/android/initramfs-utils/zImage /data/android/captivate-initramfs /data/android/linux-2.6.32 "title of build"
These are fairly simple shell scripts that only appear complicated because of the use of grep.
Related
Alright, may seem like a stupid question to some. I've searched trust me. Whats the difference between flashing a new version of android and using a new zimage?
For instance, Im using "FROYO BUILD BY dan1j3l" and using the 25/7 zimage. Whats the difference between using that and the for example "Froyo 2.2 Android Build by Parad0XUA" with the same zimage or darkstones's 26/7 new froyo build?
Im guessing that functions wise, it depends on the zimage but stability wise on the version of android? can anyone enlighten me?
Julian2103 said:
Alright, may seem like a stupid question to some. I've searched trust me. Whats the difference between flashing a new version of android and using a new zimage?
For instance, Im using "FROYO BUILD BY dan1j3l" and using the 25/7 zimage. Whats the difference between using that and the for example "Froyo 2.2 Android Build by Parad0XUA" with the same zimage or darkstones's 26/7 new froyo build?
Im guessing that functions wise, it depends on the zimage but stability wise on the version of android? can anyone enlighten me?
Click to expand...
Click to collapse
Look at it this way:
New ROM=new UI
New Zimage=new version
Basicaly...when you update ROMS you are giving a total update to your phones UI and when you update Zimage...you are only updating the file that tells your phone wich version of Android to use.
Hope this answers your question
this means theoretically speaking, darkstone's newest build with the same zimage would be better than dan's froyo(one of the earlier ones) with the same zimage?
I hope I'm right. Thanks, it has cleared some of the doubt in my head about this matter
Julian2103 said:
this means theoretically speaking, darkstone's newest build with the same zimage would be better than dan's froyo(one of the earlier ones) with the same zimage?
I hope I'm right. Thanks, it has cleared some of the doubt in my head about this matter
Click to expand...
Click to collapse
yeah thats right mate, plus prob has better drivers or new things that have been solved so it will be smoother
Demon_man said:
yeah thats right mate, plus prob has better drivers or new things that have been solved so it will be smoother
Click to expand...
Click to collapse
Oh alright, thanks guys
but how can i solve the robotic voice problem in android?? :S i cant talk with android...
Julian2103 said:
Alright, may seem like a stupid question to some.
Click to expand...
Click to collapse
LOL, was wondering the same thing myself
just to add something...
have you ever heard, when speaking about linux, the words "distro" and "kernel"?
well, a distro (like ubuntu, mandriva, red hat) is the "whole world" built around the kernel, that is the same in all distros (if you keep it to date and recompile it).
The kernel is "the real thing", the way the os can "speak" to the machine and the HW.
Well, the Zimage is the kernel, the "rom" is the distro.
In other words, once you have chosen the "distro" (the rom) you like, you could only keep the kernel (the zimage) up to date, in order to have the newest features and the hw working (eg the last zimage solves the panel problem, it was not "slleping" while in sleep mode. One of the future zimages will add the gps support)
Hope to have semplified ...
@victorbd :
have you run crlcad?
it usually solves the sound problem.
Have you the right radio (.50 and better above .08)?
if yes to the previous questions, try a different ROM (WM ROM)
Very helpful,
Thanks
devilman said:
just to add something...
have you ever heard, when speaking about linux, the words "distro" and "kernel"?
well, a distro (like ubuntu, mandriva, red hat) is the "whole world" built around the kernel, that is the same in all distros (if you keep it to date and recompile it).
The kernel is "the real thing", the way the os can "speak" to the machine and the HW.
Well, the Zimage is the kernel, the "rom" is the distro.
In other words, once you have chosen the "distro" (the rom) you like, you could only keep the kernel (the zimage) up to date, in order to have the newest features.
Hope to have semplified ...
Click to expand...
Click to collapse
Very well put. Thanks
devilman said:
just to add something...
have you ever heard, when speaking about linux, the words "distro" and "kernel"?
well, a distro (like ubuntu, mandriva, red hat) is the "whole world" built around the kernel, that is the same in all distros (if you keep it to date and recompile it).
The kernel is "the real thing", the way the os can "speak" to the machine and the HW.
Well, the Zimage is the kernel, the "rom" is the distro.
In other words, once you have chosen the "distro" (the rom) you like, you could only keep the kernel (the zimage) up to date, in order to have the newest features.
Hope to have semplified ...
Click to expand...
Click to collapse
Wonderful and simplicity example.
Thanks!
Sent from my HTC Desire using XDA App
right boba, i was tempted to add something like this to my explanation, but i decided it would have confused more...
so, just to summarize everything, what boba is rightfully saying is that the right combination is a rom written for the zimage that it uses, so that it can really make "usable" all the features the zimage is able to "drive"
this said, usually (but not always) updating the zimage is enough to have the new features
The android version used in these buids, extracted from other pdas like the Desire, in fact, is able to use all the feature the phone has, but sometimes it cannot use them because of the zimage that is not able to drive the hw (think about the gps at the moment)
So, when speaking about android and hd2, usually updating the zimage is enough (the developers tell us when it is not enough)
victorbd said:
but how can i solve the robotic voice problem in android?? :S i cant talk with android...
Click to expand...
Click to collapse
Well Victorbd, since day one I have also had the robot voice problem. Today I flashed a different WM rom onto the phone, and now the robot voice is gone. Volume is rather low, but I am sure this will be resolved sometime in the near future.
Here are my settings, hopefully they will help.
#1 The Phone is a US T-Mobile HD2
#2 The WM ROM is OzROM 4.40 WWE
#3 The Android build is Darkstone HD2 Froyo V.1
#4 The zImage isCotulla zImage 7.25.10
Now I just have to find a solution to the sleep of death.
Good luck boss.
intoxic8ed said:
Now I just have to find a solution to the sleep of death.
Click to expand...
Click to collapse
You might want to trying the previous zimage 7/23. The 7/25 gave me wierd wake-up issues. I could still wake it up, but it required two power button presses.
Now, here's another stupid question... I'm using the 7/23 zImage as I've heard of all the problems people are having with the 7/25. When the next zImage is released, assuming it's as stable as 7/23 (which has been perfect for me), when I replace the zImage, do I essentially have to re-setup my Android build? Because I've literally gotten it to where I use it as my daily ROM. I'm literally having no problems other than VERY occasional 3G/Data loss but even that works most of the time. Will just updating the zImage leave all my settings/apps/etc...?
You just to back to WMo, plug in to your PC, take out the old zimage and put in the new one, restart Android. Should things work worse than they did with the old zimage, just reverse the procedure.
Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether. I looked around and found a thread that has patch to enable it for the DI28 system. It is a zimage file 4.3 mb, there is also a zimage in the rom of 5.5 mb (located in /kernel/update/) Would it be possible to replace the 5.5 with the 4.3? Or would there be a problem because the smaller file was from a DI28 vs a DK28
warlar12 said:
Or would there be a problem because the smaller file was from a DI28 vs a DK28
Click to expand...
Click to collapse
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Koadic said:
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Click to expand...
Click to collapse
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
warlar12 said:
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
Click to expand...
Click to collapse
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Kcarpenter said:
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ive been staring at my computer screen and getting more and more confused...I can not find a program or a way to decompress the file. But apparently it is compressed by a zip program. And on the phone it decompresses it once you flash the rom. Other then that I have decided to call it a night on trying to find a way, (I am sure there is a way.) It is giving me a major headache lol.
The main problem so far is that the source has not been released. However I think it has in a way because it is on the rom, which means there is a way to get it off and mess with it. Just hasnt been discovered yet.
Its packaged by cpio I believe... Ill find something on it tomorrow for you...theres a dev thread that talks about it somewhere...but its probably not for the weak of heart or someone without a bit of kernel knowledge. Not sure how vast your skill set is.
Sent from my SPH-D700 using XDA App
warlar12 said:
Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether.
Click to expand...
Click to collapse
I haven't tried any of the Froyo leaks so I can't comment on whether the Froyo kernel has RNDIS support out-of-the-box or not. Once the Epic Froyo kernel sources are released I'll patch in proper RNDIS support if necessary.
Meanwhile, if it's the case that RNDIS can't be enabled in the stock Froyo kernel, then I'm afraid that nothing can be done to fix that without the kernel source code.
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes. So once I get some more knowledge I'll be able to compile my own.
Sent from my SPH-D700 using XDA App
warlar12 said:
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes.
Click to expand...
Click to collapse
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
warlar12 said:
So once I get some more knowledge I'll be able to compile my own.
Click to expand...
Click to collapse
A kernel can't be compiled without the source code, that's what we're all waiting for.
mkasick said:
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
A kernel can't be compiled without the source code, that's what we're all waiting for.
Click to expand...
Click to collapse
Ahh so really there is not a way to change it besides building a new one from source
Hi, as the topic states, does anyone know where i can download one and flash? my setup on my sig is current.
thanks
So you're trying to run the official kernel with a custom ROM? Why?
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
nomadman said:
why not? and what prevents me from running an official kernel? to OC and drain my batteries? other than that, what else?
Click to expand...
Click to collapse
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link. - http://www.filedropper.com/update3-e3671133717dsigned-opal-frg83-from-dmd64e3671133
Phateless said:
Because you can't OC is probably the main reason. The only other one I can think of is the random battery drain that some kernels experience.
On the plus side I can think of stability and battery life. Knock yourself out, I'm sure someone can post it for you.
I have the zip file for the 2.2 OTA but I have no idea where to find the kernel.
Here's a link to my dropbox. - http://db.tt/XHrvInZ
Click to expand...
Click to collapse
IMO, the current ROm im using (TheOfficial) is working wonderfully. I care less about overclocking since I don't play games and dont find the need for the applications I use to be overclocked. Also the UI response on the ROM is incredible.
You are right, until the other ROMs iron out the random battery drain, which I have experiences in both CM7 and pershoot kernels, i wont be using them because i do not like having to restart the phone every time after i charge. ezterry's current kernel always gives me the green screen. however, ez's older kernel doesn't, but I prefer running the latest unmodified kernel.
I'm satisfied using a non-oc kernel and would rather set the mim clock freq. to ~177.
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Phateless said:
Makes sense. If you can figure out how to extract the kernel from that zip I linked you to, you should have your kernel.
Click to expand...
Click to collapse
lol, thats my problem. I don't. I also have athe official OTA Froyo image for mt3g. but i have no idea how to extract and apply it to the current OS. Thanks for the offer though. i'll try to find a way to do it. was just hoping someone had a flashable official kernel laying around they'de like to share.
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
nomadman said:
I hit a brick wall. I guess i'll just stick with ezBiffTestKernel20101106-2708_S based on kernel 2.6.34.7. It's a bit old but it will suffice until i figure it out. At least I don't have to reboot every time I pull from the USB charger.
/edit
Btw, can anyhone remember that the OTA kernel version was?
Click to expand...
Click to collapse
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Phateless said:
Naw but you could always nandroid back to stock and look. If I could figure out how to delete my google account info from my nandroids I'd email one to you. I still have a few from my mt3g.
Click to expand...
Click to collapse
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
nomadman said:
thats ok dude. too much trouble on your part. gonna try out koush-AnyKernel-a09a6f1 or dsixda_Android_Kitchen_0.113 and see what i come up with. (fish'in). and im sure there's a ROM out there that doesnt have a modified kernel i can extract from. Just cant figure out how to get it from the offical OTA archive
Click to expand...
Click to collapse
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Shouldn't been since the kernel code is open source, but I'm not sure either. I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Phateless said:
Actually there might be a legal copyright issue with distributing oem kernels in custom ROMs. I don't know for sure though.
Click to expand...
Click to collapse
The kernel is open source. I dont think i have a problem there. Its gapps that we can not redistribute. i read that from CM forum.
DonJuan692006 said:
...I did find a guide to extracting kernel's from ROM's but it requires that you are either running Linux or are running Linux in a virtual environment.
Click to expand...
Click to collapse
thanks! if u can find the link again, i'd be grateful. im on a unix (Mac) environment, so i might be able to do it. if not on Mac, I already have vmware fusion installed and its not a problem slapping on the latest Ubuntu.
I did find a how-to on CM wiki that required a boot.img and fastboot to flash. also found one requiring zimage from a rom. but i could not find the zimage file from the TMO Froyo OTA. lol.
Here's what I was reading. Which is doing the boot.img method.
DonJuan692006 said:
Here's what I was reading. Which is doing the boot.img method.
Click to expand...
Click to collapse
nice! androidcentral was down for maintenance the whole time i was researching yesterday. thanks for the link!
nomadman said:
edit/
what may keep me from using an official kernel is the 15MB additional ram. however i was under the impression that if I had radio 2.22.27.08, and H-Boot 1.33.0013(d), it doesnt limit me from using any of the froyo kernels floating around. if im incorrect with my assumptions, can someone enlighten me?
Click to expand...
Click to collapse
Glad I happened to go back a page...
The official kernel is meant to go with 0013 and 28.25 so yes, you should still have the additional RAM, which this phone desperately needs.
2.6.32.9-g94b855e
[email protected]#1 is what my phone says and I just received the OTA update a few days ago. Hope this is what you were looking for!
I've been trying to figure this out all day. I actually have a linux installation already but none of the download links for the perl files work. If you have them please upload them somewhere and I'll make us a flashable AnyKernel update.zip.
I've been trying to follow this guide: http://forum.xda-developers.com/showthread.php?t=667923 but none of the android-dls.com links work
hey? so there is much buzz about fugumod kernel blah blah
so as a noob representing the noob g3 users community [i hope there are some other than me]
my questions:
q1,differnece b/w rom and kernel??
q2,how to use one??
q3,if it overclocks then does it drain battery too fast??
q4,are they stable and safe to use??
clarkkov said:
Hey.
I bought my first Android phone 5 days ago, so I'm a noob too
But I'm a Linux power user.
Kernel is the core of the operating system, it contains drivers, filesystem interfaces and APIs needed by computer hardware to function. Android basixally uses Linux kernel.
ROM is short for read only memory, this is where the kernel and user interface (the pretty menus, homescreens, icons etc.) are installed. The propper name for this would be OS, but on phones people call in ROM, because of the place where it is installed.
Higher clock speeds require more power, more power drains the battery faster.
I havw not tried Fugumod kernels personally, although I am tempted to. It should be safe, but the only way to know that is trough extensive testing. The normal one seems safe, but no OC there.
These are simplified explanations for noobs, there is much more to it, but for gods sake, Im typing this on a 3.2 inch screen!
Sent from the other side
Click to expand...
Click to collapse
Pretty much the required anwser, but also dont forget this:
There is still bugs and problems with the OC version of fugumod kernel,cuz its stiil being ported to our phones.
Also only overclocking does not help for performance boost, We need to put JIT and COMPACHE, making more difficult to install if you don't know what are you doing.
Also, according to some user that tested OC, some phones cant be overclocked to 1.3 ghz or less making the task pretty risky...
The best we can do is wait until a custom rom adds this kernel to prove this.
Giosiken said:
Pretty much the required anwser, but also dont forget this:
There is still bugs and problems with the OC version of fugumod kernel,cuz its stiil being ported to our phones.
Also only overclocking does not help for performance boost, We need to put JIT and COMPACHE, making more difficult to install if you don't know what are you doing.
Also, according to some user that tested OC, some phones cant be overclocked to 1.3 ghz or less making the task pretty risky...
The best we can do is wait until a custom rom adds this kernel to prove this.
Click to expand...
Click to collapse
So if a custom rom comes with a kernel,i guess it would be easier as flashing a is easy.am i right?or the process would change
Sent from my GT-I5800 using XDA Premium App
i have a few noob questions too
-to install fugumod 2.2, do I just flash it on top of my kyrillos 3.0?
-what is a fs.convert file and how do I make one?
-and lastly, what is ext4? How does it make it any faster?
eKulzz said:
i have a few noob questions too
-to install fugumod 2.2, do I just flash it on top of my kyrillos 3.0?
-what is a fs.convert file and how do I make one?
-and lastly, what is ext4? How does it make it any faster?
Click to expand...
Click to collapse
There is a topic on fugumod. Not the right place to ask but here it is.
-Yes.If everything goes fine no data will be lost.
-It is a plain text file made with Root Explorer or any similar app. Just rename it to fs.convert
-ext4 is a Linux filesystem, just like FAT or NTFS in windows. It is faster than rfs.
sent from my kyrillos' v.3 fugumod 2.2 BE oc'd JIT enabled nokia 3210
hey im trying to create a custom rom ive created a kernel from source and want to try it with a ics custom rom ill make xD first rom though i do have one question though, how would i have busy box installed and it already rooted on install would i need to just use a script? or just edit to the system folder? sorry new to creating custom roms
Also anyone know where i can get stock ics rom?
gears177 said:
hey im trying to create a custom rom ive created a kernel from source and want to try it with a ics custom rom ill make xD first rom though i do have one question though, how would i have busy box installed and it already rooted on install would i need to just use a script? or just edit to the system folder? sorry new to creating custom roms
Also anyone know where i can get stock ics rom?
Click to expand...
Click to collapse
There are Roms posted in the Dev section. ICS Stock also.
Your best bet, would be to look at the directory structure on some stock rooted roms, and also look at the updater script for them.
This will give you a good starting point on what to change in your script as far as BB and SU.
MD
Also, I highly recommend you look into the android build system.
Yes its complicated.
yes its hard at first.
but there is only so much you can do to mod an already compiled rom.
even with little coding experience you are able to do a lot when you have access to the source!
plus, if you fix something, you can submit it to have it fixed for everyone.
between this guide and our CM9 thread, you should be able to get started. we have some basic setup instructions over there.
gh123man said:
Also, I highly recommend you look into the android build system.
Yes its complicated.
yes its hard at first.
but there is only so much you can do to mod an already compiled rom.
even with little coding experience you are able to do a lot when you have access to the source!
plus, if you fix something, you can submit it to have it fixed for everyone.
between this guide and our CM9 thread, you should be able to get started. we have some basic setup instructions over there.
Click to expand...
Click to collapse
haa thanks ill take a look usually work with windows but getting into linux now that i run ubuntu and have an android tab