Hey XDA.
That disclaimer video in the forum registration gave me quite the scare. Hope you guys don't eat me alive haha. I made a post on one of the android subreddits on Reddit in regards to android development and was referred here.
I'll try to keep this nice and simple: in short, I want to dive into the world of Android development. Although I don't currently have an Android device, I will have the Galaxy Nexus in hand within a few days, as well as a Kindle Fire (I realize the Fire isn't "open", but more on that later...). I'm a current CE/CS student so I have some background in both hardware and software.
My interest in Android development lies in the actual porting of the OS to new devices (hence, the Kindle Fire); app development is secondary, and after looking through available documentation I don't expect to run into any significant trouble developing apps as I have fairly good experience with Java to boot.
All this in mind, I have very little experience with Linux and lower-level tinkering - the kind required for porting a kernel etc. In addition, I can't seem to find any material to at least get me started. I fear my inexperience and ignorance in this area has me not even knowing what exactly I'm looking for.
My ultimate aim is to help contribute to the efforts of porting Android to new devices - like the Kindle Fire. I've been following some of the threads on XDA on getting ICS over to the Fire and it looks like challenging and interesting work, and I think I would learn a lot from it.
I'm sorry if I've been vague, it is only due to my ignorance. I am eager to learn and am hoping some of the more experienced android devs could help point me in the right direction!
Thanks a lot!
Related
Hey there, everyone.
I'm just looking for some advice. I've been using my Verizon Samsung Fascinate since November, and for the most part have been a very happy user. Ever since I installed a Gingerbread-based ROM, I have been extremely happy with both the device's performance and new features (nothing says cool like the Old TV Shutoff animation). Lately, I have been wanting to try my hand at modifying and packaging my own Android ROMs for the Fascinate. Obviously, I have never done something like this before, so I'm looking for some advice.
I've been programming in Java for over a year now and I'm very familiar with the language as a whole. I've used it in various programming competitions through school along with building some applications and tools for the company I'm currently interning with. Right now, I feel that I have the basic programming skills required to look through code and understand what the logic behind it is (at least I hope).
My question for you all is this: should I jump right in and start poking through the AOSP code, or would it be more beneficial for me to start off as an Android App Developer, slowly working my way into Android hacking? I have some ideas for potential apps (which I'll probably end up developing regardless, but at a later date), so if it would be more beneficial to just develop apps, I certainly have a basis for my ideas.
Any personal stories/recommendations would be excellent. Thanks in advance for any/all answers!
Hi Mods, i am a Android user who has been playing around with Android devices for almost a year now, putting ROM's and Kernels, etc on my devices. I had a Mytouch, Galaxy S 4G, and Asus Transformer. Unfortunately, i don't have time to read through all the threads and develop ROMs etc, and i do appreciate all the time and effort that the developers put into it. I am just a normal user who would like to utilize the full potential of my devices (and like to show Apple users how we can kick their A$$e$. I had a thought recently. It would be so useful to all the regular users to have a BIBLE, that gives us the general steps of rooting, installing roms, definitions of terms and abbreviations, and different mods. It doesn't need to be device specific (or maybe it does). I believe it would help everyone out a lot and help bring some uniformity to the world that is Android.
I hope someone would consider this wholeheartedly. And again, BIG THANKS to all the developers!
Yes, I too think that this sounds like an awesome idea. Something like a wiki from xda-developers. With real noob tutorials and introductions. That way, people who are interested in diving deeper into that have a starting point and xda has a recruiting effect. For example I myself would love to learn about developing from scratch because weeks ago i started my studies where I learn java and c++. Having to search for every tiny bit of information is just annoying...
theres already tutorials out there on some basic things...
Yes sure there are some tuts but nothing like a compendium..
Sent from my HTC Sensation Z710e using XDA App
Hi guys,
I'm new to the forum, but I plan on developing ROMs with a few people, so I will probably frequent them soon.
In my Operating Systems class, I was asked to come up with ideas for a project. Well, since I'm just starting to build Android ROMs anyways, I was going to see if I could use this idea for class. I guess my question is, do you guys think this would be a good project to last a few weeks of the semester (at least)? If not, can you suggest ways that will make it longer or shorter? We would be building them for a Droid Incredible.
I have a general idea, and it seams that just getting an AOSP ROM up and running would be no problem at all, from what I read anyways. It seems like the tailoring or the importing of ROMs is what really takes time and effort.
Thanks in advance for the input.
It depends on the class skills. But it's really great idea to study Linux and low level Android features. uh.. I didn't have such interesting project during my university years ((
The only big issue is high initial level of knowledge. Also many peoples may quickly give up fighting with some unclear compile or deploy issues. It's not trivial to debug on such devices. They may quickly lost their interest. But overall this is great idea. Where are you teaching?
I'm not actually the professor, I'm a student at Saginaw Valley State University (Michigan). I'm the "Class Leader" so I told the professor that I would give him the list of ideas I had for projects.
If it's for a grade, it might be a good idea then. They may lose interest, but if their grades are on the line, I would hope they struggle through it. Plus, we are all in groups, and they can pick another project if they don't like this one.
Thanks for the info, Purler.
Does anyone know how different it would be to make a ROM for something that requires a mouse input, like the Raspberry Pi?
Hi xda-developers,
I am an Embedded developer with vastnexperience in Firmware development in C programming (for microcontrollers), pcb designing, corel draw/photoshop (intermediate level) . Now I am looking to stretch my self a lil further by trying my hands on Android Programming. I have no prior experience in Software development. It would be kind of experienced developers out here to guide me with possible approaches that I can give to Android development without a much steep learning curve. As I would be practicing android development mostly on weekends (as of now), I would like to get started with things that I can relate with already. That way it would keep me going. Help me out with:
1. Possible applications I should work on. Something that can also be helpful for the community of users and developers.
2. Starting point and other obstacles I would come across while development.
3. Application ideas.
P.S: I also have a rPi lying around catching dust.
Some of the features still cant use on this. Libraries could be use.
Start with "Hello World"
Regardless of your software development capabilities you should always just mess around with the tools that are available and see what you like and what you don't like.
Try every tool you can, when you feel like you know those inside out have a go at extending the functionality of one of those.
For me when it comes to learning a new technology like Android SDK just playing with it inspires me to want to create real and practical applications.
Goodluck and have fun.
PS: I would stick around and see what happens with the release of Qt 5.2 Hint hint...
Yea. Android like embedded requires you to set up a Dev environment so get that up first. ROM building vs app developing are hugely different. Decide which and download the tools. (May require you to install a whole new os and tweak it heavily. Last time I ventured to compile a ROM it was a day to set up my Linux distro of choice)
And like what was said before start with hello world and move up in small bites. You will gain better understanding of how things work and will be less frustrated. Don't expect a full featured app to appear. Once you play around with all the little components eventually you will see a big picture and the building blocks for the "big app" will be there ready to use.
Sent from my One using xda app-developers app
Hi my name is Corey.
I'm starting this thread to get a better understanding from the developers point of view on the hardships, annoyances and general dislikes about android development. Stuff like the current tools, what feature you would like, and more importantly what parts of these IDE's you hate. I myself have been developing for android for about 6 months now and the first part for me is the interface, the fact that the IDE makes me do all the work instead of being automated in some way, and the setup process I have to go through to make sure the IDE is working on every new machine.
Yes i do have an entrepreneurial spirit but i think its a valid question and as a learning developer one i thought I'd get some background on.
Thanks for taking the time to help me out..
You should do some work for the galaxy mega 6.3 i9205........we need it.
2SHAYNE
coreybain3 said:
Hi my name is Corey.
I'm starting this thread to get a better understanding from the developers point of view on the hardships, annoyances and general dislikes about android development. Stuff like the current tools, what feature you would like, and more importantly what parts of these IDE's you hate. I myself have been developing for android for about 6 months now and the first part for me is the interface, the fact that the IDE makes me do all the work instead of being automated in some way, and the setup process I have to go through to make sure the IDE is working on every new machine.
Yes i do have an entrepreneurial spirit but i think its a valid question and as a learning developer one i thought I'd get some background on.
Thanks for taking the time to help me out..
Click to expand...
Click to collapse
Probably those impatient people who are constant asking for the next update/revision on roms lol