yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Known issue
[Verizon Samsung Galaxy S III] mbsmd:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Thanks. Any work-around to get back in? Can I reinstall ROM without deleting data to reset the lockscreen settings?
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Hmm, I'm not sure. I didn't try it
[Verizon Samsung Galaxy S III] PsiPhiDan:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Does anyone else get stuttering when playing music and doing something else (messaging, Internet, etc)?
[Verizon Samsung Galaxy S III] Tazilla:
No it's just the stable build. The one before the official build.
[Verizon Samsung Galaxy S III] cybertec69:
Goo Manager keeps telling me that there is an update to my ROM, I believe I am running the latest one.
[Verizon Samsung Galaxy S III] tihsllub:
Qwerty keyboard doesn't landscape when phone is turned.
[Verizon Samsung Galaxy S III] tihsllub:
About phone should tell you your ROM info.
[Verizon Samsung Galaxy S III] cybertec69:
I am all good, now I am running the latest one, so far it's running smooth. Really had no problems with the last build, what improvements have been baked into this one.
[Verizon Samsung Galaxy S III] tihsllub:
Yay got my keyboard working.

---------- Post added at 07:51 PM ---------- Previous post was at 07:46 PM ----------

OK weird issue. I flash the old SuperSU every time I flash a new ROM so that it forces an update. I had to open SuperSU 5 times before it stayed open. I am having just really odd app closings with other apps also. No toast messages just gone. Hmmmm
[Verizon Samsung Galaxy S III] cybertec69:
Already discovered one bug, the verge app keeps crashing as soon as you open it.
[Verizon Samsung Galaxy S III] mike216:
I found a changelog on twitter. Search for liquid0624 and you'll see it linked to a paste bin. If you have trouble finding it I'll try to find it.
[Verizon Samsung Galaxy S III] Zzim:
Two issues that I have with this ROM.

The first being the most annoying issue that has been present with every update. Whenever I play any music app and put the phone in standby there is a stutter in the music. This also happens when I take it out of standby right after I swipe to unlock the music will stutter once or twice. For example Apollo the app that comes with the rom for playing music I play a song put the phone in standby and it stutters. This can get really annoying when i'm answering texts and every time the music stutters when I swipe to unlock the phone.

My other issue is that my phone stays at "Activating" when I turn it on, it will go away when I hit the home button and I get cell and data service. This happens with more then just this ROM so it might be normal.

Any ideas on the music stutter that I can try?
[Verizon Samsung Galaxy S III] DroidHam:
Maybe the official version should get pulled.... Seems like it has alot of problems....

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

Here's the stable version...

http://ge.tt/m/4ooLkId
[Verizon Samsung Galaxy S III] tihsllub:
I'm not having any issues. I clean flashed and let my phone rest. No problems since. Had some crash messages for gmail and YouTube but its been fine since.
[Verizon Samsung Galaxy S III] burningembers:
LS v2.1 STABLE = Smooth, fast, no issues except for the "Always On" LED option that has never worked right.

LS v2.1 OFFICIAL = Choppy, laggy, random apps keep randomly crashing without a Force Close message, black screen of death, sometimes touch screen becomes completely unresponsive despite screen being on..."Always On" LED still doesn't work :P

Not sure what's up :(

I've clean flashed it, ODIN-wiped everything and clean flashed it, formatted every thing possible and clean flashed it. No go.

Went back to STABLE and all the problems disappear (except for LED). OFFICIAL must just hate me :(
[Verizon Samsung Galaxy S III] tihsllub:
I'm sorry your having issues with the ROM. I really recommend letting this one soak in. First flash I didn't have root. But I reflashed and bam root. Then I let it soak in and everything sorted itself out. Runs great.
[Verizon Samsung Galaxy S III] DroidHam:
Makes no sense lol you shouldn't have to let it soak to get root

---------- Post added at 10:42 PM ---------- Previous post was at 10:42 PM ----------

If official works for you, great. If not, I posted a link to the stable.
[Verizon Samsung Galaxy S III] tihsllub:
My superuser binary didn't update when I started my phone. So I went round 2 factory reset and system wipe. Then flash ROM flash kernel(kt747) then a superuser zip. Started phone then opened superuser and all is well in the world.

---------- Post added at 10:04 PM ---------- Previous post was at 10:01 PM ----------

And I meant soak as in let the phone sort itself out when you flash a new ROM. You can't race a fresh built engine because your rings aren't cut in and your bearings are bedded in. You have to run it at low speeds until the breakin is completed. Flashing a ROM is the same way. Phone has to figure out the correct and fastest paths.

---------- Post added at 10:48 PM ---------- Previous post was at 10:04 PM ----------

Anybody notice that the sleep mode is missing from quick settings. It looks to be replaced by power. Bummer I used it. Put my phone directly into deep sleep which helped it last longer. To the tune of 12 hours of moderate use and having roughly 40%+/-
[Verizon Samsung Galaxy S III] masri1987:
People the force close issue was a CM issue from 4/1 - 4/4, being fixed on 4/5 nightly.
[Verizon Samsung Galaxy S III] jamesino:
A car engine and a ROM are not the same thing; one is mechanical and the other is digital.

A new ROM or kernel shouldn't take more than an hour and one or two reboots to "soak in"
[Verizon Samsung Galaxy S III] tihsllub:
Exactly but how many are trying to "see what she's got" after the flash? And not letting the phone settle in?
[Verizon Samsung Galaxy S III] rhamorsky:
When i first installed OFFICIAL, it took about 15 mins for the phone to settle and show root status. after about 10 hrs had an SOD. Then i changed kernels to the bms EASTER build and after almost 24 hrs and moderate use, the only problem i have is with google play fc's. Had that issue since CM 10.1 came out and also have that same issue on my UNROOTED Galaxy Note 10.1. IMO, the new 3.4 builds arent quite as snappy as the older 3.0 builds but initial growing pains are about the same. If i wanted no problems, id go buy a brand new phone and run it as is. Where's the fun in that?
[Verizon Samsung Galaxy S III] Azuma73:
Hah, True dat yo!! :p

Running new build just fine here(clean flash). Noticed LeanKernel is now baked in. Only issue I've noticed so far is that my beaut widgets time display won't update.....lockscreen or home!?!? :p

Killer work to all those involved!!
[Verizon Samsung Galaxy S III] tihsllub:
Only issues I have is a couple app windows that like to close on their own. And it stops by reopening app until window stays open. Reboot ur phone and ur back to square one with that issue. If that's the worst I'm fine with that because TW is annoyingly bland. All my friends are all running stock phones. Makes me want to puke when I try navigating their phones.
[Verizon Samsung Galaxy S III] DroidHam:
Checkout Beans. It has some nice customization with the stability if tw
[Verizon Samsung Galaxy S III] KINGDROID25:
Has anyone had issues with GPS??.. I tried using it yesterday but every so often it would say GPS signal lost which made it hard to get to a family function..

Also will there b a re release of the rom cuz of the bugs tht everyone have been dealing with??.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] cybertec69:
Went back to the previous build, some of my apps just keep force closing.
[Verizon Samsung Galaxy S III] gseyffert:
I had this issue as well. Go to Settings -> Sound and make sure you have lock sounds and touch tones unchecked. What you're hearing is that little click that goes off when you un/lock your phone, which just plays silently it you have your volume off, and interrupts the music. Changing this setting solved it for me.

---------- Post added at 01:21 PM ---------- Previous post was at 12:52 PM ----------

So how is this build as compared to the 3/16 one? I'm still running that one with absolutely no issues, so I'm a little wary about switching up to the newest one.
[Verizon Samsung Galaxy S III] tarigand:
Is anyone else experiencing the "tap to refresh" on the cLock widget? I am on the Official build and still can't get it to refresh.
[Verizon Samsung Galaxy S III] DroidHam:
Yup

---------- Post added at 06:07 PM ---------- Previous post was at 06:07 PM ----------

I had the same issue on the official build its messed up
[Verizon Samsung Galaxy S III] gseyffert:
Well I updated to the newest version. The only little glitch I'm getting is that the screen will randomly go dark for a second or two when I'm navigating the launcher and drop me out at the default screen. Anyone else having this issue?
[Verizon Samsung Galaxy S III] tihsllub:
Please don't say cLock is acting up. I haven't had an issue with the latest download. Sigh.... Now I'm gonna be on my guard.
[Verizon Samsung Galaxy S III] mike216:
Ya man, I don't know everything has been great after flashing BMS recent kernel and fixing permissions. Things weren't too bad before doing this. I did get some YouTube force closes which made me want to fix permissions. The 3-22 and recent builds are great. Clock working GPS and everything else
[Verizon Samsung Galaxy S III] jamesino:
LeanKernel v5.2 is up by the way.
[Verizon Samsung Galaxy S III] Azuma73:
So, should I zap that phucker!?!?!? Link me "pour fAvour"!?!?!?!?
[Verizon Samsung Galaxy S III] mademan420:
http://rootzwiki.com/topic/32286-kernel-aosp-jb-v52-4413-leankernel-minimalistic-kernel/
[Verizon Samsung Galaxy S III] jamesino:
For future reference, am I allowed to directly link to the developer's download link? Or could I only post a link to a forum post where the developer himself posted a download link?
[Verizon Samsung Galaxy S III] mademan420:
Not 100% sure so to be on the safe side, I just post a link to the forum and leave it up to the person to locate the link;)
[Verizon Samsung Galaxy S III] vzw2491:
I don't know if this is just me or what, but is anyone else having trouble to get "force dual panel" to work? i check mark it, restart my phone, and nothing happens. When i go back into settings, interface, it's automatically unchecked. I even tried to use xposed DPI settings by changing the screen (dp,px) to 800 x 1280 for "com.android.settings" which always used to work for me. I can change the DPI and that works fine, but the dual panel isn't working at all. Anyone have any suggestions?

It's not really a big deal at all. But i really love having the dual panel view.
[Verizon Samsung Galaxy S III] jamesino:
I just flashed a BMS kernel. Things are working well so far, but everything looks a bit...bluer.

I'm not sure how to quite describe it, but the vibrancy and color/saturation is def. a bit different than LeanKernel. Not sure which one is the most accurate color profile, but it's definitely a bit different.

Is this normal? Do kernels affect your color profile?
[Verizon Samsung Galaxy S III] jakereeves31:
Why wouldn't you ask in that kernel's thread?
[Verizon Samsung Galaxy S III] jamesino:
Found it, it's because it's packaged with Trinity Colors. The stock kernels, including LK I believe, had a slight yellowish cast to them. You won't notice is until you try it with Trinity Color color profile.
[Verizon Samsung Galaxy S III] newbie4ever:
I think some kernels do have different color settings, i would say pic the one that you like better
[Verizon Samsung Galaxy S III] gseyffert:
I'm still noticing a general choppiness running this over BMS. No more force closes anymore thankfully, though! (Knock on wood). But even overclocked to 1674 MHz and having my minimum set to 910 there's a general choppiness, especially when doing things like pulling down quicksettings. It's not there as much when I'm just navigating the launcher, but very noticeable upon waking up the device and navigating settings menus.
[Verizon Samsung Galaxy S III] mike216:
Go in recovery/advanced and fix permissions. It helped with the force close issues for me. I changed my DPI and was right back at square one with the force close issues but that's a different story. You might have to uninstall and install the xposed app that's built into the rom if your using it to change the DPI. After fixing permissions my apps went back to 320. Hope it works for anyone getting force closes. Everything is going well so far after some frustration
[Verizon Samsung Galaxy S III] cybertec69:
Installed the stable ROM, "official is buggy" but it seems to show the wrong internal memory size, my phone has 16 gigs internal, if you look at the rest of the storage the numbers do not add up.
[Verizon Samsung Galaxy S III] cybertec69:
View attachment 1867274

I know that 4 Gigs are used up for system memory, so if I have 12.5 Gigs left, according to the chart I should be left with 7 plus Gigs, not 3 plus gigs.

,
[Verizon Samsung Galaxy S III] Dearborn1977:
On music stutter, try a different kernel like BMS. As for activation issue, that's been well covered in this thread and pretty much all others. Settings - mobile networks - cdma subscription - change to RUIM/SIM.
[Verizon Samsung Galaxy S III] gseyffert:
I tried to stick with the new build, but had to flash back to the 3/16 build after waking up and seeing that NFC Service had kept my phone awake for 13 hours while I was asleep...
[Verizon Samsung Galaxy S III] dzy_1:
I've been wanting to use Liquid as my daily, but I seem to keep getting one big issue. The LTE speed for me is horrid on this rom for some reason. Other ASOP roms (slim, carbon) are fine, but Liquid only gets me about 1.5Mbps down (never seen it hit 2)...With other roms I'd get in the 3-6 range signal depending. Is anyone else experiencing this?
[Verizon Samsung Galaxy S III] david_hume:
Nope. I've gotten 28mbps download on a 3 bar. Pretty much the same with every ROM I've used.
[Verizon Samsung Galaxy S III] nemofbaby2010:
which radio are you using?
[Verizon Samsung Galaxy S III] cybertec69:
How come stable version runs better than the official version, now I have goo manager constantly reminding me that there is an update for my ROM. The official version has a few bugs that need to be ironed out for it to be a daily driver, a few of my apps open then just close, and when switching between wifi and LTE the phone does a quick reboot, never had these issues with the stable version, so my question is why was this official version pulled out of the oven, apparently it was not fully baked yet.
[Verizon Samsung Galaxy S III] mike216:
Date seems pretty solid for me
[Verizon Samsung Galaxy S III] jakereeves31:
And when he says date, he means data:P
[Verizon Samsung Galaxy S III] cybertec69:
Nice speeds, I used to get those, not anymore, I live in new York City, the only time I might see speeds like that again is real early in the morning, lol.
[Verizon Samsung Galaxy S III] mcdevil58:
I'm getting 7 down and 2 up with 2 bars on LTE
[Verizon Samsung Galaxy S III] david_hume:
Because of the 3.4 kernel. 3.0 is a lot more stable and will be for quite some time.
[Verizon Samsung Galaxy S III] pringlet:
google speech to text isn't working on latest build

is the google speech to text crashing on anyone else? Whenever I trigger it either from the keyboard microphone icon or the google search widget, I get a flash of a popup message and that's it.
[Verizon Samsung Galaxy S III] Shallow_1:
I'm not
[Verizon Samsung Galaxy S III] WillisD:
Have you updated Google search?
[Verizon Samsung Galaxy S III] PsiPhiDan:
There's a ROM called "official is buggy"?

Glad to hear it's stable though - seems awfully ironic. ;)
[Verizon Samsung Galaxy S III] cas239:
Update your Google search app in the play store
[Verizon Samsung Galaxy S III] Jwaves:
Ok so im using the stable version. Im loving it and getting slightly better battery life with this as far as far less bugs than I am on the official version. My BIGGEST PROBLEM is that at least twice a day my phone freezes it mostly happens when im on the phone. I have to then take off the case (which is somewhat of a hassle) and pull the battery of course. Is there any time of short term fix that could keep this from happening less frequently?
[Verizon Samsung Galaxy S III] VinBertinelli:
Now that's what I call battery life volume 2

Only 50 mins of screen time but 15 hours of the charger
[Verizon Samsung Galaxy S III] Aashiqmunda:
Bug: After setting a custom Device hostname in the Development menu and rebooting the device, it sets back the Device hostname to default.
[Verizon Samsung Galaxy S III] jakereeves31:
That really doesn't seem very good to me
[Verizon Samsung Galaxy S III] jamesino:
Could increasing the minimum clock speed of the deep sleep state help prevent SODs since one of the causes of SODs is the fact that the core is underclocked too low to wake up?
[Verizon Samsung Galaxy S III] Jwaves:
ill try that. but im getting great battery life the way everything is now. do you think that would have a big effect on the battery while deep sleeping?
[Verizon Samsung Galaxy S III] fathertomany:
LIQUIDSMOOTH restarts my phone when I try to play candy crush saga.

Sent from my LIQUIDSMOOTH SGH-T989
[Verizon Samsung Galaxy S III] mcdevil58:
What kind of battery life do you normally get?
[Verizon Samsung Galaxy S III] pringlet:
That did the trick. Thanks!
[Verizon Samsung Galaxy S III] mt3g:
Anyone itching for rc2(most stable IMO) with the Headset Control bug fixed? I can make the zip for you guys if you'd like. Don't just "thank" my post, let me know if it'll be worth my time :)

T-Mobile SGS III
[Verizon Samsung Galaxy S III] Jwaves:
does this use the 3.4 kernel?
[Verizon Samsung Galaxy S III] mt3g:
RC2 is 3.0 and stable as a rock with the fix implemented.

T-Mobile SGS III
[Verizon Samsung Galaxy S III] jamesino:
RC2 was the build right before Liquid fixed the headset control right?

If this is the case, then yes please!!!! I was literally just thinking about this a few days ago. I'm currently running the v3.0 version with the headset buttons fixed, but I still get SODs every 1-3 days. Thank you so much!
[Verizon Samsung Galaxy S III] mt3g:
correction I fixed the headset controls lol. I don't think he looked into it very much. I will make the build and post it here tonight or tomorrow morning. I need someone to get me a link of the rc2 rom though. They're not available on his site.
[Verizon Samsung Galaxy S III] mike216:
Yes. 3-22 build has been the best, in my opinion
[Verizon Samsung Galaxy S III] Zzim:
Where are the links to the previous versions and the "stable" versions? Nothing on liquid's site and the only link on goo I see is the official ROM.
[Verizon Samsung Galaxy S III] jamesino:
Look through Liquid's forum posts and you'll find them dating back from a few weeks ago.
[Verizon Samsung Galaxy S III] Zzim:
ah damn was hoping for something more organized..... a hunting I will go.
[Verizon Samsung Galaxy S III] jamesino:
Actually, the links are now all dead.

---------- Post added at 06:21 AM ---------- Previous post was at 06:19 AM ----------

Ah, sorry about that, Thank you for fixing the headphone controls! I think the newest RC2 prior to headphone fix being implemented was the build released on Mar 13th right?

I have a version called "Liquid-JB-v2.1-031213-d2vzw.zip" is this the correct one?

If so, how should I go about uploading it (if I'm allowed)?
[Verizon Samsung Galaxy S III] mike216:
Could someone please help us all and upload RC2 for mt3g so he can fix the headset buttons!

By the way thanks a lot for that fix. I couldn't run it without that option!
[Verizon Samsung Galaxy S III] jamesino:
I have the "Liquid-JB-v2.1-031213-d2vzw.zip" version on my computer. I believe this was the last build prior to the Headphone Buttons being officially fixed in the next release right? ie. Is this the RC2?

Am I allowed to upload this and where and how should I do it?
[Verizon Samsung Galaxy S III] mt3g:
No, it'll say rc2 in it. I can not find it anywhere. :( hope someone uploads it I'll check in the am guys

T-Mobile SGS III
[Verizon Samsung Galaxy S III] jamesino:
Hm, I seem to recall that when I flashed it, it said RC2 in the About Device menu setting.
[Verizon Samsung Galaxy S III] mt3g:
Upload it to dropbox and I'll look at it but I don't know why it would it'd say stable but be rc2 lol.

T-Mobile SGS III
[Verizon Samsung Galaxy S III] gseyffert:
Standby, I'm uploading the 3/16 Stable build to my DropBox right now and then I'll post the link here. Personally I prefer this build over any of the one's coming after, super quick, and haven't had a SOD in two weeks.

---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------

And here's the link -

http://db.tt/hhw7h0Fw

---------- Post added at 12:58 AM ---------- Previous post was at 12:56 AM ----------

Also, I liked the messaging app and Apollo from the official build, and they run just fine on the stable build ;]
[Verizon Samsung Galaxy S III] Instien:
I too had the same problems, however it isn't just with Liquid Smooth, but some other AOSP roms. Wish this wasn't the case because I prefer AOSP, however I went back to Touchwiz until the problem is fixed.
[Verizon Samsung Galaxy S III] fathertomany:
I am using LIQUIDSMOOTH KANG. I do not get any freezes, ever. But my version does not like the game CANDY CRUSH SAGA. If I play it for a while the phone does a quick reset?

Sent from my LIQUIDSMOOTH SGH-T989
[Verizon Samsung Galaxy S III] ThunderRootedDragon:
Hopefully all of those who are having issues are doing clean flashes and not riding dirty...lol - Also realize a lot of the "stability" issues are more likely related to the 3.4 base, which is still buggy -- even the 3.0 base kernels are not 100% solid 100% of the time.

As for me -- did a dirty flash over the 3/16 with LK and basically upgraded -- rom def felt smoother and more crisp on the tsf launcher--I like, no, I loved the new messaging custys--wanted to see what "dark liquid was" but was busy with minor theming and tsf-- but I had some fc's on two key apps (romtoolbox, secure settings, TWC) figured it was either dirty flash related or app related, but had to return to 3/16 as a result. ...I think I'll go ahead and clean flash it just to be sure.

Nice build liquid. Thanks.
[Verizon Samsung Galaxy S III] Bstin:
I have the d2usc build of RC2

https://www.dropbox.com/s/a2k1wjdr3z9z79y/Liquid-JB-v2.1-RC2-d2usc.zip

I also have a build of d2usc that was built by someone else on 3-9 which is what I used when I was on RC2 if you are interested (i don't know the benefits of it, it was also really solid though)
[Verizon Samsung Galaxy S III] mt3g:
I can use the one you linked, expect an rc2 with the headset controls fixed in a couple hours. Slowly waking up here.

T-Mobile SGS III
[Verizon Samsung Galaxy S III] cybertec69:
Clean flashed here multiple times, still went back to the stable build, the official is just too buggy.
[Verizon Samsung Galaxy S III] mademan420:
PM sent
[Verizon Samsung Galaxy S III] mt3g:
He released two days too early. The newer builds with the new cm fixes seem to have fixed a lot of the issues.

T-Mobile SGS III
[Verizon Samsung Galaxy S III] cybertec69:
When was the latest release posted.
[Verizon Samsung Galaxy S III] mt3g:
Got it and downlaoding, upload when I finish will be posted for you VZW, I recommend using the build I post as your AOSP Stable Backup, I do.

Here is USC RC2 with the headphone fix. It is a 3.0 kernel, it doesn't have any issues that the latest builds have been having. http://www.mediafire.com/?babc4ra44woobua

Here is VZW RC2 with the headphone fix. It is a 3.0 kernel, it doesn't have any issues that the latest builds have been having.

http://www.mediafire.com/?1sytzsyku8khp5h
[Verizon Samsung Galaxy S III] mike216:
Thanks mt3g! I hope we see a D2vzw build also? Good morning