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

[Q] How to cook a ROM?

I've been looking into creating my own Galaxy Nexus ROM but I can't for the life of me find out where to start. This is mainly going to be just for entertainment purposes of course.
As far as I know (which is not very much at all) I must compile the AOSP source code. The problem is I don't even know what compiling is. I don't mind if I have to learn as I have a very high interest in this and I'm possitive that I could learn fast.
Could someone please point me in the right direction to making a ROM?
I've also heard of people doing RAM optimizations,fullu deo-dexed, init.d scripts and speed optimizations. How would one go about doing that?
Any help would be GREATLY appreciated.

You have a lot of reading ahead of you.
I know there are guides for some of the things you mention at freeyourandroid.com but honestly man start reading
Android - making grown men pee sitting down since 2.0

Read the stickied post in the general forum on how to compile from source.
Also, you should really know and understand how the android system works before making a rom.
Sent from my Galaxy Nexus using xda premium

Hypercore said:
As far as I know (which is not very much at all) I must compile the AOSP source code. The problem is I don't even know what compiling is.
Click to expand...
Click to collapse
Let's start here. Do you know much about operating systems? You say you don't know what compiling is... so I take it you've never done any programming, even, say, a quick intro class in university? That's not a huge deal--I'm no programmer but I work with OSes all the time (especially Linux) and have learned a lot of scripting here and there.
I'd say start with learning about how Android works internally. Might even want to read up some on Linux if you don't know much about it, since that's the foundation.
There are plenty of guides on various forums (at least, there used to be) here, but a good place to start is to take an update .zip file and pick it apart. Start with a basic AOSP ROM, maybe, and start digging through it on your computer to see what's there and what does what.

Kernel repacks

Is FD02 still the latest repack option that we have, or have I missed one?
I try to keep a check on sfhub's handy autoroot tool to see if there are any updates but wanted to make sure there hasn't been a development since his last update.

We may have lost Steady to the Gnex and there being no reason to do one other than to be up to date with a decent build such as FD26.... we havent seemed to convince anyone to do one quite yet?

RainMotorsports said:
We may have lost Steady to the Gnex and there being no reason to do one other than to be up to date with a decent build such as FD26.... we havent seemed to convince anyone to do one quite yet?
Click to expand...
Click to collapse
Thanks for the reply. I know I've seen a few names bandied about in reference to picking up the repack reins but hadn't found anything confirmed.
I should add I'm one of those anal retentive types who likes having everything in sync (baseband and kernel) regardless if it matters or not. I Odin stock kernels onto custom ROMs then lose access to cwm, so when I want to flash something new I have to autoroot back to a cwm repacked kernel. It's a vicious cycle I put myself through. lol

If there was someone to mentor me I am willing to pick up the job since I am staying on this phone for 2 years. Stalking sfhub i picked up 2 very good threads on kernel development for this phone. But without a little help its something ill get to eventually instead of right this moment.

RainMotorsports said:
If there was someone to mentor me I am willing to pick up the job since I am staying on this phone for 2 years. Stalking sfhub i picked up 2 very good threads on kernel development for this phone. But without a little help its something ill get to eventually instead of right this moment.
Click to expand...
Click to collapse
I wonder if you could PM SteadyHawkin, Shabbypenguin, or chris41g. I'm not 100% certain about the latter but I think all those people have worked in the kernel repack field.
I wish I had the time and technical knowledge to take up the project. You would have my full support and thanks

T-Mobile GS3 CM9: How do we get started?

I badly want to help get CM9 working, or at least learn from trying, on the T-Mobile variant of the GS3. I'm a pretty decent hacker, but I know I don't have enough / any experience with the Android OS / Kernel development to work on the GSM/LTE portions of the ROM. However, I feel that if someone could help me and anyone else interested to get the toolchain setup and source properly downloaded, we could help with the easier portions of the ROM and learn a little about the complex portions of the ROM just by watching what the more experienced devs are doing.
Right now, it seems like ...maybe.. a few people are working on their own rather than a collaborative effort (except the Sprint variant that has Team Epic working on a ROM). I don't want to slow progress by taking up a bunch of valuable dev time, but if one person could just help get some of the less experienced people off the ground, we could probably accelerate this effort...
In the meantime, would you guys mind posting some links to the best resources you have found for getting started building CM or even building Android in general? It doesn't really matter if it's a guide for a different device. I have searched but there is so much information missing in sources I have found.
Thank You,
KevlarTheGreat

Count one more.
I would love to get involved. I have a good amount of Linux and C experience (7+ years), but need a good place to start with Android ROM development (specifically for the GS3).
Sent from my Glitchy CM9 Fascinate

mybook4 said:
Count one more.
I would love to get involved. I have a good amount of Linux and C experience (7+ years), but need a good place to start with Android ROM development (specifically for the GS3).
Sent from my Glitchy CM9 Fascinate
Click to expand...
Click to collapse
M'ladies and gents, couldeth you count a third member of this exquisite inquiry.

Team Epic is sorting it out, just be patient:good:
http://www.epiccm.org/2012/06/sprint-sgs3-cm9-development-plan.html

That is if it truly works on all carriers phones without trouble.

kscasper13 said:
Team Epic is sorting it out, just be patient:good:
http://www.epiccm.org/2012/06/sprint-sgs3-cm9-development-plan.html
Click to expand...
Click to collapse
From what I understand, they are sorting it out for Sprint but T-Mobile is much different because it's GSM. Here is their reply to me when I asked if there would be CWM install scripts that would support both T-Mobile and Sprint from the same ROM:
From this post: http://forum.xda-developers.com/showpost.php?p=28021070&postcount=23
CMTeamEpic said:
No, there will not be ROM's that work on all variants. CDMA and GSM are quite different.
The tools like CWM will work on all variants (if made properly) because they don't use the radios.
Click to expand...
Click to collapse
I'm a bit surprised at this answer because I'm coming from the HD2 where tytung has two different versions of the kernel in his amazing CM9 ROM. It chooses which one to install automatically based on which radio support you have PPP vs RMNET.

CyanogenMod 7 Project

Hi guys,
So for the past week I think I have at least wiped/flashed/Odin'd different ROMs for my new Captivate Glide at least a hundred times. I've finally settled on thegreatergood's LiteROM 0.9.0 and it's working great for me. Not only the one ROM though as I've had to find many workarounds for different things. Flashables/kernels/apks you name it. Although I have no regrets and I'm really proud of how It's like a beast in my pocket, I am quite bothered by one thing which is that the whole thing feels like a big piece of patchwork..
Coming from a HTC Desire Z running CM7 serving me loyally for many years, I miss that officiality (<-- oops, red snakes.. not sure that's a word. Whatever. Shakespeare made his own words too right? ) and the stability that CM7 offered.
I'm a humble man, and possibly carry the apologetic traits of a typical Canadian. Instead of whining and/or nagging some senior developer to hurry up on their ICS or JB development I've decided to build my own CM instead.
However some thought, I think the reason why the JB based experimental CM 10.1s for the Captivate Glide have been a difficult task is because it's probably quite a challenge to build something from something that's not currently very well understood, namely the JB. So I thought, why not just build I nice and stable ROM based off of GB and if it does well it could probably officiated as a CM7 port for the Captivate Glide.
I have a feeling that this is a very plausible task. But I have no way to do it alone.. I have zilch experience in development in anything, had to drop out of my C++ course and have been doing nothing but lurking and leeching since I started modding when I was eleven. All I have is a vision. If someone could point me in the right direction or even form a development team with me, I would be very grateful.
And if this goes well, I will have gained some long overdue experience
So.. Anyone?
P.S. I guess this goes in this forum too. But my phone gets real angry when I flash certain things onto it. The biggest issue currently is that it will freeze and crash (more specifically the screen will freeze and fade into white lines..) whenever I try to use ClockWorkMod Recovery.. I dunno if the crappy 1500 mAh China battery I got ripped off with is an issue but I'm waiting on an OEM one in the mail..

Post in general not development bub...
And were on cm 10. Why fall back?
Sent from my SGH-I927 using xda app-developers app

I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app

hey bud im with you ... though I think CM9 would be better as ICS has been released, stable, and has a few more tweaks and features that CM7 didn't ... things like in JB where we have a transparent notification pull down, control over the dpi of certain apps etc.
First thing you should do is readup on the compile cm10 from source thread, get your feet wet there it'll get you all setup with a development system .. Linux is a must so I hope that you're savvy in the *nix shell or things will be antagonistic right off the start ...
I installed the CM9 recently and radio etc didn't work .. Guaranteed there is tonnes of information across all devices on xda-developers and even in general development threads.
Scroll through these forums, find the github links and learn how to setup your own, download the sources for the kernels from the other devs (theres a couple CM10.1s out there).
CM7 .. while I appreciate where you're coming from as i LOVED having CM7 on my Galaxy ACE - everything just worked... battery was great, it looked cool, and it was just off the stock enough to be unique and rub in iPhone users' faces
If I had the time I'd take it on with you .. chart your work and links that have helped you as you go along.

maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.

lorddavid said:
maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.
Click to expand...
Click to collapse
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight to CM7 : http://forum.xda-developers.com/showthread.php?t=1273718
Another one for CM9 : http://forum.xda-developers.com/showthread.php?p=20844007
.... maybe I should just build a linux VM and give it a go in my spare time .... we're so starved for developers for our glides even amateur contributions can't hurt .... in the 2nd link the guy said it took him 11 months to learn how to mod for ICS from no experience so ..... depends on how much you want to commit to it ..

yohan4ws said:
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight : http://forum.xda-developers.com/showthread.php?t=1273718
Click to expand...
Click to collapse
yes, i know that, and i was thinking that a cm9 (because there is a ics fully working in the glide) can be a good option, but not sure

This doesn't belong here, please, some mod, move this to General. Thanks

chrisyjwai said:
I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Flagged to be moved to general. If this turns into a dev thread, then you can flag to move it to the dev section, but you only post in the dev sections if you actually have a product or are actively working on something.
Your intentions seem great, but never wait for someone else to help you, otherwise it will never get done. No one is going to carry you through learning this.
There's a ton of guides out there on how to build, port, cherry pick CM commits, etc. etc. Go find them and start learning. Ask SPECIFIC questions if you have any.
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc. There's a lot of steps in between. So go and get started.

gtmaster303 said:
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc.
Click to expand...
Click to collapse
That doesn't make any sense.... lots of people show up to college and say that, and then enroll in the courses to do that ..