So, I have a T989D and I'm a budding Android developer (almost finished my first major release). Once my first app is released to the masses, I will have plenty of time to develop ROMs while I'm updating my app.
This being said, I know absolutely nothing about ROM development, but quite a bit about the Android framework, java, etc. etc. I assume most ROM development is cracking open the source and tweaking to your hearts content, however, there must be some very specific things which I'm not sure my skills will translate into effectively?
So, what I really want to know from other Developers turned ROM makers is, how much of my skills are transferrable and what are the quirks/pitfalls I'm going to have to learn?
I'm quite excited to get involved and develop some ROMs for this phone, a nice kickstart would be appreciated.
Thanks!
Related
I just recently decided that I have had enough of WinMo on my tilt2 and opted to see how the development of Android OS was coming along for the phone. Not surprisingly, it has developed a lot since I first picked up the phone in December and first thought of the idea of placing Android on the phone.
To my point-- I have some programming experience and would be interested in learning the language behind Android. Obviously it is linux based, but is that the only thing I need to know?
Does anyone know what I need to know to get started?
Links to appropriate sites with details on the language is really what I am looking for. Thanks to any and all that will help (not looking for trolls, get enough of those from other sites).
I too am learning linux, I've had to use linux commands for over a year now as I also own a G1 and you often (when rooting) need to go into a terminal to make changes. I unfortunately don't know much of the language required to create or change much of the android OS I only know the file structure and how to change that. If I were you I would jump over to http://www.android.com download the developers kit which comes with an android emulator and they have lots of tutorials and demo apps for the android OS. It won't do much as far as help you modify the system but it's a good place to get started.
Hope this helps and if you have any questions about the things I do know, feel free to ask me
androidonhtc.com/wiki/Get_Involved[/url] you can try this.
I'm interested in doing some development for android. I'm just not sure where to start. I see a ton of books on Amazon.
I'm just wondering what would be recommended for an absolute beginner. I know my way around a computer so i don't need it that noob'd down.
I think i would like to play with some apps, and eventually move to Kernels and Roms.
What you you recommend?
Probably the best way to start is to learn Java (the main coding language for apps and userspace), and C (the main languages for kernelspace stuff). After that, messing with the App Inventor would be the place to go.
Search dsixda very helpful thread
Sent from my PC36100 using XDA App
i was thinking of learning some basics of android app development and coding with a very basic walk through so that i can fully understand what i'm going to be able to use the Java code in particular applications. Would this be a bad strategy.
As a software developer, I would recommend spending a couple weeks getting the basics of Java and object-oriented development down. Do a few sample apps in Java. Once you've done that, try Android. I'm afraid that learning to code, learning Java, and learning to develop for Android all in one may be too much for someone.
You really need to have the basics of Java and object-orientation down, then take on Android as it's not altogether simple, particularly for someone who's just learned to code.
As far as kernel/ROM development, I'm guessing C and Linux shell scripts are the things to learn there. If you want to write Android apps, do as I've mentioned above.
HI, I am new, this is my first real post so if this is posted in the wrong area sorry.
SO, I was working with a zune developer on an RTS and I had a large amount of art done for it. He got overwhelmed with the project and so I am looking for someone who thinks they can tackle an RTS. I have all gesture commands and ui layed out as well as basic unit properties. I have about a dozen fully animated sprite units and about 6 buildings complete so far.
If you think you are upto the challenge OR have a solid game that you would like some killer art done for let me know. BUT, I want to see it is some app store, I dont want to waste my time with a fizzled project.
If you want to use sprites I have already made thats cool, I would only request a cut when the game goes on an app store.
Very nice sprites, and the game looks good so far. Were you able to keep the source or do you plan on starting from scratch?
all info pertaining to the game can be found here.
I think the game is open source as others have dived into it. I know pathing was a difficult problem and did not have much of a solution. the project was for the zuneHD.
I will move this to SW development since this is an ongoing project, once you have a close to finished, or finished product PM me and I will move it back. IE Beta. .
~~Tito~~
Hey I'm a programmer looking for an artist to work with on various projects. I currently focus on Android development however I do have some experience with XNA / C# before (made a little tilemap engine on it and whatnot). I also just got my Samsung Focus registered on my developer account and have compiled a test sample on it just 2 days ago. I am really excited about Windows Phone 7.
I ALSO plan on making a fully crossplatform RTS at some point for iOS / Android / WP7 and I may be able to get started now. However, I would definitely want to sell it and keep it closed source / proprietary. Making an RTS is a HUGE task however, and will need a lot of planning and thinking ahead.
If you're in USA that's an extra bonus. If you have MSN Messenger that's another bonus. PM me if you're interested in working together on various projects.
There's a current "small" and cross-platform 2d game project I'm working on that I don't want to disclose publicly atm and we can discuss that if you have any interest in that, but I guarantee you I would love to make an RTS in the near future but merely lack an artist and an idea .
In my signature you can see all the devices I own for testing on. I am very inclusive, I love all smartphones.
I also do some music, I can show you some samples if you are interested in going further in regards to this.
Raptor550, I've sent you a PM, could you check please?
P.S. Seems like by default the PM notifications are disabled here.
I've been a member here for a short while but a frequent visitor for a long time. Recently, with the release of ICS I've become more interested in the work being done by ROM developers here, including a certain 15 year old doing a lot of work porting ICS.
I'd like to know what programming language is used in ROM development so I can maybe learn a thing or two and put in some work of my own.
EDIT: Posted this here because I own a G2 so if languages are different depending on phone, I'm obviously more interested in how to do work on my own.
C, C++, and Java.
If you’ve spent any amount of time on XDA, you’ve heard of XDA Recognized Developer Cyanogen or the nearly ubiquitous CyanogenMod. In fact, chances are that at you’ve either run CyanogenMod on one of your devices at some point in the past, or you’re running it (or a kanged version) now. In many ways, CyanogenMod represented all that was good about Android Open Source Project (AOSP) and proceeded to go where the carriers and manufacturers were unwilling to take their devices. Along the way, Cyanogen inspired developers everywhere to reach for what was previously lacking in the Android community.
Cyanogen also saw an emerging trend which he wasn’t too happy about – the term “chef” being applied to the Android custom development scene, along with the emergence of the so-called “WinZip ROM.” So he created a thread back in 2010 to speak to this emerging trend and offer up some advice. The overriding theme was that contributing quality was far more important than contributing quantity on XDA.
He had this advice to offer for those looking to make their own Android ROMs:
Stop. Write an app or two first, learn how the system works from a developer standpoint. Learn some Java. Read the developer documentation. Learn how to use Git. Then learn how to build AOSP from source. Read the porting guides, and learn how the build system works….. Now try to put your new found skills to work on enhancing the platform by writing code or making theme overlays. And share! And put that s**t on your resume. There is a *ton* of information out there but any kind of “step-by-step rom cooking guide” is going to be a complete fail- it’s too broad of a subject.
As XDA has grown right along with the meteoric rise of Android, so has a desire of users to create their own ROMs, kernels, themes, and so on. Much of this work classifies as “original development,” but there’s been a growing trend to what many are calling “derivative development.” This category covers most of ROMs based on stock releases from the manufacturers, applying patches and scripts aimed at optimization, theming and/or removing stock applications, and using “kitchens” that run a stock release through a list of scripts and then repackage as a recovery-flashable update.zip. This is what Cyanogen was expressing frustration about—shortcuts being taken to achieve a product that differs only slightly from stock (derived) and pushed out instead of building from source and delving into the core of Android and making something truly original.
XDA-Developers exists first and foremost for developers. It’s at the core of who we are; it’s in our blood; and it’s in the air we breathe. There is a place for derivative works—they provide an entry to the scene which can help to introduce people to the wonders of Android. But let’s not stop there. Don’t be satisfied with just creating yet another derivative of someone else’s work. Instead, follow Cyanogen’s sage advice and learn about Android from the ground up, and create something truly original and innovative.
Here are some locations to help you on the path to learning about Android and contributing to the community as a whole:
Android Developer Guides
Working with Android Source
Downloading the Android Source
Git Tips and Tricks
Building CyanogenMod
Pro GIT Book
source : http://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/
original source : http://forum.xda-developers.com/showthread.php?t=667298
Well put and a great reminder for all.
Side note - What is with all the "reserved" posts? This has to stop, its just spam. I will delete all posts on sight and repeat offenders will have their ability to post removed.
Sorry to divert the topic.
andyharney said:
Well put and a great reminder for all.
Side note - What is with all the "reserved" posts? This has to stop, its just spam. I will delete all posts on sight and repeat offenders will have their ability to post removed.
Sorry to divert the topic.
Click to expand...
Click to collapse
moved and cleaned...nice..
i was also curious of the so many reservations
anyway, the message is clear..
Dev = Creator(File Pusher)
Chef = Indirect Piracy? LOL
For the chef thing is my opinion since its just improvising, not really creating