Related
Will someone please help me in getting a kitchen set up for the Samsung Epic and at least have the paitence to teach me the basic skills of developing for Android and building ROMs for Android. (Like what is the stuff I need to know, and stuff that is essential to having a working Android ROM)
Please and thank you,
Korey
Whosdaman said:
Will someone please help me in getting a kitchen set up for the Samsung Epic and at least have the paitence to teach me the basic skills of developing for Android and building ROMs for Android. (Like what is the stuff I need to know, and stuff that is essential to having a working Android ROM)
Please and thank you,
Korey
Click to expand...
Click to collapse
Here are some links to get you started. There's a lot of stuff to learn, so my best advice is to be patience and lurk, read, and learn. I know nothing about your particular device, but much of this will apply.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
http://forum.xda-developers.com/showthread.php?t=633246
http://blog.coralic.nl/2010/01/28/build-eclair-aka-android-2-1-for-hero-from-source/
http://forum.xda-developers.com/showthread.php?t=622916
http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
http://forum.xda-developers.com/showpost.php?p=6738713&postcount=1
http://www.kandroid.org/android_pdk/index.html
http://android-dls.com/wiki/index.php?title=Main_Page
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
http://forum.xda-developers.com/showthread.php?t=641223
http://adrianvintu.com/blogengine/post/Colored-Logcat-Script-for-Windows.aspx
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://forum.xda-developers.com/showthread.php?t=623976
http://lukasz.szmit.eu/2009/12/making-your-own-rooted-android-rom.html
http://groups.google.com/group/android-kernel
http://groups.google.com/group/android-building
http://groups.google.com/group/android-porting
http://groups.google.com/group/android-developers
http://groups.google.com/group/android-ndk
http://groups.google.com/group/android-platform
Look for the sticky thread by Cyanogen in this forum called "some advice". Are you looking to build roms from source, or just modify existing roms?
Do you know any Java or C?
Building roms may seem fun, but it takes research and patience. Lurking github commits, textbooks, and the forums is a great start. The community is very eager to help, and that's one of my favorite parts about android. But deving shouldn't be as simple as copy paste. Where's the fun in that?
I understand where you're coming from though, I was the same way a few months ago. Built a rom from source, posted it, then realized how uninformed I was.
I am now improving my skillz by reading textbooks on Java ("Head First Java") and C ("The C Programming Language"), both available as pdf documents. I'm mucking around in kernels and am going to start writing apps as well. Its a good place to learn the framework. You could also get into theming, but that requires a little graphic design know-how.
Good luck man, and have fun with it
Sent from my Nexus One using XDA App
Me too would like to learn more about creating ROMs for android (Galaxy S I9000 here)
I do have java experience (quite a lot, actually) but I really have no idea where to start when creating a ROM
thanks
Did you ever get a kitchen going?
Hi Mods, i am a Android user who has been playing around with Android devices for almost a year now, putting ROM's and Kernels, etc on my devices. I had a Mytouch, Galaxy S 4G, and Asus Transformer. Unfortunately, i don't have time to read through all the threads and develop ROMs etc, and i do appreciate all the time and effort that the developers put into it. I am just a normal user who would like to utilize the full potential of my devices (and like to show Apple users how we can kick their A$$e$. I had a thought recently. It would be so useful to all the regular users to have a BIBLE, that gives us the general steps of rooting, installing roms, definitions of terms and abbreviations, and different mods. It doesn't need to be device specific (or maybe it does). I believe it would help everyone out a lot and help bring some uniformity to the world that is Android.
I hope someone would consider this wholeheartedly. And again, BIG THANKS to all the developers!
Yes, I too think that this sounds like an awesome idea. Something like a wiki from xda-developers. With real noob tutorials and introductions. That way, people who are interested in diving deeper into that have a starting point and xda has a recruiting effect. For example I myself would love to learn about developing from scratch because weeks ago i started my studies where I learn java and c++. Having to search for every tiny bit of information is just annoying...
theres already tutorials out there on some basic things...
Yes sure there are some tuts but nothing like a compendium..
Sent from my HTC Sensation Z710e using XDA App
Hey!
A while ago I got the idea of learning how to cook roms.. I made some research on it and I found some helpful stuff on xda. Well, I tried but quiet didn't understand and manage to be successful in doing what was told there..
I've read lots of stuff like "The hardest part of developing roms is getting started". So I guess this is the part where I need the most help
Whatever, the reason why I opened this thread is that I wanna hear some developers. Their ideas on developing; How to get started, their short story on how they started developing...
Basically I wanna learn where/how to start from those people who experienced and managed to become a developer..
I mean, I wanna know your stories as I really think they will help me, they will be examples to me...
Well, not only me, to anyone who reads them.. I'm hoping that this thread will help other newbies like me...
Thanks!
My first android phone was the g1, didn't install CM until the myTouch on t-mobile. I started writing scripts for android phones. Little ones, like LCD Density script or apk removal. Then worked on a theme. Didn't really go anywhere. Fixed a bug for Salvagemod for the Evo, then started working on SalvageMod. Evo needed a kernel after support was said and done, I figured out how to compile it, looking at other commits, I was able to make changes successfully to the Freedom Kernel for the Evo. Then decided that I wanted to work on some gui application. Cmcompiler came about.
While there are many many more details from start to finish. Point is really, that no one is going to teach this to you. You have to want to learn, and you simply have to do it. Its hard work. I have spent hours and hours of messing with things to get them to work correctly. Trial and error is a great way to learn android. Sadly "Android" isn't the only thing you have to learn when it comes to development. You need to learn the tools that come with the development, like packaging or install script if you have a local gui application, or git/svn/bzr for version control systems. Most importantly, you need to have fun learning. If you are not having fun. Quit.
I do not feel attracted when you ask devs to answer, but still.
I started with XDAs kitchen.
No development ofcourse, but a good place to start.
I felt XDA kitchen was not enough, so I started to learn BASH - the scripting language in wich Kitchen is written.
I started with opening the "menu" file out of the kitchen.
After a while, I neede batch-resize, as I wanted to become a themer.
I made it together with my dad.
After I saw that some themes contain more items then another, I made CopyFrom.
AndroidCentral was my next idea - a combination of all home-made tools.
Just like lithid, I felt a GUI was needed.
But I started to work on it for cross-platform usage.
Conclusion: writing scripts is a good way to start. Google is my best friend, as I am new to scripting also.
Good luck
Sent from my Galaxy Nexus using Tapatalk 2
To echo the sentiments of the two previous posts by lithid and mdroid, I also started by writing simple scripts and small projects. Android Utility was my start up project.
My first real projects involved Rosie (HTC Sense launcher) and theming it. Then it become modding the apk to do other things (remapped, 4x5, 5 column app drawer, transparency, etc). The process of learning how to theme and mod one apk really helps you learn.
My recommendation is to pick one particular aspect of your device/Rom and learn as much as you can about it. You will find quickly that by doing so you inevitably have to learn how to use the Android tools, scripting, BASIC programming fundamentals, and a general idea of how everything works.
And yes, Google is your friend. Also stackoverflow
Sent from my PG86100 using Tapatalk 2
I also wanna to start developing. Thanks the infos. Can you write a few standard dev-tools name?
Sent from my ZTE Blade using XDA app
After creating this thread and reading the opinions of developers I followed this tut and tried this kitchen.. Helps in modifying a ROM.
And as I already had Cygwin installed using the way shown in the above tutorial I tried this tool for modifying the boot.img..
And if you want to modify apps you can give a shot to this tool...
These tools are basically really easy to use and efficient. Especially for a newbie like me.
oh, and these words of cyanogen would be really helpful..
start developing is not easy...but if you really want it and can dedicatebtime and patience all will just be fine... it's not recommended that u try to do all at first...maybe just a mod can be ok for you or anyone starting here...try modding a rom,changing stuff,adding tweaka and playing with build.prop as well...then if all goes right u can think on modding more stuff like apjs,themes,including simo comex apks...those who needs extra settings,etc... you'll gain xperience as long as time goes on and will fibd lot of interesting stuff u'd like to invlude on builds...so don't rush...good roms need time and patience
Sent from my MB860 using XDA
Thanks! when I read your ideas, telling me to play around with a rom and all that. I feel that Im really lucky. I've already been playing around with the ROMs I've used so far.. like editing build.prop, basic theming, editing apks, I once edited framework-res.apk to enable the navigation bar, etc...
Yesterday I tried porting MIUIv4 on the cm9 for for my device following some tuts on xda.. I did everything right, but no luck I get stuck in boot logo... Whatever I'll not give up!
I'm planning to study those kitchen stuff more for now, I'll give a shot to the tutorial mentioned on the portal today..
Whats your device?
My next plan to modding a ROM. I read also the MIUI porting thread, that's not hard. A long time ago, with my previously phone, the Xperia X8 (miss you...), i tuned up the stock ROM and modified a cooked ROM for myself - without XDA. I registered after here.
Sent from my ZTE Blade using XDA app
LG GT-540 optimus
I know. Its really easy. Plus I tried to port MIUI by mikegapinski on cm9 by miroslav_mm.. both roms are developed for GT-540.. I do everything right but I get stuck...
I don't what to mod, I mean I don't have any ideas... so Ill try porting MIUI
Hey bro. My advice? Do some heavy softmodding first (Take lets say tejas rom and add themes, adjust framework, add tweaks, add custom animations.custom this custom that basically add what you think is nice and yeah after long you will get more and more weird ideas )
This thread will be more like an advanced user/development "bible", to help keep the threads I am linking to clean, and to put all the information in one place. This information will also be put in the advanced section of the amaze bible doc, and also the WIKI we are working on.. I want to make sure anyone who wants this information has NO problem finding it!
I've seen a lot of people who have been making comments about "wanting to learn" at the same time that I am seeing the developers/contributors in these forums start offering "how-to's" for some of the more advanced functions.. I've also seen some comments from users who have not made any significant/consistent contributions - the secret they may not be aware of, if you can successfully read and understand enough to do the stuff we do in these forums, then YOU can take that to a new level.. and offer something back.
I will update this thread with some of the different threads/tutorials that already exist, and I would like to see people give feedback on the types of information that might be useful.. instead of just propositioning people who already develop, who may be busy with other things - let's crowd source some of our own development, after all, we all started somewhere..
Everything here, and all those how-to threads will be added to the amaze wiki - which will eventually replace the current always up to date amaze bible(doc)(which we need help updating btw, anyone on XDA can help contribute by helping do THAT here). HINT: ANYONE can help contribute to our knowledge base in the wiki! Please do! Before you give negative feedback to any dev, I want you to ask yourself - what have I contributed?
First, the bible I already posted some Advanced Android 101: So you wanna go to the next level?
If maybe building from source isn't your thing, you could look in the Everything Development Thread which has an ongoing discussion about how to COOK(or customize) a rom, a good first step toward conquering bigger and better things.. if you want to give this a go, read that thread, ask good questions, and help us create a solid starting point for future developers!
Next, with the recent release of the source for the ICS kernel, there has been a lot of interest in getting that running - Here you can learn how to Build Your Own Kernel, and then you can easily find posts by several devs working on getting these kernels fully working.. currently the issue is getting WIFI working(which we knew might be an issue), but THIS is something that users can help figure out..
If you can setup the build environment for building your own kernel, then you can ALSO [TUTORIAL]How to compile CM9 for the Amaze 4G - if you can learn how to do this, you will learn the right questions to ask to research how you may contribute to the project..
This post I have posted many useful links to different guides for porting - no one guide is going to be perfect, but if you read them and try them out.. you will learn a TON, and maybe even have a successful port! Remember, porting heavy framework changes like AOSP, sense4, aokp, etc - some of it is kernel dependent and will require more than any guide can spell out.. trial and error my friends.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Are there any more development/advanced tutorials in the amaze forums I missed? Any in any other forums you have seen that are well written? Any questions you have about something not covered can be asked here, but please post in the relevant thread if your question relates to it! I would really like this thread to be more for feedback about what we can help YOU do, so if you have any suggestions/questions regarding how we can help you do that, please post!
This post will have some of the related but not easily categorized, random information I find in the future..
Man I really want to start but my computer is way to sluggish
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
eggydrums said:
Man I really want to start but my computer is way to sluggish
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Well, compiling is processor intensive, even if the computer is sluggish, a semi-decent processor and a fair amount of ram do all of the work once you finish.. and there is stuff in the bible for customizing themes and more under Advanced Android 101: So you wanna go to the next level? Then there's the Everything Development Thread, that doesn't require a powerful computer at all, you're just switching out files before flashing.. and I am going to start posting some of the stuff I've learned in there soon too!
If you have anything you'd like to see, or anything you might have to offer.. feel free to post it
http://forum.xda-developers.com/showthread.php?p=28647619
Would this help? Found it in One S forum... but idk jack about developing (way to much work for too little result) so idk if it helps
Sent from my HTC One S using xda premium
glacierguy said:
http://forum.xda-developers.com/showthread.php?p=28647619
Would this help? Found it in One S forum... but idk jack about developing (way to much work for too little result) so idk if it helps
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
You mean the video it links to? That is all I got in the xda app.. if the video has anything new it could be added to the everything development thread, they were working on instructions there for using dsixda kitchen..
Sent from my HTC_Amaze_4G using xda app-developers app
I just want to learn to develop rom so that I can contribute to this amazing sight. I asked in the g 2 forums and not once did I ever get any help. Super savvy with computers modding well at least flashing that is haha. But I know with a little guidance I can be a big contribution to the site. So any words of advice would be great and some links to guides will be even more great haha. Thank you so much in advance
Sent from my HTC_Amaze_4G using xda premium
Spastic909 said:
I just want to learn to develop rom so that I can contribute to this amazing sight. I asked in the g 2 forums and not once did I ever get any help. Super savvy with computers modding well at least flashing that is haha. But I know with a little guidance I can be a big contribution to the site. So any words of advice would be great and some links to guides will be even more great haha. Thank you so much in advance
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Well, first, go into different roms, and look at their changelog - see if you can figure out what they are changing - don't just look at the roms in these forums.. look in other forums too. Download a rom, look at the updater-script to see if there is anything there that is making the change in that you saw in the changelog.. look at the files the updater script specifically sets permissions for(if it does), as those files are usually modified, hence why they have to set permisions.. look at the /system/etc folder.
Get a program like winmerge(I think that is what it is), or filemerge for mac, or some other program that will compare files AND directories line by line.. compare a stock rom to a modified rom- as long as it compares directories too, it will output which files the stock rom didn't have, which have been changed, what has been changed- THIS is the easiest way to figure it out for yourself. Piece by piece.
For example, right now I am trying to figure out why the custom kernel here isn't changing my clock speed - if I unpack the zip file, I see he has replaced the init.qcom.post_boot.sh file, and if I compare that with the stock rom, or the energy rom I am using, I see he commented out the lines that change the frequency.. so I look at the updater script, the aroma_config file, and each file tells me what it is doing.. I see the badass.sh file creates a file called 89badass in the init.d folder.. part by part you can figure out exactly what he was doing, how he was making the changes.
There is no real "guide" that is going to help as much as finding a way to figure it out for yourself.. programs like filemerge and winmerge are free and easy to find, and DEFINITELY give you a good place to start. Technically making your own rom is just making changes to a stock rom until you are actually reCODING something - but those changes can be pretty huge and technical, and do awesome things.. you just got to figure out what they are, and how to do them.
Everything above should give you a good place to start..
Silentbtdeadly said:
Well, first, go into different roms, and look at their changelog - see if you can figure out what they are changing - don't just look at the roms in these forums.. look in other forums too. Download a rom, look at the updater-script to see if there is anything there that is making the change in that you saw in the changelog.. look at the files the updater script specifically sets permissions for(if it does), as those files are usually modified, hence why they have to set permisions.. look at the /system/etc folder.
Get a program like winmerge(I think that is what it is), or filemerge for mac, or some other program that will compare files AND directories line by line.. compare a stock rom to a modified rom- as long as it compares directories too, it will output which files the stock rom didn't have, which have been changed, what has been changed- THIS is the easiest way to figure it out for yourself. Piece by piece.
For example, right now I am trying to figure out why the custom kernel here isn't changing my clock speed - if I unpack the zip file, I see he has replaced the init.qcom.post_boot.sh file, and if I compare that with the stock rom, or the energy rom I am using, I see he commented out the lines that change the frequency.. so I look at the updater script, the aroma_config file, and each file tells me what it is doing.. I see the badass.sh file creates a file called 89badass in the init.d folder.. part by part you can figure out exactly what he was doing, how he was making the changes.
There is no real "guide" that is going to help as much as finding a way to figure it out for yourself.. programs like filemerge and winmerge are free and easy to find, and DEFINITELY give you a good place to start. Technically making your own rom is just making changes to a stock rom until you are actually reCODING something - but those changes can be pretty huge and technical, and do awesome things.. you just got to figure out what they are, and how to do them.
Everything above should give you a good place to start..
Click to expand...
Click to collapse
I'm gonna start trying to figure this out before my first android I was totally computer retarded my parents died when I was 14 and I had to quit school and start working so at 32 yrs old now this is pretty tough so thank you for trying to help folks like me learn and keep up with all this new technology. I think I'm starting to get it a little reading goes a long way.
sent from one badass htc amaze with ics [email protected]
eggydrums said:
Man I really want to start but my computer is way to sluggish
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
i build kernels on an old laptop with a intel centrino duo, 512mb of ram, and ubuntu 10.04. if yours beats that, you will be fine (takes me 5 mins to build kernels)
ziggy46 said:
i build kernels on an old laptop with a intel centrino duo, 512mb of ram, and ubuntu 10.04. if yours beats that, you will be fine (takes me 5 mins to build kernels)
Click to expand...
Click to collapse
I assume ir runs windows xp?
Sent from my HTC_Amaze_4G using Tapatalk 2
EclipzeRemix said:
I assume ir runs windows xp?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
yup, and it has a sticker that says windows vista capable. WHICH IS A LIE!!!!
i got the laptop for free though. its a compaq presario v3016us. i think some ram was taken out of it before i got it. (im gonna buy 2gb soon)
quick question. How do I check the change log or is there a link to it or so I can use I think that's what I'm asking!
Sent from my HTC_Amaze_4G using xda premium
Over the past couple weeks every waking moment of spare time I have had I have used reading any article, watching any movie, browsing any forum thread I have found on the topic of custom rom development and I think I'm getting close to where I can begin my first build. If any of the users here can point me to any helpful links to help me with this I would greatly appreciate it. Now, onto my question. This is probably considered pure sacrilege but I was just curious on the matter. I was wondering, lets say I was wanting to port the new ToudhWiz over to our device would this be possible. If it is possible how difficult is it going to be and is it a project a beginner developer could ever hope to accomplish?
Onto my second question. I have been waiting ever since I got the DNA to see an Ubuntu Touch port for it and have got to the point where I don't believe I'm ever going to see it happen. Is this due to it being harder to build then lets say a AOSP based Rom or is it because not many people in our community here seem to care if it happens or not? The reason I'm asking is because after I get a couple Roms compiled from the simple FAQs I have been able to find and have figured out kind of what I'm doing I think I would like to try to port it over. Once again, ANY and all help is greatly appreciated, whether it's just links to other sites that has helped the developers here get to where they are or even someone wanting to help me learn personally. I have the upmost respect to all of the developers on this site and want to be able to consider myself among this elite group very soon. If I have posted this in the wrong place let the mods move it and let me know of my mistake.
Sincerely,
DrewHamm974
As someone who is fairly new to android / Rom development. Its something that takes a bit of time. I started small by just learning how to compile from source to figuring out how to get it set up to work on a device that already has support to eventually bringing roms to this device when they weren't supported.
I'm no expert but also knowing a programming language like C, C++, and Java will help.
Xda-university.com has some stuff on Rom development.
As for porting TW probably won't happen. Ububtu touch good luck... You will need either someone to do kernel work or learn how to dev a kernel first...
Sent from my dlx using XDA Premium HD app
.torrented said:
As someone who is fairly new to android / Rom development. Its something that takes a bit of time. I started small by just learning how to compile from source to figuring out how to get it set up to work on a device that already has support to eventually bringing roms to this device when they weren't supported.
I'm no expert but also knowing a programming language like C, C++, and Java will help.
Xda-university.com has some stuff on Rom development.
As for porting TW probably won't happen. Ububtu touch good luck... You will need either someone to do kernel work or learn how to dev a kernel first...
Sent from my dlx using XDA Premium HD app
Click to expand...
Click to collapse
First off I would like to say thank you very much for answering my question. Honestly, I was hoping for an answer from you, Pio, Palmer, or amit_sen. I am currently running CyanFox and must say it is awesome. If I could be bold enough to ask, why would porting TouchWiz not work? Is it due to something about it being a proprietary rom or is it something in the source that won't compile for anything but a Galaxy phone. The reason I am asking is due to the fact if I'm not completely mistaken I saw a sense rom for either the S2 or S3 not long ago.
Now onto Ubuntu touch, I thought all you had to have to port it was a working CM 10.1 build to get it working. Also, is there anywhere besides XDA University you could send me to help learning Rom and/ or Kernel development. Once again I greatly appreciate you taking the time to answer my question I idolize any devs that are on here freely giving their time and hard work.
DrewHamm974
Bump
DREWHAMM974 said:
Bump
Click to expand...
Click to collapse
I would recommend learning how to build CM 10.2. Once you have a working build, figure out how to build AOKP (or any other ROM without official support).
After that, you will probably have new questions.
Thanks will definately do.
Sent from my dlx using XDA Premium 4 mobile app
Touchwiz would be easy to get booting but almost everything would be broken. And because you can't actually compile touchwiz it makes fixing anything a giant pain. Ubuntu touch on the other hand would be relatively easy because you can compile it.
Sent from my HTC Droid DNA using XDA Premium HD app
If I remember correctly, Ubuntu touch is typically based on the cm10.1 kernel, for whatever it's worth.
Sent from my Droid DNA using Tapatalk Pro