Database Info

Anyone rooted? How is Jellybean on AT&T One X?

Hello. I have the Samsung Galaxy S3 and want to switch back to the One X due to its awesome screen. I initially didn't like the One X due to the overbearing Sense (especially the multitasking, I hated that side scrolling thing). Are there stable builds od Jellybean available? If you tried them, how is your experience with it?

I'm using CM10 on my One X and love it. So much faster and more responsive than sense.
Sent from my Nexus 7 using xda premium

After I rooted I went to CleanROM 4.5 and I loved it. I enjoy sense, I just was much nicer on CleanROM thats for sure. But this is my first ever android phone, so i wanted to experience stock android. That's when I flashed CM10. I Gotta say, man is it ever smooth! This phone runs amazingly with Jelly Bean, its so fast so smooth and just so much better than sense.
I have owned every iphone up until now, and man, it was the right choice to change!
Sent from my HTC One X on CM10!

I only played around with CM10 for a short time yesterday, so others can certainly speak on the matter better than I. But seeing as you haven't received a great many responses so far, here is my 2 cents:
Short answer is that JB is very young, and things are changing quickly and often.
The general UI is very smooth, and works very well. But there are still various bugs being worked out on certain aspects, which may or may not be a deal breakers for you (for now), depending on how you use your phone. On the 8-26 nightly, streaming audio was broken (Pandora didn't work at all) and even playing non-streaming music (MP3's on the SD) mostly did not work. It looks like this may have been fixed on the 8-28 nightly. But things are changing literally day by day, and not always for the better due to upstream changes. Seems that in call volume has gone back and forth from fixed to broken, for instance.
Video camera is mostly fixed on nightlies that are labelled EXPERIMENTAL in the file name, broken in the ones that do not. I say "mostly" because the output was good most the time, but 1 time out of maybe the 10 tries I made, the output was still garbled. Again, this is something that may get ironed out very soon. The dev mentioned they just got a open source version of the phone's camera software, and he sounded very optimistic this would help remedy the camera bugs.
Everyone's requirements for what makes a daily driver is different. But for me, there are enough issues to wait longer for the bugs to be worked out. No knock on the devs at all. Their hard work is totally appreciated. What has been accomplished is awesome (and in such a short time). But CM10 is still being billed as in an "early state". Some early adopters will have to tolerate some bugs to have the cutting edge, that's just how it always is. For those that need a more stable product, we'll have to wait a bit.

Yeah building on what he said, CM10 is stable enough for a daily driver (and has been for awhile) as long as you don't need your video camera. Things break here and there but as long as you pay attention to the thread then you will know what to expect from what builds. And btw the streaming audio was fixed in 8-28, used it this morning.
Sent from my One X using xda premium

Hey guys, just found this thread.
I am very interested in the one x but do not want anything to do with sense! Assuming I get a one x with 1.85 firmware or earlier, do you think there is enough development going on to get a extremely stable cm10 (or cm9) build for this phone?
It feels a little big to me and the power button could be in a better place, but I like everything else about the phone.
stnguyen09 said:
Yeah building on what he said, CM10 is stable enough for a daily driver (and has been for awhile) as long as you don't need your video camera. Things break here and there but as long as you pay attention to the thread then you will know what to expect from what builds. And btw the streaming audio was fixed in 8-28, used it this morning.
Sent from my One X using xda premium
Click to expand...
Click to collapse

Besides the video camera, LTE also seems to have problems? Browsing through the thread I see people have to set a bunch of settings after every reboot for LTE to work. That can be a big issue for me.

toptalent said:
Besides the video camera, LTE also seems to have problems? Browsing through the thread I see people have to set a bunch of settings after every reboot for LTE to work. That can be a big issue for me.
Click to expand...
Click to collapse
Its only two settings, which are easy to access
Sent from my One X using Tapatalk 2

How is jellybean?? As rick Ross would say. Like making love to the woman of your dreams, in a room full of money out London and she screams.
Sent from my One X using xda premium

I love Jellybean, but more importantly I don't think I'll ever go back to a non-AOSP based ROM. The devs who work on Sense ROMs do an amazing job removing bloatware and speeding up what HTC gave us, but you can't match the speed of software that was designed from the ground up to be sleek and smooth. Plus I just enjoy the customizability of AOKP and CM10.
My personal preference is CM10, mainly because of battery life and the small tweaks that are unique to CM10 (for now). As others have stated there are some stability issues with Jellybean, but there are bugs in all software and in time they will be worked out. Make a full backup in TWRP and just try flashing CyanogenMod for a day to see if you like it. Titanium Backup Pro offers complete backups of all app data and even SMS, so I am constantly flashing new ROMs without much risk of permanent data loss.

toptalent said:
Besides the video camera, LTE also seems to have problems? Browsing through the thread I see people have to set a bunch of settings after every reboot for LTE to work. That can be a big issue for me.
Click to expand...
Click to collapse
I don't know. LTE works for me. Noticed it when I went to work today. Btw LTE just got switched on in Wilmington, DE. I never had to change any settings, it just worked.
Edit: I remember I was on CleanROM (forget which version, but it was quite awhile ago, I think it was based on 1.85), then moved to AOKP M6, then to CM10.
Sent from my One X using xda premium

Yep, lte has always worked for me as well (cm10 and aokp). I did come from cleanrom though (started with version 1). I switched to aokp jellybean and it's been more stable and honestly, smoother than cm was. That was back on the 8/16 version so things may have changed. Since I can't comment on the newer releases of cm, I will say that the aokp jellybean release is extremely smooth overall. As with cm, camera and video still have issues. My personal opinion though, is that neither aokp or cm are as stable, smooth, complete as cleanrom de was. They are getting close though and definitely close enough that I have no desire or need to go back (though clean de was/is a heck of a rom).
Sent from my One X

CM10 is surprisingly polished.
Most things thats is important will work and MiLocker works really well on it too.
Most Awesome feature is the ability to remap the buttons.

Getting better every day and tonight's build should have 100% working cameras in the nightly builds. No more experimental builds. I highly suggest cm10, haven't tried miui or aokp jb releases yet, been in cm10 for close to two weeks and can tell you it's really dd material now. Most kinks are gone, and battery life is usable even with wake locks. And with a new build everyday, only getting better constantly.
Sent from my One X using Tapatalk 2

Cm10 is amazing....video camera is 100% as of the latest 8/31 nightly
Lte is an issue if u did not come from a sense 4.0.3 ROM such as stock 1.85 senseless 1.1 or clean ROM 4.0.
I never have issues with lte I never go into settings to change anything.
The one gripe is battery life is not as good as it was on sense first day on cm10 is worse it gets better every charge but its maybe 80-90% wat it was on sense. I still go the whole day 15+ hours and still have 40% batt I just charge every night now no big deal its worth it tho whole experience is so much better
Sent from my One X using xda app-developers app

stnguyen09 said:
Yeah building on what he said, CM10 is stable enough for a daily driver (and has been for awhile) as long as you don't need your video camera. Things break here and there but as long as you pay attention to the thread then you will know what to expect from what builds. And btw the streaming audio was fixed in 8-28, used it this morning.
Sent from my One X using xda premium
Click to expand...
Click to collapse
you should also know that there is a low volume issue on calls. The person at the other end will hear you as if you were wispering if you talk normally.
I hate screaming at my phone. Developer has tried increasing the mic volume but than it brings in-call echo.
Hopefully they can get it squared away but be ready to talk loud or repeat yourself during phone calls. weird part is that SIP calls (like with Skype) works fine.
I am still running the ROM and loving it.
Than ks

[Q] Best rom for service ONLY all other variables aside?

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

How the hell the Razr M get a leak before us?????

Here's the article from android central needless to say I'm [email protected] speechless.....
www.androidcentral.com/jelly-bean-droid-razr-m-leaks-out
Sent from my SCH-I535 using xda app-developers app

Wow that is ridiculous. And to add insult to injury every S3 on every other carrier has gotten a leak so its not like its because its an S3. Goose fra ba, goose fra ba.

Verizon and Samsung just don't play nice just look at the gnex for example.
Sent from my Galaxy SIII

microdot said:
Wow that is ridiculous. And to add insult to injury every S3 on every other carrier has gotten a leak so its not like its because its an S3. Goose fra ba, goose fra ba.
Click to expand...
Click to collapse
This is one of the reasons why we have AOSP based roms. We become less dependent on manufacturer/carrier updates.
I ask you all, who has a more vested interest in getting the i535 working the best it can on the latest and greatest? The manufacturer / carrier that already took your money and can't directly make any more profit from giving you an upgrade or the many people who own the i535, use it every day, and have the development skills to make it rock (more)? I say it's the people.
CM10 is working excellently now. I recommend M2.
To the manufacturers. Give us the hardware. Open your radio code. We'll do the rest.
To the carriers. You are not phone companies anymore. You are simply Internet Service Providers. Minutes, texts, and data are all the same thing...data (especially when VoLTE is launched).
Sent from my SCH-I535 using xda premium

mybook4 said:
This is one of the reasons why we have AOSP based roms. We become less dependent on manufacturer/carrier updates.
I ask you all, who has a more vested interest in getting the i535 working the best it can on the latest and greatest? The manufacturer / carrier that already took your money and can't directly make any more profit from giving you an upgrade or the many people who own the i535, use it every day, and have the development skills to make it rock (more)? I say it's the people.
CM10 is working excellently now. I recommend M2.
To the manufacturers. Give us the hardware. Open your radio code. We'll do the rest.
To the carriers. You are not phone companies anymore. You are simply Internet Service Providers. Minutes, texts, and data are all the same thing...data (especially when VoLTE is launched).
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Yea, but there are still multiple things that are broken on AOSP ROMs because we don't have JB code for our phone out there to port into them. Camera is half functional, many issues with bluetooth, the ever present flicker. And those are the ones I can think of off the top of my head. AOSP is damn good, don't get me wrong. I run CM10 for a daily driver and venture out into the other flavors every now and then. But it isn't near perfect yet either.

VZW has JB for the S3. If and when it leaks who knows. (My opinion of course).

Brian Gove said:
Yea, but there are still multiple things that are broken on AOSP ROMs because we don't have JB code for our phone out there to port into them. Camera is half functional, many issues with bluetooth, the ever present flicker. And those are the ones I can think of off the top of my head. AOSP is damn good, don't get me wrong. I run CM10 for a daily driver and venture out into the other flavors every now and then. But it isn't near perfect yet either.
Click to expand...
Click to collapse
The flicker is fixed and aosp camera is 90% compared to touchwiz.

droidstyle said:
The flicker is fixed and aosp camera is 90% compared to touchwiz.
Click to expand...
Click to collapse
What have you been running? I'm on CM10 M2 and I've never fully lost the flicker. That's updating each nightly until the M2. It comes and goes. Now with that, I do run the leankernel, update each time it does. That might be the cause of my flicker, dunno.
And the camera is severely lacking compared to TW. Video recording might as well get thrown out the window unless you're doing a silent film or have REALLY loud people that you're recording. Can't save to the extSD without the MOD that doesn't have half the resolutions working and force closes on different things. All the face recog and little adjustments here and there don't exist in the AOSP camera.

I was reading that as well and was like wow.
Sent from my SCH-I535 using xda premium

Brian Gove said:
What have you been running? I'm on CM10 M2 and I've never fully lost the flicker. That's updating each nightly until the M2. It comes and goes. Now with that, I do run the leankernel, update each time it does. That might be the cause of my flicker, dunno.
And the camera is severely lacking compared to TW. Video recording might as well get thrown out the window unless you're doing a silent film or have REALLY loud people that you're recording. Can't save to the extSD without the MOD that doesn't have half the resolutions working and force closes on different things. All the face recog and little adjustments here and there don't exist in the AOSP camera.
Click to expand...
Click to collapse
No flicker on pa 2.2 or eclipse 2.1...the aosp camera has more resolutions than the stock cm camera...no force closes for me. I dont need face detection or all the little adjustments, but yes the touchwiz camera is better

droidstyle said:
No flicker on pa 2.2 or eclipse 2.1...the aosp camera has more resolutions than the stock cm camera...no force closes for me. I dont need face detection or all the little adjustments, but yes the touchwiz camera is better
Click to expand...
Click to collapse
I'm guessing my flicker is from the diff kernel then not blending with the ROM very well.
AOSP doesn't have bigger resolutions tho does it? AOSP lists it as 8mp and TW uses the actual pixels(eg 1600x1200) and I've never bothered to see if they correspond I just assumed they did.

Brian Gove said:
I'm guessing my flicker is from the diff kernel then not blending with the ROM very well.
AOSP doesn't have bigger resolutions tho does it? AOSP lists it as 8mp and TW uses the actual pixels(eg 1600x1200) and I've never bothered to see if they correspond I just assumed they did.
Click to expand...
Click to collapse
8mp is 3456x2304...here is a good read about resolution and mp
http://www.photoshopessentials.com/essentials/image-resolution/

I felt the same way and I just read it after waking up an hour ago... very disappointed, I don't want these ports I want real vzw jb.
Sent from my SCH-I535 using XDA Premium App

Kinda funny to because I'm pretty sure they can't even get root yet lol.
Sent from my SCH-I535

hmm if the gs3 was laggy or there was no way to get google now then ya i would want jb but my phones flies and has google now so i dont really care about jb :silly:

I understand your point, but we have had this phone for almost a 4 months now and that phone has been out for just under a month ,Inc has been busting his ass dealing with other carriers leaks and ungrateful bastards on on this site, I'm just saying having a leak would make life better for all involved....
Sent from my SCH-I535 using xda app-developers app

mybook4 said:
This is one of the reasons why we have AOSP based roms. We become less dependent on manufacturer/carrier updates.
I ask you all, who has a more vested interest in getting the i535 working the best it can on the latest and greatest? The manufacturer / carrier that already took your money and can't directly make any more profit from giving you an upgrade or the many people who own the i535, use it every day, and have the development skills to make it rock (more)? I say it's the people.
CM10 is working excellently now. I recommend M2.
To the manufacturers. Give us the hardware. Open your radio code. We'll do the rest.
To the carriers. You are not phone companies anymore. You are simply Internet Service Providers. Minutes, texts, and data are all the same thing...data (especially when VoLTE is launched).
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So much truth. Everything's all ass backwards. Carriers think that they're phone designers and phone designers think they're software designers while google sits by going "duuuuur". Now we have stupid trivial things like the RIL holding cm10 back all because some assholes want their locks on everything. Imagine if AT&T or Intel told you what software you had to run on your computer? How did this sense of entitlement come about in the mobile industry?

Imatoasta said:
Imagine if AT&T or Intel told you what software you had to run on your computer? How did this sense of entitlement come about in the mobile industry?
Click to expand...
Click to collapse
I totally agree with this.

bL33d said:
hmm if the gs3 was laggy or there was no way to get google now then ya i would want jb but my phones flies and has google now so i dont really care about jb :silly:
Click to expand...
Click to collapse
While I semi-agree it would still be nice to have REAL JB like pretty much every other S3 in the world. I want my expandable notifications!!

I don't see why some people are surprised by this? Considering Motorola is now pretty much owned by Google?

Questions for those that went from Galaxy Nexus to Galaxy SIII

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?

Poor Signal Strength with Cyanogen 10 & 10.1

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