Related
i got my kitchen setup.. for my first cook would this be the best ROM to start with?
RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.1
5.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.
exe ??
much thanks..
20twins10 said:
i got my kitchen setup.. for my first cook would this be the best ROM to start with?
RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.1
5.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.
exe ??
much thanks..
Click to expand...
Click to collapse
I, along with others, would suggest to start with the stock rom.
It forces you to learn the ins and outs of how things work and how to do certain mods and helps you just understand everything overall. but you can always choose to start with someone else's rom, but that doesn't necessarily make you a rom chef.
codybear said:
I, along with others, would suggest to start with the stock rom.
It forces you to learn the ins and outs of how things work and how to do certain mods and helps you just understand everything overall. but you can always choose to start with someone else's rom, but that doesn't necessarily make you a rom chef.
Click to expand...
Click to collapse
I have no problem getting into ROM's head first.. taking someone else work and reworking it to my own doesnt give me any gratification.. i'd like to be able to say "i made this work this way". yeah everyone is doing ROM's, will i ever release what i do, who knows.. i just know what i want..
i'm not looking into making the best ROM out or recoding till my eyes hurt.. I would like to learn the in's n outs.. And learn to implement some of the MODS currently out.
did some searching and i've come up with Stock Incredible Sense *3.26.605.1* (Rooted) by rmk as a base.. any better bases?
now that im thinking of it, i'll need to get the OTA's worked in from there..
much thanks for the info..
so as much as i want to dig into all this.. time isnt on my side.. my wife and i had our twin daughters back in october, and it's extremely difficult to find any kind of computer time. not to mention im not even back to work yet, and i have already obligated myself to my small record label and my interest in working for myself via real estate sales.. i may just need to let the ROM people keep doing what they do and i enjoy and support their work..
I've got thick skin so feel free to throw things.
Watching the forum over the last month I've seen a proliferation of ROMs to the point that I've stopped updating - also partly because my favorite and second favorite teams have stopped putting out new versions. I finally succumbed to the burning urge to try another ROM last night but ended up with buyers "meh."
The ROM environment has become so fragmented that it's hard to know what the advantage of ROM a is over ROM b other than appearance.
A comment from one of the ROM makers brought the problem into sharp focus. "I've renamed my ROM because I didn't know one of my team members already had a ROM named X."
How can you be part of a "team" and not know what's being produced by that team?
It seems like we've got more themers producing work in the form of full ROMs rather than themes. I've got nothing against themers, I love packages that can completely change the look of my device and I'm always on the lookout for cool new themes.
I'd rather see ROM maintainers and themers working together where the former group produces faster and more reliable ROMs while the latter group produces mods for those ROMs.
Do the two groups just not want to work closely together or are there predominantly just mostly lone wolves working at the ROM/theme level in Android?
Wrong section. Suppose to go in q&a (QUESTIONS and answers)
Sent from my SGH-T959 using XDA Premium App
I disagree because it's directly applicable to development and is aimed at the developers. It's not a general q/a question
I agree with this. There's no need to make a "rom" if you just change the theme. Just make a theme and zip it up then post it in the themes section. And oh yea I believe people refer to these people as "winzippers".
Sent from my HTC Glacier using XDA App
OP has a great point about our forum here. Ive really stopped doing anything but for my own use, and with the exception of a few real roms put here, I've watched our Vibrant area here turn into a rom porting paradise, without a lot of original work done by people calling themselves devs. Several of these self proclaimed devs have asked me for help with recent projects, and have then been unable to provide even a simple logcat for diagnosis. If someone cant pull a logcat or understand how to do other basics, you really need to take your time and learn.
It is okay to theme and do little things while you learn, and take the time to put out a quality product, instead of a hurried build thats half broken. We have a slight handful of true devs out here, and a whole bunch of people who want to learn, but seem to be in too much of a hurry to kang others work and not really learn how to build a rom from the ground up. Its a damn shame.
Ginger Clones of the World Unite!!! via the XDA App
I agree with Br1cK'd. There are a lot of "devs" lately that seem to be kanging together half broken ROM's. I can't tell you how often lately I've flashed something only to find major bugs, when the OP claims that the ROM is 100 percent working and bug free. It seems that most of the more skilled developers have moved on to newer devices. I'm all for people learning but they need to do a lot of quality control before they post their work on XDA.
are you tryna say my team member ferhanmm that did an error ? whats up with you son?>
But then... what actually constitutes a "Rom".
For as far as I know, according to CM6/7/Miui people, only theirs are truly "Roms", as they are built from ground up.
Everything else is just a themed stock Rom, or improvements to existing Sammy framework. (Which I still love btw)
If there were malicious Roms that are purposely bricking systems, then I would argue for stricter requirements for releases. But as it stands, I think the openness of this forum allows users and developers alike to find what makes them happy.
I just think in general, Rom devs/maintainers get more credit (Thanks button hits?) than purely themers. As there is a feeling that themers kind of "work for" Rom Devs... Which is why people tend to package their work as Roms instead of themes (So their work seems less derivative or what not)
Wrong section, but I agree.
Sent from my SGH-T959 using XDA Premium App
Br1cK'd said:
OP has a great point about our forum here. Ive really stopped doing anything but for my own use, and with the exception of a few real roms put here, I've watched our Vibrant area here turn into a rom porting paradise, without a lot of original work done by people calling themselves devs. Several of these self proclaimed devs have asked me for help with recent projects, and have then been unable to provide even a simple logcat for diagnosis. If someone cant pull a logcat or understand how to do other basics, you really need to take your time and learn.
It is okay to theme and do little things while you learn, and take the time to put out a quality product, instead of a hurried build thats half broken. We have a slight handful of true devs out here, and a whole bunch of people who want to learn, but seem to be in too much of a hurry to kang others work and not really learn how to build a rom from the ground up. Its a damn shame.
Ginger Clones of the World Unite!!! via the XDA App
Click to expand...
Click to collapse
first of all about the logcat ? did you learn alone ? i guess that if someone ask you, its nno bad to help is it ? because i bet some one showed you...now about the kang, so almost every rom here is a kang right ? almost all roms based on stocks from i9000s and stocks kb1`s isnt it ?... i guess this people have the right to learn, but seems you guys that already know a little dont like to help huh?
I have more than enough mods on my rom to constitute it not being a theme, and I don't know about you but I don't memorize every rom name out there. It sounded similar so I changed it, what's wrong with that? Since 2.2 has already been tweaked to the max I was able to put out a pretty stable version in the first post. Only things I can really do from here are make it more efficient and finish the theme which I plan to do but I just posted it. And it's my first rom so thanks for the encouragement.
I agree, the forum is filling up with "roms" that are just the same rom rethemed over and over and over again. What annoys me most are these self-proclaimed "devs" who take bits and pieces of other people's work and put them together for their own "rom" when they didn't really write any of it. Just take a look at their credits lol... It's a crazy long list.
I don't think there's anything wrong with having multiple ROMs. After all, everyone will like something different.
I think what the OP is saying though is that there are ROMs out there are essentially the same pieces with different theme, or maybe a new lock screen, and whatnot. I think the OP means little additions like that can be part of a theme or the theme & apps forum and could be added to any ROM and doesn't warrant releasing a new ROM under a new name and new dev.
jimmynguyen91 said:
I agree, the forum is filling up with "roms" that are just the same rom rethemed over and over and over again. What annoys me most are these self-proclaimed "devs" who take bits and pieces of other people's work and put them together for their own "rom" when they didn't really write any of it. Just take a look at their credits lol... It's a crazy long list.
Click to expand...
Click to collapse
as my partner said above, hell son you dont undestand, everybody uses tweaks that are made because there is no need to redo it...name me any rom you have created ? do you know about roms? dont be stupid
ColorNapkin said:
I don't think there's anything wrong with having multiple ROMs. After all, everyone will like something different.
I think what the OP is saying though is that there are ROMs out there are essentially the same pieces with different theme, or maybe a new lock screen, and whatnot. I think the OP means little additions like that can be part of a theme or the theme & apps forum and could be added to any ROM and doesn't warrant releasing a new ROM under a new name and new dev.
Click to expand...
Click to collapse
+1
Sent from my SGH-T959 using XDA Premium App
I did my first root about two month ago. Since then I have tried about 20 various roms or updates to them. I tried one last week that seemed to be a copy from an established developer. The other team got really pissy and used alot of immature slang when confronted. I will no longer use any roms from them. I agree that people should learn from the ground up before posting roms and stop the plagiarism.
I appreciate the hard work of the legitimate developers on this site.
Sent from my SGH-T959 using XDA App
ferhanmm said:
I have more than enough mods on my rom to constitute it not being a theme, and I don't know about you but I don't memorize every rom name out there. It sounded similar so I changed it, what's wrong with that? Since 2.2 has already been tweaked to the max I was able to put out a pretty stable version in the first post. Only things I can really do from here are make it more efficient and finish the theme which I plan to do but I just posted it. And it's my first rom so thanks for the encouragement.
Click to expand...
Click to collapse
dont pay attentionn to this ppl fer.. day just stupids ... look at thhe quote i made above.. its just stupid, they want us to redo the same **** that is already made... for example.. whats the need to do a gps fix when jellette made one already ? its just stupid
them may be half a$$ed devs but them gotta have donate button
Bosina & Br1cK'd, first, thanks for your input and participation but this thread isn't about helping or not. It's about packing up thematic changes and publishing them as a ROM rather than a theme bundle.
If a group of members wants to debate about newbies not giving as much as they get, please start a new thread.
bosina said:
as my partner said above, hell son you dont undestand, everybody uses tweaks that are made because there is no need to redo it...name me any rom you have created ? do you know about roms? dont be stupid
Click to expand...
Click to collapse
this dude ha ha shut up im trying to read and your comments are unnecessary and full of hate and You act like You are a Big Time developer who dont take s**t from anyone , go smoke something and relax , i dont see Team Whisky complain or Eugene, just You big time savior .
But if the teams join there will be more people to split the donation money between so maybe thats why people stay separate ?
Hello I'm a newb!
I'm sorry, but this is the unfortunate state I find myself in.
When I first found this site, what I was expecting to find was a ICS for my phone. I could not have guessed what I would learn here. I had no idea I had a counter in my phone to worry about when installing open sourced roms? Next after much more reading I am to learn the source code Google releases is not complete, and uses binary drivers? Now I am to learn about CIQ, and my phone is spying on me? Wow!
Before I say anything else I want to express my thanks to this community. This has been such a resource I had no idea that it would be when I started. Thank you!
Now on to my question that after learning about all of that I don't seem to have a clear answer to. What I wanted when I first considered getting an Android phone, was to build from source, and run my own rom. I still want this, even more so since I learned about CIQ.
1. Due to the counter on my phone
2. I am to understand multiple images that make the phone work (boot, firmware, system)
3. The binary drivers.
Is this at all a reasonable goal?
Are there more flash images that I haven't read about yet?
Would having a direct from Google rom even be desirable?
I own a stock SGH-I777, I have done nothing to it yet.
Lastly about this site:
Is there anything you think I should read about on the forums?
Any language I should know, as in what does hellraiser imply/mean?
Any Android experience you think might benefit a could be developer?
Counter can be reset and avoided all together.
Sorry I don't know much about AOSP building, but your better off starting with compiling CM and learn from there unless you are really experienced in coding.
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source. Ty for reminding me.
NEME5I5 said:
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source.
Click to expand...
Click to collapse
AT&T Galaxy S2 SGH-I777 has never had CIQ.
LiLChris06 said:
AT&T Galaxy S2 SGH-I777 has never had CIQ.
Click to expand...
Click to collapse
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
NEME5I5 said:
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
Click to expand...
Click to collapse
No it was just some phones, I think the skyrocket had it at some point.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Ok, so I rooted my first cell phone. It would seem heimdall latest has a bug that will brick your phone. (I'm on Mac OS Lion) I used the 1.3.1 instead, and it worked fine.
I saw many more sites, and this was quite easy. The way they showed it was very complex. Since I'm new at this should I wait to try out a ICS rom till after Samsung releases their source code, and the devs have had a chance to get it stable? How complete is the open source version of ICS? There was a note on the fsf.org page that linked me over here that some of the parts were still binary. Is it still true?
I think long term I want to get away from the official releases.
Well, you came this far, might as well flash an ICS rom now. If the leaks are any indication of status, the Samsung release will be pretty stable but the included kernel is problematic because it can cause hardbricking. Besides, you want to get away from stock, and all of the big roms released thus far are pretty darn stable; I don't know anything about binary parts or any of the coding, but plenty of people have no problem running CM or AOKP. Even the Samsung-based roms all look AOSP-like nowadays because they use Apex or Nova (not many devs like Touchwiz anymore). So take your pick, they're all good roms and most look like AOSP to some extent, with a few (mainly CM and AOKP) striving for pure AOSP.
Make sure to read and follow this guide carefully for flashing stuff, and have fun!
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Prother, by no mean to offense you, but seriously, if you don't know those fundamental technical terms, I strongly suggest you to hold off what you about to do and spend more time reading.
Let me go off and do a search the post for you, where you can get used to those terms.
Hang tight, prother.
Pirateghost said:
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
So I will. To be honest I don't see the connection between the new jargon, and development I learn in school. There is definately much to learn here. I was expecting this to be like Zaurus development from back when I was active, it's very clear to me that this is a very different beast.
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
votinh said:
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
Click to expand...
Click to collapse
Thank you friend. I may not have my own rom at the end of summer, but I should be on my way to understanding what would be needed for one.
Well the terms I wanted are not present on that list, most of that I was familiar with. To be honest, some of it I have not seen before as well. What is hellraiser, and some of the other xda developed jargon? I do have a tab open to that part of the forums, I just hadn't made it over there yet. I started on the forums for my device, then Android OS, and lastly general. Is there any other place I should pay special attention to that would help me?
Phalanx7621 said:
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok? I'm not sure I understand, is there something you don't like about the aokp rom that doesn't work very well?
I want off of the carrier provided images based on personal conviction. Google's development practices smack of cathedral, as do all of the 3rd party companies. In a sense they are abusing the spirit of free software by using a signed kernel to impede (if not actually prevent) our right to modify hardware we own. Any normal user of the software provided by the community (bazaar) can only help the cause.
I plan to share what I personally learn with close friends who live in my area. The more people we liberate, the better for everyone else. I simply applaud the work done here.
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
karate104 said:
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
Click to expand...
Click to collapse
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
From a relative noob:
Follow the directions in the " [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!! " thread. Then pick a rom you want to try and follow the CWM directions ... after that , find a ROM you like. If you don't want to void your warranty, wait for your carrier to provide the closest thing to what you want ... but, I'm happy with my flashed ICS ROM.
NEME5I5 said:
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
Click to expand...
Click to collapse
Just like everyone else has said. Read read read. Search for answers for your questions before you ask on forums. U will be fine as long as u can read and follow simple directions. Good luck to u. If u haven't flashed a rom yet I would recommend aokp. Awesome rom.
Sent from my SGH-I777 using XDA
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