Related
I would like to start learning how to put roms together. I would like to start with developing a 2.2 rom compiled from galaxy s I900 source. Is there anyone here that can point me in the direction of a good tutorial on how to start? I have been using other peoples work for like a year and a half and would really like to create rather than use. I am a total noob when it comes to developing so any help would be great. thx
Go here;
http://forum.xda-developers.com/forumdisplay.php?f=613
Read a lot before you ask.
Good luck!
You can't develop a rom using only kernel source.
Sent from my SCH-I500 using XDA App
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
yutzyscott said:
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
Click to expand...
Click to collapse
All I have to say is good luck with that.
fallingup said:
All I have to say is good luck with that.
Click to expand...
Click to collapse
In all seriousness do you stay apprised in any way shape or form of android related news our just enjoy smearing the forums with your illinformed ramblings and negativity? Speak of what you know and don't be so eager to dismiss anyone with the fortitude to increase their own knowledge base on an operating system such as this when its these people who we all depend on to better our experience with said operating system. As it is these people for whom google turns to when it comes to ideas on how to better their future stock releases. Thank you for the vote of confidence.
Sent from my SCH-I500 using XDA App
You do realize fallingup has written more android code than your phone can hold?
The reason they seem testy is they(actual developers) have been spending all their free time trying to get Samsungs crappy code to compile, and every couple of hours some one asks for an easy how to guide for porting Froyo.
Spend some time reading the forums. Find out what is already being done, then learn the basics of rom development. THEN, ask intelligent questions on how help develop Froyo for our phones.
Asking for an easy way to cook roms is the equivalent of the kid in the back seat asking "are we there yet" every 30 seconds. If you really want to learn how to cook roms, try a couple easy ones with the kitchen I linked to, then learn how to work on roms without the kitchen. Then work on Froyo. There is no easy way.
I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing. As far as my last post I meant no disrespect to fallingup in fact it was my mistake to quote his post. I actually intended on quoting jt1134 so, to fallingup, I have used your stuff many times and have nothing but respect for what you do. I apologize for the misquote. I in no way think myself to be super genius to the 10th power nor do I believe that I can actually do anything worth while with this code. I'm just bored and want to learn. I'm also an Android addict.
P.S. Thank you for the link. Also you'll notice in my last post now that you know of my misquote, that I am actually 100% behind people like fallingup. I would never knowingly give a verbal bashing like that to him.(god I feel like **** now)
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
I'm tired. I'm generally a nice guy, sorry!
jt1134 said:
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
Click to expand...
Click to collapse
Now I have the right person quoted. Did you even read my post??? Let me repeat a key part so that you can understand and maybe you can stop battering the new guy.
"I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing."
I have admitted to my know nothingness. I simply want to learn. You could respond with something such as Galaxy S 2.2 is not a good place to start the learning process. Or you could have left it alone entirely and just thought that the link posted by "sgtmack" was sufficient enough. After all it did answer the exact question I asked. You might know a lot more about code and code writing than me but you have to admit, "your kind of an arrogant ass!" Now I would like to end this banter by allowing you to respond in whatever way you deem necessary. I myself will give this no further thought as I would like to move on now. That and I believe I have made myself look bad enough now.
As for fallingup and sgtmack, thanks for the hard work and helpful advice.
yutzyscott, do you not realize that jt and dirrk are the ones that got us the voodoo kernel? do you know they are the ones that got the kernel booting in the first place using samsung's ****ty source code? without jt, there would be nothing to build a rom around. wtf do you mean ill-informed when jt probably knows more than most people about developing for this phone? pay some ****ing respect for people that deserve it.
Yeah I do but, when this whole thing started I did not read who the post was by but, rather I just read the post. While I appreciate his work and am actually using it, my pride was hurt and its hard to interpret someones tone on a forum. I was under the impression in the beginning of all this that it would be known that I downloaded the 2.2 ota pushed to the original galaxy s and not the source they have been working with and making leaps and bounds with despite the road blocks. I was interested in learning how to port it (the ota I mean) rather than just sitting on my hands waiting to use anothers work. Chances are that I would never even come close to understanding what I was looking at but, I had to try. Now I'm sorry I asked. I quit...I was wrong, sorry! Leaving it to the experts. I'll go back to helping people with simple basic problems on droidforums.net and continue being an expert on using the real experts work.
This doesn't need to be turned into a flame thread. So here's my advice: join us on irc.freenode.net #samsung-fascinate and ask questions there. learn how to build a kernel, and maybe try to find out how exactly to port roms from other devices. Its a tough business, especially when we don't even get working kernel source from the manufacturer.
There are a ton of people that are working on the galaxy s phones, trying to get AOSP and the like on them. These phones are quite different than any other android phones, just with the way that the hardware / partitions are, so there is a lot to work through and document. Once one of the SGS phones is running aosp, im sure the others wont be too far behind. I wouldn't bother porting another crappy samsung rom, cause it will still have a lot of the crap that we are trying to get rid of by running aosp.
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
jt1134 said:
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
Click to expand...
Click to collapse
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thats always a good excuse
this was an entertaining thread lol.. misunderstandings is one of the biggest downfalls of online conversation.
Not meant to be offensive. Just funny. http://www.geekologie.com/2010/10/a_day_in_the_life_of_internet.php
Sent from my SCH-I500 using XDA App
Yes yes, this is a life story thread, but I want to chronicle how far we have come in the last few months, and the incredible teamwork this community has.
Around march, I got my Galaxy Player for the first time. With the galssy eyes of a techno geek unwrapping his new gadgets, I tore open the box, and beheld my shiny new toy, something, which I did now know at the time, that would take me far beyond my wildest dreams of technical success. Of course I bricked it withing the first 3 hours, "accidentally" deleting ALL the dalvik control settings from build.prop, and not having adb installed at the time, or even knowing what the heck Odin was, spent a merry 7-8 hours trying to get my prized posession back to it's stock state. I probably repartitioned and flash over 50 times that night, which was also when I flashed the INTL bootloader off of zaclimon's thread (little knowing that I would have a healthy partnership with him in just a few months), and thet next morning, I was back in business.
Of course I crack-flashed ALL the rom's there were for the 4.0 at the time. Klin's klassic, steve's, rooted stock, whatever I could find. I just couldn't help but feel slightly depressed that there wasn't really much of a dev presence for my new device, and I was more the enviously eyeing the 5.0's ICS builds. So I lurked for a few months, pondering whether I should even activate my dormant XDA account, scared that I was just too much of a noob to actually get help.
One day though, I took the plunge. I decided that I was going to try and get my feet wet in this "xda" thing, and maybe browse general, helping the occaisonal user in distress. Just 1 day later, I posted my first contribution thread, without even having 10 posts! The tweak guide for the Player, how proud I was of it. All the nice tweaks I had enjoyed on my TF and had discovered for my Gplayer, all there for my own personal quick applying.
2 days after that, I began asking klin1344 about ICS, as reading through some threads, I thought I heard some rumours about a secret underground build that may have been surfacing, as well as whether or not SGS (what is that?) tweaks can be used on our player. He pleasantly responded with the fact that no, there was no ICS, and he had never considered using SGS tweaks. Would I like to be his dev partner?
I will not lie to you, this FLOORED me. Little me, the noob who had maybe had is Gplayer for 2 weeks, and barely knew his way around the terminal, being asked by a dev to help him? Easily one of the proudest moments of my XDA career. I signed up immedately, we began discussing, and ended up coming to a mutual agreement that partnering may not be the best idea, as we both had differing opinions on what should constitute a ROM. He was going to let me support Klassic (my favorite rom), and he was going to start a SGSII themed rom (which turned into ICY fusion.
With joy in my heart, I learned the basics I needed from him (such as DD) and began applying all the tweaks I had from my tweaks thread into this rom. I decided to rename it "stratusrom", and include multiple releases. One beta, one weekly, and one stable. This was nixed completely as soon as I learned how hard devving could be, and after a few false starts that long time forum members will remember, and renaming it "stratusrom" and eventually "etherealrom" (hence the celestially-named projects that I am related to, if you guys wanted to know), I began devving. Not much happened here, I released a few iterations, guiding hands such as daniel644 and the dev zaclimon provided their amazing help to the poor little dev who could (me), trying to make a decent rom. At one point, I had a falling out with Klin (whcih I am sure most of you remember, that was a scary night for me, the little dev, being whaled on full-force by a senior-class dev, with both us us threatening to remove our work), but let's not dig up old bones. Long story short, I rethemed my rom, made it not-klassic, and just worked on it until about mid-july.
In the meantime, I was releasing a whole slew of threads documenting my research. Who knew that SGS roms could be easily ported, and that rom creation wasn't scary? I had a blast finding all of these things out, and even gained a small following during this time, as most development had died off, with klin never really getting his heart back into 4.0 development, tdm leaving, and Balor leaving his kernel for good.
Then it happened. I decided to spearhead an ICS initiative (as at the point, while I didn't even know what a compiler was, thought I was knowledgable enought to start something like that), to finally get it working. Ah, the good old days. Me, neyodmiun and zaclimon, swapping ideas, with the occaissonal user popping in to offer advice or to comment on our progress. Around this time, I also began getting support questions, and as I answered them nicely, and genuinely tried to help them beyond the normal "find my help post" and no response afterwards, and ended up getting a reputation as being someone who wouldn't blow off noobs (not that I am accusing anyone of doing so, but I know that some devs do not take users seriously at all). zaclimon offered up the idea of hiring a freelance dev, and that was ultimately accepted as our plan. Enter Oisis.
This is where most of you guys will know me from. With Oisis on board, we booted ICS on august 13th, and were in business after that. I formed a team aptly named "TeamSuperNova", and got to work learning what the heck GCC was, and where the vendor folder went. What's github again?
Not much to tell from here, as the rest is just history.
I want to thank everyone on XDA for making this journey possible. From klin1344, and zaclimon, to goldflame, and all the other users to have taken on the excellent role of support, so that we can work on what really matters, I think I, no WE have accomplished what we wanted. While our entire community is very small, we are all united as a TEAM, working together like clockwork. Some new user has an issue with cm9? The support team is on it right away, and we normally have their issues sorted out in a few hours. Someone wants to start development? Zaclimon, me, or any of the other devs quickly pop in and give them some advice on where to start, and some resources to use. Any PM that I get, however noobish or "silly" it seems, I answer, and most of the time I actually get it resolved. So don't be afraid to speak up and give your opinion or ask for help. That's what we all are here for. To help, and contribute, as much as we can.
Thank you XDA, users, and everyone for making all of this possible. Now that my speech is over, feel free to put up your own personal story, or just discuss.
Where did you actually start to learn to dev? I've been wanting to start and I asked Meticulus (if you remember him, he was part of the old dev family) and all he told me was "Read a lot " Not the best answer.
Sent from my YP-G70 using xda app-developers app
You are a great example of what xda members should be like, I also would like to try to follow in your footsteps as I just got my sgp two weeks ago to !
thank you hanthesolo for all your great work!
EcHoFiiVe said:
Where did you actually start to learn to dev? I've been wanting to start and I asked Meticulus (if you remember him, he was part of the old dev family) and all he told me was "Read a lot " Not the best answer.
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Well quite honestly, I just picked it up here and there. Devving isn't really something you "pick up overnight", or read a how to on. Essentially the best way to learn how to dev, is to do something horrible to one of your devices, and then try to fix it . I can't tell you how much I learned when I bricked my player for the first time. What's Odin? You mean cwm installs WITH the kernel? Just take you're time, try and Google anything you may have questions about, and ask devas anytime you have a problem (hopefully in pm). Other than that, my ROM creation guide may help you get started (although I really need to clean it up), and once you feel confident enough to start compiling, pop me a pm, and I will be happy to guide you through any questions you may have.
spartacus279 said:
You are a great example of what xda members should be like, I also would like to try to follow in your footsteps as I just got my sgp two weeks ago to !
thank you hanthesolo for all your great work!
Click to expand...
Click to collapse
Thanks for the compliment! I HATE it when devs get a superiority complex over their users, and basically refuse to talk to them/help them, or do so in an extremely condescending way, which hurts the community more than it helps, especially a small one like this.
To start revving, just refer to my response above, and pop me a pm whenever you need any help .
I've hard bricked my Player twice and I guess I know how to recover from any situation, I know all the things and headaches associated with bricking a player and such. But thanks for your reply!
Sent from my YP-G70 using xda app-developers app
This might not be the right place for this, but is anybody working on porting an ICS kernel to the photon? I do not know enough programming to work on a port, but I am looking forward to something happening. The guys over at the Atrix forum are working on a kernel and are getting pretty far quickly. I do know that the Atrix shares some hardware with our Photons, like the GPU, which I have read is one of the biggest drivers that we need to have a proper working ICS or JB port for our phones. Well hopefully this will point some kernel devs to a forum that could have great benefits to the advancement of our phones. Thanks to any devs that may already or decide to work on this kernel.
Edit: Here is a link to their GitHub: https://github.com/CyanogenMod-Atrix/android_kernel_motorola_olympus/
Did everybody abandon us?
Sent from my MB855 using xda app-developers app
Kernel Devs Wanted
I don't think we've been abandoned. I saw that Th3Bill was on Moto's sourceforge trying to get the sources we need, a rep at Moto is trying to help us but they do not have a time frame yet. I also think that once the Atrix kernel is closer to being finished more devs will jump onboard to get the kernel going for our phones. Really I made this thread to get some devs attentions that may have not known about the Atrix development going on. Until then I am trying to learn some C coding and trying to make heads and tails of how the Atrix guys got to where they are. I've only coded in Javascript and for only about 2 years now, so it's kinda slow going, but We Still Have Hope! Also if I can come across a cheap Photon that I can dev on it may help out a bit, I can't really dev on my only phone.
Maybe some useful info.
A PM I got from lehjr over at the Atrix ICS port thread :
"Porting the kernel as it is right now isn't advisable because you may not know if issues are a problem with the hardware being setup slightly differently, or a problem with the kernel itself. We are currently only in a very early alpha stage.
Porting the kernel once it is stable should be much easier, but keep in mind that you will likely have to refer to device-specific references in the GB source to make the required changes, since technical documentation for the Photon and Electrify seems to be very scarce to non-existent, whereas we at least have documented teardowns and a nearly complete schematic for the Atrix as well as a serial out port from the JTAG port. "
I know that this is not new info, but for the programmers that do not know where to start I think this is a step forward in the right direction.
We're getting close. Well the Atrix is getting close.
I keep following the thread over on the Atrix Forums http://forum.xda-developers.com/showthread.php?t=2016837 and it looks like their project has come together. They have marked almost every aspect of their kernel as Completed. If we still have any developers that know how to modify a kernel to port from the Atrix to our Photons it looks like the time is almost here. The one thing they have marked as "work in progress" is the fingerprint reader which we do not need. Well thought I would share the good news with you guys. A fully working ICS would be nice. Cheers!
i had always meant to do some developing but the drop in activity i realized when i moved from the sensation to the rezound really compelled me to start plus i have some work that i really have to do and really dont want to do so you know how it goes. Anyway to it
i started by googling how to build android roms which lead me to xda university giving me a nice expaination as to the various parts of android which i was already familliar
another search lead me to the offical how to build android from source page. i had a few concerns so i thaught i would ask here
i have knowlage building various web applications(php,js,ect) and not the let the fromework so this for me kinda apps i like thinking and innovating. i have a little experience with c++(i was at the stage of learning a gui when my old laptop crashed) so i think i have atleast good enough programming experience to catch on to java at a nice pace. Am currently reading and following googles nice little guid on developing android. Am in the process of setting up work envo (already got ubuntu 12.04 up). and thaught i would just leave a post here to see if anyone had any advice for me?
what i wanna do is be able to port for us,build original roms AOSP they call it for us, build and or port sense roms for us and eventually get to the point where i can get us sense5 or help neo(or any other dev) help us get sense 5. oh and i think i would like to build/modify kernels as well. oh oh and being able to invent exploits to get root or s-off for devices i might get in the future.
Question: while i was reading i was seeing where the buiding process was doing alot of synceing with google servers ect. i dont actually want to submit whatever garbage i might write to them while am testing so im still on the right track following the guid here correcto??
short version: I wanna build android custom roms ect not just edit files and put it out am i on the right tract following the guid here (i already know a lil programming)? http://source.android.com/source/initializing.html
any advice/resources/links welcomed
oki am on the page that says "building and running" i dont see anything for our device am guessing thats because development from aosp has stopped for us and thats where ppl like neo and cyanogen make thier magic. what is the next tut or read for me?
Try this. You could always pull Neo's CM 10.2 repos instead of the 10.1.
http://signatures.mobile-overload.com/wp-content/uploads/2013/07/sig-cm-5.png
Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Roarster31 said:
Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Click to expand...
Click to collapse
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
thewadegeek said:
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
Click to expand...
Click to collapse
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Roarster31 said:
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Click to expand...
Click to collapse
There is no hard/fast guide on what "rom-editing" is. Are you wanting to contribute to kernel development? Better know a lot of C. Wanna roll a cool application for a ROMs special settings? Java is what you want. What I'm getting is you know more Java, so why don't you write and application that you think will solve a problem, then talk to a developer about including it in their ROM?