yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] hallstevenson:
I copied the instructions to this thread.
[Verizon Samsung Galaxy S III] Zzim:
I don't think I ever got a response to my only issue with this ROM and I think this is something all custom ROMs suffer from. I can't seen to get the "My Verizon" app to auto update the widget. I have click on it and update it manually by logging in every time.
[Verizon Samsung Galaxy S III] PsiPhiDan:
Page 570. I didn't know they were there until about one minute ago. I saw your rant and thought, "let's see how long it takes me to find them." I looked at the build date in the thread title: "10/6", and went back several pages at a time until I found October 6th. Turns out it was on October 5th, but I was close enough that I found it easily.

All this took me about 1 minute and no swearing. :thumbup:
[Verizon Samsung Galaxy S III] RRF12:
The my Verizon widget doesn't auto update on any 4.3 rom. You have to log in.
[Verizon Samsung Galaxy S III] tlogank:
Cannot get GPS to actually lock on 2.10, which is a deal breaker for me (I use navigation and Strava almost daily). Any suggestions besides a different ROM?
[Verizon Samsung Galaxy S III] rhamorsky:
I use something i found a while back. I downloaded faster gps and gps status. In faster gps i changed the ntp server to north america and region to united states which will change the server. Then in gps status i went to tools, manage a gps state, and reset. Then back into tools, manage a gps state and redownload data. I then give gps status a minute and for me it locked. I repeat theses steps after each new ROM flash. Also make sure privacy guard is not active for any app that uses gps or you wont get a lock. Works for me, hope it helps:cool:
[Verizon Samsung Galaxy S III] doodlebro:
Hey wouldn't it be swell if they put the instructions in the OP? ****, I'm a genius! Call MIT boys.

Takes one minute and saves from people ever asking about it. DAMN.

At least a few people understand my struggle, it took 3 hours to get my phone up and running and I very well have experience with this sort of thing. Not necessarily liquid's fault (I love the ROM and used to run your thunderbolt ICS builds that you so graciously made for those of us still stuck with a POS) but my TWRP lost read write privileges and was acting funny until I couldn't do anything but boot into Odin. I apologize for my rant, but let's seriously just post instructions in the OP when you update it with the links. It's not rocket science to give the users of your ROM the easiest way to do so.
[Verizon Samsung Galaxy S III] Droid316:
Geez you flash Rom then gapps then kernel.Just like the other roms you have installed.Is it really that difficult.

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] RayMcGrath:
Liquid smooth 4.3 should have started with liquid smooth 3.0, and on a new thread with a new op. This Is a great rom! I don't understand.
[Verizon Samsung Galaxy S III] hallstevenson:
Wrong
[Verizon Samsung Galaxy S III] Droid316:
That's the way i did it and it worked fine for me.

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] hallstevenson:
Seems to me that installing the ROM wasn't the issue so I'm not sure what the **** your rant here is about...
[Verizon Samsung Galaxy S III] Droid316:
My rant? If so to me people are crying about the OP not having detailed install instructions.

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] DrkGhst87:
Not picking sides here but doodlebro has a bit of a point. I usually don't look for install instructions from some random guy, even if they are copy/pasted from the origin page. I usually check the OP for the new ROM download and check to see if anything has changed (like the install routine). If nothing is there from the ROM maintainer then I go ahead and flash. Now please note that I usually wait a few days and lurk the thread to see if people have ran into a few problems or not to warrant me waiting on flashing this new ROM. But if there isn't anything there, I flash away. If for whatever reason I run into problems I go ahead and search for myself for a fix before posting for help. Also, your post was 22 pages back for me on the app... the most I go back is 10... and again I wouldn't be looking for install instructions randomly posted within the thread that will be surely buried by the next update. Wouldn't it be better to put it into the OP where most check anyway? Any who, you also failed to mention that in some cases TWRP causes issues during install. Also noted within thread but unless you knew to look for it, it might be hard to come by. CWM is the recovery of choice to flash 2.10 to avoid install issues. Personally I would of just pointed the guy in the right direction, since it seemed he was going through a bit of trouble and just went about my day but oh well. To each their own I guess.

---------- Post added at 11:30 PM ---------- Previous post was at 11:16 PM ----------

Here's the direct link to the install instructions post bud. Also, a few users here seemed to run into problems using TWRP. Not sure if it's 4.3 ROMs that's the issue or if it's TWRP itself but CWM seems to work, YMMV. Good luck fixing your phone.

https://www.facebook.com/liquidsmoothroms/posts/372663309532084

Also, if your sticking with Liquid Smooth I would suggest following them on Facebook. They seem to post things there a lot.
[Verizon Samsung Galaxy S III] flyestAC:
Cleanup aisle 6...
[Verizon Samsung Galaxy S III] hallstevenson:
Good luck and let us know what Liquid says... In case you haven't noticed, he doesn't post / comment in this thread. This is pretty much 100% just other *users* that you're ranting at.
[Verizon Samsung Galaxy S III] TokedUp:
All the problems that you are having are directly related to TWRP. I'm still amazed that ppl use TWRP when flashing 4.3 roms. It just doesnt work right. Change your recovery and get over it.
[Verizon Samsung Galaxy S III] &roid:
This is true...
[Verizon Samsung Galaxy S III] brons2:
The widget didn't auto-update for me when I had the stock rom, or Synergy, or anything else. Maybe I'm doing it wrong but just my observation.
[Verizon Samsung Galaxy S III] hallstevenson:
Works fine here....
[Verizon Samsung Galaxy S III] kerfex:
Sorry no Inet over the weekend

Sorry for the lase replay, I have no data connection where I live and my Inet was down over the weekend.(Vermont) But, yes I am using the latest gapps listed in the OP on 2.10 (gapps-jb-20130813-signed.zip)and when i switched back to 2.9 I used the gapps-jb-20130301-signed.zip.
[Verizon Samsung Galaxy S III] hallstevenson:
Yeah, same here. I read "auto update" and thought, "it doesn't auto-update even on stock !". I was using it quite a bit after we switched from unlimited to a 4gb/mo plan.
[Verizon Samsung Galaxy S III] tarigand:
Hey all. Still on 2.8 and working on bringing up the courage to flash 2.10. I did have a couple of questions regarding 2.10.

1. are people experiencing reboots during phone calls?

2. are people getting a lot of reboots randomly?

Also, does anyone have an MMS.apk that has the default white background and not the black one?

Thanks.
[Verizon Samsung Galaxy S III] rhamorsky:
Me too! No problems with TWRP. I think alot of people have problems because kernels and recoveries tend to be updated to accommodate new android versions but alot of users are still using older versions. Just my two cents worth. If im wrong then.....awwww hell!:p
[Verizon Samsung Galaxy S III] doodlebro:
Looks like I'll just be sticking with CWM from now on... Strange how TWRP has such trouble, but a quick reflash of recovery was all that was needed before it worked again. I appreciate the link to the instructions and the general help. It'd be nice if the moderators of this board could take 5 minutes to set general rules for how the OP is structured in these release threads. All that is missing here is the most basic of instructions. Or a nice warning for those of us who have just sat on 4.1/4.2 for awhile and came back recently for something fresh.
[Verizon Samsung Galaxy S III] DrkGhst87:
No problem at all. Glad everything works.

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

Not ranting, merely making an observation. I'm constantly ROM hopping, so paying attention to how each ROM dev works in maintaining their thread is of little importance, since most devs post important info in the OP. If that's how liquid works that's fine, never had a problem with installs or the ROM thus far, but for others that may run into problems it would be nice. I'm sure not everyone knows to follow them on Facebook, something that isn't in the OP, for updates. Not trying to argue here. Wasn't my argument to begin with. Just trying to help out.
[Verizon Samsung Galaxy S III] hallstevenson:
Trust me, I checked the OP for instructions myself after I saw Liquid's posting on Facebook. Worse, someone from LiquidSmooth's team updated the OP after v2.10 was released ... and still left out instructions !

As I mentioned above, this thread is pretty 99% user-supported - I haven't seen any posts from Liquid for a while. Granted, they really CAN'T either - they build ROMs for multiple phones on multiple carriers.
[Verizon Samsung Galaxy S III] cinco312:
Awesome bro! I been waiting for these. Thanks!
[Verizon Samsung Galaxy S III] gseyffert:
Is there any way to slow the transition speeds between apps down? I like the update, but everything moves a little too quickly for my taste...
[Verizon Samsung Galaxy S III] cinco312:
Go into settings/Development/ then scroll down to "Drawing" you'll see Window, Transition, and Animator scale. I have mine set to .5
[Verizon Samsung Galaxy S III] gseyffert:
Thank you! It's been a while since I've rooted around in the settings much.
[Verizon Samsung Galaxy S III] cinco312:
No problem brother. Make sure you unlock Developer settings first by going into Settings/About phone and tapping the build number repeatedly. Can't remember if it's unlocked by default or not.
[Verizon Samsung Galaxy S III] Wh1t3Rose:
You know it's really not that difficult. Anyone that has flashed a ROM more than once knows that you wipe data and the flashable zip wipes system for you. Flash gaaps that matches your android version. Thats it. It is not difficult. It never changes. I don't care what ROM you flash. It will never change. If anyone can't remember this simple process then they have no business flashing ROMs and should just go back to stock. I'm tired of seeing people complain all the time. I understand people reporting bugs or even asking for help on how to do something. But saying that the Dev NEEDS to do something is just wrong. Learn to research things yourself or ask very nicely in the thread. Do not attack the developer. People also seem to forget that this is a DEVELOPER forum NOT a help/support forum. So learn things as simple as the install process or go back to stock.
[Verizon Samsung Galaxy S III] zamball:
Reboot Hangs on S3 Boot Image

* I am unable to search this thread since the search function is not working...

Has anyone else come across a reboot issue where the system just hangs on a reboot on the Samsung Galaxy S3 logo? The only way I have found it to get around it is to restore from a backup after formatting the internal SD. Then going back to a backup using TWRP.
[Verizon Samsung Galaxy S III] &roid:
I had that issue when I installed with TWRP and apparently it only affects certain phones. To fix, I installed the latest CWM and flashed. All had been fine since.
[Verizon Samsung Galaxy S III] yamaha_wins:
I've had zero reboots. During phone calls or anything.. Black MMS? My messenger has a white background..

Only problem I had was with the building tether which I dirty flashed the ROM over the install and that fixed the issue.
[Verizon Samsung Galaxy S III] Droid316:
So informative.

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] joshua5683:
*tells a long speech full of common complaints of our society and gains tons of thanks*
[Verizon Samsung Galaxy S III] Droid316:
True story

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] zamball:
I am assuming after you installed CWM you did a clean install of LS? Did you install a 10.2 Nightly or did you install the latest stable?

Thanks for your help!
[Verizon Samsung Galaxy S III] hallstevenson:
Yet correct.

Instructions for this build have been posted and they are not "standard"
[Verizon Samsung Galaxy S III] Droid316:
"Right"

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] hallstevenson:
Normal custom ROM install steps:

Install ROM

Install gapps

Reboot

Liquid 2.10 install steps:

Install ROM

Reboot system

Setup your phones settings, anything that isn't Google related or let your phone sit for 5 minutes

Reboot back into recovery

Wipe cache and dalvik

Install gapps

Reboot

(copied from Liquid's Facebook posting and trimmed slightly)
[Verizon Samsung Galaxy S III] kerfex:
You dont have to do all that

I was having problems with 2.10 and went back to 2.9 but it was " glitchy" So here is what i did. I went back to full stock using odin. S-on no root and original stock rom. Set everything up and ran it stock for a day. Then I went through the whole process of getting S-Off and root again.

Then I factory wiped three times. Wiped the cache three times and wiped the Dalvik three times. Then I flashed the ROM, then flashed Gapps then rebooted and set everything up just like normal. Works great. Smooth it is and runs like it came with the phone from the factory.
[Verizon Samsung Galaxy S III] &roid:
Latest stable after wiping with CWM.
[Verizon Samsung Galaxy S III] kerfex:
Still having Wifi issues

OK, When I was on 2.9 it was great except it would not connect to certain channels on a 5 GHZ WiFi. Works fine with any 2.4 GHZ WiFi. I switched to 2.10 because I had read in the thread that this issue should be fixed in 2.10 because it's Android 4.3. Well I am still having the same issue and can not connect to 5 GHZ WiFi. Anyone else having this problem? Should I try switching to the other radio's? (I535VRBMB1_firmware.zip)
[Verizon Samsung Galaxy S III] hallstevenson:
I've "heard" (saw thread titles but didn't read them) of others having this problem. You would think that an Android update, i.e. 4.2.x to 4.3, would solve that. I guess it could be a radio issue, but going back doesn't seem logical. Then again, it could be a regression in MF1 firmware.

A Google search is indicating that 4.3 in fact broke this. Have you tried a non-stock kernel ? Kernel devs may be able to fix this.
[Verizon Samsung Galaxy S III] kerfex:
Yeah, I think you are correct. Unless there is a bug in VRBMF1_Firmware. Ill try the older one and give an update tomorrow. Just saw your update. I was using BMS kernel with 2.9 but when I tried to use it with 2.10, I got stuck in a boot loop. Which kernel would you suggest? And thanks for the info and help!
[Verizon Samsung Galaxy S III] tarigand:
Anyone know why android os would be taking up so much battery? I am assuming that is the cause of the battery depleting. I am currently on WiFi and have been seeing this for the past couple of days.

Thanks
[Verizon Samsung Galaxy S III] hallstevenson:
BMS works fine with LS 2.10

---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------

Mine uses about the same %. I don't know if that's out of the ordinary. I checked a half dozen screenshots and they're all in the 12+% range. It's usually down the list though.
[Verizon Samsung Galaxy S III] tarigand:
Thanks for that.

So just tried to use the instagram video feature and just like every other time it crashes the camera and reboots. Now I'm getting this error on boot up. Is this a concern?

LS 2.10 BMS kernel
[Verizon Samsung Galaxy S III] kerfex:
I have tried twice to use he BMS kernel with 2.10 and I got boot loops each time. Weird. So I am trying the Ktoonsez KT747 kernel and all seems to be working fine now.
[Verizon Samsung Galaxy S III] hallstevenson:
Go into your recovery tool (CWM, TWRP, etc) and run the "fix permissions" tool.
[Verizon Samsung Galaxy S III] tarigand:
Did a search and that is what I found. Panicked. Should have searched first :rolleyes:
[Verizon Samsung Galaxy S III] thrgk:
Can someone please link the latest liquid smooth ROM download for Verizon s4? I am not sure which one to download from the list. I thought d2vzw but want to be sure
[Verizon Samsung Galaxy S III] kenbrownstone:
D2vzw is S3 not S4
[Verizon Samsung Galaxy S III] thrgk:
Which is s4
[Verizon Samsung Galaxy S III] hallstevenson:
Wrong thread. You want this one.
[Verizon Samsung Galaxy S III] DieselNY:
Hi was hoping someone can help me. Been on 2.9 for a month and all good. Just today for no reason a few sounds stopped working. Keyboard no longer makes the clicking sound. Same thing when I click any app on my home screen there is no sound. YouTube videos have no sound. I tried all the options in the sound settings and no luck. I even wiped and flashed 2.10 and it did not fix the problem.

When I go to the volumes and adjust the ring tone I hear the ring tone so I know the speaker works. Also when the keyboard shows spelling options and I click the word it makes the keyboard click sound but only then. It's crazy. Any ideas? Thanks.
[Verizon Samsung Galaxy S III] lou1210:
Try to reflash the ROM over it and see if the sound comes back.
[Verizon Samsung Galaxy S III] zamball:
Same error... after installing stable 10.1.3. I also upgraded to the newest version of TWRP v2.6.3.0. Re-downloaded both zips and followed:

Liquid 2.10 install steps:

Install ROM

Reboot system

Setup your phones settings, anything that isn't Google related or let your phone sit for 5 minutes

Reboot back into recovery

Wipe cache and dalvik

Install gapps

Reboot

still hangs on Samsung Galaxy SIII screen.

Any other thoughts?

Thanks for the help!
[Verizon Samsung Galaxy S III] cinco312:
Anyone know how I can get my device back in the play store menu? Ever since I flashed the latest build my device doesn't show up. I cleared all cache from Play services and Framework and everything else I can think of.
[Verizon Samsung Galaxy S III] &roid:
After wipe and install with CWM first boot took a good 10 minutes. After that and waiting the 5 more minutes, all worked fine for me.
[Verizon Samsung Galaxy S III] twistedillutions:
Haven't been here in a while been on BF threads over on SD anyways.. Im on 2.10 working fine i jst have a question does anyone one drop 384Mhz to 189Mhz on the for minimum usage im on BMS kernel
[Verizon Samsung Galaxy S III] rhamorsky:
If you followed these steps exactly as listed above, you did a dirty flash. have you tried the same instructions doing a wipe first? On the newest TWRP, wipe does factory reset, cache, and dalvik in one step or you can go in under advanced wipe and do them separately.
[Verizon Samsung Galaxy S III] picarito:
Does enybody know why the vibration strength in advanced settings in blocked in li

quid 2.10? Because I wanna change the vibration for the soft keys and it worked in liquid 2.9
[Verizon Samsung Galaxy S III] JRJ442:
Usually the kernel has to support it. Maybe it doesn't on this build. You could always try a custom kernel.

---------- Post added at 08:28 PM ---------- Previous post was at 08:22 PM ----------

I've seen some say its TWRP related, but I've had it happen on both CWM and TWRP. And I've also had it happen on every 4.3x ROM I've tried. I found wiping cache helps it boot again being stuck.
[Verizon Samsung Galaxy S III] picarito:
I do have BMS kernel installed tho
[Verizon Samsung Galaxy S III] beepea206:
I'm getting some random reboots since I flashed the newest version. Pretty random too. Here's the logs from kmsg:

I assume it's the 'modem' issue the kernel felt there was. Not sure if there's a fix. I'm on the stock/CM kernel, FWIW.
[Verizon Samsung Galaxy S III] RBarnett09:
Can someone on 2.9 pull the AOSP keyboard apk for me, please? It would be SUPER appreciated.

I want to test it on 2.10... though I know it may not be very successful.
[Verizon Samsung Galaxy S III] beepea206:
Isn't that this app? https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin
[Verizon Samsung Galaxy S III] cinco312:
http://goo.gl/zzb5mH
[Verizon Samsung Galaxy S III] Deltadood24:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

I use to hate valentines day.. Well today this made it a good one! Haha thanks for this awesome shenanigans team
[Verizon Samsung Galaxy S III] luis86dr:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

There's going to be a lot of pissed off wives/girlfriends today with this release. Gj! :p
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Did you wipe data and such?
[Verizon Samsung Galaxy S III] bobby janow:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Consider it a compliment and move on.
[Verizon Samsung Galaxy S III] narsciso:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Thanks for bringing us the goodgood, sir!
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

ROM is BEAST
[Verizon Samsung Galaxy S III] pinhead875:
Taken straight from the OP:

WE TAKE NO CREDIT FOR ANY WORK THAT COMES ASSOCIATED WITH THESE BUILDS UNLESS SPECIFIED OTHERWISE. ALL CREDIT GOES TO TEAMLIQUID, CYANOGENMOD, AOKP, SlimROMs & THOSE WHO HAVE CONTRIBUTED! THANKS FOR KEEPING THINGS OPEN SOURCE!

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

One thing I'm getting is Unfortunately Settings has stopped after trying to setup a pattern for the lock screen
[Verizon Samsung Galaxy S III] mademan420:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13
[Verizon Samsung Galaxy S III] swirly05:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

No Pie??
[Verizon Samsung Galaxy S III] lvgdgts:
I sure did. I'm great at following directions. I just don't know enough about these phones to be a good trouble shooter.
[Verizon Samsung Galaxy S III] jlikes08:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

So I flashed this, gapps, and kt747.

My home hardware button wouldn't work! What could have caused that? Known problem or what? Restored back to carbon for now.
[Verizon Samsung Galaxy S III] Always_Jonezen:
First off want say thanks. Will be flashing in a few. Has anyone tried file sharing with wifi-direct on this build it was not working on the last build.
[Verizon Samsung Galaxy S III] danstar:
I am thinking about giving this a try. Can we use inverted 4.2.1 gapps on this?
[Verizon Samsung Galaxy S III] Always_Jonezen:
A couple of post back someone posted that they are using inverted gapps and are happy with it
[Verizon Samsung Galaxy S III] droidxxxxx:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Hmmm..well maybe its just me then? Does GPS work for everyone? I wonder why it would do that for me only on 4.2 Roms..but works fine on most 4.1 Roms..
[Verizon Samsung Galaxy S III] luis86dr:
Re: [ROM][4.2.2][RC1] LiquidSmooth ROMs - d2vzw & d2usc - 2|14|13

Make sure before flashing you wipe Data, System, Cache, and Dalvik Cache. Also check your download. Make sure your MD5 matches. Few MD5 checker apps on the play store. Just food for thought.
[Verizon Samsung Galaxy S III] bitemeoftn:
So I looked through and tried everything in the Q & A section but I still can't get my wireless tether working. I can however tether with USB. Just wondering if anyone might have any suggestions on how to fix this. Thank you in advance.