yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] myk.robinson:
For some reason, after installing the latest update, I can no longer receive calls. I can dial out, but calls coming in go to voicemail. Guess I can try calling Verizon to re-activate the phone or something.

---------- Post added at 11:58 AM ---------- Previous post was at 11:36 AM ----------

I dirty flashed the rom from 05/15/2013 and the phone is now working fine. May just be coincidence, who knows.. But if anyone has any answer for why this may have happened, please speak up.

I did verify, the IMEI is still correct in the software, so I have no clue whay caused the glitch.
[Verizon Samsung Galaxy S III] Fenuxx:
Also having calling issues. When making calls, I can't hang up, but the calls themselves are fine. Seems like it gets stuck at "dialing" but the call actually goes through. The in-call time counter never works either.

Edit:

Incoming calls are going to voicemail for me, not ringing the phone, just tried one from my VOIP home phone. The phone rings and rings and rings on the caller's end, but then just goes to voicemail without any incoming call going through.
[Verizon Samsung Galaxy S III] mastamoon:
I just tested this again to my work phone. I was able to call it no problem and then hang up no problem. Both while it was ringing and after my work's voicemail picked up.

I also tested a call from my work phone to my cellphone.. it rang as expected on both sides and after about 30 seconds went to voicemail (googlevoice).

Are you guys flashing anything else on top of the rom? A kernel, theme or mod of any sort? What gapps package are you using? Have you updated your phones firmware to the latest as posted in the OP?
[Verizon Samsung Galaxy S III] Fenuxx:
Using GApps 20130301, with the latest VRBMB1 radio, RPM, TZ, and SBL. This was happening both with the stock kernel, and LeanKernel 6.0, so I don't believe it's kernel related.

I just reverted to your 0517 build Masta, and all is well again. If I had to point my finger at something, I'd point at the RIL changes from the 0520 build. I know the RIL stuff was causing people problems a little while back, and it's the only significant thing that changed between the 0517 and 0520 builds.
[Verizon Samsung Galaxy S III] mastamoon:
Should be broken on everybody's phone if its the RIL. RIL isn't very selective. Not something that has voltage differences or something that could cause inconsistencies. I mean, anything is possible I suppose, but just seems unlikely.

Try today's build for me and let me know. If it still doesnt work, Im going to need you to wipe system in recovery, then flash rom and gapps again. At most you will have to re-add your google account, but last time I did it, I didnt even need to do that.

New build will be in the OP in about 5 mintues or is on my FTP site right now. :)
[Verizon Samsung Galaxy S III] Fenuxx:
I always do a clean flash anyway. I don't believe in dirty flashing. It's too dirty :P

I'll give it a shot and see if it helps at all.
[Verizon Samsung Galaxy S III] mastamoon:
Ok, so you always clean flash... what do you restore? Any kind of system data? Can you try any of this stuff before restoring/installing apps?
[Verizon Samsung Galaxy S III] PerCompLLC:
I'm not having any issues with calls either. In fact, in-call volume is working better then it ever has for me. The only thing different I'm running is LK6.0 so that I can run faux Sound.
[Verizon Samsung Galaxy S III] Fenuxx:
No restoring of any kind. I just let Google do it's thing on installing my apps, and I go from there. I basically start out fresh every time. Completely wipe everything (save for my microSD card), and re-setup my apps manually. So unless Google is responsible for any derping, it wouldn't be that. Call it all paranoia left over from the OG Droid days.
[Verizon Samsung Galaxy S III] mastamoon:
Wow.. ok. :confused:
[Verizon Samsung Galaxy S III] myk.robinson:
I just tried again with today's ROM and I get the same results, I can make an outgoing call but cannot receive. Everything else seems to work fine. I revert back to the 05/15/2013 ROM, and everything works as it should.

Not sure what I can do to help troubleshoot the issue, but I guess first its important to see if anyone else can confirm the issue.

[MENTION=2963287]mastamoon[/MENTION], any idea why this might be happening? I am using the kernel that's included with the ROM, the only thing even remotely custom that I have done is use NovaLauncher, but I seriously doubt that has anything to do with it since it's the same launcher I'm using on the 05152013 version. I am running the latest firmware as well. What can I do to get the right information to you for diagnosis?
[Verizon Samsung Galaxy S III] landale:
I can say for me I definitely do not have any issues making or receiving calls as I have received several today. I did have an issue yesterday after I flashed where my phone didn't automatically connect to the bluetooth in my car like it normally does but it worked when I manually connected them. I haven't had this issue happen again though. If it helps I am on LeanKernel 6.0.
[Verizon Samsung Galaxy S III] goldsmitht:
Guess I'm going to have to back up the 5/20; can't receive calls

:what:
[Verizon Samsung Galaxy S III] mastamoon:
Have you guys tried flashing the official nightly to make sure it's not the new ril patches?
[Verizon Samsung Galaxy S III] jlokos:
I cleaned flashed your latest build with LK 6.0 kernel and I can make and receive calls fine.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah same here. IDFK
[Verizon Samsung Galaxy S III] goldsmitht:
Another interesting issue, I can't enter voicemail password. I'm testing AOKP 5/21 and it works fine. Dirty flashed as usual, and same kernel on both

:what: :confused:
[Verizon Samsung Galaxy S III] MG386:
Flashed today's afternoonly 5/21 no problems with making/receiving calls. Cleared both caches, format system, flash rom/gapps
[Verizon Samsung Galaxy S III] goldsmitht:
Clean or dirty?
[Verizon Samsung Galaxy S III] sivarticus85:
Very interesting.... I clean flashed today's build and was having issues making and receiving calls... curious indeed. Today's official build worked fine. Clean flashed that one too.
[Verizon Samsung Galaxy S III] Fenuxx:
Still having the same problems on 0521 as on 0520. Can't receive calls, and can't hang up on those I make. Completely clean flash as before.

Restoring my nandroid of 0517, everything works fine. I also did a complete reinstall of 0517, and again, everything works fine. This is, again, happening with the default kernel included with the ROM, as well as LeanKernel

My method (in case you're wondering) is:

Boot to TWRP, wipe system, data, cache, dalvik, and internal storage (data/media)

Install ROM + GApps

Boot to system, and sign in. First thing I did after all my apps freshly re-downloaded from the Play Store was to test calls.
[Verizon Samsung Galaxy S III] mastamoon:
Do you have problems on official?
[Verizon Samsung Galaxy S III] Fenuxx:
Just did a quick flash of the official 0521 (wiped everything, of course). Didn't sign into my Gmail this time, but I can make and receive calls just fine with it.
[Verizon Samsung Galaxy S III] Hybridnoob:
Everything works like a dream here on 5/17 and 5/20! Thanks, Masta :cool:

I'm sorry a few people are having issues, but I thought it was important to let Masta and everyone else know it's working great for some too!
[Verizon Samsung Galaxy S III] MG386:
Depends on your definition of clean, like I said, I cleared caches and formatted system. I did not clear data partition.
[Verizon Samsung Galaxy S III] alee:
5/20 and 5/21 have not given me any luck with BT. Going back to 5/17 and everything works right away.
[Verizon Samsung Galaxy S III] jguns112:
On 5/20 I had the same issues as others are reporting with incoming calls and hanging up. 5/21 seems to have fixed them though!
[Verizon Samsung Galaxy S III] icedmayhem:
Just noticed on unofficial you still have the 3.4.41 kernel but official builds are now up to 3.4.45. Any plans for this to be part of it
[Verizon Samsung Galaxy S III] sivarticus85:
To those having issues with phone not answering/hanging up, after I wiped dalvik and cache it worked just fine. Just putting it out there.
[Verizon Samsung Galaxy S III] mastamoon:
Looks like the issue is part of the ril cleanup. Something about low signal causing some buggyness.
[Verizon Samsung Galaxy S III] prototype7:
Yeah, I was just going to say I got the hang up issue on a test build of slim with the RIL patches. It was in a low signal area, but couldn't reproduce it with 4 more calls in the same spot (to different people though, so it could depend on their signal as well). It went to voicemail, I left a message, hit the button and it turned grey but didn't hang up. Pretty funny though, I didn't notice for a few seconds and kept wondering why my screen was flickering every time my finger waved over the sensor.
[Verizon Samsung Galaxy S III] goldsmitht:
Makes sense, had the issue in my basement TV room, bad service there.
[Verizon Samsung Galaxy S III] myk.robinson:
For whatever it's worth, I had issues even when the phone was showing full signal. I did not do a clean install or cache wipe, if that matters. On the next release, I'll run a backup and try a clean install. Not sure that it will make a difference though, because if I dirty flash a previous build, without wiping any cache, the phone goes back to working fine again.
[Verizon Samsung Galaxy S III] mastamoon:
hrrrm.

Well there was a new patch uploaded so maybe that will clear this issue up. Mine worked fine all the times I tested over the past 2 days.. then last night I made a fake call to 'the man' to get my kid to go to bed and got the couldnt hang up bug. Couldnt bring the phone app up and in the dropdown it said unknown.. was weird, had to do a battery pull. I didnt take notice of signal strength but in general I have about 2 bars in my house.
[Verizon Samsung Galaxy S III] airmaxx23:
Could someone please tell me where and how to report this, I've asked in the official thread but no one seems willing to help. I can replicate this on any device running CM10.1, using a long notification tone makes it easier to notice.
[Verizon Samsung Galaxy S III] betam4x:
Call hanging up and touch tones still busted on 5/21.
[Verizon Samsung Galaxy S III] mastamoon:
Its a known issue now, work is being done on it but if it isnt resolved by build time, ill leave the new RIL stuff out. Flash to official for the time being.
[Verizon Samsung Galaxy S III] Fenuxx:
That would make sense for my issues as well. I get about -100dBm on LTE, and about -80dBm on 3G typically at my place.
[Verizon Samsung Galaxy S III] mastamoon:
5/22 build in OP

-- removed wifi driver updates to see if they are effecting my battery life

-- removed RIL updates till the call issue is sorted out

-- added invisiblek's kernel for testing korg/caf merges

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] Aali1011:
Regarding the Camera I don't know if my device has gone bad or if it is kernel related but. When i take a picture on the screen the the time of viewing everything is ok. After taking the photo and viewing it there always seems to be a black mark. Nothing is on the lens and this has only started happening recently. Its touch and go as well. All the photos from today i took have it some from the other don't.
[Verizon Samsung Galaxy S III] mastamoon:
Having some serious graphical issues mostly if I have a Facebook chat head pop up while the phone is locked/screen off. Screen on will make it go bananas especially if I pull down the notification bar while at the lock screen.
[Verizon Samsung Galaxy S III] lostwhat83:
Don't know where to report it.. Maybe here. Someone correct me if this isn't an ok place to post a logcat...

Restart phone. When phone done booting make it do that "error". Once that error happens:

Open terminal

Su (give root access)

Logcat -d -f /sdcard/logcat.log *:v

Post logcat from sdcard into this forum

Again if this is the wrong place to post logcats please correct me. I'm just trying to help out.
[Verizon Samsung Galaxy S III] mastamoon:
Disabling hardware overlays fixes.

InvisibleK fyi ping.
[Verizon Samsung Galaxy S III] Aali1011:
Thanks for the reply masta. Any suggestions as to what i can do or look into.
[Verizon Samsung Galaxy S III] alee:
Something like that happens for me if I pull out my headphone from the jack while playing music on the lock screen.
[Verizon Samsung Galaxy S III] goldsmitht:
On #5/22, and hang up, dialtones, and answer bugs all fixed. Mist have been whatever you reverted. Had some screen glitches, but after reboot, I can't force them again.

Oh well, alls working great again, sorry...

:what:
[Verizon Samsung Galaxy S III] ddggttff3:
hay mastamoon, just a FYI, looking at the latest code revision for the RIL fix, it seems they fixed the hangup bug, and timezone bug. Any way you can add the latest revision for a build tomorrow? id love to test it out. Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
Yeah if it's working it will certainly be added for tomorrow's build.
[Verizon Samsung Galaxy S III] mastamoon:
That's really odd. Haha, I'll have to think about that one. Can you post some examples?
[Verizon Samsung Galaxy S III] Aali1011:
Nothing in this one taken a day ago.

Took this one before the top one.

Black Spot

Black Spot

Screenshot:

Actual Photo:

Camera is set to the full 8mp saving to the sdcard and super jpeg quality. Other then that everything is normal. I even took some compressed air to the phone to blow anything that may be in there out with no luck.
[Verizon Samsung Galaxy S III] Stupifier:
Holy sh*t. Huge battery drain improvement seen using this build.

I was on 5-17 unofficial and noticed issues with wake locks and high battery drain while phone is not in use. I'm talking like over 50% battery drop while I sleep overnight.

I'm now on this latest unofficial (5-22) and seeing almost the exact opposite. I woke up just now and hardly see any drop of battery while I was sleeping.

Just wanted to report my vastly different experience between your 5-17 and 5-22 unofficial Masta.
[Verizon Samsung Galaxy S III] goldsmitht:
You running stock kernel?
[Verizon Samsung Galaxy S III] Stupifier:
Sorry did not mention. I'm running on Ktoonz Kernel (default settings) under both 5-17 Unofficial and 5-22 Unofficial. I also am running Greenify on both. I'm greatly enjoying the improvement I'm seeing in 5-22.

-With my phone just sitting, BetterBatteryStats is reporting a 1.3% drop per hour in my battery.

-Before, while on 5-17 build, I was experiencing at times up to 10% drop per hour while phone was just sitting. At best I would sometimes get 4% per hour drop.
[Verizon Samsung Galaxy S III] mastamoon:
The only thing I can say is there is a piece of dust or something on the lens. The last 2 pictures show why this is likely. When you are taking a picture with the camera and are fully zoomed out, you are not actually seeing the whole picture on the screen. You miss a good chunk all the way around. When you actually view the picture in gallery, you see the full picture and now see the dust that is on the edge of your lens.

That's the only thing I can think of. Doesn't look software based, that would be more block/pixel looking. And when you zoom, which you probably did in the first photo where there is no speck.. that part of the lens/picture is thrown away. That would explain the come and go part of it. If you want to really test, go back to stock and take some pictures and see what happens. That would tell us for sure.
[Verizon Samsung Galaxy S III] mastamoon:
5/23 builds in the OP

-- Download 1 has the new RIL included again

-- Download 2 has the current RIL included

-- brought back 2 of the Wifi patches to see if battery life changes compared to last night
[Verizon Samsung Galaxy S III] cesium:
Hey masta, is there a way to enable softkeys on these builds? Scoured the settings menu but didn't see anything
[Verizon Samsung Galaxy S III] mastamoon:
Gotta edit the build prop manually.
[Verizon Samsung Galaxy S III] cesium:
Ahh that explains it, thanks! Will look into it :)
[Verizon Samsung Galaxy S III] masri1987:
Masta I know it's silly, but is there anyway to add 4 rows to quick settings tiles?
[Verizon Samsung Galaxy S III] myk.robinson:
[MENTION=2963287]mastamoon[/MENTION], i tried today's build with the new RIL, dirty flashed on top of the 05/17/2013 build. Happy to report, my phone rings, I can hang up just fine as well :)

Thank you, sir.
[Verizon Samsung Galaxy S III] Aali1011:
No zooming done but I am very well open to the idea of going back to stock and testing. As i said i have tried cleaning the lens externally and tried using compressed air to see if it would move possibly. As for just missing a chunk of the picture when fully zoomed out is there a reason for that? I have noticed that and always thought of it as a glitch or a bug and simply got used to it. I ask now out of genuine curiosity.
[Verizon Samsung Galaxy S III] iofthestorm:
The screen is widescreen but the image sensor is 4:3. The camera app used to just show the full image and have buttons in the remaining space IIRC but I think since 4.1 or 4.2 Google decided for some reason to use the full screen for the preview and cut off the top and bottom parts.

I think this answers your question, not sure if I understood correctly.
[Verizon Samsung Galaxy S III] Aali1011:
That it did thanks sir. So i decided to be a little intrepid and crack the phone open. Took some pictures with out the lens cover and still got the mark. Cleaned the cover and the CMOS sensor and tried a couple pics with and without the back and no difference. Gonna try going down to stock and seeing if it brings any change.

I was looking at the initial post and saw the recommended GAPPS along with modem and then there is a 3rd file. What is that file exactly the "SBL update"
[Verizon Samsung Galaxy S III] mastamoon:
That's crazy. That would be the oddest digital artifact ever if it clears up on Touchwiz. Still think it's something physical but damn...
[Verizon Samsung Galaxy S III] Aali1011:
So had the same affect going back to stock ICS. This time though i saw the blur on the screen in the stock camera. So i figure it is either the cmos sensor or something else has failed. Tough to say. Getting a new phone though so that is cool and will be back to the Masta goodness. BTW the new builds are having better battery life then before which is nice to have back.
[Verizon Samsung Galaxy S III] mastamoon:
Sounds like either part of the actual sensor went bad or there is dust somewhere you cant access/blow out. Nothing a new phone wont fix though! :P

Yeah battery life is back to what it was. I think that Wifi blob was causing some issues. Wont know till I go back to the CM kernel in the next build. :good:
[Verizon Samsung Galaxy S III] wareynolds:
Is download 1 the new RIL that appeared to be problematic or the new old one?

I am confused. I thought Cherry picks were what you put in that were not committed, but here you say download 1 only. Are we supposed to do these ourselves or is this supposed to mean that these changes are separated based on the download above with the New and Old RIL. If that is the case there are three links here but only two builds.

Thanks for clearing things up.

Walt
[Verizon Samsung Galaxy S III] myk.robinson:
After using it for a day, I switched to the "current RIL" build. I noticed on the new RIL build I had signal loss and dropouts in places that normally have excellent reception. With the current RIL build, reception is back to normal.

Any truth to this, or placebo effect?

All I can say is my phone seems to not like whatever is going on with RIL (whatever that is)
[Verizon Samsung Galaxy S III] mastamoon:
No it means that the new RIL cherrypick is in Download 1 only... Sorry for the misunderstanding :)
[Verizon Samsung Galaxy S III] mastamoon:
Really the code base is close to the same with some work done to make it more universal for more phones. It shouldnt effect signal strength really. Anything is possible I suppose. It looks like it will be merged soon as most device maintainers seem to be giving it the :good:, so hopefully your experience was 'placebo'.:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
5/24 builds in the OP

-- reverted 2 kernel commits to see if one of them was the cause of the bluetooth issues

-- repo sync @ 2:20PM EST

Anybody with bluetooth issues, please test and report back.

Thanks!
[Verizon Samsung Galaxy S III] WhammyDroid:
Are the wifi blobs still in the build or did you remove them?
[Verizon Samsung Galaxy S III] mastamoon:
The drivers are still in, the blob is out. If I'm wording that correctly.
[Verizon Samsung Galaxy S III] npro1464:
The call volume is driving me crazy on the Official ROM. Is it any better on here? Also, I flashed the radio package here (https://plus.google.com/104277415207525128383/posts/iAVpVPYqMtM) If I flashed yours would I have to do a complete wipe? Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
No complete wipe needed although I would do caches and system just to make sure.. Then flash rom and gapps.

I have had no issues with call volume and nothing in this build should make any difference but you never know.
[Verizon Samsung Galaxy S III] razorloves:
the radio package in the op is the same as the one in that g+ post. no wipes needed when flashing modem/rpm/tz

EDIT: ninja'd. lol. mastamoon answered above.
[Verizon Samsung Galaxy S III] cesium:
Flashed 5/24 dl1 over I believe it was 5-17 build (cleaned caches), and getting big drain and wonky stats from bluetooth despite it being off and not turned on. Battery life has been draining quite fast since flashing, despite not changing my usage patterns.
[Verizon Samsung Galaxy S III] ddggttff3:
Same thing here for me, but I have not had bluetooth on once. Wonder if its just a glitch in reporting, or is a bluetooth service somewhere eating up my battery?
[Verizon Samsung Galaxy S III] NegativeOne:
I'm on 5/24 with new ril. Getting bad artifacts still
[Verizon Samsung Galaxy S III] mpetruzz:
I'm using gosms pro and have no issues with MMS.

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] V3TTOO:
Weird. I am using stock on your 1/18 ROM with no issues.
[Verizon Samsung Galaxy S III] mastamoon:
I just installed my 1/17 MMS and sent MMS fine. Weird.
[Verizon Samsung Galaxy S III] sparkerjc:
LOL, some weird stuff with mms going on. Your 1-18 build works for me jsut fine, and group mms option is back. It was missing entirely on 1-17 for me. :confused:
[Verizon Samsung Galaxy S III] mastamoon:
OK, it looks like MMS doesn't like big file sizes. I can send sub 1mb files OK, but anything bigger fails.

I did increase some MMS limitations in the 1/18 build so I guess I went overboard.
[Verizon Samsung Galaxy S III] vdefender:
So glad for these A2DP revert builds!!! I jumped on 10.1 immediately when it released, but the scratchy bluetooth sent me right back to cm10. But even cm10 wasn't good for me, i would have to connect, start playing music, then make a phone call and then hang up, for the bluetooth to sound good. I just flashed your 1/17 build yesterday right over my cm10 and it upgraded perfectly, perfect bluetooth (i've only tested streaming), 4g to 3g handoff worked great on my 80 mile drive to and from work. I haven't once had to do airplane mode in the last day and half dropping in and out of 4g. AWESOME! I haven't found a single issue.. I'm not changing this ROM LOL!
[Verizon Samsung Galaxy S III] PerCompLLC:
Mastamoon - handoffs seem to work fine on 1/18 for me...
[Verizon Samsung Galaxy S III] mastamoon:
Glad its working for you! :)

Thanks. Seems to be fine here to, but I think I might be seeing some more -0dbm signal drops than usual. Ill keep an eye on it over the weekend.
[Verizon Samsung Galaxy S III] PerCompLLC:
I'll keep an eye on it as well and let you know what I observe.
[Verizon Samsung Galaxy S III] V3TTOO:
What is the -0dbm drops? Is that when it has no signal at all, or something else? Just trying to see what I should look out for.