Related
I am a jailbroken iPhone convert. I am loving this phone so far and have heeded the warnings to not mess with the phone too much. My question is, when is it safe to use the roms that are available? Is there that big of a difference in performance? I jailbroke my iPhone to get features Apple wouldn't allow our have. what do I gain with custom roms? Thanks for all that has been done so far and look forward to what its to come.
I don't know of there is a time period to use them but most custom roms freshen up your desktop icons as well most of them improve battery life and add the ability to overclock.
You can gain quite a few features with Custom Roms. Such as overclocking, custom ui's, much better performance (snappier). I highly recommend flashing a custom ROM. Currently CM9 and CM7 are a work in progress and should be released sooner than later, (CM7 is currently in it's testing stage). Also to do all of this you have to root your device. A guide can be found here: http://forum.xda-developers.com/showthread.php?t=1327741&highlight=how+to+root Keep in mind many features can be gained once rooted, but as you probably know the warranty is voided.
Thanks for the help so far. The only question still remaining for me is; at what point are these roms considered stable enough for someone new to start using. I have read the warnings and really don't want to have to reinstall everything over and over again because of instability issues. thanks
ed20910 said:
Thanks for the help so far. The only question still remaining for me is; at what point are these roms considered stable enough for someone new to start using. I have read the warnings and really don't want to have to reinstall everything over and over again because of instability issues. thanks
Click to expand...
Click to collapse
It really all depends on what you are after.
I will say that even the stock ROM on the Atrix 2 is not that stable, and there are a TON of bugs in it.
All the ROMs that are here are in a beta format and are not even at a 1.0 revision yet. If you are not technical at all, and don't really like playing with your device a lot, and flashing ROMs, to try and get a feature that the stock ROM is missing, then I totally advise against flashing anything. These "ROMS are completely safe and stable enough", but both lfaber06 and are I always trying to "improve" on them, no matter what revision that the ROM is at, as well as requests for new features. That really is why it may seem that people are flashing all the time, not really because of instability.
Since he and I are really the only two devs in here right now, there is not going to be a lot of choice in ROMs and since this phone is still fairly new, everything is still "new" and in beta/alpha. Since you are coming from the iphone, and flashing ROMs is not really something that you do, I say you wait until you find something you really want that is not available in the stock ROM, and has been put into one the ROMs available here, then try flashing that. Until then just hang tight for a while. There are plenty of hacks that can be done to the stock ROM, to fix things, and make that better at this time. Also take some time to learn a little about android and flashing and how it all works, not intimately, or on a very technical level, but that might save your "you know what", if you have an issue during a flash or while running an unfamiliar ROM.
Thank you VERY much. That was the answer I was looking for. I am technical savy, just haven't done much with android so far. I am one that likes to tinker and get the most out of any of my electronics.
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.
I had the Vibrant and flashed all kinds I'd ROMs with it. Moved to the iPhone 4s and then traded that for my new S3. It was a good choice. So now I'm planning to get started flashing on this phone.
Wanted to know what is the same and what is different from the Vibrant from previous Vibrant users.
What's the best place to start flashing? I'm looking for stability and speed. Preferably more stability than stock cause stock is a little buggy honestly.
Sent from my SCH-I535 using xda app-developers app
GoodVibrant-ions said:
I had the Vibrant and flashed all kinds I'd ROMs with it. Moved to the iPhone 4s and then traded that for my new S3. It was a good choice. So now I'm planning to get started flashing on this phone.
Wanted to know what is the same and what is different from the Vibrant from previous Vibrant users.
What's the best place to start flashing? I'm looking for stability and speed. Preferably more stability than stock cause stock is a little buggy honestly.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Please elaborate on what is buggy about stock?
My question was more about everything else I posted besides that statement but to answer the question, I am getting force closes on some apps and occasionally the home screen locks up. That's what I meant by buggy.
Sent from my SCH-I535 using xda app-developers app
there's a link in my signature that should help you id post it but im on my ipad using tapatalk right now.
In before the lock
Sent from my Galaxy SIII
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
And I was hoping someone could tell me what's stable and smooth right now. Stock has been touch and go for my device and I haven't done anything to it. I'm looking for a fast non-overclocked kernel matched with a stable daily driver ROM. Any help is appreciated, dickhead comments aren't. This place has turned all elitist. This is the General forums....thought I could get away with a few simple questions with answers based on experiences, after having read through all these threads.
Speaking of which NeverendingXin, I read a lot of that thread yesterday but it seemed to give descriptions of what AOSP vs AOKP vs CM10 vs MIUI. Which I learned a lot from and I appreciate. But I was looking for more advice on specific ROMs. Anyone that could say "This ROM with this kernel has worked for me and I like it's speed" or whatever would do.
You want to find out what's stable and smooth?
Man up and make a backup of your current rom and flash away trying different roms. You'll likely end up getting different responses from different people and it isn't likely you'll have their same experience. Just find out for yourself. The guide the person above directed to you to was made to prevent threads asking what rom is stable or to use.
Sent from my Galaxy SIII
GoodVibrant-ions said:
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
And I was hoping someone could tell me what's stable and smooth right now. Stock has been touch and go for my device and I haven't done anything to it. I'm looking for a fast non-overclocked kernel matched with a stable daily driver ROM. Any help is appreciated, dickhead comments aren't. This place has turned all elitist. This is the General forums....thought I could get away with a few simple questions with answers based on experiences, after having read through all these threads.
Speaking of which NeverendingXin, I read a lot of that thread yesterday but it seemed to give descriptions of what AOSP vs AOKP vs CM10 vs MIUI. Which I learned a lot from and I appreciate. But I was looking for more advice on specific ROMs. Anyone that could say "This ROM with this kernel has worked for me and I like it's speed" or whatever would do.
Click to expand...
Click to collapse
Well in that sense the best information I can give you is that for a touch wiz ics Rom I'd use synergy, I used that for a long time and it was always super stable and smooth for me. If your looking for aosp then I'd use either liquid smooth or slim bean I'm more familiar with liquid and it's really great, but I'm trying out slim bean and it's so far been good as well. I hope this helps
GoodVibrant-ions said:
In after the ****
Honestly, the post was more about the Vibrant than anything. I was hoping to see some of the same people and get their experiences on ROMs compared to what we had on the Vibrant.
Like on the Vibrant it went from Android 2.1 to 2.2 to 2.3 and you constantly had to be aware of what you were flashing. It doesn't seem that way (yet) with the S3 from what I've been reading. Is that the case? At this point everything is compatible and we're able to flash away for the most part?
Click to expand...
Click to collapse
I'm from the Fascinate but I've also worked on the Vibrant.
* You don't have to worry about bml/mtd here. Which means you can flash basically everything without having to odin.
* You do have to worry about the locked bootloader. CASUAL can unlock it. Droidstyle has a sticky thread here on xda to help you with this and many other processes.
* There are excellent stock and AOSP-based ROMS. AOSP-based ROMS aren't quite 100% (but close) on RIL issues though.
*On verizon, radios are typically flashed separately and only in certain circumstances (odin package) included with ROMS.
* You DO have to worry about the IMEI issue. There are numerous threads about backing up this information and a Sticky thread with a tool for recovering it.
* If you are looking for a custom kernel check out Leankernel which is linked to in the signature of the poster above me. note that it's an AOSP kernel. Find the touchwiz version in the same forum.
Something else to bote about unlocking the bootloader, if you are going to use EZ Unlock from the market DON'T!!!! Go to root wiki and download version 1.2. For some reason 1.3 & 1.4 are wonky. The older versions are on the same thread as 1.4.
My vote for a ROM is Paranoid Android, I had some bug issues on Liquid Smooth but on PA I have had none thus far. I would reccomend flashing Paranoid Android version 2.5 instead of 2.51, there seems to be an issue for some users with the latest commits in 2.51 from what I read earlier today.
I'm sure you know how to back up you IMEI but just in case use the terminal method and the synergy flash method.
Just trying to cover most bases, I didn't know what you knew and didn't know.
Sent by one of my many Anthromorphic Personifications
GoodVibrant-ions said:
My question was more about everything else I posted besides that statement but to answer the question, I am getting force closes on some apps and occasionally the home screen locks up. That's what I meant by buggy.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The reason I asked is because stock on the S3 is as stable as you are going to get. The most stable custom Roms are going to be the ones based of stock TW and you can get them with some added tweaks. They are no more stable then stock as stock is stable as a *****. If you are getting force closes and lockups there is probably an issue with what you have installed.
Any AOSP rom will still have bugs and will be the least stable out of all the options. No matter how many people say Liquid or AOKP or CM10 or PA or MIUI is running great, they run no where near as stable and perfect as any TW rom.
If you want stability, go with a TW rom. read the different threads, mostly the last couple of pages of each which are usually about the latest release and you will know what is good and what is not.
This is what I am running and it does not get any more stable then this but then again stock was stable as ***** as well...
http://forum.xda-developers.com/showthread.php?t=1904329
Thanks guys.... this is exactly what I was looking for. As far as backing up the IMEI, I've never had to do that. Not on the Vibrant or My HTC View....so I have some reading to do there. Any tips or links to threads on that would be appreciated.
And I did have to unlock the bootloader on the View, but it's not a process I know a lot about.... so reading to do there as well.
Thanks for the tips guys. Looks like I'm going back to do some more studying.
Sent from my SCH-I535 using xda app-developers app
A very very good post explaining how to flash recoveries, roms, and just about anything else you ever would need to know:
http://forum.xda-developers.com/showthread.php?t=1762709
IMEI Backup:
http://forum.xda-developers.com/showthread.php?t=1852255
EZ-Unlock for you bootloader, download version 1.2 it is towards the bottom of the first post:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Sent by one of my many Anthromorphic Personifications
Perfect. Thanks man. I'd seen the first two threads but not the ezunlocker thread. Should be all I need to figure out how to get started and which ROM to try.
Thanks for the help guys
Sent from my SCH-I535 using xda app-developers app
PaulG1488 said:
You want to find out what's stable and smooth?
Man up and make a backup of your current rom and flash away trying different roms. You'll likely end up getting different responses from different people and it isn't likely you'll have their same experience. Just find out for yourself. The guide the person above directed to you to was made to prevent threads asking what rom is stable or to use.
Sent from my Galaxy SIII
Click to expand...
Click to collapse
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
shangrila500 said:
Something else to bote about unlocking the bootloader, if you are going to use EZ Unlock from the market DON'T!!!! Go to root wiki and download version 1.2. For some reason 1.3 & 1.4 are wonky. The older versions are on the same thread as 1.4.
My vote for a ROM is Paranoid Android, I had some bug issues on Liquid Smooth but on PA I have had none thus far. I would reccomend flashing Paranoid Android version 2.5 instead of 2.51, there seems to be an issue for some users with the latest commits in 2.51 from what I read earlier today.
I'm sure you know how to back up you IMEI but just in case use the terminal method and the synergy flash method.
Just trying to cover most bases, I didn't know what you knew and didn't know.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
rampantandroid said:
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
Click to expand...
Click to collapse
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
shangrila500 said:
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Check the PA thread for the answer - go into PA settings, go to the app settings, find the settings app in there and hit reset. My guess is that it is a bug with the current version of the ROM.
GoodVibrant-ions said:
Perfect. Thanks man. I'd seen the first two threads but not the ezunlocker thread. Should be all I need to figure out how to get started and which ROM to try.
Thanks for the help guys
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
shangrila500 said:
Well the one in the marketplace may work fine for you but everyone else who has tried version 1.4 has posted so many messages because it didn't truly unlock their phone and gave them a soft brick. The reason it may work for you is because the dev finally fixed it. I just know that there have been numerous threads of people getting soft bricks from version 1.4.
As for Liquid, it is their spin off of CM10. There are a few notable differences but I honestly don't know how to describe them properly, you would just have to flash it and mess with it yourself.
I agree completely about CM10 being buggy as hell, I personally don't care for it but without it we wouldn't have half of the roms we do.
The upside to Liquid, PA, and some of the other offshoots is that the devs over them are busting their ass to get all the kinks worked out, and from my testing they are better than CM10 bug wise. Everyone's phone is different though and something that works for me will not work for someone else. For instance I can successfully over clock my phone to 2.1Ghz where a lot of people can go above 1.7 or 1.9 without losing stability.
As for you question about PA, I thought there was a setting to get rid of the double menu, but I just took a quick look and couldn't find it. I very well may have overlooked it though, as I said it was just a quick look. You could try googling it or asking in the PA thread and seeing if anyone can point you in the right direction.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
rampantandroid said:
I did it this way and spend 2 weeks of hell. Don't recommend this, PLEASE.
Here's my own thoughts, as reliable as the butt dyno installed in my TSX:
CM10: depending on the build it was OK to "omg, I just rebooted why is this running so slow?" I tried this rom twice and gave up. I had installed a nightly from Friday which is what had serious issues. I'd reboot and within 15 minutes everything would be crawling.
ParanoidAndroid: I might accept this if I could opt to have a phone styled settings app. I see no way to get that, and I don't enjoy my settings app on my S3 using a tablet layout. Can this be changed?
AOKP: Wifi didn't work without a kernel, battery life ranged from amazing to terrible (no data on why, I didn't look at my wakelocks) and bluetooth didn't function right - it didn't auto connect to my car.
MIUI: Verdict is out, first flashed it yesterday. First thoughts are that it feels slightly slow, but that might be because I put the governor into dynamic mode. Battery life is looking about on par with paranoid
Liquidsmooth: didn't see any reason to use this over PA or CM, didn't feel much smoother to me (forgetting the nightly build I flashed of CM10, because that was just awful.)
The one on the marketplace worked fine for me? It always says "unknown" but it unlocks. What does LiquidSmooth change from CM10? They don't seem to have many builds.
Can the ParanoidAndroid settings app be made to have a phone layout for settings instead of the double paned layout? If yes, I might give Paranoid a second try.
Click to expand...
Click to collapse
So what ROM did you end up using? Any that you'd recommend?
Please read forum rules before posting
Questions go in Q&A
Thread Moved
Thanks
FNM
Been using Cyanogenmod for a week now. Very dissapointed in the fact that my bluetooth audio sounds like AM radio. Also I get extremely bad echo during calls. Tried CM10 and 10.1. Both have the bluetooh issues.
Sure its a little bit faster. But, I rooted and installed a custom rom in hopes to IMPROVE me phone experience and I got just to opposite.
I'm considering going back to the rooted stock rom but I can't seem to find the link to the original latest verizon rooted rom. I didn't make a backup. Can anybody help me locating it?
On another note, I'm willing to try another custom rom if someone can vouch for it and ensure that there are no major bugs like CM10.
Should've bought an iPhone o_o but really the developers spend there personal time making these roms not for money but for us and themselves so if you're "disappointed" in them then make your own or try others, read threads and find out bugs before you flash.
Sent from my SCH-I535 using xda premium
xdakevin1 said:
Been using Cyanogenmod for a week now. Very dissapointed in the fact that my bluetooth audio sounds like AM radio. Also I get extremely bad echo during calls. Tried CM10 and 10.1. Both have the bluetooh issues.
Sure its a little bit faster. But, I rooted and installed a custom rom in hopes to IMPROVE me phone experience and I got just to opposite.
I'm considering going back to the rooted stock rom but I can't seem to find the link to the original latest verizon rooted rom. I didn't make a backup. Can anybody help me locating it?
On another note, I'm willing to try another custom rom if someone can vouch for it and ensure that there are no major bugs like CM10.
Click to expand...
Click to collapse
Don't use bluetooth so can really comment about it, however there are some great touchwiz roms in the Android Development section I stay away from the Original Android Development just because I have found too many issues.
As for some suggestions Synergy is pretty cutting edge though you may have to play with voltages if you install ziggy's kernal. Clean rom is another nice option. Hyperdrive and Delta have also run solid for me. Currently running Beans 12 and it is almost everything I can ask for, if a 5x6 launcher were included it would be perfection for me.
I would say to install twrp as your recovery, if you haven't done so, and install a rom and run it for a few days and see how it handles. Make a backup, twrp lets you rename them so you can easily restore to your favorite rom, and install something else for a few days. Also you may want to try different kernels as well, KT runs good for me but there are many more to choose from.
Finally just remember that each user runs different apps and has different needs and that while we all hqve the same phone minor variatikns n hardaware and just the way the rom flashes can have different effects such as bluetooth audio interferance or poor battery life or app abc will not work for one person but another has none of tjese problems.
Good luck and just remember that the perfect rom is out there waiting for you. You just need to flash like a madman until you find it.
Check out mastamoon's CM 10.1 rom. His latest 2-28 rom is near perfect. BT audio sounds great, signal handoff isn't as good as TW, but it's good enough as a daily driver. I've had little problems with it, to the point i don't even notice it. Try that and your mind will change.
xdakevin1 said:
Been using Cyanogenmod for a week now. Very dissapointed in the fact that my bluetooth audio sounds like AM radio. Also I get extremely bad echo during calls. Tried CM10 and 10.1. Both have the bluetooh issues.
Sure its a little bit faster. But, I rooted and installed a custom rom in hopes to IMPROVE me phone experience and I got just to opposite.
I'm considering going back to the rooted stock rom but I can't seem to find the link to the original latest verizon rooted rom. I didn't make a backup. Can anybody help me locating it?
On another note, I'm willing to try another custom rom if someone can vouch for it and ensure that there are no major bugs like CM10.
Click to expand...
Click to collapse
A. If you have issues with a ROM either post in the ROMs thread or in the Q&A section. Not start a thread in General bashing a ROM developers spent countless hours on. Just a respect thing.
B. Go to original development look for yourself, see what has features you like.
At this point, my phone is just one big tweak.
I'm sorry you're getting echo in calls and problems with BT. Would probably be solvable if you had asked since echo has been fixed for a long time.
Tapatalk via CM10.1 Galaxy S3
That's funny because i've been using AOSP for a few months now and its made my phone a thousand times better.
Neverendingxsin said:
That's funny because i've been using AOSP for a few months now and its made my phone a thousand times better.
Click to expand...
Click to collapse
+1
Sent using Tapatalk
I'm running the same ROM and absolutely love it. The only thing that's missing is multiview. Other than that it's near perfect.
Sent from my SCH-I535 using xda premium
responses are laughable
I think its funny, this guy has a valid complaint about how CM 10 is making his Bluetooth sound bad, and weather it's true or not, members just bash the $hit out of him, lol.
To the OP, if you don't like the ROM or something is glitchy, I've done two things in the past when I've experienced this.
1. make a backup (I use my backup root), and then boot into recovery, wipe (cache, davlik, system, and Format), then reflash your ROM.. OR
2. Find a new ROM and try that out. Currently I'm running the latest CleanRom with Morphology 1.5, and Ac!d audio..I have no issues with sound or bluetooth.
I hope that helps man, good luck and remember. Keep Calm and Flash Roms.
There are at least two threads where a total noob can seek help to fix the two issues he has, and one more where he can read how to fix his issues. Perhaps there are better ways to address his concerns?
Tapatalk via CM10.1 Galaxy S3
1Dirty_Mike said:
I think its funny, this guy has a valid complaint about how CM 10 is making his Bluetooth sound bad, and weather it's true or not, members just bash the $hit out of him, lol.
To the OP, if you don't like the ROM or something is glitchy, I've done two things in the past when I've experienced this.
1. make a backup (I use my backup root), and then boot into recovery, wipe (cache, davlik, system, and Format), then reflash your ROM.. OR
2. Find a new ROM and try that out. Currently I'm running the latest CleanRom with Morphology 1.5, and Ac!d audio..I have no issues with sound or bluetooth.
I hope that helps man, good luck and remember. Keep Calm and Flash Roms.
Click to expand...
Click to collapse
It really isn't a valid complaint. See below.
Restola said:
I'm sorry you're getting echo in calls and problems with BT. Would probably be solvable if you had asked since echo has been fixed for a long time.
Tapatalk via CM10.1 Galaxy S3
Click to expand...
Click to collapse
Plus, it's free. Beggars can't be choosers. Please don't condone his actions - he came across as very rude and ungrateful, whether intentional or not. You shouldn't complain when people give you free stuff. Period.
Sent from my SCH-I535 using xda app-developers app
Neverendingxsin said:
That's funny because i've been using AOSP for a few months now and its made my phone a thousand times better.
Click to expand...
Click to collapse
Couldn't agree more Sir.
Sent from GS3 running CM10.1
To the OP I say I hope you find a solution to your problem. Keep flashing and find what you need brother. To everyone else I am pretty new to this particular medium (xda forums) but looking at almost every topic I've seen I gather one very singular feeling. Please xda take away the "post new topic" option. Its pretty obvious that every single question that can possibly be asked has already been answered. So why ask any question. They are apparently evil and the world wide web has only limited space so lets please not clog it by asking a question twice *gasp*. There is a section for every device and build for developers only that by all means should be kept as streamlined and clutter free as possible but in general forum questions should not be so vehemently discouraged.
Sent from my SCH-I535 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I am also disappointed in the CM rom's performance...but I think the blame (for my issues, at least) resides totally with Samsung.
The rom itself works great, but when you're in the middle of a town and everyone else in the restaurant has 4g and you've only got 1x (not even 3g)...well...that's an issue.
Wish they would release the friggin RIL so I could just stick with a 4.2 rom. Grrrr!
S3 Radio
I don't know if this is the right place to post this or not. I recently had to return my phone to stock because my phone needed to be re provisioned to activate it again. This happens when you flash multiple roms apparently. I got my phone working and commenced to do everything to flash back to CM 10.1. I noticed I can make calls however, my 3g data will not come up. So, I have flashed back to stock and everything works fine. Anyone know of a tip that might resolve this issue. I was using the nightly from yesterday.
SubliminalME said:
I am also disappointed in the CM rom's performance...but I think the blame (for my issues, at least) resides totally with Samsung.
The rom itself works great, but when you're in the middle of a town and everyone else in the restaurant has 4g and you've only got 1x (not even 3g)...well...that's an issue.
Wish they would release the friggin RIL so I could just stick with a 4.2 rom. Grrrr!
Click to expand...
Click to collapse
Me too, my only real issues with CM (or any non-TW ROM) stem from the fact that the radio interface has not been released by Samsung and therefore the reverse-engineered AOSP RIL will probably never be as good as stock. It's not limited to signal strength issues, you also can't take full advantage of the phone's World Phone capabilities with a non-Touchwiz ROM. Unfortunately for me, that's a deal-breaker, my phone needs to work as a phone first and foremost and if Touchwiz ROMs have a better and more functional radio, I have to stick with that.
I have been using the latest nightlies of Cm and they have been running great. phone works great except in some areas where I can't get a signal with TW roms either.
I had CM running on my Dinc2. Since getting the S3, I've been running CleanROM with mods. (when I was on CR5.6 I was using KindaCrap Mods and now that I'm on CR 6.0 I"m using Andy Bones' AOSP Theme, which gives it a lot of the feel of CM).
I've tried almost every ROM on here. KK ROM's and JB ROM's...for some reason...VIPER XL always has issues for me. No idea why as it's a great ROM...I get dropped calls, SIM disappears and I have to reboot and a few programs FC all the time. Completely clean install...wiped entirely...tried different kernels, stock, OV and UV...everything. Just isn't stable for me.
Anyway - I love KK ROM's because of the battery life but I dislike the any non-sense camera. Sundream's MIUI ROM's were great but slightly outdated and sometimes had Google Voice issues.
Not complaining at all! I love all these ROM's and respect the dev's hard work!
Drew489 said:
I've tried almost every ROM on here. KK ROM's and JB ROM's...for some reason...VIPER XL always has issues for me. No idea why as it's a great ROM...I get dropped calls, SIM disappears and I have to reboot and a few programs FC all the time. Completely clean install...wiped entirely...tried different kernels, stock, OV and UV...everything. Just isn't stable for me.
Anyway - I love KK ROM's because of the battery life but I dislike the any non-sense camera. Sundream's MIUI ROM's were great but slightly outdated and sometimes had Google Voice issues.
Not complaining at all! I love all these ROM's and respect the dev's hard work!
Click to expand...
Click to collapse
My two cents:
I've found the "best" Sense-based ROM for a camera is Turge's t-mobile-based ROM (http://forum.xda-developers.com/showthread.php?t=2423735).
I also had trouble with ViperXL with random reboots and Airplane mode being enabled during calls. I may have just not used the right kernel.
In my opinion, KK ROMs don't really add much functionality to justify their installation. I always find myself going back to Turge's ROM for stability and Sense, which I really like.
Turge's ROM, being based on T-Mobile, enables hotspots, which is great.
Sense works, the camera works - everything just works; right out of the box.
I've added XPosed modules (e.g., Sense 5 toolbox) that help add some flexibility like swiping down to show notifications.
I also installed a camera that has both panorama and photo sphere (Gallery3d - http://forum.xda-developers.com/showpost.php?p=45923009).
But beyond that, no added mods.
Drew489 said:
I've tried almost every ROM on here.
Click to expand...
Click to collapse
If you've tried every ROM, why do you need us to spoonfeed you our recommendations?
"Best ROM" questions are frowned upon on XDA. The question is entirely pointless, as everyone uses their phone a bit differently, and what works "best" for one person might not for another. You might as well be asking what our favorite color is: What I answer really doesn't apply to you or anyone else.
Also, the question is an insult to the developers. Calling one "best" implies that others are somehow inferior, which is unfair to the devs that work so hard to bring us ROMs for free. Such discussions eventually just devolve into a popularity contest.
redpoint73 said:
If you've tried every ROM, why do you need us to spoonfeed you our recommendations?
"Best ROM" questions are frowned upon on XDA. The question is entirely pointless, as everyone uses their phone a bit differently, and what works "best" for one person might not for another. You might as well be asking what our favorite color is: What I answer really doesn't apply to you or anyone else.
Also, the question is an insult to the developers. Calling one "best" implies that others are somehow inferior, which is unfair to the devs that work so hard to bring us ROMs for free. Such discussions eventually just devolve into a popularity contest.
Click to expand...
Click to collapse
Basically this.
Thread closed