Related
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
does anyone know, or have a reason, or encounted in a problem with CM 10.1 cuz i recently installed CM 10.1 stable on my ATT S3 and it keeps restarting itself after 20/30 minutes tops, maybe longer but once in a while it randomly restarts itself
installed everything perfectly, no reason to be acting crazy since its from CYANOGENMOD TEAM but ROMS are not perfect or as good as STOCK ROMS (that come pre-installed on your device)
any issues, bugs, any kind of thing you have noticed with cm 10.1 yu can post it here
new upcoming features, fixes, what should be there or shouldnt be there, whats missing everything
HELPING EACH OTHER SOLVE SIMPLE/SERIOUS with CM 10.1 and above ISSUES
am currently running Synergy ROM 4.1.2 Stock rom with ZIGGY KERNEL (clocked at 1.3 Ghz) and its pretty sweet, stable, good battery, perfomance is top notch for a stock based rom that come with all samsung boatload
SO DUMP ALL THE PROBLEMS/SOLUTIONS IN THIS NEW THREAD FOR CM 10.1 AND ABOVE - ATT S3 I747
ANYTHING YU THINK IS COOL/AWSOME ABUT CM 10.1 ON YOUR AWSOME S3 GET IT HERE
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
winosxbuntu said:
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
Click to expand...
Click to collapse
First and foremost, no OS or software, including android, is perfect. Secondly starting a new thread does not mean it will not get "cluttered" either. The ROM thread for CM is not as bad as you make it out to be. The idea is that the newest material covers the most recent nightlies. It is not that difficult to go to the end and work backwards. In regards to you random reboots, look on JIRA as it exists for this very reason. Take a logcat and report on JIRA if not already covered. JIRA gives you all the bugs reported and their current status towards a fix. This is a wasted thread for this very reason.
As far as ROMs being different...that is the point. Each developer(s) put their own spin on it. That is what makes these development threads so great. You can look for a ROM that you like best. Some ROMs are more universal (but you still need your device specific version), such as CM, while others are device specific.
And phones are not created equal. They may look the same, have the same hardware specs, and all else seemingly equal, but slight manufacturing imperfections make them different. Two people can have the exact same phone from the same carrier, manufactured on the same day, but due to some ever so slight differences from imperfections, ROMs will work differently on each. For instance, in your case CM reboots randomly. For others, such as myself, this is no longer an issue. However, it is possible that another ROM will work great on your phone but not on mine.
While you say CM is not perfect like the stock rom, the stock rom is not perfect either. I have AT&T and the stock rom has several issues. The lockscreen securities can be bypassed, the alarm likes to not work at random times (software bug), and every now and then I get a battery plummet after a phone call when the phone switches between 4G and 4G LTE. Others may or may not have these issues but they seem to be rather common (the security bypass affects all S3 phones that were on 4.1.1 that I am aware of). For this reason I stick to custom roms because I do not have these problems which I personally view as severe for me (Aside from protecting my data and enjoying battery life, I rely on my phone as an alarm clock). Now that 4.2.2 has come as far as it has, it is stable enough that I can use it as a daily driver. I knowingly accept any bugs that are there because typically the ones that exist do not have a large affect on me, if at all, unlike the stock rom.
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Sarmiento_Luise said:
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Click to expand...
Click to collapse
As of now, Geodev is the only one in development. If you're trying to get your post count up, go to the XDA General section and post in the new members forum or the off topic lounge.
postcount++
imho that geodev thing sounds shady at best.
If you would decide to port a custom rom to a new device, would you really start by porting KitKat if the device
currently only runs jellybean? Wouldn't it be easier to use the stock kernel for now to get cm10 running
and then wait paitiently until htc releases the kernel src to make it a full unofficial cm10 build.
Instead this sounds more like taking the existing source of a hopefully hardware compatible build
and bending it until it brea.. ehm works.
I may be biased, but if you plan to make any kind of release you usually don't go and announce it to the world.
This only encourages the rather impatient endusers to come up with many variations of the same old:
"i need my rls now!", "I am entitled to a release because I found this thread","GIMME RLS!!!11oneeleven"
posts that will just annoy the crap out of every dev I've ever met. Also there is absolutely no point in asking for
beta testers before you even have a working build ready.
Combine that with the recent e-begging post and draw your own conclusions.
DroidTwe4kz said:
[...] I can't continue developing until someone gift me new computer (or motherboard only). [...]
Click to expand...
Click to collapse
In any case, for the time being it might be a good idea to check if there are some services you could deactivate
in order to get a little bit more speed out of your phone. I personally have no problems with lags, but maybe
it's because I don't expect the phone to run every app ever made at the same time since it has only 512MB RAM.
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
I have tried all possible custom ROM's for my tomato but none of them are fully stable. Most of them has there own issues. Require a Custom ROM which is at least fully stable and usable. Below is the list of all common issues with lollipop custom ROM's for Yureka .. :-
1. (major issue) capacitive touch buttons can't be disabled completely nd so On-screen nav bar can't be used at its best.
2. Battery drain is another issue with all the custom ROM's..
3. Gapps stopping.. FC occurring during reboots nd sometimes even after reboots.. AOSP crashing...!
4. Camera app is not upto mark in any of available custom ROM's.. Worse performer than stock lollipop..
5. ROM's must provide us with some powerful custom kernel's to give us full control on hardware.. No rom has provided a great kernel which can be used for tweaking...
6. Status bar and notification panel getting f****d up with customization in most of the ROM's..
7. (Most Important in my case) Colors are really dull in most of the ROM's.. Color production is very poor and can be felt while playing games..
If all these issues can be resolved by any ROM developer, for me it will be the perfect ROM... Waiting eagerly for it..
All problems mentioned above are based on the ROM's reviewed by me which are:-
1 SOKP 5.1.1
2 BlissPop rom for tomato
3 Resurrection 5.1
(?I suggest developers to add viper4android as equaliser app and cameraNext modded app as default camera app) ? both are best in their category
Flashed from my Yureka
Off-Topic...This is a development section....Ur querries and requests whether related to development or not should have been posted in general section...
It is related to development
Flashed from my Yureka
First of all the topic of this thread is just wrong,as you require you build one stable for you(as if its easy as installing an apk),
second the issue you mentioned here are already posted by many users in the specific ROM threads,
Third thing is that feature requests should be made in general section or in specific ROM threads,
fourth you don't pay them to demand or suggest them,
fifth just wait patiently,posts and unwanted threads like this will irritate some developers so that you may lose some ROMs !!
Note: I request mod to move this thread to its specific section.
Sent from my LG-D855 using XDA Free mobile app
Why don't you build yourself a custom ROM and fix all your ISSUES yourself? the developers do their best, and we should do our part and not complain.
Of course they do... It was meant to be a request nd nothing to boil the things off...All bugs mentioned above were to help developers identify all the issues nd to avoid them as all these are common one's.....!!
And I don't think any developer will see this post as an offence as it is not meant to be.. Developers are no God and they too need to be told about what they need to avoid..
Also this post has been posted in development section as it covers common issues related to ROM's which are posted here...!!
Flashed from my Yureka
The latest rr rom seems to be stable enough to be used as a daily driver. Better than stock cm12 anyways
Sent from my AO5510 using XDA Free mobile app
While I understand that you did not mean to rile people up with your post, it comes off as a little bit demanding. Devs know what they have to work on, feedback on the custom ROM posts is there for that. They need not be constantly reminded of it by seeing it on the front page. If everyone started demanding things by making posts about it on the forum nothing would get addressed. Developing a ROM is not a simple task it requires a lot of knowledge. Developers know what bugs their ROMs have and they try their best to fix them. Also I agree with people above that this should not be in the development section its a general thread.
I have RR in My primary phone Nexus 4 which is pretty stable. For Yureka, I'll probably root and go with RR soon. If the demand is for most stability, go with Stock. But till my usage on CM12 Lollipop, it's not that stable enough and there are rarely bugs too (These are complained many times in YU Forums). Hence it might be pretty obvious reason for that instability of Custom ROMs. One solution I'm wishing for now. How to install Xposed GravityBox module to Yureka phone? Since it comes with CM12 which violates the rule of install in Non-AOSP, is there AOSP version available for this phone? If not, can a AOSP custom ROM be built to 1+1/Yureka phones?
This thread should be closed asap.
Be happy with whatever you're probided by the devs. They are human beings (just like us) and do these works in their free time. Bug fixes take time, they aren't fixed with a click of a button. All 5.1.1 roms (for dual sim devices) had the systemui/settings fc bug. But these bugs have been solved now. See, I told you bug fixes need time. You flash roms at your own risk, so you shouldn't demand things. Rather, just be humble in listing the bugs and wait for the dev of the respective rom to fix them. These are devs spending their leisure time in compiling roms fro your device while they could've been out enjoying with their friends. They don't even get paid for all this. So next time before you use the F word in a thread, think twice.
arvindgr said:
.... is there AOSP version available for this phone? If not, can a AOSP custom ROM be built....
Click to expand...
Click to collapse
here's something that promises much, i think. and the dev @percy_g2 seems to be well-respected.
In what way its related to development...Is posting ur querries a development??? Or giving suggestions to those who already know what to do and what not a development??...This is totally an off-topic...
Build a bug-free ROM and post it here or a kernel and post it here..and thats development btw...
Pinpointing errors and bugs is known as reporting btw...
Sent from my AO5510 using XDA Free mobile app
@Da_Gamer_pk
First before creating a thread, find the right need, right place, section etc.
there is clear impulisiveness and an impact created.
Please take care of the next one
Thanks for the understanding
sreeprajay
parasthakur37 said:
This thread should be closed asap.
Click to expand...
Click to collapse
why is that??
What even....
arvindgr said:
why is that??
Click to expand...
Click to collapse
Are you serious?
He's almost ordering the devs to build a stable rom, why?
If he's so keen why doesn't he himself build one?
All devs have already specified all the possible bugs on the particular rom threads so why should you post them separately in a new thread?
Imagine if everyone made new threads about the bugs? All threads would be about bugs only and nothing about development.
SO!
Think twice before posting. Post only relevant stuff. Read all the posts before posting. AND DON'T COMPARE DEVS' WORK and DON'T ORDER THEM, THEY DON'T GET PAID BY YOU!
I hope you and the OP understand my point and never commit a stupidity of this kind again.
wtf man we already have cm12.1 official (snapshot) and now we got cynogen os 12.1 that too stable !!