yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] DubleJayJ:
Odd, haven't had this problem. Made 3 calls last night and hung them all up myself perfectly fine.

---------- Post added at 06:39 PM ---------- Previous post was at 06:38 PM ----------

Service will come back after 15-30 seconds or so, and to get data back go into your vzwinternet apn until it comes back. Works for me
[Verizon Samsung Galaxy S III] Master Cylinder:
Mine did this with ONE of my Bluetooth earpieces but was fixed on the 12/21 build.
[Verizon Samsung Galaxy S III] sullivan1985:
I've now had this ROM running on my S3 for most of the day. These are my findings so far:

-GPS is slow to lock.

-Flashlight button in notification tray is flaky. You have to toggle it a few times to get the light to turn on. Same for turning it off.

-Messenger app force closes when you try to attach a picture in the app itself. Using an outside app to share it using Messenger works correctly.

-MTP reading and writing to SD Card is very slow.

-Google Camera and FV-5 do not connect to camera and force close. However, Open Camera and "A Better Camera" both connect and have full functionality.

These are not deal breakers to me. I know this is still in development. As of right now this ROM has made my old S3 more lively than it has been on official CM11 nightly downloads and much more stable. I was experiencing regular crashes that were driving me crazy.

Looking forward to future updates!
[Verizon Samsung Galaxy S III] Master Cylinder:
No problems here with the flashlight.

As far as MMS, what modem do you have installed? I have NE1 and am using Handcent which works perfectly (except one can't change or resize fonts.) .
[Verizon Samsung Galaxy S III] sullivan1985:
Using NE1 modem, but using default messanger. I'll try using Handcent to see if that makes any difference.
[Verizon Samsung Galaxy S III] Master Cylinder:
You could try 8sms which looks just like stock (in kk anyway) Handcent is a feature rich app with theming and scheduled messaging, etc.

also, n the past, disabling blacklist was a fix
[Verizon Samsung Galaxy S III] DubleJayJ:
Getting hard battery drains on what should be sleep on wifi. But overall I'm very happy with this ROM, I'm able to get a full two hours of on screen time and be down 50%. Before I was barely hitting an hour and I was down 50%
[Verizon Samsung Galaxy S III] saltcreep1:
Not using Safestrap. My bootloader is not locked. I never updated ATO so the bootloader is still unlocked. The ROM I'm using now is Slimkat.
[Verizon Samsung Galaxy S III] Master Cylinder:
Right! I was just responding to the fact that you said you were on the 'stock' firmware and radio, which I would read as a locked bootloader and impossible for you to flash this ROM. We're probably just having a language problem. You can flash this ROM (cm12) if you upgrade your modem to NE1. BAM.:good:

EDIT: Though I think a person or two are on ML1 or even older?
[Verizon Samsung Galaxy S III] Casper34:
I'm running MF1, that's older correct???

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] syst3merror:
I've reinstalled the modem, the firmware, the rom, and the full gapps and it still does the same thing with the phone issue. Here is a screenshot of what I'm talking about. The phone will stay showing this until the caller hangs up, the voicemail times out, etc.....It won't actually hang up on it's own :(

[IMG="Phone Hanging"]http://i58.tinypic.com/k2mv0k.png[/IMG]

Here is a screenshot of my current build info in case I don't have something installed that I'm supposed to.

[IMG="Phone Info"]http://i60.tinypic.com/5u2u61.png[/IMG]
[Verizon Samsung Galaxy S III] saltcreep1:
Yeah, probable poor wording on my part.
[Verizon Samsung Galaxy S III] mastamoon:
Definitely on an old baseband 'MF1'... try flashing the files from the OP in this order to make sure you are on the latest. Your baseband should change to NE1.

Recommended Firmware - d2vzw_VRBMF1_firmware.zip

Recommended Modem - d2vzw_VRBNE1_modem.zip
[Verizon Samsung Galaxy S III] syst3merror:
Ok, I'll try that and see if I have any luck
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah. That's a couple of versions back. Now the newest is NE1 and is in the OP. Go to NE1 and if it doesn't work for you you can always flash an older one. ML1 was the last.

EDIT: Or better yet, do exactly as mastamoon says:

" try flashing the files from the OP in this order to make sure you are on the latest. Your baseband should change to NE1.

Recommended Firmware - d2vzw_VRBMF1_firmware.zip

Recommended Modem - d2vzw_VRBNE1_modem.zip "
[Verizon Samsung Galaxy S III] syst3merror:
ok I've updated the modem and everything and it still doesn't work. It's weird to me that I'm having an issue that nobody else has....

*Just as a test, I'm downloading an older version of it to see if I have the same issue on older builds

**Edit number 3....I didn't see the link for the RIL BLOB and tried it (I have a verizon g3 but I use it on att) and now I'm able to disconnect the calls as of now :) WOOOHOOOOO!!!!!
[Verizon Samsung Galaxy S III] mastamoon:
Well derp.. did I miss where you said you werent using this rom on vzw? lol That was a piece of critical information.

Glad its working for you now.
[Verizon Samsung Galaxy S III] syst3merror:
no, you didn't miss it.....I missed saying it :/ derp is right! lol

So as of right now, from all the testing I've done, the only issues I can find is the chromecast mirroring (Don't care, I'd never use this anyway) and the camera issues (which I don't consider a deal breaker, just kind of sucks)
[Verizon Samsung Galaxy S III] DubleJayJ:
I see built in superuser is finally working.
[Verizon Samsung Galaxy S III] syst3merror:
are those 2 items listed in the changelog the only thing that has been updated? If so, I'll wait
[Verizon Samsung Galaxy S III] savagebunny:
Any idea still?
[Verizon Samsung Galaxy S III] zachf714:
Thanks back atcha =)
[Verizon Samsung Galaxy S III] faehsemc:
Masta... You are not allowed to have a real life. I demand a Merry Christmas Build.

All seriousness, thank you for your work! Happy Holidays
[Verizon Samsung Galaxy S III] mastamoon:
Hey-ohhhh

If any of you guys want the new modem without flashing a different recovery, I have added a link to invisibleks zip that I modded (updated 'update-binary') that will allow the recovery I have posted in the OP to flash the new modem. I haven't heard good or bad things about the new modem so you might want to have the Firmware package in the OP also on your SD in-case you want to go back since it includes the old modem.

I just flashed the new modem and haven't noticed anything different just yet. I also have never noticed a real difference between modems ever. :cyclops:
[Verizon Samsung Galaxy S III] annoyingduck:
Same here, not seeing any improvement or non improvement
[Verizon Samsung Galaxy S III] jdommer:
Does anyone else use "My Fitness Pal"? Since upgrading to this ROM, I can't get the barcode scanner in just that app to work. Barcodes still work fine in other apps.

I'm sure it's an app problem, but confirmation I'm not crazy would be nice. A workaround if anyone knows one would be even more nicer. :)
[Verizon Samsung Galaxy S III] NedDasty:
I'm having trouble flashing the CWM recovery in the OP. It tells me the build.prop assertion of d2vzw is failing--but I checked, and my build.prop lists me as d2vzw! Anybody else having this issue? Could it be due to Xposed perhaps?
[Verizon Samsung Galaxy S III] Fitz012:
Tether

Rom is awesome....love it. Just wondering if the tethering is working...I get an error every time I turn it on ..Maybe I'm doing something wrong....Thx again for all your hard work...
[Verizon Samsung Galaxy S III] mastamoon:
Broken for me also. Anybody on yesterday's build confirm if wifi tether is working/broke?
[Verizon Samsung Galaxy S III] Evil Genius Jr.:
I'm on the 20th ( I think, two builds ago)

And tethering is perfect for me.
[Verizon Samsung Galaxy S III] TwistingSoul:
You could always try this after installing the Xposed Framework:

http://xdaforums.com/showthread.php?t=2416768

Though, I just noticed the setting in Sounds (Main System Settings->Sound->Volumes) that goes into linking/un-linking the volumes for each notification type.
[Verizon Samsung Galaxy S III] Fitz012:
Fixed

I believe I may have found a fix....Go into the data/misc/wifi folder and delete it...Then reboot. Once I did that my tethering works fine.
[Verizon Samsung Galaxy S III] savagebunny:
I haven't updated past the 12-14 build, but I'm having issues here and there sending MMS currently.

Also when I send text messages, my recipient gets the message but tells me it failed to send. Quite odd
[Verizon Samsung Galaxy S III] Evil Genius Jr.:
That's happened to me on every build of everything I've tried, including stock. Haven't found a fix yet...
[Verizon Samsung Galaxy S III] savagebunny:
Hmm interesting. Well I know at least the other person is getting a message so it isn't a big hit for me.
[Verizon Samsung Galaxy S III] moparfreak426:
I've been getting this and unable to send with every 4.4.2 rom I've tried

Also, I have WiFi off all day til when I got back to apartment I know for sure. But according to battery still on. I'm running 12/15 I think
[Verizon Samsung Galaxy S III] savagebunny:
Well I got some results for people wanting to run Mastamoon :P

Btw, phone spent about ~4hrs Airplane mode when I flew from PA to Cali. Media server was me listening to music. And all that screen on time.... I got a lot of usage out of this run specially for screen on time, the game DOTS, listening to music, used some GPS, Google maps in there too
[Verizon Samsung Galaxy S III] Crewski:
Go into the wifi setting, hit the menu button and click advanced, then uncheck the scanning always available. This should fix the wifi always on.
[Verizon Samsung Galaxy S III] moparfreak426:
Sure did.
[Verizon Samsung Galaxy S III] ugachris:
Wow... 8+ hours of screen time? On 10.2 and 11 I've been happy to see 2 hours. Any hint as to how you've gotten this battery life?
[Verizon Samsung Galaxy S III] Mtsprite:
trust me its worth a try.
[Verizon Samsung Galaxy S III] mastamoon:
Those 2 things are changes waiting to be merged, but plenty of stuff has officially got merged between my last build and today's.

My change log is in addition to the "official" changelog if there were one yet.
[Verizon Samsung Galaxy S III] SDQB17:
Just thought I would pass along some info, I flashed the latest and did not have root upon boot. SU just stuck trying to update binaries and after several reboots ( like Su suggests) still no go so I flashed the same su that I have been using thru all these past updates and that worked fine.

Havent tested anything else out yet...
[Verizon Samsung Galaxy S III] matt_man:
I just flashed the latest and su is fine.
[Verizon Samsung Galaxy S III] syst3merror:
Do I need to format or flash dirty over the current cm12 I'm running?
[Verizon Samsung Galaxy S III] kenny1974:
I dirty flashed and everything is good

Sent from my SCH-S968C
[Verizon Samsung Galaxy S III] mastamoon:
If you want to use built in Su, gotta clean flash. If you want to stick with superSU, gotta flash with every install I believe, or atleast I did and never had a problem.

I've been using the built in and it's been fine, except for titanium backup being iffy.
[Verizon Samsung Galaxy S III] SDQB17:
Cool thanks for the explanation Masta.
[Verizon Samsung Galaxy S III] DubleJayJ:
I dirty flashed and built in worked fine. And I'm not noticing any changes except for when you're plugged in it'll tell percent
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I have a really good working version of cm11, can I bounce back an forth between cm11 an cm12 with minimal trouble? I'm wanting to check out cm12 but I have to have a working phone
[Verizon Samsung Galaxy S III] mastamoon:
If you have been using superSU but want to switch to built in, it's best to clean flash the first time, then dirty flashes are fine.. If you've never flashed superSU, then nothing to do here..

Might not be 100 percent necessary to clean flash to get rid of superSU, but I saw issues with just unistalling superSU. Everything was better after finally data wiping. YMMV
[Verizon Samsung Galaxy S III] betam4x:
I was going to say, i am running his baseband without issue. I never bothered to update since it's working quite well.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
Is the camera issue a permanent one for this rom or is it simply a matter of troubleshooting with code?
[Verizon Samsung Galaxy S III] sjpritch25:
Not likely

Masta's Builds are still in the Alpha stages. That being said, A lot works for being just an Alpha build. Camera, Video, bluetooth, NFC are mostly going to be buggy with Alpha builds that i've flashed in the past. I'm on 12/21 build and camera worked over christmas using camera51 (it was buggy though), camera video is a no go, and steaming spotify/pandora through bluetooth was cutting in and out to much to bare. Other than that its a daily driver for me.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Have there been any Bluetooth connectivity fixes in this or the previous build?

I wasn't able to connect to my Moto 360 (although connecting to car radio and other things DID work).

For now its a deal breaker.

Thanks!
[Verizon Samsung Galaxy S III] metalcated:
https://code.google.com/p/android/issues/detail?id=79729
[Verizon Samsung Galaxy S III] HiM@L:
guys quick question:

OT: i want to install stable ROM on my gf's phone...i know cm12 is still in alpha stage... so, what abt the cm11 version...is it stable enough?
[Verizon Samsung Galaxy S III] sjpritch25:
I never had issues with 4.4.4 roms. Everything worked. I didn't use CM11, but it's stable. The only possible bugs are flashing the nightly builds
[Verizon Samsung Galaxy S III] Rushead:
I'm on the Christmas eve nightly. It's pretty stable. You'll need to use Google Camera (or something else) tho.

Also, definitely recommend the NE1 radio. HUGE difference. Thanks [MENTION=2963287]mastamoon[/MENTION] for the tip.
[Verizon Samsung Galaxy S III] Master Cylinder:
Google camera will not let you save to sdcard1 if necessary. I always used Camera Next: http://xdaforums.com/google-nexus-5/themes-apps/app-cameranext-one-plus-one-cm11s-t2730715 (CameraNext30O.apk is the latest) for cm11 and QuickPik gallery.

But Open Camera is interesting though seems to have more complicated features, depending on what you need.
[Verizon Samsung Galaxy S III] Master Cylinder:
snip
[Verizon Samsung Galaxy S III] betam4x:
Fixed soon in 5.0.3

https://github.com/Lethargy/android_frameworks_base/commit/da2133d046e59b590e51448eda31d710da217d40

https://github.com/Lethargy/android_frameworks_base/commit/e30ccdbeac2c53b04a389c7ffd8e9d500c93ef30
[Verizon Samsung Galaxy S III] ThaSik1:
Lol so can I ask what fixes have been implemented in the official "unofficial" Dec 29th update. I maintain a GS3 for a friend who I donated the phone to, and realized after giving it to her that the Cam is buggy. Any chance that has been fixed in this release, and if not, is there an app you'd recommend to hold her over until a fix occurs maybe? Also, she complained about Instagram (didn't test because I don't use it lol). Thanks again for all your work Masta! If I should have put this in another thread just let me know bro!
[Verizon Samsung Galaxy S III] phillysdon04:
Thanks for giving us Lillipop with CM12. I reverted from my S5 to my S3 just to test this out for a few days. If I like it enough, I might sell the S5, lol. The only issue that I have so far, is not being able to connect to my Moto 360.
[Verizon Samsung Galaxy S III] mastamoon:
So you dont know if the 360 has ever connected on cm12? Maybe you should try an early build to see if its something that broke or something that has been broken.

But before you do, check the 360 for a way to delete bluetooth connections, then try to pair again. There have been a few instantances where a bluetooth changed had been merged and required the device to have its bluetooth pairings actually deleted from the device, its not enough to just unpair/re-pair.

This is the earliest build http://mastamoon.truelinux.net/ROMs/CM12.x/cm-12-20141124-UNOFFICIAL-d2vzw.zip im pretty sure bluetooth has been working from the getgo
[Verizon Samsung Galaxy S III] mikejr83:
360 is working fine. If you clean flash you'll have to go to the 360 settings and reset the device and not just unpair or delete connections to get it to reconnect.

---------- Post added at 12:59 PM ---------- Previous post was at 12:55 PM ----------

Just saw this pop up on my G+ feed. Any info on this Masta?

http://www.amongtech.com/no-cyanogenmod-12-for-old-devices-due-to-pie-feature/

Seems not applicable to us since you've provided us with cm12 alpha awesomeness.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
My GPS doesn't work. It didn't work on the 12/21 build when I tried to use turn-by-turn navigation today and when I flashed the latest build it still isn't working. Anyone else having this issue? I've used the GPS Status app which downloads the location of the satellites to help it lock on sooner and the app shows that there are zero satellite signals being discovered.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Can you confirm it works for you?

Moto 360 + CM12 gave me issues too.

I reset the moto 360 multiple time and I want to say I had a fairly clean (if not all clean) flash of CM12.

Maybe I just need to try it again. I sure do miss CM12!
[Verizon Samsung Galaxy S III] mastamoon:
Need to tighten screws or flash back to stock, grab gps lock, then flash back to cm12.
[Verizon Samsung Galaxy S III] mikejr83:
Yep. I reset just to test on the 29th build. You'll need to do the following:

* Reset the 360

* Open Android Wear app on S3 and forget the 360

* Go to the phone settings and Bluetooth and forget the 360

* Reboot your phone

* Hopefully your watch is rebooted by the time your phone boots. Open the wear app and connect to your watch. It may take some time. I thought I was having a problem so I rebooted my phone while it was saying "connecting". I had to resync my apps but it is showing connected now.

What problem are you having specifically?
[Verizon Samsung Galaxy S III] phillysdon04:
I finally got my motto 360 connected after I reset the watch, uninstall the Android wear app, reboot my phone & reinstall the android wear app. I had issues with the Camera but I installed https://play.google.com/store/apps/details?id=com.billgbennett.camerafix CmFix from the Play Store, changed the settings to the recommended 6mp/16:9 resolution and it's working.
[Verizon Samsung Galaxy S III] faehsemc:
So then do a logcat when you call next time so masta can properly fix it.
[Verizon Samsung Galaxy S III] JumperPunk:
I'm having a weird issue where j am only getting 3g data. LTE doesn't work. I'm running the 29-Dec build and the firmware/modem from OP. I know I'm in a 4g area, and ive gotten 4g here before, but not on cm12.
[Verizon Samsung Galaxy S III] mastamoon:
New build up.

Happy New Year everybody!
[Verizon Samsung Galaxy S III] XdrummerXboy:
I think it connected via Bluetooth fine, but it was just stuck at showing "connecting" in the android wear app.

Thanks!
[Verizon Samsung Galaxy S III] DubleJayJ:
Are the changes on the new build just the changes listed on the cherry picks or anything impactful?
[Verizon Samsung Galaxy S III] mastamoon:
You would have to go through the official changelog or study what was merged in the week since the last build to truly see all of the changes.

My change log is merely the difference between what would be an official build at that moment in time and my build.

If anything of significance gets merged I try and point it out. Unfortunately I haven't kept that great of track over the last week to tell you if anything impactful has been merged.
[Verizon Samsung Galaxy S III] mikejr83:
I was able to reproduce that when restoring backups from TiBU for Android Wear and Bluetooth connections. I think it's basically best to say clean flash your phone clean flash your wear.
[Verizon Samsung Galaxy S III] Master Cylinder:
Root Gone in 1/02?

Oopsie! After installing 1/02 over 12/29 I lose built-in SU. Anyone else?:crying:
[Verizon Samsung Galaxy S III] kenny1974:
Yeo, I did the same

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Macrodroid:
Best update yet! Fast, stable and fully functional! Thanks mastamoon! Found my new dd!
[Verizon Samsung Galaxy S III] DubleJayJ:
Fully functional minus the camera issue and getting data to work first time around
[Verizon Samsung Galaxy S III] matt_man:
I get the following error when I try to attach a picture to MMS Android. Process. Media. This is after upgrading to the newest CM12 unofficial and reflashing Chain fire's Su. This causes Hangouts and the stock messaging app to crash. This is on the SCH-986C variant.
[Verizon Samsung Galaxy S III] kenny1974:
Mine is a SCH-S968C as well and I had to flash chainfire su to get root back, but stock MMS and hangouts are both working flawless

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] jackyalice:
camera works well now?

I need use the scan function of it.
[Verizon Samsung Galaxy S III] kenny1974:
The stock camera is still not working

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Macrodroid:
Spoke too soon I guess, didn't survive a reboot... Bootlooped and had to restore my tw backup. Camera was still broke on install, but I didn't have any issues with data...
[Verizon Samsung Galaxy S III] XdrummerXboy:
When I clean flashed back to CM11 I had camera issues still.

Would the issues be the same ones propagated to CM12?
[Verizon Samsung Galaxy S III] Master Cylinder:
Scanning may work, depending on what app your using and what kind of scanning? QR and bar code work. My original app QR Droid didn't work but 2 others do.
[Verizon Samsung Galaxy S III] xaybor:
getting there

besides the camera not working, after a few restart and setting messaround........ this rom works pretty well.

thanks! we are heading to the right direction here
[Verizon Samsung Galaxy S III] Master Cylinder:
MMS Issues - Solved?

I discovered that on my 12/29 cm12 build that my MMS was all knotted up. Took forever to send and then wouldn't automatically download, and when I press the button to download, usually it wouldn't, or it would 10 minutes later. I discovered that one MMS I sent didn't arrive until 36 hours later.

So, I loaded up a cm11 nandroid that worked good and compared the APN settings. I found one that was different: APN Type. It was 'mms' on the cm12 ROM and 'default,dun,supl' on cm11. So I changed it (I also set my Handcent APN to Verizon.) Now it seems to work perfectly.:good: Whew! THAT'S a relief.

EDIT: Since it wasn't downloading the message automatically, I would not receive a notification that it was even there.
[Verizon Samsung Galaxy S III] xaybor:
camera and mms

confirmed, still down.
[Verizon Samsung Galaxy S III] mastamoon:
For those of you having MMS issues, can you try and use this apns file? http://mastamoon.truelinux.net/other/apns-conf.zip This is the stock apns file from the NE1 ota. Its not flashable, so just unzip and put the file in /system/etc and reboot.
[Verizon Samsung Galaxy S III] DubleJayJ:
After flashing the latest build they seemed to have been fixed.
[Verizon Samsung Galaxy S III] Master Cylinder:
Do you still have root? I didn't. (so I went back to 12/29)
[Verizon Samsung Galaxy S III] bitemeoftn:
You do have root still. You have to go to Settings/About Phone and tap the Build Number 7 times then go to your Developer Options and turn root back on. It's still there it just gets turned off on this build. Easy enough to fix though. :)
[Verizon Samsung Galaxy S III] Master Cylinder:
Awesome!!:good::good:

I just flashed it again and I still had 'Developer Options' so no need to tap 'Build Number.' But just selected 'Root' and good to go!!
[Verizon Samsung Galaxy S III] DubleJayJ:
Odd... Had it to disabled but superuser still works...