Related
i have got a samsung omnia7 and was thinking about using the sammy rainbow custom rom, what are the pro's and cons doing this?
atm i have interop unlocked it but as i am still under warranty was curious of the effects.
advice would be grateful
It varies heavily ROM to ROM. However, there are a few common things.
Advantages:
More device control. With the policy system disabled, you can modify almost anything.
More homebrew apps, and more powerful ones (things like bazaar).
Native homebrew apps and ported WinMo apps.
Install XAPs directly (such as from IE), instead of using a PC.
If you find a bug, you can directly talk to the devs about fixing it (or possibly fix it yourself).
You may get updates before your carrier would provide them normally.
Disadvantages:
Higher risk of bugs since the ROMs get a lot less testing than official ones.
Updates may come later because you have to wait for a custom packaging of the update.
Not all custom ROMs are updatable; you might need to replace it with a new version which means you'll lose all your data.
Turning off the policy system increases your risk of malware if you arent' careful what you install.
Custom ROMs may have malware built in (not saying any of them do, but it's a risk).
Currently, I'd suggest waiting a little while to see where the Samsung ROM scene goes, what bugs are found and how quickly they're fixed, what features are available and how useful they are. However, it's pretty much always possible to go back to a stock ROM (unless you somehow really badly mess up your phone) so if you want to experiment or be an early adopter, go ahead. Otherwise, I think it'll be pretty clear what ROMs are good and where the custom ROM scene is going (support- and feature-wise) within a month or so.
so i would be safer to wait and see what the dev of the roms is going to do in the case of bugs.
thanks
That's my take. Note that I'm a dev working very hard on hacks that works with stock ROMs though - somebody who spends their time developing custom ROMs may well give completley different advice. There are certainly lots of advantages to going with custom ROMs, even at this relatively early point (it helps that a lot of the experience from HTC custom WP7 ROMs carries over to Samsung ROMs as well).
it seems as though the custom roms for omnia 7 are coming on leaps and bounds, what with MIRO's ROM http://forum.xda-developers.com/showthread.php?t=1499102
there seems to be very little on the way of bugs with his atm so i think i will give that one a shot. i know i am new at this but if you don't ask then you never find out things right
thanks for your advice and input....much appreciated
I've been using the site for sometime and just wanted to put an idea if someone smarter than myself wanted to come up with technical details to make this work or it may already be in development but I'm not aware of it.
Getting the latest android update on phone with hardware capable of using it keeps coming up in a lot of articles that I read and it feels that the masses will probably never come to xda forums to get the updates they may want or need due to their lack of understanding of how to go abouts updating a rom.
The roms for most phones are being done by the community quicker and more reliable than the manufacturer in some cases. Here is what I think would work for masses to get the updates without the knowhow:
Create a process to get these custom roms quickly and easily loaded on to anyone's phone without them thinking about how to reboot in recovery mode. Similar to the Samsung devices getting updates from heimdall app found on this site. However it needs to be dumbed down and should be automatic when the user plugs in the phone.
This could be done by having a windows/mac application which when your phone is plugged in or connected wireless to your local network it would recognise what device you have and any additional information such as boot loader information it needs to search for official roms automatically from the manufacturer. If there is no updates then give the user the option to search for a market like store for unofficial roms which come with a warning to run at your own risk. These would be from the xda forums however they will need to meet a certain requirement as flashing from pc/mac may require a unique process from adb which is the key part to this idea working and I'm not too familiar with it to know if it's possible for some phones or all android phones. This store will contain different roms with user ratings of which is the most reliable rom. Essentially creating a market for roms. The user then clicks install and first thing the software does is to backup everything to save the state on the users hard drive in case you need to revert back to original.
This market should be controlled like the app store by the creators incase people abuse it. This means the requirement for any roms listed would be to include the default google experience and maybe a section for non pure google experiences as an option. It would be better if google created this app/process but let the roms be user/manufacturer driven.
Then through word of mouth/twitter/blogs this windows/mac app and within short time many people will be on ICS without much effort on google.
The android market is crying out from something like this to funnel all custom roms into a place accessible for the masses(knowing the risks of doing so). This separates the hardware binding to one specific software made for it, the user should be able to choose from selection off software which suits best for the hardware he/she purchased.
Obviously this is just an idea but hoping you clever people can come up with something similar. XDA Android Updater maybe
Isn't this exactly what ROM Manager does?
TeeRom said:
Isn't this exactly what ROM Manager does?
Click to expand...
Click to collapse
Nah he wants a better implementation that's dumbed down and on windows etc...
Sent from my GT-I9000 using XDA
Do you mean that custom ROM's are more reliable than stock ROM? Are you kidding, there are tons of issues with most custom ROM's, just read around here at XDA. But often those issues are not a big problem for a XDA enthusiast, since he chooses a ROM that suits him and also know how to work around those issues. But custom ROM is not something I would recommend my sister or my parents or any non-techie friend.
There are many roms which have become very mature and to a stage with minimal issues. I installed a ICS for my brothers desire, there may be some issues out there but many he won't come across such as migration apps from titanium backup. However he still gets to experience e latest functionality that the OS brings and he seems much happier with as the experience has become more smoother and quicker. I agree that there will be some which will be very much beta most of its lifetime and the market should reflect the known issues such as we have on the forums here.
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 do a lot of important things on my phone, so the protection is number the #1 thing for me.
All my previous 5 - 6 android smartphones were rooted by me.
The main reason for rooting was to improve security and confidence in the phone - good firewall, de -bloating, control of privilegies.
But now with S8+ I am having second thought about if rooting really protects vs exposes.
1) Lots of original protection features will be gone after rooting, like DM-verity
2) Automated system updates and therefore related security patches will be gone too. I am not a big fan of regular manual downloads and updates. So my once rooted system will become dated soon.
3) Fingerprint or iris readers be one more vulnerable to errors and manipulations
Am I taking it right?
Do a good firewall and control of priviligies outweigth the new risks that rooting could bring to S8+?
Thanks for you thoughts
Apparently now if you have a rooted S8, Netflix won't work anymore
aulamens said:
I do a lot of important things on my phone, so the protection is number the #1 thing for me.
All my previous 5 - 6 android smartphones were rooted by me.
The main reason for rooting was to improve security and confidence in the phone - good firewall, de -bloating, control of privilegies.
But now with S8+ I am having second thought about if rooting really protects vs exposes.
1) Lots of original protection features will be gone after rooting, like DM-verity
2) Automated system updates and therefore related security patches will be gone too. I am not a big fan of regular manual downloads and updates. So my once rooted system will become dated soon.
3) Fingerprint or iris readers be one more vulnerable to errors and manipulations
Am I taking it right?
Do a good firewall and control of priviligies outweigth the new risks that rooting could bring to S8+?
Thanks for you thoughts
Click to expand...
Click to collapse
You will get custom roms brother once you rooted , better than stock roms.
Thanks guys. Netflix is not a concern. But custom ROMs Iam not sure. Are they better protected than stock ROM? At least stock ROM is patched very often as new vulnerabilities are revealed. Not sure custom ROM are updated that quick. Plus automated updates without tye hassle of downloading flashing reinstalling is a big deal.
I would assume stock rom would stay most updated at least. Do stock ROMs offer the convenience of automated updates? ... and the speed and frequency of patches or fixes?
Ofcourse not rooted is more secure, it is silly to even discuss this. Rooting is the SINGLE most dangerous thing you can do. You allow 3rd party apps to modify your system. Yes, there is some sort of SuperUser app which asks for your permission, but it is still less secure than unrooted ROM. And as far as stock vs custom ROMs are concerned, would you trust more a group of enthisiasts that "modify" ROMS without proper knowlegde of inner workings or a company that does this for a living???
We all love CUSTOM ROMS, but in my experience on 5-6 (different) devices none of these are as stable as stock ROM, they cas say whatever they want, it is bull*. Stock is stock. Custom ROMs are used because we get new functionality, customizations, freedoom, maybe sometimes speed. But NEVER stability, I have flashed hundreds of ROMs since days of Desire HD through Note 2 and Nexus tablets, no custom ROM was ever as stable as stock. Period.
Personally i think it's hogwash to even think that rooting will expose you to security risks. I believe that's what most handphone manufacturers wants you to believe.
Just like an other tech you use, you make sure you do not install dubious apps. Rooting, like having admin rights on a PC, comes with certain risks and responsibilities.
Just imagine Microshaft or crapple telling you how to use their OS and how,if you have admin rights, will void your warranty or expose you to security risks, how you should use their bloatware apps or take their advice just because they know best?
Samdung doesn't like people tinkering with their stuff, especially when it outshines or is inherently superior to theirs. Their whole argument about rooting is just their way of scaring you to use their sorry of an excuse bloatware, building castles in the air and making sure you use their phones the"right" way.
Thank you Dalanik,
Then stock it is. I would still miss a good firewall or whole phone backup.
I felt quite secure when I saw new apps not being able to connect before I explicitly whitelist them in firewall.
But if it comes with a greater extent and complexity of exposure then I gave up
Thank you Frostmore,
It is not just about admin rights responsibility.
I saw people reporting fingerreader failures, knox being disabled etc. You lose some features which are designed to protect. There is no admin everyday routine that would compensate for that loss.
I would say if you don't overstand the workings of your device, you will not truly know..
Meanwhile from my experience from carriers, Samsung devices (good example: at&t note 4) is taking the enterprise route, more security for business purposes.
Non root I'd personally say from an amateur (myself) viewpoint (if you don't have the necessary knowledge to do it yourself). If someone wants to get you, they most likely will..
Another example is the location, there's multiple ways some of these apps get your location, clicking it off just seems like a "hide from user" option.
Good question though, don't see too many inquiries!
I m hesitant to root this phone. It will be the only non-rooted android I've owned. I am a developer with some embedded experience but I have become much more security conscious.
I so wish Sammy/Sprint would follow the Google Pixel model. The Pixel came out of the book without one iota of crap-a-ware. So refreshing to NOT be treated like a "mark" at a carnival.
The idea that I am Sprint's customer yet they treat me as a resource to serve up to their sponsors, like broadcast TV.
I run much of my business from this phone. I need VPN, TLS, SSL and all the security. I also develop for this device.
I may root in the future but I am going to stay clear of the bloody cutting edge for the moment. I appreciate you guys on the front line. Been there and done that...
Sent from my Pixel C using XDA-Developers Legacy app
Thanks SpringerRider, I like your idea of postponed rooting. I think Samsung with its pushy policies is becoming more and more hostile and arrogant to their own customers over time.
They degrade the support of their devices at akcelerated speed these days. For instance My 4-year old Samsung Smart TV lost 70% of its original functionality in the last year, because Samsung gradually stripped it from SmartHub via weekly updates. They don't want to support the TV even 4 years later after it was first introduced to the market. I guess the same philosophy would be applied on us, S8+ owners much sooner than we would have expected. I guess in 2-3 years we would on our own. Plus I bet Samsung would start overloading our phones with resource hungry bloatware via updates pushing us to buy newer models.
That would be the right time to root the phone and to cut the ties to Samsung.
So I totally get your idea and I thing it makes a good sense.
I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.
Lineage 14.1, Official. Installed the 'official way' (motorola unlock code). Not rooted. For me, working like a charm
You should try a different rom. AOSP Extended is based on AOSP-CAF. When I used a different ROM but also based on AOSP-CAF (purenexus) I faced the same problem.
Right now I’m on unofficial Lineage 15 (it still has some issues: random reboots sometimes but that seems to be an upstream issue as Pixels are also rebooting and having to use Footej camera to record video).
As @krondar said official LineageOS should be your best choice even though it doesn’t have some other more advanced custom ROM features. (Or just stock ROM from Motorola if you’re OK with Marshmallow)
Quantumstate said:
I have been trying ROMs for years now in my string of Motorola phones, and every single one of them has had one set of showstopping bugs or another. I haven't been able to find any firmware that I could actually live with for any length of time.
I am currently on AOSP Extended v3.3 and it can not give me notifications! My phone just vibrated with a phone call but it was not in vibrate mode! There was no phone with jiggly wires on the sides and when I turned the ringer up it was already at max! Yet no ringer.
I've missed appoointments because the calendar notifications don't work, I miss texts all the time because it can't manage out a tone.
All of us here keep upgrading to the next version in hopes of shedding one or more show-stopping bugs, but it's a dream continually unrealized.
Can any qualified developer tell me why this is so hard? Why can Android not get the basics right, even now that we have reached Oreo? Why is this advanced OS not able to do the little things a phone must do? Never-mind the advanced features like pie controls -- I'd learn those if I trusted this thing. But even on the best phones (my prior was a Moto X) I cant get a phone I can rely on.
PS - I tried an Apple phone for work a couple years ago and it worked, but I just hated it.
Click to expand...
Click to collapse
AOSP Extended is one of the best you can find here. But the version you are using is very old. I would recommend you clean flash the latest version and I believe you will love it.
I tryed Cyanogenmod 13 and it was awesome, and now I'm with Lineage 14.1 and everything is ok... no bugs,
Over the years I've tried every firmware from MIUI to Paranoid Android to CarbonROM to Cyanogenmod to ResurrectionRemix, and all have one set of basic problems or another. And worse, seem to deteriorate over time!
This should never, never happen with an advanced OS in the 21st Century. So I moved to the AOSPs and find the same syndrome! This implies a basic problem with Android -- after so many years it can not be gotten right. It's alarming.
Why is Lineage better? What is it based on? How is it different that it doesn't have these problems? How do you find out that one ROM is working better than all the others?
I've been using purenexus ROM for a few month and never faced any issue,not even a little one. It was 100% stable for me and the perfect ROM for a daily driver. AEX Is very good though and lineage OS 14.1 too.
Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.
Quantumstate said:
Actually I'd installed PureNexus right after my post above. It's 4 times faster than AOSP Extended v3.3, although I have yet to put it through the wringer. Time will tell.
Click to expand...
Click to collapse
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.
Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.
V-Droid said:
Why where you using such an old version of AOSP Extended? Currently version 4.6 (nougat) is available and work on Oreo has begun.
Click to expand...
Click to collapse
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.
Quantumstate said:
Why? Because I don't have time to be bit-twiddling every other day on my phone. I need to use my phone as a phone, since I am an adult.
Checking, my version of AOSPExtended was 9 March, 2017. You see 5 months, as old? What's the matter with you?
And no matter HOW old, why is it ever acceptable to you that it would sit silent as my phone calls, texts, appointments go by, and it forgets which keyboard I've chosen repeatedly? With this 13th generation of Android, the mission-critical fundamentals are completely busted? It was quite a feat to accomplish that.
Thankfully so far PureNexus is working. I hope that lasts more than 5 months without deteriorating.
Click to expand...
Click to collapse
If you don't have time to be 'bit-twiddling' on your phone then why did you bother on unlocking the boot loader and flashing a custom firmware?
Personally I haven't tried pure nexus, but it is very possible that 5 months ago pure nexus had the same bugs as AOSP Extended. Since they are custom firmwares, they are susceptible to bugs, that's why mainteiners push out weekly or monthly updates.
If you think that pure nexus or any other rom will deteriorate over time then you should probably restore the stock firmware of whatever device you are using, well... That of you have time, if not than don't blame maintainers remember they are not being paid for anything.
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Cobvetsely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Quantumstate said:
I don't have time to be bit-twiddling because I have actual work to do. But I want the extra features in custom firmware. Is that unusual? Is that not why most of us do this?
It doesn't matter whether PureNexus had the same bugs 5 months ago. I am using it now. In the real world one can not disprove a negative. Susceptible to bugs? Like the frickin' phone not ringing? And it forgetting basic settings? That should never, never happen. Again, these are mission-critical functions of a *phone*.
The maintainers are doing it for fun and recognition. But those maintainers who lazily emit schlock and dreck should be outed. That is not been happening, and it is time is does, for the protection of users.
Click to expand...
Click to collapse
I'm not making this statement because of my obvious bias of being employed by Motorola Mobility. But nobody knows better how to create ROMs for Motorola devices better than Motorola. I totally understand your points and agree with your logic on many of the shoddy custom ROMs put out for Moto devices. Conversely, however, I have to give much deserved credit to some of the XDA pioneer developers who have a passion for both Android and our beloved Motorola devices. @lost101 stands out, as well as @superR, @squid2, @Sands207, and the great @Buzbee2 just to name a modicum of these dedicated individuals.
If all else fails your expectations, go with a pure stock build, with root, busybox, debloating, with the custom ROM type flexibilities and customizations provided by deodexing, Xposed Framework mods & tweaks, etc, etc. You don't necessarily need a custom build to enjoy the perks and customizations of your Android OS, Grab yourself a stock build of your choosing and mold it like a piece of clay, and be your own architect. As a brilliant attorney once stated, "at the end of the day, my client is ultimately the captain of his own ship."
I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another (hidden) unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly. Doesn't realize how silly he looks.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.
Quantumstate said:
I am with you on Motorola, MotoJunkie01. No one else makes water-resistant phones, and is that not just a basic common-sense feature for something we carry with us?
But few seem to have common sense.
I've owned Motorola phones since cellphones began. I experimented with HTC, Nokia, and Samsung, but over time each one gave me reason to distrust the brand. Always came back to Moto.
I was afraid that Motorola had discarded the water-resistant feature, but the new X4 is at least IP64, so that will be my next phone. There are no custom firmwares for it yet but I'll make a note of the devs you cite. I do enterprise infosec, and rigor and quality are vital -- given my job and my nature it's why I'm so perturbed with these lackadaisical devs who learn only enough to knock something together and don't have enough sense to fix it. It's like spreading pollution...
I wish Whirleyes would bring his amazing multiboot feature -- no software enhancement comes close to being as useful and important to me, but impetuous people here pissed him off. There is some kind of multiboot available now, but it is not compatible with the XT1540.
For hardware features I rank waterproof first, large battery second, and dual SIM third. I've got to research whether the Asian Moto X4 will work in the US on Credo Mobile. (Verizon)
For software, security is of course number 1. I'd want to configure my phone like the Blackphone2, except with a hidden interface. We may soon be compelled to unlock our phones at borders and by police (which no matter what the Supreme Court says, is unConstitutional), so I'd like to unlock my phone, but have another unlock for another side of it; another phone or at least storage place, with the two sides completely secure from one another and distinct.
The supposed "Crypto" rom here is nothing of the sort. He's just using a gee-whiz name, amusingly.
I've left my phone out overnight in the rain at least twice, and what a relief it is to have this protection.
And true, stock firmware can be relied on, although I wish it had some of the nice features of customs. And I wish it got security updates over time -- that's a key reason I move to the next releases of Android.
Click to expand...
Click to collapse
Friend we share similar views and sentiments on this subject. We also seem to share in the philosophy that The Due Process Clause, Equal Protection of the Law, and safeguards against unreasonable searches and seizures have essentially all been trampled through the mud when it comes to our privacy and expectations to privacy with respect to our smartphones. Law enforcement having the authority to compel a man (or woman) to unlock their device without constitutional safeguardsl, is synonymous of the police being permitted to kick down the door to a man's house upon a "whim" or a "hunch". Or a cop conducting a traffic stop and subsequent warrantless search of the driver's person and vehicle merely because the cop feels like it. I take great pride in knowing with 100% certainty that any law enforcement who attempts to track or trace my mobile IP, or tries to monitor anything about incoming or outbound data packets on any of my devices is chasing Casper the Ghost. But, anymore I can't be so certain about John Q Law's legal authorization (or ability) to stick his long snout into my device's internal storage. I'm working the final kinks out of a simple process that will completely wipe and heavily encrypt the wiped storage with multiple layers of random binary (with the morbidly numerous anticipation that they actually can and will spend countless man hours and resources on decrypting utterly blank and random blocks of binary jibberish). All with a self determined series of keyfob button presses.
Yeah I know I'm ranting and perhaps being a bit overzealous. But, just like you said, regardless of state or federal appellate court adjudications giving authorities such authorizations, such decisions run afoul of a handful of the most rudimentary tenets of constitutional safeguards.
Word.
Most have given up and acquiesced. But not me. Never. I use Tor to get here, and just about everywhere else. Because I know what can be done.
Most will say that their words are not important enough and so they don't worry. But they do not know that what is Ok today, may not be tomorrow. I used to be in intelligence, and most here would not believe what can happen (and has happened in other nations).
BTW, there is an excellent TV series called The Americans, which I think is as good as the old Mission Impossible series (which came way before Tom Cruise). Although it can never compete with the old Secret Agent ('Danger Man') series, and the John LeCarre series', it is a high-grade and carefully-wrought storyline.
I agree with you that seems no ROM is stable; In fact if your phone is important for you as production device, I would suggest you stick with stock ROM or keep testing until a ROM which works for you and stay there! New version introduce new bug, that's the usual case on Software side, there is no way to avoid.
If you are so sensitive to bugs then stick onto stock rom instead of blaming the developers. Your fault that you can't keep meddling with your device. If you want a totally bugles device then you try to develop a rom by yourself then you will understand what it is to be a developer
MotoJunkie01 said:
Latest Stock Android 6.0.1 with @squid2 r20 kernel works flawlessly on my Moto G3 (xt1548). Two consecutive months of use and not a single bug found.
Click to expand...
Click to collapse
Better than my XT1540, rooted, no other mods except modified host file for ad removal, stock kernel. I have an average 1 bug report a week.