Develop Bugs

Roms w/ descriptions... WHERE?

Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App

3ndless said:
Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This took like 0.1 sec on google:
http://alchemistar.blogspot.com/2010/11/samsung-epic-4g-custom-rom-list-1110.html
A list is not maintained on XDA.

Go here! Click on your model below
http://forum.xda-developers.com/wiki/index.php?title=File:Samsung_Epic_4G.png

3ndless said:
Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Just look up "Samsung Epic 4G Rom XDA" on google and you'll find a whole selection of roms. Then just read their descriptions and some comments to find out what they're all about. I'm a little disappointed that this was you first contribution to the XDA forums...

RandomKing said:
Just look up "Samsung Epic 4G Rom XDA" on google and you'll find a whole selection of roms. Then just read their descriptions and some comments to find out what they're all about. I'm a little disappointed that this was you first contribution to the XDA forums...
Click to expand...
Click to collapse
Wow, don't need to be so "Humble" you guys, thanks anyways...
Sent from my SPH-D700 using XDA App

3ndless said:
Wow, don't need to be so "Humble" you guys, thanks anyways...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Oh relax, it's all in good fun. We answered you .
But you'll have a lot of questions, we all do, and you'll get your answers faster 9 times out of 10 by checking if someone already asked them first.

RandomKing said:
Oh relax, it's all in good fun. We answered you .
But you'll have a lot of questions, we all do, and you'll get your answers faster 9 times out of 10 by checking if someone already asked them first.
Click to expand...
Click to collapse
Ok, really sorry for the bother I could cause its just that i've been looking in Google about this and its very confusing. ALWAYS appears something new about this theme & I want to already finish with it to fully enjoy my equipment.
Sent from my SPH-D700 using XDA App

Theme? What do you mean?
-Sent from my custom INC Epic.

Hey I was new to it myself and as long as you can put your phone in dowload mode you have really nothing to worry about just make sure your cable is good and you have the stock rom and your good
Sent from my SPH-D700 using XDA App

3ndless said:
Wow, don't need to be so "Humble" you guys, thanks anyways...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Random's post was actually very humble, some people get crucified for not searching lol

We do need a clearer documentation of ROMs
Personally, I think OP's request is completely valid. There are a multitude of ROMS. The roms really don't have any specific vision statement such as "My goal is to be the most stable rom" "my goal is to be the most bleeding edge ROM" "my goal is to be the quickest ROM" or "my goal is to be the fastest ROM, even if stability suffers". Instead each rom seems to be a person who then does some personal tweaks and incorporates the generally available tweaks others have posted.
There's also not a clear change from version to version other than, (hopefully), the release notes which may list "teaked X", "changed Y" which doesn't help me understand if the next build is more stable, smaller, faster, or what.
Also, it's hard to tell the riger put into the software development process. While some ROMs are team built and significantly tested, it's hard to tell which. I assume ACS and Bonsai both have many people testing for many weeks prior to releasing a ROM, but I don't know that. And for the smaller ones, I have no clue.
Ultimately, it would help for someone who has enough experience with each ROM to document the differences. Alternately, a template for ROM developers to fill in each version might help. Something like.
GOAL OF ROM: (if multiple goals, list in order of importance to the developer)
DEVELOPER/DEVELOPERS: (by name, handle, or # of developers)
MAJOR BUILDS INDICATE A CHANGE IN... (time, tweaks, base build, etc)
CODE MANAGEMENT PROCESS: (formal repository, versioning in development package, 1 set of source files edited in VI with no backups or versions)
TEST PROCESS: (length of test, number of test subjects, any stress tests/unique situations/or boundary scenarios included in testing)
SUPPORT OPTIONS: (post on board, email development team, IRC, fire and forget, normal response time, etc)

You need to do what I and most of us did....read the threads following the ROM releases. Every phone is different but if 10 people on the ROM thread report Bluetooth issues and BT is important to you, don't use it. There are no info shortcuts here. Read the ROM threads.
Do you BONSAI?

Unfortunately, it's completely impractical to read through hundreds of posts per ROM to understand the pre-existing bugs with each ROM. Additionally, those bugs are tied to a build. The build they are associated with is usually not apperent from the posts.
The only way to keep up is to skim each rom regularly so you can maintain the current state of each ROM. it doesn't allow people to come in from a cold start and understand what's going on. That would be a good thing to add to the manifest listed above though:
KNOWN OUTSTANDING ISSUES:
REPORTED BUGS:

gdbassett said:
Unfortunately, it's completely impractical to read through hundreds of posts per ROM to understand the pre-existing bugs with each ROM. Additionally, those bugs are tied to a build. The build they are associated with is usually not apperent from the posts.
The only way to keep up is to skim each rom regularly so you can maintain the current state of each ROM. it doesn't allow people to come in from a cold start and understand what's going on. That would be a good thing to add to the manifest listed above though:
KNOWN OUTSTANDING ISSUES:
REPORTED BUGS:
Click to expand...
Click to collapse
Most of the big developers make an effort to list the large and recurring issues in the first page of the thread. Most other bugs tend to be one-offs caused by a bad flash or failure to wipe data prior. I understand where you're coming from, as I felt the same way when I first jumped in. Mind you, I got the phone in November of 2010, began actively following various threads within a few weeks, gained a vast amount of knowledge on the matter, didn't first root until the EB13 update in February, and didn't even sign up to the forum until March, after which I began helping others with problems I had found answers to months before even making my first post.
I don't preach hypocrisy. I generally criticize an oft-repeated question while also answering it or linking it to one of many long-existent answers. I preach learning by reading. If I tell you how to fix something today, you'll come back with a problem tomorrow because you didn't earn the knowledge for yourself, and you didn't understand what you did. The age-old parable:
"If you give a man a fish, you feed him for a day. If you teach a man to fish, you feed him for a lifetime!"
I strongly suggest everyone read as much as they can to understand as best they can! Take your epic to the toilet and read in your spare time!
While your idea is a noble one, it's a much larger undertaking than you're giving it credit for. Developers would have to collaborate to give a list of specifications, known bugs, etc. to one thread. Someone would have to oversee this thread, take in additional posts to this thread, and append them to the front page continuously. The end result would be roughly what each individual thread already attempts to achieve, with a much larger scale of chaos and a huge problem with out-of-date details.
The list Kenny linked contains a list of known Epic roms and their latest update. You could make this an XDA thread, but I can't say that trying to include every detail and bug beyond that of every rom is a good idea.
That said, look around. Find a Rom. Read about its details. If it sounds good to you, give it a test run! Use what works for you, don't obsess about which one is the "best".
-Written by a man with nothing to do during his lunch break.

No one should be "jumping in cold" and rooting and throwing on ROMs. I got my phone in September, read through posts on ROMs that had features I liked, then 6 weeks later rooted and tried a few ROMs. There are videos now in the General stickies to help cut down on the reading but as stated every phone is different right out of the box. One ROM may cause a messaging issue with a small group whereas another Bluetooth issues. Most developers list known bugs being worked on in the OP.
Do you BONSAI?

try this on youtube
qbking77 on youtube. put in search box 'How to Root Samsung Epic and flash SyndicateFrozenRom 1.1.0/1'. cannot post a link at this time, I'm too new

Actually, I read XDA every day (work's been slow recently). I've rooted my phone and installed more roms than I can count. (Also rooted my wife's and her viewsonic gtab.)
I agree that the major rom builders do a much better job of managing and documenting their development process than most 1-man outfits. However, I still can bearly tell the difference from 1 ROM to the next or 1 build of a ROM to the next. (As far as I can tell, what we have are pretty much the same ROM a dozen different times with slightly different bugs.) A standard for ROM developers to fill in would hopefully help them in focusing their ROM as much as it helps people in understanding the goals of their rom.
As for the effort involved in keeping it up-to-date, most of the worthwhile developers update their main post or start a new one at each major build. Adding some structure to that update wouldn't be a significant increase in hastle.
on a completely separate note, I understand where you are coming from with the "teach them to search" montra. (I helped moderate a very large everquest form for years.)
Since then though, I've realized that, while it's very popular on message boards, it's not very useful. You have to either have a very good understanding of where on a message board to look for the information you are interested in or you need to be a very skilled searcher. Otherwise you end up spending a significant amount of time pouring through poorly summarized search results which don't address your question without knowing if there IS an answer somwhere. While the (here are similar threads) function of vBulletin is reasonably useful, the xda search powered by google is impossible.
Wiki's form a MUCH better way of collecting answers to message boards than bulletin boards do. Unfortunately, you need your WIKI and your forum tightly integrated, (which means a CMS rather than vBulletin + mediawiki). Also, you need forum posters who, after answering a question on the forum, turn right around and post the answer into a wiki page to ensure it was there for the next person

(Actually, it'd be really cool if every Q&A forum on XDA, instead of pointing to a normal forum, pointed to a wiki answers type software install (http://wiki.answers.com/) tailored for XDA. That would hopefully significantly cut down on re-asking of questions. )

3ndless said:
Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You can look in the development area, the threads are there for the ROMs. Typically the first few posts of a ROM thread will be the information about it. Then read a few of the pages (near the beginning and the last few) to get a feel for what users are experiencing during their use of the ROM.
That should give you the information you're looking for.
Good luck

I would suggest you look into the following excellent ROMs
Midnight v 5.3 which is based on Bonsai. This is my favorite and Rob is very helpful about his and other peoples ROMs
Bonsai itself which you have to go to their site for
Syndicate Frozen 1.1.1 from ACS.
Frankenstein when ecooce finishes the newest one. This is based on the ACS ROM
There are some other ones on here that I just don't know as much about. All of the developers use each others stuff so no matter what you go with it is better than stock.
You will learn a lot from your mistakes when flashing ROMs but the trick is to read a lot through the forums so you can learn from others mistakes.
Samsung Epic Midnight

[Bounty] dsexton207 (no trolling in this thread, only dedicated donators)

Here in XDA we do not encourage [BOUNTY] due past horrid experiences many people were victim off.
Thus in most other section of the forum [BOUNTY] are actually illegal to say the least.
However if the [BOUNTY] are for a good cause it'll be allowed under a few conditions.
- The [BOUNTY] is to be donated directly to the DEV
- The [BOUNTY] will only be donated when the DEV work is complete
- You are not allowed to make demands to the DEV
- You can't promote yourself for a [BOUNTY]
- The Dev's work must be creative/original development, not just ported-themes, modified stock ROMs or kanged ROMs
- Must be Recognized Developer or at least have a good well known reputation in XDA
AGAIN NO TROLLING ON THIS THREAD!
dsexton702 is a dev most familiar in the Samsung Galaxy S 4G forums and is an avid rom dev. He constantly updates his tweaks and roms infact he made so much development hes a recognized developer!
And i communicated with him a couple times and hes willing to sell his old phone to lower the price of the galaxy s 2. He's a willing dev and i know he can deliver a whole amount of joy for our BEASTLY phones!
reasons:
1. Updates frequently.
2. He joined in april of this year and is already a recognized dev (for those of you who dont know, there are devs out there that joined 3 years ago and still isnt recognized).
3. He will make us great roms, not just any old rom he tweaks it like non other and even loves to hear requests from his testers (pretty much lets the whole community be the testers, even alpha builds)
4. He has never ever let me down on help, he will always give you advice on anything he knows unlike the lazy devs who just post their stuff and dont comment back.
5. every rom or devlopement he has out right now in the Galaxy s 4G forum is widely known and used.
6. May i remind you he posts DETAILED instructions to flash anything he makes? (some devs dont even do that, let alone post screenshots)
"Why bounty dsexton he hasnt done anything for us yet?" Well listen he hasnt got the phone alright? its like youre going to eat a pie without a mouth, which is highly not possible.
He can port his:
ICBINB roms(which are silky smooth)
Adrenaline shots
(which makes our phone smoother than the stupid iphone and better battery life)
Most likely be one of the first to modify our roms once the inid.t folder comes out to our soon to be modified kernel!
Paypal:substitute his S2
People who donated:

[REQUEST] AOSP/CM10/etc buildbox donation thread [info inside]

PayPal here:
Any donations and/or support are greatly appreciated.​
11/14/12: withdrew monies from PayPal. Putting it towards purchases of some more hardware. Leaving the donation link up because this project could surely use much more support! Thanks to everyone who contributed so far!
10/30/12: made a quick update to the chipin site. Still working on getting the chipin site and Paypal to sync properly, but all donations are definitely showing in the Paypal, so no worries.
UPDATE: The first donation of up to $50 dollars, I will match with a donation of $50.
UPDATE 2: Due to popular demand, there will be a "learner box" created for those that want to "experiment" with development on a faster machine. There should be enough parts to put it together and have it running as we approach the current project goal.
This is the official buildbox support thread. Many of you are probably wondering what a buildbox is... I will try to explain without getting too far sidetracked!
---Purpose---​We are trying to raise money in support of multiple roms/devs. This is not for one particular dev, nor is it one particular rom. Consider this a donation to the community in which you are a part of. This is helping the devs have more resources at their disposal, and ultimately, helping you have a better rom! Please read below for more of an explanation.
---What is buildbox?---​For the open source community (CM10, Paranoid Android, CNA, etc), the roms are built from source. Doing this is not very easy, nor is it quick! It takes a lot of time and effort. I don't want to simply 'thank' the devs and leave it at that. So, I have made a contribution to the open source community. I have commited a powerful server to the devs that choose to use it for building open source roms.
Now you say, "So what... they could use their own computer and build roms..."
Yes, they could. However, look at this. For many devs (especially since ICS and above), the build times have increased significantly!! I'm talking 4+ hours in some cases! In steps the buildbox. The buildbox (in it's current condition) has cut most build times to between 20 and 30 mins.
Then you ask, "Why does that matter to me?" Well, the quicker the rom is done, the quicker we discover bugs, and, in turn, can FIX bugs! Think about it: If you were waiting in the lobby at the car dealership for some work to be done and it was going to take 3 hours to complete the work, you wait. You aren't getting anything done. Now, if you were able to speed the process up to 25 min, you could get much more done that day because you aren't stuck for over 3 hours!
---Why does this matter to you?---​Maybe more choices of roms, maybe nightlies of your favorite roms, maybe less bugs! A small donation toward our goal will help keep the hardware current and allow for the devs to get the great benefit of a powerful machine. Hard drive space is quickly filling up, the RAM is over full utilization, and other hardware improvements can be made.
PayPal here:
Any donations and/or support are greatly appreciated.​
Currently supported devs (a big thanks goes out to them and their work!): Phantomphreak53 (CM10 nightlies), kbizzle (Paranoid Android), and justlovejoy (CNA)
PS: If anyone is looking for more info, has suggestions, or is interested in the project, feel free to pm me. All of the devs can vouch for me (even a couple not listed here). This is a legitimate request. We are counting on the open source community to keep this project going strong.
tl;dr, support open source development and make a donation to the development tools!

This Dude Is Amazing In his efforts to contribute to the true meaning of AOSP for ALL!
Thank You! Without You CNA wouldnt have moved as fast as it did and my future ROM's
Hopefully too! Thank You Again Sir!

If I had the money to throw down on this I would definitely make a donation for this.
Not only would this help cut build times, this would also speed up the time it takes to sync repositories, depending on the connection that the build box has.
Sent from my SPH-D710 using xda premium

I use to donate to Developers, because they spend time developing instead studying, hanging with friends or family etc.
But to be honest, and judging about other threads by you. This sounds more like: "i want a new computer" than "lets help the community".
I hope to be wrong.
Sent from my O=O

This is not a "I want to buy a new computer" type of thread.
This is a thread for donations to help keep his server up and running. Running a cloud based server for building from source requires a good internet connection, and I'm not talking 12, 20, or even 50Mbps... at the minimum it needs a good fiber connection with something like 100Mbps down and at a minimum 50Mbps up.
Just think of this, it is similar to a virtual machine you can run at home.. but you can have multiple sessions running at once. Justlovejoy could be doing something, slick_rick could be doing something, sbrissen, phantomphreak, etc. If one needs to do a sync of the repository, there would be plenty of bandwidth and processing power for all of the developers to do so.
With donations, he could go out and get more memory for making backups. He could set a cron job for something like 6 in the morning after the nightly builds complete to make a backup image of the entire build box. Our developers work is safe if there is ever any failure. That means less time reconfiguring build environment, syncing repositories, building, committing changes to github...
Sent from my SPH-D710 using xda premium

No love for sbrissen? Pretty sure most (all?) of JB development is using part of his code or chris41g's

rovar said:
No love for sbrissen? Pretty sure most (all?) of JB development is using part of his code or chris41g's
Click to expand...
Click to collapse
We would not have jellybean if it was not for sbrissen. End of story. All other developers are secondary.
Sent from my Nexus S 4G using Tapatalk 2

csmasn said:
I use to donate to Developers, because they spend time developing instead studying, hanging with friends or family etc.
But to be honest, and judging about other threads by you. This sounds more like: "i want a new computer" than "lets help the community".
I hope to be wrong.
Sent from my O=O
Click to expand...
Click to collapse
I invite you to read the information contained in the link to the chipin site. I have tried to elaborate as much as possible to help everyone understand the purpose of this project. I am including a quote from the chipin site (which I plan to update with any future upgrades for the project):
basketthis said:
**Note: This box is used specifically for development. This is not my personal computer. I do not use it to play games, type papers, or do my taxes. It is completely maintained, updated, and kept running by me. On my own donated time and money. And is completely "owned" by others. I do not benefit from any of this directly. The community (users and devs) benefit from this project.**
Click to expand...
Click to collapse
I hope that clears some things up for everyone ^
Mattix724 said:
This is not a "I want to buy a new computer" type of thread.
This is a thread for donations to help keep his server up and running. Running a cloud based server for building from source requires a good internet connection, and I'm not talking 12, 20, or even 50Mbps... at the minimum it needs a good fiber connection with something like 100Mbps down and at a minimum 50Mbps up.
Just think of this, it is similar to a virtual machine you can run at home.. but you can have multiple sessions running at once. Justlovejoy could be doing something, slick_rick could be doing something, sbrissen, phantomphreak, etc. If one needs to do a sync of the repository, there would be plenty of bandwidth and processing power for all of the developers to do so.
With donations, he could go out and get more memory for making backups. He could set a cron job for something like 6 in the morning after the nightly builds complete to make a backup image of the entire build box. Our developers work is safe if there is ever any failure. That means less time reconfiguring build environment, syncing repositories, building, committing changes to github...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
We hope to be able to invite more devs in the future. With more power, greater things come.
rovar said:
No love for sbrissen? Pretty sure most (all?) of JB development is using part of his code or chris41g's
Click to expand...
Click to collapse
I appreciate everything that sbrissen and chris41g do!
Exit_Only said:
We would not have jellybean if it was not for sbrissen. End of story. All other developers are secondary.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
You are correct, we owe credit to sbrissen for jellbybean. These "secondary devs" have produced many good roms. They have allowed the community more choices. They actively work on fixes. They try to answer the communities requests. They provide you nightlies (for the flash-o-holics out there). It doesn't sound like you are giving these "secondary devs" as much credit as they are due.
This is a completely independent project. Without support from the community, it will be hard for these great devs to continue to put out the work that they do.

rovar said:
No love for sbrissen? Pretty sure most (all?) of JB development is using part of his code or chris41g's
Click to expand...
Click to collapse
Exit_Only said:
We would not have jellybean if it was not for sbrissen. End of story. All other developers are secondary.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Thats not the point of this thread. Everyone here knows sbrissen brought us JB and were all grateful for that.
Sent from my Nexus 7 using Tapatalk 2

That's my point. Why is he not included into this?. Afaik he is the only one developing AOSP as the thread title indicates.
Tappin' Typin'

rovar said:
That's my point. Why is he not included into this?. Afaik he is the only one developing AOSP as the thread title indicates.
Tappin' Typin'
Click to expand...
Click to collapse
AOSP stands for android open source project. All of the roms listed are not touchwiz. Hence, they are AOSP. Also, the thread doesn't ever "not include" sbrissen or others. It simply states the devs that use the buildbox that I have created. That is all stated in everything I have written. If you want to donate to sbrissen, that is your choice.

As basketthis has already said... this buildbox is not only limited to the devs that are currently using his server.
I would imagine if the resources like CPUs, RAM, and bandwidth allow for it... any dev that builds from source can use this option to build their source built roms. Even kernel devs such as Agat could use this option to build from source.
The sky is the limit to how many devs could take advantage of this, the only thing that is holding this back is contributions from the community. Instead of donating $5 to a dev, you could donate 3 or 4 and donate 1 or 2 to the build box fund... or you could just donate to the dev and the dev should donate for using the build box. Either way, there will be contributions to help keep the build box up and running.
Sent from my SPH-D710 using xda premium

rovar said:
That's my point. Why is he not included into this?. Afaik he is the only one developing AOSP as the thread title indicates.
Tappin' Typin'
Click to expand...
Click to collapse
Umm the point of this thread is for e4gt users to donate (if they want) to this build box so devs can put out their roms quicker and such. Nowhere does it say sbrissen isn't allowed to use it. If he wanted to use it I'm sure he could.
Sent from my SPH-D710 using Tapatalk 2

Hmmmmmm how would one get this build box to try out? I kinda want to "tinker" with source building but my laptop sucks. The specs are horrible

Exit_Only said:
Hmmmmmm how would one get this build box to try out? I kinda want to "tinker" with source building but my laptop sucks. The specs are horrible
Click to expand...
Click to collapse
You must challenge and defeat Chuck Norris at a game of thumb wars.
But, seriously, just trying to help out the badasses around here. If more resources become available, I will be happy to invite more.

I would make a donation to say sbrissen before i made a dination like this. This seems highly risky to me.
Sent from my SPH-D710 using xda app-developers app

Risky??? Your joking right? This is the type of thing the developers you are going to donate to will be using to build ROMs you are donating for...
This community has been scarred by people like SG...
Sent from my SPH-D710 using xda premium

basketthis said:
You must challenge and defeat Chuck Norris at a game of thumb wars.
But, seriously, just trying to help out the badasses around here. If more resources become available, I will be happy to invite more.
Click to expand...
Click to collapse
Its by invite only? No wonder. Fail.

If you can prove you are a good enough dev, you would get an invite to use this service.
How is that a fail? Are you expecting complete noobs to use this and waste resources? If someone wants to get their feet wet with development, run a virtual machine.
This service is for speeding up build times for experienced devs...
Sent from my SPH-D710 using xda premium

Mattix724 said:
If you can prove you are a good enough dev, you would get an invite to use this service.
How is that a fail? Are you expecting complete noobs to use this and waste resources? If someone wants to get their feet wet with development, run a virtual machine.
This service is for speeding up build times for experienced devs...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That's fine but it should be a service for everyone who wants to try to develop. I have a itch to learn but like I said I don't have a computer with enough hardware to build a source ROM with. So how can I "prove myself" to anyone. Either way I won't donate to something I got absolutely zero access too. That's just my 2 cents. I'm sure others feel the same.

[Q] Developers

Our community seems small. How many developers do we have?

I'm getting ready to release my first ROM for this phone.
Sent from my HTC6500LVW using Tapatalk

Reefer Madness said:
Our community seems small. How many developers do we have?
Click to expand...
Click to collapse
More than enough. Not really small. We just don't have 30 copies of the same ROM like most lol.
Sent from my HTC6500LVW using xda app-developers app

cstrife999 said:
More than enough. Not really small. We just don't have 30 copies of the same ROM like most lol.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
This^ Previous phone was the GNex and it was unbelievable how many variants and kangs there were for CM10, AOKP, etc. I ran a lot of them but in the end there wasn't all that much that was different from the original rom. In a lot of cases, the variant ran worse.
Sent from my HTC6500LVW using Tapatalk

Quality is always better than quantity
Like was mentioned above, some phones have 200 Rom threads, but really what's the difference between the Rom? They (aosp variants) are 90% cm based with varying mods pulled from aokp source with pa stuff as well
Really, no disrespect intended those 3 aosp roms are all that matter as everything else is just mashed up and derivative of them
As for sense, you only really need a few roms as well; something stock for those who only want root and a few basic mods, some kind of aroma Rom with user configurable options, and or a rom with a lot if built in mods (well you don't need them lol)
Really imo if you have 5 or 6 roms that meet the above criteria you are set
Unless you have a need to flash a different rom every day that has 1 more bs script or 1 different mod in it
The end user doesn't always see the forest from the trees

I agree with what has been said already. Quality is better than quantity... My old S2 had about 194873 ^6 worth of different roms. Touchwiz this and AOSP that and don't forget the AOKP, with CM and a side of Sense ports. In the end I dropped myself on a really good rom called The Blu Kuban which was headed up by rujelus22 over in the Epic 4g Touch development forum. I ran that rom for about 18 months before I nix'd my device and went over to the red side here at Verizon. I heard he went forth to the S4 and has kept that rom's traditions alive. He was one dev who was helped by the many and made a rom that many made their daily drivers just like I did.
I know we have a good community over here as well as even before beaups dropped rumrunner on us we had a few devs tinkering with their roms.
Now remember! A community is only as good as the people around it. Support your devs any way you can if it's simple donations or a click of the thanks buttons. But most of all, be part of the community. List the bugs you find in the roms, mods, and tweaks. Help the devs make the best they can and we all prosper.

I'd still like to see old Sense on this phone. Like Sense 3 or 4.
I'd also like to see a CM variant built off Sense base. Like the old style ROMs that had all full Sense apk compatibility but no Sense launcher. Not sure if this is doable with Sense 5 though.
And last but not least, hopefully a dev will pick up Ubuntu Touch.
Just a daydreamin' wishlist.. lol

Can't port old sense to new hardware. Plus the old stuff was lower resolution.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button

tylerlawhon said:
Can't port old sense to new hardware. Plus the old stuff was lower resolution.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
you could port sense4+ to this phone (someone did it on the intl one) as the kernel base is the same (3.4.x)
dont know why you would really want to, but its possible

nitsuj17 said:
Quality is always better than quantity
Like was mentioned above, some phones have 200 Rom threads, but really what's the difference between the Rom? They (aosp variants) are 90% cm based with varying mods pulled from aokp source with pa stuff as well
Really, no disrespect intended those 3 aosp roms are all that matter as everything else is just mashed up and derivative of them
As for sense, you only really need a few roms as well; something stock for those who only want root and a few basic mods, some kind of aroma Rom with user configurable options, and or a rom with a lot if built in mods (well you don't need them lol)
Really imo if you have 5 or 6 roms that meet the above criteria you are set
Unless you have a need to flash a different rom every day that has 1 more bs script or 1 different mod in it
The end user doesn't always see the forest from the trees
Click to expand...
Click to collapse
Consumer choice is always a win. I'd kill for a thread with five million views and fifty three thousand replies. Developers in different sections have had months to build their own form of paradise. Android Revolution HD has fullSnapdragon 600 (GPU) rendering. I want to try that.

Reefer Madness said:
Consumer choice is always a win. I'd kill for a thread with five million views and fifty three thousand replies. Developers in different sections have had months to build their own form of paradise. Android Revolution HD has fullSnapdragon 600 (GPU) rendering. I want to try that.
Click to expand...
Click to collapse
thats a bs mod that requires the deleting of a lib (and does nothing)
the end user might enjoy that, real developers know the work done in roms and can sort out the differences between fancy features in a changelog and real code changes and development
views and posts have nothing to do with the work that go into a rom....you can have a thread that explodes because it has a leaked version of sense, a large user base of a rom that drives discussion and hypes upcoming releases, massive bug issues that require help and dicussion, new hboots or firmware needed to run new updates and so on
thread views and # of posts, as well as individual member post count and thanks count is really deceptive and a TERRIBLE barometer of worth in the development community
the best and most important kernel, rom, root exploit, recovery and so on developers that exist in the android world often have a relatively low post and thanks count, whereas guys who release stock deodexed roms made with a rom kitchen in cygwin have tens of thousands of posts and thanks which leads new users and even more experienced ones to inflate their value and skillsets
developers can generally sort out whos who amongst themselves, but its unfortunate that the end user often cant; usually through no fault of their own

nitsuj17 said:
thats a bs mod that requires the deleting of a lib (and does nothing)
the end user might enjoy that, real developers know the work done in roms and can sort out the differences between fancy features in a changelog and real code changes and development
views and posts have nothing to do with the work that go into a rom....you can have a thread that explodes because it has a leaked version of sense, a large user base of a rom that drives discussion and hypes upcoming releases, massive bug issues that require help and dicussion, new hboots or firmware needed to run new updates and so on
thread views and # of posts, as well as individual member post count and thanks count is really deceptive and a TERRIBLE barometer of worth in the development community
the best and most important kernel, rom, root exploit, recovery and so on developers that exist in the android world often have a relatively low post and thanks count, whereas guys who release stock deodexed roms made with a rom kitchen in cygwin have tens of thousands of posts and thanks which leads new users and even more experienced ones to inflate their value and skillsets
developers can generally sort out whos who amongst themselves, but its unfortunate that the end user often cant; usually through no fault of their own
Click to expand...
Click to collapse
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.

Reefer Madness said:
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Click to expand...
Click to collapse
Not to start a war, but I'm going to give you benefit of doubt you probably don't know him. What he said is true.. And you probably just proved his point too.
His work on other devices is proof of that. Give it time, we will see more options now that the crowd is turning more s-off.
Sent from my Nexus 7 using Tapatalk 4

Reefer Madness said:
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Click to expand...
Click to collapse
He did .. You must have not read it...
Sent from my HTC6500LVW using xda app-developers app

cstrife999 said:
He did .. You must have not read it...
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Here I was thinking it was truly reefer madness...lol
Sent from my Nexus 7 using Tapatalk 4

dottat said:
Not to start a war, but I'm going to give you benefit of doubt you probably don't know him. What he said is true.. And you probably just proved his point too.
His work on other devices is proof of that. Give it time, we will see more options now that the crowd is turning more s-off.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I know what he said is true and I don't care. CPU vs GPU. That interests me.

[Q] Custom Kernel vs Stock Kernel

Hey guys, I have a couple questions for those of you who have good kernel knowledge (especially for HTC One M8).
I'd appreciate if you made your replies as noob proof as possible, since I'm not too familiar with how Kernels work, thank you!
1. What are the best known / most common kernels are available for the HTC One M8? (give names)
2. For each kernel mentioned above, what are the pros and cons, and what do they do that's unique? And how do they compare to stock kernel? (remember to make this noob proof)
Thank you guys for your help.
Depending on how much information and the quality of such information, I will compile all replies given here into its own thread as a kernel guide for the M8, and list the usernames of all who helped in the credits.
Sent from my Nexus 9 through XDA app

1 : check the Android development and original Android development section and count the threads starting with [KERNEL]
2 : The pros and cons.....just read each independent thread, the opening posts contain all needed info with the mods they carry.
It's all written out already. Just take the time to read. And there are already "kernel talk" threads in the general section. Just explore more in the different sections here.

Mr Hofs said:
1 : check the Android development and original Android development section and count the threads starting with [KERNEL]
2 : The pros and cons.....just read each independent thread, the opening posts contain all needed info with the mods they carry.
It's all written out already. Just take the time to read. And there are already "kernel talk" threads in the general section. Just explore more in the different sections here.
Click to expand...
Click to collapse
Hehe thanks, you actually pointed out a flaw in one of my questions, which I'll have to correct the OP to better reflect my needs.
Question 1 should probably be, what are the most common or best known kernels for the M8.
And on another note, I'd just like to repeat and emphasise (something which I'll edit the OP as well to make clearer), this honestly needs to be N00b proof, I'm not joking haha I'm good at understanding ROMs and OSs (I'm an IT student btw), but I'm a complete newbie at Kernels.
Your second answer is something I already have done, and what they described there, was pure jargon to me. A list of what the kernel does, but there is no explanations for what each element on the list is.
And about reading the kernel talk threads, I did some research on Kernels and how to choose the best one for me, but none of them explained fully, more like just looked at the major points (over/underclock, touch to wake support etc...) which honestly i can just as easily get from a ROM.
But there's so much more I do not understand yet, which I would appreciate if you, or someone else explained in a simple not too technical way.
I'm pretty sure I'm not the only one with such a question.
Sent from my Nexus 9 through XDA app

Kyuubi10 said:
And about reading the kernel talk threads, I did some research on Kernels and how to choose the best one for me, but none of them explained fully, more like just looked at the major points (over/underclock, touch to wake support etc...) which honestly i can just as easily get from a ROM.
Click to expand...
Click to collapse
If you got those feature from a ROM, its only because the ROM included a custom kernel. You can't have those things without changing the kernel.
To me, custom kernels are a very personal thing. What you get (or don't get) out of them depends a lot on how you use your phone. Therefore, I think that is the reason why most kernel threads won't have much description on the exact benefits. I know lots of folks swear by custom kernels and the features they offer. But personally, I've never been much a kernel flasher or tweaker. Reason being, the times I have messed with kernels, they don't seem to give me much benefit in terms of performance (battery and/or responsiveness) and sometimes even hurt those aspects. But again, YMMV and I think it depends a lot on your setup and how you as an individual use your phone.
On that same note, I think it makes a thread like this difficult to construct; or any opinion given possibly not relevant to all. Like ROMs, its not that hard to look at the threads and discern which are most popular (if that is your goal, popular doesn't always mean best). Then pick a few that look good (seem to meet your needs or wants), try them out, and see what works best for you.
I know that sounds like a cop out; but its what I honestly believe.

@redpoint73
I see what you mean, but I am already limiting things only to the M8. So there shouldn't be that many Kernels go talk about.
Having a look through the forums it's no so well organised as to give a clear view of how each kernel compare to each other.
(note: Not to decide which one is best, but to clearly display differences, which could make it easier to see which one is better for the person)
If I was to make a guide on M8 Kernels I'd try to find what is common among them, what you can 100% expect from all Kernels.
Then I'd start naming the Kernels and displaying the different features (and how they are meant to benefit or how they work, because so far I have only found names/initials, which make it hard for a noob to understand what those features are from just a name).
So yeah, that is what I had in mind.
But its hard from purely reading the individual kernel threads, mostly coz I'm a noob at kernels (which is why I created this thread, to understand better kernels)
I had no idea about i/o schedulers... I just did some research, but the worst part is that there are some kernels which just make the names a joke, making it hard to find out what that scheduler really does. And the OP doesn't explain either.
Same is true for CPU governors. But now I'm just ranting.
It seems as there are not many people who know kernels as well as they think they do.
Sent from my Nexus 9 through XDA app

Why not make it a bit easier on yourself and participate in this thread ?
http://forum.xda-developers.com/showthread.php?t=3103465
Lots of kernel talk,regardless the rom.

I went in as you advised, but it still doesn't cover what I wanted to know, I had to search each specific feature on its own, as I tweaked it.
There are a lot of guides to individual features, no comprehensive guide (with links) for kernels.
I hv decided, I'm gonna play around a bit on my new kernel (ended up going for ElementalX), and then I'll do a kernel guide. Nothing like using a kernel to understand it better right?
Sent from my Nexus 9 through XDA app

Kyuubi10 said:
I went in as you advised, but it still doesn't cover what I wanted to know, I had to search each specific feature on its own, as I tweaked it.
There are a lot of guides to individual features, no comprehensive guide (with links) for kernels.
I hv decided, I'm gonna play around a bit on my new kernel (ended up going for ElementalX), and then I'll do a kernel guide. Nothing like using a kernel to understand it better right?
Sent from my Nexus 9 through XDA app
Click to expand...
Click to collapse
Definitely true there mate, i am on stock as it behaves very good for me. I have no need for a custom one at this moment

Stock is good... I like stock, but I'm trying to learn a bit more, expand my horizons a bit.
Got kinda boring tweaking only the ROM
Sent from my Nexus 9 through XDA app

Hey guys, as promised, after playing around with Kernels I decided to make a Comprehensive guide on Kernels.
If you wanna have a nosey and give some feedback here's the link:
http://forum.xda-developers.com/showthread.php?p=61026926
Sent from my Nexus 9 using XDA Free mobile app