yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ausman89:
Just curious, but how old is the phone you are using that you are having problems with?

My phone that I've had since day one of the S3 is working perfectly fine, but another phone I'm setting up that is brand new (got it on Friday) is the one I have issues with. I'm wondering if it has anything to do with a newer version of the S3?

Is there a chance that something changed? I'm just throwing ideas out cause I cannot figure this one out why only some phones are affected....?
[Verizon Samsung Galaxy S III] mastamoon:
Mine is a preorder phone and hasn't had issues on any of my recent builds.
[Verizon Samsung Galaxy S III] ausman89:
Yeah, same on my phone. No issues on it as I got it as a preorder. The issues I am having is on a brand new phone I'm setting up for someone else... Hopefully someone else with a new phone from the last few weeks can either confirm or deny any problems...
[Verizon Samsung Galaxy S III] mastamoon:
Have you wiped data on any installs on your "old" phone?
[Verizon Samsung Galaxy S III] ausman89:
No... Right now, I'm deathly afraid to try that. I probably should try it, cause that may help in the diagnosis...

However, that is the only thing (besides the age of the phones) that is differentiating the two phones. I restored a CWM backup of my "old" phone to the new phone and the new phone worked perfectly. I thought I had figured out a way to fix it, but as soon as you wipe it from there, the problems resume.

I have even tried installing CM10.0 (stable) and an old modem to the new phone and I still have an issue.

I am about to try a complete factory reset back to TW. I've heard conflicting reports that an original restore will work, but only on TW. Supposedly the problems still exist when you go back to CM. If I completely factory restore, I may try an alternate root/unlock method just for kicks to see if anything in the unlocking process screwed up.

---------- Post added at 08:01 PM ---------- Previous post was at 07:47 PM ----------

SON OF A $!(@&! When you do a wipe on a perfectly good phone, the issue will appear as well...

I just wiped my "working" and "old" phone and issue is now presenting itself.

SO, if anyone else doesn't want to experience my/our pain, don't do a clean install of CM until this is fixed.

Someone with some more programming experience than me... PLEASE HELP!
[Verizon Samsung Galaxy S III] mastamoon:
Damn! Sorry man. What baseband/radio are you running. I know you said you tried an old modem and cm10, but was that phone ever on B1?
[Verizon Samsung Galaxy S III] ausman89:
Yes, both were at one point.

Probably should have never updated my modem(s).

I believe the new one was on LK3 to start. My old one was on MA2. I updated both over the weekend.... Maybe that is the common link...?

EDIT: If anyone who has not upgraded their modem for awhile wants to be super brave and do a wipe/fresh install to the latest CM, that might help diagnose things if it is weirdly modem related somehow. If I am that person though, I don't touch a thing unless I really know what i'm doing... :(
[Verizon Samsung Galaxy S III] mastamoon:
I'm on B1 so I can't help, would be cool if somebody could. It's like there is a data base that is getting wonky info about being activated. Doing a restore copies over this database so no problem, once you wipe data, that database is rebuilt but with bad or empty data.

But if flashing an old modem doesn't fix, sounds like there is permanent "damage".
[Verizon Samsung Galaxy S III] Restola:
So any clean install of cm10.1 causes the activation issue after the first reboot and all subsequent reboots? But can be temporarily be fixed in settings? And this apparently started in the last week?

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] ausman89:
First boot has seemed to be fine for me, but the activation issue is even dating back to CM10.0 (stable) as I tried to fresh install back that far to hopefully jump before any issues appeared. I think something is somehow getting left behind during the fresh installs.

If you wipe the Dalvik Cache immediately preceeding booting inside recovery, I have had 100% success in things working correctly. (probably why an original boot from a fresh install has worked fine in my experience)

A simple ordinary reboot (after the intial boot after a wipe) is where the issue is present (and all subsequent reboots).

To "fix" the issue without wiping the Dalvik Cache, you can change the CDMA Subscription back to "SIM" and then go into Airplane mode, and then turn Airplane mode back off.

EDIT: I believe it started in the last week. I've had no issue on my "old" phone (I had been running Mastamoon's 3/12 unofficial), but was setting up a brand new S3 for another person I just got on Friday. I realized the issue on Sunday night. Today is when I wiped my "old" device and now see the issue there as well.
[Verizon Samsung Galaxy S III] goldsmitht:
not exactly sure which one it was, but i clean flashed a previous version of unofficial 10.1 and had no problems at all. i'm also on the latest modem and RPM and all is fine.

sorry, wish i had a better answer for you

:cyclops:
[Verizon Samsung Galaxy S III] cvsolidx17:
Last nightly I flashed from this thread was nearly a month ago. Has the reception been worked on since then? Thanks
[Verizon Samsung Galaxy S III] ausman89:
I flashed back to stock 4.1.1 using Odin and didn't appear to have any issues from my previous posts. However, once again, as soon as I go back to CyanogenMod the issue persists.

The only thing further I didn't try yet is doing the dialer factory reset. I may try that tomorrow....
[Verizon Samsung Galaxy S III] Stealth111:
I think you may have to odin back to 4.0.4 to successfully do a dialer factory reset. I have had to do it twice now myself.

Sent using Tapatalk
[Verizon Samsung Galaxy S III] SilentAce07:
I've done that. Save yourself the time. It doesn't fix it.

Wait. This is very telling. This is why an old build of cm was fine for me one day but not the next. Its because whatever problem is left from the newer cm install is not overwritten when flashing an old build. Fresh, old cm from feb 20th was fine. But coming from the newer builds, it was not. That should give a bit of a timeframe. I hope. I flashed cm10 fresh from a dialer factory reset and was fine. It was only when I flashed new cm that it occurred.

Also, know that there is no "damage" to your phone. The problem only occurs on a cm base, and it can be corrected with other ROMs (aospa, tw).
[Verizon Samsung Galaxy S III] ausman89:
So, just to clarify, has someone tried using odin back to 4.0.4, then doing a dialer factory reset, and installing CM from before February 20th and had it work successfully (even after subsequent reboots)?

I'm not too concerned about my phone right now, but if there is any method to making this work, I've got a new phone for another user I'd like to get fixed and get back to them.
[Verizon Samsung Galaxy S III] Stealth111:
I have... Matter of fact Just this weekend. I did from a February 3rd CM10.1 Nightly build, as well as the CM 10.1 M2 build from a week or so ago. No Problems on either one. I did encounter EXACTLY what you are going through now about a month ago roughly. I reported this February 5th, and I believe I got exactly ZERO responses or help to my post below! I proceeded to fix it myself via trial and error, until I got it working for good. I can tell you how I got back up and running totally fine now, if you want to try it... PM me...

http://xdaforums.com/showthread.php?p=37633801#post37633801
[Verizon Samsung Galaxy S III] V3TTOO:
Off the current topic

I know this is off the current topic, but does anyone know if there is a comparable CM10.1 Mastamoon Unofficial for the Epic 4g Touch, AKA S2? Something that is CM10.1 but just tweeked enough to work properly on the S2.
[Verizon Samsung Galaxy S III] NegativeOne:
That question doesn't quite make sense to me. These builds have cherry picks and reverts SPECIFICALLY for d2vzw. If you want to find cherry-picked builds for galaxy s2 you'll have to check those forums.
[Verizon Samsung Galaxy S III] V3TTOO:
Yes, that is what I meant, in a way. I was checking them out, and they seem to be pretty customized. Like Mastamoon's build for my S3, I was hoping for something similar for my S2. Stock Android with only a few cherry picks, but reverts for E4GT. Was wondering if anyone here knew of one with a similar semi-stock ROM. All I found were highly customized. Just need it for a work phone, so nothing fancy is needed.
[Verizon Samsung Galaxy S III] btonetbone:
Oops, delete.
[Verizon Samsung Galaxy S III] PerCompLLC:
Anyone else noticing general performance lags on the new 3.4 kernel? I'm talking about opening apps for the first time, swiping between homescreens, etc...

I'm on Masta's 3/18 unofficial.
[Verizon Samsung Galaxy S III] mastamoon:
Yep :( Seems to come and go.
[Verizon Samsung Galaxy S III] PerCompLLC:
Thanks! :D I just wanted to make sure that it wasn't just me... I imagine that it will get hammered out in the coming days.
[Verizon Samsung Galaxy S III] mastamoon:
3/19 build in OP.

- repo sync at 3pm EST
[Verizon Samsung Galaxy S III] d1ez3:
try the newest faux ultimate kernel
[Verizon Samsung Galaxy S III] ausman89:
I just got done using Odin to go back to 4.0.4, using the dialer factory reset, re-rooting, unlocking, and installing CM all over again....

My initial install of CM went just fine. I could restart over and over and the issue never appeared.

However, I tried to push my luck, and tried to wipe data/cache and then BAM! The issue comes back and now and I keep getting "NV" as the cdma subscription type upon each restart.

I at least got halfway to fixing it. I can at least get rid of the issue more permanently than the airplane mode "fix" or Wipe Dalvik Cache "fix", and I now know generically what triggers it, in being a data wipe only on an aosp CM installation, but not when coming from a TW ROM. Only when already on CM and wiping.
[Verizon Samsung Galaxy S III] Chris123NT:
Everyone having the NV subscription problem on reboots try this:

Set your subscription to RUIM/SIM and toggle airplane mode to get things back

Open build.prop and change ril.subscription.types=NV,RUIM to ril.subscription.types=RUIM,NV

I had the problem on a few builds about a month ago and that's how I had to resolve it back then.
[Verizon Samsung Galaxy S III] ausman89:
Thanks for the suggestion, but that isn't working for me.....
[Verizon Samsung Galaxy S III] sivarticus85:
Which build was the last before GSM tweaks were added?
[Verizon Samsung Galaxy S III] PerCompLLC:
Would you mind linking to it? I found one of faux's threads but I can't seem to find the right one. Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
I know my 2/28 build doesn't.. I was away the week when all the gsm stuff was sorted. Any of my March builds will have the gsm stuff in it though.
[Verizon Samsung Galaxy S III] cclarke99:
+1 - I found something but it borked my install and had to dirty flash over it.
[Verizon Samsung Galaxy S III] dpaine88:
Can anyone tell me when the 3.4 kernel started being included?
[Verizon Samsung Galaxy S III] PerCompLLC:
Yesterday. Masta's 3/18 unofficial was the first of his to include it. I believe CM merged the kernel yesterday as well.
[Verizon Samsung Galaxy S III] rampantandroid:
Did you guys get your kernel here?

http://faux.androidro.ms/d2vzw/jb42/
[Verizon Samsung Galaxy S III] WhammyDroid:
With the 3/18 build, is anyone seeing the phone crash when listening to music with headphones? I am using Google Music and the phone completely locks up when the screen is off. I have had to pull the battery 10 times today.
[Verizon Samsung Galaxy S III] termleech:
So for me the second core never hotplugged on. Probably some of the sluggishness is due to that. In general seems like the 3.4 wasn't quite ready yet but hopefully they fix it up fast.
[Verizon Samsung Galaxy S III] cclarke99:
I did. Flashed it using TWRP, wipe cache and dalvik then rebooted to a black screen. Just tried again with the same result. This time I wiped first then flashed.
[Verizon Samsung Galaxy S III] rampantandroid:
OK, well...I'm sitting on an old February build from masta because beyond the back button oddness, it works. I assume the current KT747 kernel still works on the latest 3/19 build?
[Verizon Samsung Galaxy S III] goldsmitht:
nope! will cause a black screen on boot. new CM10.1 is built with 3.4 kernel, and not compatible for some reason.

:cyclops:
[Verizon Samsung Galaxy S III] ausman89:
Another update on this issue... I have actually got things working by starting on Mastamoon's 2-15 unofficial after an Odin back to 4.0.4 stock. I've been working my way up, installing 1 update at a time, checking to see if I break things.

I got up to the 2-28 Mastamoon unofficial with things still working.

Moving on to Mastamoon's next 3-12 unofficial broke things and the cdma subscription was always set to "NV" on a reboot.

I also tried the CM10.1 official M2 release from 3-4-13. That also broke things as well.

Right now, I'm stuck at the 2-28 unofficial from Mastamoon as the last working ROM I have tried.

SO, I am using Mastamoon's 2-28 unofficial without any issues. At some point between his repo sync on 2-28, and the 3-4 official M2 release, something has been added to the base CM code that is causing the issue.......
[Verizon Samsung Galaxy S III] sivarticus85:
Sound like GSM to me. I just asked masta about it today. The first GSM build was after the 2-28 build. I would bet it may have something to do with that.
[Verizon Samsung Galaxy S III] SilentAce07:
Somebody in the Jedi thread just said they toggled mobile data on and off and it fixed it even after reboots for their rom. I find that hard to believe because I tried everything under the sun while on CM, but if someone can verify that, it'd be great.
[Verizon Samsung Galaxy S III] ausman89:
Agreed.

I'm too tired to purposely break things again tonight.... I will break things again tomorrow, try this suggested fix, and report back, unless someone else beats me to it.

I will say though that I will be extremely pissed off if that fixes things. Like you, I've tried everything I could think of. It seems dumb it could be such a simple thing.
[Verizon Samsung Galaxy S III] Obaterista93:
I saw someone post that toggling airplane mode and then switching from NV to RUIM/SIM fixed it for them. When I got the activation screen I tried it and it worked.
[Verizon Samsung Galaxy S III] ausman89:
Nah, the airplane mode trick is just temporary. As soon as you reboot the issue comes back.

Another short-term fix is to wipe the dalvik cache before a reboot (or really during since you have to be in recovery). But, same thing here as with the airplane mode. Next normal reboot and the issue is back....
[Verizon Samsung Galaxy S III] Obaterista93:
Ahh, didn't notice you meant one that'd persist between reboots.
[Verizon Samsung Galaxy S III] PerCompLLC:
Had an SOD this morning and had to do a battery pull. Went back to Masta's 3/13 unofficial with the 3.0 kernel and loaded LeanKernel 2.9. Can't afford SODs. I'm sure it won't take long before the other kernel devs get on board with the 3.4 kernel. (I hope)
[Verizon Samsung Galaxy S III] SilentAce07:
I guess a bandaid fix to the problem would be to script a dalvik/cache wipe on every reboot.

Still bothers me that there's some type of unsolved issue though.
[Verizon Samsung Galaxy S III] mastamoon:
Sounds like we are in need of a 3.0 revert build lol. And a GSMless build.

Just gotta figure out what to revert, always the fun part!
[Verizon Samsung Galaxy S III] goldsmitht:
been trying to follow this, and not sure if this helps, but one thing about the GSM angle:

i flashed CM10.1 clean to clear up a GPS issue i was having. it was before the GSM fix, but i have had no issues like you and a few others have had. Therefore, this leads me to think it is the GSM issue, however, that it also has something to do with your phones. Would suggest getting basic phone information together with others that are having this issue, and see if there is a commonality that could conflict with the GSM fix.

wish i could help more, but that seems to be the only thing that stands out.

:confused:

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Thanks for working on this!

Im currently running a build with a few reverts. I believe these were the commits that invisiblek did to get GSM working. I might have reverted more than I needed but it should be a good test. If it works, its obvious that the commits needed to get GSM functionality working will have to be massaged a bit to make everybody happy.

Build should be done in 10 minutes or so. Hopefully somebody can test.
[Verizon Samsung Galaxy S III] termleech:
The reverts in msm8960-common aand qcom-common are easy they are marked. Its the display-caf that is harder. I would just revert everything after 3/18. Probably eaisiest.
[Verizon Samsung Galaxy S III] mastamoon:
Thanks, ill take a look. I'm sure Ill get all the reverts needed then they will fix the issues the next day. :eek:
[Verizon Samsung Galaxy S III] termleech:
Lol well I think I saw invisiblek say he was gone for a couple weeks and he's been spearheading the kernel so it might be a little bit but who knows.
[Verizon Samsung Galaxy S III] mastamoon:
Here is the GSM Revert/Activation Fix TEST build.. http://d-h.st/5aW

Somebody who is having the issue, cough ausman89 cough, try this and let me know.
[Verizon Samsung Galaxy S III] luv2increase:
Can you use the 3.0 kernel on newest nightlys

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] mastamoon:
Doubtful, at least for awhile. I don't want to stifle development. The more feedback the CM guys get the better right now. Its not crippling anybody AFAIK.

I didn't think you ran my builds anyway since they weren't built with linaro?

Edit.. I just realized you might be asking if you can use a 3.0 kernel vs asking me to build with 3.0 kernel.. LOL
[Verizon Samsung Galaxy S III] PerCompLLC:
Unfortunately no...
[Verizon Samsung Galaxy S III] ausman89:
I just got through installing and checking and I'm still getting the activation error on this one...

Thanks for trying a build with a few reverts though.
[Verizon Samsung Galaxy S III] mastamoon:
DANG. Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
If your up for it, I suppose the next step is try all the officials between my 2-28 and my 3-13 and see when exactly it breaks. The GSM stuff I reverted was merged on 3-11. But that doesn't seem to be it, but really don't see anything else that would change it.. unless it was a binary/driver.

Anybody know what C2D blobs are? This change was made to theMuppets repo https://github.com/TheMuppets/propr...mmit/47a863aa595c7b25e5615a2cd64bd8ed36219c48 9 days ago. Maybe its this? This was done 4 days ago.. https://github.com/TheMuppets/propr...mmit/5316e9dc1f88cad05699792e780874632d3171f4 but believe those are display drivers.

ausman89, try 3-9 official.. 9 days puts us at 3-11.. coincidence? So try 3-9 official for ****s and giggles. Link http://goo.im/devs/cm/d2vzw/nightly/cm-10.1-20130309-NIGHTLY-d2vzw.zip
[Verizon Samsung Galaxy S III] termleech:
C2d2 is camera and andreno is graphics.
[Verizon Samsung Galaxy S III] ausman89:
I will try that one and let you know what happens. If it doesn't work, I'll just keep running through officials and see if I can nail down which one caused the issue... This could be another long day of flashing.
[Verizon Samsung Galaxy S III] mastamoon:
Thanks.

Id say start in the middle then ausman89... maybe flash the 5th or 6th official. That way we know what direction we need to look in.

http://goo.im/devs/cm/d2vzw/nightly/cm-10.1-20130306-NIGHTLY-d2vzw.zip 3/06 Official
[Verizon Samsung Galaxy S III] ausman89:
I tried officials from 3-9, 3-6, and 3-1. None of them worked.

I also went back to the 2-28 unofficial I haven't found an issue with and tested once more and it is still fine.

So, that makes it look like the issue is between the repo sync on the 2-28 unofficial and the 3-1 official nightly...
[Verizon Samsung Galaxy S III] mastamoon:
Wow, thanks!

I just finished a build http://d-h.st/sIe that I was going to ask you to test.. reverted the longpress button fix commit.. but it was commited on the 7th.. so the 6th should have worked if this was the issue.

Ill take a look again at the changes between 2-28 @ 3pm and whenever 3-1 official was built.
[Verizon Samsung Galaxy S III] mastamoon:
This is all of the commits merged between 2-28 and 3-2.

From what I can tell, the official 3-1 build got uploaded to goo.im around 12:02am PST (9:02pm EST 2/28) on 3/1.. my 2/28 build was repo sync'd around 3pm EST.

Anybody see anything suspicious? Me neither. :(

Stupid CM change-logs don't go that far back so no easy way to display the stuff below.
[Verizon Samsung Galaxy S III] ausman89:
I'm gonna complicate things. I just flashed this build and it worked.

I will go back and try the 6th one more time.
[Verizon Samsung Galaxy S III] mastamoon:
Lol crazy.
[Verizon Samsung Galaxy S III] mastamoon:
The 3/1 build should have worked too.. strange.
[Verizon Samsung Galaxy S III] goldsmitht:
for what it's worth, just tried Sons of Anarchy's B3, clean flash, and damn if i didn't get the dreaded activation bug as well.

think they are based on cm10.1 as well, don't think they did the new kernel, but i can now join the club.

one thing: Could it be because of the B1 base? About the time this started, i think was when B1 was released, and a lot of people updated to that radio and RPM. not sure how that would affect it, but hey, just thought i'd throw a few pennies into the pot to see if i could help.
[Verizon Samsung Galaxy S III] mastamoon:
Would be very strange indeed if it turns out to be the modem. I believe ausman89 has flashed older modems with no fix though.
[Verizon Samsung Galaxy S III] goldsmitht:
wouldn't think so either, but was just going over the time line and that popped into mind.

still, happened on another ROM, that i think is CM based. something they committed during that time line is doing it.

:cyclops:
[Verizon Samsung Galaxy S III] Rudy_Ruettiger:
your signal is still reported the same in dBM, however they changed the way the bars report signal
[Verizon Samsung Galaxy S III] mastamoon:
:victory:

So in an area where you would usually drop connection due to 3G/4G handoff, you stayed connected?
[Verizon Samsung Galaxy S III] mpetruzz:
Thanks! I just checked my signal and it's -98 which is what it was prior!
[Verizon Samsung Galaxy S III] kimsj756:
Yeah, thankfully I live in the busy area, so the signal doesn't fail unless I go into the building with a thick wall.

But, everything else is very smooth and good. I'm sticking with this for awhile as well.
[Verizon Samsung Galaxy S III] senorbuck:
Flashed the latest last night and it ran beautifully... except it was taking FOREVER to charge. I even flashed leankernel and enabled fast charge and it still took forever.

That normal?
[Verizon Samsung Galaxy S III] NegativeOne:
Your phone might have been doing post-flash stuff, like re-syncing, etc. This drains battery, making charging slow.

Can someone confirm whether or not the hand-off related changes can affect wifi? Seems like my phone is having problems with my work wifi now... keeps dropping
[Verizon Samsung Galaxy S III] mastamoon:
I have seen no wifi issues on mine going between work and home wifi.
[Verizon Samsung Galaxy S III] NegativeOne:
my bad. it actually does keep dropping. I'm not excluding the possibility that it's the access point. our wifi does have issues sometimes.
[Verizon Samsung Galaxy S III] PerCompLLC:
So far, yes. Normally I would have to toggle airplane when I hit the next town on my way to work in order to get data back when moving into a 4G area. This morning I didn't have to - the handoff was smooth. I've also had to toggle airplane mode at work as my building is in a fringe area. Haven't had to toggle yet today. Been here for 5 hours.