Database Users

Donate to Haykuro!!!

Hey, it just occurred to me that if everyone who CAN donates $20.00 to Haykuro, he will have himself a nice little fund starting up. If you can donate more, do so. This kid deserves our REAL thanks for all of this work. Lets pony up guys.
17 years old and kicking open source ass... he deserves to be rewarded.
EDIT: Find the link to donate on his iphoneproject.com page.

I'll surely give some $$$ if he can quickly fix market issue
by the way, your URL is invalid for paypal.

I donated a while back!

I donated a while back as well. What bugs me is that we have so many other people working on this like Daproy and Korndub and they get no $$$ or recognition for the most part. I say that Haykuro needs to set up a fund and split moneys received between people who contributed to this. None less, he is a genious.

I've had the same concerns as you.
I think Darkrift worked on this as well. Probably when the builds are pretty much complete, someone should put a list of everyone who contributed so we can send them all something as well.

I had some ppl offer donations but I have not worked on this nearly as much as you guys think. What I have done was my way of donating to him since I am poor and cannot do so with paypal. I tried to beta test when I could, write up tuts, answer questions and much the same as everyone else in the thread did. I do not know the extent of the others who are helping so I cannot say the same for them, but I personally have not been working hard enough on this to deserve donations (unless you wanna send me a free G1, I will take that )
If you feel the need to donate to me, send it here https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=4290101

Everyone has been very generous and caring, and I thank you all for that.
This post will give credit where it's due, and let everyone know what's up (clear some confusion).
History of the builds:
1. xmoo and his anonymous source post up a leak of the system folder from a developer magic (or something similar).
2. Everyone on XDA was going crazy, of course, and I tried to explain how to get it to boot properly, and no one listened, so I took it into my own hands to release a functional version.
3. After some talking with barakinflorida, he gave me the idea of implementing aHome into the build that way we had a home screen (at the time, no home screen was available as aCore crashed when you tried opening it).
4. After a week of running it, i noticed a OTA update being pushed (noticed it in logcat) i pulled it and released build 4.
5. I noticed the SPL and posted that, with the proper changes in update-script for the dream. Same thing with the radio.
6. korndub noted that my update-script for the radio was messed up and simply stripped down the update-script (not sure if you guys remember the recovery errors on my radio update, as opposed to korndubs stripped radio update).
5. A week later I got some info from darkrift which led to build 4.5.
6. After some personal tinkering i got google apps from 4.5 ported to build 4, and called it 4.9.
7. 5.0 was then released after daproy noted the camera and audio fix in the master branches of the kernel. he also kindly donated a pre-compiled kernel, saving everyone time from waiting for me to find a linux comp i could compile on.
8. Since then me and daproy have worked together to bring you the next builds. daproy provides me with the kernels, and i do everything else.
I think in the end, the people who would deserve donations would be up to you.
But this is the history of how it all came to be

I would prefer it were told like this (much more heroic):
5.5 Darkrift daringly put the life of his precious G1 on the line to test out various beta builds that haykuro made in a half asleep state. Fending away fire and deadly battery pulls, he made sure everyone who flashes one of those roms would still have a working G1.

Darkrift said:
I would prefer it were told like this (much more heroic):
5.5 Darkrift daringly put the life of his precious G1 on the line to test out various beta builds that haykuro made in a half asleep state. Fending away fire and deadly battery pulls, he made sure everyone who flashes one of those roms would still have a working G1.
Click to expand...
Click to collapse
lol oh yea, that too.. well, as you said. i was half asleep through most of that

Excuse me for being a NoOb, but here goes....
.... Is it possible to send my girlfriend through paypal? If so where can I find a "how-to"? It is very well deserved.

If she is hot, just send pics :S

Just donated $20 to the man ............. hope others follow and donate.
Keep up the good work man!

I donated a decent amount to hay and never even got a thank you. I will not donate again to him. The least he could have done was sent a thank you...

I'm gonna go ahead and give a big thanks to Haykuro/Darkrift since trying to install a2sd for the first time by following Darkrift's instructions led me to write my original tutorial(how passe that tutorial of mine seems now..), and subsequently my appstosd app, which led to the unionfs method and appstosd2. Of course other people helped along the way(TheDudeofLife, MartinFick, JF) but it was really Haykuro and Darkrift that got me going.
In short: you can partially thank both of them for having unionfs(somewhat ironic considering it was Haykuro's ROMs that never implemented it (j/k man, I think I had enough trouble trying to debug my script with TheDude's ROM))
EDIT: Upon rereading I realized that this could be taken as somewhat backhanded. I didn't mean that Darkrifts instructions were so bad I had to write my own. He intentionally(I now fully understand why) left out some parts of the process and I thought I'd take up the torch and try to have the whole thing in a way I saw as a little bit safer(or at least less scary).

[email protected] said:
I'm gonna go ahead and give a big thanks to Haykuro/Darkrift since trying to install a2sd for the first time by following Darkrift's instructions led me to write my original tutorial(how passe that tutorial of mine seems now..), and subsequently my appstosd app, which led to the unionfs method and appstosd2. Of course other people helped along the way(TheDudeofLife, MartinFick, JF) but it was really Haykuro and Darkrift that got me going.
In short: you can partially thank both of them for having unionfs(somewhat ironic considering it was Haykuro's ROMs that never implemented it (j/k man, I think I had enough trouble trying to debug my script with TheDude's ROM))
EDIT: Upon rereading I realized that this could be taken as somewhat backhanded. I didn't mean that Darkrifts instructions were so bad I had to write my own. He intentionally(I now fully understand why) left out some parts of the process and I thought I'd take up the torch and try to have the whole thing in a way I saw as a little bit safer(or at least less scary).
Click to expand...
Click to collapse
I only started this thread because I know that this kid is 17 and still working on getting his HS diploma, also holding down a job AND working on these roms. Even after he was burned by someone on the forums, he came back when it was ready and gave us Hero (with a NEW Rosie smell)... He continues to put out roms for us and now the canucks with the Rogers rom. I also just saw that there's a Hero rom he just put out for those running Magic/Sapphire devices. The kid continues to work hard on this stuff and I think he deserves to be rewarded. No matter who was helping him get stuff to make the builds lets remember WHO brought the first cupcake to the masses... Now he's brought us a GOOD (not great yet, but it'll get there) version of a rom that we aren't even supposed to have ACCESS to!!! I, for one, think that this guy should get together with JF and Dude and whoever else and start a consortium and start getting paid to develop for Android. This is the OS of the future (for now) and there is some serious need for dedicated programmers who can make it all work... I think he is more on top of it than anyone out there...
That's what made me post this... I have donated a couple of times to the kid, and I'm not done. It's not to pay him for his product, but to thank him for working his butt off on something that he doesn't have to and then giving it away to the masses (again, he doesn't have to)....
So again, Thanks Haykuro and I hope your situation changes soon... Keep up the coding man....
ChicoJD

chicojd said:
I only started this thread because I know that this kid is 17 and still working on getting his HS diploma, also holding down a job AND working on these roms. Even after he was burned by someone on the forums, he came back when it was ready and gave us Hero (with a NEW Rosie smell)... He continues to put out roms for us and now the canucks with the Rogers rom. I also just saw that there's a Hero rom he just put out for those running Magic/Sapphire devices. The kid continues to work hard on this stuff and I think he deserves to be rewarded. No matter who was helping him get stuff to make the builds lets remember WHO brought the first cupcake to the masses... Now he's brought us a GOOD (not great yet, but it'll get there) version of a rom that we aren't even supposed to have ACCESS to!!! I, for one, think that this guy should get together with JF and Dude and whoever else and start a consortium and start getting paid to develop for Android. This is the OS of the future (for now) and there is some serious need for dedicated programmers who can make it all work... I think he is more on top of it than anyone out there...
That's what made me post this... I have donated a couple of times to the kid, and I'm not done. It's not to pay him for his product, but to thank him for working his butt off on something that he doesn't have to and then giving it away to the masses (again, he doesn't have to)....
So again, Thanks Haykuro and I hope your situation changes soon... Keep up the coding man....
ChicoJD
Click to expand...
Click to collapse
? Was this responding to mine? I was honestly thanking Haykuro as well... (maybe I'm misunderstanding something?)

[email protected] said:
? Was this responding to mine? I was honestly thanking Haykuro as well... (maybe I'm misunderstanding something?)
Click to expand...
Click to collapse
No necessarily... I was actually just trying to explain why I singled him out for donations. I don't know him personally, have never seen the kids face... All I know is that he's been dedicated to making the device better, and sharing it with all of us, all the while going to school and work, dealing with everything that comes with being 17! I noticed some posts that mentioned all who helped him, and that's fine. This is about helping a kid who really needs the help. Who knows, Steve may be the next Gates or Jobs!!!

lock close delete, this is going to end up being one of those fanboy threads that get ugly.

koxx said:
I'll surely give some $$$ if he can quickly fix market issue
by the way, your URL is invalid for paypal.
Click to expand...
Click to collapse
that's a permission issue most likely, run the "auto lucid" .bat program on these forums and it can restore the permision to apps2sd folders

dbhatesyou said:
lock close delete, this is going to end up being one of those fanboy threads that get ugly.
Click to expand...
Click to collapse
Only if someone tries to make it ugly! And for the record, I'm no-one's fanboy. Let's look at it this way... In a community, those who have the means help those who need and deserve the help. Haykuro is in the latter group and a lot of us are in the former group. Would you have a thread closed based on the fact that you don't agree with the material? Does that sound like the way things are done on this board? If it is, I'm out!
EDIT: Mods, if you feel there's a better category than Dev for this thread, please feel free to move it...

Root ROMS....Comparision guide?

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!

Sick of zip developers (rant)

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.

ROM Release Rate

I understand, after 2+ years, that ROM development and the forums for the EVO are gonna slow down. Devs are going to move on to other devices, but there is a really disturbing trend here that is irritating the hell out of me.
ROMs used to be released as Aplha's Beta's RC's, final, etc. You could look at the OP and see everything about the ROM. Devs took their time crafting something unique.
Now, I'm seeing these ROMS come out at a rapid pace and I'm not liking it for several reasons.
1) Poorly written OP's that don't even list the Android base version or the kernel, etc.
2) The same ROM with different names and the only real differences are a few 3rd party apps, or a slight theme change.
3) ROMs released as finals, with a ton of bugs. I'm not talking about FFC, Netflix, 4G bugs on ICS/JB ROMS; I'm talking about ROMS with no Wifi, for example. The majority use WiFi. Why the HELL would you release something where one of the most important aspects doesn't even work?? It's like not paying attention to details is suddenly OK
Settings that don't stick. Sounds that don't stick. Constant System Process Errors. These are pre-release errors, and I don't see them getting fixed, because it's become like a race to port every other ROM from every other device and tweak to boot up on the Evo, then letting it go.
I REALLY wish I could take the time and learn how to properly cook up my own ROM. My OCD of paying attention to details would probably make it great.

Hipkat thats the best thing ive heard in weeks,someone finally speaking out about the BS thats being posted now days and its like everyones in a race to see who can come out with the most borked roms,lol,like you said,they are all the same,except the apps and some themeing and half of them cant do that either,i'm sure this isnt meant to be a bashing session,its just getting rediculous with the drama some are causing and all the crappy ass roms being released,some guys do know what their doing,theres been 1 or 2 that i've put out that i shouldnt have,but come on guys at least take your time and try to do it right,only takes a little common sense and effort.If you havent noticed,over half the members and devs have left because of the BS,when i started doing roms,it was fun,nows its just a big joke,lol.
I dont care if anyone gets pissed about this and i'm sure they will,but oh well life goes on,you will eventually get over it.

It's definitely not a bashing, but a call for Devs to take a little more time and do it right

HipKat said:
It's definitely not a bashing, but a call for Devs to take a little more time and do it right
Click to expand...
Click to collapse
I don't Dev, Cook, Build, Port or whatever term is used so I have alot of respect for those that do. With that being said I would also state that I am in complete agreement with you and Diablo.
I look at damned near every topic started in the Dev forum just to see what is being made. I take weeks to look at a new ROM and follow the threads to see what comes of it (with the only exception being Mazda's new CAJB ROM. On that one I went with name recognition and am pleased that I did)
In regards to the mass influx of ROMs I'll say this: If you guys don't take the time to keep up with each item you produce, work on bugs, add new options, answer questions from the users then you'll soon find yourself out of favor. Your reputation here, just like in RL, is something of value. It takes very little to earn trust, respect and loyalty. Most people will always give you the benefit of the doubt. Do something to devalue that trust and it can be nearly impossible to regain.
I think some wisdom can be gleaned by the following quote:
jamieg71 said:
I've seen devs, chefs, hackers, w/e, that make statements like "I do this for myself and just choose to share" or things to that effect. I call BS. I won't speak for anyone else but myself when I say, I do this for the thrill of it, for the challenge, to learn, and to share. I'd be lying if I said I didn't care about d/l numbers or that seeing my thanks meter grow did not give me some juvenalalistic (is that a word?) thrill. The fact is, guys like me doing this stuff get off on it...
Click to expand...
Click to collapse
We know why you do it, and if you want to keep your junkies and not lose your rep, then make sure you take the time to Develop your craft and thereby make a better product for the masses...
Sorry for the rant

Well said, and nice quote from Jamie, who, btw, you notice took a lot of time with Reloaded

HipKat said:
Well said, and nice quote from Jamie, who, btw, you notice took a lot of time with Reloaded
Click to expand...
Click to collapse
...lol, 'nuff said!

I think everyone needs to remember the difference between Development and Port / Theme / Tweak / Mod. That simple labeling would be a start

Over in Evo LTE land, they have finally recognized this distinction by creating entirely separate forums for "HTC EVO 4G LTE Android Development" and "HTC EVO 4G LTE Original Android Development"
One is for tweaks or ports, and the other is for people who actually compile something.

I made a request for the same original dev section but got denied as our device is to old.
I agree that there are a ton of ports and not enough originality or bugs being fixed. What I would like to state us that the op is stating that a lot have some third party apps but that's like calling the kettle black. You yourself have a rerelease of a miui from where all you did was slap your team name in the thread. I believe the original thread still exists. I'm not calling you out at all but at the same time the work that goes into all these ports or mods or what not is a ton. I myself have my rom thread and some new stuff coming out but I don't call people out usually on their stuff unless its a pure kang(meaning an actual using of ur work with out permission) not a duplicate port.
Yeah some of the revs here could put a little more work in and for sure learn to organize their rom thread a whole hell of a lot better but at the same time who else do u see bringing the newest and best to a two year old device.
XDA Moderator

It's not that they have 3rd party apps, all ROMS do, it's that some ROMS are just the same ROM with a few different 3rd party apps, or a slight variation in theming, and I mean real slight, but tbh, my biggest beef was with the OP not even listing what kernel is in the ROM, or if it has A2SD or a way to get it working, or the version of Android it's based on, etc.
Add in bug reports that get ignored or the person posting the report gets demeaned for it.
Mostly, it's just the sloppiness that I see going on over the last few months. Too hasty to release something without really perfecting it first

HipKat said:
It's not that they have 3rd party apps, all ROMS do, it's that some ROMS are just the same ROM with a few different 3rd party apps, or a slight variation in theming, and I mean real slight, but tbh, my biggest beef was with the OP not even listing what kernel is in the ROM, or if it has A2SD or a way to get it working, or the version of Android it's based on, etc.
Add in bug reports that get ignored or the person posting the report gets demeaned for it.
Mostly, it's just the sloppiness that I see going on over the last few months. Too hasty to release something without really perfecting it first
Click to expand...
Click to collapse
I can agree with that there. sloppy op's without all the listings of what is added or taken out and what its running with a q & a section amoung other things.

I feel like we developers and porters alike should make a check list. Every time you want to post something, run through the list and then once everything is there, read again. If it seems like a business proposition (detailed, understandable, provocative and complete) then, that is the right moment to unleash it.

Thats exactly what i do,i make a list in notepad of what i want to do to the rom,then i go through and check it off as i go,wahla,i have a channelog,so to speak,then post it on the thread.Just like in my 4 Kornerz thread..... http://forum.xda-developers.com/showthread.php?t=1612933

Same thing I'm gonna do as I try and update this MIUI GB ROM

What's funny is that the main reason I always hated opening ROM threads is because I'm completely OCD and feel like the posts have to make perfect sense. I try for my thread to make a little bit of sense at least at this point. And I try to keep change logs, bug reports & FAQs up to date.
But then again, I only have one ROM thread in this device section.
----------------------
Current Device: HTC EVO 4G LTE | ROM: toasted-deck CM10 | Kernel: Stock

Kernel should be listed.
a2sd included/not included AND if a specific version is known to work/not work.
Gapps included/not included (you can usually tell from the size of the ROM, but still)
SuperSU vs. Superuser
Wifi and data working/not working
Boot animation audio (can lead to uncomfortable moments when flashing in restrooms, in bed, around family or in TSA security lines--- yes, all personal experiences)
Probably much more...
RootzWiki kinda sorta tried to standardize some of that in OP headers. Would be cool to see that concept expanded in a visually pleasing manner. But, I know people like sprucing up their OP to their liking. Example:
Source: https://github.com/s...mmc-ra-recovery
Mod Type: Recovery Difficulty: Moderate Mod Status: Kang Mod Base: Carrier:
Requires Root: Yes Apply In: Fastboot Optional: Themed Optional: Android Version:
I think ports are great. If the developer is planning on just bringing it over and leaving it alone I think that's fine, but they should be upfront and say "Hey, I did this. Probably won't do any more with it myself, but anyone is welcome to add to it. Otherwise, enjoy."
What I'd really like to see is the people who respond first after an OP + OP reserved do something with that slot besides planting their flag of happening to be online at the right time (e.g. "First. Looks cool!"). They could take the lead, especially for very active developers with many ROMs and threads, to follow that thread and maintain an updated ROM Cheat Sheet/Known Fixes post. How many times have you followed the development of a ROM and things like the new boot animation didn't make it into the next update because the developer forgot. Then people post, "Hey, what happened to the boot ani" five or six times. Then a nice person posts it on Dropbox. Then a few people say other things. Then people repeat the question. Then people point them to the Dropbox link two pages back. Repeat. Repeat. Probably wouldn't matter though since a lot of people never read the OP. They sure wouldn't read that. I'll shut up.

smelkus said:
Kernel should be listed.
a2sd included/not included AND if a specific version is known to work/not work.
Gapps included/not included (you can usually tell from the size of the ROM, but still)
SuperSU vs. Superuser
Wifi and data working/not working
Boot animation audio (can lead to uncomfortable moments when flashing in restrooms, in bed, around family or in TSA security lines--- yes, all personal experiences)
Probably much more...
RootzWiki kinda sorta tried to standardize some of that in OP headers. Would be cool to see that concept expanded in a visually pleasing manner. But, I know people like sprucing up their OP to their liking. Example:
Source: https://github.com/s...mmc-ra-recovery
Mod Type: Recovery Difficulty: Moderate Mod Status: Kang Mod Base: Carrier:
Requires Root: Yes Apply In: Fastboot Optional: Themed Optional: Android Version:
I think ports are great. If the developer is planning on just bringing it over and leaving it alone I think that's fine, but they should be upfront and say "Hey, I did this. Probably won't do any more with it myself, but anyone is welcome to add to it. Otherwise, enjoy."
What I'd really like to see is the people who respond first after an OP + OP reserved do something with that slot besides planting their flag of happening to be online at the right time (e.g. "First. Looks cool!"). They could take the lead, especially for very active developers with many ROMs and threads, to follow that thread and maintain an updated ROM Cheat Sheet/Known Fixes post. How many times have you followed the development of a ROM and things like the new boot animation didn't make it into the next update because the developer forgot. Then people post, "Hey, what happened to the boot ani" five or six times. Then a nice person posts it on Dropbox. Then a few people say other things. Then people repeat the question. Then people point them to the Dropbox link two pages back. Repeat. Repeat. Probably wouldn't matter though since a lot of people never read the OP. They sure wouldn't read that. I'll shut up.
Click to expand...
Click to collapse
LOL, you forgot 'Lather, Rinse...'
Who else clicked the link

While I agree with the OP 100%, I think at the end of the day there is NO rule that states that you need to do all that..... This is for FREE, and therefore we should be happy with we get on our EVO's nowadays..... I wish developers took their time to put a fully detail change log, bug list Q&A's section, but honestly if we don't like the way certain devs handle their threads, then just move on to the next Rom either way I don't develop, and I can figure out most stuff regarding a Rom by myself now, so I'm just thankful for all the roms out for the og EVO.
Edit: what I would like to know is what's going on with all the Rom teams flip flopping, what's up with that? Sorry to go off topic, lol.
Sent from my PC36100 using xda premium

Sorry, but while I appreciate the freeness of the work done and am grateful for it, there should still be enough info to identify exactly what you're getting into.
Perfect example. A lot of ICS/JB ROMS require the patched A2SD file. Good luck finding it. Why not add a link to the OP?? Same with GAPPS
And the date that it was released is much appreciated, although not as critical. The Android version if it's a Sense and/or GB ROM is definitely something that should be there, along with the kernel.

PHE-NOM said:
Edit: what I would like to know is what's going on with all the Rom teams flip flopping, what's up with that? Sorry to go off topic, lol.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Two teams merged. Some people have left teams. I myself left td to not look partial towards a certain group.
XDA Moderator

Need help with choosing a rom

There are so many choices and I am a bit overwhelmed on what I should use. I have the Note 3 SM-N900W8 version, this phone is for my dad. I just want a simple android environment that would be Google certified(if that's a thing) so he can use apps that do not like root like Netflix. I was hoping something that is similar to base android 6 or later, I have no idea which roms would work that would be simple to use. I was hoping something like what I would use on my Nexus 6p called Pure Nexus, but obviously, it's for that phone only but would have been perfect. The current one he uses is always giving him trouble when updating apps with security options that he never has any idea what to do, so I get stuck having to do it for him. Sorry that I am all over the place with this post, but hopefully someone understands and knows what would be good. Thanks

See multiple identical what rom best rom posts .
ROM descriptions are posted .
https://forum.xda-developers.com/galaxy-note-3/development
https://forum.xda-developers.com/galaxy-note-3/orig-development
I would suggest if its for somebody else and you don't know what you are doing/ cannot read rom descriptions then stick with stock rom .

Yes I am very aware of those pages, I was just hoping from someones experience, if anyone has come across something similar to Pure Nexus. I know how to install and all that stuff. Starting to feel it was a mistake to post this thread...

nenitosoyyo said:
Yes I am very aware of those pages, I was just hoping from someones experience, if anyone has come across something similar to Pure Nexus. I know how to install and all that stuff. Starting to feel it was a mistake to post this thread...
Click to expand...
Click to collapse
It is hard to say what your need for a rom are. Every one uses there devices diffrently. What works great for me might not be good for you. And viseversa. There are never stupid or dumb questions. Even though it has been asked many times over. Best advice is to search and read and try each of them to see what fits your needs.
Btw i have at&t so I am limited on what roms I can use as I have a locked bootloader.

TheMadScientist said:
It is hard to say what your need for a rom are. Every one uses there devices diffrently. What works great for me might not be good for you. And viseversa. There are never stupid or dumb questions. Even though it has been asked many times over. Best advice is to search and read and try each of them to see what fits your needs.
Btw i have at&t so I am limited on what roms I can use as I have a locked bootloader.
Click to expand...
Click to collapse
Thanks for the advice, I am researching over what is available and taking my time to make sure I choose the right one. Thanks again.