Related
Would it not be easier to get together and create a single ROM? If JF releases a version now, there will be what? 3? 4?
So now all themers need to create 3 or 4 ports. Also, I have noticed that a lot of these different ROMs come pre-themed. Isn't this a bit redundant?
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style. Once we get past the "beta" mode of these roms and they are more official, the cookers will be able to theme and do that stuff on their own. You would then pick roms based on features/themes/addons that you like instead of just going with the newest one that is out like we are now.
Agreed! (This text is just to pass 10 char limit)
Darkrift said:
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style.
Click to expand...
Click to collapse
Agreed. That was half the reason I loved recooking my old Apache every week.
but arnt all these builds just different attempts at getting a working 1.5 build?
Freedomcaller said:
but arnt all these builds just different attempts at getting a working 1.5 build?
Click to expand...
Click to collapse
Not any longer. The official 1.5 has been released and therefore should just simply be giving people root and adding other options.
well no, the official hasnt been released till tmo sends it as an OTA. they will add their own "style" (junk apps, and some good stuff if we are lucky) to it and then we will have official builds. Once that happens, there will just need to be root/themes/modifications. each cook will add his own ideas into his roms and will have his own followers. There will continue to be branches off of each style as we have seen with JF > lucidrem, haykuro > TheDude etc.
I remember when JF made his first rom and I started hoping this would happen. It did not seem like it would based on what was required, but we are fast approaching a rom kitchen like environment in Android where any custom build you can dream will be available. Lets see the iphone do that!
Good point DarkRift....
I went ahead and tested out Haykuro's version and while it's pretty stable, hate the fact that half of my apps no longer work. For this reason, I'm probably going back to JF1.43 until the devs have time to get the software working on 1.5.
momentarylapseofreason said:
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Click to expand...
Click to collapse
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
harry_m said:
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
Click to expand...
Click to collapse
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
The growth of new Dev's are pretty exciting for me. I love to see that we have options, everyday I have something to look forward to with all these new builds, and I hope more Dev's jump on in with new and fresh ideas. Hey you never know some one can jump in XDA with a genius mind and make our UI look like the Ophone. Now wouldn't that excite you knowing you can jump to that rom instead of being stuck on 1?
Darkrift said:
well no, the official hasnt been released till tmo sends it as an OTA.
Click to expand...
Click to collapse
Incorrect. HTC has released 1.5 as an update for ADP (Dev) phones. So it *is* officially out there for Dev phones, just not an "official" TMo release for TMo branded G1s, which personally I don't particularly care about anyway (
) as I'd always take a manufacturer rom over a carrier one. I'd expect a TMo 1.5 to be practically the same as the HTC one, with additional bloatware!
Regards,
Dave
I love having all of these roms to choose from. I'm just having trouble deciding whether to give up the pdf reader, HTC VK and camera, for the ADP1.5H with multitouch. I'm thinking that sooner or later, I will be able to have all of those things in one rom though.
I am still on Haykuro's HTC build, and my phone is waaaay more exciting than the fruit phone!
The only thing that I can see wrong with this phone now, is that HTC didn't include more internal memory from the beginning. Even with the apps to sd fixes, there are still problems which crop up with those.
Azlum said:
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
Click to expand...
Click to collapse
Quality over Quantity. If they all hooked up together and made on EPIC 1.5 ROM that was plain jane but 110% stable, i would love them for it. But in the end, im waiting for JF's build. Im sure thats what he is doing.
As has been stated by people such as "Big in Japan" though....
Big In Japan said:
Android 1.5 presents more than a few problems for developers. According to Alexander Muse, applications currently running on Android won’t necessarily be compatible with Cupcake 1.5; that means a mad rush to download the new firmware and rebuild their software. Compounding the problem is the fact that the Android Market won’t allow more than one version of an app, which means developers aren’t able to simply create a new, 1.5-friendly update and leave the existing version in place for those without Cupcake. Instead, Big in Japan face creating a new build that’s also backward compatible with earlier versions of Android, something they conservatively estimate should normally take around two to three weeks of development.
Click to expand...
Click to collapse
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Just something to keep in mind.
momentarylapseofreason said:
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Click to expand...
Click to collapse
If the developers were using private APIs during the development of their application, then the fact they are broken on Cupcake is likely to be their own fault for using an API which is not necessarily static and therefore liable to change. If they only used public APIs, then it is Googles fault for changing those APIs, or the behaviour of those APIs.
This is one of the "problems" with Android being open source - you can't realistically hide the private APIs from developers since they can see them being used in the source code, and thus may be tempted to use them when in reality they should be restricting themselves to just the public APIs to ensure forwards and backwards compatibility.
Regards,
Dave
I have to agree with everyone who wants to keep things in one.
This does NOT mean that different people can't add particular modifications to what is available, it just means distributing these things as smaller components.
Start with the stock ADP1.5 image. If you want multitouch, apply the update.zip that provides multitouch (and nothing else). If you want tethering, apply the update.zip that provides the kernel with netfilter. If you want a skin (or whatever you want to call it), apply the update.zip that provides it. There is no point in bundling everything together in full system images since all this does is it makes the downloads huge and creates incompatibilities.
For example, I have always used the stock ADP firmware. I have looked at JF's full go and found that while nice, it adds things that I don't want and leaves out things that I do want, which means that it would end up being equal work to adjust those builds into something that I want as it would end up being to modify the stock image. The deciding factor is that I know exactly how my changes work against the stock image and I don't necessarily know what changes JF has made to his.
Actually since most builds are only file-based (i.e. changing some files in /system), could we make a program that (with root, of course) download the difference and apply them? Like an android market for firmware builds or say an apt for android.
Then user get the freedom to choose what they want and can go back to previous versions easily when things go wrong.
To be safe, it could just use symbolic links to apply updates, so restoring will be easier and gives the internal flash a longer life.
I haven't flashed to any Tom's yet, but this seems to be the most popular. Why is that? I looked at the change log and I don't understand what I would be gaining I guess.
Sent from my Transformer TF101 using Tapatalk
same too me, I tried it over 3.1, what I experienced:
- browser little bit slower
- more SOD
- nothing real extra feature
I have to use a custom rom for a couple of reasons:
1) My stock rom is the Chinese verison, which means no google apps or google sync. Without google, it's just not android.
2) I need the Chinese input methods. I would normally switch to the USA stock rom, but it doesn't have Chinese input. Prime does/did, Chinese handwriting input is MIA, but I'll sure it will be taken care of.
I choose to use a custom rom for these reasons:
3) I don't like excess crap on my computer. I can modify a custom rom before I install it, mostly just removing apps that I will never use.
4) Root! I love freedom on my computer. Root lets me do things. All kinds of neat things: block ads, increase speed on sd card, delete/modify system apps and directories, and lots more. Look into it, it is fun.
5) Overclock. Prime doesn't have it, but you can add a kernal that does. I currently don't overclock, but as the Tegra 2 ages, i will overclock it. I'm specifically waiting for a rom with a high GPU overclock. There is one out there that currently does have a minor GPU overclock.
6) Clockwork Recovery. Backup, restore, switch roms, clear cache and more.
Why I choose Prime:
7) Dock battery meter in the taskbar.
8) Reboot/recovery options for power button.
After looking through the current selection of roms available, I choose Prime. But I keep my eye on revolver and Clemsyn.
bobloadmire said:
I haven't flashed to any Tom's yet, but this seems to be the most popular. Why is that? I looked at the change log and I don't understand what I would be gaining I guess.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
How do you not? OP clearly states that there are optimizations made to increase load times etc etc.
No, op states "better user experience" which is very vague. Also I'm not having any slow load times, everything is pretty zippy.
Sent from my Transformer TF101 using Tapatalk
bobloadmire said:
I haven't flashed to any Tom's yet, but this seems to be the most popular. Why is that? I looked at the change log and I don't understand what I would be gaining I guess.
Click to expand...
Click to collapse
Last time I flashed a Tom he punched me in the face...
One reason I haven't seen mentioned would also be themes, but it is still early in the game, there are few options. Custom Roms are generally just optimized better, though the Transformer doesn't have nearly the bloat some Android devices have making them almost essential...
Honestly once you learn, it is such an easy process that flashing different roms/kernels and trying them is the only real way to know what is best for you and your usage.
bobloadmire said:
No, op states "better user experience" which is very vague. Also I'm not having any slow load times, everything is pretty zippy.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Then why are you worrying about ROMs? It's obvious you want some of that Baconcomb so just get it already.
Honestly, I don't know why people ever need to "beg" you to try something. If you're happy with what you got already, then be happy.
"If it isn't broken, don't fix it"
If you're curious, then just do it... because all in honesty. One person's opinion is only a opinion. The only way you're going to know if it's worth it is from YOUR personal experience. I can personally say that, PRIME 1.6 and root is good and its worth it.
If you don't want to take my word for it, then don't. I'm not going to beg you to do it.
zephiK said:
Then why are you worrying about ROMs? It's obvious you want some of that Baconcomb so just get it already.
Honestly, I don't know why people ever need to "beg" you to try something. If you're happy with what you got already, then be happy.
"If it isn't broken, don't fix it"
If you're curious, then just do it... because all in honesty. One person's opinion is only a opinion. The only way you're going to know if it's worth it is from YOUR personal experience. I can personally say that, PRIME 1.6 and root is good and its worth it.
If you don't want to take my word for it, then don't. I'm not going to beg you to do it.
Click to expand...
Click to collapse
The reason im asking is so i dont miss out on anything and obviously im looking for empiracle data to help me understand any performance benefits.
Sent from my MOTWX435KT using Tapatalk
zephiK said:
Then why are you worrying about ROMs? It's obvious you want some of that Baconcomb so just get it already.
Honestly, I don't know why people ever need to "beg" you to try something. If you're happy with what you got already, then be happy.
"If it isn't broken, don't fix it"
If you're curious, then just do it... because all in honesty. One person's opinion is only a opinion. The only way you're going to know if it's worth it is from YOUR personal experience. I can personally say that, PRIME 1.6 and root is good and its worth it.
If you don't want to take my word for it, then don't. I'm not going to beg you to do it.
Click to expand...
Click to collapse
Wow...
He asked what was the difference between stock and Prime, and you went off in another direction. He wasn't asking to be "begged" into using Prime nor asking for others to convince him into using Prime at all.
Anyways, I know Prime has a few optimizations, but I don't know if it brings any substantial changes. There's a link to download the power/recovery mod, so I suppose it could be applied to any ROM including rooted stock.
One reason I would like to root my tf101 is to be able to use a USB dongle. But I am waiting for 3.2 to come out before since I just got my tf101.
The stock version is pretty good actually. No major complaints so far.
I hav ebeen using Prime for a while but ASUS stock version is definitely quite good. Even more so for lack of garbageware that so plagues the mobile phones...
Yea I guess I'm in the same camp. I haven't seen a compelling reason to move to a different ROM versus rooted stock. There are too many posts that seem to lead users to believe that a different ROM is the same as root. Remember you can root the stock ROM. The OP is asking what user experience enhancements make Prime (or any other ROM) compelling.
If you read changelog second post it will tell you exactly what's new in the ROM. Many changes are only useful for experienced linux users, but many others are useful for everyone. The nice thing about roms is that most of the things and tweaks are already done for you. If you don't need/care about those changes then there is no point for you to reflash.
Which BXX mod did you get ?
I'm curious because I'm thinking of picking up one of these today ( the guy at Orifice Depot tried to get me to buy an Iconia, but that thing doesn't have anywhere near the support the TF is getting...)....?
Manufacturer's (ASUS included) have to be very careful about their ROM releases so they are thoroughly tested and ready to release to the general public. Consequently they are slower to release updates (i.e. NVidia updates, etc.). Custom ROMs generally consolidate the best and latest releases from various manufacturer's into the most cuttest edge versions you can possibly be running. As you'll notice this can also mean more lock-ups and weird issues since you are getting just-available changes. So if you prefer max stability, stick with the manufacturer's updates. For many of us part of the fun of owning an Android tablet is the rapid pace that custom ROMs are put out and the interesting/quirky things they bring us.
marcelol said:
I'm curious because I'm thinking of picking up one of these today ( the guy at Orifice Depot tried to get me to buy an Iconia, but that thing doesn't have anywhere near the support the TF is getting...)....?
Click to expand...
Click to collapse
I got a B60 TF and a B60 dock from my local OD this past weekend (Denver, CO).
Prime Vs Stock
Reason why I flashed the Prime Rom. With Prime and a netflix patch I'm able to stream netflix movie. Also now Adhoc connections work. I can Wifi tehther my TF101 with my Driod using the adhoc connection. I can now easily reboot into recovery prior to this going into recovery was a bit tricky. This was not possible even with HC 3.2. Also I don't have to worry about losing root becuase of an OTA update.
I am actually a flashaholic when it comes to flashing roms on my phone. But so far, I haven't come across any compelling reasons to flash custom roms on my transformer. The need to flash roms on phones offer benefits that are non existant on a tablet. For instance, one major reason to flash custom roms on phones is to enable free wifi tethering, which obviously does not apply here. Another reason, as stated above is to remove bloatware. The transformer doesn't really have that. And yet another reason is to be able to update to the latest Android version before the official release. Correct me if i'm wrong but when I looked, the 3.2 update came out officially before any transformer custom roms had it. There are a couple more minor customizations options that I'm not seeing yet being offered by the transformer roms. I am fully aware of the speed enhancements and optimizations that custom roms offer, but considering the custom roms for the transformer are still relatively new (no disrespect or discredit to the devs for their hard work), and considering that even still now, the rooting and flashing methods keep getting outdated and changed, it's too early in this ballgame for me to flash.
I've been lurking the forums here now for a month and finally pulled the trigger, my TF get's here monday.
I have yet to see any reason to flash a custom rom or even root at this point. I'll be rooting it just to say it's rooted and just for a couple of root only programs I have. The custom roms don't really bring anything to the table that this tablet doesn't have. it has the newest version of android with all the bells and whistles. I'm not going to be overclocking. I understand netflix is big for some people, but, from what I have read flashing the fix breaks some video playback. I'm ok to wait for the official netflix patch. A 32gb MicroSD and the 16gb on board space is plenty to store movies on for travel etc. I also have a server I run at home that will stream my entire movie,. TV, and music collections directly to me.
Having the best of the best and the most up to date version of android does have it's perks
as the title, on ics rom. what is the different between kernel 2.6 and 3.0?
who can tell me?
its the kernel of linux in general lol
they stopped at 2.6.something now they are on 3.0
see http://www.phoronix.com/scan.php?page=news_item&px=OTUwMg
Yay! Let the bikeshed painting discussions about version numbering begin (or at least re-start).
I decided to just bite the bullet, and call the next version 3.0. It will get released close enough to the 20-year mark, which is excuse enough for me, although honestly, the real reason is just that I can no longer comfortably count as high as 40.
The whole renumbering was discussed at last years Kernel Summit, and there was a plan to take it up this year too. But let's face it - what's the point of being in charge if you can't pick the bike shed color without holding a referendum on it? So I'm just going all alpha-male, and just renumbering it. You'll like it.
Now, my alpha-maleness sadly does not actually extend to all the scripts and Makefile rules, so the kernel is fighting back, and is calling itself 3.0.0-rc1. We'll have the usual 6-7 weeks to wrestle it into submission, and get scripts etc cleaned up, and the final release should be just "3.0". The -stable team can use the third number for their versioning.
So what are the big changes?
NOTHING. Absolutely nothing. Sure, we have the usual two thirds driver changes, and a lot of random fixes, but the point is that 3.0 is *just* about renumbering, we are very much *not* doing a KDE-4 or a Gnome-3 here. No breakage, no special scary new features, nothing at all like that. We've been doing time-based releases for many years now, this is in no way about features. If you want an excuse for the renumbering, you really should look at the time-based one ("20 years") instead.
So no ABI changes, no API changes, no magical new features - just steady plodding progress. In addition to the driver changes (and the bulk really is driver updates), we've had some nice VFS cleanups, various VM fixes, some nice initial ARM consolidation (yay!) and in general this is supposed to be a fairly normal release cycle. The merge window was a few days shorter than usual, but if that ends up meaning a smaller release and a nice stable 3.0 release, that is all
good. There's absolutely no reason to aim for the traditional ".0" problems that so many projects have.
In fact, I think that in addition to the shorter merge window, I'm also considering make this one of my "Linus is being a difficult ^&^hole" releases, where I really want to be pretty strict about what I pull during the stabilization window. Part of that is that I'm going to be travelling next week with a slow atom laptop, so you had better convince me I *really* want to pull from you, because that thing really is not the most impressive piece of hardware ever built. It does the "git" workflow quite well, but let's just say that compiling the kernel is not quite the user experience I've gotten used to.
So be nice to me, and send me only really important fixes. And let's make sure we really make the next release not just an all new shiny number, but a good kernel too.
Ok?
Go forth and test,
Linus
Click to expand...
Click to collapse
just for commemoration
same question.why brainmaster's ics version's kernal is also 2.6x as Gingersnap,but official ics is 3.0.
how about future's OTA for NS?
Singnal said:
same question.why brainmaster's ics version's kernal is also 2.6x as Gingersnap,but official ics is 3.0.
how about future's OTA for NS?
Click to expand...
Click to collapse
Because its probably a moded rom to look like its ics.
if i'm not mistaken, ics is based on the latest linux kernal - which is 3.0 (or 3.2 by now not sure )
the biggest differents are?
Have you read anything that I just posted yet? >_<
Read what i posted earlier.. and if you want follow the link.
Read under:
So what are the big changes? in my previous post!
Brainmaster's ROM isn't pretend ICS, it's the real thing. The new kernel 3.whatever won't be available until the sources are released, and there's not a huge gulf between those kernel versions anyway, it's more cosmetic
Sent from my SNES
So I finally gathered up the balls to flash my Droid with GummyCharged. It's pretty snappy. I like it except for minor glitches here and there but it was manageable. I searched online for more info about Gummy and I found that support for it has dropped.
My question is which ROM should I move my attention to next? I looked at Tweaked and Infinity, but I couldn't help but notice Deodexed/Eclipse.
It seems there's an equal amount of information on them but I couldn't really find any info about which one has the most support or which one is the obvious forerunner of the three.
So community, what is your opinion? What do you like best and why?
the only few worth ur time is tweaked, eclipse, or infinity. the others r all outdated and no longer updated. or the fp1 debloated but that isnt a custom rom really.
Sent from my SCH-I510 using XDA
There isn't really a forerunner. It's more about personal preference. Tweaked is the most customizable. Eclipse has a lot more apps replaced with their AOSP (Google) equivalents. Infinity is still a valid choice as well. I love the Infinity theme, but I personally have always had slowdowns and hotboots on it. It falls somewhere in between Tweaked and Eclipse...a good amount of customization as well as some AOSP app replacements.
I would run either Tweaked or Eclipse. I ran Eclipse from the time it was on version 1.1 up until Tweaked 2.0 came out, then I switched to Tweaked.
Specify!
I think it would be appropriate for me to specify what exactly I'm looking for. Thanks for your response shrike. What I'm looking for is the least buggy, most responsive ROM that offers reasonable battery. Customizable features is nice but that's exactly a must.
So I see the poll is shooting towards Tweaked, so I guess I'll ask, is Tweaked the most appropriate ROM that will fulfill most of what I'm looking for, if not all?
And by AOSP, what do you mean Eclipse has AOSP equivalents? (Ignorant question lol). I read about it but I don't want to interpret what I've read incorrectly.
Thanks again!
Nitro took the AOSP code from Google and compiled some of the apps for our this phone, and replaced a lot of the TouchWiz apps with the AOSP equivalents. If you want something closer to AOSP, then Eclipse is the closest we have (other than jt's unfinished CM9 port), but it is still TouchWiz at it's core.
From a stability standpoint, I've had zero stability problems with both Eclipse and Tweaked. Eclipse is farther from stock when you consider the apps and the look and feel. Tweaked is closer to stock from an app standpoint, but the framework has been more heavily modified to integrate the customizations (TSM Parts primarily).
ibthevivin said:
I think it would be appropriate for me to specify what exactly I'm looking for. Thanks for your response shrike. What I'm looking for is the least buggy, most responsive ROM that offers reasonable battery. Customizable features is nice but that's exactly a must.
So I see the poll is shooting towards Tweaked, so I guess I'll ask, is Tweaked the most appropriate ROM that will fulfill most of what I'm looking for, if not all?
Click to expand...
Click to collapse
Based on what you're looking for, I'd recommend Eclipse. I'm currently using Tweaked because I like the statusbar customization options, but everyday I experience a few freezeups that persist until I get a hotboot or I pull the battery. I've reinstalled several times after going back to stock EP4, and I've gotten the freezeups after each new installation. This has been the case regardless of whether I'm on the stock FP1 kernel or the 0415 pbj kernel. I never had this issue with Eclipse.
Son of Cicero said:
Based on what you're looking for, I'd recommend Eclipse. I'm currently using Tweaked because I like the statusbar customization options, but everyday I experience a few freezeups that persist until I get a hotboot or I pull the battery. I've reinstalled several times after going back to stock EP4, and I've gotten the freezeups after each new installation. This has been the case regardless of whether I'm on the stock FP1 kernel or the 0415 pbj kernel. I never had this issue with Eclipse.
Click to expand...
Click to collapse
Sorry to hear the troubles - while the description here is a bit too vague for me to be of much help, would you mind PMing me some specifics? Plus if there is any regularity maybe you could get a logcat?
Son of Cicero said:
Based on what you're looking for, I'd recommend Eclipse. I'm currently using Tweaked because I like the statusbar customization options, but everyday I experience a few freezeups that persist until I get a hotboot or I pull the battery. I've reinstalled several times after going back to stock EP4, and I've gotten the freezeups after each new installation. This has been the case regardless of whether I'm on the stock FP1 kernel or the 0415 pbj kernel. I never had this issue with Eclipse.
Click to expand...
Click to collapse
I flashed Eclipse. I'm liking it a lot. So far so good! I had one interesting occurrence though, it prompted for a system update. I clicked on it to update (not expecting it to but just to see what happens) and nothing did happen. I know when I had my LG Revolution with Gingervolt on it, those system updates caused issues with rebooting and turning off. So far I have no issues, but should there be a concern for this? Other than that, I am pleased.
Thanks Nitro! and thanks to the rest of you all for your feedback. My phone is impressing the crowd and has taken a nice warm dump on my friend's iPhone.
ibthevivin said:
I flashed Eclipse. I'm liking it a lot. So far so good! I had one interesting occurrence though, it prompted for a system update. I clicked on it to update (not expecting it to but just to see what happens) and nothing did happen. I know when I had my LG Revolution with Gingervolt on it, those system updates caused issues with rebooting and turning off. So far I have no issues, but should there be a concern for this? Other than that, I am pleased.
Thanks Nitro! and thanks to the rest of you all for your feedback. My phone is impressing the crowd and has taken a nice warm dump on my friend's iPhone.
Click to expand...
Click to collapse
If you keep getting update notifications, you can see this thread:
http://rootzwiki.com/topic/21207-stop-ota-notification/
This is going to be a long post, but please bare with me. The reason for this post is too hopefully reduce the number of "Help me choose a rom" threads, as they seem to get posted quite frequently, and ask basically the same questions. So in this thread ill be going through some of the basics, as well as some highlights of each type of rom
Introduction
I wrote this thread in an effort to make things easier for "noobies" or "new users" whichever you'd like to call them, so that they can have a better understanding of what the various types of Rom's are out for the Galaxy SIII or may be out in the future. Here's a very common question, what is a rom? A rom on our android phones is like the operating system on your computer, it controls the user interface, what you see and what you can do. Thankfully we have developers who have taken the stock rom's and changed them up and made them 'better' so that we the users can unlock the full potential of our phones. In this thread i will do my best to give you a brief outline of what you can expect with the different types of roms, and what bugs you may encounter. What i will not do is make any claims as to what the 'best' rom is, or tell you what you should be running. I am simply going to give you the information that you need to better help understand what can be included with each rom type
***Disclaimer: Anything you do after reading this thread is on you, what you decide to flash or not to flash is on you. I am not to be held responsible for anything that you do to your phone. This is simply information to help guide you and teach you a few things about roms.***
What you won't find in this guide, but should familiarize yourself with:
These guides don't have to be read, but i highly recommend you at least glance over them to familiarize yourself with a few things, before flashing your first rom. They all contain important information that you should know
*Any instructions on rooting your phone or how to install a rom, those can be found here
*Any rom download list, that can be found here
*A way to get Google wallet to successfully work on your Verizon SIII, that can be found here
Important ------>*A guide to backup your IMEI, that is here<------ Important
Important ------>*An IMEI repair guide/tool, that can be found here<------ Important
*A way to unbrick your softbricked phone, that's can be found here
CHAPTER 1: Touchwiz Roms
***Based on samsung's touchwiz.
Section 1: Stock Rooted Roms
These roms are exactly how its said stock and rooted they are the OTA's that verizon puts out, the only difference is that they've been pre rooted for the rooted users who want to be rooted but just want that basic stock experience. They may come in two flavors: Odex and Deodex, the difference between the two is the way that applications (apk files) are packaged. Odex is the stock way, and Deodex is repackaged, if you're looking to make minor modifications or do a little themeing then you want Deodex because 99% of theme's are built for Deodexed ROMS. There isn't much to be said for stock rooted roms, you're going to get that stock experience that comes with the phone but with root capabilities (titanium backup, wifi tether, overclocking, etc)
-Is this for me? If you want that exact samsung touchwiz stock feel with nothing added in then yes this is for you.
Section 1A: Debloated Stock Rooted Roms
These roms are going to be "debloated" meaning most if not all the fat is taken out of them. In the SIII's case you're going to lose most of the samsung apps and verizon apps. With this you may also lose some of those touchwiz features (smart alert, direct call, etc) or verizon features (NFL mobile, my verizon, etc). The benefit? You're still going to be mostly stock, and you may notice a speed increase due to there being less fat in the rom. There are various levels of debloating as well, some are more extreme and have had everything removed except for the essentials, and some will only remove a few things. Its best to read the original post with each rom to have an idea of what has been removed.
-Is this for me? If you want the barebones experience without using AOSP the yes this is for you.
Section 2: Modified "Stock" Roms
These roms, are going to be the touchwiz rom's made for verizon phones, the base (what the rom is built on) will either come from OTA updates or from leaks. These roms are modified in someway, some more than others. The modifications can include a wide variety of things from the basic speed tweaks, enhancements, and themes to including custom kernels, removing the wifi notifications, extra toggles in the notification bar, 4 in 1 reboot menu, and many other things. They are in a sense stock, but at the same time not. Think of it as a developer taking something 'good' and making it 'great' they've added in the stuff that should have already been there from the start. They will generally be deodexed already, may or may not have been debloated to a point, and generally will have a lot of 'under the hood' enhancements.
-Is this for me? For most people this is for you. You'll have a lot of the touchwiz features that you've come to love such as the camera, smart alert, direct call, and other features, while also getting a much faster and generally better experience. You'll be able to flash themes easily (make sure to double check that the theme is compatible with your rom) root app's will work and you'll be happy.
Section 3: Leaked Roms
These roms, are built off of leaked builds/bases. They may be ICS, Jellybean, etc. These rom's generally may have bugs to begin with depending on the leak itself. Some leaks are a little more stable than others, generally the only time leaked builds have major bugs is when its a leak of the next android version (a leaked JB Touchwiz build for verizon) otherwise they'll generally be almost bug free. There isn't much to say about any leaks of the current version (SIII shipped with ICS Touchwiz) because those will generally just get merged into the custom builds and such. Leaks for future versions generally have bugs, some big, some small, but usually get worked out quickly depending on the bug.
Is this for me? If you're looking to get that future android feel before its official then yes its for you. But you have to be willing to accept that everything may or may not work, and may or may not get fixed before an official release happens. You'll have the latest and greatest though and be able to brag to you're friends about having it before they do.
Section 4: Ported Roms
These roms are ports, meaning they could come from a different carrier (Example: AT&T JB touchwiz on verizon), different manufacturer (Example: Sense 4.0 on SIII), etc. These rom's will almost certainly have bugs to begin with. They are in a way like leaked roms because they aren't "official" for the SIII, but also vastly different because they may not even be mean't for the SIII. These rom's generally require a lot of work to even get booted up because its based off something that's not even mean't for the verizon SIII and a lot of work goes into them. Bugs could range from little things like screen flickering to GPS being completely borked, to your phone not even booting up. After they've had some work hammered into them and testing done, they can be really functional as a daily driver.
Is this for me? If you're looking to have something different or the latest and greatest then yes its for you. But like i said with leaked rom's you have to be willing to accept that you may encounter a vast variety of bugs that may or may not get fixed quickly or at all depending on the bug.
CHAPTER 2: AOSP (Android Open Source Project) Roms
What you won't find in AOSP: Any touchwiz features, yes this includes the camera as well. This is because touchwiz features and apps require the touchwiz framework which is not in AOSP and probably never will be. You also will find that verizon apps tend to be hit or miss as well, most of the time they won't work either, yes this includes NFL mobile and My Verizon.
Known issues when going from ICS touchwiz to AOSP JB:
*GPS may not work correctly, the fix? Before flashing to AOSP JB make sure you have a full gps lock (i personally download gps status from the market and wait until almost all satellites are locked) then from in the app boot into recovery and do your usual wiping/flashing.
*NFC may not work correctly, the fix? Ensure NFC is turned on before flashing to AOSP JB (i personally don't use NFC so i can't comment on whether that works or not, but i've heard it does)
***Based on pure android, you won't have any kind of carrier/manufacturer features added in. If you've ever had a Nexus device then you'll know what this is.
***Themeing is also super simple, with AOSP you get the Theme chooser, which makes changing themes as simple as a few clicks, just download a theme chooser theme off the market and then go into theme chooser and apply it. It really is that simple, if you want to change back just apply the "system" theme, and bam you're back to normal
Section 1: CyanogenMod (CM)
The one's who started it out, they've been around for what feels like forever. This rom will be built straight from the latest source, and it'll be fast from the get go. You'll immediately notice that you've got a lot more RAM free off the bat and this is because there is absolutely no bloat in it at all. You'll have the pure google android experience, it'll be a love or hate thing. For CyanogenMod they generally have nightly builds for those who love to flash, and it'll have added in whatever they added/fixed for that day. These builds may be stable or may not be stable, today's nightly might suck while yesterday's was great. For these if you know what features the latest android version has most likely they'll be in CM, so if you stay up to date then you'll be good to go. Some features are added in though such as notification widgets/toggles, speed tweaks, various other shortcuts. They will generally keep it mostly stock android but also give you some treats that make it better. Bugs are hit or miss, especially for the SIII because pure AOSP android was not built for it originally so some things may be a little iffy (GPS, data, nfc, mms, call volume, etc) it doesn't mean they are all broken, but it's possible they are hit or miss at times, and you're miles may vary. For one person GPS might be fine and the other it could be broken.
Is this for me? If you're looking for that pure android experience without any manufacturer crap in it then yes its for you. Just know that you may encounter bugs that don't get worked out right away, some of them take time.
Section 1A: Unofficial CM Builds
These builds are based off of CM but they are unofficial because a developer wants to make nightly changes, and add in there own modifications, themes, fixes, enhancements, etc. They come with the same risk as official CM builds, but any bugs found in them should not be reported to the official CM bug tracker because then these are unofficial builds. There isn't anything wrong with them being unofficial, its just a developer wanting to add there own twist to the CM builds.
Is this for me? If you're looking for that pure android experience without any manufacturer crap in it then yes its for you. Just know that you may encounter bugs that don't get worked out right away, some of them take time. Please read the OP's thread to understand what changes they have added in.
Section 2: Android Open Kang Project (AOKP)
Almost just like CM but with a little more added in. Its based off the android source code and again won't have any manufacturer crap added in. With AOKP you'll get added in modifications that may not be found in CM, as well as other kinds of toggles, status bar mods, notification mods, etc. I can't say everything because its still based of android source and comes with the same risk as CM which is certain bugs or things not working (GPS, data, nfc, mms, call volume, etc) They know there stuff though and have "Builds" released from anywhere from day to day or weeks apart these builds are more major releases with various fixes, modifications, etc.
Is this for me? If you're looking for that pure android experience without any manufacturer crap in it, and more modifications than CM then yes its for you. Just know that you may encounter bugs that don't get worked out right away, some of them take time.
Section 2A: Unofficial AOKP Builds
These builds are based of off AOKP but they are unofficial because a developer wants to make there own changes, and add in there own modifications, themes, fixes, enhancements, etc. They come with the same risk as official AOKP builds, but any bugs found in them should not be reported to the official AOKP bug tracker because then these are unofficial builds. There isn't anything wrong with them being unofficial, its just a developer wanting to add there own twist to the AOKP builds.
Is this for me? If you're looking for that pure android experience without any manufacturer crap in it, and more modifications than CM then yes its for you. Just know that you may encounter bugs that don't get worked out right away, some of them take time. Make sure to read the OP to understand what has been changed in the build though.
Section 3: Paranoid Android
This rom is a phone/tablet hybrid rom. Its based off of pure android source just like CM, but has made vast changes to it. You'll be able to modify how each specific app shows up on the screen (want tablet mode only for youtube then you got it, want facebook to look bigger or smaller then you got it) and you'll get a wide variety of modifications as well. If you've ever watched a video of a tablet then you'll have an idea of what can happen. It truly is a phone and tablet hybrid, bringing the best of both worlds to your phone. It'll feel like pure android source and will have those features that come with that android version just with the tabletness added in. It comes with same possibility of bugs as other AOSP roms (GPS, data, nfc, mms, call volume, etc) these bugs are not guaranteed and may or may not occur. User A might have data issues but user B may not, your miles may vary with AOSP. Its a bit harder to explain everything for this rom, but i'm doing my best.
Is this for me? If your looking for pure android goodness but with a major overhaul of added in phone/tablet mode hybrid then yes its for you. Just be willing to accept that you may encounter bugs along the way.
Section 4: Other AOSP Roms
The reason i have this section is because its impossible to describe every kind of AOSP roms, especially when more can be added and such. But other AOSP rom's will come with the same pure android source as well, and will have those features. A lot of them merge in code from other various developers (with permission of course) but also add in there own toolkits, setting menus, etc. They are all great roms, but its hard to give every single one a section because its there all based off the same source and have some of the same kind of modifications added in. They all come with the same risk as other AOSP roms in terms of bugs (GPS, data, nfc, mms, call volume, etc) For these rom's you'll have to pick and choose, if you love a certain developer that makes AOSP roms, or have used a developers AOSP rom on a different phone then you'll know what to expect from that rom/developer. Again there is nothing wrong with these rom's its just hard to give all them all there own section when most of the information is going to be the same and repetitive.
Is this for me? If you're looking for that pure android experience without any manufacturer crap in it then yes its for you. If you follow a specific developer then yes its for you. Its going to have more modifications then regular CM or AOSP roms. You really have to test them out for yourself, just read the thread and see what they've changed/modified/added in. Just know that you may encounter bugs that don't get worked out right away, some of them take time.
Section 5: MIUI Rom
Miui is AOSP based but it won't look like it is. This is because with MIUI you get an entire different user interface experience. It's got its own custom toggles in the notification pulldown, its own theme engine (theme's have to be designed specifically for miui), its own camera app, and many other apps that are designed specifically for it. The main miui team puts out a rom in chinese once a week every friday, and it then gets ported to various devices including the SIII. The downside to miui is some things take a lot longer to get worked out in terms of bugs, this is because its ported to our phone but also because its a completely different interface with many applications that have to be worked on before they'll work flawlessly. Its got the same possibility of bugs as other AOSP roms. I've personally used it before on another device and ill tell you its definitely one of a kind, and fun to play with.
Is this for me? If you're looking for something completely and totally different then yes this is for you. Just know that because the larger builds are released once a week it may take time for some bugs to get worked out, but again you'll have something that's completely different from any of your friends as long as you can accept a few bugs here and there.
Section 6: Various Issues and Solutions
NFC Issues: Grayed out, won't turn on, etc. This is NOT a problem with rom itself, to solve this issue you will need to go back to a touchwiz rom and turn NFC on. Then boot into recovery and flash your respective rom choice If that still does not work flash this zip here in recovery after flashing your respective rom.
GPS Issues: Again not Rom related entirely, its more or less AOSP related. This problem again can be avoided by ensuring a full gps lock and leaving gps turned on prior to flashing. If you still have issues after that download GPS status from the market and use that to help with the gps lock. You can also flash this zip file here to help solve the issue
CHAPTER 3: Kernels/Battery life/Radios/Jelly Bean 4.2 Storage System
Section 1: Kernels
Okay kernels are one of the biggest advantages to rooting. They can be used to increase performance vastly, increase your battery life, make your phone faster, increase ram, etc. You can modify the clock speeds using apps to overclock or underclock the cpu, you can increase or decrease the voltage, etc. They are also what makes your phone boot up (flash a kernel mean't for touchwiz on AOSP and its not going to boot up) Kernels are built on two main bases for the SIII: Android Version (ICS, JB, etc) and Touchwiz/AOSP. This means that these kernels are used for specific rom bases and android versions. You have to make sure you read what the specific kernel is built for so you don't flash the wrong one and mess up your phone. Kernels are always your miles may vary, a kernel that works great for me and doubles my battery life, might make yours worse. You really can't guarantee any of that until you flash it on and modify the settings to your liking. Always make a backup before flashing a kernel so just incase your phone doesn't bootup you can easily restore the backup.
Section 2: Battery Life
This is another question i see asked all the time "What's the battery life like?" Battery life is based on a few things:
1. ROM Choice - Some roms might have better battery life than others. Your miles again will vary. You'll never get the same experience as another user.
2. Kernel choice and settings - some kernels work better than others in terms of battery life, what works for you may not work for me. But you can modify your cpu speed settings to help with this. Settings screen off profiles can help as well. I personally decrease the cpu to 384mhz while the screen is off, and it helps me, will it help you? I have no idea.
3. Personal Use - Self explanatory, if you're constantly using your phone, browsing the web, sending emails, playing music, gps, this and that then the battery might drain faster than somebody who doesn't use there phone as much. If you manage to get 3-4+ hours of screen on time then your battery life is fine. How quickly you reach that is based on your use. This also includes whether your still on the stock battery or not, if you've got an extended battery in your phone then your battery life may very well be a lot longer than somebody with the stock battery. You have full control over your personal use.
4. Coverage and Signal - If you're constantly in areas with terrible signal then your battery life will suffer. My suggestion? If you're near wifi turn it on, that way your signal won't matter as much because all your syncing and such will be done through wifi. There isn't much a rom or kernel developer can do about this, its just based on where you live.
5. Wakelocks and syncing - Make sure to download betterbatterystats, why? Because if your battery life sucks then your phone may not be going into deep sleep and this app can help tell you why. Wakelocks are anytime that your phone is awaken from deep sleep, the more wakelocks you have the less deep sleep you get which equals less battery life. Some of these wakelocks can be controlled because many are caused by syncing. If you have apps syncing every 10 minutes, don't expect super great battery life because your phone is constantly being awaken. Control your syncing, if you don't check twitter every 10 minutes then don't have it sync every 10 minutes. A lot of those apps will automatically sync upon being started.
6. Perception - I put this here because its true. Everybody expects something different with there battery life, so they perceive it that way. Some users want over 24 hours whereas some don't. For me personally i consider great battery life to be being able to leave for work at 6:45am, then go to class, then go to the gym, then do whatever else and come home. If i can make it from 6:45am to 8 or 9pm without being forced to charge then i consider that great battery life. Why do you say its great when its only 14 hours without charging? Because i charge my phone every night before going to bed, it may not even be less than 50% less but i still charge it so that's good enough for me since i made it through my day. Everybody has different expectations so don't always assume battery life sucks when somebody says it does because its based on there own perception of what's "great" and what's "bad"
Battery life is and always will be your miles may vary because there are just too many factors to consider. Some people who say "The battery life on this rom sucks" just have a runaway app killing there battery life and don't even realize it. The only true way to gauge battery is based on what you consider to be great battery life.
Section 3: Radios
Another question asked "What's the best radio?" Radios are always your miles may vary, its all based on your signal/coverage area. But there's also a big placebo effect that comes with radios, the second you flash a new radio, you expect the signal to be better so you see it that way. It might actually be better or it could be worse or exactly the same. Some users will get increased speed on one radio and somebody else might get decreased speed, but you can't base your radio stats right after flashing it because you need to test it in real world scenarios, not just sitting around looking at the dbm. I didn't originally plan on having this section but its necessary because in the future you may or may not need a specific radio for a specific rom to work. As of right now (10/22/2012) the radio you choose to use will work on any rom (make sure its a verizon radio) in the future though you may have to use specific radios for specific roms depending on the versions of android that come out, and when that happens you'll have to make sure you're using the right radio otherwise you may not get any kind of signal at all. Remember that radios are mostly user experience based, and what works for you might not work as well for somebody else.
Section 4: Jelly Bean 4.2 Storage System
Alright i'm going to do my best to explain this in the simplest way possible. With the introduction of 4.2 Jelly Bean, the storage/file system changed as well. What i mean by this is at least on AOSP roms when you flash a 4.2 Rom you'll get a "0" (zero) folder with everything from your internal SD card in it. The reason for this is because with the multi user support its the new way Android sorts stuff. Now many of you are probably wondering "Ummm... this is confusing" or "is this bad?" it is confusing at first but honestly its not that bad. The /storage/sdcard0 now points to /storage/emulater/legacy folder which is then emulated by the 0 folder. Easy version: Even if you put stuff in /storage/sdcard0 it'll automatically show up in those other folders anyways. It may look like you've got stuff duplicated, but its really not. Whatever file is on the sdcard0 (Internal card) is only there once.
The good news, if you update your recoveries to the latest versions, then you won't have to worry about any 0 folder nonsense anyways. You'll still have a legacy folder, but that's not a big deal. Just don't mess with it and your phone will be fine.
***If anybody has a better explanation for that, PLEASE let me know and i'll update/add it in ***
I really hope that this thread can help reduce the number of questions asked about which rom to use and such. I put a lot of time into typing all of this out to help you guys, so hopefully it'll do just that and help
Also i spent a lot of time writing this up, so please do not copy and paste it on another forum and claim it as your own work. I realize its just a guide and relatively public information, but still i'd rather it not get copied and pasted onto other forums/threads.
Click to expand...
Click to collapse
***MODS: feel free to move this if its in the wrong place or something***
Mine
****Change Log****
3/14/2013
Chapter 3:Section 4: Jelly Bean 4.2 Storage Added
12/2/2012
Made backing up your IMEI "Important" to read
Added an AOSP common problem and solution section
10/25/2012
Added another IMEI backup guide to the top.
Added encouraging words for reading other guides.
10/24/2012
Added in links for other useful guides at the top
Added in known issues when going from ICS Touchwiz to AOSP JB
10/23/2012:
Added in Miui (Section 5 under AOSP Roms)
Added in Introduction and Disclaimer (very top)
Began fixing grammar errors
Super! Thx for this contribution
Sent from my SCH-I535 using xda premium
Super write up. Thank you very much.
Great info. Thanks. - noob
Sent from my SCH-I535 using Tapatalk 2
How do people have time to write this ****? Lol!
Sent from my Nexus 7 using XDA Premium HD app
Awesome write up for the noobs bro.
Sent from my SCH-I535 using xda premium
I was just thinking we really needed a single source to track the progress of each ROM category. This makes a great framework for tracking that information. Thanks for putting this together.
My suggestion would be to add a few bullets below each ROM category that note the most prominent long-term bugs. I think that could significantly reduce the same question being asked over and over within each topic.
Example: all of the AOSP 4.1.x ROMs currently suffer from low video recording volume, poor voice command recognition, and limited in-call volume range (as of this post). Just a suggestion. Keep up the good work!
DroidHam said:
How do people have time to write this ****? Lol!
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I really have no idea, i was just sitting and thinking "man i answer the same questions almost everyday, if only there was a single thread for the answer" and well... now its here
apet8464 said:
I was just thinking we really needed a single source to track the progress of each ROM category. This makes a great framework for tracking that information. Thanks for putting this together.
My suggestion would be to add a few bullets below each ROM category that note the most prominent long-term bugs. I think that could significantly reduce the same question being asked over and over. Example: all of the AOSP 4.1.x ROMs currently suffer from low video recording volume, poor voice command recognition, and limited in-call volume range (as of this post).
Click to expand...
Click to collapse
Thanks for the suggestion I actually considered that and may add it in within the next few days, we'll see what happens.
Neverendingxsin said:
I really have no idea, i was just sitting and thinking "man i answer the same questions almost everyday, if only there was a single thread for the answer" and well... now its here
Thanks for the suggestion I actually considered that and may add it in within the next few days, we'll see what happens.
Click to expand...
Click to collapse
After thinking about this concept more, a community-maintained wiki might actually be a better medium for efforts like this. Ensuring accuracy, keeping everything up to date - and remaining relevant as a result - always seems to be the greatest challenge.
This thread was well over due. Thanks for taking the time to write it up.
Sent from my Galaxy SIII
Very helpful. I think you may have repeated yourself somewhere in there
Shh! maybe I'm just paranoid, but I think people are listening....
Well thanks man!
Sent from my Nexus 7 using XDA Premium HD app
Thank you!
Super!!! Thank you! :good: :good: :good: :highfive:
Sticky!
FrostyOrDie said:
Very helpful. I think you may have repeated yourself somewhere in there
Shh! maybe I'm just paranoid, but I think people are listening....
Click to expand...
Click to collapse
I'm pretty sure i did lol
Samsung.Galaxy.S3 said:
Super!!! Thank you! :good: :good: :good: :highfive:
Sticky!
Click to expand...
Click to collapse
+1
Sent from my SCH-I535 using xda app-developers app
apet8464 said:
After thinking about this concept more, a community-maintained wiki might actually be a better medium for efforts like this. Ensuring accuracy, keeping everything up to date - and remaining relevant as a result - always seems to be the greatest challenge.
Click to expand...
Click to collapse
mhmmm. Thats why i tried to keep this as "basic" as possible and just going over the general stuff. I'm able to keep up with a lot but only to a certain extent.
Neverendingxsin said:
mhmmm. Thats why i tried to keep this as "basic" as possible and just going over the general stuff. I'm able to keep up with a lot but only to a certain extent.
Click to expand...
Click to collapse
True. Fortunately, the ROM categories themselves are fairly constant, so this thread should be pretty low maintenance. Hopefully it will get stickied or merged with a stickied thread so it remains visible to noobs.
apet8464 said:
True. Fortunately, the ROM categories themselves are fairly constant, so this thread should be pretty low maintenance. Hopefully it will get stickied or merged with a stickied thread so it remains visible to noobs.
Click to expand...
Click to collapse
Yeah thankfully they are I've just got a few more things to add and a little cleaning to do with this thread.
great writeup...this needs merged with the download list thread.