Related
So I just recently rooted my phone and settled on the Protekk CM7 ROM. It is awesome in almost every way. Yesterday I used the Google Navigation app for the first time since I did all this and the gps was REALLY bad. It was jumping all over the place, telling me that I was in a place that I wasn't and then it would be right. I was on the freeway and it was fine for a few minutes, then it started wigging out and showing me on a road next to the freeway and telling me to take these turns to then get on the freeway.
I tried a more recent build, I think it was #16, and the battery drain was terrible with that one for some reason. I could seriously sit there and watch the battery % drop a digit like every minute that I checked it.
Any ideas?
I have the same situation on my Dinc! I'm using the 3-20 nightly currently.
The CM7 nightlies are experimental and it says right in the OP that from time to time certain functions will break then may be fixed again in the next version. As the nightlies are on version 29 now I would suggest upgrading to it and see if it fixes your problems. This goes for the OP as well as GPS is usually a kernel issue and that may fix it, not sure what modifications Protekk is making to his version of the nightlies if any but maybe he played around with a different kernel. You both should be able to flash it over your current ROM with only having to do a dalvik cache wipe, not a full wipe. I just upgraded to version 29 last night from CM7 RC2 without any problems (only did a dalvik cache wipe) and my GPS works fine.
kzoodroid said:
The CM7 nightlies are experimental and it says right in the OP that from time to time certain functions will break then may be fixed again in the next version. As the nightlies are on version 29 now I would suggest upgrading to it and see if it fixes your problems. This goes for the OP as well as GPS is usually a kernel issue and that may fix it, not sure what modifications Protekk is making to his version of the nightlies if any but maybe he played around with a different kernel. You both should be able to flash it over your current ROM with only having to do a dalvik cache wipe, not a full wipe. I just upgraded to version 29 last night from CM7 RC2 without any problems (only did a dalvik cache wipe) and my GPS works fine.
Click to expand...
Click to collapse
Yeah dude, I know that. I would have posted right in Protekk's thread, but there is this dumb rule here that you have to have 10 posts outside of the development forums before you can post into the dev forums. I don't get it myself, but whatev, not my site. So I did the next logical thing and post in the Q&A thread. I wasn't complaining, I was just asking. Last night I loaded up the latest nightly, and also IncrediKernel's latest. I'll have to see what's up with the GPS with these.
badogg said:
Yeah dude, I know that. I would have posted right in Protekk's thread, but there is this dumb rule here that you have to have 10 posts outside of the development forums before you can post into the dev forums. I don't get it myself, but whatev, not my site. So I did the next logical thing and post in the Q&A thread. I wasn't complaining, I was just asking. Last night I loaded up the latest nightly, and also IncrediKernel's latest. I'll have to see what's up with the GPS with these.
Click to expand...
Click to collapse
I never said nor implied that you were complaining just pointing out how the nightlies work in case you and the other poster had missed reading it. GPS problems have been reported with various nightlies since they started and I'm sure will happen again. Most people just revert back to a known version that worked or wait for the next one to come out and hopefully its fixed again.
The rule about posting in the dev section is to keep people from starting new threads that don't belong there. It was getting out of hand for a while and every other thread there was someone asking the same question as to how do I root my phone, or I screwed up rooting my phone or some other post that had been answered many times before.
Got it. Sorry if I seemed defensive, I didn't mean it as such. I guess I spend too much time on forums that I get a little twitchy at times.
CM7.0.2.1....... sucks battery and app. Problems after update.... ??
Crans said:
CM7.0.2.1....... sucks battery and app. Problems after update.... ??
Click to expand...
Click to collapse
naw... running smooth as ever for me. maybe something went wrong with your install
Have you tried a different kernel? Make sure your screen brightness isn't up all the way also, big battery killer.
CM7 nightly
I dont think this belongs in development. try Q/A they might be able to help you out.
I am also having issues mainly with you tube all the videos are jittery as hell and tried a different rom and issue was gone.
Sent from my ADR6300 using XDA App
The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
You could check the threads for CM7 and see if it its a "development issue"...searching works from time to time
CM7 nightly
Just don't know why 7.0.2 to 7.0.2.1 would be so drastic.... understand nightlys but not stable
Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Opening a new thread about a ROM rather than posting in that ROM's thread, running it in a non standard configuration, AND having an attitude when someone points out a Q doesn't belong in dev? Yeah, I see no problem at all. /sarcasm
You guys are getting sarcasm and straight forward confused thanks for any input that actually pertained to my question... to others.... think before you speak or ask ... done... Please close this thread ASAP
Crans said:
The difference. between 7.0.2 and 7.0.2.1 has been like night and day .....my batt. After taking off the charger today went from 100 to 95 in less that 10 seconds and I'm not getting fc's. But my display apps try and open than dissapear giving me no access...... I am running dual boot sooooo... that may be the cause but 7.0.2 worked great when I updated to it..... just didn't know if I was the only one
Click to expand...
Click to collapse
um, the only thing they fixed from .2 to .2.1 was the camera.
To many people here post issues that aren't from a clean wipe.
No issues, move along.
Thank you for your reply..... as stated before...done
Remove this Thread
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.
morrisdan said:
Please remove this thread. We don't need the negativity. There are too many people spending they're own time to make CM7 what it is.
Click to expand...
Click to collapse
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
masully1984 said:
Have you tried a different kernel?
Click to expand...
Click to collapse
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).
I love using CM7 ... bugs or not please save your ignorance.morrisdan
Crans said:
If its a well known major problem with development of a rom that is supposed to be stable than yes if no than Q/A with people whom aren't even rooted....... hmmmmm hard choice,I know it was for me....... please move this post if it's not in the right section...
Click to expand...
Click to collapse
Just because someone posts something in Q&A doesn't mean they aren't rooted. Your attitude sucks man. My personal opinion would be to reflash and wipe I have been running the latest stable release for as long as its been out and been updating to the latest version asap and have had zero problems other than those cause by user error. Perhaps you did something. Gotta release 9/10 problems are user generated.
skyblaster said:
Why, so people can go on downloading a supposed "stable" release only to find out it wasn't so "stable" to begin with?
I LOVE the CM crew and all they do for the scene, but I had a very terrible experience with 7.0.0 on the DINC. First it was jittery video (which I lived with for over a week) and then all my installed apps just suddenly quit working.
A "stable" ROM should never require an end user to try a different kernel.
Anyway, I ended up back on OMGB and couldn't be happier. The only FC I can find is due to installed software (Astro SMB Module).
Click to expand...
Click to collapse
Dude you should always try different kernals with roms. You must be new. It is stable I've had zero problems. As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.
cstrife999 said:
Dude you should always try different kernals with roms. You must be new.
Click to expand...
Click to collapse
Don't let my post count fool you. I've been around since the beginning with the G1. Final, Stable, these words suggest newbie usage. Final builds should come with a final kernel. Unless you're a dev, tester, or need something specific for a certain application then you shouldn't need to kernel hack.
cstrife999 said:
As stated previously 9/10s of problems are user error and with the ignorance you are displaying I'm gonna say you did something. Just a tip when you wipe you should multiple times becayse 3.X wipes like a dirty person.
Click to expand...
Click to collapse
I understand how memory wipes work, so I don't believe the multiple wipe requirement. However, if it is an issue with ClockworkMod 3.x then I do apologize for any nay say here against CM. However, that doesn't really explain why 7.0.2 and 7.0.2.1 came out so soon after 7.0.0, and I wasn't the only one with video troubles in 7.0.0.
/deleted
10char
So strangely at 11:45pm last night my phone went absolutely nutty... Can't figure it out but all of my apps keep crashing. Gmail, Maps, etc.
I haven't updated CM7 since it came out months ago so I need a bit of help upgrading all of what needs to be done... I figure this is a good reason to bring things up to speed.
Ideally I'd like to get 7.1 on here. I also can't remember all of what I need to download to do this process. Not as brilliant as the rest of you!
Can anyone give me (or point me in the direction of) some step by step instructions of what I need to do? Real layman's terms...
Currently:
Android 2.3.3
Model number ADR6300
Kernel 2.6.37.6-incredikernel-gb-04192011+
CyanogenMod 7.0.0-Inc
Build Number GRI40
Help me get this puppy up and running!
Thanks all and Happy New Year!!!
Go to cyanogenmod.com and click on devices. Scroll down until you see the HTC Droid Incredible and click on it. Click on the wiki link. Everything you need to know will be there. Use the via clockworkmod recovery method.
Get 7.1 stable, the gapps for it, incredikernel ext4 and the adrenaline shot. That's should be good.
-My life is a shooting range, people never change-
I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then constant FC's and freezes). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to reinstall again.
Some folks have said that the problem never goes away after a fresh install... I don't know about that. My phone screwed up, I searched and found many others with the problem, tried a quick fix, then abandoned CM 7.x stable immediately.
iowabeakster said:
I hate bad mouthing projects that people have worked so hard on. But, CM 7.x stable is NOT stable on the Dinc.
If you want to keep using CM 7.x (stable)...
expect this problem to keep happening. If you are a CM 7.x (stable) user and it hasn't happened to you yet, great. But, don't be surprised when it does. Yeah, check out the CM forum for 7.x stable on the Dinc... you will find many others who have the same problem (works great for some amount of time, and then is completely fubar'd). I also just ran across another person in the Incredible discussion forum who had the same thing a few days ago. It happened to me after about a week on installing CM 7.1 stable, so I changed to Inc Deck (gingerbread) 1.3 stable. You can reinstall CM and it and it will work for some amount of time (completely unpredictable how long it will work). But someday, sometime...whammo... you will have useless phone, and you will need to start over again.
Click to expand...
Click to collapse
Hmmm interesting. Out of all the roms I have tried for the droid Incredible, CM7 has by far been the most stable. Never had any trouble with it and I have, at times, used it for months before trying a different rom.
Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.
CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.
Thanks for this tidbit... I haven't had the issue, nor do i plan on getting it.. I'm pretty adamant about keeping a certain percentage of free space on all partitions, so hopefully everything runs smooth.
Thanks again for the heads up.
tiny4579 said:
CM7 nightlies have actually been my daily driver for most of my time having service on the Incredible.
I've heard the force close issues have been due to /data/data filling up. If you keep 20MB free or more you should be fine. Root explorer is one app that will list how much free is on /data/data and a recommended app for any rooted phone. the CM7 nigthly thread has a few suggestions on how to free space. Search not enough space on the nightlies thread.
Edit: I see you posted about the /data/data partition already.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
iowabeakster said:
Oh I know! It seems to catch everyone off guard because it works fine for X number of weeks or months and then... FC and freeze hell!
A lot of the folks found it happened shortly after upgrading from 7.0 to 7.1. But just in the last couple of days I have run across a couple of people that were still using 7.0 and now seem to have the issue.
The guy at CM who does most everything for the Dinc seems to think it was related to a full /data/data partition. I reinstalled fresh and did the ext4 "no data limit" mod, after first having the issue, and it made no difference at all. So, I gave up on CM the same day.
Click to expand...
Click to collapse
Don't let this Guy talk you out of cm7. I've been running the same kang for almost a month. And I ran the stable from October 9th til December 19th. It was always my fallback. I've never had issues, and as big as the nightlies/stable threads are. Why would you let one sway you?
-My life is a shooting range, people never change-
Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.
Your sarcasm is too advanced, my friend... ;] lol
iowabeakster said:
Correct, don't let one guy do that.
Certainly don't allow your own haywire experience affect your judgment.
And certainly don't allow these dozens of folks who posted on the CM incredible forum to have any influence on your decision.
http://forum.cyanogenmod.com/topic/32784-consistent-freezingfc-after-update-to-71/
Only listen to one guy who is running some OTHER build, that everything is perfect.
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Use Pons 7.2 kang. I've been since he started and all is well. I was running the nightlies before that and have never had any issues.
Ahhhhhhh
Sent from my HTC Incredible S
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.