yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] prdog1:
This sounds to me to be a trustzone problem. That may be all you need of the firmware to make it work. Had problems with MB1 TW roms on MF1 firmware also and was able to fix them by just changing the TZ back to MB1. That why have been able to run any thing on MB1 firmware. :cool:
[Verizon Samsung Galaxy S III] prdog1:
Well. No MMS with any combination of firmware. ML1 is only modem with no signal at all and all other modems and firmware SMS only. :cool:
[Verizon Samsung Galaxy S III] chowner:
Yea :(
[Verizon Samsung Galaxy S III] smelkus:
I went from the 08/01 to 9/11 nightly. My GPS stopped working and I also have that bug where Bluetooth works when you place a call, but not when you receive a call. The NE1 modem worked fine though. There were some GPS changes recently. Toggling location access didn't work like it has a few times in the past.
[Verizon Samsung Galaxy S III] prdog1:
9/11- Mf1 Firmware- NE1 works. Ml1 doesn't. No MMS. Didn't try GPS or Bluetooth.

9/12- MF1 firmware- All Modems work. No MMS. Didn't test GPS or Bluetooth.

9/6 - MF1 firmware- ML1 modem works. Ne1 doesn't. MMS works. GPS works. Not great but weather bad here today. Didn't test Bluetooth.
[Verizon Samsung Galaxy S III] Hybridnoob:
9/8 - MB1 firmware and modem. SMS, MMS, Bluetooth (calling and receiving) and GPS works.
[Verizon Samsung Galaxy S III] vforaci:
I wonder why we haven't seen m10 yet?
[Verizon Samsung Galaxy S III] rhcreed:
Is that the firmware and the modem?
[Verizon Samsung Galaxy S III] prdog1:
Yes. All in one. :cool:
[Verizon Samsung Galaxy S III] Hybridnoob:
Yes, as far as I remember, it's the AIO (all in one) package.
[Verizon Samsung Galaxy S III] prdog1:
Ninja'd. :p
[Verizon Samsung Galaxy S III] Hybridnoob:
Yep, I was about to say that too!
[Verizon Samsung Galaxy S III] rhcreed:
Flash order is ROM - gapps - mb1 ? (After wipe/wipe) ?
[Verizon Samsung Galaxy S III] Hybridnoob:
What are you trying to do? Fix SMS? If so, check a couple of pages back - I posted instructions. You'll need to be on a nightly prior to 9/11 to safely use MB1.
[Verizon Samsung Galaxy S III] prdog1:
Ok. Looks like 9/8 last good one.

9/8 - MF1 firmware. ML1 modem. SMS, MMS working. GPS perfect. Bluetooth not tested. :cool:
[Verizon Samsung Galaxy S III] rhcreed:
Not trying to fix anything that's wrong, just want to be on the most stable versions. Also looking to improve Signal and battery. Thx..
[Verizon Samsung Galaxy S III] Hybridnoob:
To flash whatever firmware/modem you want, just go to recovery and do it. No wipes or ROM/gapps installations needed.
[Verizon Samsung Galaxy S III] stevey500:
This is somewhat of a newbish post. This phone I have is running cm11 perfectly, attempted updating to 9/08.

It updated perfectly with no FC's and ran great except for what's recently mentioned about radio issues.

LTE connects and internet works but calls/SMS are absolutely dead.

Baseband appears to be MB1 and unsure of what firmware version is flashed.

I downloaded the 18mb zip previously mentioned and flashed in the latest TWRP recovery with no errors but it is still showing MB1 as baseband and SMS/Calls are a fail.

Bummer.

I am sure that flashing back to the last milestone/snapshot will result in broken data/fc's.
[Verizon Samsung Galaxy S III] Nomad1600:
Prdog, did you ever confirm that Bluetooth worked?
[Verizon Samsung Galaxy S III] prdog1:
I have no way to test it. Dog ate my Icon headset. :cool:
[Verizon Samsung Galaxy S III] dmginc:
Try using CWM. TWRP has been giving people issues for a while.
[Verizon Samsung Galaxy S III] prdog1:
Latest TWRP works fine. There was only one version that had problems making backups and had to turn on compression. :cool:
[Verizon Samsung Galaxy S III] stevey500:
Whelp, I tried installing the latest CWM d2vzw and flashed the 18mb firmware/modem file and re-flashed 9/08 previously mentioned and my baseband is still hanging out as MB1 instead of ML1 with no call/SMS abilities but rocking full working dat/LTE. :(
[Verizon Samsung Galaxy S III] prdog1:
That firmware file is MB1. Here is MF1 and Ml1 if want to try. Flash the MF1 Firmware first and then the ML1 Modem. :cool:

MF1 Firmware - https://www.androidfilehost.com/?fid=23329332407591785

ML1 Modem - https://www.androidfilehost.com/?fid=23329332407591786
[Verizon Samsung Galaxy S III] Hybridnoob:
Do you have your IMEI in the about phone section?
[Verizon Samsung Galaxy S III] prdog1:
Pretty sure he does. He has data/4G. MB1 didn't work for me either. Not sure why. Maybe because of way originally upgraded and unlocked. :cool:
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
So are "firmware" and "modem" one and the same, or are they two different things?

Example:

1. MB1 firmware

2. MB1 modem

3. MF1 firmware

4. MF1 modem

5. ML1 firmware

6. ML1 modem

7. NE1 modem
[Verizon Samsung Galaxy S III] prdog1:
The firmware usually contains the matching modem. The modems are modem only and except for AOSP/CM they can be swapped for what is best for your area/tower. On TW any modem is interchangable. CM not so much. ML1 firmware will lock you down and could softbrick. :cool:
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Thanks. How can I find out what:

1. Firmware that I'm currently running

2. Modem that I'm currently running
[Verizon Samsung Galaxy S III] prdog1:
Modem = Baseband in about phone. If have never flashed a separate modem will be the same firmware. :cool:
[Verizon Samsung Galaxy S III] evertking:
Im using the ST s968c s3, it runs on verizon. Could i use any modem? I also lost data after the 5th.

Thanks
[Verizon Samsung Galaxy S III] Reznor7:
Bah, spoke too soon. No BT isn't working.
[Verizon Samsung Galaxy S III] prdog1:
Not sure as I have no info on dev blocks except we do know recovery, kernel and system /data are same blocks since d2vzw roms work so probably all the same. What modem does it show in baseband. Bad thing is that it is possible to brick with modem. Since it runs on Verizon it may be ok. I have no way to guarantee. Haven't found enough info on it yet. :cool:
[Verizon Samsung Galaxy S III] evertking:
s968cuduamh1
[Verizon Samsung Galaxy S III] prdog1:
Yea. That is ST modem. Not sure. All I can tell you is hold your nuts and try it. Won't work on ST anymore more than likely. :cool:
[Verizon Samsung Galaxy S III] betam4x:
Any luck on the incoming Bluetooth calling?
[Verizon Samsung Galaxy S III] thefuzz4:
Anyone rocking today's nightly?
[Verizon Samsung Galaxy S III] darklavalizard:
I'm still on 8/24 with the ML1 modem. I want to try the NE1 modem, but it appears based on certain ROM/modem configurations, that MMS and other functions like data aren't working. Are the latest nightlies + NE1 a safe combination?
[Verizon Samsung Galaxy S III] prdog1:
NE1 no MMS. Latest working nightly we have found is 9/8. Everything reported to work on MB1 firmware and modem. SMS, MMS, Data and GPS working with MF1 firmware and ML1 modem. Unable to test GPS. Haven't tested 9/14 but don't see anything in last few changelogs that would fix it. :cool:
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Hey pr I know it's off topic but what phone are you moving to after the mighty s3. sadly I love this phone and have no idea which to go to from this device which is probably still the best Samsung device to date in my opinion but like anything else I feel my device is starting to show it's age and map just wondering as you always p.have good advice/recommendations
[Verizon Samsung Galaxy S III] prdog1:
Have no Idea. Has to be unlocked since I don't use phone a lot except to dev and theme. [emoji41]
[Verizon Samsung Galaxy S III] aromig:
NE1 modem with MF1 firmware works fine on the 9/13 nightly. Data, SMS, 10ft GPS accuracy within seconds, and MMS.. with a couple simple APN adjustments.

Go to Settings-->Mobile networks-->Access Point Names. Tap on the name Verizon Internet (not the dot unless it's not already selected). Now, select MMCS and insert the link "http://mms.vtext.com/servlets/mms" without the quotes. Next, change the MMS port to 80, and add ",mms" to the end of APN type (also without quotes). Tap the menu button, select save, then turn off data and turn back on after a few seconds. There ye be.

Only catch is you can't send MMS while on wifi, but I think that is true of any modem/firmware combo right now. If not, maybe someone smarter than I can get it working. Btw, fwiw, BT voice and music streaming both work without issue on my car.

The attached photo of deliciousness was both received and sent successfully.

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] Hybridnoob:
Anyone successfully have M10 running yet? I tried dirty flashing from 9/8 (should have been safe), but got continuous soft reboots and phone process crashing. Even after formatting system, M10 wouldn't stay booted. I wonder if there's a minimum firmware and/or modem requirement. MB1 doesn't appear to work. I haven't tested any other combinations yet.
[Verizon Samsung Galaxy S III] iclickjohn:
Same here. I couldn't just dirty back to M9 neither. bootlooped as well. Just did complete wipe and getting it going again. DON'T do M10 everyone as of now until further information. OK I've rebooted into M9 and I see my IMEI is now gone...... Rebooting again to see if it returns........ And now it has returned. I think all is good.
[Verizon Samsung Galaxy S III] mjb32803:
I had just done a clean flash of the 9/14 nightly with the NANO version of gapps. This morning, I flashed M10 using the CM updater. Now stuck in reboot loops... phone seems to boot, gets to pin lock screen, then I get a few apps force closing, then phone reboots.. repeat. Went into recovery and reflashed the 9/14 nightly and everything seems ok. I have the MF1 baseband.
[Verizon Samsung Galaxy S III] AndroidCrusader:
Thanks for the heads-up! I am on 9.15 with NE1. I have been upgrading nightly. At the moment the only issue I have is not being able to MMS. I even tried the mods to APN without success.
[Verizon Samsung Galaxy S III] prdog1:
M10 bootlooped here also even after full wipe. On 9/15. MF1 firmware and NE1 modem. APN edits worked for MMS. GPS extremely hard to lock. Will have to work on config. May have typo or extra space in edits for MMS.
[Verizon Samsung Galaxy S III] mastamoon:
You guys might have to wipe contacts data. I think that was the db that was causing the issues.
[Verizon Samsung Galaxy S III] thefuzz4:
So the only thing I've noticed so far on 9/11 is that OpenVPN doesn't seem to work anymore. I can browse web pages but all of the other apps can't connect to anything. I also found out last night taking your wifes sdcard from Tmobile and putting it in your phone will work but when you put the vzw one back in you have to do a complete and full wipe of everything in order to get the phone back to vzw sim card settings.
[Verizon Samsung Galaxy S III] mastamoon:
I believe the fix for the VPN issue and MMS was in last nights build.. if not, tonights build.
[Verizon Samsung Galaxy S III] thefuzz4:
Thanks for the quick response
[Verizon Samsung Galaxy S III] darklavalizard:
What advantage does NE1 have over ML1, if any? Faster data speed? Just wondering why anyone would upgrade to it from ML1 (other than those like me who like having the latest and greatest on their phone).
[Verizon Samsung Galaxy S III] AndroidCrusader:
I switched because I lost LTE on a nightly this week.

---------- Post added at 03:38 PM ---------- Previous post was at 03:32 PM ----------

I did not edit the LTE Verizon Internet setting, rather I edited the EHRPD Verizon Internet. Maybe that was the issue.
[Verizon Samsung Galaxy S III] kidhudi:
i just flashed the latest build

the problem is i looked in hangouts APN section and all were sprint APNs

my mms is not working .

i tried to manually add verizon APNs but the wont stick. they just disappear

any thoughts?
[Verizon Samsung Galaxy S III] AndroidCrusader:
After putting in the changes you have to hit your menu soft key left of your home button. Choose the option to save, then proceed to shut off mobile data for a few seconds.
[Verizon Samsung Galaxy S III] chowner:
I'm experiencing the same thing as him.
[Verizon Samsung Galaxy S III] -Lawless:
Took OTA and after reboot and flash, I'm stuck in a boot loop.

Any ideas?

This is a new install (today) on the newest nightly. 9-15

thanks
[Verizon Samsung Galaxy S III] -Lawless:
I just started over and factory reset. I wasn't very far along on the new install when the update popped up anyway....

---------- Post added at 03:18 PM ---------- Previous post was at 02:59 PM ----------

This would be incredible if it works! I'll try it tonight with my wife's T-Mobile sim. Her S3 is about dead and I have an extra Verizon she could try.

thanks!
[Verizon Samsung Galaxy S III] SDQB17:
I am on the 8/31 nightly and just updated to the m10, upon boot I got a constant error which ( i didn't write down lol) I believe was com.android.media , Unable to get the error popup to stop so I just went back to my backup of 08/31. Any idea what that error is about? Maybe I should wait for the next nightly and forget the M release?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Settings-->Mobile networks-->Access Point Names

Anyone not seeing this option on their phone?
[Verizon Samsung Galaxy S III] -Lawless:
Ya. . That didn't work.

Sent using Tapatalk Super Advanced Pro+
[Verizon Samsung Galaxy S III] MartyMacGyver:
I'm still on 9/8... rather glad I came here to read before doing my usual update-because-the-changelog-looks-benign thing.

Besides wondering yet again what's so special about "M" builds, your post reminds me of a peeve I've had since I switched to CM11 months ago.

On stock, GPS always worked well and was pretty solid. On CM11 it's always been rather weak, as if it wasn't getting/processing signals as strongly. Furthermore Google Maps almost always reboots the phone when in navigation mode (could be a minute or an hour but it'll crash... oddly, it almost never does it if it's horizontal (landscape mode) but very readily if the phone is vertical). It loses GPS lock more easily as well.

While the Maps thing *might* be a bug (a bug that should be affecting millions of users very consistently for several months - that seems unlikely) the GPS signal strength seems very much a CM11 thing. Has anyone else experienced this in general on CM11?
[Verizon Samsung Galaxy S III] polymath257:
Yes, I have had a lot of trouble with weak GPS signals on CM. If I compare side-by-side with my old vivow running evervolv, the d2lte gets much weaker signals and doesn't lock as readily. It is better in M9 than in previous builds, but it is still not good. I've not been on stock for so long I don't know how it performs :).

As for reboots, I had problems with that when my d2lte was in a car dock until the M9 update. So far, that one has not given me a random reboot.
[Verizon Samsung Galaxy S III] mastamoon:
Friendly reminder to check your GPS screws if you are having weak gps signal.

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

Its worth checking out.
[Verizon Samsung Galaxy S III] chowner:
Anyone on 9/17 yet?

Anyone have a MMS fix for hangouts, as the one posted yesterday doesn't appear applicable.

Thanks
[Verizon Samsung Galaxy S III] mjb32803:
I've wondered the same things with GPS. Rebooting and loosing gps accuracy.
[Verizon Samsung Galaxy S III] prdog1:
Tightening screws again fixed mine on 9/17. Back within 10 ft and quick lock. :cool:

---------- Post added at 08:23 AM ---------- Previous post was at 08:22 AM ----------

If you apply that fix it fixes MMS in all messaging apps including hangouts. I use Hangouts and it worked for me. :cool:
[Verizon Samsung Galaxy S III] mjb32803:
Just flashed 9/17 and no errors so fat.
[Verizon Samsung Galaxy S III] chowner:
Do you see sprint information in hangouts? It doesn't work for me and at least one other person in this thread. I'm glad it works for some of you, but others are still having problems.
[Verizon Samsung Galaxy S III] prdog1:
I changed mine in Mobile Networks and it fixed it. Didn't mess with Hangouts access points. It fixed AOSP messaging app also. :cool:
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Getting Trebuchet erros ("Unfortunately, Trebuchet has stopped") on booting/rebooting the device on the M10 build. This off a CLEAN install. Oh well.
[Verizon Samsung Galaxy S III] kidhudi:
Which one did you choose?

i tried them all and none work with hangouts. the messaging app works fine though

but in hangouts it keeps flashing " no specified apn" on the bottom

and all apns in hangouts are sprint

probably because this is a unified LTE build and not a vzw specific rom
[Verizon Samsung Galaxy S III] prdog1:
I use the Team Blackout Clear version. It still has Metro PCS as default and the rest are Sprint. It is on default Metro but didn't work till I edited the APN in device settings>Mobile Networks>Access Point Names>Verizon Internet. :cool:
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
APN: Where?

CM11 M10: not seeing APN option. :confused:
[Verizon Samsung Galaxy S III] prdog1:
Back up a page and long press mobile networks. :cool:
[Verizon Samsung Galaxy S III] mastamoon:
For you guys having mms problems, try using this apns file. https://www.dropbox.com/s/b9zatl31s5d6237/apns-conf.xml?dl=0. Just copy it to /system/etc, make sure permissions are good then reboot.

I use this and don't have a problem. Obviously won't work well if your not on VZW.
[Verizon Samsung Galaxy S III] TokedUp:
Is M10 a nightly? Can't seem to find the right link
[Verizon Samsung Galaxy S III] prdog1:
http://download.cyanogenmod.com/?device=d2lte&type=snapshot
[Verizon Samsung Galaxy S III] mastamoon:
Did that apns file fix mms for anybody? It got a couple thumbs up but need feedback.
[Verizon Samsung Galaxy S III] AndroidCrusader:
I have lost control of my in-call volume. Has anyone discovered a workaround that I missed?
[Verizon Samsung Galaxy S III] TokedUp:
Thanks [MENTION=4538493]prdog1[/MENTION]! But I think the server must be getting hammered cuz it says it will take 6 hours to DL. Oh well i'll try again later.
[Verizon Samsung Galaxy S III] Hybridnoob:
Be prepared for problems with M10 on this device. Read back a couple of pages for examples of the issues.
[Verizon Samsung Galaxy S III] untruestory:
Is anyone here flashed to PagePlus? If so do you get data on this ROM?
[Verizon Samsung Galaxy S III] sanjsrik:
On the first page of the release, it says that they strongly recommend using CWM over TWRP. I used to used TWRP and ran into major issues installing and rebooting and having weird issues. Installing CWM got rid of all of them. Just a suggestion.
[Verizon Samsung Galaxy S III] ericsdeadinside:
I know this has been posted before, but has anyone had any luck with Instagram video or Vine? Vine just says that your device isn't compatible and Instagram will take the video but die on the upload.
[Verizon Samsung Galaxy S III] beepea206:
You just need to have TWRP 2.6.3.1 (most people have 2.6.3.0). I flashed back and forth between the unofficial CM builds with 2.6.3.1 for weeks and had no issues. If you have the older version of either recovery, you're going to get a 'binary' error and have to restore a nandroid.
[Verizon Samsung Galaxy S III] Mystikalrush:
I used 2.6.3.1 The error im getting is...

This always appears when i try to fully wipe my phone, but because of this, error, its will not properly let me restore any nandroids. This nightly really messed with some files deep inside.
[Verizon Samsung Galaxy S III] julesism:
Since we are talking recoveries... If I run a backup from ROM Manager, it fails when it boots into recovery because storage/sdcard1 is not mounted. I can manually mount from recovery, run backup in recovery, then rename the backup when I get back in ROM Manager. I'm on 6.0.4.3 touch. Is this just me?
[Verizon Samsung Galaxy S III] xgujuplaya:
is there anyway to get emojis on cm11?
[Verizon Samsung Galaxy S III] beepea206:
Yikes... that sounds like something a nightly did, because the other unofficial builds, like KitKang, don't have that problem. Sorry to hear that, man.
[Verizon Samsung Galaxy S III] eaglesfan398:
Could I update from 10.2 to the latest or will I just run into problems via updator
[Verizon Samsung Galaxy S III] TenderloinShadow:
dialer

Hey, so I've been going through the thread before I flash this, and I noticed a few comments that confused me. Some people were talking about the ability to do searches in the new dialer not being available in this ROM. I even read a comment saying the 4.4 dialer was designed specially for the N5.

This doesn't match up with anything I've previously read, so I'm just asking for clarification here. Is the full 4.4 dialer available for CM11? Is that thing about the N5 dialer true?

Thanks in advance.
[Verizon Samsung Galaxy S III] titanshadow:
Yeah I'm having issues with my headset dropping and reconnecting.
[Verizon Samsung Galaxy S III] senorbuck:
Man, got all excited. Instagram update (5.0.0) and same issue w/ the video. Still crashes after applying an effect and moving to the screen where you pick a photo for the video cover...
[Verizon Samsung Galaxy S III] BrianKLV:
I was having bluetooth issues as well. My issue was more my headset would not pair until I rebooted the phone. I flashed LeanKernel just to see what would happen and it *seems* to have fixed the problem. It may or may not fix the issue your having though and its still possible my bluetooth issue could come back.

http://rootzwiki.com/topic/32286-kernel-aosp-jb43kitkat-v90-12113-leankernel-minimalistic-kernel/
[Verizon Samsung Galaxy S III] annoyingduck:
Yes it's true. Right now the google dialer is only officially supported by the N5, and maybe (not sure) done of the play edition devices. The dialer has been shown to work on other devices, some report it working fine on ours... That was not my finding. If I were a betting man (which I am), I'd guess that cm will make their own variation of it, or that eventually google will make it more of a universal app for other devices running kk... But that's a guess
[Verizon Samsung Galaxy S III] cehrl7:
I have it installed on my phone. It works perfectly.
[Verizon Samsung Galaxy S III] calexs74:
I have the exact same issue. I can't figure out what the issue is
[Verizon Samsung Galaxy S III] titanshadow:
Is anyone else having problems using bluetooth to transfer a file to a desktop computer?
[Verizon Samsung Galaxy S III] xgujuplaya:
Is anyone having a problem with blacklist not working I'm trying to block the texts from 6250 that say VZWNMN and a number
[Verizon Samsung Galaxy S III] AlphaXray:
Yeah, I hope they actually look into this. I'm fairly certain its just a CM issue, so maybe this round they'll actually fix it. I really hate the issue with the front facing camera and snapchat. It freezes and hangs, and I've got girls I've gotta SNAP!!!

Also, if anyone else out there uses snapchat and is on CM11 could you confirm if this happens for you. The only issue is the front facing camera, the rear works fine. I just don't wanna be the only one.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
I've gotten that error before as well and it wasn't while using cm or flashing cm...

Unfortunately the only way I was able to fix was to wipe everything but the external SD card and format data and then flash a rom
[Verizon Samsung Galaxy S III] prdog1:
I already had the edit in but it didn't break anything. Only thing I see is if pull pic from hangouts for mms it is 90 degrees out of orientation. If initiate mms from gallery it comes out right. [emoji41]
[Verizon Samsung Galaxy S III] Reznor7:
I did a complete wipe and went back to M8. Everything seems to work perfectly, including Bluetooth, GPS, etc. Until I see a compelling reason to move forward, it's my daily driver.
[Verizon Samsung Galaxy S III] Reznor7:
Ha, whoops. I meant M9. Darn keys are too close together.
[Verizon Samsung Galaxy S III] aromig:
Keep getting a download unsuccessful error.

Sent from my GS3 running CM11
[Verizon Samsung Galaxy S III] McDastardly:
I did a full wipe and was able to install M10 with no issues yet. Been running good for a day now.
[Verizon Samsung Galaxy S III] mastamoon:
I just downloaded it without issue.