yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] DrkGhst87:
Anyone give the Official 3.0 a go? Just checked up on it now and saw it came out a few days ago. Been on the build from like 2 months ago and feel it's finally time to update.
[Verizon Samsung Galaxy S III] 1BadWolf:
I've been running it for 3-4 days, give or take, and the only issue I've noticed is the front facing video camera caused a crash and reboot. Other than that it's been smooth sailing. :thumbup:
[Verizon Samsung Galaxy S III] jlokos:
No issues with FFC. I get some Fc's on lockscreen and pie settings. Otherwise, eveything is working fine.
[Verizon Samsung Galaxy S III] dubluv17:
I'm getting pretty extreme lag on the notification pull down. It's worse right after I wake the phone, but it happens basically every time. I'm on 3.0 official and have noticed it on other devices, as well. Apprently the 3.1 fixes it, but is not available for our device yet.
[Verizon Samsung Galaxy S III] TenderloinShadow:
How is Google Camera on 3.0 official? I last played around with all the available ROMs about two weeks ago (currently on Beanstalk), and they all seemed to have problem with panorama and photosphere - both would just display a black screen and not work. Plus random camera FCs that require a reboot.

Thanks. Planning to try this again when 3.1 comes out.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I'm on the 3.0 official and I have no issues with the FFC. I just took a dozen or so pics. I open and closed the camera 3 times. Took more pics. No problems
[Verizon Samsung Galaxy S III] Nomad1600:
Are you on stock or Google camera? And, have you tried going from camera to video recorder and back?
[Verizon Samsung Galaxy S III] 1BadWolf:
+1 the only problem I've had with it is the front facing VIDEO camera. All other functions of the stock camera are working for me.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I have done everything I can to try to make it crash. Switched between FFC and Rear camera both video and photo mode. Took several videos and pics with rear and FFC. This is all with the stock camera. Nothing I do makes it crash.

Taking a picture with the Google FFC reboots my phone.
[Verizon Samsung Galaxy S III] 1BadWolf:
Yup, I think that's just the way it goes sometimes. I'm normally one of the lucky ones that doesn't experience any of the issues I read about other users having. That being said, I never use the front facing camera anyway. I was just testing it, so no love lost there. Lol
[Verizon Samsung Galaxy S III] TenderloinShadow:
so with Google Camera, does FFC only crash when doing video, or with photos too?

how about photosphere & panorama? I'm on Beanstalk, and normal photos work but those two don't.
[Verizon Samsung Galaxy S III] DrkGhst87:
Hmm, my wallpaper doesn't seem to want to stick. It just keeps changing back to default every so often and I have to change it back. I don't know if it's because there isn't a setting for it in settings like before, and the fact that I have to use my launcher to set one. All other types of "custom background" images are fine though (lockscreen and notification area) but again those were in settings.
[Verizon Samsung Galaxy S III] sunNsnow:
I found the same thing: my wallpaper would frequently disappear. I found this happening with the end of April to 05/06 updates. I had other issues with FCs (notifications and ringers failing to stick), so I reverted to 04/05, which seems to have less issues with FCs re: wallpapers and sounds. It has other issues, but at least the phone is not constantly FC'ing during heavy usage.
[Verizon Samsung Galaxy S III] TenderloinShadow:
What's going on here? No new nightlies for almost a month.
[Verizon Samsung Galaxy S III] luisdr007:
Anyone using a custom kernel that is good on battery with the 4/5 version?
[Verizon Samsung Galaxy S III] cinco312:
Anyone having system UI FC every few seconds on the official build?
[Verizon Samsung Galaxy S III] J913B:
Yep. Camera and UI seem to be the only major problems though.
[Verizon Samsung Galaxy S III] cinco312:
Is there any option in this ROM to record calls? I know it was impossible to record calls on this device and there were a few workarounds but that was in the ICS days. If not, do you know of an app, ROM, workaround, anything that will allow me to record calls?
[Verizon Samsung Galaxy S III] jearl75:
Xposed has a module to record calls. Plus a record button on the Dialer
[Verizon Samsung Galaxy S III] TenderloinShadow:
Is anything happening with this ROM? It seems like there's very little development still going on for the d2vzw. There hasn't been a new build in nearly a month for this one.
[Verizon Samsung Galaxy S III] :
Unless there was a build issue I believe they just spit out a new build last night...but yes this ROM is still being developed.
[Verizon Samsung Galaxy S III] Nomad1600:
Yup... new build. Big news... 4.4.3 in the form of v3.1. Charging up the phone to flash ...
[Verizon Samsung Galaxy S III] TenderloinShadow:
cool the whole d2vzw scene has been so quiet lately i was starting to wonder what was going on. downloading this now :)
[Verizon Samsung Galaxy S III] Nomad1600:
Bad news... it was a sorta prank by the dev's. They did drop an update dated 6/3 and it does fix the UI errors and FC's that many were getting, but it isn't 4.4.3 (despite having that as the Android version in the About section. I reckon they will release a 4.4.3 soon though.

I was not only getting the UI and FC issues but also Google Hangouts and Google Camera didn't work for me... and the Camera still had issues (I think Hangouts was fixed though).

I went back to AICP to see if the newer version (plus LK) offered battery life comparable to LiquidSmooth. I may bounce back and forth between the two.
[Verizon Samsung Galaxy S III] natethegreat86:
Update

The newest version that just dropped has so far fixed all my issues with ui and fc and camera is working perfectly as well. Not sure if what the previous poster said about it not being 4.4.3 is true but I don't care it's working flawlessly it's good to have my liquidsmooth back :)
[Verizon Samsung Galaxy S III] jlokos:
Agreed; the latest build is working well. According to the Dev, the 4.4.3 was a joke, although he indicated they are well on the way to producing a 4.4.3 build.
[Verizon Samsung Galaxy S III] natethegreat86:
With the fixes in 4.4.3 it should only get better too :)

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

I'm just wondering if lean kernel would work well on this, it's my kernel of choice. Will try, test, and let everyone know.
[Verizon Samsung Galaxy S III] sk2:
How do I fix this? I've tried everything.
[Verizon Samsung Galaxy S III] cinco312:
Maybe update your Gapps?
[Verizon Samsung Galaxy S III] sk2:
That didn't work.
[Verizon Samsung Galaxy S III] 1BadWolf:
A little bit of background info? Clean flash, dirty flash, stock kernel, custom kernel, xposed framework and/or modules, any additional tweaks, etc?
[Verizon Samsung Galaxy S III] sk2:
I just did a fresh install all good now
[Verizon Samsung Galaxy S III] sk2:
I figured out why it was happening. It was a mixer theme I was using.
[Verizon Samsung Galaxy S III] Cmotion:
First of all, great ROM! I've been a big fan of the liquid smooth ROMs for a long time now. I've only found a few small issues so far. Haven't had much of a chance to test out the camera, so i can't speak to the functionality of that.

So under Lockscreen settings -> Notification settings I have the first three boxes checked. I think they're something like Notifications On, Pocket Mode, and Always On. Some people may not like this feature as it uses some battery to constantly have the proximity sensor on in your pocket, but I liked it. I say liked because it doesn't seem to work anymore for me. Clean flash of the 6-2 build. I have unfortunately had the ui not responding error message (I forget the exact wording, basically a non-stop looping error message)... Only once in the few days since I flashed. Had to pull the battery. Other than those two things this is running smooth as always!
[Verizon Samsung Galaxy S III] TheBr0ken:
4.4.3 merge broke a few things and we're hard at work on fixing them. Yes there was a 4.4.3 screenshot that was a joke, but that was then.
[Verizon Samsung Galaxy S III] tihsllub:
I click the link form the official build and its a dead link for my device. Can someone help me out with a direct link to the builds?

Sent from my........
[Verizon Samsung Galaxy S III] 1BadWolf:
http://www.drdevs.com/devs/teamliquid/Nightly/S3_Unified/
[Verizon Samsung Galaxy S III] tihsllub:
Which one is the official release. I noticed the bottom one is only 66bytes is it the md5?

---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------

Or are they still betas?

Sent from my..........
[Verizon Samsung Galaxy S III] Wh1t3Rose:
They are all official semi-nightly releases. In other words they are more stable then beta releases but are not milestones. Expect a few bugs here and there but are daily driver ready.
[Verizon Samsung Galaxy S III] hallstevenson:
More stable than betas? Nope... Nightlies are (semi-)automated builds with effectively ZERO testing. That said, I run them all the time.
[Verizon Samsung Galaxy S III] snafufx:
Is anyone having any issues with sms messages not sending? I installed this rom and everything worked like a charm...until I tried to send a text. For some reason (or by luck) every time I re-flash, I can send the first text message. Everything after that indicates message not sent. I've downloaded this twice, got 4.4.3 and 4.4.2 PA gapps to no avail. Using ChompSMS and changed that to default SMS app. Other than that, everything worked like a charm but that's enough to go back to my TW rom.
[Verizon Samsung Galaxy S III] helobubba88:
Known issue with AOSP:

http://xdaforums.com/showthread.php?p=50537954
[Verizon Samsung Galaxy S III] snafufx:
Thanks for the link, I'll read into that, hopefully I'll be up and running in no time.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I've been having problems not being able to send/receive MMS. Would that workaround apply to my problem?

---------- Post added at 08:44 PM ---------- Previous post was at 08:38 PM ----------

While that may be true betas are used to introduce new features or when switching Android versions. So they tend to be somewhat less stable then a nightly. In fact expect some features to not work at all like data, texting, or WiFi. While nightlies are in fact built by a bot with no testing they are usually using a stable base with a few testing goodies thrown in that may benefit some users but may by a tag buggy. That's how I see it anyways.
[Verizon Samsung Galaxy S III] 1BadWolf:
↓↓↓

I just tested MMS and it did work for me BUT it did take longer than usual. I'm using 8sms on Sprint.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Ok. Sorry I meant Verizon only. Because Verizon is the source for the MMS problems I believe.
[Verizon Samsung Galaxy S III] snafufx:
It worked for me, every one I sent out went through. All I did was flashed MB1, installed rom, gapps, reboot. Thanks again for the help, now everything works perfectly.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
So i the MF1 and ML1 radios are the problem? Go back to MB1?
[Verizon Samsung Galaxy S III] snafufx:
For me, going back to MB1 solved my issues. I was Alliance Rom w/ ML1 baseband http://xdaforums.com/showthread.php?t=1788313
[Verizon Samsung Galaxy S III] jlokos:
I have had no issues with MMS on ML1 radio.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
OK thanks I'll give that a shot later tonight when i get off work

Many people have though. There's a whole giant thread about it either in general or Q&A. It's an AOSP issue for only Verizon users.
[Verizon Samsung Galaxy S III] jlokos:
I am on Verizon; if my recollection serves me, I do recall this issue earlier on 4.4 roms in certain service areas. It was not a problem in my area. Many folks resolved the issue then by going back to a TW rom. It is strange that it effects some phones and not others.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
You are correct. Going to back to a TW ROM does in fact fix the problem. But I love AOSP to much. It's actually a area code problem but my area code has not been reported as one of the area codes with problems. I'm hoping downgrading my modem will fix it. Will find out in a couple of hours and report back.
[Verizon Samsung Galaxy S III] sk2:
I don't recall what build it was in but the theme chooser had the ability to select what items you want themed. Does anyone know of that app or another similar?
[Verizon Samsung Galaxy S III] DrkGhst87:
I know for sure it was in the 6/7 build of v3.1. I'm on the latest and it's no longer there. Never used it so don't know why it was removed, and haven't restored it in titanium to test... maybe later
[Verizon Samsung Galaxy S III] big_edd:
How did that go?
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Haven't done it yet. Can you believe it! Lol. Just been really busy with my new job. I am going to do it tonight though. I will have time.
[Verizon Samsung Galaxy S III] elrichmeister:
Does anyone have a different camera app to flash? I've done pa 4.4.4 gaaps full modular. It said that it didn't include the new google camera.

I'm getting reboot when i switch to FFC and I take a picture.
[Verizon Samsung Galaxy S III] hoodieNation:
Use an older version of pa gapps. I've got a 4.4.2 version I kept. It's the older camera but it works all the time.

-Still rocking Beans20-
[Verizon Samsung Galaxy S III] elrichmeister:
Hmm looked on the PA Gapps thread for the an older version, and i found one dated 4.4.2 20140608 full modular, and it still has the same camera, and still the same issue. I also noticed that i need to flash the google keyboard separate, if i flash the modular pa gaaps, the keyboard force closes and never comes up.

Maybe its something i can bring up on the pa gaaps thread. Just wondering what gapps people are flashing here since FFC bug has been around for a while.
[Verizon Samsung Galaxy S III] hoodieNation:
pa_gapps-modular-full-4.4.2-20140201-signed.zip

That's what I used, and the camera works fine me.

-Still rocking Beans20-
[Verizon Samsung Galaxy S III] 1BadWolf:
I've been on Bank's 6-2_GApps_Minimal_4.4.3_signed.zip for almost a month's worth of dirty flashing. (I'm that kind of dude)

I've never experienced the FFC bug. Are you using the Google camera or the AOSP? I saw [MENTION=3683699]DrKaotica[/MENTION] reporting that they were having that same problem with the Google camera but it stopped when they switched back to the AOSP app. See here.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Yes its an issue with the Google FFC
[Verizon Samsung Galaxy S III] snafufx:
I installed the latest build (7/4/14) and everything went smooth minus one issue. My swiftkey keyboard doesn't seem to like this build (this worked fine on previous builds). I installed the keyboard, selected my theme but no matter which theme I choose the keyboard is "blank" until I press something on it, then the pop-up shows the letter I'm pressing. Has anyone else have this issue? The AOSP keyboard and Google keyboard work perfect, but like swiftkey to resize the keyboard itself. Thanks.
[Verizon Samsung Galaxy S III] 1BadWolf:
Yup. It's been discussed some of the other threads.
[Verizon Samsung Galaxy S III] snafufx:
Thanks so much for the link, guess I'll stick with google keyboard until swiftkey catches up.
[Verizon Samsung Galaxy S III] jlokos:
BT

Anybody know if BT works on 7/8 build?
[Verizon Samsung Galaxy S III] poppers162:
Anywhere I could find the pre-installed kernel for this rom as a stand alone zip?

Sent from my Unlocked SCH-I535 running whatever rom I've chosen for the day.
[Verizon Samsung Galaxy S III] sbattosai:
http://www.drdevs.com/devs/teamliquid/Kernels/d2lte/Deathly1.0-d2lte-kernel-signed.zip
[Verizon Samsung Galaxy S III] Hybridnoob:
Will this thread be updated our will a new one be added for Liquidsmooth 3.2? I hope to keep up with it on XDA in addition to G+.
[Verizon Samsung Galaxy S III] J913B:
I have an odd bug I can't seem to find a solution for. Whenever I search for anything in Google Now, I can't interact with the actual result. For example, pulling up the weather, I can't interact with the actual weather part. I can click any link below the "card" but the card itself won't move. Same with looking up a place. If I say "Home Depot", it will pull up the results, but I can't click call/directions/etc. Anyone encounter this?
[Verizon Samsung Galaxy S III] Nomad1600:
Does Bluetooth work on latest version (taking incoming calls via Bluetooth earpiece and car)?
[Verizon Samsung Galaxy S III] jetjaguar:
What dialer?

Does anyone know what Phone application is used in this ROM?

Thank you.

Jet
[Verizon Samsung Galaxy S III] sk2:
Any way to get mms working on the later builds?
[Verizon Samsung Galaxy S III] twistedillutions:
Try this

For those of us on Verizon, try this from Mastamoon in the CM11 thread:<br />

<br />

"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. <br />

<br />

I use this and don't have a problem. Obviously won't work well if your not on VZW."<br />

<br />

Seems to work best with the ML1 modem for me. Also, there's a good possibility the newest nightly might fix this built in. Have to wait and see.<br />

<br />

<br />

Sent from my GS3 running CM11<br/>
[Verizon Samsung Galaxy S III] cinco312:
i'll give this a try. Not fixed in the 10/2 build, also getting random reboots every few minuets.
[Verizon Samsung Galaxy S III] twistedillutions:
Im on pac-man rom at the moment. But it could be a bad flash or download. Try re-download the rom and reflash.

Due to bad battery life i might come back to ls..
[Verizon Samsung Galaxy S III] htrowpiks:
10/5 d2LTE build has no data for us cellular....
[Verizon Samsung Galaxy S III] Deafdan02:
Has the verizon issue been addressed in the recent builds? Thinking about updating from 4-11 to 10-21. If not, what seems to be the most stable of the updates ? At work, but been reading here and there. Thanks for the continued support for gs3!
[Verizon Samsung Galaxy S III] OptoChip:
Running 10/21 on my d2vzw since it was built and uploaded to Dr Devs with only a few random reboots on the stock Blackbird kernel, but I flashed over to LeanKernel v9.15 and have had literally 0 issues since.
[Verizon Samsung Galaxy S III] zcar.300:
Just installed this ROM. Wipe everything like you're supposed to. It is not rooted. Are we unable to root lollipop yet?
[Verizon Samsung Galaxy S III] MrBrady:
You have to flash SuperSu separately.
[Verizon Samsung Galaxy S III] zcar.300:
Sorry the only supersu I've used was an app. Where do I get the flashable version?
[Verizon Samsung Galaxy S III] MrBrady:
http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
[Verizon Samsung Galaxy S III] zcar.300:
Can that br done with odin?
[Verizon Samsung Galaxy S III] MrBrady:
Flash in recovery.
[Verizon Samsung Galaxy S III] zcar.300:
Clockworkmod Doesn't recognise the file. And when I do anything in Rom Manager it says "an error occurred while attempting to run privileged commands!".

I got root again. It was my fault I didn't recognise the fact that it was looking at the system directory rather than the directory where everything is actually stored.

Also is there a known problem with the microphone? When trying to type using voice to text or when shazam tries to listen for a song it doesn't hear anything. Also when I'm on a phone call neither side can hear each other unless i use speaker phone. :(
[Verizon Samsung Galaxy S III] zcar.300:
Has anyone ran into this issue?
[Verizon Samsung Galaxy S III] tarigand:
Hey everyone. Currently running 8/18 v 3.2 and got a random reboot. I was thinking okay this is normal as I have not had a random reboot in a while, but when I went to messenger, all of my messages were gone. I tried all the messaging apps, but it seems like the reboot wiped the data. Any thoughts on how to get it back?
[Verizon Samsung Galaxy S III] cinco312:
Not sure if you can without a backup. This ROM is dead. There's a 5.0 version that is very stable. http://xdaforums.com/galaxy-s3-verizon/orig-development/rom-samsung-galaxy-s3-liquidsmooth-t2959428
[Verizon Samsung Galaxy S III] tarigand:
Currently running build Milestone 3.2 from 11/2. Having trouble sending MMS with Verizon.
[Verizon Samsung Galaxy S III] cinco312:
There's an MMS fix in this thread somewhere. I know I posted it and a few others have a while back. I'll scour through the thread to see if I can find it.
[Verizon Samsung Galaxy S III] tarigand:
Thanks for your feedback. I tried the mastamoon fix, but it completely crippled my messaging. Could not send or received. I just went back to a backup and I'm back up and running.

:).
[Verizon Samsung Galaxy S III] johnnytraveler:
Try the night before. That one worked for me. BTW,I had the same problem as you with 2-2.

---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------

Yes, it is now universal for all S3.
[Verizon Samsung Galaxy S III] twistedillutions:
Ok im. Back again i clean flashed thr 2/1 build jst stays on bootloop. Tried 1/30build flashes fine no problems. Back to recovery dirty flash the 2/1build again stays stuck on bootloop.. Bad build.. The 1/30build works fine
[Verizon Samsung Galaxy S III] DrkGhst87:
It's already back... Just have to dig a little.

Settings > Navigation > Hardware Buttons

Make sure to enable it and you can change them to what ever you like, i.e. hold back to kill app

Same thing with lock screen torch...

Settings > Lock Screen

Select "Slider Torch" to enable lock screen torch. Might not be exactly the same way but it does the same thing.

Just tinker and dig and you'll find what your looking for next time...
[Verizon Samsung Galaxy S III] RBarnett09:
Thank you man.

I am on an older build of it.

Good information.
[Verizon Samsung Galaxy S III] DrkGhst87:
No problem. On the 1/30 or 1/31 build myself and loving it. Not missing to many features from previous builds, only thing I've found missing is lock screen wallpaper but there is a xposed module that works great so using that for the meantime. Still getting all the new settings down lol. Love this Rom.
[Verizon Samsung Galaxy S III] griz.droidx:
So the consensus is, don't flash 2-1 or 2-2 correct? I didn't see 2-2 on drdevs.. I downloaded 2-1 last night but never got around to flashing it. So from what I've read, I probably shouldn't flash either correct? I can deal with the screwy busy icon. This rom has all the features I've been looking for in a rom. It fits ME. It may not fit everyone, but for me, it works great. I'm missing a few items in the messaging app, but I'm sure I can find another that has what I need. Anywho.. thanks for such an awesome rom with the features I want and need.. I don't even have to load Xposed.. YAY!

So question. If I were to dirty flash the 2-1 build would that work? Or should I just stay on 1-31 until a newer build drops? The one I'm running now is worthy of a nandroid.. In my opionion. I'm going to make a nandroid and might try dirty flashing (something I hate doing), 2-1 to see how it goes. Because it seems that no one is having any luck wiping and flashing the newer builds.
[Verizon Samsung Galaxy S III] cr4ck3r4lif3:
TWRP doesn't work with this rom. Use CWM
[Verizon Samsung Galaxy S III] flyestAC:
Interesting. I flashed the last d2vzw build and the first lte with twrp.
[Verizon Samsung Galaxy S III] twistedillutions:
False i been using twrp latest since the first 4.4 beta build of LS. Used it for other KK roms.

---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------

Dirty flash did not work for me. Also if u wanna try yes make a backup. Hope it wort for u. So far clean or dirty flash hasnt work for me and couple other posters
[Verizon Samsung Galaxy S III] cr4ck3r4lif3:
Strange. This is the only 4.4+ rom that twrp fails to flash. I've heard a few others have the same issue.