I was curious to what you the Developers of the awesome stuff we have for the Epic are using? Are you using the SDK tools we get from Google to make new things? Or are you using some other stuff? I kind of want to make some stuff but I don't know how?
Can you tell me what you used or are using to get where you are now? How do you do it? Can you tell me where or something?
Anything would be helpful.
And please no random "I want to know this too" or arguing to whats better? That would be saved for another post/thread. I do apologize if this is a repeat thread. I didn't see it on the front. I think this should be though.
I'm not at my computer at home right now, I'll update it later all of the apk tools.
1) Version control - I use subversion
2) Diff tool - I use beyond compare
3) Zip tool - I use 7zip
4) Issue tracking - I use Google code
5) Text editor - gVIM
6) Graphics - Photoshop CS5
I am curious as well.
Plapczyn, do you know of any tutorials on developing ROMs for the Epic? Does it require a lot of coding?
Source.google.com
Read it follow instructions to get and compile code. That lets you build a rom from source code where you can alter the os. The only source code that is released for the Epic is 2.1 As of now. If you have specific problems with doing any thing in their directions pm me.
Sent from my SPH-D700 using Tapatalk
ryno502 said:
I am curious as well.
Plapczyn, do you know of any tutorials on developing ROMs for the Epic? Does it require a lot of coding?
Click to expand...
Click to collapse
There are lots and lots and lots of tutorials. Google is your friend.
It doesn't require much coding, but you can do plenty of coding if you want.
Will check it out, thanks.
I was just curious because I am not much of a programmer. XHTML, CSS, and Basic PHP is about my limit lol.
These might help...
http://forum.xda-developers.com/showthread.php?t=667298
ryno502 said:
I am curious as well.
Plapczyn, do you know of any tutorials on developing ROMs for the Epic? Does it require a lot of coding?
Click to expand...
Click to collapse
If you want to make roms, check out the Chef Central forum here on XDA. There are threads with a lot of info on how to do things. Also, you should check out what is going on the other Galaxy S forums. If you want to do dev stuff, you first need to figure out what you want to do, and then go from there. Making a rom (actually any development really, agnostic of device or system), is more about making and pulling in small incremental changes and testing them.
That's the best advice I can give you...is to always break things down into small incremental changes that can be tested in between. Use source control and CHECK IN your changes. This goes for simply swapping out pngs in apks, or doing kernel mods. That way, you always know where your latest working copy is and you what changes caused your system to break...which it inevitably will. Nobody codes things correctly the first time every time. We all have the urge to just make a whole bunch of changes at once and see if it works. The thought is that we don't have enough time to test everything in between. Trust me, you will spent 5 times more time fixing bugs by doing it this way, over just doing it right the first time.
thats good advice plapczyn, thank you. I will evaluate what I want to do and go from there. my #1 priority is app developement, to better my resume and help with my career, but I am interested is possibly experimenting in ROMs too.
Related
A few changes:
Alright so first off after seeing that this actually got some response, I'm opening it up for other people to edit as well. Hopefully we can figure out a way to do this responsibly... But I figure a community effort on this is much more valuable (especially because my theming is a bit rusty)
Key Files Chart
I am also gonna start modelling this off of a Cyanogen build because those builds seem to be the most poplar now. Keep in mind that much of what works in one theme translates well to most others.
--------------------------------------------------------------------------------------------------------------------
Original Post:
Hey guys so here is what I've been working on.
(Use new Link Above)
Its pretty much a simple list of locations of files that are essential to theming and what they control. This is definitely meant to be simple and geared more towards beginners. I think the thing that was hardest thing for me to learn theming was finding out where specific files were. So hopefully this might help bring down the learning curve.
Plan is to keep on updating this as long as there is interest and questions that people raise. Most of this is from my, relatively, limited knowledge of theming so if anyone else wants to jump in on this, I would be more than happy to add you as a collaborator (thats right, YOU!).
Also, I have this written according to how I know Haykuro's Builds work (because thats the version I use). If things are similar enough to other builds, it shouldn't be too hard to compile a master list across all three 1.5 builds. Let me know. : )
what a great idea! I wish this would have been available to me when I started my first theme! good work
Haha thanks. I been lax bout it lately cuz it really doesnt seem to be catching on at all. Ill wait and see if anymore interest builds up before continuing to update.
Hi!
I would be interested in an update I have been wading through a ton of information, I want to make a theme myself and I have just finished setting everything up properly on my system. I have seen how many image files there are to sort through and the names would be a great help, and I think, a good idea for others too
RainCrow said:
Hey guys so here is what I've been working on.
http://spreadsheets.google.com/pub?key=r_ua-t_U23ci5_oxwQ4mGrg
Its pretty much a simple list of locations of files that are essential to theming and what they control. This is definitely meant to be simple and geared more towards beginners. I think the thing that was hardest thing for me to learn theming was finding out where specific files were. So hopefully this might help bring down the learning curve.
Plan is to keep on updating this as long as there is interest and questions that people raise. Most of this is from my, relatively, limited knowledge of theming so if anyone else wants to jump in on this, I would be more than happy to add you as a collaborator (thats right, YOU!).
Also, I have this written according to how I know Haykuro's Builds work (because thats the version I use). If things are similar enough to other builds, it shouldn't be too hard to compile a master list across all three 1.5 builds. Let me know. : )
Click to expand...
Click to collapse
This is great; although I am new to Android themes, I have extensive experience with BB themes, although that is the "apples to oranges" scenario. Plazmic of course does the grunt work in those, but I have written svg's for animation, hidden docks etc. Hopefully that will help me catch on at a faster rate compared to never having done that sort of thing. So any info you can pass along is much appreciated!- Chris aka riffman
TY
Awesome work. You just simplified SO much of what I was not looking forward to.
I would like an update as well. I am lost sometimes. lol
I'm good on what most of the .png files control, but if you could make one for the .xml files in framework-res.apk/res/layout that would be killer.
Haha wow. Five months later I'm seeing this thread actually got some feedback (And linked on the "Helpful Threads" sticky to boot). I was considering making the document an open project and just working on maintaining the structure if that sounds helpful to people because there are plenty of things that I would like to know as well (like .xmls)
EDIT: Alright I just changed it to open system so that anyone can edit it. I should probably also change the name off from Haykuro seeing as how hes out of the running now...
i want to know how do i do to build a kernel for my htc desire, and ov/uc please thx
Try the Q&A section, where this should've been posted. Maybe you shouldn't be cooking kernels when you can't even manage to read forumpolicies
lol everyone learns and i want to learn how to make it just it
Alkan2 said:
lol everyone learns and i want to learn how to make it just it
Click to expand...
Click to collapse
There is a q&a section on this forum, try there. This thread will probably soon be locked down once mods found out about it and most importantly, you won't get any help here.
hello noob!
http://www.youtube.com/watch?v=JmvCpR45LKA&
Someone needs to take that ****e video off YouTube as it's harsh. How are we meant to build a community if people just shoot n00bs down before they know anything??
EddyOS said:
Someone needs to take that ****e video off YouTube as it's harsh. How are we meant to build a community if people just shoot n00bs down before they know anything??
Click to expand...
Click to collapse
Don't wanna b adding too much to this thread but agree 1000 times with this comment...if it wasn't for noob threads I'd still be stuck with stock rubbish
Sent from my HTC Desire using XDA App
This thread -> LOL
bailz2506 said:
Don't wanna b adding too much to this thread but agree 1000 times with this comment...if it wasn't for noob threads I'd still be stuck with stock rubbish
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I agree noob threads are great, they helped me immensely.. but the android development thread is there for a specific reason and so is the q&a thread
Sent from my HTC Desire using XDA App
I've been noticing the increase of stupid questions for a while but more importantly, I am getting fed up with the aggressive nature of some of the users. So people post in the wrong section, move post with warning, end of.
Also if the ROMS were cross posted to FAQ by default then more people would end up there instead of using the search to find the ROM title and ending up at the DEV thread.
xda is getting a bad rep for their mods and i'm not surprised. . . .
Alkan2 said:
i want to know how do i do to build a kernel for my htc desire, and ov/uc please thx
Click to expand...
Click to collapse
Returning to the original question.
The prerequisites for rolling your own kernel are:
- A linux system
- Terminal Know-how
- A synched GIT (such as the Bravo CM7 branch)
- Patience
That is just for building the stock kernel.
The additional prerequisites for changing stuff:
- A text editor
- A set of OC/UV values (such as Eviolett's)
- Experience in the linux terminal - more than for just compiling the stock kernel.
It doesn't seem like a lot of work - Sync the GIT, chuck in a few values, and build it. In reality, however, there is a stack of other stuff to do. I have a fairly good knowledge of the linux terminal, but still spent a stack more time getting everything ready than I wanted to (hours, in fact).
As motivated as you may be, it ain't a walk in the park, even with a detailed set of instructions. Stuff is going to go wrong, and a lot of the time, problems differ from those prescribed in the instructions.
Having been there, done that (or more accurately, failed to do that), this is just my two cents.
EDIT: Just to clarify, I failed miserably.
Bradshort said:
Also if the ROMS were cross posted to FAQ by default then more people would end up there instead of using the search to find the ROM title and ending up at the DEV thread.
Click to expand...
Click to collapse
Nice idea but look at Robo's "RCMix S v2.0 Evolutionary Sense" thread" it has a separate RCMix Guide/Tutorial/FAQ + 2 irc channels now have a look through the 12000 odd posts in that thread maybe 50% are total spam by people who don't understand how a forum works, fail to do any independent research but expect someone to hold their hand and explain everything slowly to them. I don't condone it but i fully understand the reaction a lot of "dumb" superfluous posts get
This. Simple fact is most people are incredibly lazy and thinking that devs are here to answer their every stupid question.
Terepin said:
This. Simple fact is most people are incredibly lazy and thinking that devs are here to answer their every stupid question.
Click to expand...
Click to collapse
Must agree.. I spent probably 10+ hours researching before I flashed my first ROM..
Sent from my HTC Desire using XDA App
I totally agree with fllash. It looks easy, but it certainly isn't.
Just start with downloading a copy of Ubuntu, version 10.04 and up will do just fine.
Why Ubuntu? Well, if you're only starting out with Linux and the more advanced topics such as compiling your own kernel, you'll need all the help you can get. XDA is a great community with a lot of information to be found, but it sure won't cover all the questions you'll have, so you might want to search trough the Ubuntu forums etc., as they might have more specific answers to your questions. There are also numerous books about starting with Linux, so you might want to check those out as well.
When you got a nice grip on working in Linux and the terminal, it's time to get busy programming!
If you're not a programmer already, you might want to start with Java. (Maybe write a little Android program? That way you'll also learn how Android works)
The Linux kernel is written in C and that might be a bit harsh to start out with. However, if you feel confident enough (or if you have programming skills already), go get yourself a book about programming in C, search some tutorials and start off writing some easy and silly programs, just to get a good grip on the language.
When you feel like you got a good grip on programming in C, feel free to download a kernel which is already compatible with the HTC Desire, one from CM or one from Thalamus (from Oxygen ROM) and take a look at the source code. Try to understand what makes it tick. Please note, that these kenels are for AOSP ROM's only! If you want a HTC Sense compatible kernel, go get the source from HTC which you can find here: http://developer.htc.com
By the time you got this far, it's only a piece of cake to compile and install. (Compiling and installing really isn't the hardest part about all this, so you'll manage to find your way out of this one)
Right now, you're probably thinking: "Is this all necessary? I just want my own kernel.." Well, yeah, it kinda is. You just can't follow a tutorial and end up with a kernel which is going to be great. There are going to be bugs, you're going to have problems, nothing will work from the first try.
Maintaining a kernel is hard work and requires a lot of knowledge in order to do a proper job.
Also, take a look at http://developer.android.com/. Knowing how Android works is kinda a requirement as well (at least, I consider it to be a requirement).
Oh, and for the record, please post in the correct forums next time. There's a Q&A section where you can search for, or ask questions. I understand that this is a dev-related question and you might have figured that the dev section would do fine, but unfortunately, it doesn't.
Okay? Well, happy learning! Don't let other forum members or some tough luck get you down.
Hey everybody,
I recently bought the galaxy nexus because I wanted to start getting into Rom Development.
I can programm Java and also programmed some simple apps..
But what I really wanted to do is to modify a Rom.
Can anybody tell me where to start? I read guides on how to compile from source and so on, but I don't know if that's what I need.
I want to add things like Notification bar quick settings to the rom.. Are there tutorials on how to develop these things?
Every help is appreciated, maybe you've got some great links for me, thanks!
00hero00 said:
Hey everybody,
I recently bought the galaxy nexus because I wanted to start getting into Rom Development.
I can programm Java and also programmed some simple apps..
But what I really wanted to do is to modify a Rom.
Can anybody tell me where to start? I read guides on how to compile from source and so on, but I don't know if that's what I need.
I want to add things like Notification bar quick settings to the rom.. Are there tutorials on how to develop these things?
Every help is appreciated, maybe you've got some great links for me, thanks!
Click to expand...
Click to collapse
start with decompiling apks (SystemUI.apk and framework-res.apk for example) , if u've wrote android apps before (and u said u did), then it shouldn't be that hard to look into the .xml and .jar files. when u finish, compile the .apk back. if u've worked with Eclipse then u probably know the android structure.
Edit: Here is an example of a "ROM modification" - just posting it to give u an example..
Well first thing is first. You need to have the bare basics of Android thoroughly understood obviously. Often overlooked as a first step in this process, just learning about(different than knowing about)the Android Open Source Project first will give you a specific sense of direction, purpose, as well as an identity in the community..
So again- I don't just mean knowing about it- I mean knowing exactlyhow the whole project is structured. Read about all the different types of contributions you/anyone can make to the Android ecosystem. Are you an aesthetics kind of person who would excel at UI designs for apps or whatever; Are you a person who has a good eye for problem solving? Maybe you should be scouring source code, trying to fix little-noticed "bugs" that "bug" the hell out of you. Once you know what you want to do, make sure you find out exactly how much Google provides for you, and what your own roles/responsibilities would be in the whole scheme of things.) This should give you a good idea of where you might fit in (with your current skill-set)and hopefully, it gives you some inspiration about the direction you might want to take it in the future.
Once you do this and "find your calling", post back here, and I'm sure that others qualified in that field will be more than happy to share how they got started.
There is no substitute to just jumping in and trying things though. Everybody makes their own journey differently, so do what comes naturally, and you can't go wrong.
Here ya go
http://forum.xda-developers.com/showthread.php?t=1661770
and maybe this as well?
http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
Wow thank you every body for these great comments! I think I'll compile a Rom from source first and look through all the files..
Decompiling apks looks interesting too.
Thanks for the fast responses & links, you're awesome!
Okay so I've got another question..
One thing I always liked on some custom roms was the lockscreen flashlight..
If I would hold power for 3 seconds, the flashlight would turn on until I let go the power button.
I decompiled the framework-res.apk but didn't find anything there, just .xml files.
Where are the files where I can actually code / programm something for the lockscreen?
Try android.policy.jar
Usually the jar files contain the code, xml are for visual stuff.
But my question is, are u sure it is a lockscreen feature? (I mean the torch option) . Tbh this is the first time i hear of such a mod and i've been using android devices for over 2 yrs
Sent from my Galaxy Nexus using xda premium
i know this don't sound professional and to be honest a litttle annoying but
i wanted to try this mod
http://forum.xda-developers.com/showthread.php?p=32385441
the BB10 lockscreen but i don't understand it's instructions
How to :
1) Apply patch(diff) with resources.
2) Compile.
3) Done
...? huh ? i don't get it ...any help ?
I think the patch method is for more experienced users. I don't understand it either. It seems like it might not matter though. As long as you are running a ROM with the T Mobile theme engine, it's going to be available through the Play Store soon. Just a heads up, rather than starting a new thread, wait a couple of days to see if the requests for more information in the original thread turn anything up. Someone might well be writing up a how-to guide, but that kind of thing takes time to do right. We just need to be respectful of the fact that the people who are able to provide that kind of information are doing so as a hobby. Good work takes time, so let a little time pass.
Edit: Seems like there's already a how-to link posted.
Sent from my Galaxy Nexus using xda premium
The patch is for people that compile their own roms from source.
good day.
there's tutorials on both subjects.
i would think most don't have the determination to get there.
Hey everyone, I have a couple of questions. First off as you can see from my post count I'm a lurker. I can remove/install ROMs, the basics, but never have I tried to add/remove apps or functions to one. So I've found a ROM I love, but it was designed with inactive phones in mind, to make them into second life usable music/video players. It has no phone functionality because of this. The one I'm interested in is by frickinjerms - Ubersonic - I hope I can modify others work for my personal use. Guess that should be a question too.
Would it be ok to add in phone functionality or would it be easier to find one with that already and just remove the fluff I don't want and add what I do?
As I understand it, I can just add it back in, but I'm unsure what files go back in. Is there a resource that outlines that anywhere, or can anyone throw me a bone?
Is it ok to modify the work of others for your personal use without asking, or should you seek approval first out of proper etiquette?
I've been searching through XDA and other sites looking for some basic beginners stuff for cooking up ROMs, but have only come across limited collections. I'm toying with dsixda's Android Kitchen right now, but would love to find other resources. So any pointers to learning resources would be great too.
Thanks!
For the last one, I personally believe that its not necessary to ask before modifying a rom thats for your personal use because only you will know about it anyway, and people do it all the time
You only need to ask for permission if you're reposting your personal version of someone elses rom
Sent from my PG06100
CNexus said:
For the last one, I personally believe that its not necessary to ask before modifying a rom thats for your personal use because only you will know about it anyway, and people do it all the time
You only need to ask for permission if you're reposting your personal version of someone elses rom
Sent from my PG06100
Click to expand...
Click to collapse
I figured that was likely the case I just wanted to clarify it for myself. I know people put in a lot of work on some of their ROMs and don't want to step on toes.
Thanks for the response.
You know you could use a rom that does have phone functionality. Just throwing that out there.
PlatinumPenguin said:
You know you could use a rom that does have phone functionality. Just throwing that out there.
Click to expand...
Click to collapse
Whats the point of flavors if you're forced to pick the one you don't like? Just throwing that out there.
I don't think my questions were unreasonable either. I'm not asking for someone to build me something, I'm asking for the fishing pole, not the fish.