yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] heXacode:
Mine says EVDO A too.

Don't we have a secret code we can dial to get to one of the hidden menus like other phones have? Or did nobody ever find that out?
[Verizon Samsung Galaxy S III] Droidriven:
she has the same thing that the others have, she's just on an older build that doesn't require a SIM, still no stock MMS if I'm understanding her correctly

idk about your dirty unicorn but everybody on CM has the same issue after a certain point, builds before that were a little better and gets better as you go back but worse as you come forward to current.

---------- Post added at 09:02 PM ---------- Previous post was at 08:59 PM ----------

I've seen something about that I think but I've bounced back and forth through so much info I can't be sure but I can go through my history and go down the list of links and see if I can find it again if not I'll do more searches
[Verizon Samsung Galaxy S III] heXacode:
I'll go ahead and flash what she has and start nit-picking at everything.

Update: alright so I'm on the cm11 m10 snapshot ROM and the gapps package came with hangouts and stock SMS/MMS. I can confirm both work with MMS without having to add anything. This was on WiFi. Testing on 3g now...

Update2: MMS works on 3g for both stock and Hangouts app.

Here's a new find... upon looking at Hangouts APN settings it is using MetroPCS... Wtf?
[Verizon Samsung Galaxy S III] Droidriven:
what hidden menu are you looking for
[Verizon Samsung Galaxy S III] heXacode:
I'm not sure what each menu is called. It has one where you can change CDMA to gsm or both and other stuff on it. It won't do us much good but wanted to see info on it. No worries if you can't find it.
[Verizon Samsung Galaxy S III] Droidriven:
I found something about an app "Secret codes reveler" and I'm reading some things about Alogcats and using it to capture device secret codes

---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------

you are looking for secret dialer codes right?
[Verizon Samsung Galaxy S III] heXacode:
Alogcat is one way to do it. I just did it the easy way and googled for it lol. Didn't come up with anything yet.
[Verizon Samsung Galaxy S III] Droidriven:
try the app, it won't hurt.

---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------

I'd be satisfied with the older build for now until our wrinkles get pressed, what version is it?

---------- Post added at 10:29 PM ---------- Previous post was at 10:07 PM ----------

you said you've compiled Liquid, do you know which is the latest stable build for us? I like liquid so if I can get it I'd like to, CM is cool too but some builds don't have as many goodies.
[Verizon Samsung Galaxy S III] heXacode:
Couldn't get it to spit out MSL codes. Still working on it.

http://xdaforums.com/showthread.php?p=57235723

That's the link to your post from last night that I was asking for which ROM and gapps package that girl is using. I'm on it right now. Seems to be no issues except seeing Hangouts using MetroPCS in APN settings. It doesn't seem to be causing any issues. Just weird that I see no Verizon. Just MetroPCS and Sprint lol.
[Verizon Samsung Galaxy S III] Droidriven:
sorry, that was the main page for the DLs, I wasn't sure if clicking the links on the page for the builds would start a download I didn't need yet so I gave you the main page, that's why I also listed which build and gapps she had, I couldve made it easier for you I know.

---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------

I checked with her and she is where you are, no SIM and all works even MMS
[Verizon Samsung Galaxy S III] heXacode:
This is where we will have to base our work on and work forward to fix the issues.
[Verizon Samsung Galaxy S III] ScottDB:
Look in your original build.prop - the ROM codename would be the value for ro.product.device, which in the case of my SCH-S968C - H1 would be "d2tfnvzw". Is the ro.product.device different for the H2 model?
[Verizon Samsung Galaxy S III] Droidriven:
I can tell you that without looking, yes ours are the same.

---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------

what else from H2 do you need?
[Verizon Samsung Galaxy S III] ScottDB:
I don't need any thing else from H2 - I was just curious since you had suggested several different names (d2stvz...)
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=3691964]rixter13[/MENTION] if you roll out a CM12 can you make sure we don't have the misc. drain that the others are having?

---------- Post added at 11:26 PM ---------- Previous post was at 11:21 PM ----------

oh, I was just suggesting because straight talk uses devices from other carriers so thus d2stv(verizon), d2sta(at&t), d2sts(sprint) and so on.

a straight talk build for us wouldn't work on the straight talk at&t or other carrier s3s would it? So I just suggested because just saying its a straight talk build could get confusing depending on which variant

---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------

or would it just be given a variant for d2vzw and branch from there?
[Verizon Samsung Galaxy S III] ScottDB:
I wouldn't think that a build for the d2tfnvzw would work on other carriers, since they would have different RILs.
[Verizon Samsung Galaxy S III] Droidriven:
I was just saying that d2vzw is what we already have so it needs a modified designation to what is already being used so it doesn't confuse a user, if our build is labeled the same as the builds we are using from the verizon device then how us anyone (especially new) gonna know the difference between ours and the regular d2vzw?

---------- Post added at 11:43 PM ---------- Previous post was at 11:40 PM ----------

yeah, that was my point so in builds specifically for straight talk we would have to differentiate between the carrier versions that straight talk has so that they don't get confused or mixed up if someone didn't know what they were looking for or looking at, it was just a thought

---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------

in other words give the straight talk verizon a modified name from d2vzw

give the straight talk at&t version a modified name from d2at&t

and so on just to keep them separate
[Verizon Samsung Galaxy S III] rixter13:
She was using 8 SMS, and did the MMSC fix in that SMS to get her MMS to work. As for your hangouts, did the instructions I posted in the first post of this thread not work for you? I was able to get chomp to work, but I had to use the MMSC fix in it as well.

As for the development of the rom, I would really like to get to the root of our problem and send the patches out to CM, so our phone will work with other roms and all their awesome features. As far as a "we should all be on the same rom" lets get CM running (I will release the process I used once I have a functioning rom) and chip away at this road block from there.

Now (because I am really not a heartless robot) I am terribly sorry to hear about you having cancer. I have a friends dad that currently has brain cancer and its been very rough on all of the family. I hate to see anyone go through that, and I wish you all the best with fighting it. I will definitely keep you in my prayers.
[Verizon Samsung Galaxy S III] Droidriven:
so you have a baseline to work from
[Verizon Samsung Galaxy S III] rixter13:
Liquid is based on CM, it just has a lot of goodies packed in with it (along with MUCH better battery life than most of the other roms I have used). The last one working without a SIM was late August. This goes back to the 'Lets fix things upstream' that I just mention in the post before this one.

as for secret codes, most are removed from verizon based roms, but *#*#INFO#*#* gets you into a menu where you can set some of the radio options. I have messed around in there but can't seem to gain much.
[Verizon Samsung Galaxy S III] rixter13:
If there is a patch out there for the MISC drain I will apply it, but as far as digging and trying to fix it, one thing at a time...

1st we need a rom that boots

2nd work on fixing the RIL's so we don't need the sim card

3rd work on fixing the RIL's so we can use MMS without a 3rd party app

4th start working on 5.0 specific fixes (my #1 5.0 complaint right now is bluetooth not saving my paired devices)
[Verizon Samsung Galaxy S III] Droidriven:
gotcha and yeah the BT issue would kill it for me too. Ok then, one step at a time.
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=3508760]heXacode[/MENTION] have you seen this? Its for setting ST APNs on devices that use a SIM, I think its for devices using the BYOP, I know we are using devices native to ST and not from BYOP but if this is how they setup devices for ST with a SIM then there may be something to it, just an idea if you haven't seen or tried this

if the ROM or stock MMS looks for the APNs it needs from the SIM then there must be a way to apply the APNs to a SIM instead of the device, I don't know about these kinds of things but if the SIMs have APNs stored on them then there has to be a way to put the right APNs on the SIM so that the right APNs are found when the SIM is checked, is it possible to overwrite the APNs on a SIM with a new set?

http://www.straighttalk.com/wps/portal/home/support/apn
[Verizon Samsung Galaxy S III] rixter13:
This is an interesting read...

http://www.slideshare.net/leafjohn/ril-and-android-telephony
[Verizon Samsung Galaxy S III] Droidriven:
could this be used on the SIM?

http://www.dekart.com/products/card_management/sim_explorer/

---------- Post added at 04:14 PM ---------- Previous post was at 03:23 PM ----------

I found an app called "offline SIM APN database" in playstore, it describes pushing the app to system so that it works, worth a try?
[Verizon Samsung Galaxy S III] heXacode:
I've tried that before. Didn't do any good. I don't think SIMs are gonna do us any justice at the moment. As I stated chomp SMS grabbed APNs from our devices (with and without a SIM in). Its getting it from somewhere. That was the initial clue that there's a foul up going on that stock and Hangouts aren't looking in the right place or missing something.

That's an interesting read indeed. I noticed it discussed sockets. Sockets are important for MMS and I wonder if maybe there is a missing one or error in one of the sockets for this? We should do logcats on MMS on a ROM that has issues and see if its a socket or different error spitting out.

Also why not take a good ROM with no MMS issue and back trace it to the next release to see which commits started killing it? Possibly even revert the commits for that and for SIM stuff?

---------- Post added at 10:18 PM ---------- Previous post was at 10:15 PM ----------

I would say we hold off on that SIM stuff and focus on reverting commits for it because our goal is to get rid of the issue in ROMs that request SIMs be present.

---------- Post added at 10:28 PM ---------- Previous post was at 10:18 PM ----------

Have someone with the MMS issue try it. I wished we had slot ROMs so I could go back and forth on ROMs easily without having to wipe and restart lol.
[Verizon Samsung Galaxy S III] Droidriven:
I was trying to find an easier solution than modding the ROM, I was going on the thought that if we can get the right APNs onto the SIM itself then nothing needed changing and everything could go forward instead of back, if it can be done then everything can be left the way it is and save a lot of time, backdoor simple kind of thing.
[Verizon Samsung Galaxy S III] rixter13:
I am pretty sure its this commit that caused the need for the SIM cards...

https://github.com/CyanogenMod/andr...mmit/cbc30ced486fe9b4ccec23c0538ad9598da2a8f8

I am trying to get a hold of invisiblek to see what this fixed (or why it was needed). It may be as simple as writing that file slightly differently to fix the need for the SIM, I am not sure exactly.
[Verizon Samsung Galaxy S III] heXacode:
You bring up a good point but remember not all of us are going to have a SIM card laying around and there are those who don't want to bother obtaining one for that matter so we are kind of just trying to hit 2 birds with one stone and take care of all the issues so no one will have issues like we do now.
[Verizon Samsung Galaxy S III] Droidriven:
Gotcha, I agree with that for a long term fix and its very needed and very well needs to be the end result, a temp fix would be nice though, the real fix is gonna take a while
[Verizon Samsung Galaxy S III] heXacode:
Oh trust me... some of us are still looking for a temp fix but it gets more difficult on the newer ROMs and I guess mixed results for some from what I've read. 3rd party apps are pretty much the temp fix for now.
[Verizon Samsung Galaxy S III] evertking:
Good to see people still working on this phone.. I get two emails a day looking for the stock tar! Lol seems to be a popular phone.. The tar, Which I handed off to motorhead as I got rid of the phone when things started going south with ROMs and mobile data. My daughter has it now with slim 8/12 on it and works flawless and strong 3g signal. Anyway.. Just stopped in to say good luck and to find out what ROMs are working on this phone now? Any 5.0?
[Verizon Samsung Galaxy S III] matt_man:
Mastamoon has CM12 unofficial working on this phone. I'm using it as my daily driver right now.
[Verizon Samsung Galaxy S III] PSG4m3r:
[MENTION=5280283]evertking[/MENTION] Mastamoon has a working CM12

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] kenny1974:
CM 12 is still kind of buggy, but I've been using it for a couple of weeks with all the updates
[Verizon Samsung Galaxy S III] PSG4m3r:
Quick question, has anyone here tried Dirty Unicorn rom? I think someone from the rooting thread said they used that one and it worked perfectly, but I don't see a d2xxx build on their site. I'm trying to find a rom for my friend that has everything on it working.

I found the download page for it: https://plus.google.com/111181454853354072682/posts/2VEmsreeSsk

Sent from my SCH-S968C running CM11

---------- Post added at 12:06 PM ---------- Previous post was at 11:13 AM ----------

Here's a good guide on compiling rom builds. This is for DU, but I'm sure CM isn't much different with compiling.

http://therealmofu.com/wp/?p=373

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] Droidriven:
[MENTION=4812547]PSG4m3r[/MENTION] hexacode was on DU before he flashed the CM that MrsELF used, ask him what build he used.
[Verizon Samsung Galaxy S III] heXacode:
This is the DU link to the build I used for awhile. Maintainer does not update it anymore.

https://www.androidfilehost.com/?fid=23622183712457141
[Verizon Samsung Galaxy S III] rixter13:
Getting some build errors http://pastebin.com/UGvfrPqE hopefully I can get those figured out and get a working rom soon :) If that happens, I will start trying to run down the need for the SIM.
[Verizon Samsung Galaxy S III] rixter13:
Glad I digging into this... found a big KEY here, https://github.com/CyanogenMod/andr...mmit/5cbd7de5e5c2e3fbcca1861038031d84945fc382

Not sure what needs done, but its definately worth mentioning...
[Verizon Samsung Galaxy S III] heXacode:
That's what I said before. The MMSC has been the issue. The APNs are here on our phone. What's communicating to grab it is lost in translation.

I forgot to add that adding MMSC still didn't work in most cases so what you mentioned in the quoted box is exactly what we need to get stock, Hangouts and whatever working without fiddling around with it.
[Verizon Samsung Galaxy S III] rixter13:
Just found this in the code...

// Hack for Lollipop
// The system now queries for SIM status before radio on, resulting
// in getting an APPSTATE_DETECTED state. The RIL does not send an
// RIL_UNSOL_RESPONSE_SIM_STATUS_CHANGED message after the SIM is
// initialized, so delay the message until the radio is on.
[Verizon Samsung Galaxy S III] evertking:
Just flash and go or any tweaking gotta be done? Does it have data drops?
[Verizon Samsung Galaxy S III] kenny1974:
If you're coming from anything other than CM12 you'll need to wipe system and start fresh. Use the correct gapps as well. You'll have to insert a sim card, whether its active or not, to get data
[Verizon Samsung Galaxy S III] evertking:
Lol.. Well hello Kenny! Thanks. I got a tmo sims card around here somewhere.

Let me guess... No MMS?
[Verizon Samsung Galaxy S III] kenny1974:
You guessed it. Lol. I use hangouts and have no problems getting MMS with it. The camera doesn't work on cm12 either
[Verizon Samsung Galaxy S III] heXacode:
Did you have to enter the MMSC manually in Hangouts? I may jump to CM12 if you have no issues except camera. What about that flashable zip from the other thread that fixed the camera issue in 4.4.4? Would that even work?
[Verizon Samsung Galaxy S III] kenny1974:
Hangouts worked for me without doing anything. I may try the zip later to find out
[Verizon Samsung Galaxy S III] Droidriven:
Well it seems from your posts that you've found the "nail", but the question is where is the "head"? Let's bury the head of that nail so we stop catching our feet every time we step on it! Lol
[Verizon Samsung Galaxy S III] heXacode:
Kenny stated that CM12 is showing no MMS issue. Just the SIM card issue. So CM10 and CM12 are working well except camera issue in CM12.

I'm looking into exactly what and why the CM team borked the MMS issue in CM11 but its fine in CM10 and 12. Makes no sense but its all in the commits and comments. Seems ass backward to me.
[Verizon Samsung Galaxy S III] Droidriven:
Ok, so can we take the setup for MMS from CM12 and apply to the d2lte ROMs to get the MMS straight with them and then find out how to do away with the SIM? Working MMS is good but still has the SIM issue.
[Verizon Samsung Galaxy S III] heXacode:
Its gonna be more work than just adding. Rixter is on that part. I would think people should move forward to the latest instead of being on something that may potentially never get resolved.

All that's needed in CM12 is camera issue fixed and possibly get rid of SIMs but then again its been stated that Verizon won't work without SIMs now. That's a question to ask... if we find a way to revert that will that mess with data? Will we continue having data without it? Someone mentioned that but I haven't found any source stating all phones must have a SIM in order to use Verizon's tower now.

I think that's a gray area right now because there's plenty of straight talk users on cdma-v without a SIM and working fine without data issues. Verizon must have pushed a new rule out for lollipop and require SIMs.

I don't know. I'm working relentlessly collecting all info and hope to help rixter resolve this. There's just too many loose ends at this moment.
[Verizon Samsung Galaxy S III] Droidriven:
From what I understand, the SIM issue is coming from the fact that Verizon requires a SIM on its 4g devices to regulate its LTE service, but our devices are 3g so would our devices be restricted without a SIM? The Verizon 3g devices don't require a SIM to receive 3g data do they? Is it even possible to get 3g on a Verizon fitted ROM anymore? Are we gonna have to resort to building ROMs based on our devices and work our way up instead of trying to resolve the issues in the vzw or lte based ROMs to get around our issue? Is it even possible to force these ROMs to function in a completely opposite manner than they are inherently built to function?
[Verizon Samsung Galaxy S III] heXacode:
Yeah I'm aware the SIMs are for obtaining 4g connection but keep in mind we still need the SIMs just to have data regardless of only having a 3g only phone. My concern is would data still be there after reverting the need for SIMs. We won't know that till we find out what to revert and build the ROM. I agree we should have a couple maintainers build ROMs specifically for our phones so we aren't running into all these issues. We will get there no doubt.
[Verizon Samsung Galaxy S III] Droidriven:
Yes, I agree, my questions were along the same lines as your concerns about whether or not removing the SIM on verizon based roms would even work or not, it kinda seems to me like so many knots would have to be untied to remove the SIM dependency that everything probably wouldn't stay together anymore, but if so then using a SIM would be fine as long as it works, but like you said that would kinda suck for someone that doesn't have an extra SIM laying around, but then again I guess those users could find other ROMs to use even though some of the other ones probably wouldn't be as good or as cool, can't have everything the way we want it though.
[Verizon Samsung Galaxy S III] kenny1974:
MMS is only working with 3rd party messaging apps. I use hangouts and didn't have to change any settings for it to work. I'm using the CM12 as a daily driver. Its got its problems, but that's to be expected with a new version of android.
[Verizon Samsung Galaxy S III] heXacode:
You didn't mention that before. Technically Hangouts isn't suppose to be a 3rd party app as its suppose to come with the core gapps package. At least it works.
[Verizon Samsung Galaxy S III] rixter13:
Well... I am gaining (I think), got the CM12 rom to compile finally, plug in the phone to the computer and it shows SCH-S968C (instead of the SCH-I535). Having issues with getting mobile to work, but everything else looks good.

I had a strange issue, I nandroided back to my previous CM12 rom (it was working fine) and I can't make any calls out, I can text and receive calls and mobile data works, but I simply can't place a call (fast busy signal). Looking into it further it looks like it was trying to use the phone number from my friends sim card (which is deactivated verizon), so I am not sure what to make of that.

RiXtEr
[Verizon Samsung Galaxy S III] Droidriven:
Is it acting like it goes to the SIM for everything it does or something? I was hoping that the SIM dependency wasn't buried that deep and linked to every function the device uses, seems like too many strings to cut, is it even worth the effort?
[Verizon Samsung Galaxy S III] PSG4m3r:
I'm trying to download the latest nightly, but it's going too slow on 1x lol. If you go to: http://www.cmxlog.com/11/d2lte/ you'll notice on the 12/17 nightly, it has "get imsi from sim on vzw variants" specifically for d2lte, along with other fixes and updates. Idk if this is a fix for our issue, or proof that CM wants vzw to go thru sim, but I'm trying to find out, just need a faster connection.

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] Droidriven:
Go hit one of the fast food joints with free wifi
[Verizon Samsung Galaxy S III] PSG4m3r:
Way ahead of you lol. I just installed the latest nightly, I'm gonna try taking my sim out and see if it makes a difference.

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] Droidriven:
If they found a fix for it then that will save rixter a lot of time

---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------

He may not even have to do anything else if the CM guys got it working unless he just WANTS to build for our device.
[Verizon Samsung Galaxy S III] PSG4m3r:
Nope, the new nightly doesn't fix the sim issue :(

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] Droidriven:
No new settings or options?
[Verizon Samsung Galaxy S III] PSG4m3r:
Nope. Nothing but behind-the-scenes fixes and updates

Sent from my SCH-S968C running CM11
[Verizon Samsung Galaxy S III] Droidriven:
Are you trying to say that CM is forcing the SIM depenency? Are they trying to stay with the times and convert to 4gLTE and do very little to incorporate 3g compatability? Are they mainly concentrating on the Verizon LTE device and not concerned with whether 3g works?
[Verizon Samsung Galaxy S III] PSG4m3r:
I'm guessing. It has LTE in the build name, so it'd make sense. It'd just be nice to have the option of 3G, other than just a preferred network speed. Hopefully rixter gets this stuff fixed for us in his build. Also, big thanks to rixter for putting so much effort into this! Can't wait to have a perfect CM based rom for this phone! :D You da man

Sent from my SCH-S968C running CM11