I just upgraded from a Samsung Galaxy Nexus to a Samsung Galaxy S3, and just curious why everyone is still making/releasing 4.1.2 based ROMs when 4.2.2 has been available for so long?
Having come from running 4.2.2 on my Nexus, I was used to it, so the first think I did was unlock, root and get AOKP 4.2.2 on here. It runs flawlessly and everything works, so just hoping to get some insight on why all the ROMs in the dev section are old.
Thank you
Because many of the roms in development are based off Samsung's touchwiz software, which itself is based on 4.1.2 still. For 4.2.2 roms based off AOSP, most of them can be found in original development.
Basically the difference in versions is due to
Touchwiz: Google -> Samsung -> verizon -> devs
AOSP: Google -> devs
And aosp roms camcorder has extremely low volume recording so having kids I unfortunately cant use aosp even though I really want to.
crobs808 said:
Having come from running 4.2.2 on my Nexus, I was used to it, so the first think I did was unlock, root and get AOKP 4.2.2 on here. It runs flawlessly and everything works
Click to expand...
Click to collapse
Not quite everything works on an AOSP 4.2.x ROM. The radio interface layer (RIL) software for the GS3 has not been released by Samsung, the radio software used for all AOSP ROMs is reverse-engineered and is not quite as good as the original Samsung software. Your signal strength will not be quite as good using AOSP, though you may or may not notice a difference depending on coverage where you live.
More importantly, the GS3's world phone capabilities are not fully working with the AOSP RIL, I believe you can put a GSM SIM in the phone and make calls/texts, but not get data service. So if you travel internationally and want to use a local SIM to get data, you'll want to stick with a ROM based on the latest Samsung software, which unfortunately is still based on 4.1.2.
I'm happy to hear if either of those things have changed recently, it's been a little while since I looked into it. The only reason I don't use AOSP ROMs right now is because of the RIL issue, I need my phone to work as a phone first and foremost and that means going with something based on stock Samsung software. Of course, if neither of those things bother you, use what you like.
Hmm, weird. I have no call issues, and am getting 20MB/10MB on 4G LTE for data speeds, same as I did on my Nexus running AOKP build 6 (Android 4.2.2). Even the number of bars is the same, and more bars near my office than before with my Nexus (may be due to better radio hardware though). Also, I tested audio on video recording, and hear no difference in the videos I took on my Nexus. I also have kids, and the test I did was whispering to full talking from 5ft away - hear everything.
Weird. Guess I'll just keep using it since it's working for me.
crobs808 said:
Hmm, weird. I have no call issues, and am getting 20MB/10MB on 4G LTE for data speeds, same as I did on my Nexus running AOKP build 6 (Android 4.2.2). Even the number of bars is the same, and more bars near my office than before with my Nexus (may be due to better radio hardware though). Also, I tested audio on video recording, and hear no difference in the videos I took on my Nexus. I also have kids, and the test I did was whispering to full talking from 5ft away - hear everything.
Weird. Guess I'll just keep using it since it's working for me.
Click to expand...
Click to collapse
Different strokes for different folks. Personally I like many of the features of Touchwiz (The samsung camera app among others) but hate the way it looks so I use beans 4.1.2 builds. I was on AOSP 4.2.2 for a while but had isseus with the gps not tracking my runs properly and the low recording volume really got to me.
I've found that most AOSP builds leave me wanting. AOKP has never disappointed me; across devices.
If you had good reception with the Nexus...well, that speaks volumes. You're not anywhere near a fringe area. If you have great 4g, the Nexus worked great and AOSP roms on GS3 work great.
Where I live, there are a bunch of fringe areas and a lot of handshaking between 4g and 3g. The Nexus....I had to return it immediately. TERRIBLE reception. The GS3 with AOSP was a little better...but not much. When I'm sitting beside my wife with a rooted GS3 running Cleanrom, and I'm running CM10.1 and I have no signal and she has 4g...well, it gets frustrating. lol.
But I'm glad it's working for you...wish I could run 4.2.2...stupid RIL.
For those having GPS problems, have you done this?: http://forum.xda-developers.com/showthread.php?t=2201668
I much prefer the pure Google experience. when I had an HTC I hated Sense. When I had a Motorola I hated Motoblur. I didn't see any reason to learn to like TouchWiz
Also, I think I am blessed with my geographical area. I can travel 45 minutes from one side of my home city to the other and still have 4-5 bars on LTE.
Related
First off I apologize if there is another thread about this but all I found when searching was a general "best rom", and one related to battery life.
Personally I would like to know opinions on best rom for connectivity only. I live in a strong 4G area but whenever I am in my basement I get spotty connectivity, drop calls and such. I have been on the CM10 nightlies crack flashing since the boot-loader was unlocked. I love CM10 just wondering for basic call quality, does someone have a different rom preference for call quality?
Again mods I apologize if this is out there... but i couldn't find one for call quality. I realize this all depends on the baseband and such which Samsung is infamous for theirs. I just feel like even a slight better signal would make a big difference for me considering generally it's good connection.
Also my office is in my basement and I make a lot of calls and I'd prefer to keep it that way if possible.
Any thoughts are appreciated.
I'd actually like to know this as well. I recently switched from using an iphone to a Samsung Galaxy S3 and the difference with this phone is there are so many different roms available, I don't know which one is the best whereas with the iphone there is usually 1 main jailbreak and everything else is provided by cydia.
Like you said, this mainly is based on the radio and not on the Rom, but i agree there could be some minor differences. Your best bet would be to try a couple out and see how they work in your office. I personally am running jellywiz and my signal is rock sold and i work in low signal areas a lot.
Sent from my SCH-I535 using xda app-developers app
magus15 said:
I'd actually like to know this as well. I recently switched from using an iphone to a Samsung Galaxy S3 and the difference with this phone is there are so many different roms available, I don't know which one is the best whereas with the iphone there is usually 1 main jailbreak and everything else is provided by cydia.
Click to expand...
Click to collapse
If you search the forum there is actually a main thread for best rom overall which may help you more since it doesn't seem your only concern is call quality. Sorry I don't have the thread name but I think if you do a forum search for "best rom" you should be able to find that thread.
kintwofan said:
Like you said, this mainly is based on the radio and not on the Rom, but i agree there could be some minor differences. Your best bet would be to try a couple out and see how they work in your office. I personally am running jellywiz and my signal is rock sold and i work in low signal areas a lot.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I actually planned on doing that and testing them out on my own, I was just hoping someone may have some tips on one they have used in areas such as a basement or a place they know they haven't always gotten good service but have found a rom that works great for them as far as call quality. Such as your example of jellywiz, I will certainly give that a try and see if I can hold a higher consistency for call quality. Thanks for your input!
There are definetly differences between ROMs relative to battery life... different versions of the same ROM can be quite different.
I've been using Jellywiz as my DD and it's been great. I really liked RLS4. I've updated to RLS5 this morning but my battery life has declined greatly. I've also gotten one reboot. I'm sure the dev will have it fixed in the next release (the Devs on the Jellywiz project are top notch).
I also liked Synergy quite a lot... It's not Jelly Bean, but the battery life was great and very stable!
The best thing you can do is try several different ones... Let the ROM settle for a good day or two before coming to any conclusions...
Good luck...
Dirty13ear said:
First off I apologize if there is another thread about this but all I found when searching was a general "best rom", and one related to battery life.
Personally I would like to know opinions on best rom for connectivity only. I live in a strong 4G area but whenever I am in my basement I get spotty connectivity, drop calls and such. I have been on the CM10 nightlies crack flashing since the boot-loader was unlocked. I love CM10 just wondering for basic call quality, does someone have a different rom preference for call quality?
Again mods I apologize if this is out there... but i couldn't find one for call quality. I realize this all depends on the baseband and such which Samsung is infamous for theirs. I just feel like even a slight better signal would make a big difference for me considering generally it's good connection.
Also my office is in my basement and I make a lot of calls and I'd prefer to keep it that way if possible.
Any thoughts are appreciated.
Click to expand...
Click to collapse
Without getting too granular, stock based roms have the best reception. Rom's where the RIL has had to be tweaked, such as CM, MIUI, JellyBean ports, and cross carrier ports are more likely to have radio issues.
Then, there are different radios you could flash. In my experience with many devices, changing radios has never had much of an impact on radio reception. Different radio versions generally fix bugs, and things like 3g/4g switching. For instance the latest stock radio for our device (VRLG7) fixes the "no SIM" bug. I am using that and it has worked great for me.
Generally though, I don't think actual reception (mostly dependent on hardware) should vary too much. Usually it's reliability that can vary. "Bars" aren't always an accurate indicator of reception either, signal strength in dBm is.
bfs673 said:
There are definetly differences between ROMs relative to battery life... different versions of the same ROM can be quite different.
I've been using Jellywiz as my DD and it's been great. I really liked RLS4. I've updated to RLS5 this morning but my battery life has declined greatly. I've also gotten one reboot. I'm sure the dev will have it fixed in the next release (the Devs on the Jellywiz project are top notch).
I also liked Synergy quite a lot... It's not Jelly Bean, but the battery life was great and very stable!
The best thing you can do is try several different ones... Let the ROM settle for a good day or two before coming to any conclusions...
Good luck...
Click to expand...
Click to collapse
Sorry... I got lost in an unrelated thought (battery life)....
The service side appears to be pretty sold from the ROMs that I've personally tried. Not sure you'll find a big difference here in real world performance.
CodefireX is getting me the best service I've ever had. Several other people in the thread seem to be experiencing the same thing.
Sent from my SCH-I535 using Tapatalk 2
no 4g since flashing
turbosrrgood said:
Without getting too granular, stock based roms have the best reception. Rom's where the RIL has had to be tweaked, such as CM, MIUI, JellyBean ports, and cross carrier ports are more likely to have radio issues.
Then, there are different radios you could flash. In my experience with many devices, changing radios has never had much of an impact on radio reception. Different radio versions generally fix bugs, and things like 3g/4g switching. For instance the latest stock radio for our device (VRLG7) fixes the "no SIM" bug. I am using that and it has worked great for me.
Generally though, I don't think actual reception (mostly dependent on hardware) should vary too much. Usually it's reliability that can vary. "Bars" aren't always an accurate indicator of reception either, signal strength in dBm is.
Click to expand...
Click to collapse
I have not seen the 4G indicator since flashing a week or more ago. I have tried aokp, cm10, and root66.
Not sure what to do. The phone works fine otherwise. All these are great but I would never have gone this route if I had any thought that wireless capabilities would be reduced. Any ideas on how to return to 4G would be greatly appreciated.
Out of all the 4.1 roms out there, JellyWiz's wifi/4G/3g is the most solid one. Very stable and good enough to be a DD.
Sent from my SCH-I585 using xda premium
There seems to be quite a few jelly bean roms right now, and without an official leak, I am sure each one has its ups and downs at this point.
I am coming from synergyrom, and want to give JB a try. Since theres is still "beta" I am not sure I wanna try that right away.
Which is the most stable at this point??
Definitely liquid smooth...I've tried others and always revert back to touch wiz stock based roms, and i despise touch wiz...liquid smooth jb is the best I've flashed
Sent from my SCH-I535 using Tapatalk 2
liquid smooth is awesome for aosp JB, but touchwiz there's not much thats super stable imo
thanks for the input so far!
Please note if there are known issues, that might help make decisions too.
Thanks all!!
I like codename. Super smooth, frickin' fast and barely believable battery life! Some apps don't stream audio over bluetooth and you have to enable a couple of Developer options to address screen flickering, but those are truthfully very minor annoyances you'll be happy to overlook when you get a taste of that ROM.
Seriously, try it. http://forum.xda-developers.com/showthread.php?t=1900479
I've tried both liquid and codename. They are both very very similar. I can't find cant difference in customization between the two.
Codename ran a little warm for me, not saying liquid runs cool but still.
The reason I jumped to liquid is because in codename (for me anyway) the 160 character MMS bug still persisted, it does not in liquid.
Sent from my SCH-I535 using xda app-developers app
duarian said:
I've tried both liquid and codename. They are both very very similar. I can't find cant difference in customization between the two.
Codename ran a little warm for me, not saying liquid runs cool but still.
The reason I jumped to liquid is because in codename (for me anyway) the 160 character MMS bug still persisted, it does not in liquid.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can respect that. Haven't tried liquid as the CNA ROM got posted around the time I got this phone. I've heard the 160 character error msg is a bit of a red herring, that the msgs actually do get sent but just say they didn't. Was that your experience or did they actually not get sent?
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
bc760 said:
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well said.
Sent from my SCH-I535 using Tapatalk 2
bc760 said:
One of the biggest issues with JB roms is if your not in a 4G area then be prepared for some non stop 3G data drops. Also I've noticed weaker signal strength in both service and wifi.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There is a fix for this now but just has not made it's way into all AOSP roms yet. There are in most of the newer AOKP builds right now.
The biggest issue still is the low volume when recording video's. This is an issue in all AOSP roms and has not been fixed yet. I know I also read a lot about speakerphone and in call volume problems but not sure to much about the actual issue.
This is why I am still sticking to an ICS TW Rom. I like knowing everything on my device just works.
The only major thing that keeps from moving to CM10, or Liquid Smooth is the lack of USB Audio. I leave my phone on my dock at work and stream Pandora through the dock's usb audio. I've been using SynergyROM for awhile now, and will probably stick with it until the USB Audio issue is fixed.
AOKP's new build has been great for me. No real issues to report yet...been on it since 3 came out a week or so ago?
i haven't been too impressed jb at all tbh.
Well there's two routes you can go to get your JellyBean fix, and that's either AOSP or TouchWiz.
Touchwiz: You've got two choices.
- You could go with Synergy JB 0.2 beta which is based off the AT&T leaked JB touchwiz build. I personally have not ran it so i can't comment on how well it works, but i use synergy as my touchwiz choice of roms, and was never disappointed by there work, so i'm sure the JB build is working great.
- There is also Jellywiz which is made by Incubus, he's been basing his off the latest leaks, and has a few builds out. One of them is a custom build which just has a few theme changes, and a few other things added in/changed. There's a lot of praise in that thread for his rom, the only bug i had when trying it was that i could not get voice and data to work at the same time (phone calls and web browsing at the same time) But that is because its not based off a verizon leak and until then probably will not work.
AOSP: We'll you've got a lot of options, there's a few here on XDA and then some more on Rootzwiki, so i won't be giving detail on all of them, just a few. But they will all generally 'look' the same, by that i mean because they are all based on AOSP source it'll have the same look to it, since source looks the same.
-CM10: Well it's your basic CM that you've grown to love (or hate ) you can expect nightlies, and things to get fixed in a timely matter. If you used CM7 or CM9 on previous devices then you'll know exactly what to expect. Its built directly from source and you can expect it to be speedy quick.
-AOKP: It's built from source as well just like CM10, but has more options in it, and generally more customization as well. If you use it it'll look a lot like CM10, but it'll have added in bonuses
-CodeNameAndroid: Again built from source, but with codename you've got a ton of customization thrown in, there's a lot of stuff from different AOSP options thrown into it. Right now the Navbar doesn't work without flashing a separate file, but that's not a huge problem since its just a little file to flash. I personally am using it right now and its been great to me, can't really complain about it at all
-LiquidSmooth: Built from source, those that have used a liquid rom before will know exactly what to expect. It will be speedy quick and smooth as hell. You'll find plenty of butter in it as well, they've got there own liquidsettings that'll allow you to do even more customization, and i give them major props, i've currently got them going on my old thunderbolt which is my backup phone, but also used them on my OG Droid and i can vouch that they will provide an amazing rom for users
There are more AOSP Roms over on rootzwiki, but its again the same general thing, each AOSP rom comes from source, but each developer will theme/modify/add/remove/customize to there own liking to provide you with what they feel is the best user experience. The biggest difference between the Touchwiz JB roms and AOSP is that with AOSP you'll have a lot more options going and it'll be stock jellybean, no touchwiz nonsense to hold you back. Some people love the touchwiz stuff and that's fine, but some will love having pure jellybean on there phone and being able to take advantage of that. I'll tell you honestly 100% that AOSP will be faster no matter what touchwiz rom you run.
Oh and kernel wise, i fully stand behind imoseyon's lean kernel for AOSP roms, i've always used imoseyon's kernel's and have always gotten amazing battery life on my GS3 and thunderbolt.
Phew i really hope this helps you with any decision you may have
***If i missed any Touchwiz or AOSP roms i do apologize, i don't know them all off the top of my head, so please don't think that just because i left yours out that i meant it in a bad way***
What are the general downsides with using these JB roms weither it be TouchWiz or AOSP. I'm going to take the jump soon but whats fixed or unfixable? I hear some people say screen flicker and no 3G etc.
Neverendingxsin said:
Well there's two routes you can go to get your JellyBean fix, and that's either AOSP or TouchWiz.
Touchwiz: You've got two choices.
- You could go with Synergy JB 0.2 beta which is based off the AT&T leaked JB touchwiz build. I personally have not ran it so i can't comment on how well it works, but i use synergy as my touchwiz choice of roms, and was never disappointed by there work, so i'm sure the JB build is working great.
- There is also Jellywiz which is made by Incubus, he's been basing his off the latest leaks, and has a few builds out. One of them is a custom build which just has a few theme changes, and a few other things added in/changed. There's a lot of praise in that thread for his rom, the only bug i had when trying it was that i could not get voice and data to work at the same time (phone calls and web browsing at the same time) But that is because its not based off a verizon leak and until then probably will not work.
AOSP: We'll you've got a lot of options, there's a few here on XDA and then some more on Rootzwiki, so i won't be giving detail on all of them, just a few. But they will all generally 'look' the same, by that i mean because they are all based on AOSP source it'll have the same look to it, since source looks the same.
-CM10: Well it's your basic CM that you've grown to love (or hate ) you can expect nightlies, and things to get fixed in a timely matter. If you used CM7 or CM9 on previous devices then you'll know exactly what to expect. Its built directly from source and you can expect it to be speedy quick.
-AOKP: It's built from source as well just like CM10, but has more options in it, and generally more customization as well. If you use it it'll look a lot like CM10, but it'll have added in bonuses
-CodeNameAndroid: Again built from source, but with codename you've got a ton of customization thrown in, there's a lot of stuff from different AOSP options thrown into it. Right now the Navbar doesn't work without flashing a separate file, but that's not a huge problem since its just a little file to flash. I personally am using it right now and its been great to me, can't really complain about it at all
-LiquidSmooth: Built from source, those that have used a liquid rom before will know exactly what to expect. It will be speedy quick and smooth as hell. You'll find plenty of butter in it as well, they've got there own liquidsettings that'll allow you to do even more customization, and i give them major props, i've currently got them going on my old thunderbolt which is my backup phone, but also used them on my OG Droid and i can vouch that they will provide an amazing rom for users
There are more AOSP Roms over on rootzwiki, but its again the same general thing, each AOSP rom comes from source, but each developer will theme/modify/add/remove/customize to there own liking to provide you with what they feel is the best user experience. The biggest difference between the Touchwiz JB roms and AOSP is that with AOSP you'll have a lot more options going and it'll be stock jellybean, no touchwiz nonsense to hold you back. Some people love the touchwiz stuff and that's fine, but some will love having pure jellybean on there phone and being able to take advantage of that. I'll tell you honestly 100% that AOSP will be faster no matter what touchwiz rom you run.
Oh and kernel wise, i fully stand behind imoseyon's lean kernel for AOSP roms, i've always used imoseyon's kernel's and have always gotten amazing battery life on my GS3 and thunderbolt.
Phew i really hope this helps you with any decision you may have
***If i missed any Touchwiz or AOSP roms i do apologize, i don't know them all off the top of my head, so please don't think that just because i left yours out that i meant it in a bad way***
Click to expand...
Click to collapse
thanks a bunch for the big write-up. I do live in an area that is partly 3g, part 4g, so I am a little concerned about these data drops.. Has this been fixed in the AOSP roms mentioned above?
I would hold out a few more weeks for a touchwiz based rom - I tried Incubus' and got a number of random reboots. Cleanrom 2.5 has been working great!
Currently, all the AOSP roms have the same issues -
- data drops, esp on 3g/4g handoff. There were some recent commits that claim to have fixed this, I'm not sure if it did and which rom's include it
- potential for IMEI loss or brick. Again, you should back up IMEI before any flash, I don't think these issues are present on TW
- TW camera is better. There's an AOSP JB camera mod but hasn't been updated for the newer builds yet
- GPS locks. I keep reading about this in the AOSP rom's, I don't know how common this is.
AndyMan386 said:
thanks a bunch for the big write-up. I do live in an area that is partly 3g, part 4g, so I am a little concerned about these data drops.. Has this been fixed in the AOSP roms mentioned above?
Click to expand...
Click to collapse
your welcome. It ended up being a lot longer than I had originally planned. As for data drops, I'm testing a fix right now and I can confirm it works fine
ECrispy said:
Currently, all the AOSP roms have the same issues -
- data drops, esp on 3g/4g handoff. There were some recent commits that claim to have fixed this, I'm not sure if it did and which rom's include it
- potential for IMEI loss or brick. Again, you should back up IMEI before any flash, I don't think these issues are present on TW
- TW camera is better. There's an AOSP JB camera mod but hasn't been updated for the newer builds yet
- GPS locks. I keep reading about this in the AOSP rom's, I don't know how common this is.
Click to expand...
Click to collapse
Data drops were indeed fixed
Imei issues can happen when flashing anything from radios to kernels to roms both touchwiz to aosp. It can also easily be restored.
Tw camera only has a few more features, but in terms of quality their both equal to me. Once the aosp mod is updated it'll be even better.
GPS lock is simple, just get a full lock before flashing aosp and then while having it locked boot into recovery and do your thing.
Neverendingxsin said:
your welcome. It ended up being a lot longer than I had originally planned. As for data drops, I'm testing a fix right now and I can confirm it works fine
Data drops were indeed fixed
Imei issues can happen when flashing anything from radios to kernels to roms both touchwiz to aosp. It can also easily be restored.
Tw camera only has a few more features, but in terms of quality their both equal to me. Once the aosp mod is updated it'll be even better.
GPS lock is simple, just get a full lock before flashing aosp and then while having it locked boot into recovery and do your thing.
Click to expand...
Click to collapse
link to CM10 data fix?
Alright so I just found out on android authority that cyanogen mod just released its stable builds for the galaxy s3 variants. Just scroll down and find d2vzw!
http://download.cyanogenmod.com/?type=stable
Download will be 160mb
Sent from my SCH-I535 using xda app-developers app
Hate to say it but TW Roms on the S3 FTW.
Nothing more stable then the TW Roms we have for the Verizon S3. AOSP is just not there yet and who knows if it will ever be. After coming from a GNEX, you really see AOSP was not meant for any other devices and is loaded with problems when using anything else then a Nexus device.
Would love to get another Nexus device but who knows if Verizon will ever see one again and no other network is really good enough to pull me away right now.
Also, Google's claim about no LTE on the Nexus 4 due to bad battery, did anyone at Google try the S3? I would hardly call 4 hours of on screen time over LTE bad battery. They need to look past the GNEX which for whatever reason was a disaster when it came to battery. My wife's Rezound with like a 1650mAh battery gets as much screen on time then my GNEX did with a 2100mAh battery. Knock knock, don't we think something was wrong there!
Actually, I used the Thunderbolt I had previous to the GS3 for over a year on AOSP and it was AT LEAST as stable as the stock rom...probably more so. It just took time for it to get there. Saying that AOSP will never be stable is just...well, hogwash...Right now it's questionable. The roms are stable, it's just data that has a bit of an issue. If you're in a great reception area, there's no reason to not use it. Fringe areas, well, there are pros and cons.
Chuckleb0ne said:
Alright so I just found out on android authority that cyanogen mod just released its stable builds for the galaxy s3 variants. Just scroll down and find d2vzw!
Download will be 160mb
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I saw this, this morning... Apparently people are still having issues with blue tooth audio, and NFC.. but hey its a stable build not a RC. Will be flashing this at lunch!
SubliminalME said:
Actually, I used the Thunderbolt I had previous to the GS3 for over a year on AOSP and it was AT LEAST as stable as the stock rom...probably more so. It just took time for it to get there. Saying that AOSP will never be stable is just...well, hogwash...Right now it's questionable. The roms are stable, it's just data that has a bit of an issue. If you're in a great reception area, there's no reason to not use it. Fringe areas, well, there are pros and cons.
Click to expand...
Click to collapse
I never said it will never be there I said who knows if it will get there. The Thunderbolt was never stable on stock so saying AOSP was just as stable is not saying much. lol
Signal is important to many people. If I was not worried about signals I would not be on Verizon paying their hight prices. I would be paying half the price for service running a Nexus 4 on a crappy GSM network. There are more issues then just signal and sure eventually they may all get worked out but so many people here jump devices so often we never get to see the final product if one is produced.
All I am saying is TW Roms have been so good on the S3 I cannot imagine sacrificing the stability at this point for an AOSP rom and trust me I would love to run AOSP. I never knew how good it felt until the GNEX which was my first Nexus device. Man, did AOKP rule on that phone.
I am currently using this rom. The only problems I seem to have are GPS locks, and the speaker phone echo. Supposedly some work was done on the echo, so perhaps a wipe is need to reap the benefits. At this point, once those two problems are fixed I would consider it a daily driver for anyone.
I don't use NFC or bluetooth, so I am unaware of problems related to those features.
Bass Issue
I'm not really sure if there is an exact stable build since the supposed stable build had Bluetooth issue by not giving the bass
[email protected] said:
I never said it will never be there I said who knows if it will get there. The Thunderbolt was never stable on stock so saying AOSP was just as stable is not saying much. lol
Signal is important to many people. If I was not worried about signals I would not be on Verizon paying their hight prices. I would be paying half the price for service running a Nexus 4 on a crappy GSM network. There are more issues then just signal and sure eventually they may all get worked out but so many people here jump devices so often we never get to see the final product if one is produced.
All I am saying is TW Roms have been so good on the S3 I cannot imagine sacrificing the stability at this point for an AOSP rom and trust me I would love to run AOSP. I never knew how good it felt until the GNEX which was my first Nexus device. Man, did AOKP rule on that phone.
Click to expand...
Click to collapse
If signal was so important people would only buy HTC and Motorola phones...just saying. I love my S3 but those two companies produce far better radios.
Sent from my SCH-I535 using xda app-developers app
Has anyone found a workaround to get NFC to work in Cyanogen 10 Stable?
ghostofdavid said:
Has anyone found a workaround to get NFC to work in Cyanogen 10 Stable?
Click to expand...
Click to collapse
NFC does work on cm10 stable
ddurandSGS3 said:
NFC does work on cm10 stable
Click to expand...
Click to collapse
I can't figure out why it isn't working for me. I go to Settings, Click on More, And Check the NFC box and it is light greyed out and it does not allow me to complete any NFC activities. I know my NFC works as I've used it this week on rooted Jellybean. Am I missing something very obvious?
[email protected] said:
Hate to say it but TW Roms on the S3 FTW.
Nothing more stable then the TW Roms we have for the Verizon S3. AOSP is just not there yet and who knows if it will ever be. After coming from a GNEX, you really see AOSP was not meant for any other devices and is loaded with problems when using anything else then a Nexus device.
Would love to get another Nexus device but who knows if Verizon will ever see one again and no other network is really good enough to pull me away right now.
Also, Google's claim about no LTE on the Nexus 4 due to bad battery, did anyone at Google try the S3? I would hardly call 4 hours of on screen time over LTE bad battery. They need to look past the GNEX which for whatever reason was a disaster when it came to battery. My wife's Rezound with like a 1650mAh battery gets as much screen on time then my GNEX did with a 2100mAh battery. Knock knock, don't we think something was wrong there!
Click to expand...
Click to collapse
I have to disagree. Liquid smooth rom is the first aosp I've seen that runs like butter.
Sent from my SCH-I535 using xda premium
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
nosympathy said:
If signal was so important people would only buy HTC and Motorola phones...just saying. I love my S3 but those two companies produce far better radios.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've yet to see an HTC phone as light weight as the S3. Every HTC phone I've held feels like a brick.
Sent from my SCH-I535 using xda premium
ghostofdavid said:
I can't figure out why it isn't working for me. I go to Settings, Click on More, And Check the NFC box and it is light greyed out and it does not allow me to complete any NFC activities. I know my NFC works as I've used it this week on rooted Jellybean. Am I missing something very obvious?
Click to expand...
Click to collapse
if you search "nfc greyed out" in the question forum youll find pages of results and threads about this, and youll get your informatino much faster.
theres a zip youll find, as well as instructions.
nandroid
flash TW JB rom.
enable NFC (might as well get a GPS lock also)
restore nandroid
win
For the NFC issue, I believe that the CM10 thread includes a flashable zip or APK to fix the NFC: see this thread.
I do have a general question. I have been running CleanROM 5.6 but wanted to know how "stable" CM10 is in comparison to CleanROM. I understand that I'd be missing out on some Touchwiz features (motions, smartstay, powersave), but I am most concerned w/ battery life and data connection, particularly as I find myself never using the Touchwiz features anyway.
I am finding that reception on my S3 is inferior to my Razr M - for example, where I would get 3G or 4G signal on my M, I was getting 1x or no data on my S3. From what I've also read, data on the CM ROMs is inferior to the data on the TW ROMS. Can anyone confirm this?
Also, w/ battery life, I've also read that battery life on CM ROMS is inferior to that of Touchwiz. In any case, I am finding that the battery life on the S3 in general is inferior to that of the Razr M given my use. Specifically, I push my work email, read and respond to emails, browse the web a little bit, a few phone calls and text messages, and some FB use. On the Razr M, I was consistently getting about 36 hours of use, whereas, on the S3, I have been barely able to get 24 hours. If battery life on TW is already inferior to that of the Razr M, I am not willing to sacrifice battery life further by going with CM10.
In addition to battery and consistent data, are there any other bugs/issues w/ the CM10 stable that I should be aware of (tethering, BT connectivity, low call volume, speakerphone echo, etc.)?
Lastly, I assume that CM10 stable does not have the multitude of bugs that the present version of CM10.1 has?
So, I picked up a Galaxy Note 2 tonight, pretty sweet device but I think it may just be too big. I am looking at trying the GSIII instead but had a few questions. The GNex was known for having poor cell reception/radio performance, the Note 2 is MUCH better than the Nexus and also switches between 3G and 4G in a flash, the Nexus takes quite awhile to make those switches. For those that have had the Nexus and GSIII, is the GSIII also better for reception, does it have stronger radios and faster LTE speeds? Does it switch from 3G to 4G and vice versa faster? Also, how is the battery life in comparison, even with the extended battery the Nexus is still pretty poor for battery life.
I am running CM10.1 on my Nexus and have run custom firmware from day 1, if someone who has experience with ROMs on both devices could comment it may help even more. Thanks in advance to everyone!
I don't have any scientific data per se, but I came from the gnex and it seems as though it had quite a bit better radio than my gs3. I was actually quite pleased with the gnex mobile data performance.
My gs3 drops to 3g much more frequently than the gnex at specific areas of my commute, and it's very repeatable. But, I'm sure others will say differently
My gs3 is a lot better then my gnex, never drop data at all.
The S3 destroys the GNEX in signal strength. Not even close. The GNEX was one of the worse signal devices I have owned. No issues with the S3.
Battery life not even close. With the extended battery on 4G with the GNEX I could not even pull over 2 hours on screen time. With the S3 I pull about 4 after 16 hours unplugged.
As for Roms. If AOSP is your thing, no comparison that a Nexus device is the way to go. AOSP on the S3 still has it's fair share of issues and development support is just not the same as a Nexus. I was willing to sacrifice all that for a device that just worked with a decent battery. I am quite happy running one of the custom TW Roms until the AOSP issues have all been worked out.
[email protected] said:
The S3 destroys the GNEX in signal strength. Not even close. The GNEX was one of the worse signal devices I have owned. No issues with the S3.
Battery life not even close. With the extended battery on 4G with the GNEX I could not even pull over 2 hours on screen time. With the S3 I pull about 4 after 16 hours unplugged.
As for Roms. If AOSP is your thing, no comparison that a Nexus device is the way to go. AOSP on the S3 still has it's fair share of issues and development support is just not the same as a Nexus. I was willing to sacrifice all that for a device that just worked with a decent battery. I am quite happy running one of the custom TW Roms until the AOSP issues have all been worked out.
Click to expand...
Click to collapse
Amen on the AOSP :good:
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
[email protected] said:
The S3 destroys the GNEX in signal strength. Not even close. The GNEX was one of the worse signal devices I have owned. No issues with the S3.
Battery life not even close. With the extended battery on 4G with the GNEX I could not even pull over 2 hours on screen time. With the S3 I pull about 4 after 16 hours unplugged.
As for Roms. If AOSP is your thing, no comparison that a Nexus device is the way to go. AOSP on the S3 still has it's fair share of issues and development support is just not the same as a Nexus. I was willing to sacrifice all that for a device that just worked with a decent battery. I am quite happy running one of the custom TW Roms until the AOSP issues have all been worked out.
Click to expand...
Click to collapse
x714x said:
Amen on the AOSP :good:
Click to expand...
Click to collapse
Well I believe both CM10/10.1 and AOKP work very well on the GS3, I haven't heard of any issues bit if you know of any please let me know. I am heavily considering picking up a GS3 on Swappa or new at Best Buy.
bose301s said:
Well I believe both CM10/10.1 and AOKP work very well on the GS3, I haven't heard of any issues bit if you know of any please let me know. I am heavily considering picking up a GS3 on Swappa or new at Best Buy.
Click to expand...
Click to collapse
If you haven't heard of any issues with AOSP Roms you have not read through the threads.
No issues on eclipse.
Every thing works out of the box.
Signal rocks with latest radio
No data drops
No camera issues
NFC and wallet wallet work
No force closes.
Simultaneous Bluetooth and aux work flawlessly
[email protected] said:
If you haven't heard of any issues with AOSP Roms you have not read through the threads.
Click to expand...
Click to collapse
To be fair, I've been running AOKP Milestone 1 for about a week now, and have had absolutely no issues with it. Battery life is fantastic, it is ridiculously fast, and every feature I need works fine on it. I haven't noticed one feature that is missing or doesn't work.
What are some of the AOSP issues then? Specifically CM10/10.1? They are flawless on the Nexus so I just assumed they would be on all devices.
bose301s said:
What are some of the AOSP issues then? Specifically CM10/10.1? They are flawless on the Nexus so I just assumed they would be on all devices.
Click to expand...
Click to collapse
Dude, read the threads.
A CM 10.1 rom wasn't even released till 2 days ago on the S3 as a beta. I know the camera isn't working at all.
For 4.1 ROMs it goes from signal drops in bad areas to low video recording to Bluetooth issues... Plus as you read through the threads you will just see so many complaints here and there. So might effect you and some may not.
The GNEX was made to run AOSP. The S3 was not. By no way can you think if it works on Nexus device it will work on an S3. Not even in the same ballpark when talking about AOSP.
[email protected] said:
Dude, read the threads.
A CM 10.1 rom wasn't even released till 2 days ago on the S3 as a beta. I know the camera isn't working at all.
For 4.1 ROMs it goes from signal drops in bad areas to low video recording to Bluetooth issues... Plus as you read through the threads you will just see so many complaints here and there. So might effect you and some may not.
The GNEX was made to run AOSP. The S3 was not. By no way can you think if it works on Nexus device it will work on an S3. Not even in the same ballpark when talking about AOSP.
Click to expand...
Click to collapse
Sorry if I don't have time to read hundreds of pages of threads, people have experience with them so why not ask?
I know the Nexus is by far the most hacker friendly phone, so I understand that, but since the GS3 is fully unlocked I figured AOSP ROMs would be good to go, I assumed wrong. I would have to assume that the biggest reason then is that with a Nexus you get the advantage of Google releasing the binaries/drivers for all the hardware components, and while Samsung releases the Source code for their phones that doesn't necessarily help with drivers and components, is that then right assessment on my part?
bose301s said:
Sorry if I don't have time to read hundreds of pages of threads, people have experience with them so why not ask?
I know the Nexus is by far the most hacker friendly phone, so I understand that, but since the GS3 is fully unlocked I figured AOSP ROMs would be good to go, I assumed wrong. I would have to assume that the biggest reason then is that with a Nexus you get the advantage of Google releasing the binaries/drivers for all the hardware components, and while Samsung releases the Source code for their phones that doesn't necessarily help with drivers and components, is that then right assessment on my part?
Click to expand...
Click to collapse
Yes, something like that... We don't even have source for the JB S3 kernel.
The problem with asking your question here is you get people telling you everything is wonderful. Then when you read the actual threads you realize they are not.
I can't tell you how many times I wanted to flash an AOSP ROM but after taking the time to do a little reading I always convince myself to stay with a TW Rom for now. Maybe the AOSP bugs won't bother you. Everyone is different.
[email protected] said:
Yes, something like that... We don't even have source for the JB S3 kernel.
The problem with asking your question here is you get people telling you everything is wonderful. Then when you read the actual threads you realize they are not.
I can't tell you how many times I wanted to flash an AOSP ROM but after taking the time to do a little reading I always convince myself to stay with a TW Rom for now. Maybe the AOSP bugs won't bother you. Everyone is different.
Click to expand...
Click to collapse
Well, your reply definitely helps because signal issues with the Nexus are the #1 reason I am wanting to leave it, I love the phone overall, love the design, the onscreen vs. hardware nav keys, the ability to have the newest version of Android on it within 24-48 hours of it being pushed to AOSP (even if it isn't an official ROM) and all that goes with a Nexus. What
I hate is the poor signal the Nexus has and the poor battery life the Nexus has no matter what ROM and what Kernel I have used. Mainly trying to decide between keeping the Note 2 I bought or returning it for an S3 which is more unlocked, does have AOSP and should still have better signal and battery life than the Nexus.
bose301s said:
Well, your reply definitely helps because signal issues with the Nexus are the #1 reason I am wanting to leave it, I love the phone overall, love the design, the onscreen vs. hardware nav keys, the ability to have the newest version of Android on it within 24-48 hours of it being pushed to AOSP (even if it isn't an official ROM) and all that goes with a Nexus. What
I hate is the poor signal the Nexus has and the poor battery life the Nexus has no matter what ROM and what Kernel I have used. Mainly trying to decide between keeping the Note 2 I bought or returning it for an S3 which is more unlocked, does have AOSP and should still have better signal and battery life than the Nexus.
Click to expand...
Click to collapse
Signal on TW Roms are fine. The S3 is much better then the GNEX. It is only AOSP Roms that are effected and in bad signal areas. Supposedly they have gotten it better but I am pretty sure they don't have it fixed yet as it works on stock.
[email protected] said:
Signal on TW Roms are fine. The S3 is much better then the GNEX. It is only AOSP Roms that are effected and in bad signal areas. Supposedly they have gotten it better but I am pretty sure they don't have it fixed yet as it works on stock.
Click to expand...
Click to collapse
Reading the CM10 thread definitely sounds like there's issues, battery life, BT and 3G. 3G is a huge deal to me because that's all I can get at work. I guess if it's between the GS3 and the Note 2 on custom TW firmwares I will probably stay on Note 2, faster, better battery life and amazing screen. Will still contemplate though but I think I have a decision.
Ok, for the hell of it trying a GS3 since the Nexus really is bad for battery life and signal. Will probably try TW and AOSP ROMs, if you put TWRP on it you should be able to flash between the 2 with no real problems as long as you wipe system, data and cache right?
I live and work in an area that has poor signal for Verizon. I almost immediately flashed to CM 10 after I got the Verizon Galaxy S3 because I was running CM 10 on my previous Sprint Galaxy S3 without issue. I have been updating the radio and RPM with each leak (currently running K3) and things got a little better but I constantly dropped calls. I had to flash back to stock because I flashed to CM 10.1 and my radio got messed up. I ran the newest stock rom for the last week and noticed a huge difference. I still had low signal but my data dropped less frequently and I could actually make phone calls in areas I couldn't before.
I rooted, and flashed to CM 10.1 and noticed right away the signal is not where it should be. I can't make phone calls inside of buildings with low signal at all, where with stock I could without issue. I love CyanogenMod but I don't think I can deal with the poor signal.
Any ideas on what could be causing this problem and maybe a possible resolution?
fowen said:
I live and work in an area that has poor signal for Verizon. I almost immediately flashed to CM 10 after I got the Verizon Galaxy S3 because I was running CM 10 on my previous Sprint Galaxy S3 without issue. I have been updating the radio and RPM with each leak (currently running K3) and things got a little better but I constantly dropped calls. I had to flash back to stock because I flashed to CM 10.1 and my radio got messed up. I ran the newest stock rom for the last week and noticed a huge difference. I still had low signal but my data dropped less frequently and I could actually make phone calls in areas I couldn't before.
I rooted, and flashed to CM 10.1 and noticed right away the signal is not where it should be. I can't make phone calls inside of buildings with low signal at all, where with stock I could without issue. I love CyanogenMod but I don't think I can deal with the poor signal.
Any ideas on what could be causing this problem and maybe a possible resolution?
Click to expand...
Click to collapse
Depends on where ya live, your mileage may vary. I get within 1-2 -dBm between the two.
Technically since we don't have the source code the reason CM10 has data is by a work around.
There really is nothing you can do. It is what it is. I've run devices with CM that have provided better signal, and usually were on sprint lol and then run them where they provide the same or slightly worse quality.
Happens.
Sent from my SCH-I535 using xda app-developers app
This does not ha e anything to do with cm 10. This this to do with the the phone radio. This is the reason why I switched to the DNA now I have Full bars everywhere I go. On my s3 I used to drop calls all the time.
Sent from my HTC DROID DNA.
Itzvik said:
This does not ha e anything to do with cm 10. This this to do with the the phone radio. This is the reason why I switched to the DNA now I have Full bars everywhere I go. On my s3 I used to drop calls all the time.
Sent from my HTC DROID DNA.
Click to expand...
Click to collapse
Your wrong...read OP post and you realize your wrong.
You have your DNA now leave and stop trolling.
Sent from my SCH-I535 using xda app-developers app
Ok I really hope I'm not beating the dead horse here but I have a similar problem on my verizon Galaxy s3 and I was hoping there might be a fix
My understanding is that the CM developers dont have the GS3 source for something (the RIL?) so they have to use a different RIL? I'm probably totally butchering that, because I dont understand the words I'm using, but from what I've gathered the signal is what it is on CM, and will not improve beyond where it is.
It is certainly usable for me, but there are many times my wife has 4g and I have 3g, or she has a 3g signal and I have nothing at all (she has a stock vzw gs3).
Restola said:
My understanding is that the CM developers dont have the GS3 source for something (the RIL?) so they have to use a different RIL? I'm probably totally butchering that, because I dont understand the words I'm using, but from what I've gathered the signal is what it is on CM, and will not improve beyond where it is.
It is certainly usable for me, but there are many times my wife has 4g and I have 3g, or she has a 3g signal and I have nothing at all (she has a stock vzw gs3).
Click to expand...
Click to collapse
I think you're correct on the RIL part.
I had the same issue on 10.1. I switched to an older radio, and though it is not perfect, it did give me better reception and the switch from 3g to 4g is faster. My radio is VRLHE
Why not try a rom like beans. It is a touch wiz rom that looks like aosp and had a lot of aosp features. That way the radios will work fine you will still have aosp stuff and all the goodness of being rooted.
Sent from my SCH-I535 using xda premium
Let's not get confused here. Tw rom's like beans are themed to look slightly aosp, but are far from it. Aosp has so many customization options that tw cannot come close to. (I'm an aosp guy, if you can't tell). That being said, signal strength will always be an issue on aosp based roms due to the Samsung ril only being licensed to samsung, hence only working on tw rom's. The official ril code will almost never be released as its how qualcom makes its money. Currently aosp rom's use a work around home brewed ril that is very effective, but not quite what stock rom will offer. So if your signal is poor where you are, aosp may not be the best choice for you, but for most the signal is just as good as tw, and imo the only way to run android.
Sent from my Nexus 7 using Tapatalk HD
I'm not confused, that's why I said looks like (aka themed like). Also I said some aosp features like MMS, camera/gallery, lock screen to name a few. Its no where near the same but if they are having issues which I read a few people do have with signal and losing data its a nice alternative and has SOME similar features.
Sent from my SCH-I535 using xda premium