Related
so i would like to learn how to do things for my phone and possibly help with the dev community. but i know practically nothing about linux or how to do anything useful. i am looking for links or other useful information to help me get started. i have lots of time on my hands and learn pretty quick. i assume i would start with the sdk (would i use the 1.5 one since thats what our phones are currently running on, or is the 2.0 out yet? and would i try from there), but other than that have no idea what else would be useful.
so.... yeah. helpful link to good info or any good e books, or anything like that that will get me going. thanks in advance
i would use the newest SDK, 2.0.1, and make sure that it will function on the emulators for both 1.5 and 2.0.1, frankly if you arent already proficient with linux or java, this wont be a easy thing to get into. However I WILL point out how threads like this are terribly pointless... you arent helping anyone out, and frankly you're asking for information that is quite available.
thanks for nothing. other than making me feel stupid.
Some help, maybe.
ix3u said:
thanks for nothing. other than making me feel stupid.
Click to expand...
Click to collapse
I've been spending quite a bit of time on the threads here, I too am in search of more information specific to the android. I don't know that I'll ever be able to contribute too much to the devs, but at least I can understand my phone better, and help out with answering questions on the forums.
I would think that starting with something like creating a theme would be a good place to start, and would get you a little more familiar with the ways of android. Then I would move up into other things, and before you know it you will be much more proficient. It's all about starting somewhere. (and having a good backup)
Here's some posts / links that I have collected that i thought might aid me when i create some time to start the same endeavor...
* Ratcom's guide to creating Theme's
http://forum.xda-developers.com/showthread.php?t=574167
* An Android Developers Guide (with tutorials, and tons of info)
http://developer.android.com/guide/index.html
* How-to's regarding android application development:
http://www.brighthub.com/mobile/google-android/topics/guides.aspx
* Tutorials and exercises
http://blogoscoped.com/archive/2007-11-19-n27.html
I haven't looked at most of those, but hopefully they will be a good start. I look forward to the day when I start looking at them too.
Hopefully that's helpful, it's all I can offer.
Good luck, and godspeed
-AndyS-
thanks., that is more like what i was looking for
jmhalder said:
i would use the newest SDK, 2.0.1, and make sure that it will function on the emulators for both 1.5 and 2.0.1, frankly if you arent already proficient with linux or java, this wont be a easy thing to get into. However I WILL point out how threads like this are terribly pointless... you arent helping anyone out, and frankly you're asking for information that is quite available.
Click to expand...
Click to collapse
Hmmm. So much for helping someone out who at least has the desire to learn and grow to be more. Communist much? or just a Liberal Democrat? I applaud him for trying. Who knows more about where to get the information other than XDA? Hell a google search on this stuff turns up mostly useless garbage anyways. Why spend hours digging it up when someone else may know a good resource.
Lets refrain from flames/rebuttals please.
I have a few FAQ's and tutorials on my site. Also checking things like my release notes and mind map (linked in v1.0 release) will help. There aren't any full on tutorials but it's just a good place for general info.
Check my sig.
As flipz stated, there's no good centralized place for organized information. The best advice is truly to search this site, and search with google. It's an uphill battle getting that base of knowledge built up to get you going. I know, I'm still working my way up the hill. I thought about putting a site together to organize and share information but that would take away too much from what little time I have to spend on rom developement.
I doub't that is really the answer you were hoping to get but unfortunately thats the grim reality of things. Perhaps someone with a lot more free time than I, will put together a site of their own and compile and organize all kinds of good information in a central place. It would truly be a boon to the android community.
obelisk79 said:
As flipz stated, there's no good centralized place for organized information. The best advice is truly to search this site, and search with google. It's an uphill battle getting that base of knowledge built up to get you going. I know, I'm still working my way up the hill. I thought about putting a site together to organize and share information but that would take away too much from what little time I have to spend on rom developement.
I doub't that is really the answer you were hoping to get but unfortunately thats the grim reality of things. Perhaps someone with a lot more free time than I, will put together a site of their own and compile and organize all kinds of good information in a central place. It would truly be a boon to the android community.
Click to expand...
Click to collapse
I'd be happy to bring some writers on to my site or to host some tutorials or anything that others have written. My job offers me a lot of flexibility and free time, however like you I am spending all of it developing right now. This kitchen is kicking my butt.
Edit: We'll see if I get any hits. http://geekfor.me/news/wanted-writers-for-faq-tutorial-help/
I may be able to help. My freetime seems to come and go, but I’ve always been pretty good at making How-To’s.
What format would be best?
html,pdf,etc…
ix3u said:
so i would like to learn how to do things for my phone and possibly help with the dev community. but i know practically nothing about linux or how to do anything useful. i am looking for links or other useful information to help me get started. i have lots of time on my hands and learn pretty quick. i assume i would start with the sdk (would i use the 1.5 one since thats what our phones are currently running on, or is the 2.0 out yet? and would i try from there), but other than that have no idea what else would be useful.
so.... yeah. helpful link to good info or any good e books, or anything like that that will get me going. thanks in advance
Click to expand...
Click to collapse
Good thread, thanks for starting it.
I'm in a pretty similar spot. 2 weeks ago I had zero exposure to or knowledge about Android or Linux. I'm proficient with Windows. In the last 2 weeks I've rooted, flashed RA 123, 151 & then 152. I backed up, ran an optimizer .zip file, restored, flashed fresh 1.0 and learned some very cool stuff. I'm comfortable in the terminal but I'm getting to where I'm not sure what I should or want to learn next. Also, although I've done these things easily half of it was just copying instructions from one of the fantastically helpful posts on this forum. Before I learn what to do next I'd like to understand the system better. I checked out wiki and ended up bookmarking a page that explains kernal computing, and a few others, lots of reading ahead
As a noob I have tried to learn without getting in the way too much. I'm glad you admitted your noobness and asked for some direction, you're not the only one who could use it!
obelisk79 said:
As flipz stated, there's no good centralized place for organized information. The best advice is truly to search this site, and search with google. It's an uphill battle getting that base of knowledge built up to get you going. I know, I'm still working my way up the hill. I thought about putting a site together to organize and share information but that would take away too much from what little time I have to spend on rom developement.
I doub't that is really the answer you were hoping to get but unfortunately thats the grim reality of things. Perhaps someone with a lot more free time than I, will put together a site of their own and compile and organize all kinds of good information in a central place. It would truly be a boon to the android community.
Click to expand...
Click to collapse
Sounds like what the original replyee said but said much more tact.
I'm hoping that was a compliment in a round about way.
THIS is an amazing resource. I've stopped in there before but wasn't ready to poke around too much.
I'll see you guys/gals in the spring!
I'd like to offer some insight, but there's really not much more I could add than what's already stated and linked above. Everything you need to know can be found (usually) easily on the android developer site, or in a google search. The hard part is putting those pieces together to know what needs to be done in order to accomplish what. That's not an easy task: check out cyanogen's github projects (http://github.com/cyanogen). He's made modifications to the kernel, Android applications, core frameworks, configurations, recovery images, packaged resources/images, and more. It's not just one piece that goes into these builds.
Most of what you see around here (and this is certainly not to take away from all the great work I'm referring to, because this is just as important as everything else), are people modifying what was already done somewhere else, and making it work for their own phone. And really that's all it takes to move progress forward.
You don't have to be a linux whiz or a Java programmer to be able to make progress with your phone- you just need to understand how each particular piece works in order to make progress on that piece. If you want to make a theme, you need to know what jar or apk files contain the resources, and how to replace those images and styles. If you want to add support for the camera you need to know what linux driver it should use, and how Android expects to interact with that driver. Same for supporting accelerometer sensors, etc.
There's no definitive checklist of things you have to know before you can help development, it just depends on what what you want to help with, and your willingness to research how that particular piece works and what it would take to make the necessary changes.
maejrep,
Informative and encouraging. Thanks!
I have experimented with quite a few different ROM's, and have enjoyed trying them all out.
Just wanted to post a thought out there, and see if this would be worth pursuing or if something like this exists...
A table that compares the ROMs, version, refresh date, developers, features, additional software, bugs, etc, so folks can compare the different ROMs on one page.
Link the name of the ROM to its actual thread.
Just a thought I wanted to throw out there......
Thanks,
-Sf-
The closest thing that we have is this:
http://forum.xda-developers.com/showthread.php?t=649705
But, it doesn't lay it out all that clearly without having to go to each thread and read through. Also, it is about 5 weeks since it was last updated, and we all know how much has been done in the last few weeks (especially Froyo...).
I think this is a pretty good idea. If you want to do something like this, I'd be willing to lend a hand. I am on vacation this week so have a lot of free time anyway.
I think that we could build on that format -
Add major features, bugs, developer name, etc.
Thanks,
-Sf-
It's easier to just link to all of them... you can take the time to go through the Dev's home page. After all, that leaves it up to the topic creator to update every single ROM's bugs and updates, which you can't expect them to do.
Sure, it would be easier to do that...for the posters. But, I feel that the people wanting to check out the roms would appreciate a nice overview of features and bugs then having to wade through some of the toics which can be dozens of pages, if not more. I'll probably start working on this tomorrow, since I've been spending the day figuring out why my parents computer sucks so bad. Found it - 256MB of RAM. ugh lol
this IS a great idea...would be very hard to keep it up to date and what happens if the one guy that posted the topic falls off the face of the earth? as a lot of people seem to do.
not trying to stop it before it begins. i'm willing to comb a topic or two and submit my findings...gonna need a bunch of volunteers to do the same to get multiple ROMs listed.
dusthead said:
this IS a great idea...would be very hard to keep it up to date and what happens if the one guy that posted the topic falls off the face of the earth? as a lot of people seem to do.
not trying to stop it before it begins. i'm willing to comb a topic or two and submit my findings...gonna need a bunch of volunteers to do the same to get multiple ROMs listed.
Click to expand...
Click to collapse
Agreed - I have seen lists on other websites, and they still show evil eris 1.1 as the most up to date. However, that being said, we are the most active android forum out there, especially for the Eris. I think this has the best shot in being the most accurate on the web.
We already have a comparison guide.
Its called xda-developers.com!
Lazy...lazy...lazy....
Just read! Its the best way to fully understand the ROM anyways. Way better than a spreadsheet with checkmarks and whatnot.
But if someone was willing to take the time, which would undoubtedly take A LOT of time, to list pros, cons, features, bugs, versions, updates, and all that jazz, it MAY be worth looking. But we've seen stuff like this before, it gets created, and then never looked at again.
Great idea! Yes people are lazy for not doing their own homework...but there are so many ROMs out there. I have read through almost every page of topics to the 4 or 5 ROMs I have interest in, and often find myself confusing features, bugs, etc of those ROMs simply because there are SO many pages to read through and so much to keep up with(especially when some of these topics are in excess of 200 pages). Among these 200+ pages are maybe 25 pages really worth any knowledge of having about the ROM...the other 175 are filled with redundant information, outdated problems that have been solved, and off topic or unrelated posts.
DO IT!
I was kinda thinking about creating a guide on my website since I can't really think of anything else to do with the domain/server I have lol...
or if someone else wants to, I can give them FTP access to a folder and I'll just host it.
Just an idea.
es0tericcha0s said:
Sure, it would be easier to do that...for the posters. But, I feel that the people wanting to check out the roms would appreciate a nice overview of features and bugs then having to wade through some of the toics which can be dozens of pages, if not more. I'll probably start working on this tomorrow, since I've been spending the day figuring out why my parents computer sucks so bad. Found it - 256MB of RAM. ugh lol
Click to expand...
Click to collapse
Yeah... but what happens if you stop updating? And how will you determine whether bugs are just one persons or all of theirs? And almost every ROM page I've seen has the bugs listed on the first post. I'm just saying the current system isn't just "ok" it's the best way to do it. You don't have to read through the entire thread to know the bugs, you can read the first post.
Well, it looks like interest in this idea is underwhelming at best. I'd be all about putting some time into this, but not for 3 people...
Sounds good to me!
This sounds like a great idea to me. I'll admit it would probably take a great about of effort and time to create and maintain but I'd be more than willing to lend my efforts to put something like this together and help keep it up to date. For all of you who are happy with the current system, it will still be there so keep using it. I don't think this is meant to be a complete list of everything there is to know about a ROM, more of an overview (correct me if im wrong). Plus, this would be GREAT for people who've just rooted and are trying to figure out what to try first. We all know its important to read a thread in its entirety before you flash
Just my $0.02
f z o n g
TheFzong said:
This sounds like a great idea to me. I'll admit it would probably take a great about of effort and time to create and maintain but I'd be more than willing to lend my efforts to put something like this together and help keep it up to date. For all of you who are happy with the current system, it will still be there so keep using it. I don't think this is meant to be a complete list of everything there is to know about a ROM, more of an overview (correct me if im wrong). Plus, this would be GREAT for people who've just rooted and are trying to figure out what to try first. We all know its important to read a thread in its entirety before you flash
Just my $0.02
f z o n g
Click to expand...
Click to collapse
I agree - this list should be an "easy" way to glance over the different ROMs, and do a high level comparison. So if someone prefer's hero ports for example, they can go to the developer's page to determine if that ROM is right for them.
Just like when you research out a new computer, I usually do a high level comparison at first before I start digging into the "nuts and bolts"
I don't think it's a bad idea necessarily, I don't mean to crap all over it but here is what would need to happen:
The poster of the thread would need to understand bugs and things that have to do with the ROM's. They would need to be able to differentiate between one person's bug and a bug that multiple people are having and one that everyone is having.
The poster would need to stay updating this... what happens when they get a new phone? What happens if their computer breaks? Blah blah blah there are a thousand ways you can stop.
Really what you need is a Wiki, that way multiple people could update the information. Developers could submit their own ROM updates if they wanted and users could add reviews, comments etc.
Hungry Man said:
I don't think it's a bad idea necessarily, I don't mean to crap all over it but here is what would need to happen:
The poster of the thread would need to understand bugs and things that have to do with the ROM's. They would need to be able to differentiate between one person's bug and a bug that multiple people are having and one that everyone is having.
The poster would need to stay updating this... what happens when they get a new phone? What happens if their computer breaks? Blah blah blah there are a thousand ways you can stop.
Click to expand...
Click to collapse
+1
for example. . . . what happens when your girlfriend kicks you out and you leave in a rage and forget your computer and storage drives. . . . (was working under the radar on something of the sort but low and behold victim of circumstance.
http://code.google.com/p/erisromtracker/
I'm primarily a web designer but know Rails as well, and a bit of PHP. I'd be willing to put some work into this, but I don't have time to do the whole thing on my own.
I'm thinking of a community-powered web app. Any registered user can edit anything. Edits can be "dugg" by other members to represent validity...I dunno, just some first thoughts.
I made the project page so that people could add ideas/etc and there would be an organized, sane place for figuring out how the whole thing would work, as well as a central repository for any work that actually gets done. It also just doesn't make a lot of sense to use a thread to do this, especially when we're trying to get around people using threads to do this.
^^^^
Eoghann said:
Really what you need is a Wiki, that way multiple people could update the information. Developers could submit their own ROM updates if they wanted and users could add reviews, comments etc.
Click to expand...
Click to collapse
+1
And this
Much better ideas because it's not just one person's job.
Man, I guess I'm one of the lazy ones! Actually, I've been looking through all the ROMs in lust (because I can't root - yet) and I need an easy way to figure out what the main differences are. I'd be in large favor of this!
With the newly deodexed honeycomb I have gotten the itch to start looking into how to create/develop my own rom.
What is the best way to start learning, is there a good starting point, I have been doing some reading but it just seems so overwhelming.
I do have basic Linux knowledge and can whip up a linux VM in no time to get crackin. I have been modding my EVO for the last year so i know how to be a "user" and have tinkered with the xoom but have only scratched the surface.
So my question is just this, Where to start??
any input would be helpful.
+1!
need a little walkthrough too :S!!
and someone can say what files NEVER EDIT to not brick the xoom!!
i too would be highly interested in learning what steps to take.
bossjeeves said:
With the newly deodexed honeycomb I have gotten the itch to start looking into how to create/develop my own rom.
What is the best way to start learning, is there a good starting point, I have been doing some reading but it just seems so overwhelming.
I do have basic Linux knowledge and can whip up a linux VM in no time to get crackin. I have been modding my EVO for the last year so i know how to be a "user" and have tinkered with the xoom but have only scratched the surface.
So my question is just this, Where to start??
any input would be helpful.
Click to expand...
Click to collapse
Get that VM set up, and get your environment set up so you can build AOSP.
Look through the source so you know what parts of Android are found where in the tree.
Learn a little about the platform, what does what...
Basically, just get your hands dirty.
ydaraishy said:
Get that VM set up, and get your environment set up so you can build AOSP.
Look through the source so you know what parts of Android are found where in the tree.
Learn a little about the platform, what does what...
Basically, just get your hands dirty.
Click to expand...
Click to collapse
so this is kind of what I expected for an answer but I would like a little more if you dont mind.
Like maybe a couple of links pointing in the right direction, like what does the environment need for tools etc.
ydaraishy said:
Get that VM set up, and get your environment set up so you can build AOSP.
Look through the source so you know what parts of Android are found where in the tree.
Learn a little about the platform, what does what...
Basically, just get your hands dirty.
Click to expand...
Click to collapse
That's like saying jump in a lions den and see what ticks him off. Can we get more details please? I want to get into theming and want to know the ideal OS to do it on. I was hoping on doing it in Linux but want advice from themers.
IV been playing hippie for a couple of weeks so I don't know if I missed something but, unless the full AOSP source has been released, a deodex rom will help with nothing but theming.
You can't do much to customise a ready built rom, and you would be wasting your time to try anything but the simplest of mods.
That being said, if you're happy to play with smali you might achieve a little more.
Sent from my HTC Desire using Tapatalk
alias_neo said:
IV been playing hippie for a couple of weeks so I don't know if I missed something but, unless the full AOSP source has been released, a deodex rom will help with nothing but theming.
You can't do much to customise a ready built rom, and you would be wasting your time to try anything but the simplest of mods.
That being said, if you're happy to play with smali you might achieve a little more.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
this is exactly what I am talking about here, This is kind of why I brought it up in the xoom forum, since we dont have source and we do have a deodexed rom wouldnt playing with that be a great place to start? if so like what would be the best place to start, you say play with smali, now I know I can google and get tons of answers but I am asking to explain a little more because I trust the feedback from here and I think others might benefit also
bossjeeves said:
this is exactly what I am talking about here, This is kind of why I brought it up in the xoom forum, since we dont have source and we do have a deodexed rom wouldnt playing with that be a great place to start? if so like what would be the best place to start, you say play with smali, now I know I can google and get tons of answers but I am asking to explain a little more because I trust the feedback from here and I think others might benefit also
Click to expand...
Click to collapse
Smali is a tool that will reverse engineer (baksmali) dalvik byte code into (barely) human readable code. If you can learn to understand this you can reverse and modify stuff with it. If i remember right, brut.all is the guy responsible, have a read around, but i warn you, its not for the feint of heart.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
bossjeeves said:
this is exactly what I am talking about here, This is kind of why I brought it up in the xoom forum, since we dont have source and we do have a deodexed rom wouldnt playing with that be a great place to start? if so like what would be the best place to start, you say play with smali, now I know I can google and get tons of answers but I am asking to explain a little more because I trust the feedback from here and I think others might benefit also
Click to expand...
Click to collapse
Here is one of the best sources I've found....... made by cyanogen himself, tonnes of info here.
http://forum.xda-developers.com/showthread.php?t=667298
I did come across this link http://simply-android.wikia.com/wiki/ROM_Development
looks like something that would be a helpful start. thoughts?
ps thanks for the replys
I think the best way to learn anything is just to read a lot, and to search for any questions you have. There are a thousand ways to learn to hack, but they all require the initiative to find answers on your own.
Sorry if this sounds patronizing. I always hated it when I get on a board and ask for something, and some curmudgeon geek tells me "Google is your friend". But it's true. You get better answers faster, as you can avail from the entire Internet, as opposed to the small number of people who reply to your query.
Thanks to the dude who linked to the Cyan advice post. My takeaway is this one line:
"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."
IMO if you are serious about ROM hacking, you need a dedicated linux environment. Cygwin is OK for run-time stuff, but too limited for anything else. If you only want to run basic bash commands, a simpler solution is win-bash (http://win-bash.sourceforge.net).
I'm kinda in the same shoes you are. Android interests me, although I don't have a Xoom or an Android tablet for that matter. Was gonna get a HC tab to tinker, but HC is still too green, so decided on a Nook Color for educational purposes. It's been out a while, and has many hacks already done that I can peruse. That, and it'll be useful for my "read a lot" mantra above.
Typical scenario is;
v 0.1 based on this and that.
v 0.2 changed launcher, added ringtones
v 0.3 new wallpapers, added ram script
v 0.4 added new market, added google+
Excuse me!?! This is not development. This is stealing!
I think these people should just wank instead of copy/pasting. Would be more beneficial for both public and themselves.
Rant over.
Thank you.
calyxim said:
Typical scenario is;
v 0.1 based on this and that.
v 0.2 changed launcher, added ringtones
v 0.3 new wallpapers, added ram script
v 0.4 added new market, added google+
Excuse me!?! This is not development. This is stealing!
I think these people should just wank instead of copy/pasting. Would be more beneficial for both public and themselves.
Rant over.
Thank you.
Click to expand...
Click to collapse
Agreed, but if credit is given to original devs you can't really call it "stealing" cause Android is OSP after all...I'm no dev myself but it does seem many ROMs available are CM tweaks achievable with a few market downloads or simply AOSP with extra's...however sometimes certain ROMs begin as "Zip developments" and get later support with real devs and change fundamental features (kernels, code-base etc.) so it's not all bad...
Totally agree..........
But it's not the actual non-development of new roms that is getting on my nerves the most, its the constant *****ing and arguing through lack of understanding different languages etc etc..........
All i have to say is read the threads carefully as i've noticed some people who don't speak english very well get the hump on as they don't understand clearly what people are saying.
I know i've had my rants in some of these threads before and i don't blame anyone else for doing it too. I've managed to restrain myself the last few weeks as our arguments are falling on deaf ears so whats the point, i'll just ignore the idiots making fools out of themselves by bringing us stuff we've already had for a long time and stick to what i know best.
What you've said is true Scratch...even if the ROM cookers do bring something new often nobody knows what that new stuff is because of the poor English. I'm not trying to insult them but I would recommend, especially with a specialized thing such as compiling/ making a ROM, the English needs to be clear and concise so everyone knows what is being released, what changes have been made and what's been modified. More often than not, as you say Scratch, people get upset because of a misunderstanding. Maybe those struggling with the language can consult friends/devs and ask exactly how to express something they've done in their ROM so everybody is clear on what's happening.
Scratch0805 said:
...I've managed to restrain myself the last few weeks...
Click to expand...
Click to collapse
True, I have got quite a lot to say over this entire fiasco over the Android 4.0 "ports" and "source builds" that is currently playing out in the dev zone like a long dragging soap opera, but, its just not worth it, so, just let them argue over themselves who is first and who is the true dev and what not. Besides, it's not a good feeling when these Zip Devs accuse you of various stuffs when you speak out against them. It's extremely childish and irritating to read those posts, but I guess it can't be helped. Zip developers are not a localized phenomenon, they are everywhere, and since Android and ROMs like Cyanogenmod are Open Source, we have nothing to say, and have to live with it.
There's another new phenomenon which is playing out and can be seen on pretty much every ROM. Someone gets a ROM to boot / work at a basic level, create a thread and build up major hype and hoopla on it, and EVERYONE of these "devs" proclaim "I need help to do this and do that./..... bla bla bla". Zip dev is not such a big issue per se, but, the level of intellect is terribly low among the "devs". I believe most of them are what? 12-13 year olds, and, they act their age perfectly, unlike someone like Jacob.
/End Rant
Case in point, after Arco has announced his intentions and the fact he already has a working port in progress:
I was first, it was my idea, I continue and basta.
Click to expand...
Click to collapse
Enough said.
Ahah, doing small things for the buzz (pun intended), acquiring a fame in trolland
Lol, I've made myself clear on this too.
" the ability to read is good,
the ability to understand what you've read is great "
http://www.androidpolice.com/2011/1...om-developers-i-think-we-need-to-have-a-talk/
3xeno said:
dragging soap opera.
Click to expand...
Click to collapse
Don't you mean aosp opera? Hehe...okay, I'll stop with the bad jokes.
And I fully agree with the topic. Anyone can open up any rom .zip paste in some apps, reflash and repackage it as your own.
Agree with this. Sadly I'm one of the offenders, that will have a moan at people developing zip-roms. I accept that this isnt the greatest way to deal with people on forums like theese. But it seems the only good way to get my point across to people that aren't that great at english.
Although, I must add one thing. I've seen roms get tossed around the development forums like mad. It seems to go like this in the dev. forums.
People create a booting rom. Or compile a new one.
People add a few fixes, someone creates a spin off.
Original dev discontinues rom, other 'developers' ask to continue it, even when they have projects in hand.
Someone picks up the pieces months later. After even the re-contiuned rom is given up with.
People spin roms off from there.
All i can say is dear god. I have been reading all that threads last few days and i was frapped how people are shalow in glorifying them selves and their so called development skills. I didnt want to coment anything cauze i have run into such argument once before with someone who was constantly refusing to understand what i am saying and i dont want to do it again, so i leave my thoughts here.
So people should get on the ground for change and start doing something usefull instead of make dozen threads, first when you dig something, than another one when you are asking if it can be done and finaly one when you "do" something. What they have done is nothing. They are just thanks chasers. In last few days there were more new roms than it was for whole Wildfire lifetime.
I remember tje days when there was just three or four roms and they worked, you hear me, they worked. So stop posting such s**t unles u did something that is realy worth it.
Sent from my HTC Wildfire using xda premium
Yes you are right, zip development is horrible. Lately there has been a major rise in "new" roms that have been hitting the development thread. I swear I have seen at least 5 to 10 roms all based on CM7 or oxygen. And what's different? It's "fast and stable" "Is themed to look like ICS" "Has a script that I actually don't know what it does but it must do something good". And its "my" rom because I grabbed a rom.zip from a device that runs oxygen smoothly and added the boot.img and the build prop right from the CM7 rom.zip and then cooked it and I posted it under MY account so its MY rom. There is a problem though, my genius copy/paste skills on my computer that took forever to build up are limited to actually being able to fix problems with things like Bluetooth and GPS, etc. So what do I do then? Hell I request "help" to fix the problems and once a genius like acro or another real dev comes in and fixes it for me, I take the fix and say it was all MY work. AOSP stands for ANDROID OPEN SOURCE PROJECT. The source is open to anyone that can use linux terminal (that's half the problem). The other problem is that no one could be bothered taking the time to actually learn a skill. They want to do something now, and now only. They won't spend hours and days learning how to program in java or C because it takes "too long" and just wants to begin this so called "deving" now. This is a rant about zip development, but wait you say, I do .zip development though? Yes I do, but what I am talking about is .zip development that is based on a .zip that is actually OPEN SOURCE. If something is OPEN SOURCE there is no point in taking a compiled .zip and "porting it" to our device. You do this because its easy for you to hit download and copy and paste, but you don't "have the time" to setup a download of the source and compile it to a rom. Zip development that is for CLOSED SOURCE on the other hand is way different. HTC, MIUI, etc. are all roms that have no open source code so all the work has to be done based on a .zip. Since the code is not available this is the only option. This in my opinion is the only kind of good .zip development since there is no source to build from. I would love to download the source and mess around with the ICS source and try to compile something but my computer is got really bad specs and my internet is so slow. I will just leave that kind of work to acro and the real devs
I agree with this. Looking through the more recent Wildfire ROMS, I can see a pattern for most. So, I have started to come up with a fight back, for individuality and mostly, for a better mobile experience. It would mean a lot if you could help me out with THIS.
Sorry to ask in this thread, but I thought it might be a good idea
Before I get accused of zipfile developing, I only compiled an edited kernel for the ROM to allow touchscreen to work a little.
I am not a "zipfile" developer and I am not going to be, my interest is in kernels.
I happened to come to xda at the wrong time, first thing kaassaus did was ask me to follow a tutorial to get touchscreen working (which took all of 20 seconds).
I think posting an ICS zip is okay FOR NOW because there is no OPEN source for the wildfire for it, and Arco is NOT breaking the GPL because he hasn't redistributed it yet.
Sent from my HTC Wildfire
We are not accusing anyone. My point is dev section is not a learning section. Those who want to learn development can pop into chefs section instead of releasing a rom with 2 zillion bugs.
There is a reason for this forum is not called xda-tweakers. Because our devs are devs. They are not steve jobs like tweakers.
2nd rant over. Class dismissed
Okay, Zip development is not so bad, actualy is needed in some points. For flashing kernels or some other things. But look at some of that AOSP-fast and stable roms. What do they bring us? Nothing. It is just repacked CM nightly or stable. To "develop" such rom you need WinZip and in best case Android SDK if they decide to decompile and recompile few apps instead of treating them with winzip too to change few icons and voila, NEW ROM. Better yet someome will take any theme and implement it into framework.And he will be so proud because his rom has diferent look. What else we can still expect is ES file explorer instead of OI, Miui galery, themed keyborad, different font and unforgetable scripts which do god knows what. They are the main part. Is that a rom? No it isn't my dear friends. Its a disrespect to any real developer here. All that we already have. We have themes, we have scripts we have everything that flashable and we dont need another yet ****y rom to tell us what is fast and stable.
Sent from my HTC Wildfire using xda premium
I don't find anything wrong in updating an already present ROM's with new applications update ,... even though i must say there is a trend in past few weeks that lot of ROM's in buzz section were merely identical and there was no development in them
I was browsing the old threads of the Dev Zone, and came on this:
http://forum.xda-developers.com/showthread.php?t=884659
Amazing, right? It's deja vu all over again.. (PS - Don't bump that please. lol)
I am a noob, and I know I will never be as experienced as other developers.
That is why I do not develop ROMs, and develop things I am good at.
I have done some basic programming in the past, but what knowledge is needed to jump into custom developing, I am not interested in developing apps per say, I am more interested in developing like Cyanogen Group and many of the awesome Devs on here making Kernals, and Custom Roms, etc. I tend to have some free time on my hands lately, and I figure, instead of waiting for everyone else to do the work, maybe I can do some work and contribute.
If you have any information, please point me in the right direction, with tips, advice, videos, and warnings.
Thank you in advance. :good:
Hey man, i too am interested in developing i use eclipse and can do quite a bit of java and im ok with debugging, if you ever have a project you want to start i would be interested in helping. watch videos on steve kondik. cm has quite a few urls. but from what ive been told is get a rom and import it into eclipse and make some changes and put your own stuff up on xda.
check out this screen shot, has the cm urls on it and the video of steve kondik who talks through tips of building cm and how to start and what it takes hope it helps
twayneo said:
Hey man, i too am interested in developing i use eclipse and can do quite a bit of java and im ok with debugging, if you ever have a project you want to start i would be interested in helping. watch videos on steve kondik. cm has quite a few urls. but from what ive been told is get a rom and import it into eclipse and make some changes and put your own stuff up on xda.
Click to expand...
Click to collapse
twayneo said:
check out this screen shot, has the cm urls on it and the video of steve kondik who talks through tips of building cm and how to start and what it takes hope it helps
Click to expand...
Click to collapse
Thank you, I will check those out. I realize this maybe way over my head, and by the time I can actually program something worthwhile on Android, there will be a Samsung S8 ... lol, but you have to start somewhere, I would like tips by those who have progressed.
I like the idea of simply editing a already made rom, this would be more like tweaking, but at least I could see some action.
maybe you can try to gather a group of 8 more developers, or people who want to learn, and you guys can all create a "circle" on google plus, and do a Google hangout where you can verbally talk with each other, ask questions, and share your desktop so others can see you working/creating a rom, so that way, all 9 of you future devs will have a visual and audio learning experience. that's the fastest/best way to learn and progress. so if you're interested, post your google plus profiles and people who are interested can post their profiles and everyone who is interested in doing this can add each other and make it happen. i personally have no interest in developing/creating roms. just throwing this great tool out there for those who are interested. Maybe a new pioneering team, will form out of this? maybe a cyanogenmod equivalent, or a team kang equivalent.
My suggestion is to learn to theme first. Theme something that isn't dependant on 9.pngs cause those are a bit more complicated. Building custom Roms is fun, but very detailed and time consuming. After you get the theming down, cut a stock Rom up a bit and theme it and presto, custom Rom. I learned from a thread by theimpaler. I think it was called, "so you want to learn to theme".
Sent from my SCH-I535 using Xparent ICS Tapatalk 2