yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
What's everyone running these days? I started using 4/19 Timedroid yesterday. Not too bad yet, had my Sys Ui stop once was all and when a call came in, it was really slow to show up on screen. Like, my phone was ringing but nothing was on my screen to pick up the call. Could be worse, as my Grandma used to say. ?
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I've been running the 4/21 build with a better camera unlocked an it's been smooth sailing so far.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
4/21 invisiblek had me with data issues and couldn't stop the lockscreen from rotating. Needed to go back a bit to see if this was remedied & it was. Lol.
[Verizon Samsung Galaxy S III] jackyalice:
I flashed OctOS 4/22 build. It boots fine and runs smoothly.

It is Android 5.1.1.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Cool, I'll have to look that rom up. Thanks

---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------

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

Is this what you got? Did you dirty this over a InvisibleK or other LP build or clean install? Thanks.
[Verizon Samsung Galaxy S III] jackyalice:
That's it.

I dirty flashed it.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Cool. Thanks ?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Are you able to send and receive MMS messages? I was able to send/receive for a day or two. After that, I can only receive. Sending an MMS no longer worked (which was strange). :crying:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Ik you may not want to for the obvious reasons, but I used Handsent messenger forever and never had an issue. Now I'm using Message+ by Verizon bc it's more user friendly & has cool in app features, plus I needed a change. Lol. But yeah, try it. You can configure your carrier and other things in the settings too & that, I think, helps the mms/sms issues.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I'm just using the default Messenger at the moment. SMS works fine. It's just MMS that is failing to send.

Do I need to fiddle with any Settings/Mobile Network settings? Currently, I have this.

Data roaming: OFF

Preferred Network Type: LTE

System Select: Automatic

CDMA Subscription: RUIM/SIM

APN: Verizon Internet (VZWINTERNET)
[Verizon Samsung Galaxy S III] NoCrAppleHere:
That looks fine to my knowledge. You were asking in general, right, not the settings in Handsent? What modem you on, NE1?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Yes, just in general (not for Handcent in particular). I'm on the NE1 modem.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Wish I could help more. That's about all ik though. It's just so weird to me bc I've never remotely had mms/sms issues with any rom. (I just jinxed myself but hope not) ?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Other than that MMS issue on the 04/21 build, everything is working well for me. At least we get to run 5.x on our GS3.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
True that but don't give up hope yet. It's still plenty alive, the GS3. I was going to try OctOs Cm12.x today but not yet, wanna see how we proceed with this rom here. You can try it though, page before this there is a link in it. It was said that it can be dirty flashed over InvisibleK rom. As always, though, do at your own risk. Lol.
[Verizon Samsung Galaxy S III] Master Cylinder:
Use Handcent, too, and never had a problem of any kind, except when NE1 became a requirement.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Have you ever went into Handsent settings and messed with the manual carrier settings they implemented a while back?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Handcent: I'm reading that it has ads and subscriptions?
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Only weird thing I have encountered is the charging deal I mentioned a few posts back
[Verizon Samsung Galaxy S III] dmt010:
If anybody is interested, I'm still working on putting a build together. Just plenty of garbage going on at home, haven't had time all weekend to work on it
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
We are interested! :good:

On a separate note and an update: after flashing the APN file that mastamoon had for Verizon, it appears that my MMS issue has gone away (I hope permanently). I'll continue to keep an eye out for it and see if anything comes up. For now, MMS is working again. Yay! :laugh: :highfive:
[Verizon Samsung Galaxy S III] Master Cylinder:
Actually, I forgot to mention on [MENTION=2963287]mastamoon[/MENTION]'s 12/29/14 5.0 build, I was having MMS issues, both send and receive. I changed the APN type settings to what I had on my cm11 and it fixed it. I thought this problem had been generally fixed since then, but you could have a look at this possible solution. You have to select the APN Version "VZWINTERNET" panel and then scroll down to APN Type. I changed it from 'mms' to 'default,dun,supl' and it fixed it. I've never switched it back (and dirty flashed ever since) so I don't know if all is well without that. Here's my post http://xdaforums.com/showpost.php?p=57954372&postcount=2232

I did once but fixed my problem with the above solution.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Yep, my MMS issue is "resolved" for now after flashing this .ZIP file that Mastamoon had posted. I'm letting it run and keeping an eye out. It should, by all intent and purposes, should fix the MMS issue.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
You don't have to subscribe to anything but recently, yeah, they added some ads. It's nothing like you'd think though, just like a lil box at the top of the text main screen, no popups or full-screen stuff. I see you might have remedied the issue, hope it sticks.
[Verizon Samsung Galaxy S III] Master Cylinder:
Excellent!! I forgot to mention that as well. Thanks for the link, though [MENTION=2963287]mastamoon[/MENTION] said stuff on there could disappear at any time.
[Verizon Samsung Galaxy S III] mastamoon:
You guy will want to watch this commit.. http://review.cyanogenmod.org/#/c/96519/

Nightly status for d2.. omgimpossibru!!

Everybody buy ya boi [MENTION=2044079]Nardholio[/MENTION] a sammich.
[Verizon Samsung Galaxy S III] amf66:
Quick build for you guys https://androidfilehost.com/?fid=23991606952593950

Don't kill me if it doesn't work... I don't have a d2vzw to test on. Works on d2att, though.
[Verizon Samsung Galaxy S III] amf66:
Not sure if I think it's ready for nightlies yet... radio has been very unreliable since 4/23 on my nightlies.
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh::laugh:
[Verizon Samsung Galaxy S III] XdrummerXboy:
Has anyone tried /u/amf66 build yet?

I just clean flashed the 4/21 build, reflashed the NE1 radio, and flashed mastamoon's stock APN file (just in case). I can't say anything about needing to reboot after switching from WiFi to LTE, but one thing I've noticed is Bluetooth is weird.

I connected to my Moto360 fine last night, but when I tried connecting to my receiver in my car, it connected, but then turned BT off, and it wouldn't come back on. Buuuut, it still looks like its connected and playing music via BT, but just no sound. Its pretty bizarre.

Anyways, I want to thank everyone for continuing the builds for this device. I wish I could contribute skills or money, but alas, I'm a poor college kid with a wife and baby! Someday.... Haha :D
[Verizon Samsung Galaxy S III] Master Cylinder:
Ok, no contract out on you :) It wouldn't boot flashed dirty over 4/19, but I have been having problems getting ROMs to boot lately. May be something on my end I'm still exploring. I'll flash yours clean and see what happens.
[Verizon Samsung Galaxy S III] DubleJayJ:
Flash the APN's in mastanoon's thread. After booting back up, go into your APNs and reset to default, it'll put the new ones in if it didn't already. Haven't had a problem since
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Boots Up Just Fine (For Me)

Install: fresh, clean install.

GApps: pa.micro. Boots up just fine. I haven't done anything else to the phone besides installing the ROM and booting it up. Yes, I did flash the APN file from Mastamoon too, :p.
[Verizon Samsung Galaxy S III] Stealth111:
And now, they are trying to squash d2vzw out as fast as they were gonna add it in...
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
It doesn't look so good at the moment for us. :( :rolleyes:
[Verizon Samsung Galaxy S III] amf66:
I'll put out regular builds (with cherry picks, of course) regardless.
[Verizon Samsung Galaxy S III] DubleJayJ:
If someone could tell him the fix and made sure he knew we'd probably get support. They'll probably be able to bake in the fix too
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Thanks a bunch! :good: :highfive:

On a side note, do you have a changelog for your 04/29 build?
[Verizon Samsung Galaxy S III] mastamoon:
You guys NEED to provide logs of stuff you find derpy. If everybody has the same issue, we don't need everyone to provide the same log.. But if you run up against a derp, use syslog, grab a log so people might take a look.

Syslog has a personal info scrubber so you should be able to attach logs here with little worry.

Bluetooth being buggy shouldn't stop nightlies, and IMHO either should hand off issues if they are fixable by a toggle or reboot. D2vzw has gone through worse and had official nightlies.
[Verizon Samsung Galaxy S III] amf66:
Since it's my first d2vzw build I don't really have anything.

Camera should work really well. No longer crashes when you tap to take pictures while recording.

Snapchat front facing camera is no longer stretched.

Smart dialer - turn on in phone app to dial contacts when you put the phone to your ear.

Probably some other stuff... haven't added my cherry picks so not as many features as my d2att builds.
[Verizon Samsung Galaxy S III] Stealth111:
YEE-HAW!!!

I will quote "Gerrit Code Review 6:12 PM Change has been successfully merged into the git repository."

And YES, Line #14 of the cm-build-targets is: cm_d2vzw-userdebug cm-12.1

We will have our nightlies!!!
[Verizon Samsung Galaxy S III] jackyalice:
I dirty flashed 4/29 nightly on OctOS 4/22 build.

and flashed supersu 2.49 zip, but I cannot find supersu app in app drawer.

Everything except that is good.
[Verizon Samsung Galaxy S III] Tbenson:
Nightly built. Downloading now.

https://download.cyanogenmod.org/?device=d2vzw
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Which gapps package are you going to use
[Verizon Samsung Galaxy S III] Tbenson:
I dirty flashed over from invisiblek's 20150411 cm12.1 build. I used the gapps that were posted on page one when I flashed the 411 build.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Is amf66's build same as the nightly on cm.org? Seems like people are speaking of it as if it was the same. Ty

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

How's this build treating you so far?
[Verizon Samsung Galaxy S III] Tbenson:
Pretty good so far.

MMS, Bluetooth (tested fitbit, will test car radio tomorrow) camera all working fine.

I was having a weird issue switching to WiFi on 0411 build(sometime would need a reboot) and this seems no longer an issue as I have switched back and forth quite a bit to test it out.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Cool beans. I love progress ?
[Verizon Samsung Galaxy S III] SilentDude56k:
Wow, I didn't think we'd ever get official 12.x nightlies. I was even just setting up a build environment to play around with making my own builds! I guess I'll use it to mess around with building CM 12.1 for my old dinc or something dumb like that instead :)
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I have an old DINC too. Would love to try CM12.x on that. If you build it, let me know. :) Anyway, back to the topic for the D2VZW. Glad to see that we're getting nightlies for our phone. Speaking of that, I'm testing out the 04/30 build now.
[Verizon Samsung Galaxy S III] yorkwar:
How's that 04/30 official nightly going?

Will DKP kernel work with that?

I'm on DKP kernel for battery efficiency.
[Verizon Samsung Galaxy S III] ffeingol:
I tried flashing the "official" CM 12.1 but it would not even load (for me). It blew up in recovery trying to install it. Going to try it again a bit later, so I can capture the exact error message.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
TWRP 2.8.5.0

Install Type: fresh, clean install

Build: 04/30 OFFICIAL Nightly

GApp: PA-Micro

Overall: No issues (thus far) :good:

No boot issues. Wifi connects just fine (even creating a new connection - no more "fail to save connection" error). MMS sent and received. I've just installed this last night, so it's still going through the motions of regular daily use. Thus far, no issues I've come across yet. :good:

I'm not on the DKP kernel, so I won't be able to give any comments on that.
[Verizon Samsung Galaxy S III] Master Cylinder:
I can't get anything to boot anymore - just bootloops ad infinitum. Invisiblek's, [MENTION=4131011]amf66[/MENTION]'s build, new cm nightly ... don't know what happened. I can still use my nandroid of [MENTION=3124924]timedroid[/MENTION]'s 4/19, which is a great ROM, so I'm still working out what happened. I was also able to install that fresh and boot I think as a test ?!?!

I installed philz TWRP multiboot and my phone ain't been the same since. It's not on there still - crashed doing a backup, so I switched back to 2.8.4.0. I've used 2.8.6.0 (flaky on mine) philz CWM based, etc..., tried flashing them in different ways but nothing is working for me at the moment. I've looked at the install script for the multiboot and there's nothing there that's out-of-whack. It's hard to say that's it, but just coincidental with these problems.

If anybody has any ideas let me know. I'm gonna let it slide for a minute since I'm tired of not being able to use my phone trying to flash and boot forever.

Am considering full wipe of the sdcard, or just trashing the android folder (that has been a problem in the past on certain changes in ROM structure) or even rebuilding the darn thing from scratch. (Insert non-existent head scratch emoji here.)
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Running the nightly for about 12 hours now, so far I had a call come in while using Maps turn by turn with voice on the other end but they couldn't hear me. While trying to calculate some stuff, the calculator force closed over and over and over. Upon reboot to try to remedy these issues, phone said PROCESS SYSTEM NOT RESPONDING & I just hit to close the process. Otherwise, no issues. Could have some gremlins bc I dirty flashed, but who doesn't, doesn't dirty dirty or have gremlins. ????
[Verizon Samsung Galaxy S III] XdrummerXboy:
Do you want to try flashing a stock 4.3 ROM to make sure it's not a drivers issue or something? I have the ROM if you want

---------- Post added at 11:28 AM ---------- Previous post was at 11:25 AM ----------

Also, I'm on the official nightly, seems good so far, but haven't tried taking a picture, Bluetooth, or MMS so we'll see!
[Verizon Samsung Galaxy S III] NoCrAppleHere:
http://xdaforums.com/showthread.php?t=2591895

I used this rom forever until I was told about CM roms by Mastamoon. Maybe this could help?
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey thanks guys. :good: I've got old&slows - did use it for a long time, and Alliance, and a couple of others. I even tracked down route66 4.1.2 stock build last night.

So, that may be a good plan, though. Better than wiping the sdcard (which I've never had to do.) However, considering it's been over 2 years, no telling what kind of crap is on there. Just been going through it and don't know what half that stuff is any more.
[Verizon Samsung Galaxy S III] LLStarks:
Anyone able to get get Corporate/Exchange configuration working with gmail?

Pa gapps 5.1 is the only thing I know that works
[Verizon Samsung Galaxy S III] jbleach:
I tried clean flashing the new CM nightly but had no love. It pretty much behaved the same as invisiblek's 4/15 build - it would get all the way through updating the apps, finishing the boot, dies trying to start up I guess, and then just starts the whole process including updating the apps over. I noticed some weird flashing colored pixels at the top of the screen like it was trying to display garbage or something. Have seen this on a few nightlies.

For the record I haven't been able to boot invisblek's 4/22 or [MENTION=4131011]amf66[/MENTION]'s build either. I had been running invisiblek 4/21 but flashed [MENTION=3124924]timedroid[/MENTION]'s 4/19 today because so many people were saying how great it was. Had been experiencing a few random reboots on 4/21.

all clean flashes with CWM 6.0.4.5
[Verizon Samsung Galaxy S III] Master Cylinder:
I had the exact same thing, with little green pixels visible for only a second. I've seen that on another ROM that didn't boot. You and I seem to have almost the exact same issues. 4/19 is the only that works for me, unless I go back to a 5.0 ROM perhaps. I did get 4/21 to boot as well but it had the rotating lockscreen and 4/19 didn't.

I'm thinking there's something in the /sdcard/android folder that's causing a problem, maybe. Also, when a ROM is booting up and shows too few apps to "optimize" then I know something is wrong. It will start over with a different number, etc .... The new CM nightly was the only one that didn't boot but had the app count right.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Try flashing with team wins recovery and see if that works
[Verizon Samsung Galaxy S III] SilentDude56k:
I flashed Alliance in order to fix GPS, then did a full wipe and flashed invisiblek's 4/6 nightly with PA pico gapps. I've been dirty flashing ever since and have had no problems. I'm using the NE1 modem and TWRP 2.8.6.0.

Sure thing! I'm wrapping up my AS degree right now, but I'll have a bunch of time available in about a month. No promises, but I'm pretty persistent.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Why am I unable to change to 12-hour time?

Edit:

CM 12.1 official 4-30 nightly
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Go to Settings/Date & Time
[Verizon Samsung Galaxy S III] XdrummerXboy:
Thank you much!

I wonder why there were two places for the same setting...

Edit: never mind, its not the same setting... It makes sense how they did it. I basically misread it
[Verizon Samsung Galaxy S III] jbleach:
You may have a point there. I noticed the same thing with the count of the apps to upgrade being wrong or different when boot looping - weird behavior. I was also unable to get the 4/30 nightly for the AICP Rom to boot either with the same behavior.

I have always been a CWM guy back since I had my Samsung Captivate but have been wondering if I should give TWRP a try.
[Verizon Samsung Galaxy S III] KaffeDisco:
Bluetooth

I dirty-flashed the 4-30 nightly and it booted up fine. I have mobile data and WiFi without any problems. I can't turn on Bluetooth for some reason though.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Give it a try. I've been a long-time CWM user as well. I'm now using TWRP for these 12.x ROMs.
[Verizon Samsung Galaxy S III] kmoore11:
Whoa Google Now and Search finally work again! I hadn't checked in a while and didn't see anything on here about it, unless I missed it.
[Verizon Samsung Galaxy S III] KaffeDisco:
Uhoh

Well, I wiped /system and then flashed the 4-30 nightly (and dhacker's gapps which had been working really well), and then I kept getting "unfortunately, gmail has stopped" repeatedly. Apparently my online nandroid backup I made is no good, because restoring the backup made it worse - now I'm stuck in a bootloop :P

It's been a while since I experienced some sense of panic over maybe irreversibly breaking my phone so I guess I was due :P
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
That Galaxy S6/Edge is looking good in your future, :D

Did you only wipe /system? Or did you do the customary: dalvik cache, data, cache ?
[Verizon Samsung Galaxy S III] KaffeDisco:
Oh yeah, I always do wipe /system --> install ROM --> install gApps --> wipe cache/Dalvik. No data wiping.

Also, so far the LG G4 is looking better in my book :D I just have to get my phone to survive until then!
[Verizon Samsung Galaxy S III] galets:
Where did you download 4-30? I went to the link on frontpage, and all the builds disappeared!..
[Verizon Samsung Galaxy S III] KaffeDisco:
Off the official nightly page now! http://www.cmxlog.com/12.1/d2vzw/
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Official Thread?

Maybe they need to start an OFFICIAL thread over on Original Android Development.
[Verizon Samsung Galaxy S III] dmt010:
Trying to understand y people need super su when root level privs is right here in Dev options. Anyhow nice to see build bot is finally pushing out builds. Ty Dave and mastamoon with mad mastarespects

:)
[Verizon Samsung Galaxy S III] XdrummerXboy:
Same here, always used CWM. Glad I switched. I love the big buttons

---------- Post added at 11:21 AM ---------- Previous post was at 11:16 AM ----------

Clean flashed the 4-30 official with BaNkS GAPPs, and Bluetooth works for me.... Sorta.

It took a while to connect, but once it did it was fine both times I tried. Also, the phone thinks its connected for quite a while after I wasn't. I think I wound up toggling BT to fix it.
[Verizon Samsung Galaxy S III] KaffeDisco:
Yeah, I gave up and clean-flashed 4-30 + dhacker29's, and now my phone boots again ... wish that online nandroid backup would have worked better - those nandroids I made turned out to be useless from what I can tell :P Bluetooth does seem to be working fine though now.
[Verizon Samsung Galaxy S III] KaffeDisco:
Bluetooth seems to be spotty. It works after a fresh reboot (usually), but then usually it breaks and turns itself out - sometimes with the message "Unfortunately, Bluetooth Share has stopped." If I hit the Bluetooth toggle, it turns itself off (kinda like Thinkgeek's Useless Box). The only way I can get it to work again is with a reboot. Thankfully, a soft reboot is sufficient to get things going again.