Related
I was just thinking looking through all these new roms or just roms in general and it hard to determine which one on many levels. I just thought of an idea we should have a known issues for each rom or atleast the newer ones. I think it will be easier for people to address the problem or atleast see all the known issues with that rom. I think this would help out the developers alot too. This will save me 78 pages of looking through to see known problems. So it will just be there within a few pages.
chicmagnet2k4 said:
I was just thinking looking through all these new roms or just roms in general and it hard to determine which one on many levels. I just thought of an idea we should have a known issues for each rom or atleast the newer ones. I think it will be easier for people to address the problem or atleast see all the known issues with that rom. I think this would help out the developers alot too. This will save me 78 pages of looking through to see known problems. So it will just be there within a few pages.
Click to expand...
Click to collapse
Most of the developers have a list of known issues and what is under development for the next revision at the beginning of their thread. There is no easy way to select a new ROM. I have narrowed my search for a Version 6.1 ROM to a couple of developers.
I also have been following the experiences of other users that have have a similar confirguration to mine. For example, same country and same service provider.
jws3 said:
Most of the developers have a list of known issues and what is under development for the next revision at the beginning of their thread. There is no easy way to select a new ROM. I have narrowed my search for a Version 6.1 ROM to a couple of developers.
I also have been following the experiences of other users that have have a similar confirguration to mine. For example, same country and same service provider.
Click to expand...
Click to collapse
I'm not meaning just known issues but people have alot of other minor or they dont know what to do issues ie battery drain sync keyboard or running application issues and when there hidden in between 56 pages its hard for people to see what some of the issues that might be problems with that certain rom or it harder for developers to have to go through 32 pages of stuff to find what they need to address or fix. It's just an idea maybe to implement with newer verison or newer roms.
chicmagnet2k4 said:
I'm not meaning just known issues but people have alot of other minor or they dont know what to do issues ie battery drain sync keyboard or running application issues and when there hidden in between 56 pages its hard for people to see what some of the issues that might be problems with that certain rom or it harder for developers to have to go through 32 pages of stuff to find what they need to address or fix. It's just an idea maybe to implement with newer verison or newer roms.
Click to expand...
Click to collapse
The developers here usually do a pretty good job in following their own ROM's thread so they know what trouble people are having. Incidentally, that's one of my benchmarks for a good ROM: a cook that watches his thread and responds to people in trouble.
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
larsuck said:
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
Click to expand...
Click to collapse
There is a lot of truth in what you say. ROMs on their own are usually ok; its the combination of software and install methods that leads to problems. The thing is no matter how hard you shout people always assume that its the ROM or the cook.
Case in point; I have been using Kin0kins ROMs for a little while now whilst I wait for Schaps to produce his killer ROM with the 21st century interface. K's roms are rock solid stable and fast and yet I had an instability problem after the last install.
Going through the painfull routine of "forensic investigation" of my install I discovered two things:
- I had inadvertently loaded up some software onto the SD card which had known instability problems if installed in this way. Once sorted, hey presto, one issue solved.
- 2nd issue was caused by a similar install but using software that was polled on a regular basis. Once the device went into hibernate mode it crashed, simply because the card could not wake up quickly enough to handle the software request.
Loading up old versions of software incompatible with WM6 is another popular one that tends to cause issues. Bottom line is there just is no substitute for rigour and research prior to software installs to ensure the good operation of a rom with the benefit of stability.
WB
larsuck said:
The developers here usually do a pretty good job in following their own ROM's thread so they know what trouble people are having. Incidentally, that's one of my benchmarks for a good ROM: a cook that watches his thread and responds to people in trouble.
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
Click to expand...
Click to collapse
That is somewhat true but isnt all of my arguement I am a new member here and felt overwhelm when trying to look for a nice stable fast rom to flash and I thought about what made it hard for me. Which was there are tons of un needed comments so its like you have to go through 77 pages trying to see what this rom is about. Its overwhelming and crazy, if my way isnt all the way complete or just a bit too much it would be great for someone to think of a way to make it easier for a newbie or just people in general.
I have been a long time Cell phone modder, and I have just gotten my first Android Phone, the HTC Evo 4G.
I have been reading androidforums.com and these forums for about a week now trying to get my head wrapped around things, but I still have some lingering questions.
I feel I have a good grip on how to get my phone rooted/nand unlocked, but its the what to do after that, which bothers me.
What I would like to accomplish:
More customized look and feel
Better battery life (without disabling half the features of the damn phone)
Free Wifi Hotspot
Removal of the pre-packaged crapware
Froyo
What I would not like to lose in the process:
Any of the phones functionality, including GPS/4G/Camera/Video/Bluetooth/etc.
Nice features that Sense has, such as Facebook contact syncing
Reliability or usability of the phone in general
As I have gotten older, my desire to mod has become less and less, and I get more tempted to just leave the phone alone and wait for OTA updates to come out, but when I just tried to do the wifi hotspot and learned I would have to pay an additional $30 on top of the $10 "premium data access" I made the decision to root. That being said, I don't want my phone to be something I am flashing every day. I want it to be as stable as possible so that I can get it all set up how I want without having to worry about re-flashing and losing all my data week after week to keep up with bugfixes and such.
What I don't understand is the differences between all the roms. The opinion at large seems to be that CM6 is the way to go, but it seems a lot of stuff is broken in CM6 atm, like 4G among other things.
Since this is my first android phone, I am already getting used to the Sense UI, but I have seen some other peoples home screens that just look amazing.
I guess what I am looking for is some advice, or a bit of a rundown (since I cant find all of this information in one place) about what is the best course of action to get from point A(stock phone) to point B(customized rooted phone which is "stable") over a path of least resistance.
Thanks in advance!
[also making this same post on androidforums.com]
You can accomplish everything you mentioned except froyo. If you do not want to lose any functionality then flashing a froyo rom is out of the question right now because they all have small issues. CM6 is a froyo rom.
The difference between roms is some are based on 2.2 (froyo) and others are based on 2.1 (stock for evo). Then they also differ in terms of what comes pre-installed, some remove all bloatware even sense and others do not, and then there are some in between. Any rom based on 2.1 will likely have everything working. I can tell you from experience that Damage Control and Backed Snack worked very well on my phone. The best thing to do is just try them out. Once your phone is rooted it is very easy to switch between roms.
Lastly the easiest way to achieve root is using simple root program which can be found here: http://forum.xda-developers.com/showthread.php?t=720565 (that link is assuming you have latest OTA update, if not search for simple root and you will find the one pre update)
try dc 3.2.3 very stable release(has all the features working; 4g, camera, ect) and has good battery life(don't need to disable half of your phones features), it also allows for a lot of customization(DCupdater allows you to download themes and flash them straight from your phone), and you can pick and choose what bloatware to remove using DConfig, a froyo release is suppose to come out sometime this weekend.
Another option for you is to root and then flash the latest rooted "stock" rom. then flash the latest radio and wimax. then you can use a file manager to remove bloatware. I use "root explorer" from the market. be careful what you remove as removing some things can cause problems. I am currently running this on one of my evo's with no problems everything works and battery life will get me through a day. if you need more info as removing the bloatware feel free to pm me and ill help with what i can. I'm sure using the stock rom will be sufficient for you. On the phone i have running i have all features enabled and am pushing my pop3 accounts through gmail, 4g wifitether, all works just fine.
Does any one else think that Google should be spending a lot more time here on xda and learning from the devs?
Just little features like being able to hide and unhide the nav bar, and edit the buttons of the nav bar...
Getting the smoothness of the stock launcher sorted once and for all that some custom rooms have managed...
The few extra targets on the lock screen.
You get the idea. Just little tweaks that are missing from stock that I feel should have been added from the start.
A company that large with that much resource should surely b thinking of these things before Joe bloggs comes along and adds it for them.
Sent from my Galaxy Nexus using XDA
zolah said:
Does any one else think that Google should be spending a lot more time here on xda and learning from the devs?
Just little features like being able to hide and unhide the nav bar, and edit the buttons of the nav bar...
Getting the smoothness of the stock launcher sorted once and for all that some custom rooms have managed...
The few extra targets on the lock screen.
You get the idea. Just little tweaks that are missing from stock that I feel should have been added from the start.
A company that large with that much resource should surely b thinking of these things before Joe bloggs comes along and adds it for them.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If I recall correctly some of the new features in ICS from the Cynogenmod team (the only one that I can recall is the swipe away notification menu list).
But yea I agree, those little tweaks that you mentioned would be sweet to have in future releases of android...and who knows maybe they are paying attention and in the next (major) update of theirs we might get new features.
Yes/No.
I'm sure some Google employees might check sites like this from time to time, but more often than not they're aware of bugs before most of the XDA population notices them. Legitimate issues will be reported to their bug tracker quickly I'm sure.
People may get impatient waiting for a fix, thinking, the Big G is oblivious, but the majority of the time they're a few steps ahead of most users here and a fix has been in the pipe for a while. I'm sure it's someone's, or someTHING's job, to harvest pertinent info; Google is in the information biz after all. I doubt any Google (or AOSP) presence would ever be officially declared here; I can't picture that going well.
There is a gerrit for code submissions. If they are not submitted, good luck in seeing them considered for implementation.
However, devs like us tend to introduce problems as well. Unless it can fit into the master branch for all supported AOSP devices and appears to not cause issues with other items, it will be immediately thrown out.
Ever read rom threads? At least half the posts stem from problems that were created from tampering with code/adding features.
..and I don't want to hear "insert rom" is bugless, because it is not true for any rom.
adrynalyne said:
There is a gerrit for code submissions. If they are not submitted, good luck in seeing them considered for implementation.
However, devs like us tend to introduce problems as well. Unless it can fit into the master branch for all supported AOSP devices and appears to not cause issues with other items, it will not be immediately thrown out.
Ever read rom threads? At least half the posts stem from problems that were created from tampering with code/adding features.
..and I don't want to hear "insert rom" is bugless, because it is not true for any rom.
Click to expand...
Click to collapse
Good point for sure. I definitely do not want my phone to ship with the instability custom ROM lol.
And people won't be satisfied either way. They're gonna ROM their phone anyways, not all of these things need to be included in the shipping software.
Um...Google knows man. Come on, they are the largest search engine in the world. They know what CM team has added, they know what people dislike about their products, they know EVERYTHING.
I'm sure they are learning from the devs, also have to realize a lot of the things CM adds and the fact Google doesn't include a lot of the stuff is good for the mass, a lot of my friends have a Android phones.
I always root their phones and add toggles and the extra features and they don't even realize or use them because they don't care, but I'm sure they know what people do want and what people don't based on their search histories.
I thought about this the other day...
If any of these ROMs and Kernels were actually significantly better without compromising stability then the Google devs would be out of a job pretty quickly.
I think the main advantages of custom ROMs and kernels are:
- customization above and beyond standard - but Google wants too keep a uniform ICS theme.. and adding too much detracts from this... not to mention over complicating menus and settings
- performance from overclocking - again something Google doesn't want to do for stability and hardware reasons
- getting new releases and sources before OTA updates - for the phones that are Samsung controlled which have to wait ages for them.. and you can flash a stock image for this anyway.
So custom ROMs don't really add that much that Google would want in its stock builds
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
o-k said:
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Click to expand...
Click to collapse
Xda is just an outlet where people choose to post roms.
To check on the latest status of roms, you need to open the threads and read the OP. You also need to spend at least ten minutes reading each thread, That will tell you how stable each rom is and what kind of results people are having.
Sent from my SGH-T999 using xda premium
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
shrimants said:
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
Click to expand...
Click to collapse
Actually that would be a great idea. It would help out the entire community.
Right now the way things exist, you pretty much have to read through an entire rom thread to determine the benefits/bugs of any given rom.
You could, for example, start a list for any particular rom.. read the entire thread, then make your own thread detailing current known bugs and post it in the same forum. Then the OP of the rom thread could post your link in the first post making it easy for everyone to find.
That would serve two purposes - you would learn the information you're seeking and also become an instantly appreciated contributor to the site.
Sent from my SGH-T999 using xda premium
I'm surprised the rom developers dont already have a system in place, though. The scope of the projects are presumably gargantuan collaborative works. i kind of assumed that they must have some sort of a bug tracking thing that they use between them. That bug tracking thing is what i've been venturing to find. There are a ton of user-specific bugs that I have no problem digging through the forums and figuring out myself, but what i'd love to see with roms is a list of "this is what we know isnt working yet. dont talk to us about this. we are working on it." or at the very least, "when you flash this rom, if you would like to help, run this command and upload the output HERE so we can fix some bugs we know about".
I'm coming from a linux world and it is very disconcerting to me to flash a rom, encounter a bug/error, and not be able to look at any sort of an error message or do anything to fix the problem except reboot/wipe/reflash and hope for the best. thats a very windows-y mentality to the whole thing, and i feel like if we're running linux on the phones we should be able to get a bit more involved in fixing our own problems a bit better too.
I guess what i'm trying to say is, i'd like to help and i have no clue where to even begin. with archlinux theres a beginners guide but with these roms its more of a "watch this youtube video and follow this tutorial but god help you if anyone thinks you are complaining about what people are doing for you for FREE".
EDIT: I found CM10's issue tracker, but there isnt anything specific for the GS3 there. The flicker and picasa sync issues arent even mentioned. Obviously Paranoid Android and Kang will have the same bugs as CM10, but im assuming that they'll have their own bugs introduced after they add in their own features and such.
ok.
ingenious247 said:
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
Click to expand...
Click to collapse
thanks! will it be on the CM website or here?
o-k said:
thanks! will it be on the CM website or here?
Click to expand...
Click to collapse
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
i have a question
ingenious247 said:
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
Click to expand...
Click to collapse
i've downloaded the CWM pro and the TB pro. i was wondering what exact ROMS i can use. There is also the difficulty of understanding which rom is exactly which. Is there a way to view the Change log? i'm a super noob. i'm really sorry.
Changelogs won't do you much good.
I recommend flashing everything through CWM (make sure you have 6.0.1.2 Touch - in my signature if not). I wouldn't use ROM Manager at all. Having automated tools is great, but learning how to do it yourself is even better. Plus, if you break something, knowning what you are doing makes it easier to fix. Automated tools hurt more than they help.
As for roms, your options pretty much are as follows:
CyanogenMod: AOSP, the closest thing we have to the stock Google firmware.
AOKP: Pretty much CyanogenMod with some extra options. Nothing extraordinary about those extra options, just some nice things like center clock, swagger toggles, and unicorns.
MIUI: iPhone look for Android.
ParanoidAndroid: Scalable - for tablets (imo).
Then you have the neverending amount of customized stock (TouchWiz) roms.
They are all under constant development. If you want "stable", stay on your stock firmware. All of the roms listed above are stable enough to use as a daily driver. They all have threads in the two Dev forums. But if you don't know what to pick, use CyanogenMod.
I still think ROM Manager is a great tool, it's how I started years ago and I still managed to learn what I needed to over time flashing manually
Sent from my SGH-T999 using xda premium
Hello.
Well, I've been reading the threads of the ROMS with recent updates but to be frank there's some confusion and seriously too many pages to read and get the whole idea of the state of lollipop for our gramps nexus.
What I got from all the search and reading:
- Most roms have problems with offline charging and video recording (green lines?);
[Q] - Is this only happening in the Galaxy Nexus or is every device experiencing this (apart, obviously, from the officially supported ones)
- There's no f2fs support (or it is partially missing);
[Q] - Is f2fs really important performance wise? Has anyone tried to convert the roms and gave feedback? How is it?
I'm using kitkat with f2fs and I did notice some improvements over ext4 that's why I'm asking if it is the same with lollipop or it is now redundant.
Well, I know that those questions could be easily answered by testing all the roms and I am really wanting to do that but I'm using my nexus as my only phone and daily driver and I don't have a replacement phone in case something goes wrong so I can't really test and flash like crazy with roms that are still beta. That's why I'm asking this, I want to get into the lollipop world but I can only to that when lollipop reaches a somewhat stable state without major lags and no bugs (like kitkat has been since early last year).
I also would like to suggest a creation of a role thread for ROMs, making the threads graphically similar. That would help the developers and the users since the users would have the info they need in places they are used to search for, and developers wouldn't need to think of ways to put their info on, they could use the pre made model and just edit it with their info and links.
I would also suggest an update in the thread titles (rom ones) since there are some threads that don't have updated dates of "last build" or android version and it becomes confusing. I know that the developers have more important things to do but they don't need to do it themselves, I believe that there is many people here who can take care of that by editing it acording to the respective developer's standards or orders, I wouldn't mind to do it for example. And that could also incentivate the non developer guys to actively contribute to the forums organization.
Well, best regards and sorry if I was not so clear as I'm not used to long talk in english