yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I'm beginning to discover it's actually a 4.2.2 issue. That release was suppose to IMPROVE 4G/3G/Wifi handoff but it doesn't look like that's happening. Either there is a mistake in the CM code that causes the problems I'm (and others) are seeing or my second theory is that because we don't have a 4.2.2 modem yet or even a 4.2.1 modem, that our phones aren't playing nicely with the new code Google added to improve network handoff.

I'm still hoping that by making CM10.1 aware, they can fix it up (maybe revert pieces back to 4.1) until the official 4.2.1(2) comes out for our phones with updated basebands.

So in theory everyone should see this issue IF they frequent locations with poor 4G signal. People who always have great 4G or don't ever get 4G won't really see a difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Just wanted to say thank you for your persistence in this matter; I live and work in areas with great 4G signal but I have noticed this sort of thing when away from town. I also think you may be on to something with the 4.2 modem that is yet to be released from AT&T. Keep at it; your JIRA submission and these posts are definitely going to help and are what this thread is all about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Thanks buddy. Your support is much appreciated.

The hard part is going to get someone at CM to look at it and believe in it. I've e-mailed Steve about the issue on recommendation from someone else here on the forums and I've also e-mailed Dan Pasanen with the report as he is responsible for most of the telephony type commits from the last 6 months. I'm sure they are swamped though with other issues and their own personal lives.

Anyway, the report is created. If anyone has any more info or theories let me know!

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bcos:
I also work in a weak 4G zone and have had the same reception issues.

As an experiment I dropped back down to the stock Rogers rom (4.1.1) and have witnessed noticeably better switching between 4G and HSPA. In fact, I've not once seen a 4G signal with 0 bars reception, though that happened daily with CM10.1

Your theory on the baseband sounds plausible to me. Hopefully the developers are able to sort this out.

Thanks for your investigative contributions! :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Great thank you! Did you happen to notice what the dBm reading was on average while on 4.1.1? I haven't had time to go back to CM10 yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] comdei:
Does anyone have a link to the new bootloader? I am stuck on 5/13 and would like to upgrade.

Can I just flash the new bootloader and call it a day?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Look back maybe 150 posts. There's a link to an Odin flashable zip or something. A few pages before that was instructions on how to map the bootloader partitions from the stock rom in heimdal if that's your thing

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bcos:
While sitting at my desk I was averaging about -116dBm/24asu (with 1 bar of LTE reception). For comparisons sake I wandered outside and had 3 bars of LTE reception with -98dBm/42asu.

Back at my desk (with 1 bar LTE) I switched network modes to disable LTE and the reception jumped to 3 bars of H+ reception @ -97dBm/8asu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Or follow the instructions in my earlier (quoted) post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VegUnited:
This is a smooth nightly for me, great battery. Anyone else using mightytext and having the issue with it sending two texts for every one you send through chrome ? My n4 sends one but the cm10.1 S3 sends two?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingpongg:
I agree, this is a very smooth build. I use MightyText and sent about a dozen texts from chrome this morning. I had no issues with double texts like you described. :-/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rallysquirrel:
Trebuchet crashing when moving icons on homescreen

Trebuchet is crashing when I try to move an icon on the homescreen. Is this an isolated issue?

The phone came from another rom and older bootrom so I upgraded the bootrom. rebooted and wen into recovery mode factory wipe, delvik, etc. and installed a fresh cm10.1 0529 with 130xxx gapps. Not happening on my other phone that's been running CM10.1 for a couple of months.

I installed 0530 nightly and still having the same issue on the problem phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
My signal is pretty bad when using lte network, most of the time only get 1 bar... So hope you guys fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
are you in a location with good lte?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I'll bet using T-Mobile that you are getting terrible LTE (seeing as their GS3 is HSPA+)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
I would get that "static" or "flickering" on the lock screen and often when it happened on the lock screen it would also happen in whatever app I opened up from the notification bar from the lock screen. I could deal with it because pressing "home" afterwards often cleared it up.

Starting on the 26th nightly, iirc, the multicolored static would show up on my home screen, distorting the wallpaper, but not any of the icons / dock buttons. The screen would "flicker" back and forth between multicolored static for wallpaper and the correct wallpaper. Sometimes this flickering would be fast, a few times a second. Other times it would be multicolored for several minutes before switching back to normal for several minutes. The only way to fix this after it occured was to reboot. It was a minor annoyance, but the phone was usable when it happened.

I updated to the May 29th nightly when it came out, and the problem for worse.

Now instead of being multicolored static, its just black. So when it happened on the lock screen, I can see nothing. I can still unlock the phone since I know where to slide my finger, and I can still launch programs, which immediately fixes the blank screen issue. However when I go back to the home screen from an app after this issue happened on the lock screen, the home screen will be black. No icons, no notification bar, nothing. Swiping between screens will make the phone "flicker" the correct screen for a moment before it goes black again. Pressing the volume keys will make the screen show correctly until the volume slider goes away. Pressing power to get the power menu also fixes the problem until it is canceled out of.

Only fix is a reboot. This is much worse than the multicolored static, because when this happens, the phone is not really usable.

5/29 nightly

Stock Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TKG26:
I get the static with nightlies and the "stable" release... last occurred 2weeks ago I moved back to a synergy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Ive found that by setting all the animation settings in Developer Options to off (there are 3 of them) , disabling hardware overlays, and upping the min CPU freq fixed most of that flickering. Using KT kernel 5/29 I have had no flickering on 5/29 nightly or tasks 5/27
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustangtyson:
RC3 is out :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Just downloaded and tried to flash RC3 and got an error message. Will download again and try it.

Reboot brought me to the CM GS3 screen only. Had to use the button key combo to get into recovery and flash RC2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Maybe an MD5 error still. Try downloading from another source like http://10.1.cmxlog.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustangtyson:
Mine flashed fine and booted as normal.

You may be having the "old bootloader problem" look about 20 pages back and here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
That's not another source, that just links to get.cm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Should give 530 a shot. I'm not too sure if there's any difference between 530 and rc3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] disengage:
Anyone else here try RC3 yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Weak 4G Signal Still Present on RC3

My previous JIRA report for the 4G network signal not reporting correctly was against RC2. I've confirmed tonight and taken some nice logs on RC3 in regards to this issue still being present.

I will be opening up a new JIRA report against RC3 tonight in regards to this matter.

Lets hope it gets fixed before the stable is released. I feel that it's a pretty major issue and one that should be resolved before CM10.1 is considered stable.

For anyone who has this issue or wants to support on getting it resolved, please sign up on JIRA and vote for the issue to help get it some attention. No need to comment that you have the same issue or post any further information on the matter. A simple vote is all I need.

Thanks again for your support and hopefully we can get this fringe 4G signal issue cleaned up!

Thank you.

The new report can be found here https://jira.cyanogenmod.org/browse/CYAN-1261

There is a link to the old report contained within the new report if anyone would like to reference it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Told you it wasn't easy man. Unless there's a nice soul involved in CM10.1 d2xxx dev who's out there hearing you, it's a difficult road to get your JIRA issue anything but scoffed at.

Keep up!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I hate Bluetooth. Going to try a stock derivative, I think, to see if perhaps Samsung simply has a better set of drivers for it. I can't stand Samsung's overlay, though, or much else about it like all the beeps and bloops, so I'm sure I'll be back. Soon. maybe it's time for a stupid headphone cable. Hello 2002.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I never assumed it was.

I respect the process they have set up to help weed out the reports against unsupported releases and reports opened due to application problems or user error. I understand they need to narrow down the true issues and that there is a countless amount of information logged on JIRA for them.

It is a little discouraging to see such simple little petty issues being resolved left right and center with such large bugs with widespread impact being largely ignored. I do understand that most of their "staff" isn't educated in the large areas of the Android framework and that likely contributes to some of the major issues being left on the back burner. It really is too bad but I do understand that not every issue is immediately recognized as an impact bug as they all cannot be looked at in depth the minute they are reported.

As for my original report, it wasn't shot down like most are almost immediately after being opened and this time I once again have all the required information so hopefully it will remain open to eventually be discovered by an interested CM dev. It really is too bad however that we don't have a d2att dev monitoring this thread for discussion like this. It's hard to show the impact of the issue if they aren't seeing the discussion and reports from other users.

Anyway, as I said in my post above, if anyone else is seeing this issue or wants to support the cause, please feel free to sign up to JIRA and vote for the issue. The more support it can get the more likely it will be seen.

Thanks again everyone. I'm glad we have been able to take this "development" adventure together. So often this thread is littered with discussion about what release is best and whether or not XXX issue has been fixed yet. Also we get a lot of I've seen this problem has anyone else seen it? No one wants to take charge and debug the issue. Most are too lazy to try the basic things before reverting to the forums to ask others to debug for them. It's been refreshing to bounce some of my debug type information off you guys to get your help and input. Sometimes just typing out what I'm thinking helps me understand what I'm looking at a little better and help keep my thoughts organized and recorded. Too bad no devs are involved in this thread to chime in but I can see why and am not surprised.

Cheers and happy flashing everyone!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] detule:
Hi,

I am not a staff member as you put it, not even an AT&T user, but I thought I would chime in. Hope you don't mind.

Certainly appreciate the tone of your post, if not the content. For that, I thank you - there's so much garbage on xda, it's easy to start glossing over posts, rather than paying attention to detail.

I take issue with your "It is a little discouraging to see such simple little petty issues being resolved left right and center". Couple of things:

1. We will never have a perfect RIL. Take that to the bank. The RIL layer is a house of cards built on top of a closed source binary blob, and we will never, ever have identical (or even similar) functionality as stock. If you can't deal with this, aosp roms aren't for you.

2. The motto of this project is "patches are welcome". All of us at some point were in the same spot were you were - we wanted some functionality that wasn't present. If you are passionate about chasing down this bug, roll up your sleeves and get it done. Saying "I can't" or "I don't have the time" is fine, but at the same time posting that you are discouraged that others are chasing down "petty bugs" is a bit .... discouraging, for a lack of words, no?

3. Lastly, let me also mention this, knowing full well others before me have brought it up: What you think of petty, is (perhaps) another person's project that they've invested countless hours in. Perhaps you weren't getting random reboots, or you weren't experiencing graphical glitches (or whatever other issues that were recently resolved), but others were. Even better, all of those had JIRA reports too, way before you had something up there. And you know what, someone was up all night, sacrificing time from work/life/family to hunt down whatever bug that captured their attention. Even better - for FREE! All so that couple of days later someone can get discouraged that whatever bug they thought was center of the universe didn't receive proper attention.

You've done your bid. As a good citizen of the CM community, you opened up a JIRA report for a bug you are experiencing. Now tell me how do you think demeaning other people's work and statements such as

will win over a "staff" member over to your cause?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't imagine it was demeaning rather than assuming from logical thinking that not everyone involved in the CM project would be knowledgeable enough to be able to fix this particular issue. There's is nothing inherently wrong or to be ashamed of in not knowing something, I'm sure you'll agree. :)

That being said, when basic function such as 4G/3G switching gets broken down the road (it's a phone after all), the issue is reported, yet other very low priority bugs get worked on, it's difficult to keep hope the issue will ever get resolved. And sadly working on it yourself is hardly a viable route, the learning curve being too steep to make it worthwhile when taking about RIL related things. One would probably learn how to fix it after the device stopped being supported. :p You just keep your fingers crossed in hope a good soul with more knowledge in the matter will be taking this as a personal project.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] detule:
Sure. However, what you just said, and the line I quoted:

I do understand that most of their "staff" isn't educated in the large areas of the Android framework and that likely contributes to some of the major issues being left on the back burner.

are not the same statement. There's many folks on the "staff" who are well versed on the Android framework. No, they are not Dianne Hackborne, not even close, but they do know their way around. In fact, there probably is someone that can make some headway even with this problem (even though as I said, problem with the RIL is the fact that we are dealing with a closed-source binary that's completely undocumented). Let's do the math: CM "staff" is what, 100 people (judging by the "members" tab on github)? That's world-wide. How many of them do you think have an S3? How many of them do you think have AT&T service? How many of them you think live in an area where they can reproduce this bug? Most importantly, how many of them do you think have the time to tackle this issue?

At any rate, a patch just got merged that affects our RIL, written by no other than an s3 wielding CM contributor. Lookout for any changes (good or bad).

This is probably true. But, we all started hacking around android because we wanted something fixed. It's a slippery slope, and if you have some background with coding, you'll find the curve not being quite that steep. Having said that, this is a developer forum. No, I don't expect everyone to be a developer, but let's not disrespect each other by trying to prioritize each other's work, or make sweeping statements qualifying skill-sets of the CM developer community.

Sorry to hijack the thread. I'll stop now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Had my first random reboot with rc3 last night. Back to 5/29 for me until the stable release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I thank you for your rebuttal and will leave it at that. I really don't want to get into it with anyone. My ideas, views and opinions are obviously different than yours for whatever reason and that's going to happen. Your points and comments are valid and I will take from it all that I can.

I respect your intelligent coherant post and for not outright blasting me with your views and the fact that you disagree. Perhaps some of my wording wasn't chosen wisely enough and I appologize for that. I in no way am trying to demean the CM team I love the guys for what they do and I've been running their ROMS on the Samsung Galaxy S devices since they were first released. I understand the team is big and the makeup is very diverse, I'm not disrespecting anyone in anyway at least not intentionally.

I am sorry if I offended you.

Cheers and thank you again for your input on this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TeflonMyk:
Now that's the most respectful debate that I have seen on here in a while. Kudos to you both and thanks to all the CM devs out there who give us these great ROMs!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I think that's exactly the point flex and I are trying to make. ;)

Very few people with the knowledge and the necessary requirements.

Although I don't believe it is necessarily related to AT&T itself, for that matters.

I myself have a bit of experience, mostly hacks left and right to get things working right. Do I consider these worthy of working on? Sure. Priority? Very low. I'm not kidding myself, I don't expect my little mods to be even worth setting up git to share them. It's tedious, and the chances my commits would get merged within CM are close to none.

I don't see it as disrespect and I don't think it should be seen as such to consider Telephony/RIL more important than many other things, after all, it's a phone before being everything else. :)

Have a good day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
That was it. Many thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Quitter. Try upping your voltages and playing with your governors/schedulers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
no. i want it to run at normal default settings. i have no desire to mess with that stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Well if you consider that the S3 quality control isn't great which means not all devices are created equal. Therefore what works for cyanogen might not work for you. Do what you want but for me upping my voltages 25mv across the board has completely eliminated reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Being that rc3 is one of the only cm releases that has given me a reboot, I'm prone to believe it's not my device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] suprtrukr425:
RC4 now available. http://get.cm/?device=d2att&type=RC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] twostep665:
I'm on RC3 and for the first time ever, i've had a random reboot and it won't send mms messages. Anyone else have this issue in RC3? Looking for a changelog and I don't see one for the release candidates. I effing love CM and what you guys do for the community. I will not complain bicker moan or anything about this software Thanks everyone!

Edit: flashed rc4. still no MMS. cleared data and reboot and it now works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
I just had two reboots on 531. Seems associated with navigation.

What are the differences between 531 and RG4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just wondering... Has anyone else experienced occasional losses of data connection where the only solution is to toggle data off and back on again in recent nightlies and the release candidates? I'm curious to know if it's just me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cy-rock:
RC4 installation aborted

assert problems ...bad bootloader...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
update it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Read about last two weeks of posts about boot loader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cy-rock:
thx guys ill check that out !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Where is the g app link again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
http://goo.im/gapps/gapps-jb-20130301-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Same here. Like I have crappy 3g connection and great edge but it won't swap over until I enable and disable airplane mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Thanks man

---------- Post added at 05:47 AM ---------- Previous post was at 05:42 AM ----------

Lol another release of cm. And I don't mean this really to anyone. But you would think that after 30+updates they would get Bluetooth working and or not have so many bugs. And really anyone notice a real difference with this "new" Cm rom.

My real question has anyone flashed this and have not had gps issues. Because I want to flash this but I may flash back to a TW rom and was hoping that I wouldn't have gps issues coming back. I have seen some user that had to revert back to stock just to get gps working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bitnerd:
You may have to be more specific with what problems you're having

I'm running the nightlies and use the GPS and Bluetooth almost daily with no problems. I haven't had problems in quite a long time